Hangs durning booting w/ additional serial port card

[videobruce]

I wasn't sure where to put this.

The MB (Foxconn N570SM2AA0 already has a serial port built in. I was having issues with the XP driver (nothing else available), so I purchased a PCIe serial port card and installed it. I did disable the on board port first.

I have two bootable drives and this happens with the orginal drive and the 2nd drive that I reloaded the O/S after I added the card. The O/S hangs 45 seconds, then continues to boot. I'm sure it's this serial card. Again this is with or w/o the driver installed running XP Pro w/sp2

The other possible related issue is com ports 1 & 2 are not available with the on board port disabled. Where in the registry can I regain these port numbers?

Hope this made sense.

 

[BlueAcolyte]

Hmm, I know this is weird, but have you checked your IRQs and/or plug n' play settings?

 

[Peter]

Let's skip the "IRQ conflict" myth this time. This isn't an ISA card, it's PCI, right?

Windows hanging for a long time at boot much more often is storage or ethernet related. Try disabling unused IDE and SATA channels, make sure that no Ethernet channels are set to DHCP with no cable connected.

As for the COM port names: These are entirely arbitrary in XP. You can choose your own from Device Manager, properties of the COM port, Advanced tab.

 

[videobruce]

PCIe.
I have two ethernet channels. One has been disabled. It is the com port NUMBER that I was concerned about. Ports 1 & 2 aren't available.

 

[BlueAcolyte]

I guess Windows still sees the COM port? Could you enable the onboard port and assign those ports difference numbers?

 

[tcsenter]

What "issues" were you having with the onboard port? Did this longer boot time appear after the serial port card was installed? Do you have any device connected to the serial port card?

What is the make and model of the serial port card you purchased? There may be a newer driver available for the controller than shipped on the driver CD. Currently I find two implementations for PCI Express serial port cards; NetMOS and Oxford chips.

 

[videobruce]

I had to disable and then re-enable the port to get it to work in Device Manager. Yes, the longer boot time appeared after the new card was installed. Yes, there were devices connected, but now there aren't and there is no change, it still hangs.
It is a Moschip MCS9901 chipset card (no name). I have the latest driver, but again it hung with no driver installed.

 

[videobruce]

Ok, I uninstalled the drivers, removed the card then rebooted. No change.
I disabled the 2nd SATA channels and the ethernet and firewire ports and still no change.

It still hangs on the "Windows is starting up" screen for 45 seconds.

Any ideas?

 

[bsobel]

In your boot.ini does the OS selected have /FASTDETECT enabled?

 

[videobruce]

Yes.

 

[bsobel]

It sounds to me like XP is finding the port and still trying to enumerate devices on it. Try the regpatch here http://www.stevematt.f9.co.uk/FixSerial/fixserial.htm

 

[bsobel]

You might also try adding /NOSERIALMICE to your boot.ini

 

[tcsenter]

Originally posted by: videobruce
Any ideas?

Exchange for PCI version:

SYBA PCI card

The controller chip used on this board is the NetMOS/MOSCHIP 9835, the latest drivers for which can be downloaded from MOSCHIP:

MCS9835 drivers

 

[videobruce]

Thanks for the links (which is where I got the latest drivers), but I do have another PCI version, but I didn't bother to try it since removing the card didn't have any effect, so why would another card make any difference?

It surely doesn't look as it was the serial card.

 

[bsobel]

It surely doesn't look as it was the serial card.

Then why the heck did you say "I'm sure it's this serial card". We've been trying to help you figure this out, if you already removed that as a possible cause, you kinda needed to tell us...

 

[videobruce]

Because three days ago it appeared to be the cause.
That was three days ago. Things changed. What, you never thought it was one thing and then through testing discovered it was something else? Come on now.

 

[bsobel]

Originally posted by: videobruce
Because three days ago it appeared to be the cause.
That was three days ago. Things changed. What, you never thought it was one thing and then through testing discovered it was something else? Come on now.

You asked *US* for help and you didn't update *US* when you determined that. Your on your own, I'll no longer help you in any thread.

 

[videobruce]

The "update" was 9 posts ago on the 21st.

Ok, I uninstalled the drivers, removed the card then rebooted. No change. I disabled the 2nd SATA channels and the ethernet and firewire ports and still no change.