Booting Errors List Needed

[mikeeroy@invalid.com]

I just spent half the day trying to get this computer to boot up. It
worked fine yesterday. Today I started it, it booted to DOS (I always
boot to dos because of my dos phone-address book, they type WIN to use
Windows if I want Windows). I'm running Win98se.

Anyhow, I booted to Dos without problem. Everytime I'd type WIN,
Windows started to boot, then said "Windows Protection Error - VKD,
Please Restart Computer" Over and over I did this. I unplugged it
for awhile thinking it needed a reset. I changed the CMOS to the
Default settings, I booted from a floppy, no matter what I did,
everytime I tried to start Windows, I got this error.

By this time I thought my motherboard had fried, and suspected the
built-in video card (the V in VKD meaning Video), or else windows lost
it's registry files. One of the restore floppy files said the
registry was ok, Using a couple old dos diagnostic utilities I had in
my archives, everything looked fine with the motherboard and drives. I
finally decided it was time to reinstall Windows. I reinstalled it
right on top of itself, only to find the same error message when it
restarted.

Of course this whole time I can not go online to find out what the
f**k VKD means.

Just about the time I was ready to go dig out an old 386 computer I
got in the garage, I decided to run another of those Dos utilities
after booting from an old (pre-win98) version of dos. That's when it
said KEYBOARD ERROR. Sure enough..... The ZERO KEY on the numeric
keypad was stuck down...... As soon as I unstuck it, everything
worked fine again.....

I guess I need a new keyboard, but why must windows give such a stupid
error message. Why cant it just say KEYBOARD ERROR. I could have
solved this in minutes. VKD is not even close.... Even if it just
said KEY, or something that made logical sense.....

Anyhow, before this sort of thing happens again, and drives me
bonkers, is there a place where I can download the text of ALL bootup
error abbreviations and print them, so I have them the next time?
Obviously MS cant understand simple plain English, so I need a "cheat
sheet" to keep handy....

What's odd about this whole thing is that Dos worked fine with that
stuck key, but not Windows. I was using my Dos phone-address book
with no trouble. I could not get Windows into Safe Mode though, since
that "0" apparently went to the default.

At least it works again, but wasting half the day on this was most
irritating.

If anyone knows where to find an online list of these error codes to
print out, please tell me.

Thanks

Mike

 

[Franc Zabkar]

On Sun, 30 Mar 2008 00:15:20 -0500, mikeeroy@invalid.com put finger to
keyboard and composed:

>I just spent half the day trying to get this computer to boot up. It
>worked fine yesterday. Today I started it, it booted to DOS (I always
>boot to dos because of my dos phone-address book, they type WIN to use
>Windows if I want Windows). I'm running Win98se.
>
>Anyhow, I booted to Dos without problem. Everytime I'd type WIN,
>Windows started to boot, then said "Windows Protection Error - VKD,
>Please Restart Computer" Over and over I did this. I unplugged it
>for awhile thinking it needed a reset. I changed the CMOS to the
>Default settings, I booted from a floppy, no matter what I did,
>everytime I tried to start Windows, I got this error.
>
>By this time I thought my motherboard had fried, and suspected the
>built-in video card (the V in VKD meaning Video), or else windows lost
>it's registry files. One of the restore floppy files said the
>registry was ok, Using a couple old dos diagnostic utilities I had in
>my archives, everything looked fine with the motherboard and drives. I
>finally decided it was time to reinstall Windows. I reinstalled it
>right on top of itself, only to find the same error message when it
>restarted.
>
>Of course this whole time I can not go online to find out what the
>f**k VKD means.
>
>Just about the time I was ready to go dig out an old 386 computer I
>got in the garage, I decided to run another of those Dos utilities
>after booting from an old (pre-win98) version of dos. That's when it
>said KEYBOARD ERROR. Sure enough..... The ZERO KEY on the numeric
>keypad was stuck down...... As soon as I unstuck it, everything
>worked fine again.....

Normally the BIOS POST will detect a stuck key, but maybe you have it
set to continue on error.

>I guess I need a new keyboard, but why must windows give such a stupid
>error message. Why cant it just say KEYBOARD ERROR. I could have
>solved this in minutes. VKD is not even close.... Even if it just
>said KEY, or something that made logical sense.....
>
>Anyhow, before this sort of thing happens again, and drives me
>bonkers, is there a place where I can download the text of ALL bootup
>error abbreviations and print them, so I have them the next time?
>Obviously MS cant understand simple plain English, so I need a "cheat
>sheet" to keep handy....
>
>What's odd about this whole thing is that Dos worked fine with that
>stuck key, but not Windows. I was using my Dos phone-address book
>with no trouble. I could not get Windows into Safe Mode though, since
>that "0" apparently went to the default.

Was the Numlock status on or off? If off, then your "0" key would have
been interpreted as Insert. In fact I am holding down the Insert key
while typing this sentence.

>At least it works again, but wasting half the day on this was most
>irritating.
>
>If anyone knows where to find an online list of these error codes to
>print out, please tell me.
>
>Thanks
>
>Mike

VKD is a "static" keyboard driver that is loaded from system.ini.

Go to Start > Run and type "msinfo32".

Then expand Software Environment > Drivers > Kernel Drivers and look
for "VKD" in the Driver column in the right hand pane.

You could also go to Start > Run and type "sysedit". Then look for
"vkd" in system.ini.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

 

[Franc Zabkar]

On Sun, 30 Mar 2008 18:15:16 +1000, Franc Zabkar
<fzabkar@iinternode.on.net> put finger to keyboard and composed:

>Normally the BIOS POST will detect a stuck key, but maybe you have it
>set to continue on error.

I just had a thought that maybe the Insert key is a special code that
is interpreted by the BIOS POST.

For example, my old socket 7 PCchips M571 V70A motherboard's AMI BIOS
documentation states that holding down the <Home> key before powering
on is required "if using SDRAM of 2T CAS latency". The <End> key can
be used to clear the CMOS RAM when rebooting after a BIOS flash.

Holding down the <INSert> key while booting prints a detailed BIOS ID
at the bottom of the POST screen, as follows:

51-0421-001437-00101111-071595-M571-007_66_M571-H
000-0-0000-00-00-0000-00-00-000
000-0-0000-00-00-0000-00-00-00-0-000000003FC91010 INT13-1.2
Cr-6.26.00 CPU-3.03 DIM-1.80 GPC-1.11 APM1.2-1.11 USB-1.02 IO-1.09

The AMI site does not appear to have any info on these strings.

I'm guessing that INT13, Cr(?), CPU, DIM(?), GPC(?), APM, USB, and IO
refer to the various code modules within the BIOS. For example, I
suspect that the revision number (1.2) of the INT13 module would
indicate the level of LBA support for HDs.

Maybe the above explains why your BIOS POST didn't complain about a
stuck 0/Insert key. Then again, maybe the BIOS treats the
single-function Insert key differently to the dual function 0/Ins key
???

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

 

[philo]

"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
news:rlluu3h9n75u4oi2haobp42ope8i18fg63@4ax.com...
> On Sun, 30 Mar 2008 18:15:16 +1000, Franc Zabkar
> <fzabkar@iinternode.on.net> put finger to keyboard and composed:
>
> >Normally the BIOS POST will detect a stuck key, but maybe you have it
> >set to continue on error.
>
> I just had a thought that maybe the Insert key is a special code that
> is interpreted by the BIOS POST.
>
> For example, my old socket 7 PCchips M571 V70A motherboard's AMI BIOS
> documentation states that holding down the <Home> key before powering
> on is required "if using SDRAM of 2T CAS latency". The <End> key can
> be used to clear the CMOS RAM when rebooting after a BIOS flash.
>
> Holding down the <INSert> key while booting prints a detailed BIOS ID
> at the bottom of the POST screen, as follows:
>
> 51-0421-001437-00101111-071595-M571-007_66_M571-H
> 000-0-0000-00-00-0000-00-00-000
> 000-0-0000-00-00-0000-00-00-00-0-000000003FC91010 INT13-1.2
> Cr-6.26.00 CPU-3.03 DIM-1.80 GPC-1.11 APM1.2-1.11 USB-1.02 IO-1.09
>
> The AMI site does not appear to have any info on these strings.
>
> I'm guessing that INT13, Cr(?), CPU, DIM(?), GPC(?), APM, USB, and IO
> refer to the various code modules within the BIOS. For example, I
> suspect that the revision number (1.2) of the INT13 module would
> indicate the level of LBA support for HDs.
>
> Maybe the above explains why your BIOS POST didn't complain about a
> stuck 0/Insert key. Then again, maybe the BIOS treats the
> single-function Insert key differently to the dual function 0/Ins key
> ???
>
> - Franc Zabkar
>

In the bios there is generally a choice to either:

stop on all errors (or)

stop on no errors


So if the bios was set to "stop on no errors" the keyboard error would not
have prevented
bootup.

I once had a similar thing happen on a win98 machine when someone spilled
their softdrink into the keyboard
but only told me : the computer does not boot up.

The machine started to boot...but would crash somewhere into the boot
process...or shortly thereafter

Eventually , when I picked up the KB and saw all the soda spilling out...I
figured it out.

The bios was set to : stop on no errors


I now see the wisdom of having the bios set to : stop on all errors

as the error can be corrected prior to even having windows load

 

[Bill in Co.]

philo wrote:
> "Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
> news:rlluu3h9n75u4oi2haobp42ope8i18fg63@4ax.com...
>> On Sun, 30 Mar 2008 18:15:16 +1000, Franc Zabkar
>> <fzabkar@iinternode.on.net> put finger to keyboard and composed:
>>
>>> Normally the BIOS POST will detect a stuck key, but maybe you have it
>>> set to continue on error.
>>
>> I just had a thought that maybe the Insert key is a special code that
>> is interpreted by the BIOS POST.
>>
>> For example, my old socket 7 PCchips M571 V70A motherboard's AMI BIOS
>> documentation states that holding down the <Home> key before powering
>> on is required "if using SDRAM of 2T CAS latency". The <End> key can
>> be used to clear the CMOS RAM when rebooting after a BIOS flash.
>>
>> Holding down the <INSert> key while booting prints a detailed BIOS ID
>> at the bottom of the POST screen, as follows:
>>
>> 51-0421-001437-00101111-071595-M571-007_66_M571-H
>> 000-0-0000-00-00-0000-00-00-000
>> 000-0-0000-00-00-0000-00-00-00-0-000000003FC91010 INT13-1.2
>> Cr-6.26.00 CPU-3.03 DIM-1.80 GPC-1.11 APM1.2-1.11 USB-1.02 IO-1.09
>>
>> The AMI site does not appear to have any info on these strings.
>>
>> I'm guessing that INT13, Cr(?), CPU, DIM(?), GPC(?), APM, USB, and IO
>> refer to the various code modules within the BIOS. For example, I
>> suspect that the revision number (1.2) of the INT13 module would
>> indicate the level of LBA support for HDs.
>>
>> Maybe the above explains why your BIOS POST didn't complain about a
>> stuck 0/Insert key. Then again, maybe the BIOS treats the
>> single-function Insert key differently to the dual function 0/Ins key
>> ???
>>
>> - Franc Zabkar
>>
>
> In the bios there is generally a choice to either:
>
> stop on all errors (or)
>
> stop on no errors
>
> So if the bios was set to "stop on no errors" the keyboard error would not
> have prevented bootup.
>
> I once had a similar thing happen on a win98 machine when someone spilled
> their softdrink into the keyboard
> but only told me : the computer does not boot up.
>
> The machine started to boot...but would crash somewhere into the boot
> process...or shortly thereafter
>
> Eventually , when I picked up the KB and saw all the soda spilling out...I
> figured it out.
>
> The bios was set to : stop on no errors
>
> I now see the wisdom of having the bios set to : stop on all errors
>
> as the error can be corrected prior to even having windows load

Some BIOS's have another option - to stop on all errors but keyboard, too.

 

[mikeeroy@invalid.com]

On Sun, 30 Mar 2008 15:22:47 -0500, "philo" <philo@privacy.net> wrote:

>
>"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
>news:rlluu3h9n75u4oi2haobp42ope8i18fg63@4ax.com...
>> On Sun, 30 Mar 2008 18:15:16 +1000, Franc Zabkar
>> <fzabkar@iinternode.on.net> put finger to keyboard and composed:
>>
>> >Normally the BIOS POST will detect a stuck key, but maybe you have it
>> >set to continue on error.
>>
>> I just had a thought that maybe the Insert key is a special code that
>> is interpreted by the BIOS POST.
>>
>> For example, my old socket 7 PCchips M571 V70A motherboard's AMI BIOS
>> documentation states that holding down the <Home> key before powering
>> on is required "if using SDRAM of 2T CAS latency". The <End> key can
>> be used to clear the CMOS RAM when rebooting after a BIOS flash.
>>
>> Holding down the <INSert> key while booting prints a detailed BIOS ID
>> at the bottom of the POST screen, as follows:
>>
>> 51-0421-001437-00101111-071595-M571-007_66_M571-H
>> 000-0-0000-00-00-0000-00-00-000
>> 000-0-0000-00-00-0000-00-00-00-0-000000003FC91010 INT13-1.2
>> Cr-6.26.00 CPU-3.03 DIM-1.80 GPC-1.11 APM1.2-1.11 USB-1.02 IO-1.09
>>
>> The AMI site does not appear to have any info on these strings.
>>
>> I'm guessing that INT13, Cr(?), CPU, DIM(?), GPC(?), APM, USB, and IO
>> refer to the various code modules within the BIOS. For example, I
>> suspect that the revision number (1.2) of the INT13 module would
>> indicate the level of LBA support for HDs.
>>
>> Maybe the above explains why your BIOS POST didn't complain about a
>> stuck 0/Insert key. Then again, maybe the BIOS treats the
>> single-function Insert key differently to the dual function 0/Ins key
>> ???
>>
>> - Franc Zabkar
>>
>
>In the bios there is generally a choice to either:
>
>stop on all errors (or)
>
>stop on no errors
>
>
>So if the bios was set to "stop on no errors" the keyboard error would not
>have prevented
>bootup.
>
>I once had a similar thing happen on a win98 machine when someone spilled
>their softdrink into the keyboard
>but only told me : the computer does not boot up.
>
>The machine started to boot...but would crash somewhere into the boot
>process...or shortly thereafter
>
>Eventually , when I picked up the KB and saw all the soda spilling out...I
>figured it out.
>
>The bios was set to : stop on no errors
>
>
>I now see the wisdom of having the bios set to : stop on all errors
>
>as the error can be corrected prior to even having windows load
>

Thanks to everyone that replied. I dont see anything in my bios
settings to change this. This is an IBM Net Vista computer, and the
bios settings are few. I never knew the "0" key was also INSERT. But
now that it was mentioned, it does say "ins" on it. I rarely ever use
the numeric keys, which is probably why that key was sticking. Rather
than buy a new keyboard, I took this one to the garage and blew my air
compressor around the keys. Seems to be ok now.

I did the start / run / msinfo32.
I never knew that command existed. There is a lot of information in
there. I am getting an error. Under "problem devices". It says the
following. What does this mean? I do know that the ide controllers
are for the drives. I have two hard drives installed on the first
controller as Master and Slave. I dont normally have anything on the
secondary, but occasionally plug a 3rd hard drive in there to do
backups, then remove it when I finish. There was a CD drive connected
to that, but I unplugged it since I have a portable, external USB Cd
drive player. I dont have a burner.

Here's the error message....

Secondary IDE controller (dual fifo)
hdc
This Device Has a Problem: Code=29 (0x1D)
This device has been disabled in the hardware. In order to use
this device,
you must re-enable the hardware. See your hardware documentation for
details.
Alloc resources: Logical Configuration
0
Driver: ESDI_506.pdr
4/23/1999 10:22 PM Size: 24406

 

[MEB]

There are a number of sites which provide lists of errors, REAL errors.

Try to find these on Microsoft support:
Q125174
Q74463
Q76922
Q99415

So how about a list which displays what may be in your mind WHEN they occur.

--------
Recently the following undocumented error-codes were found.
Microsoft forgot to explain them in the manuals, so they will be spread via
the internet:

Error Description
001 Windows loaded - System in danger.
002 No Error - Yet.
003 Dynamic linking error - Your mistake is now in every file.
004 Erroneous error - Nothing is wrong.
005 Multitasking attempted - System confused.
006 Malicious error - Desqview found on drive.
007 System price error - Inadeqaute money spent on hardware.
008 Broken window - Watch out for glass fragments.
009 Horrible bug encountered - God knows what has happened.
00A Promotional literature overflow - Mailbox full.
00B Inadeqaute disk space - Free at least 500MB.
00C Memory hog error - More Ram needed. More! More! More!
00D Window closed - Do not look outside.
00E Window open - Please close.
00F Unexplained error - Please tell us how this happened.
010 Reserved for future mistakes by our developers.
011 Window open - Do not look outside.
012 Window closed - Do not look inside.
013 Unexpected error - Huh ?
014 Keyboard locked - Try anything you can think of.
018 Unrecoverable error - System has been destroyed. Buy a new one. Old
windows licence is not valid anymore.
019 User error - Not our fault. Is Not! Is Not!
01A Operating system overwritten - Please reinstall all your software. We
are terribly sorry.
01B Illegal error - You are not allowed to get this error. Next time you
will get a penalty for that.
01C Uncertainty error - Uncertainty may be inadeqaute.
01D System crash - We are unable to figure out our own code.
01E Timing error - Please wait. And wait. And wait. And wait.
01F Reserved for future mistakes of our developers.
020 Error recording error codes - Remaining errors will be lost.
021 Virus error - A virus has been activated in a dos-box. The virus,
however, requires Windows. All tasks will automatically be closed and the
virus will be activated again.
079 Mouse not found - A mouse driver has not been installed. Please click
the left mouse button to continue.
103 Error buffer overflow - Too many errors encountered. Next errors will
not be displayed or recorded.
678 This will end your Windows session. Do you want to play another game?
783 Time out error - Operator fell asleep while waiting for the system to
complete boot procedure.
815 Insufficient Memory - Only 50,312,583 Bytes available

--
MEB http://peoplescounsel.orgfree.com
--
_________

<mikeeroy@invalid.com> wrote in message
news:a67uu3h2crnsm4lu1c1j0jifketo4ch47o@4ax.com...
| I just spent half the day trying to get this computer to boot up. It
| worked fine yesterday. Today I started it, it booted to DOS (I always
| boot to dos because of my dos phone-address book, they type WIN to use
| Windows if I want Windows). I'm running Win98se.
|
| Anyhow, I booted to Dos without problem. Everytime I'd type WIN,
| Windows started to boot, then said "Windows Protection Error - VKD,
| Please Restart Computer" Over and over I did this. I unplugged it
| for awhile thinking it needed a reset. I changed the CMOS to the
| Default settings, I booted from a floppy, no matter what I did,
| everytime I tried to start Windows, I got this error.
|
| By this time I thought my motherboard had fried, and suspected the
| built-in video card (the V in VKD meaning Video), or else windows lost
| it's registry files. One of the restore floppy files said the
| registry was ok, Using a couple old dos diagnostic utilities I had in
| my archives, everything looked fine with the motherboard and drives. I
| finally decided it was time to reinstall Windows. I reinstalled it
| right on top of itself, only to find the same error message when it
| restarted.
|
| Of course this whole time I can not go online to find out what the
| f**k VKD means.
|
| Just about the time I was ready to go dig out an old 386 computer I
| got in the garage, I decided to run another of those Dos utilities
| after booting from an old (pre-win98) version of dos. That's when it
| said KEYBOARD ERROR. Sure enough..... The ZERO KEY on the numeric
| keypad was stuck down...... As soon as I unstuck it, everything
| worked fine again.....
|
| I guess I need a new keyboard, but why must windows give such a stupid
| error message. Why cant it just say KEYBOARD ERROR. I could have
| solved this in minutes. VKD is not even close.... Even if it just
| said KEY, or something that made logical sense.....
|
| Anyhow, before this sort of thing happens again, and drives me
| bonkers, is there a place where I can download the text of ALL bootup
| error abbreviations and print them, so I have them the next time?
| Obviously MS cant understand simple plain English, so I need a "cheat
| sheet" to keep handy....
|
| What's odd about this whole thing is that Dos worked fine with that
| stuck key, but not Windows. I was using my Dos phone-address book
| with no trouble. I could not get Windows into Safe Mode though, since
| that "0" apparently went to the default.
|
| At least it works again, but wasting half the day on this was most
| irritating.
|
| If anyone knows where to find an online list of these error codes to
| print out, please tell me.
|
| Thanks
|
| Mike
|