5 ms·
EtherDFS – The Ethernet DOS File System
- deleted 9y ago[deleted]
- fusiongyro 9y agoNot a problem most of us have in 2017. I wonder what the use case is for having a bunch of DOS machines.
- slco1 9y agoRetro computing is a bit of a hobby for some of us. I'll find the program very useful personally.
- kyberias 9y agoFrom the page: 'For years, I was using LapLink to transfer files between my various "retro" computers.'
- sigstoat 9y agountil 4-5 years back, my wife's lab still owned some old scientific equipment whose control software ran on DOS. they'd dumped another piece of equipment a few years before that which ran an embedded DOS system, and booted/ran off of a 1.44MB floppy. (not a good design decision for long lasting hardware.) both pieces of hardware were sold to folks who intended to use them.
- lightedman 9y agoDOSBox really does suck in some specific use cases and thus a native MS/PC-DOS is needed.
- stuaxo 9y agoProbably doesn't help in those situations, but there has been a lot of progress in the last year or so on DOSEMU https://github.com/stsp/dosemu2 https://github.com/stsp/dosemu2
- lightedman 9y agoUnfortunately you're correct - these use case scenarios do not work with any emulation.
- pkaye 9y agoBefore 10 years ago it was used heavily in PC hardware development and testing. Basically DOS as a bootloader that gives you full access to the computer hardware. Windows had too many things going on in the background to give that control plus the driver development is not so easy. These days Linux seems the answer since you have the source code and can trim it down to the minimal needed for control. I'd have killed for a networking file system for DOS back then. I think we ended up using something like a lap link protocol to transfer files from my development system to the test systems.
- hazeii 9y agoDOS (without or with older hardware) is great for hardware hacking, e.g. it's trivial to write code to directly access hardware and find out how it works; the information can then be used to e.g. implement a linux driver. Note that performance is also very good as well, e.g. for bit-banged I/O just disable interrupts for minimal latency and maximum throughput. Also for simple network-attached embedded devices that have to be ultra-reliable, there isn't much to go wrong.
- cat199 9y agoSidenote: If anyone wants to make a new-school 64 bit DOS-alike, that would be really kool. thx.
- throwanem 9y agoFreeDOS seems to have a 64-bit version on Sourceforge, but it's a year stale and I can't vouch for its functionality. Still, might be worth a look: https://sourceforge.net/projects/dos64/ https://sourceforge.net/projects/dos64/
- hazeii 9y agoMS-Net is another option for connecting DOS boxes to linux servers running samba - it's a neat way of running diskless DOS boxes. https://en.wikipedia.org/wiki/MS-Net https://en.wikipedia.org/wiki/MS-Net
- jaclaz 9y ago>MS-Net is another option for connecting DOS boxes to linux servers running samba - it's a neat way of running diskless DOS boxes. Actually it seems to me like a non-option or a non-available option (unless one finds the program and license on some garage sale or the like).
- hazeii 9y agoIt's on the MS FTP server (which seems to down at present - withdrawn?). There are plenty of mirrors - first one on Google is:- http://www.kompx.com/en/network-setup-in-dos-microsoft-network-client.htm http://www.kompx.com/en/network-setup-in-dos-microsoft-netwo...
- jaclaz 9y agoWell, that is the "normal" MS DOS network driver/client, not the MS-NET you linked to on Wikipedia, which is much earlier and was (mainly) "server side": https://en.wikipedia.org/wiki/MS-Net https://en.wikipedia.org/wiki/MS-Net >The system also supplied the program REDIR.EXE, which allowed transparent file access from DOS machines to any MS-Net based server.
- mixmastamyk 9y ago> Read this article I posted on my gopher. :D