M
Mr Big
Dear users,
I have a problem with boot.ini file.
I cannot find the file and I cannot create it because I get access
denied. I have gone through the following procedure (as Administrator).
attrib -r -s -h boot.ini file not found
copy boot.ini.works boot.ini access denied, file exists
????????
Writing a new boot.ini in an editor and saving it also gives acces
denied. I have also started with the CD, gone into repair and tried to
recreate it. It finds the installation but cannot add it due to access
denied. The PC boots with a message like "boot.ini does not exist,
using c:\windows\system32".
Any idea how I can recreate boot.ini?
Background:
The PC had two HD and the boot drive was about to crash so I moved the
boot partition to the other HD using Norton Ghost (great utility BTW).
The boot drive was in a really bad condition so the procedure took a
long. I removed the old drive, reconfigured the slave as a master and
rebooted. The rest you know. I guess boot.ini on the old drive was in
some bad sectors and something strange happened during the copy
procedure. Then again, the solution can be very simple.
Sincerely
I have a problem with boot.ini file.
I cannot find the file and I cannot create it because I get access
denied. I have gone through the following procedure (as Administrator).
attrib -r -s -h boot.ini file not found
copy boot.ini.works boot.ini access denied, file exists
????????
Writing a new boot.ini in an editor and saving it also gives acces
denied. I have also started with the CD, gone into repair and tried to
recreate it. It finds the installation but cannot add it due to access
denied. The PC boots with a message like "boot.ini does not exist,
using c:\windows\system32".
Any idea how I can recreate boot.ini?
Background:
The PC had two HD and the boot drive was about to crash so I moved the
boot partition to the other HD using Norton Ghost (great utility BTW).
The boot drive was in a really bad condition so the procedure took a
long. I removed the old drive, reconfigured the slave as a master and
rebooted. The rest you know. I guess boot.ini on the old drive was in
some bad sectors and something strange happened during the copy
procedure. Then again, the solution can be very simple.
Sincerely