motherboard woes

[sammykun]

I posted this in the motherboard section, but I thought I'd try here as well:

well, I'm in need of some help. My current motherboard, an Asus A7V333, had a shorted-out usb2.0 connection pin on the motherboard itself (fried, actually). So, I decided last night to replace it with another board temporarily whilst I proceed to RMA the stupid thing. I had a SOYO Dragon K7V Dragon Plus lying around unused, so I decided to replace it with that one.

Everything's plugged in fine now, but the computer won't boot into Windows. When I tried booting into safe mode, the sequence freezes when mup.sys tries to load up. I found a few articles online about it; it seems that it's a usb2.0 driver issue...however, I haven't found a workaround to have it stop from loading.

Anyone in here did something similar, as far as motherboard replacement goes? Any idea what I could have done wrong? Do I need to reformat? I'm hoping not, since I don't plan to stick with this SOYO board forever...maybe Asus will send something better

Any help would be most appreciated...here's hoping I can get back to my work

 

[Atalia]

You did not reformat the drive so it will not work on a new mobo. asus uses VIA busmaster IDE controller does the new board use the same,
is the assignment of IO and IRQ's the same does the modem default to IRQ3 instead of IRQ1, to many variables to attempt putting that drive in, with out formatting that is, get a smaller one to use temp. or wait for Mobo.

 

[GlassGhost]

What atalia says is about 75% correct

I'm no an expert on the win xp boot loading process, but I know that win xp will be able to boot up off a hard disk that was intalled on a different MB than it is currently connected to, like in your case. Win xp just realizes at some point (and this is the problem, I'm not sure at what point!) that the MB has benn changed and begins to install new drivers for all the new MB resources.

The problem is win xp may load the usb driver (for whatever reason, who knows) before realizing that the MB is different than what it expects.

So... My question is if this new temp MB (soyo) is similar to the asus one that's fried (i.e. same chipset as the asus etc.), that could explain why win xp may be a little confused.

Other than that, I can't think of another solution until you get the replacement. Sorry

 

[Willoughbyva]

You can try booting off your xp cd and go into the recovery console and run the fixboot command. I'm not sure if it will work for you, but you can try it.

 

[GlassGhost]

Originally posted by: Willoughbyva
You can try booting off your xp cd and go into the recovery console and run the fixboot command. I'm not sure if it will work for you, but you can try it.

This won't work. The fixboot command only restores the master boot record, which is fine in his/her case.

 

[sammykun]

thanks for the help, everyone

I'd hate to go through a reformat just for a temp board...heck, I'm hoping there's a large capacity drive on sale tomorrow just so I can justify for myself in getting one to set up (heheh).

Anyhoos, I know the chipsets on both are different. I believe the ASUS A7V333 is running the KT333 chipset and the SOYO is running the KT266a chipset. Since the error is on loading the USB2.0 drivers, I was thinking about picking up a PCI USB2.0 expansion. Not too sure if this is a viable solution, though; seems to elementary to be a reasonable answer.

/me is simple-minded...wheeee

 

[redbeard1]

In general the win NT os's hate changing chipset's without a reinstall. You can reload over the top of what you have, and with no errors, you'd have the same settings and such. You just need to be very careful in the reload when your are going through the menu choices, so you don't wipe it by doing the 'fresh' install.