search

otya128 / winevdm

16-bit Windows (Windows 1.x, 2.x, 3.0, 3.1, etc.) on 64-bit Windows
GNU General Public License v2.0
2.62k stars 150 forks source link

206c:fixme:int:DOSVM_Int10Handler 1439: Unknown - 0x75 #241

Open ThomasHeinrichSchmidt opened 5 years ago

ThomasHeinrichSchmidt commented 5 years ago

When I install and use the latest Intel HAXM driver v7.4.1 (from https://github.com/intel/haxm redirected from https://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager-intel-haxm), I am no more able to successfully start a Win16 app using vm=haxmvm.dll in otvdm.ini. otvdm.exe will write the following message (in an endless loop) to stderr:

version: 1056
206c:fixme:int:DOSVM_Int10Handler 1439: Unknown - 0x75
206c:err:int:DOSVM_Int10Handler 1440: int10: unknown/not implemented parameters:
int10: AX 75a2, BX 7a4a, CX 0000, DX 163f, SI 000c, DI 109f, DS 163f, ES 163f
206c:fixme:int:DOSVM_Int10Handler 1439: Unknown - 0x75
206c:err:int:DOSVM_Int10Handler 1440: int10: unknown/not implemented parameters:
int10: AX 75a2, BX 7a4a, CX 0000, DX 163f, SI 000c, DI 109f, DS 163f, ES 163f
206c:fixme:int:DOSVM_Int10Handler 1439: Unknown - 0x75
...
...
otya128 commented 5 years ago

I fixed the issue of FPU, please try the latest version.

ThomasHeinrichSchmidt commented 5 years ago

Thanks otya, but things are worse now, after starting      C:> otvdm.exe  DRAFTBRD.EXE > otvdm.log 2>&1 I experienced a blue screen, probably caused by: IntelHaxm.sys ( IntelHaxm+12ab7 ), see "Bugcheck Analysis.txt" and ini attached. DRAFTBRD.EXE runs normally (as before)  if I do not use vm=haxmvm.dll Thanks for your help. --thomas.

otya schrieb am 16.04.2019 um 14:45:

I fixed the issue of FPU, please try the latest version https://ci.appveyor.com/project/otya128/winevdm/build/artifacts.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/otya128/winevdm/issues/241#issuecomment-483643950, or mute the thread https://github.com/notifications/unsubscribe-auth/AHsbz6ptGPCbjMrtmmrcWrlcUL-KdTGwks5vhcX3gaJpZM4cRBYq.

[otvdm]

;EnableVisualStyle=0 EnableFontAntialias=1

;DisableAero=1

; Redirect windows directory ;WINDIR=WINDOWS

; dos version ;VDMDOSVER=x.x ; windows version (default: 3.95)

;WINVER=3.1

; Separate taskbar icons among programs. (default: 2) ; 0: Don't separate ; 1: Separate for each otvdm.exe process ; 2: Separate ;SeparateTaskbar=2

; SeparateWOWVDM (default: 1) ;SeparateWOWVDM=1

; haxmvm.dll: VM using a hypervisor ; You must install intel HAXM driver (https://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager-intel-haxm) ; It is 100 times faster (in some cases) than the software CPU emulator. vm=haxmvm.dll

; Fix the size of the screen to the value considering taskbar. (default: 0) ; FixScreenSize=1

; Enable registry redirection (default: 0) ; All registry operations are redirected to: ; HKEY_CURRENT_USER\Software\otvdm\HKEY_CLASSES_ROOT ; HKEY_CURRENT_USER\Software\otvdm\HKEY_CURRENT_USER ; HKEY_CURRENT_USER\Software\otvdm\HKEY_LOCAL_MACHINE ; If necessary, combine SETUP.REG on windows setup disk with 16-bit REGEDIT. ;EnableRegistryRedirection=1

; Limit the number of fonts. (some old programs can not process many fonts) ; (default: 0) ;EnumFontLimitation=1

; Improve XOR composition. DWMDesktopDCFix=1

;DWMDesktopDCFixBackgroundColorR=254 ;DWMDesktopDCFixBackgroundColorG=254 ;DWMDesktopDCFixBackgroundColorB=254

; Don't report running under Windows NT. ;IAmNotNT=1 ; ; Set application to launch MSDOS programs with ; Works with msdos player, dosbox requires a config file to mount virtual drives ; (default: otvdm.exe) ;dosemu=msdos.exe

3: kd> !analyze -v

SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80145e82ab7, Address of the instruction which caused the bugcheck Arg3: ffffd5888936ad40, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero.

Debugging Details:

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.

For some commands to work properly, your symbol path must point to .pdb files that have full type information.

Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work.

Type referenced: nt!_KPRCB

Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.

For some commands to work properly, your symbol path must point to .pdb files that have full type information.

Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work.

Type referenced: nt!_KPRCB

Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.

For some commands to work properly, your symbol path must point to .pdb files that have full type information.

Certain .pdb files (such as the public OS symbols) do not contain the required information. Contact the group that provided you with these symbols if you need this command to work.

Type referenced: nt!_KPRCB

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff8014660e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5c52a315

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

FAULTING_IP: IntelHaxm+12ab7 fffff801`45e82ab7 48837f1800 cmp qword ptr [rdi+18h],0

CONTEXT: ffffd5888936ad40 -- (.cxr 0xffffd5888936ad40) rax=ffff87040870b790 rbx=ffff870403aa6010 rcx=ffff870403aa6010 rdx=ffffc30171b530f8 rsi=ffff870403823e70 rdi=0000000000000000 rip=fffff80145e82ab7 rsp=ffffd5888936b730 rbp=0000000000000038 r8=ffffc30171b39180 r9=ffffc30171b4f000 r10=0000000000000fff r11=0000000000000050 r12=ffff870407852da0 r13=ffff8704076e3ab0 r14=0000000000000002 r15=0000000000000001 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 IntelHaxm+0x12ab7: fffff80145e82ab7 48837f1800 cmp qword ptr [rdi+18h],0 ds:002b:0000000000000018=???????????????? Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from ffff870407852da0 to fffff80145e82ab7

STACK_TEXT:
ffffd5888936b730 ffff870407852da0 : 0000000000000000 ffff870403823e70 0000000000000038 0000000000000000 : IntelHaxm+0x12ab7 ffffd5888936b738 0000000000000000 : ffff870403823e70 0000000000000038 0000000000000000 fffff80145e79e0c : 0xffff8704`07852da0

FOLLOWUP_IP: IntelHaxm+12ab7 fffff801`45e82ab7 48837f1800 cmp qword ptr [rdi+18h],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: IntelHaxm+12ab7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: IntelHaxm

IMAGE_NAME: IntelHaxm.sys

STACK_COMMAND: .cxr 0xffffd5888936ad40 ; kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner