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

How to have autoexec/config sys menus on on Caldera OPENDOS 7/DRDOS

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

    How to have autoexec/config sys menus on on Caldera OPENDOS 7/DRDOS

    Hi, currently quite familiar on how to do option menus on msdos but for some reason i can't get it to work on opendos.
    The syntax for the menus is different than on msdos.

    Got this example from here https://nscsysop.hypermart.net/multiboot.html

    Do this on my config sys example:
    echo=1. Server
    echo=2. DR-DOS
    echo=3. XCopy all files on C: to D:
    switch server, drdos, xcpy
    exit

    :server
    set config=server
    Files=60
    Buffers=60
    return

    :drdos
    set config=drdos
    Files=60
    Buffers=60
    Device=c:\OAKCDROMDRV.SYS /D:CD001
    return

    cpy
    set config=xcpy
    Files=60
    Buffers=60
    return


    Then on autoexec.bat
    IF "%config%"=="server" goto NOVELL
    IF "%config%"=="dos" goto DOS
    IF "%config%"=="xcpy" goto XCPY

    OS
    nwcdex.exe /d:CD001
    goto DONE

    :XCPY
    cls
    @echo Copying all files on C: to D:
    xcopy c:\*.* d: /h /r /f /v /e /s
    goto DONE

    :NOVELL
    cd c:\nwserver
    server -nl

    ONE

    When i reboot the menu options show fine i can choose using the keys 1 2 3.
    Then the selection part from config.sys will work the menu will jump to the correct :tag in config.sys and then go to autoexec.bat
    But then on autoexec.bat it will parse the complete file ignoring my "goto DONE" statments and the "IF" section will run every command in the file from top to bottom.

    Its hard to find good references for drdos most about menus on the web are about msdos.

    Someone have experience doing menus on drdos ?, or know a better wat to get menus on DOS in place of the build in commands ?

    #2
    Try removing the "s around the %config% variables. I'm thinking they (the quotes) are forcing them to be treated as a string instead of a variable. Leave the "s around the words to the right of the == since these are strings.

    Comment


      #3
      If you use the [CODE] tag (#) it should take care of everything.
      PM me if you're looking for 3" or 5" floppy disks. EMail For everything else, Take Another Step

      Comment


        #4
        Another potential issue is that all of your labels are upper case. The examples I found in the DR-DOS 6 User Guide show labels in batch files in lower case only. However, the manual does not specify if they MUST be lower case. Try changing the labels to lower case. Don't forget to change them in the GOTO statements as well. Also, the GOTO statements are upper case in the guide examples. Click on the tiny picture below to see an example from the manual.

        example.png

        Comment


          #5
          Don't know what the differences are between DRDOS 7 and my DRDOS 6, but the section on configuration files and statements is pretty extensive in the 660-odd page user manual (when products were packed with real manuals and not just empty boxes with a CD inside).

          I'm guessing that you're confusing the batch file command syntax with the configuration command syntax. I believe that they're different.
          Reach me: vcfblackhole _at_ protonmail dot com.

          Comment


            #6
            DRDos manuals in pdf for,mat are available.
            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


              #7
              Originally posted by ibmapc View Post
              Another potential issue is that all of your labels are upper case. The examples I found in the DR-DOS 6 User Guide show labels in batch files in lower case only. However, the manual does not specify if they MUST be lower case. Try changing the labels to lower case. Don't forget to change them in the GOTO statements as well. Also, the GOTO statements are upper case in the guide examples. Click on the tiny picture below to see an example from the manual.

              [ATTACH=CONFIG]58509[/ATTACH]
              Thanks for the info tested this removing "" and also using lowercase but the IF statments on the autoexec file are completly ignored.

              Comment


                #8
                Originally posted by Stone View Post
                If you use the [CODE] tag (#) it should take care of everything.
                code what ?

                Comment


                  #9
                  Originally posted by soviet9922 View Post
                  code what ?
                  Click on the Advanced button which gives a larger toolbar. The "#" button will surround the text in a Code block. Basically the same as a quote block but designed for code.
                  For example,

                  Code:
                  Then on autoexec.bat
                   IF "%config%"=="server" goto NOVELL
                   IF "%config%"=="dos" goto DOS
                   IF "%config%"=="xcpy" goto XCPY

                  Comment


                    #10
                    checked dr dos manual but i don't see anything about menus for config sys maybe will be best for me to delete dr.dos and just use ms dos.

                    Comment


                      #11
                      I think MSDOS shares the same approach re CONFIG.SYS language and standard batch file language not being the same.
                      Reach me: vcfblackhole _at_ protonmail dot com.

                      Comment


                        #12
                        Originally posted by soviet9922 View Post
                        checked dr dos manual but i don't see anything about menus for config sys maybe will be best for me to delete dr.dos and just use ms dos.
                        https://web.archive.org/web/20080420...9ugch9.htm#807 shows examples of simple CONFIG.SYS menus in DR-DOS 7. Look at the SWITCH command and :LABEL.

                        Comment


                          #13
                          I have checked the documentation and using the help command and is correct, the switch command and :LABEL work perfectly like the documentation shows. Can choose and option fine and will only run the label in config.sys perfectly.

                          The issue is in autoexec.bat i don't see how to jump to a :LABEL from config.sys to another label on autoexec.bat there's nothing about that on the documentation.

                          Search on the web and only found that adding to autoexec.bat "IF "%config%"=="menu option config sys" then goto LABEL" when the autoexec.bat is reach it should jump to the correct LABEL that corresponds to the option choose in config.sys, but no mather how i try this don't work.
                          Tested adding an echo %config% at the start of autoexec.bat but this variable seems to be empty so i suposse that is why the menu don't work.
                          Start to think that is not possible to have dual menu for config.sys and autoexec.bat on dr.dos

                          Comment


                            #14
                            Use CONFIG.SYS SET command to set environment variables according your preferences, then use IF %environment-variable% - type statements to make your decisions in AUTOEXEC.BAT.

                            Easy.
                            Reach me: vcfblackhole _at_ protonmail dot com.

                            Comment


                              #15
                              thanks chuck, setting an environment variable on config.sys when you pick an option and then using it on the if statements on autoexec does the trick quite easy like you say.

                              Comment

                              Working...
                              X