>>would not boot. unless the hardware and resource config were virtually indentical...
I've successfully booted NT system disks in new machines where the
only real item in common was the fact that the disks were
IDE. Different processor, different memory, different mobo,
different vid card, different sound card, different scsi
card, different network card, different position on the IDE
controllers, what else is there?
This is, in fact, the way I resuscitated my primary domain
controller, by physically removing the NT server system
disk from the dead system and inserting it (in a different
IDE controller position, incidentally) on one of my
new Celeron systems. Booted right up. Naturally I had
a lot of reconfiguration to do and network domain games
to play and a headache from the VGA driver. I did
NOT select the VGA emergency boot, btw - the kernel
apparently recognized the config change and loaded the
VGA driver all by itself. Booted first time, though.
That's only one example. I've done it
several times in the past few months
in various contexts.
I have noticed that since service pack 3 NT has gotten
pretty darn smart about booting in an entirely different
environment. With SP 2 and earlier, damn thing would
give me a BSOD if I added a hard drive (on account
of my damfool assignment of G: as the NT system partition,
I've always believed).
Spots |
