From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-msdos@vger.kernel.org
Subject: Re: win3.1 attempts :)
Date: Mon, 22 Sep 2003 02:11:36 -0500 [thread overview]
Message-ID: <20030922071136.GQ27439@dbz.icequake.net> (raw)
In-Reply-To: <3F6D783B.50806@aknet.ru>
hi,
On Sun, Sep 21, 2003 at 02:06:51PM +0400, Stas Sergeev wrote:
> Hello.
>
> Ryan Underwood wrote:
> >>problem is that it (most likely) simply runs win.com, which is
> >>trying dosx.exe or win386.exe - both without any success.
> >But at this point, no win.com exists. Should it?
> 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.
Look at the function at 014:11f7 in setup.exe. It pushes the string
"winexec" and "krnl386.exe" among other things (including a pointer that
a return code is written to), and then calls a functino, which I guess
does some sprintf and tries to exec the string. if it fails, it pushes
a string "winexec" "dosx.exe" and calls the same function. if that
fails, it exits the caller func then.
What is this "winexec" and does it exist in a normall installation after
the first (DOS-based) portion is complete? It doesn't exist in mine,
installed through dosemu.
BTW, WFW only runs in enhanced mode, correct? Why would it need
dosx.exe in that case ? Does dosx.exe starting WFW cause it to run in
enhanced mode anyway?
----
OT: I start up my favorite code viewer, and I get the following:
http://dbz.icequake.net/share/dosemu-ida.png
I Was using a default 1.1.5.7 config with very few thins uncommented.
Apparently $_X_font = "vga" is necessary to be uncommented for this to
work right (which it does after uncommenting that), but I thought "vga"
was the default font to use under X if it is available? At least, I
don't remember having to set that option before, but my memory may be
wrong.
--
Ryan Underwood, <nemesis at icequake.net>, icq=10317253
next prev parent reply other threads:[~2003-09-22 7:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-21 10:06 win3.1 attempts :) Stas Sergeev
2003-09-22 6:18 ` Ryan Underwood
2003-09-22 7:11 ` Ryan Underwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-23 17:08 Stas Sergeev
2003-09-24 4:52 ` Ryan Underwood
2003-09-22 17:11 Stas Sergeev
2003-09-23 4:48 ` Ryan Underwood
2003-09-20 18:04 Stas Sergeev
2003-09-21 0:40 ` Ryan Underwood
2003-09-26 15:22 ` Justin Zygmont
2003-09-26 16:01 ` Ryan Underwood
2003-09-30 17:57 ` Justin Zygmont
2003-09-20 12:35 Ryan Underwood
2003-09-20 12:42 ` Ryan Underwood
2003-09-20 13:11 ` Bart Oldeman
2003-09-21 5:01 ` Barnowl
2003-09-21 5:45 ` Ryan Underwood
2003-09-21 15:28 ` Barnowl
2003-09-22 4:18 ` Ryan Underwood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030922071136.GQ27439@dbz.icequake.net \
--to=nemesis-lists@icequake.net \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox