Announcement

Collapse

Forum 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.


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.


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.



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.


"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.

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

Network over LPT or COM port

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

    Network over LPT or COM port

    You have INTERSVR and INTERLNK from MS-DOS and Lantastic 4.1 that can be used to access the drives of another PC over the LPT or COM port as if they were part of your own directory. I'm quite well in programming in ASM and Pascal and I want to program such a tool myself. So I searched internet and ran into EtherDFS. Looked like a nice start but it stated that the server part should run on a Linux machine and the source for this program was not given. And my tool should be able to run on 8088/8086 machines, both server and client.

    I had a look at RAMdrives. But I cannot see how to use this in combination with I/O ports. And even if I saw it, I just have the client side. How to handle the server side? or is it as simple as "just sending the info the client needs"? If the client needs the directory, what should be sent, the text as it woud appear on the screen or just some raw data?

    Who is able to help me with some pointers, please?

    Many thanks in advance!
    With kind regards / met vriendelijke groet, Ruud Baltissen

    www.baltissen.org

    #2
    Re-inventing the wheel? If it floats your boat.

    I suggest you look into Netware Lite, Netware DOS/NDOS (formerly DR-DOS plus Netware Lite).

    https://www.brutman.com/Dos_Networking/

    Comment


      #3
      I was forgetting Netware Lite evolved into Personal Netware too, which might be the basis in Novell DOS.

      Comment


        #4
        Have you had a look at U - N E T II? It's a full parallel port client/server network. Maybe it could give you some pointers.
        PM me if you're looking for 3" or 5" floppy disks. EMail For everything else, Take Another Step

        Comment


          #5
          Originally posted by WBST View Post
          Re-inventing the wheel? If it floats your boat.
          Mainly to learn HOW it is done. I can use the knowledge for other projects.

          I suggest you look into Netware Lite, Netware DOS/NDOS (formerly DR-DOS plus Netware Lite).
          I have the original Novell-DOS 7.01 and I made it work so that was not the problem. But in general it takes so much time to setup the network that I rather prefer tools like Laplink or UFO.

          I completely forgot about that one, thank you very much!
          With kind regards / met vriendelijke groet, Ruud Baltissen

          www.baltissen.org

          Comment


            #6
            Originally posted by Stone View Post
            Have you had a look at U - N E T II? It's a full parallel port client/server network. Maybe it could give you some pointers.
            Unfortunately it is just the software, no sources.
            With kind regards / met vriendelijke groet, Ruud Baltissen

            www.baltissen.org

            Comment


              #7
              Originally posted by Ruud View Post
              So I searched internet and ran into EtherDFS. Looked like a nice start but it stated that the server part should run on a Linux machine and the source for this program was not given. And my tool should be able to run on 8088/8086 machines, both server and client.
              It looks like the source for both the client and server are on sourceforge?

              https://sourceforge.net/projects/etherdfs/files/
              My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

              Comment


                #8
                Shades of "The $25 network" (Still have the disk)

                Comment


                  #9
                  Somewhere around here I still have some fancy cables used for parallel networking from a bit name back in the day (forget who).

                  The only times I got into serial networking was feeding disk images to my C1541 drive or to an Amiga.
                  What I collect: 68K/Early PPC Mac, DOS/Win 3.1 era machines, Amiga/ST, C64/128
                  Nubus/ISA/VLB/MCA/EISA cards of all types
                  Boxed apps and games for the above systems
                  Analog video capture cards/software and complete systems

                  Comment


                    #10
                    Originally posted by Chuck(G) View Post
                    Shades of "The $25 network" (Still have the disk)
                    Used the program a lot in the 90s.
                    "Good engineers keep thick authoritative books on their shelf. Not for their own reference, but to throw at people who ask stupid questions; hoping a small fragment of knowledge will osmotically transfer with each cranial impact." - Me

                    Comment


                      #11
                      Originally posted by WBST View Post
                      I was forgetting Netware Lite evolved into Personal Netware too, which might be the basis in Novell DOS.
                      No DRDos was the basis for Novell Dos,,, Dr Dos had a client/server com/lpt sharing set of programs iirc. If not lpt definately com port.
                      Just looked my DR Dos 6.0 User Guide. Filelink was the name of the program. Serial only.
                      Last edited by Caluser2000; May 5, 2020, 01:14 AM.
                      Thomas Byers (DRI)- "You'll have a million people using the A> [MS-DOS prompt] forever. You'll have five million using [nongraphic] menu systems such as Topview, Concurrent PC-DOS, Desq, and those types. But there'll be 50 to 100 million using the iconic-based interfaces."

                      Comment


                        #12
                        Originally posted by Eudimorphodon View Post
                        It looks like the source for both the client and server are on sourceforge? ...
                        First: I realized that I don't need the server side software at all. I'm only interested how I can integrate the obtained information of the directory structure into the directory of the client. HOW I get this info is not important. In fact I have done that before: my Commodore drive emulator not only emulates drives but my CBM computers can also directly access the files and directories of the computer running the emulator.

                        I downloaded the sources of EtherDFS only to find out that it does not contain any program that does what I'm looking for. I even contacted mr. Brutman and he confirmed that. He advised me to look for '"network redirector" interface for DOS'. So I will do that.

                        Quick edit: just googling and very promising indeed. It seems "redirector" was the keyword.
                        Last edited by Ruud; May 5, 2020, 06:55 AM.
                        With kind regards / met vriendelijke groet, Ruud Baltissen

                        www.baltissen.org

                        Comment


                          #13
                          Originally posted by Ruud View Post
                          I downloaded the sources of EtherDFS only to find out that it does not contain any program that does what I'm looking for. I even contacted mr. Brutman and he confirmed that. He advised me to look for '"network redirector" interface for DOS'.
                          I think the author of EtherDFS was pretty clear about how his program wasn't a standard network redirector; my recollection is that it abuses some direct storage block interface and otherwise isn't a "well behaved" network widget.

                          If you're working on more standard network services I'd personally love to see a direct LPT redirector to a remote TCP port. I've found a TSR that seems to do a pretty reliable job redirecting LPT1 to a file, and using that I've been able to use NC.EXE from Mr. Brutman's fine TCP suite to send print jobs to my networked Laserjet, but it'd be really cool to have a lightweight widget that did that directly.
                          My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

                          Comment


                            #14
                            Originally posted by Eudimorphodon View Post
                            If you're working on more standard network services...
                            FYI, I'm not. Thinking about it, it will be a driver that enables a PC to recognize the directory structure of another computer as parts of its own. I would prefer a driver that can be placed on both PCs and where it doesn't matter which one is the server and which one is the client. But that is something for the future.
                            As the communication is 1-to-1 over the LPT or COM port, I don't think TCP/IP or equivalent is needed; IMHO it is just overhead. So I'm afraid that you can forget "standard network services".
                            With kind regards / met vriendelijke groet, Ruud Baltissen

                            www.baltissen.org

                            Comment


                              #15
                              Originally posted by Ruud View Post
                              Unfortunately it is just the software, no sources.
                              What about using DOSBox Debugger or something similar?
                              PM me if you're looking for 3" or 5" floppy disks. EMail For everything else, Take Another Step

                              Comment

                              Working...
                              X