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

Configuring memory for playing certain games

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

    Configuring memory for playing certain games

    I remember my dad having to write several different AUTOEXEC.BAT files, depending on what game we wanted to play. Sierra games in particular. I am now trying to do the same, I suppose.

    The computer is a JPL 386 PC compatible. Here is what the MEM command gives after my bootup.

    JPL 386 mem - Screenshot 2021-10-07 113452.jpg

    I try to run Quest for Glory 2 and the response is "Your computer does not have enough memory to run this game."

    I am running DOS 6.22.

    The technical requirements/supportability of the game according to the box are:
    MS-DOS 5.0 or greater
    286 or better
    640 KB RAM
    7.5 MB Hard drive space
    Tandy Graphics, CGA (B &W), EGA, MCGA (PS/2), VGA or Hercules Monochrome
    Roland MT-32, AdLib, Sound Blaster, PS/1 audio/joystick adapter or other music synthesizer
    Mouse

    1. First I need to learn about memory. There is conventional memory, upper memory, shadow memory, extended memory, and expanded memory. Any others? Why is there a difference in how the types are usable?

    2. Can anyone point me to a crash course in how to do memory configurations? Possibly even how to create a boot menu that times out to a default?

    3. Is there some lookup table on the Internet on what vintage games require what memory configuration? (Yes, such as sierrahelp.com)
    Last edited by Bill-kun; October 7, 2021, 07:53 AM.
    Sattinger's Law: “It works better if you plug it in.” Corollary: “It works even better if you plug it in correctly.”
    "The simplest solution is the most likely solution." --My paraphrase of Occam's Razor
    "You can get [a computer] like yours at a garage sale for, like, fifteen dollars," --Strong Sad, sbemail #33

    #2
    Conventional = memory below 640k, where most programs mainly run.
    Upper = UMB = memory between 640k and 1M, mostly useful for loading drivers into to free up conventional memory
    Expanded = EMS = memory swapped in an out of a window in the Upper Memory area, older standard, mostly for 8088 and 286 class machines
    Extended = XMS = memory above 1M, mostly used by 386 and later
    High Memory Area = HMA = special 64k chunk at the top of 1M, can be used by dos to reduce it's conventional memory usage

    Comment


      #3
      In general, for config.sys-
      DEVICE=C:\DOS\HIMEM.SYS <- gives access to memory above 1 Meg
      DEVICE=C:\DOS\EMM386.EXE <- manages memory in the UMB area, also emulates/provides EMS memory unless you specify 'NOEMS'
      DOS=HIGH,UMB <- loads part of dos into the HMA, allows loading of drivers into the UMB area?

      DEVICEHIGH=cdrom.sys <- 'devicehigh' says to load the driver into the UMB area

      autoexec.bat-
      LH MOUSE.COM <- 'LH' says to load the driver into the UMB area

      Basicaly, the idea is to maximize the available conventional memory. It starts to get tricky with lots of drivers, like network, cdrom, scsi, etc. Then it starts to be like tetris, 'Ok, If I leave the mouse driver in conventional memory, that will free up enough space in UMB for the network redirector. Oooh, this mouse driver is 240 bytes smaller than the one I was using...'

      Comment


        #4
        If you’re running DOS 6.22 the easiest thing to do is run memmaker, until you get up to speed enough to do it manually.

        It will look at you current situation, ask a couple of questions, and then calculate a better use of himem.sys, emm386, and things like dos=high,umb and so forth.

        If you want specific help with your current setup, we’d need to see your config.sys and autoexec.bat, and the output from mem /c /p

        Comment


          #5
          As mentioned above, memmaker would pretty much solve your issue. 415K of conventional RAM is strangling the opportunity to run much of anything in DOS (especially games). You might want to run it twice; I've occasionally seen where it does do a little better on the 2nd pass. And you could substitute some drivers (specifically a DOS mouse driver). CuteMouse was very tiny compared to virtually anything else. Just make sure you keep a copy of autoexec.bat and config.sys in case something goes horribly wrong ( which is highly unlikely).

          Comment


            #6
            Well, this led me to run across another instance of "a question I didn't even know I should ask." Searching the files in my DOS 6.22 directory, C:\DOS, MEMMAKER.EXE is not there. The contents of my C:\DOS were copied from a boot disk, the image for which I downloaded from bootdisk.com. After searching winworldpc.com for DOS 6.22, I now realize I have been using incomplete copies of DOS 6.22 for months! I downloaded those images onto floppies. The installation would need to be actually run; it's not a simple file copy.

            Can I just install DOS 6.22 onto my existing vintage computers that already have C:\DOS and other hard drive contents? Or do I have to evacuate them, reformat so that they are bootable again, and then move all the evacuated contents back on?
            Sattinger's Law: “It works better if you plug it in.” Corollary: “It works even better if you plug it in correctly.”
            "The simplest solution is the most likely solution." --My paraphrase of Occam's Razor
            "You can get [a computer] like yours at a garage sale for, like, fifteen dollars," --Strong Sad, sbemail #33

            Comment


              #7
              Yeah, 177k is a lot to be using.

              Can you post the output of "mem /c", rather than just "mem" ?

              There may be some older drivers that take up a lot of memory (mouse.sys is one, I run CuteMouse instead, which needs only 2kb as mentioned above) which more up to date variants can help.
              I have also turned to different EMS drivers, EMM386 will win you no awards for performance! Some people use Qemm, I have run Jemm for things that don't crash while using it (some games really don't like it, and it breaks ctrl-alt-del support on my 386).

              Once you get a hang of it, writing a batch menu for selecting options in your autoexec is something well worth learning.


              Phil

              Comment


                #8
                Originally posted by Bill-kun View Post

                Can I just install DOS 6.22 onto my existing vintage computers that already have C:\DOS and other hard drive contents? Or do I have to evacuate them, reformat so that they are bootable again, and then move all the evacuated contents back on?
                If your machine boots ok now, then it should be a matter of just installing (or preferably, upgrading) to DOS 6.22. There should be upgrade-disks somewhere out on the interwebs...

                Comment


                  #9
                  Originally posted by PhilipA View Post
                  Yeah, 177k is a lot to be using.

                  Can you post the output of "mem /c", rather than just "mem" ?
                  Attached is the output.

                  C:>\mem /c/p

                  Modules using memory below 1 MB:

                  Name Total = Conventional + Upper Memory
                  -------- ---------------- ---------------- ----------------
                  MSDOS 71,053 (69K) 71,053 (69K) 0 (0K)
                  HIMEM 3,712 (4K) 3,712 (4K) 0 (0K)
                  CD1 28,880 (28K) 28,880 (28K) 0 (0K)
                  WORKGRP 3,104 (3K) 3,104 (3K) 0 (0K)
                  COMMAND 4,992 (5K) 4,992 (5K) 0 (0K)
                  EXPLOSIV 5,696 (6K) 5,696 (6K) 0 (0K)
                  MSCDEX 27,952 (27K) 27,952 (27K) 0 (0K)
                  GMOUSE 9,408 (9K) 9,408 (9K) 0 (0K)
                  Free 498,336 (487K) 498,336 (487K) 0 (0K)

                  Memory Summary:

                  Type of Memory Total = Used + Free
                  ---------------- ---------- ---------- ----------
                  Conventional 653,312 154,976 498,336
                  Upper 0 0 0
                  Reserved 0 0 0
                  Extended (XMS) 7,340,032 65,536 7,274,496
                  ---------------- ---------- ---------- ----------
                  Press any key to continue . . .
                  Total memory 7,993,344 220,512 7,772,832

                  Total under 1 MB 653,312 154,976 498,336

                  Largest executable program size 498,064 (486K)
                  Largest free upper memory block 0 (0K)
                  The high memory area is available.

                  C:\>
                  I will report later today how the installation of DOS 6.22 went. I backed up/copied off the 52 MB. hard drive from one of my 286s and I'll install on it to see what happens.
                  Attached Files
                  Sattinger's Law: “It works better if you plug it in.” Corollary: “It works even better if you plug it in correctly.”
                  "The simplest solution is the most likely solution." --My paraphrase of Occam's Razor
                  "You can get [a computer] like yours at a garage sale for, like, fifteen dollars," --Strong Sad, sbemail #33

                  Comment


                    #10
                    Yeah, with HIMEM.SYS being loaded, I see a few things that will load into high memory and free up conventional for programs to use.

                    The easiest things I would suggest to do is this:

                    Edit c:\config.sys

                    ​​​​​​The device=himem.sys line needs to be at or near the top of the list.
                    immediately below, if it isnt there, add DOS=HIGH,UMB below that, any other DEVICE= lines, change to DEVICEHIGH=

                    Save and exit. That'll attempt to load everything into high memory (it won't do it if the driver won't let).

                    Then edit c:\autoexec.bat

                    In front of any program that needs to be loaded (for instance gmouse, put LH before it- e.g.:-
                    lh c:\gmouse\gmouse.exe
                    ​​​​(I just made that path for the file up as example to show how to add "LH", which stands for Load High).

                    That should free up as much memory as possible. Save file and exit.

                    Reboot computer and retry mem /c

                    ​​​​Phil

                    Comment


                      #11
                      The main items to load high are the CD-ROM drivers (CD1 and MSCDEX). That would free up more than 50K. Drop the screensaver (Explosiv). Combine that with letting DOS use the HMA should result in a free memory available of about 600K.

                      Comment


                        #12
                        I tried Quest for Glory 2 on my other 2 working vintage computers (Swan 286/12 and KLH-195 286) and there was no problem running it. I have EXPLOSIV and GMOUSE on them, but not the CD-ROM stuff since they don't have CD-ROM drives.

                        Back to the 386. First, installing DOS 6.22 full, which includes MEMMAKER.EXE. I finally figured out how to create the DOS 6.22 installation disks so that they would work in installing.
                        1. Get the bulk file from pcwinworld.com on a modern computer.
                        2. Unzip the bulk file. Put each of the 4 *.img files in a directory.
                        3. Zip each of those files individually so they will each fit on a 3.5-inch floppy.
                        4. Switch to vintage computer. Move the *.zip files onto the hard drive.
                        5. Unzip each *.zip file onto the hard drive using PKZ240G or similar.
                        6. Write each of the *.img files onto a floppy using Rawread-Rawrite or similar. The installation disks are now created and ready.

                        I installed DOS 6.22 over my previously incomplete DOS 6.22 on my 386. It never asked for disk 4, the supplemental disk. Why didn't it? Will I have something missing?
                        I installed DOS 6.22 over my previously incomplete DOS 6.22 on my Swan and KLH (using the 5.25-inch *.img files instead of the 3.5-inch files). I believe they both asked for the supplemental disk.

                        Back to the 386. I edited my CONFIG.SYS and AUTOEXEC.BAT as told and rebooted. Here is the output from MEM /C.

                        Modules using memory below 1 MB:

                        Name Total = Conventional + Upper Memory
                        -------- ---------------- ---------------- ----------------
                        MSDOS 17,933 (18K) 17,933 (18K) 0 (0K)
                        HIMEM 1,088 (1K) 1,088 (1K) 0 (0K)
                        CD1 28,880 (28K) 28,880 (28K) 0 (0K)
                        WORKGRP 3,104 (3K) 3,104 (3K) 0 (0K)
                        COMMAND 2,928 (3K) 2,928 (3K) 0 (0K)
                        EXPLOSIV 5,696 (6K) 5,696 (6K) 0 (0K)
                        MSCDEX 27,952 (27K) 27,952 (27K) 0 (0K)
                        GMOUSE 9,408 (9K) 9,408 (9K) 0 (0K)
                        Free 556,144 (543K) 556,144 (543K) 0 (0K)

                        Memory Summary:

                        Type of Memory Total = Used + Free
                        ---------------- ---------- ---------- ----------
                        Conventional 653,312 97,168 556,144
                        Upper 0 0 0
                        Reserved 0 0 0
                        Extended (XMS) 7,340,032 65,536 7,274,496
                        ---------------- ---------- ---------- ----------
                        Total memory 7,993,344 162,704 7,830,640

                        Total under 1 MB 653,312 97,168 556,144

                        Largest executable program size 555,872 (543K)
                        Largest free upper memory block 0 (0K)
                        MS-DOS is resident in the high memory area.
                        Quest for Glory 2 now runs with no problem. I haven't used MEMMAKER,EXE yet. I will soon, I think, since eventually I want to be able to run The Dagger of Amon Ra from its original CD. I remember that took my dad forever to configure everything just right so it would fully work. And I still want to become skilled in writing AUTOEXEC.BAT and CONFIG.SYS files, including multiple boot options. Thanks!
                        Attached Files
                        Last edited by Bill-kun; October 14, 2021, 09:26 AM.
                        Sattinger's Law: “It works better if you plug it in.” Corollary: “It works even better if you plug it in correctly.”
                        "The simplest solution is the most likely solution." --My paraphrase of Occam's Razor
                        "You can get [a computer] like yours at a garage sale for, like, fifteen dollars," --Strong Sad, sbemail #33

                        Comment


                          #13
                          Nothing is using high memory right now. I think to get UMB, you need emm386, not just himem. And if you add highscan to emm386, you might get a few more. Memmaker usually takes care of all of that.

                          Comment


                            #14
                            Disk 4 is usually not needed. AFAIR, it's just supplemental stuff that generally isn't needed. Why some machines want it and others don't shouldn't be a concern.
                            Last edited by T-R-A; October 14, 2021, 11:05 AM.

                            Comment


                              #15
                              Before I start using MEMMAKER, what exactly does it do? Is it just a really user-friendly way to automatically get CONFIG.SYS and AUTOEXEC.BAT files that allocate memory optimally? Or does it change stuff that would take a lot of trouble to undo?

                              Side note: Due to various installations of software and maybe hardware, including DOS and Windows 3.1 for Workgroups, I've got about 6 different CONFIG.* and AUTOEXEC.* files in the C-root. I keep them all for the sake of knowing the history of the computer, even though it is modernly established. I don't want to lose any lines that are important to making the PC run the way I want (especially configuring hardware like my Zip drive). Once I get skilled in writing CONFIG.SYS and AUTOEXEC.BAT files, maybe I won't be so worried about that.
                              Sattinger's Law: “It works better if you plug it in.” Corollary: “It works even better if you plug it in correctly.”
                              "The simplest solution is the most likely solution." --My paraphrase of Occam's Razor
                              "You can get [a computer] like yours at a garage sale for, like, fifteen dollars," --Strong Sad, sbemail #33

                              Comment

                              Working...
                              X