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

Dr DOS 7.03 won't run F16Combat pilot

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

    Dr DOS 7.03 won't run F16Combat pilot

    When trying to run the Game F16 Combat pilot in Dr DOS 7.03 on my IBM 5155, the following error comes up immediatly:
    Not ready error writing device AUX
    Abort, Retry, Ignore, Fail ?
    The only answer that the system accepts is F and it goes back to the DOS prompt.
    If I boot any version of MS or PC DOS 5 and above, the game runs perfecly. Anyone know how to configure Dr DOS to allow F16 to write to AUX (which is the same as COM ?) Right now I have the system set up so that I can boot to PC DOS 7 or DR DOS 7.03 so that if I get the urge to play F16, I can boot the PC DOS, but I tend to like Dr DOS better for most other tasks because it leaves more base memory if configured correctly than PC DOS.

    #2
    Originally posted by ibmapc View Post
    When trying to run the Game F16 Combat pilot in Dr DOS 7.03 on my IBM 5155, the following error comes up immediatly:
    Not ready error writing device AUX
    Abort, Retry, Ignore, Fail ?
    The only answer that the system accepts is F and it goes back to the DOS prompt.
    If I boot any version of MS or PC DOS 5 and above, the game runs perfecly. Anyone know how to configure Dr DOS to allow F16 to write to AUX (which is the same as COM ?) Right now I have the system set up so that I can boot to PC DOS 7 or DR DOS 7.03 so that if I get the urge to play F16, I can boot the PC DOS, but I tend to like Dr DOS better for most other tasks because it leaves more base memory if configured correctly than PC DOS.
    I wonder if "AUX" is not defined under DR-DOS?...
    Disclaimer: The username IBMMuseum and domain IBMMuseum.com are not affiliated with IBM in any manner

    Comment


      #3
      Dr DOS online help specifies that AUX and COM are reserved device names and can not be used as a file name. Thats the only reference to AUX that I can find in Dr DOS help.

      Comment


        #4
        The real question is, why is your game writing to AUX in the first place?

        I suspect that F16 Combat Pilot really isn't interested in looking for your auxiliary console. It probably made an assumption about a DOS data structure that is different between MS-DOS and DR DOS. That assumption is leading to the bogus access of the AUX reserved device, and your reply to that bogus access is what terminates the game.

        Sorry, not all DOSes are created equal. There are significant 'under the covers' differences between most of the major versions that MS produced. And DR DOS and FreeDOS are clones and will have different implementations for some functions. Unless you can figure out what F16 Combat Pilot is doing and correct it you should just plan on running MS-DOS.

        Comment


          #5
          References to AUX in my experience are usually program errors--often, just attempting to close and re-open a file seems to result in using 3 as the file descriptor.

          If you really suspect that the program is trying to write something meaningful to AUX, there are a couple of TSRs in the SIMTEL library that will redirect AUX reference to the console.

          And the citation in the help for DR DOS simply means that certain names are mapped to physical devices, not files, and so cannot be created, deleted, renamed or moved like a "regular" file can. Other such devices are CLOCK$, PRN and NUL as examples.
          Reach me: vcfblackhole _at_ protonmail dot com.

          Comment

          Working...
          X