Brian L. Johnson wrote: > > Well, that didn't go well... I loaded the built-in network stuff > along with mstcpip, and as it wanted, I rebooted. After reboot, > Windows startup would bomb with "Not enough extended memory" (to > start Windows)... The mem command shows 502k free, and 31m of XMS > (the computer has 32m of RAM total) > > Had to restore the system.ini file (uninstalling network support in > the process) to get Windows to load. Well, I didn't say it would run in one go :) It took me a few tries, but now have it working for over three years now, totally without worries or crashes. You did throw out all other protocols after addeng TCP/IP, didn't you? Anayway, the setup dialogs are a bit buggy. So try hardcoding the INI files. I have a 3c509 installed, here are my settings. (Actually, I also have a DEC21041 installed, those settings have been deleted.) It is asumed the 3COM is set to use I/O port 300 and IRQ 10. (The windows driver auto detects the IRQ). First, PROTOCOL.INI. This is where the main network bindings are stored. This is ALL that should be there: [network.setup] version=0x3110 netcard=tcm$elnk3,1,TCM$ELNK3,2 transport=tcpip-32r,MSTCP32 lana0=tcm$elnk3,1,tcpip-32r [TCM$ELNK3] IOADDRESS=0x300 [ELNK3] Adapters=TCM$ELNK3 [MSTCP32] BINDINGS=TCM$ELNK3,DEC$21041 LANABASE=0 Second, SYSTEM.INI, holding the drivers amd settings. Add the following lines to their respective sections: [boot] network.drv=wfwnet.drv [boot.description] network.drv=Microsoft Windows Network (version 3.11) secondnet.drv=There is no extra network installed [386Enh] ; load all protected mode drivers network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386 transport=vip.386,vdhcp.386,vtdi.386,vtcp.386,vnbt.386 netmisc=ndis.386,wsock.386,wstcp.386 netcard3=elnk3.386 [Network] ; Windows networking stuff Winnet=wfwnet/00025100 Multinet=nonet EnableSharing=Yes FileSharing=Yes PrintSharing=Yes UserName=ERWIN Workgroup=CALMIRA ;) ComputerName=CC15892-B ; change to LAL Comment= LogonDisconnected=Yes LogonValidated=no AutoLogon=Yes StartMessaging=No LoadNetDDE=No LMLogon=0 LogonDomain= Priority=40 Reshare=yes CacheThisPassword=yes Reconnect=yes [Network Drivers] DevDir=C:\WINDOWS LoadRMDrivers=No [DDEShares] ; Common system (and fun) shares 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 [MSTCP] ; Read MSTCP.HLP for more finetuning info! DeadGWDetect=0 DefaultRcvWindow=64240 DefaultTTL=128 PMTUDiscovery=0 Interfaces=tcm$elnk30,dec$210410 [DNS] HostName=cc15892-b DomainName=groni1.gr.home.nl DNSServers=212.120.66.194,212.120.66.195 DNSDomains= [tcm$elnk30] ; All 0.0.0.0 means: use DHCP Binding=tcm$elnk3 Description=3Com EtherLink III (3C5X9) DefaultGateway=192.168.0.1 ; TUX IPAddress=192.168.0.2 IPMask=255.255.255.0 MaxMTU=1500 [NBT] ; Netbios stuff LANABASE=0 EnableProxy=0 EnableDNS=0 If you just add the above settings to your networkless WfW setup, you should have a working network. When you boot up, first go to Network in control panel to set user and password. > >Put one of the above packages on MS-DOS and throw Samba on your linux > >box Samba acts as an NT Server towards LanMan clients. > > Tried that... I installed msclient, configured it et al. Named the > win31 computer "lal", and the Linux box has always been named "tux", > both hostname-wise, and Samba-wise.. > > So I start Samba on Tux with it set as browseable, browse master, > et al... And "net use" on Lal can't see Tux for anything. Tux > doesn't even exist to Lal. I never seriously played with the DOS networking, but this is a common problem. Have you set the workgroup of both boxes to the same name? You haven't set either box to act as/look for a domain instead of workgroup? is the 3COM working? Can you ping the other machine? > Tux runs an Intel EtherExpress Pro 10/100, which although is not > quite as ubiquitous, is still a fairly well supported card. I have that one sitting in my NT box :) > [sigh] What else can we try? See above... -- Erwin Dokter mailto:edokter@xxxxxxx http://members.home.nl/edokter -- To unsubscribe, send a message to ecartis@xxxxxxxxxxxxx with "unsubscribe calmira_tips" in the body. OR visit //freelists.org