win3.1 attempts :)
Hello.
Quoted 3 lines · Ryan Underwood
Quoted 1 line
No idea, but if not, then it starts dosx.exe directly, which is very likely.
No win.com, dosx.exe, or win386.exe exists after the first stage of
installation in dosemu. I just verified this.
And I just verified that replacing dosx.ex_ with os2k386.ex_ makes the install to go as far as a graphical screen, under dosemu, just as I expected. I have to interrupt it at that stage - no time for experiments now. Probably at a week-end.
Quoted 1 line
Look at the function at 014:11f7 in setup.exe. It pushes the string "winexec" and "krnl386.exe" among other things
What's the use? I just tried what I suggested, and it seems to work (at a first glance at least). Trying something before assuming that it doesn't work, can sometimes save some work:)
Quoted 1 line
BTW, WFW only runs in enhanced mode, correct?
Via win.com at least - yes. That's why I still think replacing dosx.exe with os2k386.exe is OK, while replacing the win386.exe is not - it will always force the winos2 mode, which is not good.
Quoted 1 line
Why would it need dosx.exe in that case ?
It can be started directly.
Quoted 1 line
Does dosx.exe starting WFW cause it to run in enhanced mode anyway?
I don't think so, but might be trivial to figure. Just look into "Help->About" in a Program Manager to find out.
Quoted 5 lines · Stas Sergeev
Hello.
Quoted 2 lines · Ryan Underwood
Quoted 2 lines
No idea, but if not, then it starts dosx.exe directly, which is very likely.
Quoted 8 lines
Quoted 2 lines
No win.com, dosx.exe, or win386.exe exists after the first stage of installation in dosemu. I just verified this.
And I just verified that replacing dosx.ex_ with os2k386.ex_ makes the install to go as far as a graphical screen, under dosemu, just as I expected. I have to interrupt it at that stage - no time for experiments now. Probably at a week-end.
Yes, I see that it does. However, using the os2k386 in place of dosx in the install files seems to cause dosemu to have some filesystem-related problems. The first error is that it is "unable to update registration info", and then when going to file copy, there are lots of "Write error:
FOO.BAR The file is write protected. Error Code #210"
It is the same with all 3 MS-DOS, DR-DOS, FreeDOS.
Quoted 7 lines
Quoted 3 lines
Look at the function at 014:11f7 in setup.exe. It pushes the string "winexec" and "krnl386.exe" among other things
What's the use? I just tried what I suggested, and it seems to work (at a first glance at least). Trying something before assuming that it doesn't work, can sometimes save some work:)
I do not see harm, nor stupidity, in at least attempting to understand how something works before making shots in the dark.
Quoted 4 lines
Quoted 1 line
Does dosx.exe starting WFW cause it to run in enhanced mode anyway?
I don't think so, but might be trivial to figure. Just look into "
Help->About" in a Program Manager to find out.
To do that, one would need a working installation, which you have and I do not. :)
Signature · 1 line
Ryan Underwood, <nemesis at icequake.net>, icq=10317253