I added a second HD with win95 on. This hard drive was taken out of an old PAckard Bell system (used the hardware for new system). The new sys HD has W2Kpro (master),(works OK). Second HD win95 (slave). When I boot my system and get my boot page it reads;

windows 2000 pro or something
win 95

If i select W2K it boots fine. If I select 95 i get an error message;
Following file is mis or corrupt
<winows 2000 root>\system32\ntoskrnl.exe
Please reinstall a copy of above file.

How do I replace this file?

Bellow is my boot.ini file if its needed to referance.

[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\Win 95

[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\Win 95

is a rather "unusual" boot.ini to say the least...

The entry for W2K is OK; the 'entry' for '95 is pure fantasy...

The reference to '95 would "resemble":

c:\"Windows"

******
If i select W2K it boots fine. If I select 95 i get an error message;
Following file is mis(sing) or corrupt
<win(d)ows 2000 root>\system32\ntoskrnl.exe
Please reinstall a copy of above file.

How do I replace this file?

- you don't/can't. The entry as is for '95 is effectively another instruction for the boot-loader to attempt to boot to W2K (although you have tagged that line to be for '95)... It goes looking for W2K (ntoskrnl.exe), fails to find it on the partition stated to be on the W2K drive... (and that partition doesn't exist...), nor is it on the '95 drive.

Simply slaving the '95 drive to the W2K Master, and then adding a line to the boot.ini will not produce a dual-boot.

**********
To achieve a dual-boot - providing all the required conditions can be met - there has to be a bootsect.dos created which enables '9x to boot via the W2K boot-loader. There are at least a couple of ways to create this, and t3sjman appears not have reolved this item.

**********
This is the second post by t3sjman on this problem:

http://www.computing.net/windows2000/wwwboard/forum/55191.html is the first.

In the other post there was a request (response #2) for details of which version '95 is installed on this old PB-drive; also what is the format of the W2K Primary partiton. Neither info has been provided - thus t3sjman is still having problems. Also there was an outline of the issues involved (response #5) - but until t3sjman provides the info requested he's going round in circles...

If the version of '95 is '95a (this version cannot access fat32) or W2K = ntfs in the Primary, then there are workarounds that will allow the dual-boot - typically an add-in boot-util; or setting the '95 drive as Master to W2K set as Slave and then make the required tweaks to create the dual-boot; but this latter route would be a last resort...

Again - if t3sjman post the details of '95 and format of W2K Primary - then he'll get a workable resolution, one way or another...

Actually, this was the 3rd post. Didn't think anyone would respond after post went to 2nd page. My mistake.

Yes I keep going around in circles and would like to get out of the loop. I am in road construction this is my hobbie. I don't claim to be a IT professional.

Will post details asked for in respose #4 and #5,
http://www.computing.net/windows2000/wwwboard/forum/55191.html

But I think you alreddy gave me the answer.

jmant3s

Hey all,

We have a Dell PC with Win2K Professional and today I got a "Missing Ntldr" error.
I followed your reply in the forum here to boot from a floppy with the Ntldr, NTDETECT and Boot.ini files.
Now I get a new error :
+++++++++++++++++++++++++++++++++++++++++++++Windows 2000 could not start because the following file is missing or corrupt:
Windows 2000 root>system32?ntoskrnl.exe.
Please rei-nstall a copy of the above file.
+++++++++++++++++++++++++++++++++++++++++++++
I'm stuck and all my important files and S/W will be lost if I have to format and do a clean install !!!!!!!!!!!!!!

I heard I could use another hard-drive for OS installation and recover my first drive. How do I do this? Would appreciate if you can throw some light on this!

Please help me with any documentation or resources or directions as to how I should proceed !

Any help would be greatly appreciated,
Thanks in advance,
Await your reply ASAP,
K.

Can you recall what was going on prior to the initial error message?

If you can, post the boot.ini here; useful to see what's a going on???.

Options otherwise/besides:

A W2K repair routine which checks the system files.

http://is-it-true.org/nt/nt2000/atips/atips71.shtml

details the two routes for W2K repair (Manual/fast). On this occasion I would go the manual and use all three options.

If the repair route(s) fail then post back; there are other options too; but perhaps let's stay with the 'conventional' approaches first?

Obviously do NOT reformat etc. the drive...

Below is the Boot.ini file I've been using:
+++++++++++++++++++++++++++++++++++++++++++++
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
+++++++++++++++++++++++++++++++++++++++++++++

I still get the same error and cannot boot from the CD and have no command prompt ..... just the error screen.

Any help would be greatly appreciated if you can tell me how I can use another harddisk from another system with same config to fix the first one. Is this feasible?

Thanks,
K.

K:

Have you tried the repair routines I pointed to above?

You cannot use the ERD from another drive/system to repair this one; but a repair can frequently be achieved without an ERD as the required info etc. is also on the hard-drive in the %winnt%\repair folder. When no ERD the repair routine accesses that source. It's not always a successful approach, but does frequently work OK.

If the repair routines in my earlier post don't resolve it for you post back. As I said earlier there are other approaches - that will (usually) at least allow access to (and recovery of) the data. But let's go the standard routes first?

Also what was going on prior to the initial problems?

You 'should' be able to boot via the 4 floppies - or the CD - providing the boot-sequence (cmos/bios settings) are appropriate; i.e. either first boot-device = a: then c: ; or first = CD then a: then c: : or first = CD, then c: then ??? Check what your current boot-sequence is in the bios settings, and change accordingly if it's currently c: first... Once you have either the floppy set as first boot device - or the CD - then you should be able to boot and run/access the the CD and run setup\repair etc.

Would it be okay to boot with the Win2k boot disks i.e the 4 floppies and still regain the old system? Pls bear my dumb Qs as I'm trying to learn things.
I was trying to change the boot sequenee but it was not being saved. Is this because I haven't used the boot disks yet?
Thanks in advance,
K.

You have to go into the bios to change the boot-sequence. Almost immediately followng the standard (POST) (power on self-test) routine you should see a message telling you whuich/what key(s) to press to enter/access the bios. After that it's a relatively simple task to navigate to the appropriate section and make the change etc.
Then you boot with floppy or CD - depending on which you make first boot-device.

Personally I tend to favour leaving the floppy as first device and hard-drive second. Although as floppies seem to be disappearing it will not be long before it's logical to make it CD then hard-drive?

When you have changed the sequence you have to use the option to save changes and exit; simply using the exit (or exit without saving changes) option will not save the change.

Once you can boot with either the floppies or CD then you should be able to run the repair routines alluded to earlier.

If the repair options fail to resolve it all then there are other routes open to you - without resorting to another PC etc. (one of which essentially means you recover the original installation via an Upgrade of the current installation - more details on that later if need-be). See if the repair routes resolve it all first - once you can boot via floppy/CD.