The motherboard in the PC I was using as my domain controller died. I
want the domain controller back up and running ASAP so I thought I'd
just pull the HDisk out and put it in another PC and boot.
Unfortunately I get a BSOD "inaccessible boot device" error when win2k
boots...

I tried running recover but doesn't fix it!

Is there anyway I can sort this?

The reason that it isnt booting up is because the IDE controller on
the Hard Drive is looking for the one that was previously installed. 
Youre going to need to put the HD in a computer with the same mobo and
change the IDE controller in Device Manager to the default MS one.

Go to controller properties -> update driver -> dont search, choose
driver to install -> select "Standard Dual Channel PCI IDE
Controller", then shut down.  Then, move the hard disk to the new PC,
it will detect the IDE controller.

tom20-ga; Thanks for the suggestion but this isn't possible. I don't
have a pc with the same mobo.

actually, the "second" recover does (should?) fix this...

Not the first one that comes up, but the one that installs and finds
an existing WINNT directory. You'll need to be prepared to reinstall
any service packs.

http://support.microsoft.com/default.aspx?scid=kb;en-us;318752

This might be worth burning a tech support incident with Microsoft as
they will walk you through this and help you not to lose too much.

I've done it before, but I'm skittish to recommend something to
someone and not be able to back up the results.

Already tried that, it detected the install, showed it checking some
files and stuff, rebooted and same STOP error :(

The link you provided was to info on the recovery console. Did you
mean to post that? If so what should I be looking to do from the
recovery console to fix this problem?

Thanks In Advance!

if you can get to a DOS prompt, you may be able to change the (hidden)
c:\boot.ini to reference a different location for NT to boot.

If all else fails, install a second version (don't DELETE the
partition) in c:\winnt.2 or some such. At least you'll have a bootable
hard drive. That *does* overwrite stuff (IE, common files) in "program
files" so be prepared. Still, I'm hesitant to suggest too much more
because of the potential to lose data if you're not careful. Once
again, I'm strongly suggesting that, if recovery of functionality is
more valuable to you than $2, you really should contact Microsoft or a
local technical support guru for assistance.

Can you try this, to update the drivers for your IDE controller?

Q216406 Specifying Third-Party Disk Controller Driver During Setup 

http://support.microsoft.com/support/kb/articles/q216/4/06.asp

Specifying a third-party controller driver during Setup should be
necessary only if Windows 2000 does not contain a driver for your SCSI
adapter, CD-ROM drive, or special disk controller, or if Setup does
not detect your hardware correctly.  To select a third-party
controller during Setup:

1)      Obtain the correct driver file from the motherboard or
controller card maker.  Copy file to a floppy disk.

2)      Change motherboards.

3)      Place Windows2000 Setup CD in the CDROM-Drive, reboot, and
boot from the CDROM.

4)      Early during the first phase of Setup, at the "Setup is
inspecting your computer's hardware configuration" screen, press the
F6 key ASAP; (F6 quickly to prevent drive controller detection).  Then
press ?S? to specify an additional device.

Alternate: During the first phase of Setup, press F8 to troubleshoot,
and choose boot up in Safe Mode.  Press F6, then press ?S? to specify
an additional device.

Note:You do not need to install the ATA-100 driver during the WIN2K
install process on a non-RAID IDE motherboard; WIN2K will simply treat
it as an ATA-66 drive. Once Setup is complete,  install SP2, and WIN2K
will see the drive as ATA-100.  If the drive is on a SCSI or RAID
controller, you must use the 3rd party mass-storage device <F6>
option, or WIN2K doesn't see the drive.

5)      Win2000 setup will now ask for a TXTSETUP.OEM disk.  Place the
TXTSETUP.OEM disk in the floppy drive, and press Enter to continue.

6)       Windows installs the correct driver.

7)       To continue with Setup, press Enter.

If that first solution does not work, this, should:

1)      Open the Recovery Console and type LISTSVC.  A list of drivers
loaded on startup will be displayed.

2)      Locate the IDE drivers and type DISABLE name.ext (where
name.ext is the driver name and extension).

3)      Once the IDE drivers are disabled, exit and reboot.  On
reboot, Win2k will load the standard default IDE driver and should
startup.

crythias-ga; I don't want to reinstall e.t.c, I want to keep the
configs, i.e. the users/groups/romaing profiles, shares e.t.c...

As for the other suggestions...

I've tried disabling practically all drivers/services to no avail...
Additionally when I tried the recovery thingy it reset all the
"listsvc" drivers/services by the look of it so this shouldn't be
what's causing the problem?

Maybe there isn't going to be a way round it...

lticket - im positive that is the problem.  it happened to me last
year and it took me forever to figure it out.

Tom

Any suggestions as to what I should look out for in terms of IDE
drivers? I went through and practically disabled everything and still
didn't fix it. Additionally, as I mentioned earlier I did a "recovery"
which looks like it's restored the drivers e.t.c to the default but
still no joy!?