PVR-500 locks computer on reboot

[PEverett]

I have an XP Pro workstation platform with very ample resources. However, I am a newb to this PVR world.

Running GB-PVR with a PVR 150 (non-MCE) I have been able to get things working fine.

I also have a PVR 500MCE.

So, taking things one step at a time, I have removed the PVR 150, run the "hardware clear" program from Hauppauge, and then installed the PVR 500MCE.

XP locates the new hardware and installs it. Device Manager shows two tuner cards, no problems. I loaded the Hauppauge non-MCE software so as to get all of the software encoders (which I think I saw as a tip here), WinTV etc.

Now, with everything loaded, I can watch both WinTV and GB-PVR -- no known problems. By reading threads here, I think I know how to setup GB-PVR for two tuners but at this early stage I just want to test watching two programs at one time to verify that both tuner cards are functioning as would be expected.

(I have not confirmed recording capabilities, yet.)

However, as soon as I reboot the computer, it locks up on the Windows reloading screen. The keyboard is dead and I have to power-down. :mad:

When I take out the card, the system reboots normally. If I then remove the drivers, and put the card back in, the system reboots.

This is completely repeatable for me and I have tried 2.0.30.23123, 2.0.30.23074 and 2.0.18.22316 drivers - all present the same result of working exactly as I would expect when first loaded, but locking up as soon as I reboot.

Any tips on what I might check out for the cause? :confused:

[Chris.Day]

Try adding /PCILOCK to your boot.ini file

[PEverett]

Sincere thanks for the tip Chris, but it was not sucessful (and it seems to have somehow lead to a loss of COM3 and COM4 when I made that change. Weird - maybe due to having a PCI fax/modem that was on COM3.)

So, now I have two problems to fix. But hey, as a newb this sort of thing seems to be the way of computing. :confused:

[Chris.Day]

Just remove the /PCILOCK option again. I don't know why this would cause you to loose your serial ports, but it sounds like you've probably got some kind of resource conflict.