Windows GUI lab for editing, building, and executing 16-bit x86 modules on WHP (Windows Hypervisor Platform).

Coding in 16-bit on Windows has been more difficult than in the past, and I would occasionally find myself thinking about a problem in 16-bit. When WHP was released I created some stub programs to execute 16-bit code. Then AI came along and I had some agents convert all my notes into an IDE. Could be an educational interface, but no one learns/uses 16-bit x86 any more.

It is uncertain how much legacy support I will integrate (BIOS, DOS, video modes, etc.) but it meets my current needs to develop 16-bit real and unreal code with very little boilerplate.

Alpha Release for 16-bit testing:
https://github.com/bitRAKE/whp_x16

Edit: added light/dark theme, key shortcuts (faster dev cycle).

(Link snazzy image to make it look more impressive than it is:)

How used this ? In windows 10
I try but not get any like on your screen.

Did you follow "Quick Start" steps?

I'm going to guess you don't have WHP: ... it's an optional Windows feature.

I also assumed, "git clone --recursive <repo>" is known by user.

There is also a user guide.

Edit: I have fixed the steps.

Perhaps it's an older version of WHP? Can you paste the console text?

This snippet of your code: irks me a bit, because this is exactly what I wanted to avoid when I wrote fasm. See the fasm source, which was sometimes assembled as 16-bit too, and it has such instructions consistently written like:

I need to create some examples for the AI to pick up on the alternate syntax.

rep16 and rep32 and rep64

The full syntax also allows to specify segment overrides: and the assembler verifies that what you request is actually encodable (if, for instance, you forget which string instructions can use a different segment and for which operand).

Verify your system meets the Hyper-V prerequisites.
It might be because of that.

bitRAKE this is a top-notch project.
I really admire your coding skills.

For some reason I am getting:

Maybe I am doing something wrong.

Thank you. It is mostly a shim between Tomasz's work and WHP. There is potential for a larger project: different machine configurations, more extensive debugging, etc.

On the error, the only creation is a missing INI file, or the binary modules. Likely, the location of the ASM files is not writeable. It's possible to completely separate whp16.exe from fasmg and the 16-bit assembly files. The initial configuration is the repo layout - perhaps the x16/ directory is readonly.

Great to see someone frying out some crispy floats off the (almost forgotten by "modern" codes) x87 FPU!
Unfortunately, I don't have any support to run this, but I'm certainly here for the assembly code.