#Dosbox windows 3.1 kernl386 crash code#
#Dosbox windows 3.1 kernl386 crash windows#

Although it just so happens that later versions of MS-DOS are sufficiently similar to 3.10 to allow the other version checks to pass, which means that spoofing the version number should work fine as well.

#Dosbox windows 3.1 kernl386 crash windows#

The remedy is clear now: you need to downgrade your DOS to a version supported by Windows 1.x.

(In this case, AX happens to hold the DOS version number, so you could in principle guess what DOS version Windows crashed on based on what is displayed on the screen.) In the beta release, between those two there is an additional MOV AX instruction that sets the other string to вЂDOS 2.0 or greater requiredвЂ™.

#Dosbox windows 3.1 kernl386 crash code#

When the version number check fails, control flow jumps straight to the fragment which displays the вЂIncorrect DOS versionвЂ™ message, and then whatever happens to be in the code segment at the offset held in AX. '5.!.ДЄt address 6E96 is a simple wrapper around DOSвЂ™s вЂprint stringвЂ™ system call. The code that would print them, however, was not, and this is what produces the garbage output. In the final release of Windows, these detailed messages were hastily removed. When one of these checks fails, the beta version of Windows displays a message detailing the specific check that failed to pass: Windows does not merely obtain the officially-advertised version number to ensure the version number is not spoofed, it also tests whether certain fields of the DOS data segment are found at the expected addresses.

Windows 1.x was designed to run under MS-DOS 2.0, 3.0 and 3.10 to ensure it only runs under one of these, it performs a version test on its host DOS. This is a botched version check error message.