Content-Transfer-Encoding: |
7bit |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Wed, 12 Jan 2000 06:04:34 -0800 |
Content-Type: |
text/plain; charset="iso-8859-1" |
MIME-Version: |
1.0 |
Reply-To: |
|
Parts/Attachments: |
|
|
Usually removing a protocol from Network Settings will also remove 16 and
32-bit commands from your System.ini; however, your system probably hung
after you asked the computer to restart or some other malady occured.
Use the sysedit command from the start button RUN command and then go to
your system.ini file and edit out the banyan command.
You'll probably see something like this:
[386Enh]
mouse=*mickey.mouse
device=z:vvinesd.386
device=lockme.up
NOTE: to disable a command in the INI files, place a semi-colon to the
left of the command ----
; device=z:vvinesd.386 <----- like that and then save your
changes
If the error reappears after rebooting go to your system registry through
the REGEDIT command and do a "hunt and destroy" mission on every instance of
"z:vvinesd.386."
Hope this helps!
--gary r. tennesen
[log in to unmask]
[log in to unmask]
----- Original Message -----
From: Mary-Belle Simmons <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, January 11, 2000 7:53 PM
Subject: [PCBUILD] Error message on boot/reboot
> Hello again, everyone. In trying to follow everyone's advice (before
> subscribing to this mailing list) for a Direct Cable Connection, I tried
>
> various protocols in my Windows>Settings>Network. I was having trouble
> with my internet connection, and tech support instructed me to remove
> most all of the protocols, including Banyan. I did this, but am now
> getting an error message on reboot or cold boot that reads as follows:
>
> "Cannot find a device file that may be needed to run Windows or a
> Windows application.
>
> The Windows registry or SYSTEM.INI file refers to this device file but
> the device file no longer exists.
>
> If you deleted this file on purpose, try uninstalling the associated
> application using its uninstall or setup program.
>
> If you still want to use the application associated with this device
> file try reinstalling that application to replace the missing file
>
> z:vvinesd.386
>
The PCBUILD web site always needs good submissions. If
you would like to contribute to the website, send any
hardware tech tips or hardware reviews to:
[log in to unmask]
|
|
|