General discussion

Locked

failure to initialize VKD device?

By brucekocher ·
After fdisking,formatting,and reimaging a Toshiba 2590cdt laptop with win98, iI still receive the message."While initializing device VK Windows protection error. You need to restart your computer.An internal stack overflow has caused this session to be halted.Change the STACKS setting in your Config.sys file,and then try again."The curious thing is if I f8 it and choose to boot on bootlog mode the machine seems to work fine until I need to reboot again.

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

failure to initialize VKD device?

by wired_777 In reply to failure to initialize VKD ...

Try renaming smartdrv.exe and rmm.pdr
they are the cause of about 50% of the windows protection errors.
Other causes include:
- A real-mode driver and a protected-mode driver are in conflict.
- The registry is damaged.
- A driver is being loaded from the System.ini file for which a protected-mode driver has already been initialized.
- There is a physical I/O or RAM address conflict.
- There are incorrect CMOS settings for a built-in peripheral device (such as
cache settings, CPU timing, hard disks, and so on).
- The Plug and Play feature of the computer's BIOS is not working correctly.
Good Luck!

Collapse -

failure to initialize VKD device?

by brucekocher In reply to failure to initialize VKD ...

The question was auto-closed by TechRepublic

Collapse -

failure to initialize VKD device?

by moflic In reply to failure to initialize VKD ...

Try oloking at the bootlog file for errors.
Have you tried increasing the stacks in config.sys?
that's:
stacks=9,256
or
stackshigh=9,256 (if you have HMA available)
9=nubmer of stacks
256=bytes allocated for stacks.
increase that, although it may not solve your problem, the error message could be just unrelated to stacks.
try also loading in config.sys:
device=c:\windows\himem.sys /testmem:on

Collapse -

failure to initialize VKD device?

by brucekocher In reply to failure to initialize VKD ...

The question was auto-closed by TechRepublic

Collapse -

failure to initialize VKD device?

by jason.brimhall In reply to failure to initialize VKD ...

Something I have seen associated with this quite often is the msdos.sys file and virtual memory. Try booting a: and then deleting the msdos.sys, resys the drive and then extract vkd.vxd (delete it from the system dir first) from the win98 cab files. Another thing that has worked for me is simply deltreeing the system dir, deltree the reg files and then rerun win98 setup. It might seem like a far shot after and fdisk format reinstall, but I have seen it work (more than likely since the install is not an image of the workstation but the win98 install cd).
I would also del the config.sys and autoexec.bat (at least rename them to something like *.old) as a prelim to the reinstall of win98 and as part of the extracting vkd.vxd from the cab files.

Collapse -

failure to initialize VKD device?

by brucekocher In reply to failure to initialize VKD ...

The question was auto-closed by TechRepublic

Collapse -

failure to initialize VKD device?

by vmm In reply to failure to initialize VKD ...

It is difficult to do with laptop, but try to attach another (external) keyboard or maybe update keyboard driver. I had such a problem before I changed the device.

Collapse -

failure to initialize VKD device?

by brucekocher In reply to failure to initialize VKD ...

The question was auto-closed by TechRepublic

Collapse -

failure to initialize VKD device?

by brucekocher In reply to failure to initialize VKD ...

This question was auto closed due to inactivity

Back to Desktop Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums