A file specified in the System.ini is damaged

[Shaku]

When I turn on my computer, before everything fully loads, I get this message:
"A device file specified in the SYSTEM.INI file is damaged.
It may be needed to run Windows.

you may need to run then Windows Setup Program again.
If the file is included in another software package, you may need to reinstall the software that uses the file.
VTD
Press a key to continue"

The probem is that when I do hit a key the comp reboots itself and does the same thing over and over. I'm running Windows ME.

[T-32]

sounds like a vxd error to me... sometimes when programs or devices bundled software are uninstalled.. Not everything us uninstalled and references to vxd, or (virtual device drivers), are left behind. Go over your system ini and remove any references to any programs or bundled software you have deleted lately.. As always back up system ini, and don't delete just rem the line out.. see if this helps,,, to get passed the point of reboot boot to safe mode and choose to load all drivers manually... when you get to the vxd reference that is stalling you.. don't load it... this should get you into safe mode.. good luck T-32

[Steve R Jones]

Generally speaking, this happens when you manually delete a program instead of uninstalling it.

You're going to need a startup disk. Do you have one?

[techless77]

try to boot the computer step by step it will hang on the line with the corrupted .vxd file. Once you have the file name you can use
start/run/sfc to extract a copy of the file from a .cab file or find it
at driverguide.com.


Have a blessed day!

[Shaku]

I do have a startup disk actually. If it helps thank God I made one.

[John Prophet]

Have you downloaded or installed anything recently..or uninstalled??

Have you messed with any networking stuff? Like changing Dial up providers or going from broadband to dialup??

I ask this because I often see these errors relating to "client for microsoft networks".

What is the name of the file it is listing? Is it called "vtd"??? Never heard of that one.

Id try to boot to safe mode and then go to the C:\system.ini file and have a look and see if you see the file mentioned....then just type rem in front of it. That will disable it without deleting it etc.

Then reboot and if all is normal you are ok.

JP

[Shaku]

Well...it's kinda hard to explain, but here goes. I was logged on AIM and MSN (if that makes a difference) running mIRC, and at mircscripts.org I think it was. I was downloading an addon for IRC and RIGHT after it finished downloading the comp crashed. (I've had COX Cable for about a year) The "System.ini message" started appearing after that.

[Shaku]

Well...it's kinda hard to explain, but here goes. I was logged on AIM and MSN (if that makes a difference) running mIRC, and at mircscripts.org I think it was. I was downloading an addon for IRC and RIGHT after it finished downloading the comp froze. The "System.ini message" started appearing after that.

The name of the file is "VTD". (Would that be a nickname/acronym for the problem file?) The message also pops up after I try to boot up in Safe Mode.

[John Prophet]

Can you just use WinME restore to go back to b4 the incident?

JP

[John Prophet]

or else just do this.

make a boot floppy....put "scanreg.exe" on it.

boot to floppy, run "scanreg/ restore" and restore back to earlier backup. It keeps like 5 registry backups from previous succesful boots.

If the WinMe bootdisk is too full, you might have to borrow a w98 bootdisk or just boot to your ME floppy and delete some stuff off of it to make room for scanreg.

Then again I guess you can just boot off the stock WinMe bootdisk, then navigate to c:\windows\command folder and run "scanreg /restore"

or you might HAVE to copy it to the floppy, I cant remember.

JP