Urgent Help, Please...

[3rd gen noob]

TClite installed a new ASUS A7N8X-D motherboard today

he can't boot into windows, gets a blue screen error and loops back into restart and then blue screen...

tried repairing boot sector on hdd, didn't help any
chkdsk reported "did not scan", when forced to scan found "one or more errors"

are there any quick fixes to this problem, or any ways to boot into windows without a format/reinstall...we can actually see the folder lists, just can't do anything.

windows xp pro corp

p.s. would using the 'wrong' windows disc (i.e. not the one used to install windows on the system) be causing the problem

p.p.s is it possible to fit a new motherboard without reinstalling windows xp?


thanks in advance for any rpelies/advice...

[Somebody1234]

When replacing the motherboard it's always recommended to do a clean install of your OS.

What board did you have before? Did it have an Nvidia chipset?

My thinking is that the old board probably had a Via chipset and had the drivers for that. An idea would be to reinstall the old board and uninstall those drivers. If you get the system up and running with the old board why don't you recover any data you want to keep?

I still think that the best thing to do is format and reinstall.

[zapjb]

I concur with Somebody1234. Any major new hardware like a mb is going to need a new install of Windows.

[3rd gen noob]

old board was an asus a7v333 via chipset, cant use it as its fried, the new board is a replacement, are there any other alternatives to reinstalling windows? also on boot after posting the next screen says failed to detect my hdd, but its recognises it in bios......

TClite btw

[Somebody1234]

Hey TClite, :)

If you need to recover some data from the drive... Either repartition the drive with Partition Magic and reinstall the OS to the new partiton and recover the data or install the OS to a new drive and then reconnect the original drive a slave. You can then recover the lost data that way. Otherwise you will have to format and reinstall and loose the data.

I don't think it will be easy to get your current setup to work. To change the chipset requires that all the associated drivers be changed before it will work.

[Somebody1234]

If you're going to reinstall I suggest that you put at least 2 partitions. One for your 'system' (c:\), one for your 'data' (d:\), which would include e-mail, documents, music, images, downloads, shared files etc. Many programs let you define the default destination directory which you would point to that 'data' partition.

That way when you need to reinstall the system, only the system gets wiped. To reinstall an OS is not a big deal, it only takes ~45 minutes. If you do it that way you get to keep all your own files. As a bonus it's easier to do backups.

[_John_Lennon_]

Originally posted by Somebody1234@17 September 2003 - 21:28
If you're going to reinstall I suggest that you put at least 2 partitions. One for your 'system' (c:\), one for your 'data' (d:\), which would include e-mail, documents, music, images, downloads, shared files etc. Many programs let you define the default destination directory which you would point to that 'data' partition.

That way when you need to reinstall the system, only the system gets wiped. To reinstall an OS is not a big deal, it only takes ~45 minutes. If you do it that way you get to keep all your own files. As a bonus it's easier to do backups.
His past motherboard was fried, it might have effected the HD too.


How did he lose his Mobo noob?

[adamp2p]

What's up noob, ol pal?

Is this your computer? Who is TClite?

B)

[3rd gen noob]

hi, sorry for the delay in reply folks...

tc has since formatted his comp, there wasn't anything wrong with the hdd, we put it in mine as slave to check...

anyway, he formatted and reinstalled xp, problem solved now

thanks for the help

:beerchug:

@adam, i'm not too bad, how's you?
TClite is a board member here and a very good friend of mine

[_John_Lennon_]

meh, guess it was just a bad XP install.

*shrugs.

happens.

[Somebody1234]

It wasn't a bad install. He replaced the motherboard which had a different chipset than the original. When that is the case, it's normal that you would need to reinstall the OS.

[3rd gen noob]

Originally posted by _John_Lennon_@19 September 2003 - 20:42
meh, guess it was just a bad XP install.

*shrugs.

happens.
it couldn't have been a bad install cos he had the same install for a number of months...i think somebody1234 is right though

[lynx]

Actually, there are often ways of getting round this problem, as long as old and new boards have fully compliant acpi support, but by the time I saw the thread you said he had reformatted his pc, so there's not much point in going through it.

[_John_Lennon_]

Originally posted by 3rd gen noob+19 September 2003 - 16:53--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (3rd gen noob @ 19 September 2003 - 16:53)</td></tr><tr><td id='QUOTE'> <!--QuoteBegin-_John_Lennon_@19 September 2003 - 20:42
meh, guess it was just a bad XP install.

*shrugs.

happens.
it couldn&#39;t have been a bad install cos he had the same install for a number of months...i think somebody1234 is right though [/b][/quote]
OH&#33;

Ahh, i see now, it wasnt a fresh install.









Well then, no worries, I made that same assumtpion about not having to reinstall windows, when I upgrade my comp for the first time. Bought a new motherboard, new processor, new Ram, and yup, didnt work for same reason.