Absolutely, the VxD layer has also been of particular interest to me. Unfortunately, much of that VxD layer is poorly-documented. Much of what comprises the Win32 subsystem in Windows 95 (i.e. VWIN32) is not well…
Windows development (especially on 16-bit Windows) was weird and strange, but the VxD layer comprising the enhanced mode 386 components were even more arcane, originally written in assembly-only and virtually…
What's noteworthy is that EMM386 is also a hypervisor, albeit a very thin one. It is absolutely noteworthy, and something I touch on in my article; Windows/386 was heavily based on EMM386's code, both for the EMS…
What sort of conclusions do you want more explanation for? If you're curious about, for example, how I determined that the Windows/386 executable format was in the Xenix x.out format, I didn't. Geoff Chappell…
All in all, this was a very fun project to do, as Windows/386 was really lacking the kind of in-depth analysis that its successors got. I hope to update the project in the future, as well as maybe pivot to something…
Yet more proof, if any was needed, that C++ is a lost cause and never should've existed. Undefined behavior in C is bad enough, but apparently the C++ people decided to take it to the next level. In the old days, C(++)…
Glad to see my project picking up some traction! EmuWoW is still being worked on and I have an Alpha on the way to work with.
Yeah, I do take your point, and I never denied that all of these are going to be valid consideration for some program for some customer somewhere, my main point was that in most cases, it doesn't matter. Like you said,…
Honestly, I'm going to go against the grain here and say that 99% of the time, this is needless pedantry. Yes, these assumptions are technically wrong, but most of the time, let's be real, they're right, or else people…
Absolutely, the VxD layer has also been of particular interest to me. Unfortunately, much of that VxD layer is poorly-documented. Much of what comprises the Win32 subsystem in Windows 95 (i.e. VWIN32) is not well…
Windows development (especially on 16-bit Windows) was weird and strange, but the VxD layer comprising the enhanced mode 386 components were even more arcane, originally written in assembly-only and virtually…
What's noteworthy is that EMM386 is also a hypervisor, albeit a very thin one. It is absolutely noteworthy, and something I touch on in my article; Windows/386 was heavily based on EMM386's code, both for the EMS…
What sort of conclusions do you want more explanation for? If you're curious about, for example, how I determined that the Windows/386 executable format was in the Xenix x.out format, I didn't. Geoff Chappell…
All in all, this was a very fun project to do, as Windows/386 was really lacking the kind of in-depth analysis that its successors got. I hope to update the project in the future, as well as maybe pivot to something…
Yet more proof, if any was needed, that C++ is a lost cause and never should've existed. Undefined behavior in C is bad enough, but apparently the C++ people decided to take it to the next level. In the old days, C(++)…
Glad to see my project picking up some traction! EmuWoW is still being worked on and I have an Alpha on the way to work with.
Yeah, I do take your point, and I never denied that all of these are going to be valid consideration for some program for some customer somewhere, my main point was that in most cases, it doesn't matter. Like you said,…
Honestly, I'm going to go against the grain here and say that 99% of the time, this is needless pedantry. Yes, these assumptions are technically wrong, but most of the time, let's be real, they're right, or else people…