Ralf: Thanks for responding. I've been using various home networks for 25 years or so, but I'll admit I know just enough about networking to be dangerous. In any case, I set networking up on this Freedos machine using the help pages at http://wiki.freedos.org/wiki/index.php/Networking_FreeDOS. I couldn't find a packet driver for my onboard nic, so I went with a ndis driver (RTGND.DOS).
Anyway, hopefully, the following will answer most of your questions. *** C:\NET directory *** DHCP.COM NETBIND.COM PING.EXE PROTMAN.DOS PROTMAN.EXE PROTOCOL.INI RTLGND.DOS WATTCP.CFG *** PROTOCOL.INI file *** ;--- PROTOCOL.INI --- [protman] DriverName=PROTMAN$ [RTGND] DriverName=RTGND$ medium=_auto [PKTDRV] drivername=PKTDRV$ bindings=RTGND intvec=0x60 chainvec=0x68 *** FDCONFIG.SYS file *** SET DOSDIR=C:\FDOS !COUNTRY=001,858,C:\FDOS\BIN\COUNTRY.SYS !LASTDRIVE=Z !BUFFERS=20 !FILES=40 !MENUCOLOR=7,0 MENUDEFAULT=1,5 MENU 1 - Load FreeDOS with JEMMEX, no EMS (most UMBs), max RAM free MENU 2 - Load FreeDOS with JEMM386 (Expanded Memory) MENU 3 - Load FreeDOS low with some drivers (Safe Mode) MENU 4 - Load FreeDOS without drivers (Emergency Mode) 12?DOS=HIGH 12?DOS=UMB 12?DOSDATA=UMB 1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG 234?DEVICE=C:\FDOS\BIN\HIMEMX.EXE 2?DEVICE=C:\FDOS\BIN\JEMM386.EXE X=TEST I=TEST I=B000-B7FF NOVME NOINVLPG 34?SHELL=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\FDAUTO.BAT 12?SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\FDAUTO.BAT DEVICE=C:\NET\PROTMAN.DOS /I:C:\NET DEVICE=C:\NET\RTGND.DOS DEVICE=C:\NET\DIS_PKT9.DOS *** FDAUTO.BAT *** @ECHO OFF set DOSDIR=C:\FDOS set LANG=EN set TZ=UTC set PATH=%dosdir%\BIN if exist %dosdir%\LINKS\NUL set PATH=%path%;%dosdir%\LINKS set PATH=%path%;C:\NET set NLSPATH=%dosdir%\NLS set HELPPATH=%dosdir%\HELP set TEMP=%dosdir%\TEMP set TMP=%TEMP% set BLASTER=A220 I5 D1 H5 P330 set DIRCMD=/P /OGN /Y set COPYCMD=/-Y set OS_NAME=FreeDOS set OS_VERSION=1.3-RC3 set autofile=C:\FDAUTO.BAT set cfgfile=C:\FDCONFIG.SYS alias cfg=edit %cfgfile% alias auto=edit %autofile% alias reboot=fdapm warmboot alias reset=fdisk /reboot alias halt=fdapm poweroff alias shutdown=fdapm poweroff if not exist %dosdir%\bin\vinfo.com goto Only8086 vinfo /m if errorlevel 3 goto Support386 if errorlevel 2 goto Support286 :Only8086 if "%config%"=="2" goto END MEM /C /N goto FINAL :Support286 if "%config%"=="3" goto END LH FDAPM APMDOS CTMOUSE MEM /C /N goto FINAL :Support386 if "%config%"=="4" goto END LH FDAPM APMDOS rem LH SHARE rem if EXIST %DOSDIR%\BIN\DOSLFN.COM LH DOSLFN REM NLSFUNC %dosdir%\BIN\COUNTRY.SYS REM DISPLAY CON=(EGA),858,2) REM MODE CON CP PREP=((858) %dosdir%\CPI\EGA.CPX) REM KEYB US,858,%dosdir%\bin\keyboard.sys REM CHCP 858 REM MKEYB UK CTMOUSE SHSUCDX /QQ /D3 REM LH SHSUCDHD /QQ /F:FDBOOTCD.ISO DEVLOAD /H /Q %dosdir%\BIN\UDVD2.SYS /D:FDCD0001 REM DEVLOAD /H /Q %dosdir%\BIN\UIDE.SYS /H /D:FDCD0001 /S5 SHSUCDX /QQ /~ /D:?SHSU-CDR,D /D:?SHSU-CDH,D /D:?FDCD0001,D /D:?FDCD0002,D /D:?FDCD0003,D MEM /C /N SHSUCDX /D C:\NET\NETBIND.COM set ip=10.0.0.40 set netmask=255.255.255.0 set gateway=10.0.0.1 set dns=10.0.0.1 :FINAL if exist %dosdir%\bin\fdnet.bat call %dosdir%\bin\fdnet.bat start if exist %dosdir%\bin\fdassist.bat call %dosdir%\bin\fdassist.bat if exist %dosdir%\bin\welcome.bat call %dosdir%\bin\welcome.bat :END *** WATTCP.CFG *** my_ip=10.0.0.40 netmask=255.255.255.0 nameserver=10.0.0.1 gateway=10.0.0.1 *** boot *** Ethernet board driver installs ok. Modules PROTMAN, RTGND, DIS_PKT9 install ok. NETBIND.COM reports ethernet board's address id D05099769204. *** NTCPDRV.EXE *** NTCPDRV.EXE installs Trumpet TCP version 3.1 Interrupt = 0x61 MAC/DIS converter packet driver version 9 6 ok and reports my ip = 10.0.0.40 netmask = 255.255.255.0 gateway = 10.0.0.1 *** ping *** ping 10.0.0.40 from Freedos machine gets no response. ping 10.0.0.40 from Windows machine gets no response. *** DHCP *** DHCP reports Packet driver failed *** questions/comments *** I'm not sure about NTCPDRV reporting interrupt 0x61 relates to PROTOCO.INI's intvec=0x60? Also not sure why NTCPDRV reports MAC/DIS converter "packet driver" when I've installed a ndis adapter driver? For what it's worth, I've tried 3 different ethernet cables. On Tue, Nov 3, 2020 at 12:46 AM Ralf Quint <freedos...@gmail.com> wrote: > On 11/2/2020 6:54 PM, Marv wrote: > > Freedos noob here. I've been running old Dos programs like Wordstar, > Supercalc, etc. ok on Freedos for a couple of weeks. Now I'm trying to get > it on my LAN so I can move files around easier. > > I'm using an ASRock N3150B-ITX (circa 2015) with an onboard ethernet > adapter. Specs say: PCIE x1 Gigabit LAN 10/100/1000 Mb/s, Realtek RTL8111GR. > > NICSCAN says vendor is 10EC (Realteck) and device is 8168 (RTL8111/8168B > PCI Express Gigabit Ethernet controller). > > I finally found the right ndis driver for the adapter. I can now get thru > the boot process without any errors, and Netbind shows the adapter's > hardware address. > > My problem or question is the hardware address Netbind shows on boot > doesn't show up in a listing of IP addresses on my router nor does ARP list > it. > > Does the IP address only get assigned to the hardware address when a > program uses WATTCP.CFG? > > I think I have my WATTCP.CFG is setup correctly, but I'm not entirely > sure. I want to use a static IP address. But since the device/hardware > address doesn't show up on the router, I can't turn it into a static IP > there. I've been assuming setting my_ip to an unused IP in WATTSCP.CFG will > create the static IP, but apparently not? > > I know this is not a Freedos question or issue, but how and when does an > IP address get assigned to a device in this kind of network? > > Well, you do not say what kind of network stack you are actually using. > You need more than just the driver for the NIC, but also software that > provides the whole (TCP/)IP stack. With that in place, you should have the > option to select either to use a static IP (with all associated info like > netmask and gateway) or get this info assigned via DHCP (which uses the MAC > address as the physical identifier). > > Also not sure where you are looking for the device/hardware address on > your router, a static address isn't likely to show up at all (ok, some > routers have some "network view", which shows active device by IP address). > Most importantly, you need to make sure that the static IP info that you > are entering matches in IP address, netmask and gateway the LAN side > interface of your router. If that is correct what you entered, well, that > is hard to tell without you providing some real info about that... > > Ralf > > > > > > > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon> > Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link> > <#m_3893177822728162183_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > _______________________________________________ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user >
_______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
