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

XT / AT and a network

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

    XT / AT and a network

    Hallo allemaal,

    I used to have a Novell Lite network for my DOS machines. To transfer files from my W7 machines to these DOS machines I first had to transfer it to a machine equipped with W98 and XP and running XP at that time and then I had to reboot to W98-DOS so I could run Novell Lite and transfer the files once again.
    In the mean time I have equipped various machines with XTIDE and the Universal BIOS that enables me to use CF cards. These can be written by the W7 machines and read by the DOS machines. In some occasions I simply use floppies or UFO, a LapLink equivalent.

    But I still wonder if there are possibilities to use the network again, but in a more simpler way. I found EtherDFS but it is meant for Linux and I have not enough experience with Linux. So any pointer or suggestion is welcome!

    Many thanks in advance!


    Kind regards / met vriendelijke groet, Ruud Baltissen

    www.baltissen.org
    With kind regards / met vriendelijke groet, Ruud Baltissen

    www.baltissen.org

    #2
    Mike Brutman has a great suite of TCP/IP / ftp / other network utilities. Easy to use and works on even the lowest spec'd 8088's.

    Check out http://www.brutman.com/mTCP/

    I use it to connect to a simple FTP server hosted on my NAS. Works a treat - just remember when using Mike's FTP client that it defaults to ascii transfers. Type the command 'image' to set it to binary before copying files!
    System 80 Expansion Interface located! Thanks to all who helped out and the good people in the NZ vintage computer forums!

    Comment


      #3
      As long as the target machine is a 386SX or better you can try parcp-usb. This one connects to the parallel port of historic PC or Atari ST, and on the other side to Win 2000-10, Linux or Mac OS-X via USB. And then you have a master to be started on the one side, and the client on the other side, and that client offers a Norton Commander like user interface. It can transfer between 70-120 kb/s, including folder structures. https://joy.sophics.cz/parcp/

      Very easy usage, no need to setup anything. It works just on the fly.
      <album>

      Comment


        #4
        I still use NWLite because it's lightweight enough that I can run games/software direct off the network share with any DOS PC - no upper memory, transfers, reboots, etc

        I virtualised my server with VMWare (VirtualBox didn't cut it) and have it share a folder mounted by DOS for Workgroups. That mounted file share is also shared over my modern samba network by the Linux host - so I can drop files on it and immediately run them directly on the old hardware (no reboots, no transfers, no slow downs).

        Downside is that it was horrendously complicated so I'm not sure if it meets the "simple" requirement, but it's an option.
        Twitter / YouTube

        Comment


          #5
          I use LanMan and just use SMB sharing. To maintain the security of my newer machines I use a NAS unit with the older protocols enabled as an intermediary.

          Comment


            #6
            I don't have a network set up for DOS machines at the moment, but when I did it ran NetWare. I find that NetWare works especially well on old DOS versions because it uses very little conventional memory compared to most of the others. Also, it's fast. I timed how long it took to launch an app on a PC XT from a local 10MB MFM hard disk, versus running the same app from a network drive and the network was considerably faster.

            I need to set up a NetWare server again but first I need to locate my old license diskettes. I know I saved them somewhere...

            Comment


              #7
              Anyone know of a DOS TCP/IP client that has USB WiFi support? (e.g. Ralink RT7601)

              Comment


                #8
                Originally posted by SpidersWeb View Post
                I virtualised my server with VMWare ... and have it share a folder mounted by DOS for Workgroups.
                My intermediate ran DfW as well so I'm familiar with it. But running it virtual, I never thought about that. I can give it a try at least.

                Downside is that it was horrendously complicated so I'm not sure if it meets the "simple" requirement, but it's an option.
                I don't see what is so "horrendously complicated" in the first place. And if it is, it is a one time operation. I don't need the intermediate PC anymore and therefore saving on hardware and time (handling an rebooting it).

                Many thanks for this idea!
                With kind regards / met vriendelijke groet, Ruud Baltissen

                www.baltissen.org

                Comment


                  #9
                  Originally posted by 3pcedev View Post
                  Thank you, I will have a look at this.
                  With kind regards / met vriendelijke groet, Ruud Baltissen

                  www.baltissen.org

                  Comment


                    #10
                    Originally posted by Ruud View Post

                    I don't see what is so "horrendously complicated" in the first place. And if it is, it is a one time operation. I don't need the intermediate PC anymore and therefore saving on hardware and time (handling an rebooting it).

                    Many thanks for this idea!
                    Yep there is no intermediate step required, and you can get (very cheaply) quiet Core 2 era machines with VT-x that can just sit and be left on in the background barely using any power (one of my servers uses a laptop power brick).

                    But getting everything setup did take a lot of trial and error, which is what I meant about the complicated. It's a bit much for most people but if you've got the time it's fantastic when setup and running.

                    I did it twice because I needed it at another physical location and also added things like making the machine also double as a gateway with dhcp/bootp, dns, iptables etc to keep the vintage networks off my main network - but not deny them internet or file sharing access.

                    In my file share setup, I was sharing a mounted network share in DOS. It is easier if you use D4WG as a server, but that didn't quite meet my requirements (I wanted the servers themselves to be able to back up contents, move things to USB drives etc).

                    Glad I inspired someone else to mess with it If you run in to issues with CLIENT/SERVER conflicts and NWLite send me a PM, I have a fix.
                    Twitter / YouTube

                    Comment


                      #11
                      Depending on which way you want to do the networking, I did have a solution a few years ago involving VPC 2007, Windows 95, Interlnk and a parallel cable.

                      The old machine was connected to the modern machine with a parallel cable. On the old machine, I ran INTERSVR, then on the modern machine I installed Windows 95 inside a VPC 2007 VM with parallel port passthrough enabled. Within Windows 95 I enabled the option to let it use DOS mode storage drivers. This lets you install INTERLNK on Windows 95 and see the old machine's hard drive from within it. This INTERLNK connection in turn could be shared on the Windows 95 VM and then it could be accessed by the host machine as a network share (or indeed from any other machine on the network).

                      End result was being able to read/write to the old hard drive directly from a modern OS with the virtual 95 machine acting as a bridge.

                      Whilst this was fine for backing up old hard disks or moving downloaded files over to the old machine, it is unfortunately the 'wrong way around' if you were hoping to browse the modern machine's resources from the old machine, and of course INTERSVR ties up the old machine so it can't be used for anything else at the same time. That and VPC 2007 doesn't work properly/at all on newer versions of Windows and many new computers don't have parallel ports, although if you do have one you could probably substitute another virtualisation platform as long as it supports parallel port passthrough and also can visualise a network card which has Windows 95 drivers available. Possibly you could also substitute Windows 98 in too, although I don't know if that was able to directly use DOS storage drivers the way that 95 was?

                      Comment


                        #12
                        Originally posted by Ruud View Post
                        I found EtherDFS but it is meant for Linux and I have not enough experience with Linux.
                        Hello Ruud, I'm quite late to the party, I know.
                        Myself I use a little RPi with the EtherDFS server onboard as a little NAS for my retro machines. I find such setup very convenient. If you're still looking for a "plug and play" solution, let me know - I can dump the image of my RPi and upload it somewhere for you, so all you'd have to do is write the image to an RPi and boot it (no Linux magic involved - well, not on your side that is).

                        Comment

                        Working...
                        X