XFX Geforce 2 MX 400: Endless reboot

[Aqualung]

I chose to put a TV on the cabinet I'm working on, and bought this video card from XFX with Geforce chipset and TV out - both RCA and S-Video.

I've installed the video card without any problem, and got the TV out to work (only in Windows, but it's no problem to me, I'm going to use MAME32).

But when I tried to load a game on MAME, the system just rebooted after the "OK" screen. No matter what I do and configure, it keeps rebooting when I try to load a ROM.

I'm using Windows XP. Could this be the problem?

[SNAAAKE]

Similer happend to me before with XP...very strange so I use 98 but you can try to clear the CMOS setting or see if there is somethin there....My motherboard had problem with XP so I just installed a brand new copy of 98 and works perfect.You can also try to use compatibility mode in xp when you load mame32....I am not quite sure and xp was useless in my cabinet anyways.

Luck luck and the problem seems very anoying I guess.

[Aqualung]

I tried to reset CMOS and use compatibility mode with MAME but both alternatives didn't work.   I even tried to run other emulators like WinKawaks and Gens but they rebooted the machine too. But PC games work OK, like Pro Pinball: Fantastic Journey, Prince Of Persia 3D and Interstate '76 Nitroriders.

Then I put back my Voodoo 3 old card and everything worked perfectly. Very strange.

As I can't format my HD (can't backup because I don't haver a CD-R burner available), I'm gonna buy a new HD today that will be used for the cabinet and install an old WinME copy I have here. If it doesn't work, I believe I'll give up and return the video card.

[SNAAAKE]

I still think XP is the problem here.Anyways.....good luck

[Aqualung]

Thanks a lot, Snaaaaaaaaaaa(...)aake!  

The problem was Windows XP. I've installed another HD with Windows ME and MAME worked with the GeForce card.

I only got some problems with fullscreen on my TV, image looked like losing some frames probably because of the NTSC/PAL frame limits (24/30), but unhooking the monitor and let Windows boot only with TV as the main monitor and no second monitor solved this problem.

Thanks again.

[SNAAAKE]

You are welcome man

See I kindy already knew what happend here.