Name: abuthemagician Date: April 30, 2007 at 07:21:15 Pacific Subject: Net Start crashes Dos 6.22 OS: Dos 6.22 WFW 3.11 CPU/Ram: ? / 64mb Model/Manufacturer: virtual PC 2007
Comment:
I am running DOS 6.22 and WFW 3.11 in VPC 2007. I have everything working except networking. When autoexec.bat runs the "net start" command, the information about my nic shows, but then it goes no farther and i have to reboot. Commenting out himem.sys seems to fix the issue, but i need a special config for emm386 as seen below. Any help?
config.sys: DEVICE=C:\VMADD\VMADD386.SYS DEVICE=C:\WINDOWS\HIMEM.SYS DEVICE=C:\WINDOWS\EMM386.EXE RAM I=B100-B7FF I=C600-C7FF I=CC00-CFFF I=E600-EFFF FRAME=D000 DOS=HIGH,UMB DEVICEHIGH=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFER DEVICEHIGH=C:\WINDOWS\IFSHLP.SYS STACKS=9,256 REM ********************************************** REM **** DOS Virtual Machine Additions ***** REM ********************************************** DEVICEHIGH=C:\VMADD\CDROM.SYS /D:IDECD001 /L:E LASTDRIVE=Z DEVICEHIGH=C:\WINDOWS\DC21X4.DOS /I:C:\WINDOWS
WfW3.11 has networking built in, you need to configure the Networking thru Windows not use MS-DOS NWC3.0 or whatever else you are trying to do, see the following posting for a link to the updated WfW TCP Stack:
"C:\WINDOWS\net start" is about all you need in DOS to prepare for WfW networking - - although there's no reason to load that command 'high'
Was this 'transcribed'? "LOADHIGHG" seems to be a creatively spelled instruction - - otherwise the usual cobbled together startup patchwork, put together by rote with little rhyme or reason
"Commenting out himem.sys"
EMM386 requires himem - - as well, the RAM parameter is a pointless and wasteful legacy, and should be replaced by NOEMS (removing the need for any FRAME)
I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter.
You do not need the “Smartdrive” line in the config.sys file.
You do need the “Smartdrive” line in the autoexec.bat file.
I would suggest that “SET TEMP=C:\DOS” be “SET TEMP=C:\TEMP.” If you don’t have this directory (Temp), create it. I personally do not want all the temporary files added to the DOS directory.
I would add a line in the config.sys tile as “FILES=50" or some other number. The higher the number, the more conventional memory used.
Why are you using double buffering?
When your computer first starts, at the starting MS-DOs, hit the F8 key. It will ask you to confirm each line in the config.sys file and in the autoexec.bat file. Should show line that need work.
CoffeeBreak I'm intrigued as to why you say not to load smartdrive. Even on a VM in VPC2004 and 2007 Dos seems slow to me without it. I know it takes a large bit of conventional but it's worth it, mind you the Double_Buffer is a bit overkill.
Also along the lines of adding Files=50 as CoffeeBreak said you should probably add Buffers=20 or 40 in your config.sys file and change LastDrive=Z to something like G or H.
DEVICE=C:\VMADD\VMADD386.SYS can anyone tell me what this loads? I now it's part of the VPC additions but what does it provide for DOS that it needs to be loaded first? I've never bothered to install them in DOS as I evry rarely require teh features it provides.
