Hi Matt!
There is no problem with your boot.ini file.
The problem is the Windows Registry.
The boot device drivers in the registry point on one driver and the new Server 
use a newer or another driver to boot up your disk controller card.

When you restore your files/images to a new hardware you need to be sure that 
the drivers who installed on the orginal machine is the same as new new one. 

There is only one way to sold your problem right now.
That is to install the new drivers on the orginal machine and then backit up 
and restore it to the new machine.

But we have a group at Cristie Data Products who looking to sold this kind of 
problem when you clone system or run a Disaster Recovery on new hardware.

Good luck
Christian 

============================================================
Från: "Adams, Matt (US - Hermitage)" <maadams AT DELOITTE DOT COM>
Datum: 2003/09/03 Wed PM 04:52:42 CEST
Till: ADSM-L AT VM.MARIST DOT EDU
Ämne: Suggestions for W2K recovery

All,

I am looking for some suggestions on the best way to handle a W2K recovery
to different hardware.  It is not so much the different hardware I am
battling, it is boot.ini.  I am trying to find out at what point boot.ini
gets put into place from the restored server.

The current (old) server has the Compaq boot partition therefore the
boot.ini looks like this:

[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Server"
/fastdetect
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows 2000 Recovery Console" /cmdcons

The new server will not have that seperate Compaq/HP boot partition and
should look like this:

[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Server"
/fastdetect

I checked boot.ini both before and after the C: and System State restores.
It remained the same, so I am assuming that at some point during the boot is
when the old boot.ini gets put into place and causes the new server to come
up with a BSOD for "Inaccessable Boot Device"

Thoughts or suggestions?

Regards,

Matt

 


This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law.  If
you are not the intended recipient, you should delete this message.  Any
disclosure, copying, or distribution of this message, or the taking of any
action based on it, is strictly prohibited.
============================================================