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

    Originally posted by keenerb View Post
    I verified it IS still working for me; I had upgraded my raspberry pi 3 in my little mac portable system to a 4. I'm using the :: c-d syntax, it just works fine.

    [ATTACH=CONFIG]61351[/ATTACH]

    Are you sure your server and client version match?
    Sorry for going away a bit from the original topic, but I see that you run a virtual floppy?
    Is it something like; https://code.google.com/archive/p/xt...ialDrives.wiki
    Pls point me in a good direction for a floppy emulator, so then I maybe do not need to reuse the few old 5.25" floppy disks I have left for just creating install / boot disks...

    I'm kind of starting to rediscover these old computers and it seems a lot of convenient things been added since...
    And I see that Trixter is writing in this tread, I must take the opportunity (even if only seen on you tube as I have no 8088 machine) - your demos are incredible!
    I did a part of the "coding" for Pinball Fantasies (and Illusions) PC version back in the 1990s, but since then I have done other things and almost not touched any old computer... Though, I saved some stuff from back then, that now come up to the surface during some basement cleaning. Sadly I did throw away some CRTs, IBM computers and stuff that I really would like to have now, but it is 20 or more years ago... Anyway. I will set the machines on a physical network tonight to see if this fixes my problem, thanks for all good advises!

    Comment


      Originally posted by JohanLu View Post
      Sorry for going away a bit from the original topic, but I see that you run a virtual floppy?
      Is it something like; https://code.google.com/archive/p/xt...ialDrives.wiki
      Pls point me in a good direction for a floppy emulator, so then I maybe do not need to reuse the few old 5.25" floppy disks I have left for just creating install / boot disks...

      I'm kind of starting to rediscover these old computers and it seems a lot of convenient things been added since...
      And I see that Trixter is writing in this tread, I must take the opportunity (even if only seen on you tube as I have no 8088 machine) - your demos are incredible!
      I did a part of the "coding" for Pinball Fantasies (and Illusions) PC version back in the 1990s, but since then I have done other things and almost not touched any old computer... Though, I saved some stuff from back then, that now come up to the surface during some basement cleaning. Sadly I did throw away some CRTs, IBM computers and stuff that I really would like to have now, but it is 20 or more years ago... Anyway. I will set the machines on a physical network tonight to see if this fixes my problem, thanks for all good advises!
      I am actually using "ethflop", which is written by the same person who wrote "etherdfs". It replaces an existing floppy drive with a network-mounted floppy image, but you can't use it for booting sadly. A Gotek/HXC device is your best bet for a replacement virtual floppy drive imo.

      http://ethflop.sourceforge.net/

      It supports a massive 31mb virtual floppy drive, even on my Tandy 1000 with 720kb drives! The access time isn't great, it's still slow, but it's hugely convenient.

      Comment


        Originally posted by keenerb View Post
        I am actually using "ethflop", which is written by the same person who wrote "etherdfs". It replaces an existing floppy drive with a network-mounted floppy image, but you can't use it for booting sadly. A Gotek/HXC device is your best bet for a replacement virtual floppy drive imo.

        http://ethflop.sourceforge.net/

        It supports a massive 31mb virtual floppy drive, even on my Tandy 1000 with 720kb drives! The access time isn't great, it's still slow, but it's hugely convenient.

        Thanks, I will check it out... when I got etherdfs working... Now on the same physical network, still not working... The MAC autodetect have never worked ether... I'm starting to think my router may not like what is sent, can it be some kind of firewall preventing this? Perhaps I shoud make a new small network from scratch...

        Comment


          I use a local raspberry pi on a dumb hub for my etherdfs/ethflop setup. I've not had a lot of luck with routers and wifi and whatnot passing the raw packets the ethertools use...

          Comment


            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.
            You might be surprised. Even if you are trapped in the ever shrinking Microsoft world, there are innumerable cheap single board Linux computers that you could use as a server for less than $75.
            Once upon a time, the internet sucked because it came through the phone. Now the phone sucks because it comes through the internet.

            Comment


              Originally posted by Eudimorphodon View Post
              I found an "installable from a directory" distribution of Caldara DOS 7.0.3 and went ahead and installed that over 6.0. Took nearly two hours start to finish but it did complete...

              And EtherDFS does work under it. So, yeah, DR-DOS 6 problem.
              Probably a little late for you but DR-DOS before v6 (with the march 1993 update) has incompatible internal structures (CDS etc) that means all redirectors that expect to create drives as if they were PC/MS-DOS v4+ will have problems. I've had limited success mapping DR-DOS 5 and original 6 using those different structures on a custom redirector and v3.4x doesn't seem to be possible at all. So for normal redirectors it's best to use the v6 March 1993 update or as you've found v7 and up.

              Comment


                Originally posted by bob22 View Post
                Probably a little late for you but DR-DOS before v6 (with the march 1993 update) has incompatible internal structures (CDS etc) that means all redirectors that expect to create drives as if they were PC/MS-DOS v4+ will have problems.
                Yeah, I don't know if i'm inclined to roll back considering I was having some other issues with v6, but that is interesting to know that there were such major behind the curtain changes inside a single "version". (This is one of the complications I've been noticing with DR-DOS, there are a *lot* of different variations of it.)

                One sticking point I have with seven is, so far as I can tell, the equivalent configuration (it's not identical because they changed out HIDOS.SYS for HIMEM.SYS and got rid of the on-the-memory-manager switch to tell it to load high, instead switching to an MS-DOS like "DOS=HIGH" syntax) gives me almost 10k less base memory than six did, and I'm not clear why, other than it looks like 7 isn't loading some of the data structures into upper memory that 6 did. Documentation for optimizing DR-DOS's memory usage is scarce (or at least hard to find) compared to MS-DOS, especially for weird edge cases like an XT with upper memory blocks.
                My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

                Comment


                  If you do decide to go back to v6, you'll need to search for the update which is called MAR_UPD.ZIP. After which your NFS and other redirectors should work fine.

                  Comment


                    I did try to set up a local router with factory settings without success. I am really out of ideas how to make EtherDFS work, is there any way to test that the communication works? The strange thing is that the first tries, it (at least I think so) managed to create a 0 byte size file from the DOS client to the Linux-disk, but it cant autodetect the MAC adress, and nothing seem to work. Is there any other way to test that the prococol it relies on is "open" and not filtered by the router or linux os? What I think, is there is some problem on the linux side, as the other things I tested did not have any effect at all...

                    Comment


                      Just because I said so, I got it up and running. Finally! It must have been the network that was playing me a trick...

                      Comment


                        Originally posted by JohanLu View Post
                        I did try to set up a local router with factory settings without success. I am really out of ideas how to make EtherDFS work, is there any way to test that the communication works? The strange thing is that the first tries, it (at least I think so) managed to create a 0 byte size file from the DOS client to the Linux-disk, but it cant autodetect the MAC adress, and nothing seem to work. Is there any other way to test that the prococol it relies on is "open" and not filtered by the router or linux os? What I think, is there is some problem on the linux side, as the other things I tested did not have any effect at all...
                        So you have a firewall enabled on the Linux server? That could possibly be blocking up the works.

                        If you have tcpdump installed on the Linux box you can try running "tcpdump" and see if the server is responding to the client. This is complicated by the fact that etherdfs uses raw packets, not TCP/IP, but this works:

                        tcpdump -i (your ethernet device) not ip and not ip6 and not arp

                        pretty effectively. The communication is really minimal; when you do the initial "etherdfs :: C-E" you should see a single packet with the source your PC's MAC address and the destination ff:ff:ff:ff:ff:ff; the server should reply with a single packet. That's all I see, anyway. Subsequent file operations should produce a spew of packets with the PC's and server's MACs alternating as source and destination; I haven't analyzed it in great detail but it looks like every packet sent by one side gets a matching single packet ack, so if you see a string of packets going one direction with no response I would *guess* that points to a problem.
                        My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

                        Comment


                          ... or, never mind, then.
                          My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

                          Comment


                            Originally posted by Eudimorphodon View Post
                            ... or, never mind, then.
                            Thanks anyway... I'm so happy... This works like a charm!

                            Comment

                            Working...
                            X