Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Alright, I have an engineer who has hooked his palm pilot up to his NT platformed pc. Well apparently the palm software modified the boot string in a way that renders NT useless.
Error message read Inaccessible_Boot_Device, and the long famous set of numbers mostly 0'sSpecs include: WinNT, 128 RAM SCSI 6gigHD, PII266.

DO you have Recent ERD for your NT wrkst? Did you try loading from last known good configuration when booting? You will more than likely need to use your ERD's to repair your NT box. SO use your boot disks and ERD's to fix your machine.
I hope this helps
Keep posting
JJ

If your Windows NT system partition is on FAT and not NTFS, boot with a system disk and edit the boot.ini file. It should look somewhat like the following:
* As always, make a backup of the file before modifying it.
----------------------------
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(2)\WTSRV
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WTSRV="Windows Terminal Server Version 4.00"
multi(0)disk(0)rdisk(0)partition(2)\WTSRV="Windows Terminal Server Version 4.00 [VGA mode]" /basevideo /sos
---------------------------------------------

Failing the ideas above, not the least using the ERD routine... If this doesn't work, then re-install NT and let it 'Upgrade' the current installation. It will find/detect it when you run the set-up routine; then it gives you choice to 'Repair' (with or without the ERD) and also Upgrade. The Upgrade option will preserve all current settings, restore the NT boot-loader etc. - but you will have re-install the appropriate Service Pack.
But try the Repair option first...

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |