SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Dream Machine ( Build your own PC )
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Spots who wrote (7458)5/13/1999 12:26:00 AM
From: Clarence Dodge  Read Replies (1) of 14778
 
ALL you have to do
to multiboot an NT on another drive is to add a line
to the boot.ini file which clues NT in to where the
alternate NT system is.

Everything went well until the actual boot attempt. This backup copy of NT is on the same disk as the origin except one partition over, so the added line in boot.ini was the same as the existing line except Partition(1) changed to Partition(2).

Both OSs show up during boot. When I choose the new one though, the message comes up that NT cannot start because the file winnt\system32\Ntoskrnl.exe is missing or corrupt.

So back to an original NT boot, check the new OS for that file and its there alright. Next, thinking it may be corrupt, I replace it with a copy from the original NT system32 folder, which I know is good since I just booted it. Back to try a boot from the new backup copy and the same message comes up.

Why is this Ntoskrnl.exe file apparently working ok in the original NT but not in the backup copy?

Sorry
to be so long getting back.

Not a problem:-)

Clarence
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  

HomeMailHotSubjectMarksPeopleMarksKeepersSettings
Terms Of UseContact UsCopyright/IP PolicyPrivacy PolicyAbout UsFAQAdvertise on SI
© 2025 Knight Sac Media.  Data provided by Twelve Data, Alpha Vantage, and CityFALCON News