First of all I do experience lots of hungapps (Not responding) status when operating this program.

Usually it crashed on me when hiting serial port button. Then when I finally managed to brake through hungups this is what I saw:

http://img291.imageshack.us/img291/141/bliat.th.jpg

It's not like there (Com 1 should read N N N N Y Y on the signals)

and after I put the dot on com1 and hit OK it hungups again :nope:

I did disconnected the UPS end of the cable, completely switched off pc. Turned it on back again. And there were still lots of hungapps. :06:

When I disconnected the RS 232 cable from pc restarted and ran the digicom.exe again signals changed to N N N N Y Y on com1, but hangups still occur

Nothing like a challenge, but I would just get a USB cable and hook it up that way.

There is no usb connection on my ups. But I'm thinking RS 232 to usb converter cable might work..

Oh ok, you mentioned getting one in the first post.

Like said before, double check your BIOS to check the comm port settings.

Checked that in first place it's set to: 3F8/IRQ4 (COM1) as it should be..

BTW I'm having different system and boot discs. My system drive is C: but OS boots from drive D:

I would like to move boot files to system drive C: but still not sure how ? :hmmm:

Could this be related somehow to issues with serial port com1 ?

I found some info about it here: http://www.techspot.com/vb/all/windo...ot-sector.html

But I'm still not finding it clear what was ment to do at the second post from the top there..

Ok so I reinstalled OS now the program ain't crashing anymore. But signals on COM1 shows Y N Y Y Y Y with cable pluged in to pc. I suppose cable might be the bad ?

Contact - do the wrap test as I suggested in my email - click wrap and short pins 2 and 3 - if it fails the port is bad and you will need to use a usb2serial adapter. If it passes - well - I don't know at that point.

ynyyyy is what I would expect from a working cable plugged into a UPS.

Shorting of 2 and 3 pins test passed. I can see sent/received when doing so.

But this is the only test I was able to make because signals are: DCD - red; RI - green; DSR - red; CTS - red.

I suppose they should be all green there as you mentioned in that readme you've sent me ?

When the cable is plugged up they will be r g r r

When you unplug the cable - they should realtime update to all green

RI - should never go red - it stands for ring indicator and is your pc's way of saying its connected to a ringing telephone.

Getting nnnnyy when the cable is unplugged and ynyyyy when the cable is plugged in - and also passing the wrap test - means the port on the pc is good. I assume you ran the test thru the cable - and if so that means the cable is good to.

That leaves 2 possibilities - a glitch in the software - or a problem with the port on the Ups itself. No way to check the second possibility really unless you have an exact duplicate UPS.

UPS's can be run either via the com port, or a USB cable. Most APC's have both. When connected via USB, you are not using the COM port. Reconfigure your software to look for a USB device. Windows should have detected it upon plugging it in.

The COM port seems to be already in use on your device manager tab. That means you either need to use a real RS-232 cable (make sure you don't use a null cable - it won't work) on COM 1, or use the supplied USB cable. You will not be able to make the system use COM1 when COM1 exists on your system for a real device/port that exists. You are creating a conflict.

-S

Subman - Com 1 in device manager doesnt show anything other than the device is there. It doesn't mean its in use.

True, but since it shows up, it is 'already' reserved. You guys either need to use another COM port that is not already reserved, or switch to using that physical COM port with an RS-232 cable. If his app is trying to make a USB connection look like COM1, you will fail.

This also may be difficult with all the damn Bluetooth reservations he has to try and use another COM port. Most apps that deal with COM ports will only use 1 through 4.

-S

He is trying to use a straight 232 (serial) cable - no usb adapter involved. Regular mb serial port. The app I sent him does nothing more than verify the port doing loopback, cts and dsr tests.

The port is passing (and running the app will also tell us if its in use by another provess) - so its either the port on the ups (which is really doubtful) - or something in the software.

Thinking.... Making sure it is not a Null modem cable - checked?

App upgrade? Maybe he has a wrong rev for his app?

Let me think if I have any other ideas.

-S