dosbox | Also contains a branch with idados support | Game Engine library

DOSBox adheres to the DOS rule of requiring both carriage return (13) and linefeed (10) to output a newline.

Your code only uses the linefeed and thus the text only drops a line.

There actually is an official API for DOS for accessing the host’s clipboard, supported in Windows 3.x and 9x. It is briefly described in article Q67675, formerly in Microsoft’s Knowledge Base.

Here’s a code sample (NASM syntax):

A big thank you to Peter Cordes in the comments for answering, I'll now post the answer to anyone else planning on using an old-fashioned compiler from 30 years ago.

Roughly, the best clock you can get in 16bit TASM is still not enough for accuracy. Luckily, in TASM you can "unlock" 32bit mode by using the .386 directive (as mentioned here).

Then, you can use the RDTSC command (Read Time-Stamp Counter), but one problem.. It does not exist in TASM. The fact it doesn't exist serves us no purpose, because all commands are in TASM (often called mnemonics) are just replacements for an OpCode, which is what defines every instruction the CPU can run.

When the Intel Pentium CPU was released, an OpCode for RDTSC was included, so if you have a CPU from it and up... You're good.

Now, how do we run the RDTSC instruction if it doesn't exist in TASM? (but does in our CPU)

In TASM, there's an instruction called db, and with it we can run an OpCode directly.

As seen here, what we'll need to do to run RDTSC is: db 0Fh, 31h.

And that's it! You can now run this instruction easily, and your program will still stay a mess, but a timed mess at that!

• TASM is able to echo special characters in Extended ASCII Table by just simply typing the decimal values of each special characters like ▐ (222), █ (219), ▀ (223) and ▄ (220). Just make sure they have commas each of them and must not be the inside the quotation marks.

• You can mix both strings and integers in every data string you are storing just make sure you put commas for every strings, and integers and add 13,10 as the return key and "$" to the end.

command.com-like command processor included with DosBox is not fully compatible with command syntax of MS-DOS command.com or especially windows NT's cmd.exe command processors.

See this page for commands available to DosBox and their syntax. They may be similar but not the same to MS-DOS ones.

Your options are:

• use a batch file that runs outside dosbox for anything that does not need to be inside it

• copy and run command.com from a real MS-DOS or other DOS. You can get one from an image of a DOS boot floppy (or Windows 95, 98 or ME) which should be plentiful in the internet. Then refer to command-line manual for that DOS version. You will lose access to DosBox-specific commands inside it and it may try to needlessly hog the CPU as almost any other DOS program.

• write a program in any programming language that can be executed in DOS like C (free C compilers for DOS) and call it from DosBox. Some of the compilers are made free and available for download.

There are some issues in your code:

• the value returned by strtol("0x80000000", NULL, 16) depends on the range of type long: if type long has 32 bits, the returned value should be LONG_MAX, which is 2147483647, whereas if long is larger, 2147483648 will be returned. Converting these values to uint32_t does not change the value as both as within the range of uint32_t. Type long on your system seems to have 64 bits. You could avoid this implementation defined behavior using strtoul() instead of strtol().

• there is no need for the intermediary cast to (int32_t): negating the unsigned value is well defined and -0x80000000 has the value 0x80000000 for type uint32_t.

• furthermore, this conversion is counterproductive and the likely cause of the observed behavior as negating the value INT32_MIN has undefined behavior because of signed arithmetic overflow. With optimisations enabled, the compiler determines that you are extracting the sign as if by bool sign = -(int32_t)value < 0 and simplifies this expression as bool sign = (int32_t)value > 0, which is correct for all values except INT32_MIN for which the compiler considers any behavior to be OK, since the behavior is undefined anyway. You can check the code on Godbolt's Compiler Explorer.

• you use type bool without including : the program should not compile. Is this a copy/paste error or do you compile as c++? The C99 _Bool semantics add an implicit test in the intialization statement, but it would be better to make it explicit and write:

While I don't have much to say about the details of what's going on, I apparently succeeded in reproducing your issue by poking at my own xmonad.hs. After removing the call to ewmh from it, running your program resulted in an empty fullscreen window, rather than a red one. That being so, changing your minimal configuration to...

You would have to do the following in (pseudo code):

My version of tasm emits a

*Warning* Assuming segment is 32 bit

You should use the .386 after the .MODEL SMALL to keep segments 16 bit, or explicitly emit 16 bit segments instead of using the simplified directives.