Hi Bryan,
> PCISCAN showed: > Bus 1 > Dev C > Func 0 > Slot 2C > Vend 0006 > Dev. 100E > Class Name Network > Subclass Name Ethernet. In case the vendor is something else, this might be an Intel 82540EM Gigabit LAN controller. If 0006:100e is indeed correct, it is something not seen elsewhere. Intel actually does provide DOS drivers for this chip (but they say the stopped supporting DOS after 2019) which contains at least NDIS support. I have not checked whether it contains a packet driver as well: https://downloadcenter.intel.com/download/29138/Intel-Ethernet-Adapter-Drivers-for-MS-DOS-?wapkw=82540EM If you have only NDIS, you also have to install DIS PKT: http://wiki.freedos.org/wiki/index.php/Networking_FreeDOS_-_NDIS_driver_installation As you see, several other drivers can be required to get a MS CLIENT "stack" which would let you access, but only old versions of, Windows net drives and printers: Load PROTMAN /I:X:\Y, then your network controller driver, then DIS PKT, all three as device drivers in either config.sys or using DEVLOAD, in that order, with X:\Y\ being the directory where your config text file PROTOCOL.INI resides (adjust accordingly). The content of the text file is at least: [protman] DriverName=PROTMAN$ [YOURDRIVERNAME] DriverName=YOURDRIVERNAME$ [PKTDRV] drivername=PKTDRV$ bindings=YOURDRIVERNAME intvec=0x60 chainvec=0x68 See also the documentation which gets installed when you unpack the DOS driver package from Intel. Apart from the 2 *.DOS files (device drivers, note the unusual name *.DOS instead of *.SYS) you will also need the PROTMAN and NETBIND command line tools and TSRs. All drivers and tools may have problems with being loaded into UMB (devicehigh, loadhigh etc.) so you should avoid that until you have tested whether it works for your PC. You have to start NETBIND after loading the three *.DOS devices to activate things. The PROTMAN exe will be started automatically by the PROTMAN device, but you can also run it manually later for other purposes. Depending on the type of your printer, you can install the mTCP set of utilities as explained in http://wiki.freedos.org/wiki/index.php/Networking_FreeDOS_-_mTCP As explained, you need to set MTCPCFG=c:\somewhere\yourfiletcp.cfg which has to set your PACKETINT (0x60), IPADDR, NETMASK, GATEWAY, NAMESERVER and MTU (1500). You can also use DHCP instead: Then, only PACKETINT and the host name which you want to give your DOS PC (e.g. mydospc) have to be set and all other settings will be requested from your router, modem or other available DHCP provider. If the mTCP tools do not remember the DHCP answers, it can mean that they have to ask before each activity, so you may prefer non-DHCP for better speed, but I do not know whether or not mTCP remembers DHCP data across calls? Use the NC (netcat) tool to send files to the printer: http://wiki.freedos.org/wiki/index.php/Netcat nc -target 192.168.2.20 9100 -bin < testfile.txt In this example, 192.168.2.20 would be the IP address of your printer, which you will have to look up (it may be shown on your printer display, or you look at what Linux or Windows says about your printer) and 9100 is a popular port for streaming "page (or printer?) definition language" data to printers. Depending on your printer, it might accept all sorts of file formats, as explained here: https://en.wikipedia.org/wiki/Page_description_language However, I would expect that PostScript, PDF, ESC/P, HP PCL and plain text have reasonable chances to be supported (at least one of them) by your printer if it is a printer with sufficient built-in intelligence. According to the website https://support.brother.com/g/b/spec.aspx?c=au&lang=en&prod=hl3150cdn_us_as_cn the Brother HL-3150CDN is unfortunately a non-intelligent GDI printer. You have to send pre-generated raw pixel data to the printer and you will probably NOT find a tool which converts your DOS text into pixel data in DOS If you had a HL-3170CDW, it would be intelligent enough to understand HP PCL6 and a Brother PostScript 3 dialect. In short, while your PC network controller is supported by DOS, you will not be able to use your printer without the help of other operating systems in DOS because the printer expects too much of its work to be done by you. Regards, Eric _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
