CF-18 COM1 unable to start.

Hi,

I just recently noticed that in device manager, COM1 has a yellow exclamation mark beside it. under device status it says 'this device cannot start (code 10).

model number is CF-18KHHZXBM and is running windows 7 ultimate.

I noticed this problem the other day and can't even tell what hardware exactly COM1 is related to. My rear serial port is COM 2, and my GPS card is COM 3... I figured this out by disabling the serial port and gps in the BIOS.

Does anyone know what other serial devices are in this toughbook?

thanks

 

I'd guess it's your Touchscreen; it's probably been subsumed by the Touchscreen HID driver. Others here may know better than I do, however; I've never owned a CF-18 or 19.

mnem
*Still in love with my fine 29*

 

with conflict. Reset your bios to default then save & exit. Or change it to another port not in use.

ohlip

 

I'd like to but can't determine what device COM1 is... Rear serial port is COM2, internat GPS is COM3, what other hardware could be COM1?

 

What Ohlip was saying, is go to the bios, and set all the com ports to "auto" (or just "restore to default settings" for the whole bios), reboot your computer, and then use a program to search your com ports for your GPS (like GPSinfo)

It should detect your hardware, as well as tell you what baud rate your gps is operating at.

 

Like I said before, most likely it is your Touchscreen. The driver for the Touchscreen takes over the port.

mnem
*Touched*

 

I understand what he was saying. What i was getting at was regarding the second part of his post... I can't change it to a port not in use when i don't know what device is causing the issue. Also, when a device cannot start it doesn't use any resources so there's no IRQ conflict.

My CF-18 has two serial ports, the DB9 connector on the back and the other internal which is currently occupied by my GPS module. A third com port was showing up, turning all the ports to off or auto in the bios didn't do anything (initially).

I know what you're getting at but the touch-screen shows up properly in the bios as well as other on-board serial devices like the touch-pad, keyboard, etc.

I've since resolved the issue and it was (i believe) actually caused by the GPS.

The hardware ID of the com port in question was:
ROOT\*PNP0501\1_0_17_0_0_0

After setting the bios to defaults then disabling the GPS, it was still there.

In the process of trying to figure this out I had formated and re-installed windows 7 about 4 times over the course of this week. But i was using the install CD to format and it was only doing a quick format. I used the recovery console to do a proper format and then re-installed windows 7 yet again.

Upon boot up the mystery device was gone.

started installing drivers and programs.

When i tried to apply the GPS fix i got an error saying the registry was not accessible. Looking at the .reg file the key was [HKLS\SYSTEM\CurrentControlSet\Enum\ACPI\ PNP501\1\DeviceParameters]
"SkipEnumerations"=dword:fffffffe

That bolded part got me thinking that this could somehow be related to the mystery device showing up in device manager. Further looking at the registry the *\1\ subkey did not exist under PNP501 and regedit would not let me add it for some reason.

So i rebooted, went into bios and enabled the GPS. When windows loaded i got the found new hardware notice for the gps and got the bouncing mouse. I then Rebooted, disabled the GPS and went into regedit and the \1\ subkey now existed and i was able to merge the gps .reg file which solved the bouncing mouse. Still no extra com port in DM.

Ultimately I think it was some kind of issue with my initial order of installation when i first setup the tablet. As I've learned the order of installing stuff on these is actually important if you want things to work. The GPS was an afterthought that came after I had already setup the tablet, after installation is when it appeared.

What is really puzzling is that it didn't dissapear until i did a proper format and re-install of windows, I did several quick formats and re-installs and every time it was there on first boot.

It also appears I'm not the only one to have this happen:
http://forum.notebookreview.com/pan...ve-unknown-device-device-manager-cf-19-a.html

 

Rep for the feed-back. We need more of that.

Thanks,

Jeff