Probs w/ system.ini & win registry...HELP!!

b20uvkft6m5xwg

A few months back I decided to try to install a home network using my current and retired(!!) pc's. I was referred to the MSDN guide to home networking and thus embarked...

However owing to some crappy instructions on the MSDN site, things did not go that well. Anyway I decided not to go through w/ the whole thang!

But...
Since I removed the network login options @ startup etc. I keep getting this message @ startup requiring me to hit return to allow the machine to continue to load...

Cannot find device needed to run windows or win application
The Windows Registry or System.ini file refers to this device but the file no longer exists.
If you want to continue using this application, uninstall or reinstall it.
z:vvinesd.386

Press any key to continue

I'm using win98-SE and I have checked the system.ini & registry by running MSCONFIG but I haven't been able to see if there is anything wrong. Is there, like w/ the device manager any tell-tale signs like Yellow question marks ??
I'm reluctant to edit the system or regedit w/out knowing exactly what I want to delete.

If anyone knows anything I can do could you let me know please. I've also tried using Norton's Clean Sweep but his has done nothing.
Please Help

---

80p.
SAVE CHIP !!

seamus

OK....You've probably tried all of this but..

Step 1. Go to Control Panel --> Add/Remove Programs and check for the device's program. If it's still there - remove it! if no joy..

Step 2. Go to your Device manager. Anything not working will have a teeny-weeny(I swear it's tiny!!) yellow circle + ! in the bottom left-hand corner of its icon. Check it out. Delete if neccessary. else {

Step 3. Open your system.ini file and/or registry and search for this 'vvinesd.386'. Only delete references here if you know exactly what you are doing.

If all else fails, upload your system.ini, and give us all a goo. Dat's all I can suggest

---

When I was young, I dreamed of being a Fireman. Then I learned that they put out the fires.

b20uvkft6m5xwg

Here's the system.ini if its any help!!??

START

[boot]
oemfonts.fon=vga850.fon
shell=Explorer.exe
system.drv=atmsys.drv
drivers=mmsystem.dll power.drv
user.exe=user.exe
gdi.exe=gdi.exe
sound.drv=mmsound.drv
dibeng.drv=dibeng.dll
comm.drv=comm.drv
mouse.drv=mouse.drv
keyboard.drv=keyboard.drv
*DisplayFallback=0
fixedfon.fon=vgafix.fon
fonts.fon=vgasys.fon
386Grabber=vgafull.3gr
display.drv=pnpdrvr.drv
atm.system.drv=system.drv
scrnsave.exe=C:\WINDOWS\EASYPH~1.SCR

[keyboard]
keyboard.dll=
oemansi.bin=xlat850.bin
subtype=
type=4

[boot.description]
system.drv=Standard PC
mouse.drv=Microsoft Mouse
keyboard.typ=Standard 101/102-Key or Microsoft Natural Keyboard
aspect=100,96,96
display.drv=NVIDIA RIVA TNT2 Model 64 (Gateway - English)

[386Enh]
DEVICE=CDAINT2F.VXD
ebios=*ebios
woafont=app850.fon
mouse=*vmouse, msmouse.vxd
device=*dynapage
device=*vcd
device=*vpd
device=*int13
device=*enable
keyboard=*vkd
EMMExclude=C000-CFFF
display=*vdd,*vflatd
TimerCriticalSection=5000
UniqueDOSPSP=TRUE
PSPIncrement=5
ComBoostTime=2

[NonWindowsApp]
TTInitialSizes=4 5 6 7 8 9 10 11 12 13 14 15 16 18 20 22

[power.drv]

[drivers]
wavemapper=*.drv
MSACM.imaadpcm=*.acm
MSACM.msadpcm=*.acm
MSVideo.VfWWDM=vfwwdm.drv
wave=mmsystem.dll
midi=mmsystem.dll

[iccvid.drv]

[mciseq.drv]

[mci]
cdaudio=mcicda.drv
sequencer=mciseq.drv
waveaudio=mciwave.drv
avivideo=mciavi.drv
videodisc=mcipionr.drv
vcr=mcivisca.drv
MPEGVideo=mciqtz.drv
dvdvidex=mcicinem.drv DVD
MPEGVideo2=mciqtz.drv
ActiveMovie=mciqtz.drv

[vcache]

[MSNP32]

[Password Lists]
DAVID R. STAUNTON=C:\WINDOWS\DAVIDRST.PWL

[ScreenTime]
Password Value=0

[CineMac]
Password Value=0

[Network Drivers]
Dynamic=Yes

[TTFontDimenCache]
0 4=2 4
0 5=3 5
0 6=4 6
0 7=4 7
0 8=5 8
0 9=5 9
0 10=6 10
0 11=7 11
0 12=7 12
0 13=8 13
0 14=8 14
0 15=9 15
0 16=10 16
0 18=11 18
0 20=12 20
0 22=13 22

[drivers32]
msacm.lhacm=lhacm.acm
VIDC.VDOM=vdowave.drv
msacm.msg711=msg711.acm
vidc.CVID=iccvid.dll
VIDC.IV31=ir32_32.dll
VIDC.IV32=ir32_32.dll
vidc.MSVC=msvidc32.dll
VIDC.MRLE=msrle32.dll
msacm.msg723=msg723.acm
vidc.M263=msh263.drv
vidc.M261=msh261.drv
MSACM.imaadpcm=imaadp32.acm
MSACM.msadpcm=msadp32.acm
MSACM.msgsm610=msgsm32.acm
MSACM.trspch=tssoft32.acm
VIDC.IV50=ir50_32.dll
msacm.iac2=C:\WINDOWS\SYSTEM\IAC25_32.AX
VIDC.IV41=ir41_32.dll
VIDC.YVU9=iyvu9_32.dll
msacm.l3acm=C:\WINDOWS\SYSTEM\L3CODECA.ACM
msacm.msaudio1=msaud32.acm
msacm.msnaudio=msnaudio.acm
VIDC.CJPG=ctwbjpg.dll
VIDC.YUY2=msyuv.dll
VIDC.I420=yuv2rgb.dll
msacm.sl_anet=sl_anet.acm
msacm.voxacm160=vct3216.acm
vidc.mpg4=mpg4c32.dll
vidc.mp42=mpg4c32.dll
vidc.mp43=mpg4c32.dll
VIDC.NTN1=ntcodec.ax
VIDC.UYVY=msyuv.dll
VIDC.YVYU=msyuv.dll

END

---

80p.
SAVE CHIP !!

phaxx

Urr.... two options, as I see it, the first is reinstall windows (Heh, that's usually my first suggestion regarding windows problems ), and the second is go through with the MSDN instructions, so hopefully that file will be replaced and all will be okay.

Oh, thought of another, open up the registry editor (regedit.exe) and search for "vvinesd.386" (all keys, values and data) and see if it's found. If it is, remove the offending values.

Something to do before that, however, is make a backup of the registry. (Registry menu, Export registry file, and chose the "all" option at the bottom.)

If something else is broken by this, you can just run that registry file you exported and it'll fix it up again.

That's all I can think of for now.

(As far as I can see, the problem isn't in the system.ini)

_CreeD_

It's in your registry pure and simple, search, delete.
Win9x will use the registry for practically all your software, always check this first. The INI files are more for legacy support (And the odd setting that you may need to edit outside of windows itself if things go hairy), so should be checked last.

As for setting it back up, heres a quick guide:

1. remove all network components.
2. Install the adapter, reboot, check in Device manager afterwards to see if it is installed correctly.
3. You need the following installed -
CLIENT/..For Microsoft Networks.
PROTOCOL/Tcp-IP (Manually set an Ip on each machine, 100.100.100.x (1,2,3 etc), Subnet 255.255.255.0. gateway can be left blank but if you have problems try setting it to the machine's IP address, sometimes Win9x gets Conf00zed and tries to send packets from your Dial Up Adapter instead (your modem).
FILE & PRINT SHARING
Identification Make sure each computer name is unique, but that they all have the exact same workgroup name.

When this is done on each machine go to a dos box and type PING 100.100.100.x, where x is the last digit of each of the other machines. This basically plays ping-pong with small packets of info between them, testing the connection. It should come back with some speed statistics for each machine, for your purposes these are not important just that it does not say DESTINATION UNREACHABLE (Then it's back to checking everything above)


Finally Open Windows\System32\Drivers\etc\LMHOSTS.SAM and enter the IP's and names of the other machines (It gives you an example in the file itself and is very easy). LMHOSTS may be in a dif location so if need be just do a search. If you dont do this you may not be able to see each machine by name (Although you will be able to ping them).


[This message has been edited by _CreeD_ (edited 24-08-2001).]