Just a little question: what emulator did you create those logs with?
Edit: Just improved my emulator's CR0 reset and write behaviour to only keep the defined bits(clearing the others, with 80486 setting bit 4). I've also improved the 80486 to keep bits 29/30 during reset(as documented).
Edit: Now logging on a 80486. But I see all kind of triple faults from an INT3 instruction on that(Windows 3.0 in Standard mode)?
It's the usual Windows 3.0 with MS-DOS 6.22 boot menu(only HIMEM.SYS loaded from the Windows directory) on a 80486 in Standard mode.
Edit: I see the INT3 triple fault keeps occurring on 0110:0AB3
Edit: I see INT 31h with AX=0002? Apparently mapping a real-mode segment to a LDT descriptor?
DPMI interrupt 31h calls: http://www.delorie.com/djgpp/doc/dpmi/ch5.n.html
Edit: The DPMI interrupt does end up at the correct 0051:2832 address.
Edit: UniPCemu's latest 80486(improved CR0 register to handle undefined bits and reset/init state better) running far into the Windows 3.0 booting(a few disk reads before crashing into the MS-DOS prompt), having aborted it since it took so long to log:
https://www.dropbox.com/s/hy28hu1pr94vubd/deb … 10_1736.7z?dl=0
Still running a diff against win30_s.txt, which takes a long time("diff -u --speed-large-files win30_s.txt debugger.log>win30_s.diff").