josephdaniel
Experienced Member
Curious, is it possible to back up a IBM 5160 with a functioning network card to a local NAS or possibly some sort of remote back up server? If so how would Someone go about getting it to work?
Oh sure... probably the easiest way would be to use an FTP client to connect to the FTP server on the NAS and dump the files into the directory (or zip them up first and then dump the zip on there).
Another option is to install Microsoft Network Client, map a NAS drive, and copy files to it (e.g. using xcopy). This works nicely with Linux and Samba too...
If I recall correctly Microsoft Network Client requires MS-DOS 3.2 or later.
...The only change I'd suggest is to use -e0 on the pkzip command-line so that no compression is used if the computer doing the compression is very slow (ie. 8088/8086). This is because the time it takes to compress is an order of magnitude longer than the time it takes to transmit uncompressed data.
I have tried this, MS-NET client requires a 286, and it wont work with a NEC V20/30, its checking for a REAL 286, at least in the version I have, but I do go this method on my 286 and faster boxen, they all map drive letters to my NAS box for file transfer/backups.
I have tried this, MS-NET client requires a 286, and it wont work with a NEC V20/30, its checking for a REAL 286, at least in the version I have, but I do go this method on my 286 and faster boxen, they all map drive letters to my NAS box for file transfer/backups.
Well, it's strange problem. MSLANMAN works fine with a V20-equipped system. I wonder if the issue with MS-NET is simply the installation program...
tar is available for MS-DOS, which gives you a portable way to archive your files:
http://ftp.gnu.org/gnu/tar/
Johnathan Disney came up with a method for doing this on 8088 that used DOS 3.30, Microsoft LAN Manager v2.2c, and NetBEUI only (so it required a custom windows 2000 or NT server, but this can probably easily be solved nowadays with virtualization). He had a network drive working on a PCjr with a single floppy disk and a Xircom PE3PD, and the memory usage wasn't super-terrible.
He wrote up a very long, nice document with complete steps but I'm having trouble locating him -- he never gave me permission to distribute it, so hopefully I can track him down and get his permission to share the doc.
Thanks guys. I currently have PC-DOS 2.1 I am hoping to get 6.22 on there for greater compatibility/flexibility. I have mtcp but I coulden't figure out how to get the FTP server to work...
Thanks guys. I currently have PC-DOS 2.1 I am hoping to get 6.22 on there for greater compatibility/flexibility. I have mtcp but I coulden't figure out how to get the FTP server to work...
I think the instructions are pretty good - I've spent days on them. What part did you have problems with?
Johnathan Disney came up with a method for doing this on 8088 that used DOS 3.30, Microsoft LAN Manager v2.2c, and NetBEUI only (so it required a custom windows 2000 or NT server, but this can probably easily be solved nowadays with virtualization). He had a network drive working on a PCjr with a single floppy disk and a Xircom PE3PD, and the memory usage wasn't super-terrible.
He wrote up a very long, nice document with complete steps but I'm having trouble locating him -- he never gave me permission to distribute it, so hopefully I can track him down and get his permission to share the doc.
Johnathan Disney came up with a method for doing this on 8088 that used DOS 3.30, Microsoft LAN Manager v2.2c, and NetBEUI only (so it required a custom windows 2000 or NT server, but this can probably easily be solved nowadays with virtualization). He had a network drive working on a PCjr with a single floppy disk and a Xircom PE3PD, and the memory usage wasn't super-terrible.
He wrote up a very long, nice document with complete steps but I'm having trouble locating him -- he never gave me permission to distribute it, so hopefully I can track him down and get his permission to share the doc.
I've pinged Jonathan about that very document in the last few months. He is still out there and remembers it. It will come eventually.
Installer would actually install, it was upon reboot loading the network that it complained about needing a 286, but it might have just been the version I was using, never dug much deeper. Just used mTCP on my 8086 (with V30) box.
That is a very misleading error. It is not MS LANMAN that is erroring out, it is the driver for your NIC. MS LANMAN works fine from 8088 and up. In fact both Client and LANMAN will run on an 8088. I had the same issue on my 5170 except I was getting a "req. 80386" error. It turns out, in my case, the drivers for the 3COM 3C515-TX (fast Ethernet 16bit ISA NIC) will only work on a 386 and up not a 286.