Newsgroup: it.aiuto
Titolo: Aiuto per file VXD

Nell'aprire il computer dopo aver fatto il check e sta per caricare i
vari driver, win98 mi dice che si trova in errore di protezione sul
file "vftd.vxd". qualcuno puo' aiutarmi a capire cosa e' questo file e
come si puo' ripristinare senza riformattare?

vi...@dmail.it
 ha scritto:

 Il file vftd.vxd non e' un file di windows..
 L'unico riferimento che ho trovato e' ad un programma di protezione dei
 files di nome File Protector..
  L'avevi per caso installato?
 
 Ciao.
-- 
                    dubium sapientiae initium

 come si puo' ripristinare senza riformattare?
ho avuto un problema simile che ho risolto facendo un semplice scandisk.
e' un problema abbastanza comune e documentato.
ti lascio le istruzioni che ho trovato su un sito sui "tricks and tips"
di windows 98:
---------------------------------------------------
Have you ever got a "VxD error" message while starting Windows 98 or 98
SE? It's pretty much "fatal", and automatically returns you to the DOS
prompt. :
Especially if you upgraded to Win98 from Win95 or OSR2, since some old
32-bit protected virtual drivers might have "survived" the upgrade. The
MS Windows 98 Resource Kit Help file (Win98rk.hlp, found in the
\Tools\Reskit\Help folder on the Win98 Setup cd-rom) states that:
"If a virtual device driver (VxD) is missing or damaged, Windows 98
displays an error message that indicates which VxD is involved. If the
VxD is critical to the operation of Windows 98, then Windows 98 does not
start and the screen displays the command prompt. You might need to run
Windows 98 Setup and select Verify or Safe Recovery to replace the
missing VxD."
But there is an easier solution to this problem. The generic driver
Vmm32.vxd (located in C:\Windows\System) was built when you first
installed Win98 on your computer. Depending on your hardware specs, it
may contain some or all of the following VXDs (Virtual eXtended
Drivers):
biosxlat.vxd, configmg.vxd, dynapage.vxd, ebios.vxd, enable.vxd,
ifsmgr.vxd, int13.vxd, ios.vxd, parity.vxd, reboot.vxd, vcache.vxd,
vcd.vxd, vcomm.vxd, vcond.vxd, vdd.vxd, vdef.vxd, vfat.vxd,
vfbackup.vxd, vflatd.vxd, vkd.vxd, vmcpd.vxd, vmouse.vxd, vmpoll.vxd,
vpd.vxd, vsd.vxd, vtdapi.vxd, vwin32.vxd, vxdldr.vxd. Vmm32.vxd is not
only slow to load (because of its huge size), but if you have
added/changed your hardware devices after installing Win98, this old
driver might not match your system specs anymore. Certain system errors,
like random lockups, error messages at startup, VMM errors, erratic
and/or slow mouse movement etc, might be resolved by selectively
overriding a VXD included within Vmm32.vxd.
EXTRACT /Y /A D:\WIN98\BASE4.CAB VCOMM.VXD
to extract VCOMM.VXD to the current directory. Typing in the first .CAB
file name in a given folder (in this case BASE4.CAB), forces EXTRACT.EXE
to search all CABs in the same directory for the file you specify.
Change the cd-rom drive letter if different on your system. Now move
VCOMM.VXD to C:\Windows\System\Vmm32, and reboot.
From now on Win98 will use the individual VXD instead of the one
contained in Vmm32.vxd, because if the same VXD loads twice, the second
instance (in this case the one in C:\Windows\System\Vmm32) intercepts
all the calls to that particular VXD. Alternatively you can edit
System.ini (located in your Windows folder) using Notepad, and add an
entry for the VXD you know creates "problems", under the [386enh]
section. Example:
device=vcomm.vxd
VXDs known to generate error messages more frequently are: configmg.vxd,
ntkern.vxd, vcomm.vxd, vdd.vxd, vdmad.vxd, vflatd.vxd and vmouse.vxd.
You can also check which VXDs are used in Vmm32.vxd on your Win98
computer by running Control Panel -> System -> Device Manager tab ->
Your device name -> Driver tab -> Driver File Details button, and look
for all drivers that have VMM32 in parenthesis after their filenames.
Example:
C:\WINDOWS\SYSTEM\VCOMM.VXD (VMM32)
Check all items on your Device Manager list for similar drivers and
write down their names. Extract them to C:\Windows\System\Vmm32 and then
reboot. Now go back into Device Manager, and check again for the same
drivers. You'll notice that all (VMM32) instances after the driver
filenames are gone. UPDATES: - Run VXD_FIX.BAT [27 KB, free] to copy all
necessary VXD files from your Win98 Setup cd-rom to your
C:\Windows\System\Vmm32 folder:
- Read this "VMM32.VXD" page for more details:
http://windows-help.net/windows98/vmm32.shtml
 
-----------------------------------------------------------------
spero di esserti stata di aiuto
Alo!