Re: 'select proper boot device' .... Strange recent behavior with hybernation and now startup!

Tech-Archive recommends: Speed Up your PC by fixing your registry

Smoker~ wrote:
Don't use the hibernation at all if you have problems with it and until this
is fixed it will only complicate the matter.

as I said, it is happening now from shutdown, that's the scary part.

Go into your BIOS and check all the settings especially your boot sequence
where the order should be Floppy first, then CD ROM/Optical, then Hard
Drive.

Unplug your DSL modem from the power, pull all the cords out of it and wait
awhile. Do this with your machine turned off. Verizon calls this recycling
the modem. Actually it might be a goof idea to reboot with your modem
disconnected from the computer, then shut it down and plug everything in and
start up. I really forget but call VZ and they will tell you.


If you have a problem starting up what happens when you start in Safe Mode?

like I said, I can't do anything, either from hibernation startup or
starting from a shutdown, no F8 , no nothing!

What OS are you using?

WinXP Pro, clean install first of the this year.

Try it as the solution. You're talking about your uninstall of Sun Java? Got
to get you stable before you install that again, don't you think?


I have been doing some investigating after I sent this and it looks like
this problem is not uncommon but as usual, varied answers, worst thing,
it can be a precursor to HD failure. for some background, should have
done this first, in my case that shouldn't be the problem as it is a new
drive with a new XP Pro install 2 months back. modem was installed from
the very first and no problems for a month then this. I have done a
Google search and it doesn't sound very good and pretty much seems to
have little to do with modems, or even programs for that matter. maybe
things like BIOS, which I haven't really changed much from its default,
the boot sequence as you are talking about is HD only for simplicities
sake and quicker startup. however, reading some of the answers to this
problem from that search does sound suspiciously HD in nature and the
fact that it will start after a reboot, but now is taking more reboots
to get it to start should be a clue. guess I better call Maxtor,
unfortunately I'll have to wait until next week.

I found this suggestion in a discussion of this problem. what do you think?

How to Repair the Boot Sector:
If XP won't start it may be due to a damaged boot sector or a missing or
corrupt ntldr or ntdetect.com files.

To replace damaged ntldr and ntdetect.com you can copy fresh files from
the XP CD using the COPY command. Boot with the XP CD and enter the
Recovery Console (as above). At the Command Prompt type the following
(where "X" is your CD-Rom drive letter) allowing the files to overwrite
the old files
COPY X:\i386\NTLDR C:
COPY X:\i386\NTDETECT.COM C:

To repair a damaged Boot Sector at the command prompt type FIXBOOT and
press Enter. Then answer "Y"


then from a Google groups search, there's things like this over the years:

Your hard drive is in some way corrupted, and the Recovery disk being
sent to you are the ONLY way to work through finding out if it can be
fixed by you, or if you need replacement hardware

If your computer work besides the annoyance you have described, try
going into the BIOS and unselect everything on the boot sequence besides
the hard drive.

Is there a setting in the bios for the amount of time it waits for the
drives to spinup? It sounds like your boot drive isn't being recognized
the first boot. ON the reboot since the drives have spunup their recognized.

Is the "IDE Detect Timeout" set to 35 seconds ? That is the
maximum time the BIOS will wait for a drive to finish spinning
up, when connected to the Southbridge. I don't think the Promise
20378 chip has a configuration option for timeouts (RAID BIOS
modules for add-on chips don't seem to support that option
in general).


.

Quantcast