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

DIGPAK drivers released under MIT License. Help wanted to port them from TASM.

  • Filter
  • Time
  • Show
Clear All
new posts

    Pretty sure that wasm (Open Watcom Assembler) accepts masm 6.1 syntax.


      Originally posted by pan069 View Post
      Pretty sure that wasm (Open Watcom Assembler) accepts masm 6.1 syntax.
      Yes, but there are differences. For example, IIRC WASM requires that you explicitly declare procedures as public whereas in MASM all procedures are public by default. See also digger's post above about UNION. Anyway, my point is that Wojciech Galazka's claim that binaries are identical is only valid if he is using an open source assembler since that was the requirement from the OP. He didn't mention which assembler he used.
      Looking for a cache card for the "ICL ErgoPRO C4/66d V"


        Good news. I tried assembling Wojciech Galazka's MASM port using JWasm v2.14 and the assembly succeeded without any errors or even warnings.

        Great job, Wojciech!

        Also, the resulting TSR loaded successfully, at least in DOSBox. Haven't checked whether the driver actually works in a game or anything, but it's late here right now, and I'll happily test that soon.

        See this post on GitHub for details.

        I hope to combine the efforts of Wojciech Galazka and Trixter so far, and to improve the DIGPAK sources for more fun retro DOS tinkering. Also, I hope to eventually offer these for inclusion in the FreeDOS project, which would finally scratch off a very old item from that project's wishlist.

        Any more contributions to this project are absolutely welcome!
        Last edited by digger; November 22, 2021, 05:43 PM.



          What do you want to do with Digipack ?

          Add support for more devices for games supporting it ?


            What do you want to do with Digipack ?

            Add support for more devices for games supporting it ?
            Maybe that would be too tedious to do without having the source code of the game... I don't know up to what point it is worth the effort. That for the games that load the driver into memory. Perhaphs for games that relay on a TSR would be easier.

            Nevertheless, I think the drivers and SDK, now made public and free, could be used for releasing new DOS games. They really may facilitate all the SFX managing, saving a lot of hours of coding. I'd wish I knew about these before...

            I also read somewhere (maybe on the project's github) an idea about building drivers for FreeDos. But I don't have any more details about this, and I cannot figure out what would be the use and implementation.

            Nevertheless, in my personal case, I would use them just the way the author left them, so I downloaded and saved them before any official alteration is made.
            Last edited by carlos12; December 12, 2021, 08:51 AM. Reason: Aditional note about TSR


              Originally posted by carlos12 View Post
              Nevertheless, I think the drivers and SDK, now made public and free, could be used for releasing new DOS games. They really may facilitate all the SFX managing, saving a lot of hours of coding. I'd wish I knew about these before...
              I am still working to build a "SDK Like" Version of MOD Master with source for game developement.
              The main interesting part of Digipak is for PC Speaker digital output.
              Mod Master support it, but it is of course slower because all the output is done in the IRQ, not like Digipak.

              The utlimate goal is to allow replay of Tracker music, VGM (OR DRO...) and multi channel digital output.
              Working even on 8088.