Hangs durning booting w/ additional serial port card

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.

 

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

 

Normally I would say that you have introduced an unintentional resource conflict with you new serial card.
By this I mean Windows is having trouble allocating IRQ or DMA or just mapped memory to the card because something else is already using that resource.

In Device Manager you will find alternative settings for these for the card.
Make sure the BIOS has released these for the slot concerned.

However you mentioned that you installed the card because of similar (?) issues with the existing port.

There is a possibility that the mapped memory is (becoming) duff so you will need to find a way to check this. Software memory exercisers (memtest etc) are not very good at pointing to this kind of fault, substitution or swapping modules around is better. It may simply go away by reseating the modules.

 

With the card removed and everything disabled except for SATA1, if any of the above was a issue, why would it be a issue now?

 

Did you test your memory?

 

No. Why would that have anything to do with this? :confused

 

Funny I distinctly remember explaining this in post#3.

 

Sorry, I overlooked that (as most do by not reading the whole response). I did two different tests on the memory, both showed ok.
Why would reseating the memory have anything to do with "memory mapping"?
Are you saying sections of the memory are not available for use?