>I tried to install WFW311 in a VPC2007 guest.
> All seemed to go well until I actually started windows by entering win
> on the command prompt after the reboot.
>
> I am now seeing the following two error messages and then I am
> returned to the dos prompt:
>
> "The following error occurred while loading protocol number 0.
> Error 58: THe network has responded incorrectly. You may need to
> reconfigure the protocol using Network Setup. If your computer is a
> portable, make sure it is connected to its docking station"
>
> Then:
> "Application error
> PROGMAN caused a General Protection Fault in module KRNL386.EXE at
> 0001:93D5."
>
> And then I am at the C:\ prompt. :-(
>
> The guest settings are:
> RAM = 32Mb
> HDD = 512 Mb
> NIC: using my host NIC (Intel PRO/100 VE)
> Sound: enabled
> HV: not available
> Display: default
>
> DOS version: MS-DOS 6.22 (MSDN download)
>
> My WFW311 install selections (apart from next-next-next):
> Keyboard layout: Swedish
> NIC: DEC 211
> Workgroup: I set it to my home network name
>
> Everything else is the defaults....
>
> I realize that this is probably not a VPC issue as such, but there is
> nowhere to go on an old windows like this.
>
> What could I do to get it running?
>
>
> Bo Berglund

>news:(email address - cut out)...
>>I tried to install WFW311 in a VPC2007 guest.
>> All seemed to go well until I actually started windows by entering win
>> on the command prompt after the reboot.
>>
>> I am now seeing the following two error messages and then I am
>> returned to the dos prompt:
>>
>> "The following error occurred while loading protocol number 0.
>> Error 58: THe network has responded incorrectly. You may need to
>> reconfigure the protocol using Network Setup. If your computer is a
>> portable, make sure it is connected to its docking station"
>>
>> Then:
>> "Application error
>> PROGMAN caused a General Protection Fault in module KRNL386.EXE at
>> 0001:93D5."
>>
>> And then I am at the C:\ prompt. :-(
>>
>> The guest settings are:
>> RAM = 32Mb
>> HDD = 512 Mb
>> NIC: using my host NIC (Intel PRO/100 VE)
>> Sound: enabled
>> HV: not available
>> Display: default
>>
>> DOS version: MS-DOS 6.22 (MSDN download)
>>
>> My WFW311 install selections (apart from next-next-next):
>> Keyboard layout: Swedish
>> NIC: DEC 211
>> Workgroup: I set it to my home network name
>>
>> Everything else is the defaults....
>>
>> I realize that this is probably not a VPC issue as such, but there is
>> nowhere to go on an old windows like this.
>>
>> What could I do to get it running?
>>
>Try turning off hardware virtualization in the vm's settings and restarting
>it.
>
>> HV: not available

>WFW311 logo is shown. Instead I see a black screen with the cursor
>blinking on line 3 and nothing more happening....
>Ctrl-Alt-Del does not work.
>Reset cause a new start of DOS.
>*Now* when I use the win command I get the error messages on a
>graphics screen as described above. And then I am back at the black
>screen with the blinking cursor only....
>On Sat, 10 May 2008 21:40:57 +0200, Bo Berglund <(email address - cut out)>
>wrote:
>
>>I tried to install WFW311 in a VPC2007 guest.
>>All seemed to go well until I actually started windows by entering win
>>on the command prompt after the reboot.
>>
>>I am now seeing the following two error messages and then I am
>>returned to the dos prompt:
>>
>>"The following error occurred while loading protocol number 0.
>>Error 58: THe network has responded incorrectly. You may need to
>>reconfigure the protocol using Network Setup. If your computer is a
>>portable, make sure it is connected to its docking station"
>>
>>Then:
>>"Application error
>>PROGMAN caused a General Protection Fault in module KRNL386.EXE at
>>0001:93D5."
>>
>>And then I am at the C:\ prompt. :-(
>>
>>The guest settings are:
>>RAM = 32Mb
>>HDD = 512 Mb
>>NIC: using my host NIC (Intel PRO/100 VE)
>>Sound: enabled
>>HV: not available
>>Display: default
>>
>>DOS version: MS-DOS 6.22 (MSDN download)
>>
>>My WFW311 install selections (apart from next-next-next):
>>Keyboard layout: Swedish
>>NIC: DEC 211
>>Workgroup: I set it to my home network name
>>
>
>I now changed the RAM amount down to 8 Mb hoping that 32 Mb was really
>too much for WfW311.
>When I started up the guest I found that there were a few messages on
>DOS boot tha might shed some insight:
>C:\WINDOWS\net start
>DEPCA MAC Driver Version v1.13.006
>Copyright....
>MAC0014E: Diagnostic error 90 detected on ethernet card.
>Error loading device driver DEPCA.DOS
>Error 7306: THe driver failed to initialize
>DEPCA.DOS was not loaded.
>Error 7321: Network-card drivers failed to load.
>
>Virtual Machine Folder Sharing
>Copyright....
>MSCDEX Version 2.23
>Copyright....
>Drive E: = Driver IDECD001 unit 0
>Microsoft (R) Mouse Driver Version 1.0.1
>
>It looks like there is some problem with the emulated network card,
>maybe selecting the DEC211 card was not right during WFW311 setup?
>If so, how can I fix it now?
>
>I also noted that now I don't get the two error messages after the
>WFW311 logo is shown. Instead I see a black screen with the cursor
>blinking on line 3 and nothing more happening....
>Ctrl-Alt-Del does not work.
>Reset cause a new start of DOS.
>*Now* when I use the win command I get the error messages on a
>graphics screen as described above. And then I am back at the black
>screen with the blinking cursor only....
>
>
>I *have * installed the Virtual Machine Additions for DOS from VPC2004
>on this guest prior to installing WFW311 (it was the only way I could
>figure out to get the setup files over to the guest).
>I have now used it to copy over the autoexec.bat, config.sys and all
>windows\*.ini files to my host machine.
>
>Here is the contents of the protocol.ini file:
>----------------------------------------------
>[network.setup]
>version=0x3110
>netcard=ms$ewmctp,1,MS$EWMCTP,1
>transport=ms$nwlinknb,NWLINK
>transport=ms$ndishlp,MS$NDISHLP
>transport=ms$netbeui,NETBEUI
>lana0=ms$ewmctp,1,ms$netbeui
>lana1=ms$ewmctp,1,ms$nwlinknb
>lana2=ms$ewmctp,1,ms$ndishlp
>
>
>[protman]
>DriverName=PROTMAN$
>PRIORITY=MS$NDISHLP
>
>[MS$EWMCTP]
>DriverName=DEPCA$
>MaxMulticast=8
>MaxTransmits=16
>AdapterName=DE210
>IOAddress=0x300
>
>[NWLINK]
>BINDINGS=MS$EWMCTP
>
>[MS$NDISHLP]
>DriverName=ndishlp$
>BINDINGS=MS$EWMCTP
>
>[NETBEUI]
>DriverName=netbeui$
>SESSIONS=10
>NCBS=12
>BINDINGS=MS$EWMCTP
>LANABASE=0
>
>Config.sys is like this:
>------------------------
>DEVICE=C:\VMADD\VMADD386.SYS
>DEVICE=C:\DOS\SETVER.EXE
>DEVICE=C:\WINDOWS\HIMEM.SYS
>DOS=HIGH
>FILES=30
>SHELL=C:\DOS\COMMAND.COM C:\DOS\ /p
>REM **********************************************
>REM **** DOS Virtual Machine Additions *****
>REM **********************************************
>DEVICE=C:\VMADD\CDROM.SYS /D:IDECD001 /L:E
>LASTDRIVE=Z
>DEVICE=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFER
>DEVICE=C:\WINDOWS\IFSHLP.SYS
>STACKS=9,256
>
>Autoexec.bat looks like this:
>-------------------------------
>C:\WINDOWS\SMARTDRV.EXE
>C:\WINDOWS\net start
>@ECHO OFF
>PROMPT $p$g
>PATH C:\WINDOWS;C:\DOS
>SET TEMP=C:\DOS
>@REM **********************************************
>@REM **** DOS Virtual Machine Additions *****
>@REM **********************************************
>SET DOSVMADD13=INSTALLED
>c:\vmadd\fshare.exe
>C:\WINDOWS\MSCDEX.EXE /S /D:IDECD001 /L:E /M:8
>c:\vmadd\idle.com
>c:\vmadd\mouse.com
>@rem win
>
>Anyone familiar with the WFW311 handling???
>
>
>Bo Berglund

>I tried to install WFW311 in a VPC2007 guest.
>All seemed to go well until I actually started windows by entering win
>on the command prompt after the reboot.
>
>I am now seeing the following two error messages and then I am
>returned to the dos prompt:
>
>"The following error occurred while loading protocol number 0.
>Error 58: THe network has responded incorrectly. You may need to
>reconfigure the protocol using Network Setup. If your computer is a
>portable, make sure it is connected to its docking station"
>
>Then:
>"Application error
>PROGMAN caused a General Protection Fault in module KRNL386.EXE at
>0001:93D5."
>
>And then I am at the C:\ prompt. :-(
>
>The guest settings are:
>RAM = 32Mb
>HDD = 512 Mb
>NIC: using my host NIC (Intel PRO/100 VE)
>Sound: enabled
>HV: not available
>Display: default
>
>DOS version: MS-DOS 6.22 (MSDN download)
>
>My WFW311 install selections (apart from next-next-next):
>Keyboard layout: Swedish
>NIC: DEC 211
>Workgroup: I set it to my home network name
>

>My CPU does not support HV so it was never aproblem for me.
>Where should I go and change things to get the right driver?
>I assume it is in one or a few of the control files:
>config.sys and/or autoexec.bat
>However, I don't understand from where it is coming because I can't
>find any network driver load commands in config.sys or autoexec...
>On Sun, 11 May 2008 08:54:03 -0400, Robert Comer
><(email address - cut out)> wrote:
>
>>>I also noted that now I don't get the two error messages after the
>>>WFW311 logo is shown. Instead I see a black screen with the cursor
>>>blinking on line 3 and nothing more happening....
>>>Ctrl-Alt-Del does not work.
>>>Reset cause a new start of DOS.
>>>*Now* when I use the win command I get the error messages on a
>>>graphics screen as described above. And then I am back at the black
>>>screen with the blinking cursor only....
>>
>>Make sure you have hardware virtualization turned off for that VM, I
>>found Windows3.11 wouldn't run with it on.
>
>As I stated already in my first posting the HV is not even available.
>My CPU does not support HV so it was never aproblem for me.
>
>>As for your networking problem, that driver isn't the right one, it
>>should be the one for the Intel 2104x/2114x (driver name DC21x4$)
>
>Where should I go and change things to get the right driver?
>I assume it is in one or a few of the control files:
>config.sys and/or autoexec.bat
>There is an error message concerning the network already on DOS boot
>(before I use the win command).
>However, I don't understand from where it is coming because I can't
>find any network driver load commands in config.sys or autoexec...
>
>Config.sys:
>------------
>DEVICE=C:\VMADD\VMADD386.SYS
>DEVICE=C:\DOS\SETVER.EXE
>DEVICE=C:\WINDOWS\HIMEM.SYS
>DOS=HIGH
>FILES=30
>SHELL=C:\DOS\COMMAND.COM C:\DOS\ /p
>REM **********************************************
>REM **** DOS Virtual Machine Additions *****
>REM **********************************************
>DEVICE=C:\VMADD\CDROM.SYS /D:IDECD001 /L:E
>LASTDRIVE=Z
>DEVICE=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFER
>DEVICE=C:\WINDOWS\IFSHLP.SYS
>STACKS=9,256
>
>autoexec.bat
>-------------
>C:\WINDOWS\SMARTDRV.EXE
>C:\WINDOWS\net start
>@ECHO OFF
>PROMPT $p$g
>PATH C:\WINDOWS;C:\DOS
>SET TEMP=C:\DOS
>@REM **********************************************
>@REM **** DOS Virtual Machine Additions *****
>@REM **********************************************
>SET DOSVMADD13=INSTALLED
>c:\vmadd\fshare.exe
>C:\WINDOWS\MSCDEX.EXE /S /D:IDECD001 /L:E /M:8
>c:\vmadd\idle.com
>c:\vmadd\mouse.com
>@rem win
>
>Except possibly the C:\WINDOWS\net start command.
>But there is no specific driver mentioned, how does one get that
>loaded correctly?
>
>Is there a way to disable networking to get into windows and then
>inside windows finding a place to configure the NIC?
>
>
>Bo Berglund

>On Sun, 11 May 2008 08:54:03 -0400, Robert Comer
><(email address - cut out)> wrote:
>
>>>I also noted that now I don't get the two error messages after the
>>>WFW311 logo is shown. Instead I see a black screen with the cursor
>>>blinking on line 3 and nothing more happening....
>>>Ctrl-Alt-Del does not work.
>>>Reset cause a new start of DOS.
>>>*Now* when I use the win command I get the error messages on a
>>>graphics screen as described above. And then I am back at the black
>>>screen with the blinking cursor only....
>>
>>Make sure you have hardware virtualization turned off for that VM, I
>>found Windows3.11 wouldn't run with it on.
>>
>>As for your networking problem, that driver isn't the right one, it
>>should be the one for the Intel 2104x/2114x (driver name DC21x4$)
>
>I reverted to using the undo disks to get back before WFW installation
>and tried to redo it from scratch. When I come to the network setup
>the choices for network cards do not include the Intel 2104x...
>The only Intel NICs listed are:
>EtherExpress 16(MCA), EtherExpress 16 or 16TP, EtherExpress/32,
>TokenExpress 16/4, TokenExpress EISA 16/4, TokenExpress MCA 16/4
>
>How can one install the 2104 NIC in WFW311 setup???
>
>
>
>Bo Berglund

>>>I reverted to using the undo disks to get back before WFW installation
>>>and tried to redo it from scratch. When I come to the network setup
>>>the choices for network cards do not include the Intel 2104x...
>>>The only Intel NICs listed are:
>>>EtherExpress 16(MCA), EtherExpress 16 or 16TP, EtherExpress/32,
>>>TokenExpress 16/4, TokenExpress EISA 16/4, TokenExpress MCA 16/4
>>>
>>>How can one install the 2104 NIC in WFW311 setup???
>>>
>
> On Sun, 11 May 2008 12:17:20 -0400, Robert Comer
> <(email address - cut out)> wrote:
>
>>Get the proper driver from Steve's site. (NDIS2 driver)
>>
>>There's an install adapter in Wfw3.11 that allows you select a floppy
>>or path, just pick "Unlisted or updated network adapter".
>>
>>--
>>Bob Comer
>>
>
> After making a new WFW311 install *without* selecting any network card
> I got WFW311 working.
> Next I downloaded the drivers from Intel. Steve's page does *not* have
> them as far as I could see but they are here:
> http://developer.intel.com/design/network/drivers/nd2_300.htm
>
> After putting them on a virtual floppy disk and then going to the
> Network/Network Setup function in WFW I was able to add the adapter
> from the WFW subdir of the wfw311 subdir of the Intel disk tree.
>
> Now I have networking enabled in WFW and no more error messages on
> startup. :-)
>
> But the only protocol is NetBEUI, and my external network uses TCP/IP
> so my next task is to get TCP/IP working in the WFW311 guest.
>
> Found a tutorial here:
> http://www.yale.edu/pclt/WINWORLD/WFWG311.HTM
>
> And the Microsoft TCP/IP stack for WfW 3.11 here:
> http://developer.intel.com/design/network/drivers/nd2_300.htm
>
> Now I just have to see what can be done with the network using WfW
> 3.11. :-)
>
> Cheers
>
>
> Bo Berglund

>>>I reverted to using the undo disks to get back before WFW installation
>>>and tried to redo it from scratch. When I come to the network setup
>>>the choices for network cards do not include the Intel 2104x...
>>>The only Intel NICs listed are:
>>>EtherExpress 16(MCA), EtherExpress 16 or 16TP, EtherExpress/32,
>>>TokenExpress 16/4, TokenExpress EISA 16/4, TokenExpress MCA 16/4
>>>
>>>How can one install the 2104 NIC in WFW311 setup???
>>>
>
>On Sun, 11 May 2008 12:17:20 -0400, Robert Comer
><(email address - cut out)> wrote:
>
>>Get the proper driver from Steve's site. (NDIS2 driver)
>>
>>There's an install adapter in Wfw3.11 that allows you select a floppy
>>or path, just pick "Unlisted or updated network adapter".
>>
>>--
>>Bob Comer
>>
>
>After making a new WFW311 install *without* selecting any network card
>I got WFW311 working.
>Next I downloaded the drivers from Intel. Steve's page does *not* have
>them as far as I could see but they are here:
>http://developer.intel.com/design/network/drivers/nd2_300.htm
>
>After putting them on a virtual floppy disk and then going to the
>Network/Network Setup function in WFW I was able to add the adapter
>from the WFW subdir of the wfw311 subdir of the Intel disk tree.
>
>Now I have networking enabled in WFW and no more error messages on
>startup. :-)
>
>But the only protocol is NetBEUI, and my external network uses TCP/IP
>so my next task is to get TCP/IP working in the WFW311 guest.
>
>Found a tutorial here:
>http://www.yale.edu/pclt/WINWORLD/WFWG311.HTM
>
>And the Microsoft TCP/IP stack for WfW 3.11 here:
>http://developer.intel.com/design/network/drivers/nd2_300.htm
>
>Now I just have to see what can be done with the network using WfW
>3.11. :-)
>
>Cheers
>
>
>Bo Berglund

>>>I reverted to using the undo disks to get back before WFW installation
>>>and tried to redo it from scratch. When I come to the network setup
>>>the choices for network cards do not include the Intel 2104x...
>>>The only Intel NICs listed are:
>>>EtherExpress 16(MCA), EtherExpress 16 or 16TP, EtherExpress/32,
>>>TokenExpress 16/4, TokenExpress EISA 16/4, TokenExpress MCA 16/4
>>>
>>>How can one install the 2104 NIC in WFW311 setup???
>>>
>
>On Sun, 11 May 2008 12:17:20 -0400, Robert Comer
><(email address - cut out)> wrote:
>
>>Get the proper driver from Steve's site. (NDIS2 driver)
>>
>>There's an install adapter in Wfw3.11 that allows you select a floppy
>>or path, just pick "Unlisted or updated network adapter".
>>
>>--
>>Bob Comer
>>
>
>After making a new WFW311 install *without* selecting any network card
>I got WFW311 working.
>Next I downloaded the drivers from Intel. Steve's page does *not* have
>them as far as I could see but they are here:
>http://developer.intel.com/design/network/drivers/nd2_300.htm
>

>>I also noted that now I don't get the two error messages after the
>>WFW311 logo is shown. Instead I see a black screen with the cursor
>>blinking on line 3 and nothing more happening....
>>Ctrl-Alt-Del does not work.
>>Reset cause a new start of DOS.
>>*Now* when I use the win command I get the error messages on a
>>graphics screen as described above. And then I am back at the black
>>screen with the blinking cursor only....
>
>Make sure you have hardware virtualization turned off for that VM, I
>found Windows3.11 wouldn't run with it on.
>As for your networking problem, that driver isn't the right one, it
>should be the one for the Intel 2104x/2114x (driver name DC21x4$)

>On Sun, 11 May 2008 20:48:39 +0200, Bo Berglund <(email address - cut out)>
>wrote:
>
>>
>>Now I just have to see what can be done with the network using WfW
>>3.11. :-)
>>
>
>So now:
>- MSDOS 6.22 installed
>- Virtual Machine Additions for DOS (VPC2004) installed
>- Windows for Workgroups 3.11 installed
>- Network support for the emulated NIC installed
>- WfW 3.11 TCP/IP installed
>- S3 Trio64+ video driver installed and running at 1024x768
>
>Is there any chance of getting mouse integration working with the
>additions? There is none at the moment.
>
>
>
>Bo Berglund

>>I also noted that now I don't get the two error messages after the
>>WFW311 logo is shown. Instead I see a black screen with the cursor
>>blinking on line 3 and nothing more happening....
>>Ctrl-Alt-Del does not work.
>>Reset cause a new start of DOS.
>>*Now* when I use the win command I get the error messages on a
>>graphics screen as described above. And then I am back at the black
>>screen with the blinking cursor only....
>
>Make sure you have hardware virtualization turned off for that VM, I
>found Windows3.11 wouldn't run with it on.
>
>As for your networking problem, that driver isn't the right one, it
>should be the one for the Intel 2104x/2114x (driver name DC21x4$)

> Found a tutorial here:
> http://www.yale.edu/pclt/WINWORLD/WFWG311.HTM
>
> And the Microsoft TCP/IP stack for WfW 3.11 here:
> http://developer.intel.com/design/network/drivers/nd2_300.htm
>
> Now I just have to see what can be done with the network using WfW
> 3.11. :-)

>>and tried to redo it from scratch. When I come to the network setup
>>the choices for network cards do not include the Intel 2104x...
>>The only Intel NICs listed are:
>>EtherExpress 16(MCA), EtherExpress 16 or 16TP, EtherExpress/32,
>>TokenExpress 16/4, TokenExpress EISA 16/4, TokenExpress MCA 16/4
>>
>>How can one install the 2104 NIC in WFW311 setup???
>>
>Get the proper driver from Steve's site. (NDIS2 driver)
>
>There's an install adapter in Wfw3.11 that allows you select a floppy
>or path, just pick "Unlisted or updated network adapter".
>
>--
>Bob Comer
>

> The blog is at
> http://blogs.msdn.com/virtual_pc_guy/archive/2004/10/26/247793.aspx

>"Bo Berglund" <(email address - cut out)> wrote in message
>news:(email address - cut out)...
>
>> Found a tutorial here:
>> http://www.yale.edu/pclt/WINWORLD/WFWG311.HTM
>>
>> And the Microsoft TCP/IP stack for WfW 3.11 here:
>> http://developer.intel.com/design/network/drivers/nd2_300.htm
>>
>> Now I just have to see what can be done with the network using WfW
>> 3.11. :-)
>
>My old MSDN CD of 16-bit operating systems has a whole subdirectory under
>the WfW311 directory called \TCPIP which explains how to do all this, and
>contains all of the 16-bit TCP/IP utilities e.g. FTP.EXE, TELNET.EXE,
>TRACERT.EXE etc...
>
>It's just over 1Mb in size...

> - MSDOS 6.22 installed
> - Virtual Machine Additions for DOS (VPC2004) installed
> - Windows for Workgroups 3.11 installed
> - Network support for the emulated NIC installed
> - WfW 3.11 TCP/IP installed
> - S3 Trio64+ video driver installed and running at 1024x768

>
>Now I just have to see what can be done with the network using WfW
>3.11. :-)
>

>>After making a new WFW311 install *without* selecting any network card
>>I got WFW311 working.
>>Next I downloaded the drivers from Intel. Steve's page does *not* have
>>them as far as I could see but they are here:
>>http://developer.intel.com/design/network/drivers/nd2_300.htm
>>
>
>http://www.essjae.com/VPC/default.htm#VPC_-_General
>Emulated Intel 21140a Drivers (Intel 21143) --DOS Drivers are here!
>*Link to Intel's Website*
>
>( DOS drivers == NDIS2 Unified 21xxx driver v3.0 )

>>http://www.essjae.com/VPC/default.htm#VPC_-_General
>>Emulated Intel 21140a Drivers (Intel 21143) --DOS Drivers are here!
>>*Link to Intel's Website*
>>
>>( DOS drivers == NDIS2 Unified 21xxx driver v3.0 )
>
>I suggest you change the link to actually point to the end position.
>The link you have is very confusing since the Intel page shows about
>30-40 *different* download links and once it is shown you have lost
>the wording on your page that hints on what to look for. A better URL
>is:
>http://developer.intel.com/design/network/drivers/nd2_300.htm
>where the actual download is located.
>
>(Maybe changing your link to open in a separate window is also viable
>so that one can easily go back and check what it said...)

> Seems like the screen driver is involved, why?

>"Bo Berglund" <(email address - cut out)> wrote in message
>news:(email address - cut out)...
>
>> - MSDOS 6.22 installed
>> - Virtual Machine Additions for DOS (VPC2004) installed
>> - Windows for Workgroups 3.11 installed
>> - Network support for the emulated NIC installed
>> - WfW 3.11 TCP/IP installed
>> - S3 Trio64+ video driver installed and running at 1024x768
>
>You should also be able to install v1.0 of the 16-bit SB sound card driver.
>
>Also, have you had a go at installing 16-bit IE5? Everything works until you
>actually try to browse to a website... ;-)

>"Bo Berglund" <(email address - cut out)> wrote in message
>news:(email address - cut out)...
>
>> Seems like the screen driver is involved, why?
>
>Sorry - I don't know...

> What screen driver/resolution do you use?

>"Bo Berglund" <(email address - cut out)> wrote in message
>news:(email address - cut out)...
>
>> - MSDOS 6.22 installed
>> - Virtual Machine Additions for DOS (VPC2004) installed
>> - Windows for Workgroups 3.11 installed
>> - Network support for the emulated NIC installed
>> - WfW 3.11 TCP/IP installed
>> - S3 Trio64+ video driver installed and running at 1024x768
>
>You should also be able to install v1.0 of the 16-bit SB sound card driver.
>
>Also, have you had a go at installing 16-bit IE5? Everything works until you
>actually try to browse to a website... ;-)

> So it is probably no use trying to use IE5 on any modern type
> webpage....

> Have you tried a copy of Netscape?

> >>I reverted to using the undo disks to get back before WFW installation
> >>and tried to redo it from scratch. When I come to the network setup
> >>the choices for network cards do not include the Intel 2104x...
> >>The only Intel NICs listed are:
> >>EtherExpress 16(MCA), EtherExpress 16 or 16TP, EtherExpress/32,
> >>TokenExpress 16/4, TokenExpress EISA 16/4, TokenExpress MCA 16/4
> >>
> >>How can one install the 2104 NIC in WFW311 setup???
> >>
>
> On Sun, 11 May 2008 12:17:20 -0400, Robert Comer
> <(email address - cut out)> wrote:
>
> >Get the proper driver from Steve's site. (NDIS2 driver)
> >
> >There's an install adapter in Wfw3.11 that allows you select a floppy
> >or path, just pick "Unlisted or updated network adapter".
> >
> >--
> >Bob Comer
> >
>
> After making a new WFW311 install *without* selecting any network card
> I got WFW311 working.
> Next I downloaded the drivers from Intel. Steve's page does *not* have
> them as far as I could see but they are here:
> http://developer.intel.com/design/network/drivers/nd2_300.htm
>
> After putting them on a virtual floppy disk and then going to the
> Network/Network Setup function in WFW I was able to add the adapter
> from the WFW subdir of the wfw311 subdir of the Intel disk tree.
>
> Now I have networking enabled in WFW and no more error messages on
> startup. :-)
>
> But the only protocol is NetBEUI, and my external network uses TCP/IP
> so my next task is to get TCP/IP working in the WFW311 guest.
>
> Found a tutorial here:
> http://www.yale.edu/pclt/WINWORLD/WFWG311.HTM
>
> And the Microsoft TCP/IP stack for WfW 3.11 here:
> http://developer.intel.com/design/network/drivers/nd2_300.htm
>
> Now I just have to see what can be done with the network using WfW
> 3.11. :-)
>
> Cheers
>
>

> "Bo Berglund" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>
> > - MSDOS 6.22 installed
> > - Virtual Machine Additions for DOS (VPC2004) installed
> > - Windows for Workgroups 3.11 installed
> > - Network support for the emulated NIC installed
> > - WfW 3.11 TCP/IP installed
> > - S3 Trio64+ video driver installed and running at 1024x768
>
> You should also be able to install v1.0 of the 16-bit SB sound card driver.
>
> Also, have you had a go at installing 16-bit IE5? Everything works until you
> actually try to browse to a website... ;-)
>
>
>

> On Sun, 11 May 2008 23:10:24 +0100, "Mark Rae [MVP]"
> <(email address - cut out)> wrote:
>
> >"Bo Berglund" <(email address - cut out)> wrote in message
> >news:(email address - cut out)...
> >
> >> - MSDOS 6.22 installed
> >> - Virtual Machine Additions for DOS (VPC2004) installed
> >> - Windows for Workgroups 3.11 installed
> >> - Network support for the emulated NIC installed
> >> - WfW 3.11 TCP/IP installed
> >> - S3 Trio64+ video driver installed and running at 1024x768
> >
> >You should also be able to install v1.0 of the 16-bit SB sound card driver.
> >
> >Also, have you had a go at installing 16-bit IE5? Everything works until you
> >actually try to browse to a website... ;-)
>
> Now working! :-)
>
> Had to do the following:
>
> 1) In Windows Setup change the display driver to:
> S3 Trio64V 1.70.04 800x600 256 C SF
>
> 2) When starting up IE5 cancel the Connection Wizard because it tries
> desperately to set up a *modem* connection, which I don't have.
>
> 3) When starting up IE5 the next time click the STOP button when it
> hangs trying to get a website.
>
> 4) Next in IE5 go to the Tools/InternetOptions/Connections tab and set
> it for "Your local area network...".
> Also on the General set "Home page" as the blank page. Then OK out.
>
> 5) Next restart Windows (in my case this involves restarting the whole
> machine because I don't seem to be able to get back to C: after using
> WfW3.11 anymore...)
>
> 6) Now I was able to enter an URL (to a simple website, known to do no
> tricks like java or similar) and it worked!
>
>
> Bo Berglund
>

> I tried to install WFW311 in a VPC2007 guest.
> All seemed to go well until I actually started windows by entering win
> on the command prompt after the reboot.
>
> I am now seeing the following two error messages and then I am
> returned to the dos prompt:
>
> "The following error occurred while loading protocol number 0.
> Error 58: THe network has responded incorrectly. You may need to
> reconfigure the protocol using Network Setup. If your computer is a
> portable, make sure it is connected to its docking station"
>
> Then:
> "Application error
> PROGMAN caused a General Protection Fault in module KRNL386.EXE at
> 0001:93D5."
>
> And then I am at the C:\ prompt. :-(
>
> The guest settings are:
> RAM =3D 32Mb
> HDD =3D 512 Mb
> NIC: using my host NIC (Intel PRO/100 VE)
> Sound: enabled
> HV: not available
> Display: default
>
> DOS version: MS-DOS 6.22 (MSDN download)
>
> My WFW311 install selections (apart from next-next-next):
> Keyboard layout: Swedish
> NIC: DEC 211
> Workgroup: I set it to my home network name
>
> Everything else is the defaults....
>
> I realize that this is probably not a VPC issue as such, but there is
> nowhere to go on an old windows like this.
>
> What could I do to get it running?
>
> Bo Berglund