Looking for tech help?
Whether you’re looking for dependable tech advice or offering helpful tricks, join the conversation in our forums.
Merely disconnecting the power from the drive (if you even have one) won't solve the problem.
Boot from a Windows CD, into 'repair console' and then issue the 'fixboot' and 'fixmbr' to repair booting issues.
Assuming you have access to a Windows disc, then boot from it and use it to access the 'system restore' points.
Sorry that these solutions depend on have a Windows disc, but if you can borrow one from a friend, you should be able to get back on track.
Also... make sure NOT to have any USB flash-drive installed upon boot-up. This always plays tricks on people and I've watched many presentations get delayed due to people not understanding that the computer will try to boot from the attached device!
Based on my advice above, you would also be able to do a system repair, if booting from a Windows CD. Note that if you try a re-install, Windows will bug you about having it installed already. Quite often, this will mess up your desktop but will indeed replace any damaged OS files so that you're up and running again.
Hope this helps?
Mark in Toronto
@MarkinTO made a good suggestion - learned something - Plus have found that my new
HP printer - officejet 6700 - plugs in with a usb cable - cant have that plugged in at startup
because it locks up the system - Looking for a mass storage device - hahaha
anyway - I was going to suggest hitting - Del - at startup and looking at setup - if it is not
listed, then a reset - should - cover it as markin said. if the del wont even get you to the bios
then back to markins answer - again :-))
Instead of unplugging the USB cable, turn your printer off when you start your PC up. Once it is up and running, remove the drivers for your printer and then reboof your PC with the printer ON. The PC should come up and try to configure your printer. If it still tries to boot from your printer, replace the printer cable and/ or make sure your PC is fully up to date driver wise.
thanks - printer not on at start up. own outlet so I keep it off until needed. not totally happy with
this new printer anyway - they changed some of the printer function software so everything is
some sort of work around.
the restart with it on and the hp programs etc uninstalled sounds like a good idea.
hahaha even when I forget to unplug the usb after use it will take forever when I shut
down for the night.
I will try that, thanks again.
Edit you bios boot menu placing flash under hdd so you boot up doesn't try to find a flash drive in your printer. If your printer doesn't have a flash drive it might have the same driver as a model that does. You can also disable boot from flash until you need it unless you use it a lot.
Some "printers" ARE mass storage devices. I have not checked. Dooes your printer have card slots for SD cards, etc.? In that case it may appear as a mass storage device as well as a printer and whatever else is attached. If you have to unplug it to boot, I'd suggest removing it from the device manager and uninstall all of its drivers. After booting, don't plug the printer in right away. Many USB device setup instructions tell you NOT to plug in the device until the installation software tells you to. If you get this working OK, then you can update drivers from the web.
The BIOS is technically a firmware item that controls POST and a lot of I/O. You might want to make sure it is current. Check the website for the PC mfg under software/drivers/firmware. Also, the HP printer usually comes with drivers AND firmware. Look that up on the HP support site under drivers/firmware/downloads. Also, make sure the printer is plugged into the right version USB port (USB vs. USB 2.0 vs. USB 3.0).
Hi, I run into this often with usb devices such as printers with card slots. There are good suggestions here but if you haven't resolved your issue yet try disabling "boot to usb" and or disabling all but the hard drive as boot options in your bios. I have found that going to the last page in the bios and restoring the optimal defaults first is sometimes necessary.
I had the same problem on an intel DQ35JO system board and my blue screen occurred with the windows XP CD as well. It was a dual boot machine and Both XP and Win 7 were suddenly blue screening. I was able to repair the Win 7 system with the Win 7 DVD but never could get the XP partition to boot again.
"MarkinTO" is right on the money with his tips, Jon D. I'm running XP (SP3) on what most might consider a quaint antique of a machine (a Compaq EVO sporting an old CD-ROM drive and a Floppy " A " drive along with a blazing 512MB of RAM ). Even though I know my "A" drive is as dead as the proverbial overly flogged horse, the EVO still sees it as "functioning properly", lights up the little green light at start-up, etc. Since I never use it and it doesn't seem to have any other impact on the machine's functioning, I've just decided to leave the thing be and "let sleeping dogs lie" since "if it ain't broke, don't fix it" as they say.
But, fortunately, I've not encountered the exact problem you seem to be experiencing, Jon. But, the two times where I've managed to completely mess up XP's proper functioning (by my incessant tinkering "under the hood"), I've followed very similiar steps "MarkinTO" listed above with good results. And, oh yeah, don't forget the USB flash drive as he said... I've done that more than once myself.
Sorry to hear that you can't boot into WinXP Home. This suggestion isn't very computer geek, but it just might work. Try replacing your keyboard and then try F2 setup to remove the Floppy. I'm not kidding...your solution may be just that simple. Wal-Mart has cheap one's for as low as $10. If it doesn't work you can return it. Good Luck!
Together Everyone Achieves More
I made the assumption that your computer had not been recently placed into service from storage. If so, if you are using a P/S2 keyboard be sure that you have it plugged into the "purple" port and not the "green" port that is used for mice. Also examine the pins to understand if any are bent or broken.
Note: This post was edited by its original author to merge two posts into one. on 06/07/2013 at 12:09 PM PT
We need more information. What kind and how old a computer? How much RAM (Working Memory)?
I just dealt with a HP/Compact (2005) with XP Home. The computer only had 1Gigabyte RAM and had just added a usb printer and Xfinity "Advantage Gaurd Security".
Computer would stop at HP blue screen wait then boot OS, reboot OS, reboot OS then freeze at HP Blue screen.
Added memory up to 4Gigabyte and solved all problems.
Hope this helps!
On the one hand, it could be a hardware issue. Or it could be a virus or some other form of malware, or it could be some new piece of hardware that is causing problems.
If you have access to another computer, try downloading one of the plethora of Linux trial CDs - the ones where you burn the Linux image to a CD and can boot from it. Simply put this will tell you at least one important thing - if it's a hardware or software issue. Odds are if the hardware is FUBAR, then it won't load properly either.
On the other hand, if it does load properly, you will have the option of backing up any files you haven't already backed up. You should be able to plug in a USB based drive and copy the files to the external drive.
At this point, you can of course, either try a repair installation OR you can blow out the hard drive and do a fresh, clean installation. With XP, it's generally best to clean installation. Granted, it's more work doing it that way, but its also more reliable.
if it's a hardware issue,... You will likely need/want a new system - and depending on the system, you can possibly replace the motherboard, CPU and RAM (and potentially the hard drive if that's the problem) - or you can simply replace the entire system with a newer one. But don't throw out the hard drive just yet. You can possibly restore data from it by removing it and putting it in an external enclosure once you've got the system up and running.
Assuming that you actually have a floppy device (I've seen stranger), as someone else suggested, I'd completely disconnect both power and data cables and see if the machine comes up. In that F2 setup, check to see if the floppy drive is listed in any other setup screens besides the boot sequence.
Now see if the machine boots. If it doesn't, check to see what BIOS version you are using and then DOWNLOAD the BIOS from the manufacturer's website and flash the BIOS. (Use another PC to create a.. ummm... not floppy disk but a CD. You can always get an external floppy drive (USB) these days if you really need one pretty cheap or go out and replace the one you already have. Make sure if your drive is 2HD that you are using matching floppies. They don't work well with some really old stuff.
Take that bad floppy disk out of the drive. Doh. (What's a floppy, my son asks!)
Seriously, boot to bios and remove the floppy if possible. Change the boot sequence to primary disk first, then CDROM. Last choice should be the floppy if it has to be in there.
Make sure everything is plugged in fully, inside and out. Keyboard, mouse, drive cables...
More info would help. Good luck!
Give this a try.
Based on this thread in another forum
Rather than removing the floppy drive from sequence, try turning the Floppy to OFF. It worked for this individual, it's worth a shot.
Here is a Youtube video on how to do it.
Note: This post was edited by its original author on 06/07/2013 at 3:35 PM PT
When you turn your computer on, you might see F2 Setup and F12 Load Devices, or something to that effect. Press F2, which will get you into your computer's BIOS. Using the arrows, scroll down to Startup Order, tap "RETURN" to get into the menu. On some computers, all you have to do is tap the "D" key to push a startup item down on the list of items to start. Tap "U" for raising a highlighted drive up on the list. Make sure that your hard drive or your CD ROM is first, at the top. To get out of that menu, tap "ESC," and "ACCEPT The CHANGE."
Then scroll down to "DRIVES." Tap "RETURN." "Floppy" is probably the first on the list. Tap "RETURN" to highlight "Floppy" and open up the choices. Using the left arrow key, go all the way left and choose "OFF." Tap "ESC," then choose "ACCEPT CHANGES," and tap "RETURN." You might still have to accept "EXIT," by tapping "RETURN."
The machine will shut down and restart. Your annoying Floppy message should have disappeared.
Happy computing to you!
I may be mistaken, but I believe if the load sequence was changed so that Drive C is the last device such as "A:, E:, C:", the floppy error would not display if it ended up finding the OS on C:. The BIOS will keep looking in the boot order until it finally got to C: and finds the OS. The floppy error displays because it is the last device listed to be searched for the OS, and it failed. The PC went past Drive C in its search for a bootable OS, indicating a hard drive failure. Don't overthink the symptoms; the simplest and most likely solution is usually right.
So long as Drive C is where the OS is located and it is in the Startup Order list, it doesn't matter what order it tries to boot each device. If C: is the first device it will not search the others on the list since it already found a bootable OS. If it is the last device and a floppy drive is first, it will turn on the floppy drive light briefly, didn't find the OS, then go on to the next device without any error indicators. The error indicates it can't find an OS on ANY device listed and the floppy was the last device it had on the list. Either Drive C isn't on the list, Drive C is not available (crashed), or conceivably the OS on Drive C is corrupted. Hard drive crash is the most likely reason for the floppy error.
Low-level errors like this may point to the operating system being confused as to the correct drive letter to boot from. Maybe it's not seeing the C: drive, or the master boot record has become corrupted. So it looks to the floppy to see if there is a boot record there, or the like.
The first thing I'd do is run a scan on the hard drive. Use Seatools for DOS to see if you have any bad sectors, or if the SMART has been tripped. If it has, you have a dying drive. Resolving that becomes a whole other issue, but it's where I'd start before I did anything else.
Looking for tech help?