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

Does anyone know of a zx style command line emulator for DOS?

  • Filter
  • Time
  • Show
Clear All
new posts

    Does anyone know of a zx style command line emulator for DOS?

    I thought zx is pretty cool, it allows you to execute a CP/M program from a win32 command prompt and it redirects file i/o to the host OS - this allows you to use CP/M tools that process files like assemblers, linkers, etc.

    Obviously on an x64 machine you can't run dos/16 bit code, but a zx style emulator for dos on win32 would be pretty cool. I know about vDos and vDosPlus, but they seem more like a full emulator than a just run this command and done. I've tried to automate them for this task and it is complicated.

    Is there something out there that does this that I am unaware of?

    Could you explain what you mean with "zx", please? I first thought about the ZX-Spectrum but I'm not sure if you mean that.
    With kind regards / met vriendelijke groet, Ruud Baltissen


      Apparently it is called:

      An adaptation of zxcc-0.5.6 by Wayne Warthen

      I got it from the RomWBW - it is in the tools directory.

      Let's say you had a CP/M program that took one file for input, processed it, and then wrote a file for output such as an assembler. If under CP/M you would call asm infile.asm, then in Windows using ZX, you would call zx asm infile.asm and it will emulate the CP/M, but the infile and outfile calls are redirected to the real windows filesystem.

      I did find some other things on this that would allow running 16 bit code on an x64, but no good solutions. One is called ntvdm64x, but it doesn't look like code that can be trusted. There was also a similar one with a related to Wine or something. It would be great to have an x64 plugin subsystem that allows running 16 bit code, but I searched for awhile last night and didn't see anything worthwhile. Using another program like "dos16 pkzip -a test" would a step down from full integration, but would still be something.


        What kind of DOS programs are you trying to run?


          I'd say mostly command line tools like pkzip and so on. I know there are win32 equivalents of many, but not all.


            Try DosBox
            It's an emulator program which emulates an IBM PC compatible computer running a DOS operating system.
            Although it intended for old games it is possible to run another DOS software and tools under DosBox
            on the new Windows system (including modern 64-bit Windows 10).


              Originally posted by alank2 View Post
              I'd say mostly command line tools like pkzip and so on. I know there are win32 equivalents of many, but not all.
              The reason I asked is that a long, long time ago in a place not at all far away, I set upon writing a 16-bit x86 emulator. The original objective was to be able to run Windows 3.x programs on a 64-bit Windows machine. It never got that far. Not even close. The furthest it got was the ability to run command line programs compiled with Turbo Pascal and it does that very well.

              I just tried to run PKZIP with it. It stopped at "cld", an instruction I have yet to implement. Out of curiosity, I tried running SYMDEB; it stopped at "iret". So it is not ready for what you need it to do.


                That sounds pretty cool. Another program I'd like to run is Borland's Turbo Link or TLINK.EXE from BC502.


                  Originally posted by alank2 View Post
                  That sounds pretty cool. Another program I'd like to run is Borland's Turbo Link or TLINK.EXE from BC502.
                  I just tried running TLINK version 5.1 from the Borland C++ 3.1 installation. It failed trying to load DPMI support. That is something very far from my radar.

                  alecv is right. These tools run very well in DOSBox. I do not know whether DOSBox can run a single program from the console command prompt, then shut down. If not, it is not nearly as convenient as something like "RunDOS tlink ..."


                    Thanks for trying - I appreciate it!


                      So I finally found exactly what I was looking for:

                      Regular page:


                      My goal was making Borland C++ 5.02 work on an x64 box which looks like it will so long as it is installed in a non LFN directory like C:\BC5. BC5.02 has 16-bit code for TLINK and TASM. I have previously kludged a solution together with a custom program and vDos. The custom program would get called and generate the conifg/autoexec that vDos needed to run the real executable. This new tool (msdos.exe) requires none of that - it can run 16bit code directly as in "msdos tlink", or it can generate a new executable using "msdos -ctlinkc.exe tlink.exe". Then you can just rename the original tlink.exe to tlinkdos.exe and rename the tlinkc.exe to tlink.exe. Now it can be directly called from BCW and it works.

                      It only seems to be able to run one executable though so far. I couldn't get it to run a batch file unless I made it run /c batchfile, but that did work.


                        He also has one of these for cp/m too: