• DOSBOX and NE2000 emulation

    From Kurt Weiske@1:218/700 to All on Wed Apr 15 22:33:01 2020

    My version of DOSBOX (DOSBOX-SVN Daum) supports the NE2000 patch. I was able to get it working with my network, and loaded the MTCP software on it. Worked like a charm, once I replaced NPCAP with the older WINPCAP software.

    It's fun being able to play with DOS internet software again - next step is to get Windows for Workgroups talking to the network emulation...
    --- SBBSecho 3.10-Win32
    * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)
  • From Ryan Fantus@1:218/820 to Kurt Weiske on Wed Apr 15 23:50:45 2020
    My version of DOSBOX (DOSBOX-SVN Daum) supports the NE2000 patch. I was able to get it working with my network, and loaded the MTCP software on it. Worked like a charm, once I replaced NPCAP with the older WINPCAP software.

    Can you paste a link with a howto guide or something? I would love to get
    this working myself!

    --- Mystic BBS v1.12 A46 2020/04/13 (Linux/64)
    * Origin: monterey bbs (1:218/820)
  • From Kurt Weiske@1:218/700 to Ryan Fantus on Thu Apr 16 10:02:00 2020
    Ryan Fantus wrote to Kurt Weiske <=-

    My version of DOSBOX (DOSBOX-SVN Daum) supports the NE2000 patch. I was able to get it working with my network, and loaded the MTCP software on it. Worked like a charm, once I replaced NPCAP with the older WINPCAP software.

    Can you paste a link with a howto guide or something? I would love to
    get this working myself!

    I'll put a final draft up on the realitycheckBBS.org web site, but here's
    what I've got so far. It's finicky, sometimes DHCP will fail 3 times out of
    4, but work the 4th time.


    +------------------------------------------------------------+
    | CONFIGURING DOSBOX with NE2000 emulation and mTCP software |
    +------------------------------------------------------------+


    1. Find a fork of DOSBOX that supports the NE2000 patch. I used DOSBOX-SVN Daum from 2014, which allegedly is less buggy than the 2015 version.

    2. Confirm the following section in your dosbox.conf file:

    [ne2000]
    # ne2000: Enable Ethernet passthrough. Requires [Win]Pcap.
    # nicbase: The base address of the NE2000 board.
    # nicirq: The interrupt it uses. Note serial2 uses IRQ3 as default.
    # macaddr: The physical address the emulator will use on your network.
    # realnic: Specifies which of your network interfaces is used.
    # Write 'list' here to see the list of devices in the
    # Status Window. Then make your choice and put either the
    # interface number (2 or something) or a part of your adapters
    # name, e.g. VIA here.
    ne2000=true
    nicbase=300
    nicirq=3
    macaddr=AC:DE:48:88:99:AA
    realnic=list

    3. Install WinPCAP from https://www.winpcap.org/. This software is no longer supported, but I couldn't get npcap, the replacement, to to work.

    4. Run DOSBOX and look in the status window. You should see a list of
    network interfaces like so:

    Network Interface List
    -----------------------------------
    1. rpcap://\Device\NPF_{02C5160E-3B81-40F1-BF97-EC9384205B78}
    (Network adapter 'VMware Virtual Ethernet Adapter' on local host)

    2. rpcap://\Device\NPF_{33E4D987-523A-4803-978F-4C78A0E1CDDD}
    (Network adapter 'TAP-Windows Adapter V9' on local host)

    3. rpcap://\Device\NPF_{37DAC71E-9617-4516-87DE-F2DCB425E1D6}
    (Network adapter 'Realtek PCI GBE Family Controller' on local host)

    4. rpcap://\Device\NPF_{157C99AB-2743-42D2-B58D-C33195E00FE1}
    (Network adapter 'Microsoft' on local host)

    5. rpcap://\Device\NPF_{FDD94540-D88C-4E05-A0D5-C14C35421D81}
    (Network adapter 'VMware Virtual Ethernet Adapter' on local host)

    5. Edit the [ne2000] stanza in your dosbox.conf to read "realnic=<Your NIC number>. Exit DOSBOX.

    6. Download the Crynwyr NE2000.com packet driver from http://crynwr.com/drivers/ to your DOSBOX drive.

    7. Download the MTCP suite from https://www.brutman.com/mTCP/mTCP.html.

    mTCP is a set of TCP/IP applications for personal computers running PC-DOS, MS-DOS, FreeDOS, and other flavors of DOS. The applications include:

    DHCP: a DHCP client for auto-configuring your machine for use on your
    network.
    FTP: an FTP client for transferring files across the network at high speed. FTPSRV: a high performance FTP server that allows multiple connected
    clients, a sandbox area for untrusted users, etc.
    HTGET: the HTGet program for downloading files/content from web (HTTP)
    servers
    HTTPSERV: an HTTP server supporting HTTP 0.9, 1.0, 1.1
    IRCJR: the IRCjr IRC (Internet Relay Chat) client for chatting on IRC networks.
    NC: the Netcat command which can be used to send and receive data easily across a network.
    PING: the Ping command for checking basic network connectivity.
    PKTTOOL: A packet sniffer and diagnostic tool for packet drivers
    SNTP: an SNTP client for getting the current date and time from public
    servers on the Internet.
    TELNET: a Telnet client for connecting to Unix systems, BBS systems, or any computer that supports Telnet.

    Copy the files to a folder \mtcp in your DOSBOX drive and in the
    mtcp\samples\ folder, copy the sample .cfg file to your \mtcp directory.
    Edit the file to suit your configuration, and add SET MTCPCFG=<location of your .cfg file> to the autoexec section of your DOSBOX.conf.

    8. Re-run DOSBOX. From within DOSBOX, run the following commands:

    NE2000 0x60
    Packet driver for NE2000, version 11.4.3
    Packet driver skeleton copyright 1988-93, Crynwr Software.
    This program is freely copyable; source must be available; NO WARRANTY.
    See the file COPYING.DOC for details; send FAX to +1-315-268-9201 for a copy.

    System: [345]86 processor, ISA bus, Two 8259s
    Packet driver software interrupt is 0x60 (96)
    Interrupt number 0x9 (9)
    I/O port 0x300 (768)
    My Ethernet address is AC:DE:48:88:99:AA

    (The line above should correspond to the macaddr entry in dosbox.conf)


    DHCP
    mTCP DHCP Client by M Brutman (mbbrutman@gmail.com) (C)opyright 2008-2020 Version: Mar 7 2020

    Timeout per request: 10 seconds, Retry attempts: 3
    Sending DHCP requests, Press [ESC] to abort.

    DHCP request sent, attempt 1: Offer received, Acknowledged

    Good news everyone!

    IPADDR nnn.nnn.nnn.nnn
    NETMASK nnn.nnn.nnn.nnn
    GATEWAY nnn.nnn.nnn.nnn
    NAMESERVER nnn.nnn.nnn.nnn
    LEASE_TIME 86400 seconds

    Settings written to 'c:\mtcp\mtcp.cfg'



    At this point, the MTCP suite should work.







    ... Start where you are. Use what you have. Do what you can.
    --- MultiMail/DOS v0.52
    * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)
  • From Ryan Fantus@1:218/820 to Kurt Weiske on Thu Apr 16 16:59:31 2020
    I'll put a final draft up on the realitycheckBBS.org web site, but
    here's what I've got so far. It's finicky, sometimes DHCP will fail 3 times out of 4, but work the 4th time.

    Thanks! I'll give this a shot.

    --- Mystic BBS v1.12 A46 2020/04/13 (Linux/64)
    * Origin: monterey bbs (1:218/820)
  • From Thierry Olmedo@2:250/1 to Kurt Weiske on Sun Apr 19 18:24:05 2020

    Hello Kurt!

    15 Apr 20 22:33, you wrote to all:

    My version of DOSBOX (DOSBOX-SVN Daum) supports the NE2000 patch. I
    was able to get it working with my network, and loaded the MTCP
    software on it. Worked like a charm, once I replaced NPCAP with the
    older WINPCAP software.
    It's fun being able to play with DOS internet software again - next
    step is to get Windows for Workgroups talking to the network
    emulation...

    Hello! , i also use an emulator to test things but i use PCem, it is the closest thing to the real hardware that i have tried, i have my old machines and i use them all the time , but it is easier for me to test first in emulator and later in real hardwar
    best regards

    Thierry


    --- FMail/386 1.60.GPL
    * Origin: 386_40mhz-8MB_ram/DOS6.22/IBM_TCP-IP/Binkd-DOS/Fmail1.6/
  • From Thierry Olmedo@2:250/1 to Kurt Weiske on Sun Apr 19 18:30:48 2020

    Hello Kurt!

    16 Apr 20 10:02, you wrote to Ryan Fantus:
    here's what I've got so far. It's finicky, sometimes DHCP will fail 3 times out of 4, but work the 4th time.
    +------------------------------------------------------------+
    | CONFIGURING DOSBOX with NE2000 emulation and mTCP software |
    +------------------------------------------------------------+
    Exelent guide ! , thanks !

    regards


    Thierry


    --- FMail/386 1.60.GPL
    * Origin: 386_40mhz-8MB_ram/DOS6.22/IBM_TCP-IP/Binkd-DOS/Fmail1.6/
  • From Kurt Weiske@1:218/700 to Thierry Olmedo on Thu Apr 23 09:23:00 2020
    Thierry Olmedo wrote to Kurt Weiske <=-

    Hello! , i also use an emulator to test things but i use PCem, it is
    the closest thing to the real hardware that i have tried, i have my old machines and i use them all the time , but it is easier for me to test first in emulator and later in real hardwar

    PCEM looks very interesting; I'll need to take a look at it. The one thing stopping me from running a purely emulated environment like setting up a DOS VM or PCEM has been getting files to/from the host OS to the guest. With DOSBox, I can copy the files directly from the guest into a folder. I've
    been trying to find a way to make ISOs of folders in the host appear on the guest, but I'm not there yet.


    ... What is the reality of the situation?
    --- MultiMail/XT v0.52
    * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)