From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-msdos@vger.kernel.org
Subject: Re: win3.1 attempts :)
Date: Mon, 22 Sep 2003 23:48:04 -0500 [thread overview]
Message-ID: <20030923044804.GB19554@dbz.icequake.net> (raw)
In-Reply-To: <3F6F2D4E.7050306@aknet.ru>
On Mon, Sep 22, 2003 at 09:11:42PM +0400, Stas Sergeev wrote:
> Hello.
>
> Ryan Underwood wrote:
> >>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.
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.
>
> >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.
> >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. :)
--
Ryan Underwood, <nemesis at icequake.net>, icq=10317253
next prev parent reply other threads:[~2003-09-23 4:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 17:11 win3.1 attempts :) Stas Sergeev
2003-09-23 4:48 ` 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-21 10:06 Stas Sergeev
2003-09-22 6:18 ` Ryan Underwood
2003-09-22 7:11 ` 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=20030923044804.GB19554@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