Hi Curiosity, thanks for taking your time out for me.
If when I'm using XPort to split the ports for other usage, I've not selected any usb devices in XPort as I don't think I'm having any of them misbehaving when resuming.
The next time the com1 gps resumed correctly out of hibernation, I'm not going to change anything (while taking note of other programs that were running before hibernation and if they resume correctly, including the usb devices I have) and let it hibernate the same way for a few days and runs to see if there's any consistency.
If the answer to my previous qns if other usb devices could prevent the com1 from resuming correctly is yes they do then I suppose I'll have even a harder time to troubleshoot as none of the usb devices seems to misbehave. If it comes down to this, then I'll take note of your advise above.
Following your previous explanation, XPort does detects the com1 as 9600 when the com1 is working correctly. Does that means the baud rate settings is correct at 9600?Quote:
I still don't understand why you are setting everything to 9600 when the GPS is sending at 4800. It's just causing more problems.
I can't recall manually setting com1 baud rate to 9600 as it should already be the default. Perhaps in CF I did as the default could have been 4800.
Do I still have to set them to 4800 both on com1 and CF despite both G4 and CF manuals state to use 9600?
Will a opened GPS appz be it CF Navigator or Garmin caused any issues if left opened during hibernation and susequently resume? Or it depends whether the baud rate are set correctly in these appz? If it does affect, I could disable CF Navigator or set it to 4800 as advised and close Garmin (cos Garmin does not have baud rate settings) before hibernating but this makes using a car pc so painful. There were times during troubleshooting the com1 gps resumed correctly despite these appz were opened and appz obviously carried on working where it left off.
Wonder if the following screen shot gives you any clues. As you can see when the com1 gps port does not resume correctly, you'll see garbage/weird characters in the status bar. Hitting scan does nothing as it will say no gps found.
My vendor previously use the default bios cfg so I assume it was shipped with the OS preinstalled this way. I did read newer OS (including WinXP) will still turn on ACPI even if it's off in bios. I did try with it on but overlook checking the device manager ACPI. I appreciate very much that you have brought up stuffs I need a second look. Wonder where the drivers to update ACPI comes from?Quote:
Changing ACPI in the BOIS without reinstalling Windows can cause sleep and hibernate to not work properly. You should at least update your kernel in Device Manager, under "Computer". You should be using USB 2.0 and ACPI enabled.
As far as USB, can you list all the devices plugged directly into the PC and how many hubs? What's plugged into the hub(s)? Are they powered?[/QUOTE]
The only device I have plugged in directly to 1 of the 2 rear usb ports was the keyboard which I've since plugged out and now plug in to the front port only when needed as the rear port now is dedicated to my Touch HD Mobile PC as it had issue going through a hub. Even then as part of my troubleshooting, I do not plug in the Touch HD. The other rear port is connected to a quality Berklin usb hub (unpowered at the moment) located at the back of my boot. Connected to this hub is the Huawei E270 USB modem and Asus Wireless G Adaptor (combined 500mA+300mA if I'm not wrong and though appear drawing more than usual 500mA per port available but everything on here seem to work fine) which so far does not appear to have any resuming issues. This hub was previously powered by either drawing power from one of the internal unused usb port of the previous Hi-info N5 car pc or combined in such way from the battery as well (not sure of the details as it was done by my dealer) but he say G4 is much more stable and no longer need such a mod.
Again, thank you so much for assisting which I know does take alot of your time.