VOGONS

[Solved] RTL8169SC-based card on Windows 3.11 for Workgroups

Topic actions

First post, by zerker

Posted on 
User metadata
Rank Member
Rank
Member

Hello folks. I'm having pretty good progress setting up my machine on both Windows 3.11 and Windows 98, but I'm having trouble with networking on the earlier Windows.

I managed to find RealTek drivers http://www.realtek.com.tw/downloads/downloads … &Downloads=true, but only for the RTL8169SB. I downloaded the NDIS drivers anyways, and successfully added them to Windows. Unfortunately, on bootup, it just freezes after it (apparently successfully) loads the drivers:
dosnet.png

Here are the relevant config files for reference:
autoexec.bat

@ECHO OFF
PROMPT $p$g
SET SOUND=C:\SB16
SET BLASTER=A220 I5 D1 H5 P330 E620 T6
SET MIDI=SYNTH:1 MAP:E MODE:0
SET CTCM=C:\SB16
SET PATH=C:\WINDOWS;C:\DOS;C:\Apps;C:\Apps\InfoZip;C:\SB16
SET TEMP=C:\TEMP
C:\SB16\CTCM
C:\SB16\DIAGNOSE /S /W=C:\WINDOWS
C:\SB16\AWEUTIL /S
C:\SB16\MIXERSET /P /Q
C:\SB16\CTCU.EXE /S /W=C:\WINDOWS

GOTO %CONFIG%

:Default
LH /L:0;1,3328 /S C:\DRIVERS\CTMOUSE\CTMOUSE.EXE
LH /L:1,28288 C:\WINDOWS\MSCDEX.EXE /S /D:mscd000 /E
GOTO END

:Ultima7
C:\DRIVERS\CTMOUSE\CTMOUSE.EXE
GOTO END

:EMS
LH C:\DRIVERS\CTMOUSE\CTMOUSE.EXE
GOTO END

:Network
LH /L:0;1,3328 /S C:\DRIVERS\CTMOUSE\CTMOUSE.EXE
LH /L:1,28288 C:\WINDOWS\MSCDEX.EXE /S /D:mscd000 /E
C:\Windows\NET START
GOTO END

:END

config.sys

[menu]
menuitem=Default
menuitem=Ultima7, Ultima 7
menuitem=EMS
menuitem=Network

[common]
DEVICE=C:\DOS\HIMEM.SYS
BUFFERS=10,0
FILES=40
STACKS=9,256
FCBS=4,0
DOS=HIGH

[Default]
DEVICE=C:\DOS\EMM386.EXE NOEMS HIGHSCAN WIN=DD00-DFFF WIN=DA00-DCFF
DOS=UMB
DEVICEHIGH /L:1,11264 =C:\DRIVERS\VIDE-CDD.SYS /D:MSCD000

[Ultima7]
REM Ultima 7 needs less, not more :)

[EMS]
DEVICE=C:\DOS\EMM386.EXE HIGHSCAN
DOS=UMB

[Network]
DEVICE=C:\DOS\EMM386.EXE NOEMS HIGHSCAN WIN=DD00-DFFF WIN=DA00-DCFF
DOS=UMB
DEVICEHIGH /L:1,11264 =C:\DRIVERS\VIDE-CDD.SYS /D:MSCD000
DEVICEHIGH=C:\Windows\IFSHLP.SYS

system.ini

[boot]           
386grabber=macx.3gr
286grabber=vgacolor.2gr
display.drv=macx.drv
oemfonts.fon=vgaoem.fon
fixedfon.fon=vgafix.fon
fonts.fon=vgasys.fon
shell=progman.exe
network.drv=wfwnet.drv
mouse.drv=lmouse.drv
language.dll=
sound.drv=mmsound.drv
comm.drv=comm.drv
system.drv=system.drv
keyboard.drv=keyboard.drv
drivers=mmsystem.dll msmixmgr.dll
SCRNSAVE.EXE=(None)

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

[boot.description]
aspect=100,96,96
displayinf=OEMMACX.INF
display.drv=mach64 Driver
mouse.drv=Logitech
language.dll=English (American)
system.drv=MS-DOS System
codepage=437
woafont.fon=English (437)
keyboard.typ=Enhanced 101 or 102 key US and Non US keyboards
network.drv=Microsoft Windows Network (version 3.11)
secondnet.drv=No Additional Network Installed

[386Enh]
device=C:\WINDOWS\SYSTEM\dva.386
display=macxvdd.386
EGA80WOA.FON=EGA80WOA.FON
EGA40WOA.FON=EGA40WOA.FON
CGA80WOA.FON=CGA80WOA.FON
CGA40WOA.FON=CGA40WOA.FON
device=vwavsyn.386
device=vsbpd.386
device=vsbawe.386
device=*vpd
mouse=lvmd.386
woafont=dosapp.fon
COM4Base=02E8
COM4Irq=3
COM3Base=03E8
COM3Irq=4
device=vpmtd.386
device=lpt.386
device=serial.386
device=vcomm.386
device=vtdapi.386
device=vshare.386
…Show last 167 lines
device=vcache.386
device=ifsmgr.386
device=lanman10.386
network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386
ebios=*ebios
keyboard=*vkd
device=*vpicd
device=vtda.386
device=*reboot
device=*vdmad
device=*vsd
device=*v86mmgr
device=*pageswap
device=*dosmgr
device=*vmpoll
device=*wshell
device=*BLOCKDEV
device=*PAGEFILE
device=*vfd
device=*parity
device=*biosxlat
device=*vcd
device=*vmcpd
device=*combuff
device=*cdpscsi
local=CON
FileSysChange=off
PermSwapDOSDrive=C
PermSwapSizeK=31972
netmisc=ndis.386,ndis2sup.386
transport=nwlink.386,nwnblink.386,netbeui.386
netheapsize=20
InDOSPolling=FALSE

[standard]

[NonWindowsApp]
localtsrs=dosedit,ced

[mci]
Sequencer=mciseq.drv
WaveAudio=mciwave.drv
CDAudio=mcicda.drv

[drivers]
midimapper=midimap.drv
timer=timer.drv
Wave=sb16snd.drv
Aux=sb16snd.drv
Midi=sb16fm.drv
Midi1=sb16snd.drv
Midi2=sbawe32.drv
Midi3=ctvmd.drv
Midi4=wavsynwg.drv
mixer=sb16snd.drv

VIDC.MSVC=msvidc.drv
VIDC.RT21=ir21_r.dll
VIDC.IV31=ir32.dll
VIDC.CVID=iccvid.drv
VIDC.RLE=ativdacc.drv
VIDC.YVU9=ir21_r.dll
VIDC.MRLE=msrle.drv
VIDC.IV32=ir32.dll
VIDS.DRAW=udh.dll
DCI=atidci
joystick=IBMJOY.DRV
[LogiMouse]
Type=PS/2
DragLock=None
SwapMiddleBottom=No

[vcache]
minfilecache=512

[Network]
FileSharing=Yes
PrintSharing=No
winnet=wfwnet/00025100
multinet=nonet
LogonDisconnected=yes
EnableSharing=Yes
UserName=DELTA
Workgroup=GALAXY
ComputerName=RYANARMS
Comment=Ryan Armstrong

[network drivers]
devdir=C:\WINDOWS
LoadRMDrivers=Yes
netcard=rtgbnd.dos
transport=ndishlp.sys,*netbeui

[sndblst.drv]
DisableMidiPort=0
Port=220
MidiPort=330
AwePort=620
Int=5
DmaChannel=1
HDmaChannel=5
PnpFlag=1
FDMAPlayback=0
FDMARecording=0
FullDuplex=1
RecordGain=0, 0
OutputGain=0, 0
AGC=0
SaveOnExit=0
VoiceVolume=16, 16
FMVolume=16, 16
CDVolume=17, 17
LineVolume=16, 16
MicVolume=16
MasterVolume=4, 4
SpeakerVolume=16
AuxVolume=16, 0
InputMasterVolume=4, 4
MuteVirtual=10
OutputMixerSwitch=1e
BassTone=16, 16
TrebleTone=16, 16
Mux_WaveIn=1e
WaveReverb=8000
WaveSynthVolume=80008000
WaveSynthReverb=3f
WaveReverbMute=0
WaveSynthMute=0
WaveSynthReverbMute=0


[Installable Compressors]
vidc.rle=ativdacc.drv

[Macx]
EngineText=off
DevCapStretchBlt=on
DeviceBitMap=off
VGADAC=on
DesktopSize=800x600
Dithering=on
Environment=Small Font
PaletteManager=on
PixelDepth=16
ScreenSize=800x600
VGADither=off

[mciseq.drv]
disablewarning=true

[joystick.drv]
JoyCal0=136a 008e 29c7 0073 0000 0000
JoyCal1=0000 0001 0000 0001 0000 0001


[DDEShares]
CHAT$=winchat,chat,,31,,0,,0,0,0
SCHAT$=winchat,chat,,31,,0,,0,0,0
CLPBK$=clipsrv,system,,31,,0,,0,0,0
HEARTS$=mshearts,hearts,,15,,0,,0,0,0

[NWNBLINK]
LANABASE=1

[Password Lists]
*Shares=C:\Windows\Share000.PWL

The download site does have a much smaller subsection for the RTL8169SC, but it only has PXE and RPL ROM code, which I don't think will help for Windows 3.11. Correct me if I'm wrong.

I've also tried the older 10/100 "only" driver from the relevant area without success. It reported a "Serious internal error!" and did not start at all.

Any suggestions or tips?

Last edited by zerker on 2016-03-14, 23:54. Edited 1 time in total.

Reply 1 of 8, by hyoenmadan

Posted on 
User metadata
Rank Member
Rank
Member

Latest versions of NDIS2/ODI/Packet drivers have nasty bugs and don't play very well with DOS.
You need the ones which come in the famous "OEM Disk Driver" zip files, also found at Realtek site (Them date from 1999-2001).

Also, would be that your card is too new and requires features in the PCI bus that are only found in the PCI rev 3.0 specification, like MSI/MSIX interrupts. Turning on these features in an unsupported old board can cause the system hang just like happened in your system. Try an older Realtek 10/100 card and check how it behaves in your system.

Because a board has PCI slots doesn't mean that you can plug any PCI card in them and it will work. Older would have an higher voltage requirement compatible with the older specification, but not the new one. And newer ones would require features which aren't present in the older systems but are compatible with the newest specification.

Reply 2 of 8, by zerker

Posted on 
User metadata
Rank Member
Rank
Member

Well, the card works in the same PC if it's running Windows 98, so it's nothing to do with the PCI bus/card compatibility. I will try to track down the "OEM Disk Driver" you suggest and see what works.

The main purpose of the card was to get networking in Windows 98, and for that it succeeded. I'd LIKE to get Dos/Win 3.11 working as a bonus, but it's not worth tracking down an alternate card for. If I can't figure out a solution, I'm okay with falling back to a null-modem cable.

Reply 3 of 8, by tayyare

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie

As far as I know, you don't need ODI/DOS packet drivers to be installed for Windows 3.11 network functionality. Furthermore, I can't see any lines in your autoexec.bat or config.sys files that supposed to load Realtek ODI drivers. Is this (loading DOS packet drivers automatically) some kind of a FreeDOS thing? For Arachne perhaps?

DEVICEHIGH=C:\Windows\IFSHLP.SYS and C:\Windows\NET START are the only lines needed in your config.sys and autoexec.bat files AFAIK, (which you already have), and they both added by Windows 3.11 network setup and completely generic/not related to Realtek.

GA-6VTXE PIII 1.4+512MB
Geforce4 Ti 4200 64MB
Diamond Monster 3D 12MB SLI
SB AWE64 PNP+32MB
120GB IDE Samsung/80GB IDE Seagate/146GB SCSI Compaq/73GB SCSI IBM
Adaptec AHA29160
3com 3C905B-TX
Gotek+CF Reader
MSDOS 6.22+Win 3.11/95 OSR2.1/98SE/ME/2000

Reply 4 of 8, by NJRoadfan

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie
tayyare wrote:

As far as I know, you don't need ODI/DOS packet drivers to be installed for Windows 3.11 network functionality. Furthermore, I can't see any lines in your autoexec.bat or config.sys files that supposed to load Realtek ODI drivers. Is this (loading DOS packet drivers automatically) some kind of a FreeDOS thing? For Arachne perhaps?

Realtek likely doesn't ship NDIS3 drivers for WfW 3.11. For some reason they keep shipping NDIS2 DOS drivers (which also apparently work on OS/2) and occasionally ODI and packet drivers. WfW 3.11 will work with them, its just annoying to configure. First thing to troubleshoot is EMM386, see if the driver will load with it disabled. If so, you likely have a conflict with the card using UMBs for some reason.

Reply 5 of 8, by chinny22

Posted on 
User metadata
Rank l33t++
Rank
l33t++

Just to double check, the PC is physically connected and able to reach a DHCP server. when starting windows?
3.x just hangs trying to find a network if not conected. Win /n gets around this, (but looses network)

Reply 6 of 8, by zerker

Posted on 
User metadata
Rank Member
Rank
Member
NJRoadfan wrote:

First thing to troubleshoot is EMM386, see if the driver will load with it disabled. If so, you likely have a conflict with the card using UMBs for some reason.

Thanks for that suggestion. That appears to have been the problem.

Now I need to set up my other machine in such a way that I can talk to it. Time to either configure NetBIOS and IPX in Linux... or just do the sane thing and install the TCP/IP stack on Windows 3.1 😀

Or both? 😈

PS: Yes, I do have a DHCP server on my router.

EDIT: Just a heads up that I've installed the TCP/IP stack and was able to successfully both ping and then mount network shares from my Linux PC. I'm happy 😁

Reply 7 of 8, by SyMBA

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Hi.

You can install TCP-IP/32-bit and access to internet or comunicate in your lan with other recent PC's.

There is Internet Explorer 16-bit (version 5.01 max) or Netscape Comunicator.
you can also use the 16-bit mIRC.

Good Luck in your Build.

Reply 8 of 8, by deksar

Posted on 
User metadata
Rank Member
Rank
Member

Hi @zerker,

I have the exact NIC on my Win 3.11 system, looking for its driver. Could you please let me know how to get it for that OS?

Best.

Go to top of page Go to top of page
Back to General Old Hardware
Close window
Close window