Posted 07 May 2011 - 01:01 PM
I have uninstalled Ascom, and reinstalled it, as well as EQAscom. I have updated .Net framework and still the same error. I've looked online and can't find any answers.
Anyone have any ideas?
Posted 07 May 2011 - 01:55 PM
Posted 07 May 2011 - 07:58 PM
If the port has traffic on it while Windows starts, the system will think it's a mouse and open it itself, which is consistent with your error message. Disconnect the serial cable or shut down the mount while booting and see if that helps. What version of Windows are you using? XP?
Another possibility: has the serial port number the USB adapter uses changed?
Posted 07 May 2011 - 08:30 PM
I'm really stumped.
Posted 07 May 2011 - 11:00 PM
Nobody said anything about you using a mouse. When Windows sees activity on a port during bootup, Windows decides that port must be a mouse. It doesn't matter that the device isn't really a mouse. When this happens one must go into Device Manager and disable (I say disable, NOT delete) the bogus "mouse" device, then reboot. If you delete the bogus mouse device, it'll just come back on reboot. That's why you must disable rather than delete it. Please go into Device Manager and see if a bogus mouse device is present. That is what the above poster was trying to tell you.
I'm not using a mouse, it's a laptop.
Posted 07 May 2011 - 11:23 PM
Posted 07 May 2011 - 11:52 PM
Posted 07 May 2011 - 11:54 PM
Posted 08 May 2011 - 11:29 PM
This is the last resort - I would try all other suggestions first.
Posted 09 May 2011 - 05:01 PM
Now, on my Windows XP machine, after the update I didn’t lose ASCOM but had to reload the driver program for the RS-232/USB converter, it ‘lost’ the comm port it was assigned to. It showed as ‘active’ in device manager, but it wouldn’t play until I reloaded the driver.
Posted 09 May 2011 - 07:48 PM
Posted 09 May 2011 - 07:51 PM
Posted 09 May 2011 - 07:58 PM
Rusty, do you happen to know the number of the update(s)?
I'll check in a few minutes. The error code I keep getting has to do with the NetFrame version, the update deleted it in favor of a different version, and it won't accept the older version EQ likes. On my XP machine, it isn't a problem for some reason.
Posted 09 May 2011 - 08:50 PM