After Updates, StartUp Menu F8 on boot not working

  • Thread starter Thread starter Dugie
  • Start date Start date
D

Dugie

Hi,

I hope someone can help.

Win 2K Pro, SP4.
After installing all 10 of the latest from Win Update, I noticed
that pressing F8 at boot doesn't work. It worked fine before the updates.
Everything else
seems ok.

When pressing F8, at times the screen will flash the Startup Menu, but the
boot continues.

Thanks,
Dugie
 
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:
Hi,

I hope someone can help.

Win 2K Pro, SP4.
After installing all 10 of the latest from Win Update, I noticed
that pressing F8 at boot doesn't work. It worked fine before the
updates. Everything else
seems ok.

When pressing F8, at times the screen will flash the Startup Menu,
but the boot continues.

Thanks,
Dugie
Click to expand...

What does your boot.ini look like? Copy/paste it into a response to this if
you want.

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

"A man should keep his little brain attic stocked with all the
furniture that he is likely to use, and the rest he can put away in the
lumber-room of his library where he can get it if he wants it."

Sherlock Holmes
 
Galen said:
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:


What does your boot.ini look like? Copy/paste it into a response to this if
you want.

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

"A man should keep his little brain attic stocked with all the
furniture that he is likely to use, and the rest he can put away in the
lumber-room of his library where he can get it if he wants it."

Sherlock Holmes
Click to expand...
Boot.ini:

[boot loader]
timeout=40
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

Thanks!

Dugie
 
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:
Galen said:
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:


What does your boot.ini look like? Copy/paste it into a response to
this if you want.

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

"A man should keep his little brain attic stocked with all the
furniture that he is likely to use, and the rest he can put away in
the lumber-room of his library where he can get it if he wants it."

Sherlock Holmes
Click to expand...
Boot.ini:

[boot loader]
timeout=40
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

Thanks!

Dugie
Click to expand...

That looks to be okay by my reckoning? Hmm... Curious... What happens if you
try to force it by editing the boot.ini?

http://support.microsoft.com/?kbid=239780

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

"A man should keep his little brain attic stocked with all the
furniture that he is likely to use, and the rest he can put away in the
lumber-room of his library where he can get it if he wants it."

Sherlock Holmes
 
Galen said:
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:
Galen said:
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:

Hi,

I hope someone can help.

Win 2K Pro, SP4.
After installing all 10 of the latest from Win Update, I noticed
that pressing F8 at boot doesn't work. It worked fine before the
updates. Everything else
seems ok.

When pressing F8, at times the screen will flash the Startup Menu,
but the boot continues.

Thanks,
Dugie

What does your boot.ini look like? Copy/paste it into a response to
this if you want.

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

"A man should keep his little brain attic stocked with all the
furniture that he is likely to use, and the rest he can put away in
the lumber-room of his library where he can get it if he wants it."

Sherlock Holmes
Click to expand...
Boot.ini:

[boot loader]
timeout=40
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

Thanks!

Dugie
Click to expand...

That looks to be okay by my reckoning? Hmm... Curious... What happens if you
try to force it by editing the boot.ini?

http://support.microsoft.com/?kbid=239780
Click to expand...

Not sure what can be forced. What would you suggest to forcc?

I visited the http://support.microsoft.com/?kbid=239780 link. It's not
simple. :-) Explanations for the switches are minimal.
I'll try /safeboot:minimal /sos /bootlog /noguiboot and leave /fastdetect in
place. It's a home computer with no networking. Also backed up my boot.ini
file.

Thanks!
Dugie
 
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:
Galen said:
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:

Hi,

I hope someone can help.

Win 2K Pro, SP4.
After installing all 10 of the latest from Win Update, I noticed
that pressing F8 at boot doesn't work. It worked fine before the
updates. Everything else
seems ok.

When pressing F8, at times the screen will flash the Startup Menu,
but the boot continues.

Thanks,
Dugie

What does your boot.ini look like? Copy/paste it into a response to
this if you want.

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

"A man should keep his little brain attic stocked with all the
furniture that he is likely to use, and the rest he can put away in
the lumber-room of his library where he can get it if he wants it."

Sherlock Holmes
Boot.ini:

[boot loader]
timeout=40
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

Thanks!

Dugie
Click to expand...

That looks to be okay by my reckoning? Hmm... Curious... What
happens if you try to force it by editing the boot.ini?

http://support.microsoft.com/?kbid=239780
Click to expand...

Not sure what can be forced. What would you suggest to forcc?

I visited the http://support.microsoft.com/?kbid=239780 link. It's not
simple. :-) Explanations for the switches are minimal.
I'll try /safeboot:minimal /sos /bootlog /noguiboot and leave
/fastdetect in place. It's a home computer with no networking. Also
backed up my boot.ini file.

Thanks!
Dugie
Click to expand...

When you use the sample boot.ini file provided on the page does it boot into
safe mode? I'm basically trying to see what solutions there are to offer you
because, well, I'm not sure of the reason that this has happened. It's
something I've not seen before and when I try to find an answer for you via
the normal search routines I come up with nothing specific though it could
be that I'm just using flawed search terms. <g>

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

"A man should keep his little brain attic stocked with all the
furniture that he is likely to use, and the rest he can put away in the
lumber-room of his library where he can get it if he wants it."

Sherlock Holmes
 
Galen said:
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:
Galen said:
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:

In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:

Hi,

I hope someone can help.

Win 2K Pro, SP4.
After installing all 10 of the latest from Win Update, I noticed
that pressing F8 at boot doesn't work. It worked fine before the
updates. Everything else
seems ok.

When pressing F8, at times the screen will flash the Startup Menu,
but the boot continues.

Thanks,
Dugie

What does your boot.ini look like? Copy/paste it into a response to
this if you want.

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

"A man should keep his little brain attic stocked with all the
furniture that he is likely to use, and the rest he can put away in
the lumber-room of his library where he can get it if he wants it."

Sherlock Holmes
Boot.ini:

[boot loader]
timeout=40
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

Thanks!

Dugie

That looks to be okay by my reckoning? Hmm... Curious... What
happens if you try to force it by editing the boot.ini?

http://support.microsoft.com/?kbid=239780
Click to expand...

Not sure what can be forced. What would you suggest to forcc?

I visited the http://support.microsoft.com/?kbid=239780 link. It's not
simple. :-) Explanations for the switches are minimal.
I'll try /safeboot:minimal /sos /bootlog /noguiboot and leave
/fastdetect in place. It's a home computer with no networking. Also
backed up my boot.ini file.

Thanks!
Dugie
Click to expand...

When you use the sample boot.ini file provided on the page does it boot into
safe mode? I'm basically trying to see what solutions there are to offer you
because, well, I'm not sure of the reason that this has happened. It's
something I've not seen before and when I try to find an answer for you via
the normal search routines I come up with nothing specific though it could
be that I'm just using flawed search terms. <g>
Click to expand...

Hi Galen,

When I tried the switches above:
/safeboot:minimal /sos /bootlog /noguiboot /fastdetect

I got a blue screen:
STOP: 0x0000000A (0xEB915354,0X000000FF,0x00000001,0x804640791)
IRQL_NOT_LESS_OR_EQUAL
Address 80464079 base at 80400000, Date Stamp 427b58bb - ntoskrnl.exe

Took me a while to remember to use the Recovery Console to ren the old .ini
so I could boot. :-(

My C: drive is a fairly new WD 160GB, so I'm using Western Digital's Dynamic
Drive Overlay v9.85. Using only 128G (binary?), since I don't trust the
overlay... yet. Other drives: 20G & 30G. Machine is 902Mhz.

I'll try the sample file & report results, assuming it's:
[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 Advanced
Server" /fastdetect /SAFEBOOT:MINIMAL(ALTERNATESHELL)

I won't be around for a few days.
If an MVP is having problems researching this, I don't feel so badly about
finding no solutions. :-)

Thanks for your suggestions and help!

Dugie
 
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:
Galen said:
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:

In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:

Hi,

I hope someone can help.

Win 2K Pro, SP4.
After installing all 10 of the latest from Win Update, I noticed
that pressing F8 at boot doesn't work. It worked fine before the
updates. Everything else
seems ok.

When pressing F8, at times the screen will flash the Startup
Menu, but the boot continues.

Thanks,
Dugie

What does your boot.ini look like? Copy/paste it into a response
to this if you want.

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

"A man should keep his little brain attic stocked with all the
furniture that he is likely to use, and the rest he can put away
in the lumber-room of his library where he can get it if he
wants it."

Sherlock Holmes
Boot.ini:

[boot loader]
timeout=40
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

Thanks!

Dugie

That looks to be okay by my reckoning? Hmm... Curious... What
happens if you try to force it by editing the boot.ini?

http://support.microsoft.com/?kbid=239780

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

Not sure what can be forced. What would you suggest to forcc?

I visited the http://support.microsoft.com/?kbid=239780 link. It's
not simple. :-) Explanations for the switches are minimal.
I'll try /safeboot:minimal /sos /bootlog /noguiboot and leave
/fastdetect in place. It's a home computer with no networking. Also
backed up my boot.ini file.

Thanks!
Dugie
Click to expand...

When you use the sample boot.ini file provided on the page does it
boot into safe mode? I'm basically trying to see what solutions
there are to offer you because, well, I'm not sure of the reason
that this has happened. It's something I've not seen before and when
I try to find an answer for you via the normal search routines I
come up with nothing specific though it could be that I'm just using
flawed search terms. <g>
Click to expand...

Hi Galen,

When I tried the switches above:
/safeboot:minimal /sos /bootlog /noguiboot /fastdetect

I got a blue screen:
STOP: 0x0000000A (0xEB915354,0X000000FF,0x00000001,0x804640791)
IRQL_NOT_LESS_OR_EQUAL
Address 80464079 base at 80400000, Date Stamp 427b58bb - ntoskrnl.exe

Took me a while to remember to use the Recovery Console to ren the
old .ini so I could boot. :-(

My C: drive is a fairly new WD 160GB, so I'm using Western Digital's
Dynamic Drive Overlay v9.85. Using only 128G (binary?), since I don't
trust the overlay... yet. Other drives: 20G & 30G. Machine is 902Mhz.

I'll try the sample file & report results, assuming it's:
[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
Advanced Server" /fastdetect /SAFEBOOT:MINIMAL(ALTERNATESHELL)

I won't be around for a few days.
If an MVP is having problems researching this, I don't feel so badly
about finding no solutions. :-)

Thanks for your suggestions and help!

Dugie
Click to expand...

Hmm... A BSOD... Well that throws a monkey wrench into it.

Here's general information on your error?
http://support.microsoft.com/default.aspx?scid=kb;en-us;130802

I'd say that it's time to go back and double check to make sure the updates
(these specific ones) did this... I'd then also consider rooting about for
driver issues - what drivers (I'd actually start with video on this one I
think) might need to be updated after having done the recent updates at
Microsoft?

So, this is where I'd go if this was on my system. I'd start by going to the
manufacturer's sites and looking for drivers. I guess I'd start with the
video drivers. You mentioned no networking - surely there's some form? Even
if it's just internet - 'tis still a network... Or is this really a
completely disconnected PC without the internet at all? If so is there a NIC
in it? Does the behavior change if you disable the device?

If that's no go then, well, you can try disabling any BIOS caching though
that issue was meant to be fixed in SP3 and tended to show up in multi-CPU
server type computers. It's worth a shot at any rate.

Assuming, and at this point I am, then I'd start removing the most recent
updates. Start by removing all of them. Reboot and try safe mode. Does it
work? No? Then we know it's not the updates? Yes... Well, this is going to
be a lot like fun... Install them one by one until it breaks again. When you
find the one that breaks it you're entitled to free support. Give 'em a
call... <g> Really, at the least let us know what's going on.

I've gone ahead and dug down to the "best" information I could find on the
subject at the Microsoft site. This link should take you there for what it's
worth... (Yes, I have no social life and have no been sitting here typing
this response (though it's not much - most of the time was spent doing
additional searches hoping I'd find something I'd already missed) for a
couple of hours. Feel free to take a look, as it's your system there's a lot
more that might make sense to you than will to me because you'll perhaps
know something about it that I am not aware of.

http://search.microsoft.com/search/...0x0000000A&qp=windows+2000&swc=3&na=33&cm=512

I'm not sure what effect you're going to get with the alternate boot.ini,
I'm glad you were able to remember how to use RC to restore the backup. I
generally make it a point to make a boot.ini backup on any system. I don't
suppose this is that interesting to anyone but a geek but in the process of
searching I did stumble across this site (note that this hasn't a darned
thing to do with your problem but it might give you something to read while
you're fuming) that has managed to make it's way into my bookmarks now:

http://www.dewassoc.com/support/win2000/setupwin2000.htm

Anyhow, I have no social life so don't mind putting in more hours. I'd give
the above a try and see what you come up with.

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

"A man should keep his little brain attic stocked with all the
furniture that he is likely to use, and the rest he can put away in the
lumber-room of his library where he can get it if he wants it."

Sherlock Holmes
 
I'd say that it's time to go back and double check to make sure the updates
(these specific ones) did this... I'd then also consider rooting about for
driver issues - what drivers (I'd actually start with video on this one I
think) might need to be updated after having done the recent updates at
Microsoft?
Click to expand...

Hi Galen,

I asked this over at the Update group and was advised to update my
video driver, only I don't see on the manufacturer's site anything
more recent for my particular video card.

The problem was that after I installed update KB904368, my screen
turned green and it was awful. The following day, I uninstalled that
update and the green persisted through "restart" but then vanished a
moment later.

I have no idea what to do about this. The update icon is sitting in
the system tray, but I don't dare reinstall that update.

I installed a newer video driver (I think) from Microsoft when I was
installing all the updates after a format last January, but I'm not
sure if the older one was uninstalled first - it was an update so I
just installed it.

Another problem I have with the updates is that when I install an
update and it prompts me to restart the computer, my screen eventually
goes black, but then just hangs and I have to shut off the computer
and then turn it back on. So, since then, I've been restarting
*after* refusing that prompt, and that works ok. I asked about this
in the Update group quite awhile ago and no one responded.

Windows 2000 Pro, with all updates and service packs except for the
one I mentioned that turned my screen green.

Thank you for any insight you may be able to offer.

Gail
 
In Jyeshta <[email protected]> had this to say:

My reply is at the bottom of your sent message:
Hi Galen,

I asked this over at the Update group and was advised to update my
video driver, only I don't see on the manufacturer's site anything
more recent for my particular video card.

The problem was that after I installed update KB904368, my screen
turned green and it was awful. The following day, I uninstalled that
update and the green persisted through "restart" but then vanished a
moment later.

I have no idea what to do about this. The update icon is sitting in
the system tray, but I don't dare reinstall that update.

I installed a newer video driver (I think) from Microsoft when I was
installing all the updates after a format last January, but I'm not
sure if the older one was uninstalled first - it was an update so I
just installed it.

Another problem I have with the updates is that when I install an
update and it prompts me to restart the computer, my screen eventually
goes black, but then just hangs and I have to shut off the computer
and then turn it back on. So, since then, I've been restarting
*after* refusing that prompt, and that works ok. I asked about this
in the Update group quite awhile ago and no one responded.

Windows 2000 Pro, with all updates and service packs except for the
one I mentioned that turned my screen green.

Thank you for any insight you may be able to offer.

Gail
Click to expand...

It sounds like there's quite a bit going on with your system so I'll try to
tackle one for you. Depending on the age of the video card it may no longer
be supported. The KB904368 wasn't a security update but rather a problem
fixing update where people were unable to use Office to save to floppy after
the rollup. I'm not sure that would have any impact on graphics but who
knows??? If you don't mind the rather simple workaround... Don't save to
floppy from Office directly. Just save it to disk and then move it to a
floppy. An idea might be to ping the manufacturer's of the card and see what
they have to say about it.

When you get the black screen does it ever reboot or does it just lock up?
My guess would be that there's something conflicting with it - perhaps some
security software - that is getting in the way. What happens if you disable
your anti-virus, anti-trojan, anti-scripting, etc etc etc and then do a
reboot after updating? Does anything show up in the event log when that
happens? I don't suppose we'll know until Patch Tuesday rolls around again
unless you want to try KB904368 again? <g>

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

Please note that if you're reading this in a browser and the domain is
not owned by Microsoft then this work is being used without permission.

Access MS Newsgroups :
http://kgiii.info/windows/all/general/msnewsgroups.html
 
In Jyeshta <[email protected]> had this to say:

My reply is at the bottom of your sent message:


It sounds like there's quite a bit going on with your system so I'll try to
tackle one for you. Depending on the age of the video card it may no longer
be supported. The KB904368 wasn't a security update but rather a problem
fixing update where people were unable to use Office to save to floppy after
the rollup. I'm not sure that would have any impact on graphics but who
knows??? If you don't mind the rather simple workaround... Don't save to
floppy from Office directly. Just save it to disk and then move it to a
floppy. An idea might be to ping the manufacturer's of the card and see what
they have to say about it.
Click to expand...

That's a good idea, about saving to disk, if I'm ever in that
situation. Thank you!
When you get the black screen does it ever reboot or does it just lock up?
Click to expand...

It rebooted once after a very, very long waiting period of maybe 30
minutes. All other times, I've panicked after waiting a comparable
period of time and simply turned the computer off and then back on.
My guess would be that there's something conflicting with it - perhaps some
security software - that is getting in the way. What happens if you disable
your anti-virus, anti-trojan, anti-scripting, etc etc etc and then do a
reboot after updating? Does anything show up in the event log when that
happens? I don't suppose we'll know until Patch Tuesday rolls around again
Click to expand...

These are all good points I hadn't thought of. But before the format
and reinstallation of the OS and all other software, I had much the
same set-up and this "restart hanging" never used to happen before.
But who knows, it could be one of the issues you list above. I don't
know where I'd find anti-scripting, though, unless that's simply
software I don't have installed.
unless you want to try KB904368 again? <g>
Click to expand...

No thank you! <g>

Thank you so much for your reply. Next update, I'll try turning off
my anti-virus and firewall (after disconnecting from the internet) and
see if the prompted "restart" works.

Gail
 
In Jyeshta <[email protected]> had this to say:

My reply is at the bottom of your sent message:

Thank you so much for your reply. Next update, I'll try turning off
my anti-virus and firewall (after disconnecting from the internet) and
see if the prompted "restart" works.

Gail
Click to expand...

Gail,

This looks like one of those long debugging processes. Sometimes it takes
(and I've not a problem with this) a couple of months before it's truthfully
able to be figured out. I've seen threads that lasted a month in even busy
newsgroups. I keep them flagged but you might lose it. http://kgiii.info
(sorta almost like spam I guess but it's not commercial by any means) but
you can find me there or in here when it next crops up if the information
given doesn't fix it. It's worth looking into, the security apps, and a test
of the patch seems to be just a pain in the butt more than it is harmful. I
suppose that might help you speed up the testing process if you want but,
well, as it's not doing anything too major there's no real reason to hurry.


--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

Please note that if you're reading this in a browser and the domain is
not owned by Microsoft then this work is being used without permission.

Access MS Newsgroups :
http://kgiii.info/windows/all/general/msnewsgroups.html
 
In Jyeshta <[email protected]> had this to say:

My reply is at the bottom of your sent message:



Gail,

This looks like one of those long debugging processes. Sometimes it takes
(and I've not a problem with this) a couple of months before it's truthfully
able to be figured out. I've seen threads that lasted a month in even busy
newsgroups. I keep them flagged but you might lose it. http://kgiii.info
(sorta almost like spam I guess but it's not commercial by any means) but
you can find me there or in here when it next crops up if the information
given doesn't fix it. It's worth looking into, the security apps, and a test
of the patch seems to be just a pain in the butt more than it is harmful. I
suppose that might help you speed up the testing process if you want but,
well, as it's not doing anything too major there's no real reason to hurry.
Click to expand...

Hi Galen,

Thanks very much again! Now I'm kind of worried since you said it
might be a very long debugging process. I'm tempted to just keep on
clicking "no" at the restart prompt and then simply doing restart
myself, which so far works okay. Thank you for the link; I'll check
that out now.

Gail
 
Galen,

Thanks for your help. Since my return, I have been reading but not
responding; this is becoming very complicated and overwhelming for me. Once,
in the days of DOS before Win 3.1, things were much simpler. No longer
especial not so with W2K and above.
Daunting as it seems to me, I'll check the sites you mention, and try some
changes.
Your efforts are appreciated. I want to ensure you know this.

Dugie

Galen said:
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:
Galen said:
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:

In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:

In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:

Hi,

I hope someone can help.

Win 2K Pro, SP4.
After installing all 10 of the latest from Win Update, I noticed
that pressing F8 at boot doesn't work. It worked fine before the
updates. Everything else
seems ok.

When pressing F8, at times the screen will flash the Startup
Menu, but the boot continues.

Thanks,
Dugie

What does your boot.ini look like? Copy/paste it into a response
to this if you want.

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

"A man should keep his little brain attic stocked with all the
furniture that he is likely to use, and the rest he can put away
in the lumber-room of his library where he can get it if he
wants it."

Sherlock Holmes
Boot.ini:

[boot loader]
timeout=40
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

Thanks!

Dugie

That looks to be okay by my reckoning? Hmm... Curious... What
happens if you try to force it by editing the boot.ini?

http://support.microsoft.com/?kbid=239780

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

Not sure what can be forced. What would you suggest to forcc?

I visited the http://support.microsoft.com/?kbid=239780 link. It's
not simple. :-) Explanations for the switches are minimal.
I'll try /safeboot:minimal /sos /bootlog /noguiboot and leave
/fastdetect in place. It's a home computer with no networking. Also
backed up my boot.ini file.

Thanks!
Dugie

When you use the sample boot.ini file provided on the page does it
boot into safe mode? I'm basically trying to see what solutions
there are to offer you because, well, I'm not sure of the reason
that this has happened. It's something I've not seen before and when
I try to find an answer for you via the normal search routines I
come up with nothing specific though it could be that I'm just using
flawed search terms. <g>
Click to expand...

Hi Galen,

When I tried the switches above:
/safeboot:minimal /sos /bootlog /noguiboot /fastdetect

I got a blue screen:
STOP: 0x0000000A (0xEB915354,0X000000FF,0x00000001,0x804640791)
IRQL_NOT_LESS_OR_EQUAL
Address 80464079 base at 80400000, Date Stamp 427b58bb - ntoskrnl.exe

Took me a while to remember to use the Recovery Console to ren the
old .ini so I could boot. :-(

My C: drive is a fairly new WD 160GB, so I'm using Western Digital's
Dynamic Drive Overlay v9.85. Using only 128G (binary?), since I don't
trust the overlay... yet. Other drives: 20G & 30G. Machine is 902Mhz.

I'll try the sample file & report results, assuming it's:
[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
Advanced Server" /fastdetect /SAFEBOOT:MINIMAL(ALTERNATESHELL)

I won't be around for a few days.
If an MVP is having problems researching this, I don't feel so badly
about finding no solutions. :-)

Thanks for your suggestions and help!

Dugie
Click to expand...

Hmm... A BSOD... Well that throws a monkey wrench into it.

Here's general information on your error?
http://support.microsoft.com/default.aspx?scid=kb;en-us;130802

I'd say that it's time to go back and double check to make sure the updates
(these specific ones) did this... I'd then also consider rooting about for
driver issues - what drivers (I'd actually start with video on this one I
think) might need to be updated after having done the recent updates at
Microsoft?

So, this is where I'd go if this was on my system. I'd start by going to the
manufacturer's sites and looking for drivers. I guess I'd start with the
video drivers. You mentioned no networking - surely there's some form? Even
if it's just internet - 'tis still a network... Or is this really a
completely disconnected PC without the internet at all? If so is there a NIC
in it? Does the behavior change if you disable the device?

If that's no go then, well, you can try disabling any BIOS caching though
that issue was meant to be fixed in SP3 and tended to show up in multi-CPU
server type computers. It's worth a shot at any rate.

Assuming, and at this point I am, then I'd start removing the most recent
updates. Start by removing all of them. Reboot and try safe mode. Does it
work? No? Then we know it's not the updates? Yes... Well, this is going to
be a lot like fun... Install them one by one until it breaks again. When you
find the one that breaks it you're entitled to free support. Give 'em a
call... <g> Really, at the least let us know what's going on.

I've gone ahead and dug down to the "best" information I could find on the
subject at the Microsoft site. This link should take you there for what it's
worth... (Yes, I have no social life and have no been sitting here typing
this response (though it's not much - most of the time was spent doing
additional searches hoping I'd find something I'd already missed) for a
couple of hours. Feel free to take a look, as it's your system there's a lot
more that might make sense to you than will to me because you'll perhaps
know something about it that I am not aware of.

http://search.microsoft.com/search/...0x0000000A&qp=windows+2000&swc=3&na=33&cm=512

I'm not sure what effect you're going to get with the alternate boot.ini,
I'm glad you were able to remember how to use RC to restore the backup. I
generally make it a point to make a boot.ini backup on any system. I don't
suppose this is that interesting to anyone but a geek but in the process of
searching I did stumble across this site (note that this hasn't a darned
thing to do with your problem but it might give you something to read while
you're fuming) that has managed to make it's way into my bookmarks now:

http://www.dewassoc.com/support/win2000/setupwin2000.htm

Anyhow, I have no social life so don't mind putting in more hours. I'd give
the above a try and see what you come up with.
Click to expand...
 
Galen said:
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:
Galen said:
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:

In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:

In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:

Hi,

I hope someone can help.

Win 2K Pro, SP4.
After installing all 10 of the latest from Win Update, I noticed
that pressing F8 at boot doesn't work. It worked fine before the
updates. Everything else
seems ok.

When pressing F8, at times the screen will flash the Startup
Menu, but the boot continues.

Thanks,
Dugie

What does your boot.ini look like? Copy/paste it into a response
to this if you want.

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

"A man should keep his little brain attic stocked with all the
furniture that he is likely to use, and the rest he can put away
in the lumber-room of his library where he can get it if he
wants it."

Sherlock Holmes
Boot.ini:

[boot loader]
timeout=40
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

Thanks!

Dugie

That looks to be okay by my reckoning? Hmm... Curious... What
happens if you try to force it by editing the boot.ini?

http://support.microsoft.com/?kbid=239780

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

Not sure what can be forced. What would you suggest to forcc?

I visited the http://support.microsoft.com/?kbid=239780 link. It's
not simple. :-) Explanations for the switches are minimal.
I'll try /safeboot:minimal /sos /bootlog /noguiboot and leave
/fastdetect in place. It's a home computer with no networking. Also
backed up my boot.ini file.

Thanks!
Dugie

When you use the sample boot.ini file provided on the page does it
boot into safe mode? I'm basically trying to see what solutions
there are to offer you because, well, I'm not sure of the reason
that this has happened. It's something I've not seen before and when
I try to find an answer for you via the normal search routines I
come up with nothing specific though it could be that I'm just using
flawed search terms. <g>
Click to expand...

Hi Galen,

When I tried the switches above:
/safeboot:minimal /sos /bootlog /noguiboot /fastdetect

I got a blue screen:
STOP: 0x0000000A (0xEB915354,0X000000FF,0x00000001,0x804640791)
IRQL_NOT_LESS_OR_EQUAL
Address 80464079 base at 80400000, Date Stamp 427b58bb - ntoskrnl.exe

Took me a while to remember to use the Recovery Console to ren the
old .ini so I could boot. :-(

My C: drive is a fairly new WD 160GB, so I'm using Western Digital's
Dynamic Drive Overlay v9.85. Using only 128G (binary?), since I don't
trust the overlay... yet. Other drives: 20G & 30G. Machine is 902Mhz.

I'll try the sample file & report results, assuming it's:
[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
Advanced Server" /fastdetect /SAFEBOOT:MINIMAL(ALTERNATESHELL)

I won't be around for a few days.
If an MVP is having problems researching this, I don't feel so badly
about finding no solutions. :-)

Thanks for your suggestions and help!

Dugie
Click to expand...

Hmm... A BSOD... Well that throws a monkey wrench into it.

Here's general information on your error?
http://support.microsoft.com/default.aspx?scid=kb;en-us;130802

I'd say that it's time to go back and double check to make sure the updates
(these specific ones) did this... I'd then also consider rooting about for
driver issues - what drivers (I'd actually start with video on this one I
think) might need to be updated after having done the recent updates at
Microsoft?

So, this is where I'd go if this was on my system. I'd start by going to the
manufacturer's sites and looking for drivers. I guess I'd start with the
video drivers. You mentioned no networking - surely there's some form? Even
if it's just internet - 'tis still a network... Or is this really a
completely disconnected PC without the internet at all? If so is there a NIC
in it? Does the behavior change if you disable the device?

If that's no go then, well, you can try disabling any BIOS caching though
that issue was meant to be fixed in SP3 and tended to show up in multi-CPU
server type computers. It's worth a shot at any rate.

Assuming, and at this point I am, then I'd start removing the most recent
updates. Start by removing all of them. Reboot and try safe mode. Does it
work? No? Then we know it's not the updates? Yes... Well, this is going to
be a lot like fun... Install them one by one until it breaks again. When you
find the one that breaks it you're entitled to free support. Give 'em a
call... <g> Really, at the least let us know what's going on.

I've gone ahead and dug down to the "best" information I could find on the
subject at the Microsoft site. This link should take you there for what it's
worth... (Yes, I have no social life and have no been sitting here typing
this response (though it's not much - most of the time was spent doing
additional searches hoping I'd find something I'd already missed) for a
couple of hours. Feel free to take a look, as it's your system there's a lot
more that might make sense to you than will to me because you'll perhaps
know something about it that I am not aware of.

http://search.microsoft.com/search/...0x0000000A&qp=windows+2000&swc=3&na=33&cm=512

I'm not sure what effect you're going to get with the alternate boot.ini,
I'm glad you were able to remember how to use RC to restore the backup. I
generally make it a point to make a boot.ini backup on any system. I don't
suppose this is that interesting to anyone but a geek but in the process of
searching I did stumble across this site (note that this hasn't a darned
thing to do with your problem but it might give you something to read while
you're fuming) that has managed to make it's way into my bookmarks now:

http://www.dewassoc.com/support/win2000/setupwin2000.htm

Anyhow, I have no social life so don't mind putting in more hours. I'd give
the above a try and see what you come up with.
Click to expand...

Hi Galen,

By installing the Recovery Console on my hd, I now have access to the F8
boot choice menu. It's a workaround for the original problem. :-)
I've updated my video driver (dated 2002) from the manufacture's site. Next
to update are the Realtek RTL8139/810x Family Fast Ethernet NIC, and
Efficient Networks Enternet P.P.P.o.E Adapter. So I do have a network. :-)
My computer and the web.
Also checked those sites you gave, but saw nothing to help. The
setupwin2000.htm page is saved, will take some time to read.

Results so far, using the boot.ini you suggested:
- Safe mode still gives the BSOD, same variables.
- Disabling both CPU Internal & External Caching in the BIOS, Safe mode
starts, then freezes on the "Windows is starting up" screen, after waiting
10 minutes. No BSOD.
- Enabling CPU Cache, disabling only External, Safe Mode starts, then gives
a BSOD.
- Enabling the External Cache, disabling only the CPU Internal cache, Safe
Mode freezes as above on the "Windows is starting up" screen. No BSOD.

I haven't yet tried disabling my NIC.
I'm assuming that getting Safe Mode to work is important.

Dugie

P.S. Can we <snip> some of the older parts of messages on replying?
 
In Dugie <[email protected]> had this to say:

My reply is at the bottom of your sent message:
Hi Galen,

By installing the Recovery Console on my hd, I now have access to the
F8 boot choice menu. It's a workaround for the original problem. :-)
I've updated my video driver (dated 2002) from the manufacture's
site. Next to update are the Realtek RTL8139/810x Family Fast
Ethernet NIC, and Efficient Networks Enternet P.P.P.o.E Adapter. So I
do have a network. :-) My computer and the web.
Also checked those sites you gave, but saw nothing to help. The
setupwin2000.htm page is saved, will take some time to read.

Results so far, using the boot.ini you suggested:
- Safe mode still gives the BSOD, same variables.
- Disabling both CPU Internal & External Caching in the BIOS, Safe
mode starts, then freezes on the "Windows is starting up" screen,
after waiting 10 minutes. No BSOD.
- Enabling CPU Cache, disabling only External, Safe Mode starts, then
gives a BSOD.
- Enabling the External Cache, disabling only the CPU Internal cache,
Safe Mode freezes as above on the "Windows is starting up" screen. No
BSOD.

I haven't yet tried disabling my NIC.
I'm assuming that getting Safe Mode to work is important.

Dugie

P.S. Can we <snip> some of the older parts of messages on replying?
Click to expand...

I don't see why we can't, 'tis our thread... I snip here and there depending
on the importance or likelihood of someone else joining in, seems that no
one's come to rescue me so I'm going to have to say that they're unsure too.
I hate the idea of recommending a repair installation unless you've at least
got SP4 slipstreamed but that's the next logical step other than the one at
the very bottom of this. I suppose you could wait until you absolutely had
to get into safe mode to do it or you could continue using your current
method. It's interesting that when the safe mode was forced that it through
a BSOD and that nothing from the updates did any good. It makes me wonder if
there's an underlying hardware issue that we're overlooking and, to be
honest, unable to diagnose without being able to strip it and test it.

An alternative is to uninstall the updates (one by one) until the problem
goes away but that would just be too logical. Then, when we find out what
the update was that caused it, we can determine if it's something you need
or if there's a work-around for it. Then there's always the big swift boot
right into the side of the tower. While it doesn't often do a lot of good it
is a great way to vent your frustrations.

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/

Please note that if you're reading this in a browser and the domain is
not owned by Microsoft then this work is being used without permission.

Access MS Newsgroups :
http://kgiii.info/windows/all/general/msnewsgroups.html
 
Back
Top