kc0ws
New Member
Posts: 23 
|
Post by kc0ws on May 30, 2009 15:33:34 GMT -5
I tried the AIM program on my Toshiba Tecra A9 laptop and as soon as the program gets past the tiny "COM1" box, it opens the main window and puts the //./COM port open message up, and then it stays there. Doesn't make any difference whether there is anything plugged into the port or not. This is a real port on the laptop (not USB), and it seems to be normal, but the program gets stuck. Only way to get out is to kill the program (will not exit or respond in any way.) I can't even try a USB port easily, as the program never gets that far (unless I went in and edited the configuration file manually).
I searched for a similar issue in the forum, but didn't find any. Hope I don't have a unique problem, as I am taking the PowerAIM 120 to a seminar I am taking next week, and am planning to use it to measure components.
|
|
|
|
Post by Bob on May 30, 2009 17:58:24 GMT -5
I have read about the A9. It looks like a really nice computer. A notebook with a serial port is nice. If you copied the AIM files from another computer, be sure to check the com port number. It's saved in the ini file and the port may be different on different computers. Use the Device Manager to make sure the A9 serial port is assigned "com1". It should start up at 57.6K.
It is very strange that the program hangs up, I don't recall seeing that even when the com port is not working. If the AIM is unplugged from the computer, the program still runs ok and goes into the demo mode. (You can load stored scan files in the demo mode.) There must be something different about Vista Business. Maybe a Vista guru can advise us on this.
-73/ Bob
|
|
kc0ws
New Member
Posts: 23
|
Post by kc0ws on May 30, 2009 21:29:39 GMT -5
I should have included more details, but am trying to pack this afternoon and evening. I have read about the A9. It looks like a really nice computer. A notebook with a serial port is nice. If you copied the AIM files from another computer, be sure to check the com port number. It's saved in the ini file and the port may be different on different computers. Use the Device Manager to make sure the A9 serial port is assigned "com1". It should start up at 57.6K. I have the software on a USB stick (since it doesn't "install" anything outside its directory structure. Both this and the last computer are using COM1: It does connect to COM1:, and it changes the speed to 57600 from 9600. It is very strange that the program hangs up, I don't recall seeing that even when the com port is not working. If the AIM is unplugged from the computer, the program still runs ok and goes into the demo mode. It should, but it doesn't unless there is already another copy of the program running (so it can't get to the port), in which case it comes up with the port info in red, and runs in demo mode. It won't get to demo mode if it is the first copy run. There must be something different about Vista Business. Maybe a Vista guru can advise us on this. Actually I ordered this laptop downgraded to XP, so it is running XPSP2 (IT at work is skipping the Vista generation). In case it helps, I also ran 675A with the same result. I am willing to run a version with debug/logging/instrumentation, if that would help. I will have time on my hands evenings while I am at this training session. Also, I just reran a test to make sure I had everything straight, and I had to tell Windows to "shoot that horse". After shooting the horse, Windows volunteers to send a crash report to Redmond. I copied those four files (did not send report) to another directory, so I can send them to you if they would be helpful. One is 1.6MB, so too big to post, but should be able to email them. |
|
|
|
Post by Bob on May 30, 2009 23:00:15 GMT -5
I just tried it using a USB stick on my laptop running Vista Home Premium and a usb interface on com4. Also using a regular serial port (com1) on another computer running Win 2K. The usb stick is ok in both cases here.
Its important to have the complete program in the same folder on the usb stick, especially the default_config.cfg file. Some older versions of the config file are not compatible. Version 684 displays a warning about this.
73/Bob
|
|
