Announcement

Collapse

Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

EtherDFS - an ethernet drive for DOS

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    EtherDFS - an ethernet drive for DOS

    I've searched the forum, and I found no mention of EtherDFS.

    So I quote here the post by its author, Mateusz Viste, in the Usenet group comp.os.msdos.misc:

    """
    Hi all,

    Today I released a new version of EtherDFS: v0.7. Since one of the major
    changes of this version is that it became compatible with MS-DOS, I
    thought it would be relevant to announce it here (so far it was
    compatible only with FreeDOS).

    EtherDFS is an 'installable filesystem' TSR for DOS. It maps a drive from
    a remote computer (typically Linux-based) to a local drive letter, using
    raw ethernet frames to communicate. It runs on 8086+ and consumes 7K of
    RAM memory. It can be loaded high.

    http://etherdfs.sourceforge.net

    Mateusz

    """


    Also, he then released version 0.8 of EtherDFS, with this announcement in the same newsgroup:

    """
    Today I released a new version of EtherDFS (along with its server-side
    Linux companion, ethersrv-linux). EtherDFS v0.8 brings a few enhancements
    and compatibility improvements:

    Changelog:
    - improved self-detection to avoid loading EtherDFS twice,
    - added unloading support (/u),
    - fixed a FindFirst regression (fixes usage under 4DOS),
    - fixed SETATTR action when using a non-FreeDOS attrib command,
    - implemented the 'Seek From End' call,
    - minor memory optimizations,
    - makes sure the redirector API is available before installing,
    - support for multiple drive mappings.

    EtherDFS is available for download on the project's website:
    http://etherdfs.sourceforge.net

    Mateusz

    """

    Basically, you run the EtherDFS Linux daemon and then in the same ethernet LAN you run the EtherDFS DOS client in your MS-DOS/FreeDOS machine and map a network drive against the EtherDFS server. This is done through raw ethernet, so no TCP/IP stack is involved. You only need an ethernet NIC with a DOS-compatible packet driver on the DOS machine. It runs on 8086 and up MS-DOS machines. And it is open source.

    I haven't tried it yet, but I thought it could be of interest to the folks here.

    #2
    Looks promising, but as long as the server is Linux-only, I am afraid the audience will be extremely small. If he put up a DOS server program (working through DOSBox perhaps), I bet it will get more attention.
    My Retro Computing and Vintage Gaming Blog : http://nerdlypleasures.blogspot.com/

    Comment


      #3
      It looks interesting and i will see if it works on Windows 10 as it should be able to run Linux programs since the Anniversary Update.

      Comment


        #4
        WAIT WHAT?

        run linux programs in win10? surely you just.
        It is a mistake to think you can solve any major problems just with potatoes.

        Comment


          #5
          look here: https://www.howtogeek.com/249966/how...on-windows-10/

          Comment


            #6
            Originally posted by pietja View Post
            From the article : "There are some limitations here. This won’t work with server software, and it won’t work with graphical software. It’s intended for developers who want to run Linux command-line utilities on Windows." This is server software, although I don't know whether this program is what they are talking about.
            My Retro Computing and Vintage Gaming Blog : http://nerdlypleasures.blogspot.com/

            Comment


              #7
              grep, tail, find, dd, awk etc would all be good to have natively certainly.

              Comment


                #8
                Interesting.

                We talked a while back about adding ATAoE to XTIDE Universal BIOS (it was probably only really me that was really interested in it!). It's a standards based layer-2 protocol.

                https://en.m.wikipedia.org/wiki/ATA_over_Ethernet

                Comment


                  #9
                  Originally posted by pearce_jj View Post
                  grep, tail, find, dd, awk etc would all be good to have natively certainly.
                  Aren't they already, albeit not from MS? I have versions of all those for DOS dating back to the mid-1990s. Pretty sure there'd be native Windows versions too (though I haven't looked).

                  The 'server' limitation presumably means running a daemon, doesn't it? That would make sense as you'd need tighter integration for that to work.

                  Comment


                    #10
                    I doubt the EtherDFS daemon will run on the Windows 10 "Linux environment", because the EtherDFS daemon is coded to "attach itself" to the Linux eth0/whatever interface. However, you could run the EtherDFS daemon on a Linux VM.

                    I hope the author publishes a DOS-based EtherDFS daemon.

                    Comment


                      #11
                      Originally posted by Great Hierophant View Post
                      Looks promising, but as long as the server is Linux-only, I am afraid the audience will be extremely small. If he put up a DOS server program (working through DOSBox perhaps), I bet it will get more attention.
                      I think the point is the ability to transfer files between modern machines and vintage ones, that's why the server runs on a modern OS.
                      And this may be very useful for low-memory clients, eg. 5150 with 64KB RAM, where one can't run SMB/NCP/NFS clients.

                      Comment


                        #12
                        Originally posted by AlexC View Post
                        Aren't they already, albeit not from MS? I have versions of all those for DOS dating back to the mid-1990s. Pretty sure there'd be native Windows versions too (though I haven't looked).
                        Of course, it's called Cygwin, and I think there's at least one alternative project as well.

                        Comment


                          #13
                          Originally posted by Great Hierophant View Post
                          Looks promising, but as long as the server is Linux-only, I am afraid the audience will be extremely small. If he put up a DOS server program (working through DOSBox perhaps), I bet it will get more attention.
                          The protocol uses raw Ethernet frames, so it operates below TCP/IP and below even IPX. DOSBox doesn't emulate a packet driver (or Ethernet hardware) so there is no way to produce raw Ethernet frames from within it.

                          Likewise it would only work under Windows if they provide a raw packet API to their Linux compatibility layer, which I imagine they wouldn't as very few programs would ever use it. EtherDFS only uses this method in order to keep the client tiny. I think the only way to get it working under Windows would be to port it to run natively. Same for DOS, but then you'd have to have a retro server running DOS natively, which isn't really the point of EtherDFS, which is designed to link modern PCs with retro ones. Personally I plan to run a Linux server for my retro PCs anyway, so it suits me perfectly as-is! If you wanted your server to be a retro PC as well, you'd probably be better off running Novell or something on it so you are running real networking software from the same era as well.

                          ATA over Ethernet would be interesting but I imagine it would cause the client app to become a lot larger, having to translate BIOS calls into ATA commands. ATAoE also makes a disk image available over the network, so it's not used for sharing files. In this case, each retro PC would have its own large file on the server which is presented on the client machine as a single disk, and in order to share files you'd have to shut down the PC, mount the disk image locally, make your changes, unmount, then boot up the retro PC again. With EtherDFS it's a remote filesystem rather than a remote disk image, so multiple PCs can access the same network share at the same time, creating files that the other machines can see immediately.

                          Comment


                            #14
                            I run a hyper-V server (homelab) here at the house that's the primary storage and compute box. It runs a bunch of junk like Emby, a DC, a torrent server, Server Essentials 2012 R2, all kinds of stuff for the house.

                            One of the things I run is a Server 2003 box so that Windows 3.1 and 98 have a place to log in and store files over the network. Those OS's are just to old to log into the newer OS's via SMB. For DOS, the Microsoft network stuff uses way too much RAM especially if you want to build a boot disk and do some installs over the network. I'll fire up an Ubuntu VM for this and try it out, I'll mount the Server 2003 share on the Ubuntu box and then try to share it out with the ethersrv-linux package.

                            Comment


                              #15
                              This is essentially a lightweight netware that uses linux as the file server. If it works it's an incredibly lightweight way to make a linux directory just show up under DOS as a drive letter. This can breathe new life into systems that can use a parallel-port xircom adapter but can't have a hard disk, like early laptops. I keep meaning to test it out, and will report back when I do.

                              For those worried about "I don't run Linux", you can easily run Linux as a VM inside whatever you are running (ie. use virtualbox, qemu, etc.). And you can also cross-mount between host OS and VM OS. It's not as elegant as running Linux by itself but it does work.
                              Offering a bounty for:
                              - A working Sanyo MBC-775 or Logabax 1600
                              - Music Construction Set, IBM Music Feature edition (has red sticker on front stating IBM Music Feature)

                              Comment

                              Working...
                              X