"No operating system" message

Hi there,

maybe you could help me solve the following problem, couldn't you?

I have two operating systems installed on one PC (Win2k Pro & Win XP Pro).

Due to recent crashes of Win XP I decided to re-format partition C:
where it was installed. After that, I installed Win XP again, but not
being on Win2k, but using the bootable mode of the Win XP installation cd (after switching in the bios to read from the CDROM first).

The installation ran smoothly and correctly, but when I turn on the
computer, then I'm unable to boot from C: (in the bios the boot
settings are: A, C, SCSI).
Following information appears:

"Verifying DMI Pool Data ... "
No operating system

Fortunately, I've made a XP Boot Disk using a program called WinRescueXP and whenever I put the floppy into the A: drive, then the PC boots correctly and I'm able to choose the O/S and to load it.

I already have copied the files from the XP Boot Disk into the root
directory, ie C:, but it did not help. Which file is responsible for
detecting the operating system?
How could I solve this problem? I don't want to have to put the floppy into A each time I'm about to turn on the computer

Thank you!
Ralf S.

 

If you boot to your XPpro CD and start the install there will be an option for the recovery console. - (kind of DOS for NTfs)

There are two console commands which might apply:

fixmbr
fixboot

Try them - although I will warn you, it may force the XP bootloader to come up and that is where you will choose XP or W2K - on each boot.

Personnally I use LILO for my W98/W2K/WXP/Linux box - but after I did the WXP install, choosing W98 will bring up the XP boot loader and I have to choose W98 again from that menu. (M$B$)

 

You need ntldr, ntdetect.com, and boot.ini. The computer will boot from a "quick-boot" floppy containing these three files (for future reference--I realize you are trying to avoid booting from floppy).

 

Abraxas,

currently I'm booting from the floppy which contains the files you mentioned - so I'm able to load Windows XP this way only. My root directory (C:\) also contains theses files and a few other. Unfortunately, the PC ignores them and displays the info "no operating system ".

Yes, I want to avoid this method of booting

Thnx,
Ralf S.

 

You could try replacing the files on HD with the ones on the floppy. Are they the exact same sizes, or different?
There are problems copying these files. For example, I got a message after trying to copy ntldr that the copy operation could not be completed due to some sys protection or permissions issue, but the copy was fine and the PC still booted from the floppy, so I don't know what that was all about.
What else in on the floppy, just out of curiosity?

 

Also, just out of curiosity, how is the HD partitioned? Is XP first or 2k? There is a problem with the OS being detected in the NT family if the primary OS is located above the 4 gig limit on the HD.

 

Yes, I did replace those files from the floppy prior to writing here, but this didn't help, although all files have copied without any problems.

I have to HDDs - the O/Ss are on the bigger and first HDD (20 GB): WinXP is first on C: (7 GB) and Win2kPro is on H: (5 GB).
The rest, ie another partition E:, is being used for data storage.

On the smaller HDD (3.2 GB) I have three partitions D, G, F each has a size of approx. 1 GB.


Maybe I'll try the suggestion given by Profgab101 yet ...

Thanks,

Ralf S.

 

Take a close look at the boot.ini files on PC and floppy. They are simple text files so any editing program will do.

Make sure the file on the Hd matches the floppy file since this data is read early on in the boot sequence and must be correct so NT will know where to look for an operating system.

If there is a difference, just edit and save the hard disk copy. BTW - if you use notepad for the changes, make sure it doesn't append a .txt on the end because trust me (been there, done that) boot.ini.txt WILL NOT work.

 

The files in C: match the files on the bootable floppy perfectly. I have copied the entire content of the floppy into C:. Despite of this the PC does not see them and wants to boot from the floppy only.

I'm at a complete loss

 

Go into the recovery console, remove the floppy (just in case--you don't want to inadvertantly repair the floppy-boot process), and try Profgab101's suggestions.

 

I did follow the instructions given by Profgab101, but to no avail. After entering the command "fixboot" when in C:\Windows\ ,
it said that it would repair the booting problem, but it has only been corrected supposedly. In fact, I ran into the same problem after doing this procedure.

What is "fixmbr" for? I did try to apply this as well, but finally was frightened of doing this, because it said that it might mess up the partitions in case something's running not well.



Ralf S

 

Hi again,

as I mentioned before, the command "fixboot C:" didn't repair anything. Trying to enter "fixmbr" while being logged into C: I can read following (this is a translation):
"Warning! This computer has a non-standard or not well working master boot record ".

But below it says that applying this can cause some partitions to be inaccessible. Should I risk???? It seems logical, because Windows loads when it reads from the floppy and never loads when it reads from C:

What do you thing about this?

Ralf S.

 

I guess if I were in your situation, I would try the fixmbr. The warning may be something of an exaggeration, just to warn you of worst-case scenarios. The warning had it right--there is something wrong with the Master Boot Record.
Again, I would remove the floppy before using this command.

 

I'm almost giving it up! The command "fixmbr" also didn't repair anything. The difference is that now I can see the same message in English (before in Polish): "Missing operating system" when booting from C:

It's odd that fixmbr claimed having repaired the problem. I did it even twice, and it was strange that at the second try it also said about a non-standart or corrupted Master Boot Record.

Maybe I should mention it again that I did re-install WinXP Pro on a HD where another OS (Win2kPro) has already been installed. After a smooth installation problems began ...

Ralf S.

 

Wow, M$ being extra stubborn.

Well, you can always start the XP install program, and when it detects the existing install choose "repair" - it will go through what appears to be a full install, but all existing programs, files and personal settings will still be there.

The only possible downside to this is that any other M$ O/S installed (it will probe all connected drives.) will now be listed in the XP bootloader.

 

Hi all,

according to Profgab101's suggestion I booted from CD-Rom and using the Recovery Console I tried to repair the existing copy of WinXP Pro. The installation ran well, but I still can't boot from C: - it didn't tell "missing operation system" this time, but displayed this message "Verifying DMI Pool Data ... ". I waited more than 10 minutes to see if something happens, but nothing happened.

Could it be that my harddrive is physically damaged although it loads WinXP Pro and Win2k Pro when using a bootable floppy?

Should I thank MS that after trying to reinstall MS's OS I have to buy another HDD?

Is there anything you know of I could try yet to solve this terrible issue??

Ralf S.

 

Hi ralfska. Prior to try "fixboot" and "fixmbr ", I suggest first go to B.I.O.S. set-up and check and be sure that your B.I.O.S. has not put your Master Boot Record, or MBR (1st sector on your 1st H.D.) in READ-ONLY mode.

Some B.I.O.S.es list this feature as "Virus Protection ", too. Be sure that you DISABLED it first.

And, if you have to re-install everything, I strongly recommend you that try to back-up everything yours off-line, take away (phisically disconnect) your 2nd H.D., leaving your 1st one alone, and repartition it. Install the older O.S. in "C: ", and leave the rest blank, 'till the 2nd. O.S. install time (as "D: "), and just then add your older H.D. Then play with drive letters or "mount points" (a-la UNIX) as you wish

Good Luck.

 

Hi jmmf, I didn't find anything put in the read-only mode in the Bios and hope I didn't oversee this.
Maybe I could "Load Bios Defaults" and/or "Setup Defaults" to see if it doesn't solve the problem, but honestly, I'm almost giving up ...

How do you think?: Can the HDD get phisically damaged as the boot sector doesn't work?

Ralf S.

 

Yes, it can. And very easily, indeed.

Better follow my advice and strat fresh. Back-up all your personal and valuable data to your 2nd *physicall* H.D., or get some one from a friend just for 1 day or so... Then disconnect that H.D. and blow-up yours.

Again... Good Luck !!!

 

ralfska - you could have picked up a boot sector virus. That would certainly account for some of the strange things your system is doing. Some of these critters are clever enough to survive a MBR repair attempt.