Don't worry about your \Documents and Settings folder. Win2k will not overwrite
the directories in here. It will make a new directory like ADMINISTRATOR.NAME
and NAME is the computer name you give during setup. Back it up anyway, just
in case (onto a different drive ideally).
I don't think it will harm anything in \Program Files but back if up first if
you are paranoid.
Before we start hacking up your old registry, first make a copy of it.
I recommend that you copy the entire C:\WINNT\system32\config folder
to somewhere really safe. If anything goes wrong, you will have backups
of everything vital and can restore your old system back to normal.
If the two motherboards have different IDE chipsets then you should uninstall any
bus mastering drivers and install the Standard MS IDE drivers.
Switching from an Intel IDE chipset to VIA will guarantee you a blue screen on bootup.
If you will be switching video cards, uninstall your video drivers and switch
back to VGA . I'd recommend you do not switch any hardware until we're done and
the new motherboard is booting.
Ok so with all that done, set up the system onto a new motherboard.
Boot off a Win2k cd and install it into \WINNT2
Be really careful with the setup program and DO NOT delete your existing Win2k
folder, reformat, convert FAT to NTFS or any other stupid thing you can do here.
You want to "Leave the file system intact".
When it says "Press F6 to install drivers", do it. Put the ATA133 driver floppy
in and select the Win2k Fasttrack driver.
[Last I checked, XP users should also use the 2k driver and not the XP driver,
unless you like blue screens. XP users can install the XP driver after the system
is installed and running perfectly.]
Let the installation finish and boot to the new clean Win2k install.
While it boots, notice if you do not get a boot menu (I'm pretty sure you do...)
then use the system control panel, ADVANCED tab, Start up and Recovery button.
Checkmark the "Display list of operating systems"
Ensure that you have two "Microsoft Windows 2000 Professional" entries in the list.
If you like, edit c:\boot.ini and change the names so you can tell them apart.
Leave the default choice the top one, the new installation in \WINNT2.
Might be wise to ensure the drive is working okay before we bother with the rest.
Maybe schedule a chkdsk on restart and let it run.
Ok now to get down to the real work.
Search the \WINNT folder for "fasttrak" and move whatever you find to some other
folder and get them out of the way.
Then repeat the search in the \WINNT2 folder and copy those files
to the same location in the \WINNT folder.
I had: fasttrak.sys .inf .cat and .pnf
Open up regedit
Track down ALL instances of Fasttrack driver using the find option.
search for "fasttrak"
Search ONLY within [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet]
Export any of the found branches to reg files. Use your head when exporting
branches, make sure you get everything you need. Sometimes you have to
export more than you need. Just edit the file in notepad and remove
anything that does not apply.
There will be two other items to search for and export.
1.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Fasttrak\Enum]
Has a value like this:
"0"="PCI\\VEN_105A&DEV_5275&SUBSYS_807E1043&REV_01\\3&61aaa01&0&30"
Redo the search/export using VEN_105A&DEV_5275
2.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_105a&dev_5275]
Has a value like this:
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
Redo the search/export using {4D36E97B-E325-11CE-BFC1-08002BE10318}
Of course the fasttrak.inf file will have most of the information you need
on where stuff is hiding in the registry.
Now take all these reg files and append them into one big file. As I said before,
you are really just going to have to use your head to know what to export and how much to trim.
I have an example registry file here. It is the actual file I used on my system.
Don't simply use my file to import into your system. It won't work.
With that in mind, if anyone dares to try this and it works, send me
a copy of this file. I'd like to see what is different.
Attach your old registry:
Now the next step is to attach your old registry so we can modify it. Start->Run "regedt32" Pick the HKEY_LOCAL_MACHINE window and select the top of the tree with the same name. Then on the Registry Menu, select "Load Hive"
navigate to C:\WINNT\system32\config and select "system" (no extension)
When prompted for a key name, enter "ZYZZY"
Now before we can move on, we need to know which ControlSet to edit.
Just look at the ZYZZY\select\current value as shown in the picture.
It indicates controlset001 in the picture, but it certainly could be
controlset002 or 003 on your system.
I recommend that you now repeat the search we did above, but this time use the
ZYZZY branch and check that you have similar registry entries for your old raid controller.
I deleted most of these old registry entries before proceeding, but you probably don't need to.
Use your judgement. Maybe you will find an important registry key you missed earlier?
Now open up a copy of the reg file we created earlier (yes make a copy).
Replace all occurrences of
\SYSTEM\CurrentControlSet\
with
\ZYZZY\ControlSet001\ (or whichever controlset is active)
Save the file and then run it to merge it's contents with your system.
That's it for changes.
Now unload the ZYZZY hive we loaded earlier.
I believe you have to select the ZYZZY branch
specifically in order to use the Unload menu item.
Now check that you have performed all the necessary changes.
Reboot and at the boot menu, select your old Win2k installation
(should be second from the top).
With any luck your system will now boot up and not blue screen.
Email me and let me know it worked.
Use the system for a while and when you are comfortable,
delete the \WINNT2 folder and the
C:\Documents and Settings\whatever.NAME folders that the
new \WINNT2 install was using.
Given that the audience for this page will be extremely small, I will try to answer any
email containing legitimate questions. Please let me know about any errors or omissions.
Later on I had some more thrills with this stripe set:
www.Seanster.com/raid/raid_stripe_fun.html
