My Ocelot has been churning along without attention for about six years. Years ago the PC I used to connect to the Ocelot died.
Now I am unable to connect with a newer PC. I've tried both the "d" and "e5" versions of Cmax with the same results - when I select "Attach to Controller" Cmax immediately starts spewing dialogs with an "Apro Exception." message. The only way to halt this is to kill Cmax in Task Manager.
I am running Windows XP SP3 and using the stock COM1 port on a Dell Inspiron 8200 notebook. The Ocelot is working fine, I would just like to make some changes to the program.
Apparently the reason I am unable to connect is the serial port is not functioning. I've attempted to connect to a CM11A via Active Home software through COM1 with same result. Since this unit includes its own cable I feel this has eliminated concern that the problem might be with Ocelot or my serial cable.
If anyone can suggest what else I should check I would appreciate it. My computer is a six year old Dell Inspiron 8200 notebook running XP Professional SP3. Here is what I've done:
1. Verified COM1 is enabled in bios. 2. Uninstalled and reinstalled COM1 in Device Manager. 3. Verified there are no IRQ conflicts. 4. Disabled the internal modem which is on COM3. 5. Searched registry and group policies to see if I did something in the past to disable COM1 - may have but it isn't obvious to me. But I have this nagging feeling I have seen something in the past about disabling COM port polling to improve computer performance.
Unfortunately I don't have a loop back connector but I am willing to get one if it will help me resolve this. Any tips on best way to troubleshoot a COM port that isn't working?
Ok, got it working but not sure why. In the bios settings I changed the COM port from COM1 to COM2. Device Manager still shows COM1. Doing this caused COM1 to "wake up". I then was able to connect to Ocelot.
