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

DOS Networking Client

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

    DOS Networking Client

    Hello All,

    I just wanted to pick the hive mind to see what people use/prefer as a client for DOS networking. Basically here is my situation:

    I have a Win2K3 server which serves as a NAS to all of my machines modern, vintage, mac, or PC. Obviously the modern machines connect directly through their OS (OS 9/X and Win7) networking services over TCP/IP w/out issues. My 486 system (the Everex STEP Megacube) can access the network through either WfW 3.11 or MS Lanman 2.2c in DOS mode. Of course the two don't seem to coexist well (or at least I can't get them to play nice) but it does the trick. I can access the server, map network drives, set the time off the time server, etc.

    As i mentioned one issue I have with Lanman is getting it to run with WfW: i.e. I can either have WfW's networking working or the DOS one working. If I have networking started through DOS, WfW throws up an error. Also changes in setup in one or the other breaks the other one. The other issue is memory usage. Lanman (even with a basic client) is a massive memory hog.

    i wanted to know if anyone has experience with MS Client 3.0? Does it have a smaller memory footprint? Does it run well on older machines (5150/5160)? Which would you guys recommend for the above scenario (connecting to and using network drives off of a Win2K3 server)?

    Thanks,
    Current Wish List: 1. IBM 7531 Industrial Series PC 2. NEC MultiSync XL (JC-2001) Monitor 3. MicroSolutions UniDOS card 4. Compaq 14" VGA CRT Monitor (the one that came with the SystemPro). 5. Stacker HW CoProcessor Board MCA BUS. If you have any of the above for sale please PM me. Thank you!

    #2
    TCP/IP is a huge memory hog. You probably want to use another protocol.
    -Marcoguy

    Comment


      #3
      Lan Client would use less resources, since if you're using Lan Manager, it's meant to manage a network, not just access it. Exactly what error does WFW show?

      I'm not for sure, but I don't think MS Lan Client would run on a 5150/60, simply because of the memory overloads. Maybe try mTCP on those machines? Except for the 5150.
      ~Ian~

      Remember, wherever you go, there you are.

      Comment


        #4
        Originally posted by marcoguy View Post
        TCP/IP is a huge memory hog. You probably want to use another protocol.
        Can you explain what you're thinking about? Doesn't the TCP/IP just take up a small buffer? As for applications, that will be variable and run from a few K to whatever. mTCP applications all run under 250K usage.
        WANTED: Cardinal 2450MNP modem.

        Comment


          #5
          I'm talking about the apps associated with the protocol. Most of them aren't really meant for computers that don't have 3Mb+ ram. TCP/IP is a newer protocol, so programs for it are for newer computers. (New is a relative term! ) I wasn't thinking of mTCP, actually.
          -Marcoguy

          Comment


            #6
            Originally posted by marcoguy View Post
            TCP/IP is a newer protocol, so programs for it are for newer computers. (New is a relative term! )
            I agree. Cerf worked on it during 1973-74, and it was adopted in 1982. That's pretty new to us old folks.
            WANTED: Cardinal 2450MNP modem.

            Comment


              #7
              I mean that things like actual programs that connect to it in DOS and are actually useful to a person with a somewhat normal knowledge of computers.
              -Marcoguy

              Comment


                #8
                Originally posted by DOS lives on!! View Post
                Lan Client would use less resources, since if you're using Lan Manager, it's meant to manage a network, not just access it. Exactly what error does WFW show?

                I'm not for sure, but I don't think MS Lan Client would run on a 5150/60, simply because of the memory overloads. Maybe try mTCP on those machines? Except for the 5150.
                I am not at home to check but it basically runs akin to: "You have networking started from outside of windows. This disables some features". However, networking through WfW still works.

                As far as the clients they should both run on 8088 machines as long as you don't use the full redirectors. The minimum system req. per MS are:

                Code:
                Both clients have the following minimum requirements:
                  - Intel 8088 or higher processor (80286 for full redirectors)
                  - 640 kilobytes (K) RAM
                  - 1 megabyte (MB) free hard disk space
                  - Supported network interface card
                  - MS-DOS version 3.3 or higher
                  - Windows version 3.1x is optional (should not be used with Windows for  Workgroups)
                As far as mTCP - mTCP is very specific (and good) at what it does. Unfortunately it does not allow me to use resources across my MS network.
                Current Wish List: 1. IBM 7531 Industrial Series PC 2. NEC MultiSync XL (JC-2001) Monitor 3. MicroSolutions UniDOS card 4. Compaq 14" VGA CRT Monitor (the one that came with the SystemPro). 5. Stacker HW CoProcessor Board MCA BUS. If you have any of the above for sale please PM me. Thank you!

                Comment


                  #9
                  Are you running LanMan on a machine with WfW installed??

                  WFW comes with it's own command line NET command - you can mount drives (NET USE), log on to domains (NET LOGON) etc, and when you type "NET STOP WORKSTATION" your memory comes back to you I actually put the NET LOGON and NET STOP WORKSTATION commands in to my menu (for those times I don't want to start Windows but want to copy files).


                  If you are talking about seperate machines, just make sure the Windows box is the browse master. For mysetup I used a Windows 2000 Server and set it up to be a primary WINS host, and domain controller.

                  To solve the memory issue with LanMan make batch files to initialise the network and remove entries from autoexec.bat (or for DOS 622 use bootmenus). So you can login, copy your stuff to hard disc, reboot and play. I'm yet to find a DOS network proggie that can read file shares from a modern PC without sufficating it of RAM.

                  Edit: by 'read' I mean 'mount', I like using XTGold for my copy shinnanigans
                  Edit2: despite efforts, I couldn't get domain authentication over NetBEUI and the memory usage wasn't much diff with LanMan
                  Last edited by SpidersWeb; June 7, 2012, 06:41 PM.
                  Twitter / YouTube

                  Comment


                    #10
                    Originally posted by marcoguy View Post
                    I mean that things like actual programs that connect to it in DOS and are actually useful to a person with a somewhat normal knowledge of computers.
                    Huh?

                    The issue of memory isn't related to the system. When I say Lanman is a memory hog I am talking about how much conventional memory it is using. On my Everex I have 64MB of memory but I still can't run many programs and have Lanman loaded. I think it uses about 200KB of conventional memory.
                    Current Wish List: 1. IBM 7531 Industrial Series PC 2. NEC MultiSync XL (JC-2001) Monitor 3. MicroSolutions UniDOS card 4. Compaq 14" VGA CRT Monitor (the one that came with the SystemPro). 5. Stacker HW CoProcessor Board MCA BUS. If you have any of the above for sale please PM me. Thank you!

                    Comment


                      #11
                      Originally posted by Shadow Lord View Post
                      As far as mTCP - mTCP is very specific (and good) at what it does. Unfortunately it does not allow me to use resources across my MS network.
                      mTCP has:
                      • a DHCP client
                      • an FTP client
                      • an FTP server
                      • a Telnet client
                      • an IRC client
                      • the Netcat utility
                      • ping
                      • an SNTP client (for setting the time from a network time server)
                      • htget for fetching files from an HTTP server


                      Not very specific at all. But yes, it does not provide access to SMB shares via a drive letter ...

                      I use the MS LAN client on my 386 once in a while - it has it's uses. But I am a lot happier with FTPing what I need to the machine when I need it instead of having the MS client burn all of that memory - it is quite a pig.

                      And if you are on an 8088 class machine, your options are very limited. The older Novell network clients work if you have a Novell server around. That's about it.

                      Comment


                        #12
                        Originally posted by SpidersWeb View Post
                        Are you running LanMan on a machine with WfW installed??

                        WFW comes with it's own command line NET command - you can mount drives (NET USE), log on to domains (NET LOGON) etc, and when you type "NET STOP WORKSTATION" your memory comes back to you I actually put the NET LOGON and NET STOP WORKSTATION commands in to my menu (for those times I don't want to start Windows but want to copy files).


                        If you are talking about seperate machines, just make sure the Windows box is the browse master. For mysetup I used a Windows 2000 Server and set it up to be a primary WINS host, and domain controller.

                        To solve the memory issue with LanMan make batch files to initialise the network and remove entries from autoexec.bat (or for DOS 622 use bootmenus). So you can login, copy your stuff to hard disc, reboot and play. I'm yet to find a DOS network proggie that can read file shares from a modern PC without sufficating it of RAM.

                        Edit: by 'read' I mean 'mount', I like using XTGold for my copy shinnanigans
                        Edit2: despite efforts, I couldn't get domain authentication over NetBEUI and the memory usage wasn't much diff with LanMan
                        Yes, I have Lanman on a system w/ WfW which is a no no . I do plan on using DOS boot menus at a later stage to achieve separation between different duties (Windows/Gaming/Networking/etc.). But even in that scenario if I can maximize conventional memory in any given "boot menu option" that would be a bonus. I may have to do as you suggest and constantly turn on and off the network services w/ a batch file no matter the client I end up using.
                        Current Wish List: 1. IBM 7531 Industrial Series PC 2. NEC MultiSync XL (JC-2001) Monitor 3. MicroSolutions UniDOS card 4. Compaq 14" VGA CRT Monitor (the one that came with the SystemPro). 5. Stacker HW CoProcessor Board MCA BUS. If you have any of the above for sale please PM me. Thank you!

                        Comment


                          #13
                          One of the best things about DOS 6.x is "memmaker"
                          (assuming you have a 386, and DOS 6.x)

                          Optimises your startup and agressively scans 640-1024Kb to find any memory to shove things in.
                          Twitter / YouTube

                          Comment


                            #14
                            If you're using an 8088 system, you can configure things so that lanman can be activated via a CONFIG.SYS menu, if you're using a late-enough version of MS-DOS. An EMS 4.0 card helps some, as lanman can use some of that memory.
                            Reach me: vcfblackhole _at_ protonmail dot com.

                            Comment


                              #15
                              Originally posted by Shadow Lord View Post
                              ....i wanted to know if anyone has experience with MS Client 3.0? Does it have a smaller memory footprint? Does it run well on older machines (5150/5160)? Which would you guys recommend for the above scenario (connecting to and using network drives off of a Win2K3 server)?

                              Thanks,
                              I use MS Network Client with the Netbeui protocol on my XT. It works great sharing resources between my XT and my P4 laptop with Windows XP. I have not been able to get the netbeui protocol working completely on Windows Vista or 7. Also, MS network client can be made to run as a server, but performance is very slow as a server.

                              the memory used is as follows;
                              IFSHLP = 3,952 (4K)
                              PROTMAN = 400 (0K) protocol manager?
                              EXP16 = 7,968 (8K) packet driver
                              NDISHLP = 1440 (1K)
                              NETBEUI = 37,792 (37K) protocol
                              BASIC = 13,696(13K) redirector

                              65248(64k)

                              Not to bad, and most of that be loaded hi if you have UMB's

                              Of course, I use mTCP, when I really want to save ram and don't need the network shares.

                              Comment

                              Working...
                              X