Date   
Re: CAT sharing in N1MM+

Andy k3wyc
 

"Panadapters, rotators, StepIRs antenna's and N1MM+ are all in need for the CAT connection at the same time. The work arround with LP Bridge or VSPE is not that easy and also not without impact on the stability of the CAT connection.
So we are definitly in need for some kind of CAT sharing possibilty in N1MM+ itself. "

Kees,

I don't know the full details of your setup but I use PSTRotator A (not PSTRotator) for connecting my SDA100 SteppIR controller and my rotator controller to N1MM+.  This setup removed the need CAT port sharing.   Also works well with DXLabs.

 http://www.qsl.net/yo3dmu/index_Page346.htm

I don't control a panadapter and don't know if they are supported.
 
73,
Andy k3wyc



---In N1MMLoggerplus@..., <pa5wt100@...> wrote :

John K3CT quickly responded on my request to make, in RUN mode, the RIT available on the keyboard when using my FTdx3000. I tested it out in a experimental version of N1MM+ he made. This function is working very fine and now during a run the RIT can be tuned from the keyboard. That's what I need in cw.
When checking in S&P mode I noted some not very reliable behaviour when tuning the rig from the keyboard. After some tests I find out this was caused by the program LP bridge which I am using for sharing the CAT connection between N1MM+ and my panadptor program. When connecting N1MM+ the my set directly all worked fine but my connetion with the panadaptor was gone!  Now I tryed using VSPE instead of LP Bridge and for unknown reasons this works better. Only every now and then there is some blinking of the frequency.
I assume the tuning issue with my FTdx3000 was due to collisions of the CAT commands from the both programs I am using.

Panadapters, rotators, StepIRs antenna's and N1MM+ are all in need for the CAT connection at the same time. The work arround with LP Bridge or VSPE is not that easy and also not without impact on the stability of the CAT connection.
So we are definitly in need for some kind of CAT sharing possibilty in N1MM+ itself.     


73, Kees PA5WT

CAT sharing in N1MM+

Kees de Wit
 

John K3CT quickly responded on my request to make, in RUN mode, the RIT available on the keyboard when using my FTdx3000. I tested it out in a experimental version of N1MM+ he made. This function is working very fine and now during a run the RIT can be tuned from the keyboard. That's what I need in cw.
When checking in S&P mode I noted some not very reliable behaviour when tuning the rig from the keyboard. After some tests I find out this was caused by the program LP bridge which I am using for sharing the CAT connection between N1MM+ and my panadptor program. When connecting N1MM+ the my set directly all worked fine but my connetion with the panadaptor was gone!  Now I tryed using VSPE instead of LP Bridge and for unknown reasons this works better. Only every now and then there is some blinking of the frequency.
I assume the tuning issue with my FTdx3000 was due to collisions of the CAT commands from the both programs I am using.

Panadapters, rotators, StepIRs antenna's and N1MM+ are all in need for the CAT connection at the same time. The work arround with LP Bridge or VSPE is not that easy and also not without impact on the stability of the CAT connection.
So we are definitly in need for some kind of CAT sharing possibilty in N1MM+ itself.     


73, Kees PA5WT

Re: Installation problem

Andy (KU7T)
 

Bruno and others,

 

This and similar issues are best trouble-shooted with the right information.

 

Can you please send 1) install.log from the N1MM+ application folder, 2) LogError.txt from the N1MM+ user folder (if exists) and 3) any other Application Event log error entries (type eventvwr inside cmd.exe) to us at ProblemReports@...

 

Thanks

Andy

KU7T

 

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Wednesday, July 22, 2015 5:11 PM
To: N1MMLoggerplus@...
Subject: [N1MMLoggerplus] Installation problem

 

 

Hi,

A couple of weeks ago something ’hit’ my Windows 8.1 computer making it inoperarable. The serviceshop uninstalled programs, including N1MM+, i in order to locate the problem.Today I got the computer back in good working condition, I think. However, when I tried to install anew N1MM+ it failed. The reject message (in Swedish) tells me that it is not possible to find the search path to the desired unit. I ran as administrator. What can I do?

73

Bruno / SA6AXR

 

Re: Installation problem

Vytenis LY5T
 

Hi Bruno,

I'm afraid, if OS is in Swedish its bit tricky. If it was in English,Google would help find many answers. I'd go into  C:\Program files\N1MM+\ (or C:\Program files(86)\N1MM+\ if 64 bit) and open install.log. Examine its content. It may show something interesting. As always, take a look into Windows eventviewer for error events during installation time.


GL
Vytenis
ly5t

Re: WAE CW Question

Bob Evans
 

Thanks Mike.

Yes, I've loaded in a hundred dummy Qs and played around with sending QTC batches.  That runs smoothly but I always have to work through the "599 0" sending done when I hit CTRL-Z.  At the moment, my workaround is just to hit ESC before the "599 0" gets sent but I'm hoping I don't need to do that throughout the contest.

It's got me stumped!  ;-)

Bob K5WA

Installation problem

Bruno SA6AXR
 

Hi,

A couple of weeks ago something ’hit’ my Windows 8.1 computer making it inoperarable. The serviceshop uninstalled programs, including N1MM+, i in order to locate the problem.Today I got the computer back in good working condition, I think. However, when I tried to install anew N1MM+ it failed. The reject message (in Swedish) tells me that it is not possible to find the search path to the desired unit. I ran as administrator. What can I do?

73

Bruno / SA6AXR

 

Re: WAE CW Question

VE9AA - Mike
 

Hi Bob,


You may need some fake QSO's in the bank, for the fake QTC's to send properly as you are doing your testing.  At least that's how I recall it from several years back before I did one.  Not sure if this is where the 0 is coming from.  Seems a tad odd, but I am sure some testing will show why that is happening.


Also, QTC's for the CW and SSB legs, wont send if the program thinks you are in EU (I doubt that's he case, but thought I'd mention it as I have seen it before)  I think RTTY will work- as the rules are a bit different.


ON5ZO's explanation was truly excellent !


Mike VE9AA



---In N1MMLoggerplus@..., <k5wa@...> wrote :

Franki,

 

Thank you very much.  This is exactly what I needed.  I’m going to digest this to see if it answers my question about NL+ sending “599 0” when CTRL-Z is pressed.

 

73,

Bob K5WA

 

 

 

Bob, let's do a short walk through.

Apart from the QTC game, it's just a serial number contest between EU and DX (i.e. non-WAE countries). You do not need to send QTC if you're not in it to put down a big score but
of course the demand from EU will be huge. And we appreciate the QTCs.
DX (i.e. non-EU) can offer the EU to send QTC or accept a request initiated by a EU station.

Some sound files available I received many years ago but I forgot from whom:
http://users.telenet.be/on5zo/audio/QTC.zip


Re: WAE CW Question

Bob Evans
 

Franki,

 

Thank you very much.  This is exactly what I needed.  I’m going to digest this to see if it answers my question about NL+ sending “599 0” when CTRL-Z is pressed.

 

73,

Bob K5WA

 

 

 

Bob, let's do a short walk through.

Apart from the QTC game, it's just a serial number contest between EU and DX (i.e. non-WAE countries). You do not need to send QTC if you're not in it to put down a big score but
of course the demand from EU will be huge. And we appreciate the QTCs.
DX (i.e. non-EU) can offer the EU to send QTC or accept a request initiated by a EU station.

Some sound files available I received many years ago but I forgot from whom:
http://users.telenet.be/on5zo/audio/QTC.zip


Re: Logger halting with RFI

gbyahoo@...
 

You can try this:

Right-click on that radio's bandmap and choose 'Reset Radios' to restart the connection.

>> Gerald, VE1DT


---In N1MMLoggerplus@..., <k6ddj599@...> wrote :

Hello,
     I have a small intermittent problem with RFI.  Despite the effort and progress made in fixing my RFI problem, every once in a while when I am tuning up on changing frequencies, N1MM will stop.  No radio control at all.  I just have to shut N1MM+ down and restart it again.  Now, I also use Ham Radio Deluxe and when this happens with HRD, the program immediately reconnects to the radio and I continue on.  N1MM however does not try to reconnect as far as I have been able to determine.  Is there somewhere in the program settings that I can have the program try to reconnect upon loss of radio connection?

Thanks,
Dean K6DDJ

Logger halting with RFI

Dean Jones <k6ddj599@...>
 

Hello,
     I have a small intermittent problem with RFI.  Despite the effort and progress made in fixing my RFI problem, every once in a while when I am tuning up on changing frequencies, N1MM will stop.  No radio control at all.  I just have to shut N1MM+ down and restart it again.  Now, I also use Ham Radio Deluxe and when this happens with HRD, the program immediately reconnects to the radio and I continue on.  N1MM however does not try to reconnect as far as I have been able to determine.  Is there somewhere in the program settings that I can have the program try to reconnect upon loss of radio connection?

Thanks,
Dean K6DDJ

Re: Frequency tolerance

John Bednar
 

John,



The release note is accurate.


The program change only modified the decision of when to display the Station Call in the Info Window.


John, K3CT

On 07/22/15, w9ily@... [N1MMLoggerplus] wrote:






























The most recent update included an increase in frequency tolerance for spot messages in the info window. Did this increase the frequency tolerance for the bandmap as well? I have noticed that when several calls are displayed on the bandmap in close proximity to each other the wrong call is often displayed above the entry box and that call is quite a bit further from the actual receiver frequency than my desired station. How can the correct call be entered in the entry box other than clicking on it which will than change the transmit/receive frequency? Of course, typing the correct call works but I am hoping there is an easier way. Thanks.
John W9ILY

Frequency tolerance

John Holmes W9ILY
 

The most recent update included an increase in frequency tolerance for spot messages in the info window. Did this increase the frequency tolerance for the bandmap as well? I have noticed that when several calls are displayed on the bandmap in close proximity to each other the wrong call is often displayed above the entry box and that call is quite a bit further from the actual receiver frequency than my desired station. How can the correct call be entered in the entry box other than clicking on it which will than change the transmit/receive frequency? Of course, typing the correct call works but I am hoping there is an easier way. Thanks.
John W9ILY


Re: crash

Steve London
 

Stop N1MM+, delete LogError.txt and recreate the error. You will then have a much smaller LogError.txt to work with.

73,
Steve, N2IC

On 07/22/2015 08:40 AM, wb1edi@... [N1MMLoggerplus] wrote:
here is the fiirst few lines from one of the logerror files. they are
5-6 Mb files.
i do not know what to look for.
thanks
barry

System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32
msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at
System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr
dwComponentID, Int32 reason, Int32 pvLoopData)
at
System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32
reason, ApplicationContext context)
at
System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32
reason, ApplicationContext context)
at System.Windows.Forms.Application.RunDialog(Form form)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at System.Windows.Forms.Form.ShowDialog()
at N1MMLogger.Net.EntryWindow.ShowErrorMessageWindow(String
messageText) in Logger.Net&#92;Forms&#92;EntryWindow.vb:line 16883
at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName,
String Info) in Logger.Net&#92;Modules&#92;SharedCode.vb:line 226
at N1MMLogger.Net.CWIFInterfaceClass.HandleNonXMLMessage(Object&
data, String& aStr) in Logger.Net&#92;Classes&#92;CWIFInterface.vb:line 584
at N1MMLogger.Net.CWIFInterfaceClass.HandleMessage(Object& data) in
Logger.Net&#92;Classes&#92;CWIFInterface.vb:line 546
at N1MMLogger.Net.EntryWindow.HandleSerialMessage(Byte[] arr) in
Logger.Net&#92;Forms&#92;EntryWindow.vb:line 17259
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[]
arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object
obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at
System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry
tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object
obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
at
System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at
System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32
msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at
System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr
dwComponentID, Int32 reason, Int32 pvLoopData)
at
System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32
reason, ApplicationContext context)
at
System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32
reason, ApplicationContext context)
at System.Windows.Forms.Application.RunDialog(Form form)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at System.Windows.Forms.Form.ShowDialog()

Re: crash

barry whittemore
 

here is the fiirst few lines from one of the logerror files. they are 5-6 Mb files.
i do not know what to look for.
thanks
barry

 System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.RunDialog(Form form)
   at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
   at System.Windows.Forms.Form.ShowDialog()
   at N1MMLogger.Net.EntryWindow.ShowErrorMessageWindow(String messageText) in Logger.Net\Forms\EntryWindow.vb:line 16883
   at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info) in Logger.Net\Modules\SharedCode.vb:line 226
   at N1MMLogger.Net.CWIFInterfaceClass.HandleNonXMLMessage(Object& data, String& aStr) in Logger.Net\Classes\CWIFInterface.vb:line 584
   at N1MMLogger.Net.CWIFInterfaceClass.HandleMessage(Object& data) in Logger.Net\Classes\CWIFInterface.vb:line 546
   at N1MMLogger.Net.EntryWindow.HandleSerialMessage(Byte[] arr) in Logger.Net\Forms\EntryWindow.vb:line 17259
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.RunDialog(Form form)
   at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
   at System.Windows.Forms.Form.ShowDialog()

Re: Simple SO2R question

Jim W7RY
 

Sorry Mike. Those all go into the deleted folder. It’s really simple to click the box that says “show message history” when you reply... Like the list owners want you to do.
 
 
>>For Jim W7RY...there was only one thread entitled "Simple SO2R question" and if you would look in your email inbox, I am sure it arrived within the past xx hours.
 
>>Mike VE9AA dit dit

73

Jim W7RY

 

Re: USB sound cards

Jim W7RY
 

Test.
Showing message history.

73
Jim W7RY



---In N1MMLoggerplus@..., <jimw7ry@...> wrote :

John
I forgot that you can name them. It’s been a while since I've been in the shack.
 
I named mine to which radio I have them hooked to.
 
Great idea.
73
Jim W7RY
 
 

Sent: Wednesday, July 22, 2015 2:33 AM
Subject: RE: [N1MMLoggerplus] USB sound cards
 
 

Logger+ Audio also stores the soundcard endpoint name (friendly name) to eliminate the audio device shuffling problem. It also restores the soundcard mixer audio level on normal program exit.

If duplicate soundcards are installed the friendly name should contain a 1, 2, etc.

John, K3CT

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Wednesday, July 22, 2015 5:00 AM
To: N1MMLoggerplus@...
Subject: RE: [N1MMLoggerplus] USB sound cards

 

Adding a sound card (that could be in built to a VNA or a SDR) can and does alter the “pecking order” that Windows perceives the sound cards to be. The default sound card can change. This can cause confusing where software uses the sound card Windows number rather than the sound card end point name.

So you had what was thought to be MMTTY (and most other programs) all set up and next time it does not work as expected. You may have plugged in your USB SDR or a USB VNA or even an ordinary USB sound card since you set up MMTTY. This then changes the sound card numbering and MMTTY is now looking at the wrong sound card.

2Tone avoids this problem as it remembers the sound card endpoint name (Vista and later) rather than the number, but it can be confused if you install two exactly the same sound cards as they have the same end point name.

73 David G3YYD

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: 22 July 2015 03:56
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] USB sound cards

 

On Tue,7/21/2015 8:00 PM, 'Jim' jimw7ry@... [N1MMLoggerplus] wrote:

> That is why I would not use identical cards if you can avoid it.

My writeup listed a half dozen very good USB sound cards with stereo
Line ins and Line outs. The newer one, the ASUS Zonar U5, sells for
about $70. So one sound card gives you both radios for SO2R! There's
even an additional $10 rebate until the end of July.

For SO2R RTTY, I'm using 2Tone as my primary interface because it can
use the sound card in stereo to feed the two radios independently. MMTTY
only does a mono out.

73, Jim K9YC

Re: USB sound cards

Jim W7RY
 

John
I forgot that you can name them. It’s been a while since I've been in the shack.
 
I named mine to which radio I have them hooked to.
 
Great idea.
73
Jim W7RY
 
 

Sent: Wednesday, July 22, 2015 2:33 AM
Subject: RE: [N1MMLoggerplus] USB sound cards
 
 

Logger+ Audio also stores the soundcard endpoint name (friendly name) to eliminate the audio device shuffling problem. It also restores the soundcard mixer audio level on normal program exit.

If duplicate soundcards are installed the friendly name should contain a 1, 2, etc.

John, K3CT

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Wednesday, July 22, 2015 5:00 AM
To: N1MMLoggerplus@...
Subject: RE: [N1MMLoggerplus] USB sound cards

 

Adding a sound card (that could be in built to a VNA or a SDR) can and does alter the “pecking order” that Windows perceives the sound cards to be. The default sound card can change. This can cause confusing where software uses the sound card Windows number rather than the sound card end point name.

So you had what was thought to be MMTTY (and most other programs) all set up and next time it does not work as expected. You may have plugged in your USB SDR or a USB VNA or even an ordinary USB sound card since you set up MMTTY. This then changes the sound card numbering and MMTTY is now looking at the wrong sound card.

2Tone avoids this problem as it remembers the sound card endpoint name (Vista and later) rather than the number, but it can be confused if you install two exactly the same sound cards as they have the same end point name.

73 David G3YYD

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: 22 July 2015 03:56
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] USB sound cards

 

On Tue,7/21/2015 8:00 PM, 'Jim' jimw7ry@... [N1MMLoggerplus] wrote:
> That is why I would not use identical cards if you can avoid it.

My writeup listed a half dozen very good USB sound cards with stereo
Line ins and Line outs. The newer one, the ASUS Zonar U5, sells for
about $70. So one sound card gives you both radios for SO2R! There's
even an additional $10 rebate until the end of July.

For SO2R RTTY, I'm using 2Tone as my primary interface because it can
use the sound card in stereo to feed the two radios independently. MMTTY
only does a mono out.

73, Jim K9YC

Re: crash

Vytenis LY5T
 

Are there any relevant messages in N1MM+ Logerror.txt or Windows Eventviewer?

Vytenis
ly5t

crash

barry whittemore
 

NE1F and I have had a persistent issue since the switch to logger plus.

we have a unique situation compared to most.

We have two PCs connected through an RS232 switch that has been modified to have the TX from the rig tied to bot RX lines on the two PCs.
This has allowed us to each track what the radio is sending out as long as one is controlling the radio.
PCs are both Win 7 with real RS232 not USB adapters.


The rig is K3 at 38400 baud.

The problem did not ever exist with logger but showed up with logger plus.

all works fine for a while but eventually the PC that is not in control gets a crash and the box pops up asking to send data. at that point it is completely locked up and the only option is to run task manager and force shutdown of program.  We have noticed that if left alone it sometimes will pop up the force close box after about 30 mins.

Most of the time it occurs on the NE1F PC as she is usually not the controller but when she is it happens on NF1O PC so it does not appear to be related to one PC.

We have occasionally gotten the error box on a PC that is in control and it is easily cleared and recovered from.

Any ideas on what we can try?

Thanks
Barry
NF1O


Re: Simple SO2R question

VE9AA - Mike
 

Hi Andy, 

I always use the online YAHOO interface, that way my email inbox is not plugged with hundreds of emails everyday from the dozen groups I am subscribed to.  Up until recently, Internet alone for me was VERY expensive....up to $260/month, so every Mb or even kb counts !...I am a little better off now, but it's the price you pay for living in rural NB. People in populated W or VE or EU probably cannot fathom this.

For Jim W7RY...there was only one thread entitled "Simple SO2R question" and if you would look in your email inbox, I am sure it arrived within the past xx hours.

I had a simple question and there were 3 or 4 great ops who were nice enough to collectively answer them. 
All replies to my thread were acknowledged and I really do appreciate each and every one of them for the various data they provided to me.  It really boiled down to the very moment I found a stn on the second radio and what occurs in the 3-4 seconds it takes to work them....and the keystrokes involved.  Not much more than that. Key to me, but simple for guys who do SO2R every contest.

Thanks to Ted, Steve, Rick etc(who did I forget?). for the FB info !

Mike VE9AA dit dit