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

Error Starting Networking in DOS 6.22

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

    Error Starting Networking in DOS 6.22

    Installed the MS Network Client 3.0 for DOS into my DOS 6.22 machine.

    Installation seemed to go fine, install found my network card (Intel Etherexpress 16 LAN Adapter), TCP/IP Protocol was added, Networking Start Info is setup in the config.sys and autoexec.bat files.

    On restart, the system does the net start command successfully, but next step is to load tcptsr.exe / tinyrfc.exe / emsbfr.exe. When trying to load these I am getting the:

    net0111 error accessing nemm.dos

    It will fail loading the .exe's from there, hit Enter, then it finishes loading to the DOS Prompt.

    I read around and a couple places mentioned updating the driver for the NIC Card (I am using the one that comes with the MS Network Client). I downloaded several versions of the EXP16.dos driver file and tried to load it into the MS Network Client setup to use in place of the driver the Client has built-in. But all places I have downloaded the driver from dont have an .inf file with them, so when I point the Client setup to the folder the Intel Driver is in, it says no driver file was found there...

    1. Am I doing something wrong?

    2. If its the driver, does anyone have the full driver package?

    3. Do I need to do something else?

    The nemm.dos file is in the DOS\NET folder so I dont see how it couldnt access it...so not thinking the file is the issue.
    "In Life, The Days Are Long But The Years Are Short..."

    #2
    Is everything that is supposed to be in the 'path' actually in the 'path'?
    PM me if you're looking for 3" or 5" floppy disks. EMail For everything else, Take Another Step

    Comment


      #3
      Yes, its all there...

      Like I said, I have read others getting this error due to older driver version...not sure if that applies here or not.
      "In Life, The Days Are Long But The Years Are Short..."

      Comment


        #4
        Check the file attributes on the file nemm.dos and the directory that it resides in. If they are "read only" that could cause problems if MS Network Client needs to write to them.

        PS. I use that same NIC on all of my dos machines with MS Network Client and have not had trouble. However, I don't use tcp/ip on the machines that are less than 486 processor. The one machine with the 486 runs Win 3.11 for workgroups and I believe that handles tcp/ip in windows. On the older machines I use the NetBeui protocol, but that means that they can't talk to any thing newer than Win XP. Also, it might be helpful if we could get a look at your config.sys and autoexec.bat
        Last edited by ibmapc; May 9, 2017, 06:56 AM. Reason: Miss Spelled NetBeui

        Comment


          #5
          I am gonna try some of the things you said (checking the files) and checking my path....once I verify that I will post my files....

          Thanks for the advice.
          "In Life, The Days Are Long But The Years Are Short..."

          Comment


            #6
            I figured it out...it was the path in my config.sys file pointed to the wrong place for the files....
            "In Life, The Days Are Long But The Years Are Short..."

            Comment


              #7
              Originally posted by Smack2k View Post
              ...it was the path in my config.sys file pointed to the wrong place for the files....
              No, that was not it. The path statement is in your autoexec.bat file!
              PM me if you're looking for 3" or 5" floppy disks. EMail For everything else, Take Another Step

              Comment


                #8
                Originally posted by Stone View Post
                No, that was not it. The path statement is in your autoexec.bat file!
                I think he means the path he was using for the device drivers. Device=C:\......\xxxxxx.xxx
                PCjr, DTK PC-XT Turbo, 386DX 33, 486 laptop, Pentium 120, Pentium III 500, various old laptops, Commodore Colt, all working. I also have a 286 that I need to see if I can repair.

                Comment


                  #9
                  Originally posted by KenEG View Post
                  I think he means the path he was using for the device drivers. Device=C:\......\xxxxxx.xxx
                  Hehehehe... that's not called the path, even though that might be what he meant.
                  PM me if you're looking for 3" or 5" floppy disks. EMail For everything else, Take Another Step

                  Comment


                    #10
                    Its a path to the executable file.
                    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

                    Working...
                    X