boot.ini and ntoskrnl.sys missing or corrupt after running Nonav

[Guest]

ere's the situation:

I ran nonav (a symnatec utility to uninstall software and registry settings
on a system) and afterwards, I get two seperate messages that the boot.ini
and ntoskrnl.sys are missing or corrupt. I go into windows setup with the
repair option, and load the scsi driver to see my HD, setup never does see
the windows install. At this point I install windows into a new directory,
and boot up windows.

The problem is that I do not see the domain user's profile, I do see other
domain profiles, but not the normal user profile that I was using when I ran
nonav.

Can i edit the boot.ini file to point to the first directory winnt in the
first partition, or will this cause me more problems? If this would be the
way to go, I would create a 2000 boot disk with the original boot.ini just in
case the edited boot.ini doesn't work, correct?

Any other ideas or suggestions to pursue?

TIA

 

[John John]

You can make a boot floppy disk and try to boot with it. See here:
http://www.nu2.nu/bootdisk/ntboot/

Note: As instructed in the article the correct folder path for Windows
2000 is winnt. Also note that you may need the scsi drivers on the
diskette.

John

 

[Guest]

Thanks for the info, I was looking for a site on the boot.ini parameters.

One thing that I'm not really sure about is why the user profile is missing,
along with some other proograms & data. I can see and navigate within the
original WINNT directory, but I can't see any programs /data related to the
user's profile. Outlook data, desktop items , etc are nonexistent. I would
think that they are out there somewhere, but I am having a hard time finding
them.

Any ideas?

 

[Dave Patrick]

Boot.ini may be incorrect. Try creating a boot disk. For the floppy to
successfully boot Windows 2000 the disk must contain the "NT" boot sector.
Format a diskette (on a Windows 2000 machine, not a DOS/Win9x, so the NT
boot sector gets written to the floppy), and copy Windows 2000 versions of
ntldr, ntdetect.com, and boot.ini to it. Edit the boot.ini to give it a
correct ARC path for the machine you wish to boot. Below is an example of
boot.ini. The default is to start the operating system located on the first
partition of the primary or first drive (drive0). Then drive0 partition 2
and so on.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows 2000 0,1"
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows 2000 0,2"
multi(0)disk(0)rdisk(1)partition(1)\WINNT="Windows 2000 1,1"
multi(0)disk(0)rdisk(1)partition(2)\WINNT="Windows 2000 1,2"

Another possibility is to try loading the controller driver also from
floppy. For the floppy to successfully boot Windows 2000 the disk must
contain the "NT" boot sector. Format a diskette (on a Windows 2000 machine,
not a DOS/Win9x, so the "NT" boot sector gets written to the floppy), then
copy ntldr, ntdetect.com, and boot.ini to it. Edit the boot.ini to give it a
correct ARC path for the machine you wish to boot.

In order for this to work you'll want to change the arc path in boot.ini
from multi syntax to scsi syntax to indicate that Windows 2000 will load a
boot device driver and use that driver to access the boot partition. Then
also copy the correct manufacturer scsi driver to the floppy but renamed to
ntbootdd.sys


Something like this below;

[boot loader]
timeout=10
default=scsi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows 2000 0,1"
scsi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows 2000 0,2"
scsi(0)disk(1)rdisk(0)partition(1)\WINNT="Windows 2000 1,1"
scsi(0)disk(1)rdisk(0)partition(2)\WINNT="Windows 2000 1,2"


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| ere's the situation:
|
| I ran nonav (a symnatec utility to uninstall software and registry
settings
| on a system) and afterwards, I get two seperate messages that the boot.ini
| and ntoskrnl.sys are missing or corrupt. I go into windows setup with the
| repair option, and load the scsi driver to see my HD, setup never does see
| the windows install. At this point I install windows into a new directory,
| and boot up windows.
|
| The problem is that I do not see the domain user's profile, I do see other
| domain profiles, but not the normal user profile that I was using when I
ran
| nonav.
|
| Can i edit the boot.ini file to point to the first directory winnt in the
| first partition, or will this cause me more problems? If this would be the
| way to go, I would create a 2000 boot disk with the original boot.ini just
in
| case the edited boot.ini doesn't work, correct?
|
| Any other ideas or suggestions to pursue?
|
| TIA

 

[Dave Patrick]

It's really as simple as this; the profiles are all stored in;

C:\Documents and Settings\

either it's there or it isn't. In the past I've had my share of OS
destruction due to symantec installs or uninstalls.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Thanks for the info, I was looking for a site on the boot.ini parameters.
|
| One thing that I'm not really sure about is why the user profile is
missing,
| along with some other proograms & data. I can see and navigate within the
| original WINNT directory, but I can't see any programs /data related to
the
| user's profile. Outlook data, desktop items , etc are nonexistent. I would
| think that they are out there somewhere, but I am having a hard time
finding
| them.
|
| Any ideas?
|
|

 

[John John]

I don't know, with Symantec disasters you never know what kind of mess
one might end up with! Hopefully you can boot the original installation
and things pan out, or you have a recent backup set...

John