Discussion Locked

Can't replace the missing VXD files.

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have an old IBM ThinkPad with an installed Win98 OS. Now my problem is, upon boot-up, it displays a few missing VXD files like DFS, VNETSUP and VREDIR. I suspected some device drivers that I installed so I removed them from my system, but no effect. I used to copy the missing files from the other desktop computer to my laptop but it displays an error message of "Cannot make a directory entry (Error #52). My second option is to re-install the OS but still it doesn't work because of a "SUWIN Error". Third, I've done also the Direct Cable Connection to back-up first my files before re-formatting the drive as my last option but I can't installed the needed files from my OS because of the Error #52 again. Does anybody here knows a solution 'bout my problem? please help me guys. Acctually I can't find also the exact key to enter the CMOS. I acquired this laptop from a surplus shop. Thanks a lot guys.

6 replies

by sgt_shultz

those missing files error are from a network card installation. try reinstalling the (any) nic if you can. or try installing removing and reinstalling all network services and protocols. maybe you removed nic from device manager but not from network configuration but not from network properties, see? (control panel/network)
try removing stuff in safe mode. boot in safe mode and get rid of any 'phantom' devices that show up in Device Manager only in safe mode. if still have problem do step by step confirmation boot up and note where missing files are being sought. remove references (probably in system.ini). if still error, sounds like registry goobered. sometimes shutting down normally from safe mode will repair registry stuff otherwise look into repairing corrupt registry via microsoft export/import method or buy 'registry healer' for ~$15
give the make and model of laptop (if it has one! give BIOS number if that is all you can find) and the wiz's here will help you get into BIOS
things to try for entering bios: after boot, control-s or control-z. at prompt during boot, f1, f10, del, try each f-key. some brands (namely compaq), may need setup diskette, they don't have normal BIOS setup, see? see mfg website for setup diskette.

by jtpaderes

i already remove all that pertains to my NEC card, but it all re-apperas again. Your right that the F1 key is the key to enter the CMOS, but this should be done during a complete reboot, not by just pressing the Ctrl-Alt-Del key. Thanks..

by curacao_dejavu

Hi,

First record all networksettings that you have, (all the client and protocols that you are using).
next remove them all. reboot the machine, and then install them back again. (you will need the windows cd)

next problem:
the su-win driver error that you are receiving is because windows is not recognizng the cdrom when installing from it.

so to reinstall it you need a bootable diskette thats boot with a cdrom (bootdisk.com) use the win98 one, use that to boot from it, format the c-drive, than make a directory on the cd drive and copy the win98 folder to the c-drive (i always use c:\win98 it's easy to remember) .
restart the pc again with the bootfloppy , but use "boot windows without cdrom support this time"
then change to the c:\win98 folder, and start the setup.

That's it.

IBM keys to enter cmos should be f2, f1, or f10.

Leopold
Leopold

by jtpaderes

i already remove all that pertains to my NEC card, but it all re-apperas again. The SUWIN is from the deffective Memory/RAM. Your right that the F1 key is the key to enter the CMOS, but this should be done during a complete reboot, not by just pressing the Ctrl-Alt-Del key. Anyway Thank you very much..

by wcp

Problem #1:
This usually occurs when uninstalling a NIC (in your case, probably PCMCIA) drive did not go well.
To resolve the problem, you need to remove and reinstall ?Client for Microsoft Network? from Network Neighborhood. Copying or extracting those files does not work.

Problem #2:
This error message typically appears while installing OS because of faulty RAM. Your option is to replace the RAM with a known good one and try again.

Problem #3:
Like you said, you want to resolve the problem #1 so you can backup your data before reinstalling Windows 98

This discussion is closed to new replies.