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 and Windows Network Shares (Was: Shares)

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

    DOS and Windows Network Shares (Was: Shares)

    Hi all

    If you were to fit IBM PC/AT with a 3.5" 1.44Mb floppy drive, and an ISA network card, is it possible to boot DOS with relevant drivers to allow the machine to access shares on say a Windows 2008 R2 server?

    Any thoughts on this would be appreciated.

    Regards,

    Chris.
    https://www.micromuseum.co.uk/

    #2
    Check out THIS LINK.
    I prefer Microsoft Network Client for DOS using the NETBEUI protocol. The server would also need to run the same protocol. So, netbeui may not be the best choice. I believe TCP/IP will run on a 286 with MS Network Client, but I haven't tried it.
    Last edited by ibmapc; August 8, 2012, 07:55 PM.

    Comment


      #3
      Thanks for that info! Just what I needed!
      https://www.micromuseum.co.uk/

      Comment


        #4
        You will likely have trouble going from DOS -> Windows 2008 even with TCP/IP because the old DOS software doesn't have support for the newer standards (even over TCP/IP, DOS Samba tools wont be doing 128bit encrypted passwords etc) and over time support for the old standards gets dropped. I use MS LanManager for DOS and Windows 2000 Server with domains - because I found that to be the most reliable for viewing/mounting shares. MS Client or LanMan without domains, often gave trouble (for me anyway) viewing (NET VIEW) other machines.

        You'll also likely find it kills your conventional memory on a machine without upper memory, so DOS 6 boot menus or putting the command line network start commands in a batch file instead of AUTOEXEC is a good idea I found (especially the TCP/IP TSR which is huge). Another alternative would be not installing a DOS client, and instead installing Windows 3.11 with networking, so you can get in there when you need it. I tend to just do this now as it makes things a lot easier - when you return to DOS you get all your conventional memory back.

        Just a few thoughts from when I set up my network, you could have a different experience, let us know how you get on

        Edit: if its just for the intiial install, might be easier to go with FastLynx 3.3 (serial/parallel cable, how I used to do it when the machines were current) or mTCP (which has an FTP client).
        Twitter / YouTube

        Comment


          #5
          I stuck with Win2000 server as well, also lets me connect my old 68K macs to my file archives.
          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


            #6
            Originally posted by SpidersWeb View Post
            ... Another alternative would be not installing a DOS client, and instead installing Windows 3.11 with networking, so you can get in there when you need it...
            Will Windows 3.11 with netrworking run on a 286?

            Comment


              #7
              Originally posted by ibmapc View Post
              Will Windows 3.11 with netrworking run on a 286?
              Good point, even if it does, it'd be painfully slow and require at least 2.5Mb total memory to boot.
              Scrap that idea I use it on 386's.
              Twitter / YouTube

              Comment


                #8
                I have WFW 3.11 with networking support running on a 386. The network features themselves aren't that slow, but starting them, or running programs that extensively use the networking features are much slower. There is a big difference in speed for this between a 386 and a 486. Running it on a 286 will require more memory and more (much) waiting time.

                I believe MS Lan Client will ask you to input a domain (not a workgroup), but it will serve the same purpose.
                ~Ian~

                Remember, wherever you go, there you are.

                Comment


                  #9
                  Thanks for all the advice. Will have a play over the weekend and see what I can do!
                  https://www.micromuseum.co.uk/

                  Comment


                    #10
                    Originally posted by DOS lives on!! View Post
                    I have WFW 3.11 with networking support running on a 386. The network features themselves aren't that slow, but starting them, or running programs that extensively use the networking features are much slower. There is a big difference in speed for this between a 386 and a 486. Running it on a 286 will require more memory and more (much) waiting time.

                    I believe MS Lan Client will ask you to input a domain (not a workgroup), but it will serve the same purpose.
                    There's a download on the MS FTP site somewhere that replaces the 3.11 16-bit TCP stack with the 32-bit stack from NT3.51 - it's a bit faster, and has a few extra features. It might make a difference to network-heavy programs.

                    Comment


                      #11
                      You're probably looking for MS's TCP/IP-32B. It provides the updated TCP/IP protocol along with more networking features. Although installing it after Win32S is really bothersome.
                      ~Ian~

                      Remember, wherever you go, there you are.

                      Comment


                        #12
                        To the Original Poster, ChrisCwmbran,

                        You specify that your using an IBM PC/AT. Am I correct to assume that it has an 80286 processor?
                        If that is the case, I think we should do a better job of staying on topic and not recommend a software that needs a 386 or better.

                        Comment

                        Working...
                        X