Is there a way to get a log when winevdm is run on ReactOS?

[obsolete-is-better]

I got a crash when trying to install PageMaker v5 in ReactOS with Winevdm.

[otya128]

You can get the log by the same procedure as when you do it on Windows.

[obsolete-is-better]

I don't fully know why but the build that works on ReactOS doesn't have a console window for displaying a log even if you run winevdm from a command prompt.

I'm using the following build:

otvdm-for-old-windows-v0.8.1.zip

[obsolete-is-better]

So I think i know what was going on with not being able to get a trace when run on ReactOS by default the builds are debug builds and i think it interferes with Winevdm's trace so i used a release build and was able to get a trace.

I used the following settings: "WINEDEBUG=+relay,+msg,+int21" trace.txt

[otya128]

If you are using 0.8.1, it may have been fixed. Please try https://ci.appveyor.com/project/otya128/winevdm/builds/42133115/job/sgr7a7rsjb70pn73/artifacts

[obsolete-is-better]

It gets a little farther now but is unable to create the installation directory for some reason.

it's also opening a console window now before it didn't. And sometimes it crashes like in the screen shot above.

trace.zip

[cracyc]

Looks like GetDlgItemText is failing for whatever reason.

03fc:Call USER.93: GETDLGITEMTEXT(0032,0bdd,16770002,0090) ret=1217:a55a ds=1237
03fc:Ret  USER.93: GETDLGITEMTEXT() retval=00000000 ret=1217:a55a ds=1237
03fc:Call KEYBOARD.5: ANSITOOEM(16770002 "",1237:8af6) ret=1217:3087 ds=1237
03fc:Ret  KEYBOARD.5: ANSITOOEM() retval=ffffffff ret=1217:3087 ds=1237
03fc:Call KERNEL.90: LSTRLEN(12378af6 "") ret=121f:dc55 ds=1237
03fc:Ret  KERNEL.90: LSTRLEN() retval=00000000 ret=121f:dc55 ds=1237
03fc:Call KERNEL.51: MAKEPROCINSTANCE(12171a0e,1236) ret=1217:199a ds=1237
03fc:Ret  KERNEL.51: MAKEPROCINSTANCE() retval=120700d2 ret=1217:199a ds=1237
03fc:Call USER.87: DIALOGBOX(1236,000000c9 #00c9,0032,120700d2) ret=1217:19e5 ds=1237
03fc:trace:msg:WINPROC_CallProc32ATo16 (6E4883A1, 000202E4, WM_CANCELMODE(001F), 00000000, 00000000)
03fc:CallTo16(func=1207:00c2,ds=1237,0032,001f,0000,0000,0000) ss:sp=1237:8b4a ax=1237 bx=0006 cx=0000 dx=0000 si=0032 di=0000 bp=8b74 es=1237 fs=003b
03fc:RetFrom16() ss:sp=1237:8b4a  ax=0000 bx=0006 cx=0000 dx=0000 bp=8b74 sp=8b4a
03fc:trace:msg:WINPROC_CallProc32ATo16 (6E4883A1, 000202E4, WM_ENABLE(000A), 00000000, 00000000)
03fc:CallTo16(func=1207:00c2,ds=1237,0032,000a,0000,0000,0000) ss:sp=1237:8b4a ax=1237 bx=0006 cx=0000 dx=0000 si=0032 di=0000 bp=8b74 es=1237 fs=003b
03fc:RetFrom16() ss:sp=1237:8b4a  ax=0000 bx=0006 cx=0000 dx=0000 bp=8b74 sp=8b4a
03fc:trace:msg:WINPROC_CallProc32ATo16 (6E4883A1, 000402FA, WM_SETFONT(0030), 280A01A5, 00000000)
03fc:CallTo16(func=1207:00d2,ds=1237,003d,0030,0060,0000,0000) ss:sp=1237:8b4a ax=1237 bx=0006 cx=0000 dx=0000 si=003d di=0000 bp=8b74 es=1237 fs=003b
03fc:RetFrom16() ss:sp=1237:8b4a  ax=0000 bx=0006 cx=0000 dx=0000 bp=8b74 sp=8b4a
03fc:trace:msg:WINPROC_CallProc32ATo16 (6E4883A1, 000402FA, WM_INITDIALOG(0110), 00020304, 00000000)
03fc:CallTo16(func=1207:00d2,ds=1237,003d,0110,0042,0000,0000) ss:sp=1237:8b4a ax=1237 bx=0006 cx=0000 dx=0000 si=003d di=0000 bp=8b74 es=1237 fs=003b
03fc:Call USER.156: GETSYSTEMMENU(003d,0000) ret=1217:1a3a ds=1237
03fc:Ret  USER.156: GETSYSTEMMENU() retval=00000043 ret=1217:1a3a ds=1237
03fc:Call USER.413: DELETEMENU(0043,f060,0000) ret=1217:1a45 ds=1237
03fc:Ret  USER.413: DELETEMENU() retval=00000001 ret=1217:1a45 ds=1237
03fc:Call USER.176: LOADSTRING(1236,1227,1237:8aa4,0080) ret=1217:1a68 ds=1237
03fc:Ret  USER.176: LOADSTRING() retval=0000001d ret=1217:1a68 ds=1237
03fc:Call USER.92: SETDLGITEMTEXT(003d,0bd6,1237:8a24 "Error getting directory name.") ret=1217:1a91 ds=1237
03fc:trace:msg:WINPROC_CallProc16To32A (6E48CD8D, 003E, WM_SETTEXT(000C), 0000, 12378A24)

[obsolete-is-better]

I will probably need to try the GCC build of Winevdm on windows xp to make sure it's not the OS causing a problem cause it's acting really unstable but it is interesting it's mainly the installer that's the problem. If i copy files from PM5 installed under the regular winevdm build the program does run with some issues related to unimplemented windows functions.

but it is able to continue