Boot Failure With New Motherboard

I changed a multiprocessor motherboard with onboard scsi for a single processor board using a pci scsi card and now get bsod 'BOOT device inaccessible".
Running win 2k with SP4.
Tried repair install with adaptec drivers but no luck.
Installed a new system in separate folder and it works but I would still like to repair or at least understand what the problem with the old system is.
Is it the change from onboard scsi or is it the multiprocessor/uniprocessor ?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AlexanderREnterprise Web DeveloperCommented:
Unfortunatly you cannot just take a working OS from one motherboard to the next.  OS checks serial number of the motherboard in some cases (thats what i heard), or does whatever other kind of verification for major hardware changes, and if the difference between hardware conf. of last boot is too different of current boot, it locks itself.  The best you can do is to reinstall the OS together with all your programs and transfer your personal data to the new system.
A Windows install includes device scanning, and the "list" is used by the Windows install to build the registry.

When you changed the hardware the chipset, controllers, and buses are now different that what the registry
"wrote in stone" during the initial install of Windows.

When changing hardware you have to boot to the O/S CD Recovery Console and run the commands
chkdsk /r

When changing hardware you [sometimes] have to boot to the O/S CD and do an overtop install. Your essentially
running the device scan and registry build process of the Windows install to "re-gather" the new chip/device information
from the new hardware.

The reason your "other folder install" worked was because the device scan/registry build was performed during the install.
Is your boot drive on the same PCI device as before?  Windows has  tendency to remember this it really makes it next to impossile to to a motherboard swap.

I have never had a problem doing a MB swap under Linux and as long as my boot drive was the same device number as before I have only a few problems doing a MB swap under Windows.
Introduction to R

R is considered the predominant language for data scientist and statisticians. Learn how to use R for your own data science projects.

To the best of my knowledge you do not have to reinstall OS, boot from cd and do a repair install, this should fix your plroblem.
I've seen that error too many times!

Basically, Windows is expecting to find your boot device based upon:
1) the boot.ini file,
2) the drivers that were loaded for the onboard scsi

Windows "remembers" how to access your SCSI boot device.  When your SCSI drivers change, Windows can no longer find your boot device.  Specifically, if your original MB hadn't had onboard SCSI, the MB swap wouldn't have caused your problem.  It happened because you changed SCSI drivers, not specifically because you changed MBs.  In any case, you will need to repair your OS by first loading the drivers for your new SCSI device.  

Often you only have to:
1) Boot from your Windows CD.
2) Let it scan for your hardware, it will find your boot device.
3) Then exit setup.
4) take out the CD, and reboot.

The last time I had to deal with this, when the system booted, it came right up.  Unfortunately, I've also had to do the complete repair, in the past, also.

Good Luck!

multiprocessor to single processor requires complete reinstall.  too many files to replace core of system, Xp dont work well, windows 2000 cant handle it.  will have to do new install.
Windows is always good for a good laugh!

Now, when it scans for all the new hardware, it will also probably reboot for each device it finds!

What does your scsi have to do with the boot device?

What does your boot.ini say?

HAL for multiprocessors was supposed to be fixed as of NT 3.51, which precedes Win2K.  I wouldn't say it was the dual processors, more than likely, the radical hardware change sent Windows into Altzheimer's memory.

This used to happen when someone would try to move a hard drive with an OS on it, from Win95 and Win98, etc., to another computer.  Not knowing the hardware, and "thinking" [as if a computer could ever really do that!] that it already "knew" the hardware, these OS's would get confused, have an anxiety attack, and then a panic attack, instead of scanning for hardware changes and adjusting.

Also, you didn't say if it was the Server or the client your running.  If it's the server, you definitely have to completely reinstall it on a new system, that is, when you change the motherboard.  A client shouldn't have that sort of problem, well, at least not after a number of reboots.

Server or client?
BobWaughAuthor Commented:
This is a client machine
I have tried a repair install and pressed F6 to load adaptec drivers which does appear to work.
When booting it gets to the windows logo and halfway through the bargraph on the bottom of the display before 'falling over'.
That is why I was wondering if the problem is not one of not finding the scsi drive but something else.
Building on ACSIPaul's post, there could be a chance you get the SCSI driver issue fixed this way:

# rename the file ntbootdd.sys to ntbootdd.sys.old (in c:\)

# find the scsi driver file for your new adapter and rename it to ntbootdd.sys and copy it into the c:\ directory.

Not sure it will work, but at least worth a try. I do believe the change of scsi controllers caused your problems - or do they have the same controller chip on them? As well it might be interesting to post the content of your boot.ini file to us.

BobWaughAuthor Commented:
Cannot find any file with the name ntbootdd.sys.
Here is boot.ini:

[boot loader]
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WIN_BOB="Microsoft Windows 2000 Professional" /fastdetect

The system in WIN_BOB is the new, working installation and WINNT the original now non-working one.
This is Windows 2000 professional with SP4

If I look at the system information with ERD commander the the original system says the Kernel is Multiprocessor but with one CPU
The working system states Uniprocessor

I don't have all of the information to hand but ERD commander shows that the CPU for both installations is not the same. The same speed but other diferences
BobWaughAuthor Commented:
I forgot to mention that the original onboard scsi was also adaptec
You can rarely change a motherboard to a completely different type without reinstalling, not to mention adding SCSI etc.

Occassionaly it works but imho it just isn't worth trying.

Major hardware change=reinstall. It just isn't worth fiddling for ages trying to get around this,


means basically it's the C Drive, an IDE device.

so it wasn't the SCSI that was at fault, rather, you really confused XP by transplanting its heart without anesthesia, basically.  Naturally, you got cardiac arrest, if you can understand that.

So now, you have an alternate Operating System, which is a very good idea.

Do you have NT ResKit or some form of windiff?  This will tell you exactly what files are different on both partitions, and if they exist and one which partitions they exist.

Windiff is a handy tool for just such circumstances, but don't simply try to copy files that are different or do not exist.  The new OS has the files needed because it has redetected and rescanned all of your hardware upon installation.  The old OS has the old motherboard information.

There is also a tool called NTHQ [as far as I remember] that is helpful in your situation.  Try to find it.

Otherwise, you're just going to have to grunt it out, trying to get the stuff from the old OS to the new OS, and you really should add another hard drive for this, in case OS #2 goes kaput.

Anyway, if you can get OS #2 to work as OS #1 was, the basic idea is then to reverse the order and reinstall OS #1, however, be aware that XP is aware of partitions and often you cannot then simply delete some partition, as in formatting it and trying to reinstall because the bootsector may move to the second partition [this also happens when you install, reinstall, or add a new installation on another partition or disk].

First document all of the files, folders, etc., that you want to keep for the fix, and put them somewhere where neither OS can delete or change them, such as another drive.  Then you begin the slow process of restoring the entire system.

And plan this thing out.  A 250 gig partition is a fool's paradise.  Try to get partitions in the 50 to 80 gig area for a 160 to 250 gig drive.  The second drive is either a tool you keep around for such annoyances, or, standard install to preserve customer installations from customer damage.  It's just a good practice and makes happier customers, even if they're employees at your company; it also cuts your overhead seriously when problems occur because you can fairly well restore anyone system really quickly and they hardly ever lose anything.

Dell and Microsoft are currently trying to standardize the dual OS technique, while keeping one hidden from customers, so that a restore is merely a matter of selecting the hidden partition to fix a bad system.  You might consider how this works.

Most companies have a clone around for initial installs.  That is, a harddrive that they simply copy, with all software, and voila, install in as short a time as it takes to copy one disk image to another disk.  That is followed by a network install of the OS, or a quick CD install.  The one biggie problem is the changing of hardware, which is difficult for Windows to work around.

You're not in such bad shape though, once you've got at least one OS up and running, you can use the computer itself to fix the problem.  So, it's decision time: are there files you need on OS #1?  If so, you need to plan how you're going to get them, keep them, and restore OS #1 as the main OS.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BobWaughAuthor Commented:
Thank you all for your help.
I agree with you GinEric about partitioning large hard drives and hope people take note.
The route I finally took was:

Booted the system with the old motherboard (it was not dead but certainly not well) then added the new adaptec card and its drivers.
I then connected the boot hard drive to the new card. I rebooted and disabled the onboard scsi in the bios and the system found its own way home.
I then took the hard drive and scso card, inserted them in the computer with the new motherboard, switched on and sat back to watch it loads all of the new drivers it needed and ended up the a working system with all programs, data intact. Again thank you very much you each gave me pointers to work to
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Operating Systems

From novice to tech pro — start learning today.