Solve : bios boot options vs actual boot options?

1.	Solve : bios boot options vs actual boot options?
Answer» i posted earlier about the NTLDR missing..that is not the real problem..here is the real problem toshiba a135.. under f2 setup i go into the bios boot options MENU and it has four options.. cd/dvd hdd fdd lan i put cd/dvd at the top and save..then check and it TRULY is at the top of the list..i have even on one occasion disabled the hdd as a boot option.. computer does not read from cd/dvd and gives the missing ntldr msg..this is not the problem.. when i do f12 to select boot option it only list the following hdd lan i dont know or understand how the f12 boot options are different from the f2 bios setup options..or how to get them synchronized so the computer can boot from cd..the drive works..spins and acts LIKE it is reading..but is not loading because the f12 boot options do not have cd/dvd among the options and apparently the bios settings are not being used.. keithWhen you are making the changes in the main screen have you tried hitting F10 which is "save changes and exit" ? ?Quote computer does not read from cd/dvd and gives the missing ntldr msg..this is not the problem.. It is not reading the drives properly. Some BIOS firmware has defaults that over ride the user preferences when a valid boot device is not found. This can happen when there is a bad cable, the drive is failing or there may be some other type of weakness in the hardware and electronics. A common problem is when people use CS, cable select, when they do not have the right cable. Flat 40 wire ribbon is not the right cable. The message "missing NTLDR' is given when the BIOS finds a device with a NT boot sector and without the loader. Most often that is found on floppy drives. But it can occur if there are two HDDs in the system and the wrong one was selected. Also, in a single drive system a damaged or altered MBR will CAUSE this error. In a few cases the operator has tried to change the partition settings with a program that does not work well with the current guidelines set by Microsoft for the MBR. Linux can do that. But even a bad HDD can do this. The drive may be good one day and bad the next. I have one here that was working, but just today it failed and it would prevent the BIOS from doing anything. It would stall the machine!

Answer»

i posted earlier about the NTLDR missing..that is not the real problem..here is the real problem

toshiba a135..

under f2 setup

i go into the bios boot options MENU and it has four options..

cd/dvd
hdd
fdd
lan

i put cd/dvd at the top and save..then check and it TRULY is at the top of the list..i have even on one occasion disabled the hdd as a boot option..

computer does not read from cd/dvd and gives the missing ntldr msg..this is not the problem..

when i do f12 to select boot option it only list the following

hdd
lan

i dont know or understand how the f12 boot options are different from the f2 bios setup options..or how to get them synchronized so the computer can boot from cd..the drive works..spins and acts LIKE it is reading..but is not loading because the f12 boot options do not have cd/dvd among the options and apparently the bios settings are not being used..

keithWhen you are making the changes in the main screen have you tried hitting F10 which is "save changes and exit" ? ?Quote

computer does not read from cd/dvd and gives the missing ntldr msg..this is not the problem..

It is not reading the drives properly. Some BIOS firmware has defaults that over ride the user preferences when a valid boot device is not found. This can happen when there is a bad cable, the drive is failing or there may be some other type of weakness in the hardware and electronics. A common problem is when people use CS, cable select, when they do not have the right cable. Flat 40 wire ribbon is not the right cable.

The message "missing NTLDR' is given when the BIOS finds a device with a NT boot sector and without the loader. Most often that is found on floppy drives. But it can occur if there are two HDDs in the system and the wrong one was selected. Also, in a single drive system a damaged or altered MBR will CAUSE this error. In a few cases the operator has tried to change the partition settings with a program that does not work well with the current guidelines set by Microsoft for the MBR. Linux can do that.

But even a bad HDD can do this. The drive may be good one day and bad the next. I have one here that was working, but just today it failed and it would prevent the BIOS from doing anything. It would stall the machine!

Solve : bios boot options vs actual boot options?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment