From: Barnowl <barnowl@uronramp.net>
To: Ryan Underwood <nemesis-lists@icequake.net>
Cc: linux-msdos@vger.kernel.org
Subject: Re: win3.1 attempts :)
Date: Sun, 21 Sep 2003 00:01:55 -0500 [thread overview]
Message-ID: <20030921000155.70fb78f6.barnowl@uronramp.net> (raw)
In-Reply-To: <20030920123558.GR27439@dbz.icequake.net>
Ryan -
To give you hope I have seen win95 at least once installed and run via dosemu. It was on a pre-0.9x release. don't ask , dus idon't remeber how it was done :(
Evan
On Sat, 20 Sep 2003 07:35:58 -0500
Ryan Underwood <nemesis-lists@icequake.net> wrote:
>
> Hi,
>
> So, armed with a fresh copy of DOSEMU 1.1.5.7 and quite happy with the
> changelog entry referring to windows, I set out to create a fresh
> win3.1 setup on my machine to help with hacking WINE.
>
> I have a kernel 2.4.23-pre4 and running Debian.
>
> I tried both the WFW3.11 and the plain Win3.1. For each of these, I
> took the gdi.exe, user,exe, krnl386.exe, and mouse.drv from OS/2's
> windows, compressed them (-> .ex_), and replaced the original files with
> the OS/2 versions that use DPMI instead of blasted VCPI.
>
> I put all of the windows installation disks into a single directory,
> lredir'd from the file system.
>
> I attempted the install with each of FreeDOS (kernel 1.1.28), DR-DOS
> 7.04, and MS-DOS 6.22 running under DOSEMU. Each time I attempt to
> install on D:\windows which is lredir'd to a dir under my home directory.
>
> Here are the results and some notes:
>
> WFW3.11
> -------
> FreeDOS: Completes the initial file copy in DOS. When it would go to
> start windows to go to the next part of the installation, it crashes to
> a dos prompt instead, sitting in D:\windows. From there, one can issue
> .\system\krnl386.exe to start windows. (Just \system\krnl386.exe doesn't
> work; '\system' seems to be reserved to FreeDOS somehow.) However, when
> windows starts, it complains about not being installed all the way and
> refuses to go further. Through trial and error, I discovered that
> issuing '.\system\krnl386.exe /?' somehow bypasses this and gets one
> into the installation.
>
> The installation is straightforward for the first part. When it
> actually goes to copy some files, you must have a disk in the A:
> drive for some reason, or you will get an A.R.F error on screen, and
> be unable to continue the session (close dosemu). I tried to redirect
> the floppy to /dev/null or /dev/zero, but then after the file copy, the
> installer would have a GPF and hang the DOSEMU session.. Putting a
> diskette in the A: drive for its "probe" gets us past the file copy...
> and then the session hangs with some corrupted video. :( The mouse can
> still be moved around (you see the windows mouse moving) so the DOSEMU
> isn't completely hung-up, but windows doesn't want to do anything more.
>
> DR-DOS/MS-DOS: Both of these end up the same way, so I'll put them
> together. Everything is exactly the same up until this point as FreeDOS
> except the '.\system' thing. Both of these DOS manage to complete the
> file copy and move on to the printer setup, and afterwards the network
> configuration. However, after the network configuration, both of them
> crash with the same GPF: WINSETUP.EXE caused a GPF in WINSETUP.EXE at
> 0001:113b. The address is the same _every time_ the installation is
> attempted.
>
> If I quit the dosemu session and attempt to resume the already
> half-completely installation, it is no use; it still crashes in the same
> spot after the network setup.
>
> Ok, so I give up on WFW3.11. Perhaps the networking portion is giving
> the dosemu some trouble. So, I try good (bad?) old Win3.1. All DOS
> gives me the same results here. The initial file copy completes, then
> crashes to dos instead of starting windows. Windows can be started
> manually in the same way as before. The initial configuration is ok, it
> asks for a disk this time (I point it to the dir on the hdd), and
> eventually it GPF at the same segment but a different offset this time
> after the files are copied.
>
> One difference: It complains about the mismatching of "system files",
> which I guess means that it doesn't like the OS/2 windows files as much
> as WFW3.11 did.
>
> I want to stress that the crash addresses are not random occurrences;
> they are repeatable and deterministic. Only once in the whole night did
> I have an unexplainable GPF while doing all these installations, which
> is about in line with windows' track record anyway... :)
>
> So, I hope this feedback helps somehow, please let me know if you have
> any more questions. I would like to be able to fully install WFW3.11
> under dosemu, and if the bugs can be worked out, I'll create a HTML
> walkthrough with screenshots.
>
> See ya,
>
> --
> Ryan Underwood, <nemesis at icequake.net>, icq=10317253
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2003-09-21 5:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 12:35 win3.1 attempts :) Ryan Underwood
2003-09-20 12:42 ` Ryan Underwood
2003-09-20 13:11 ` Bart Oldeman
2003-09-21 5:01 ` Barnowl [this message]
2003-09-21 5:45 ` Ryan Underwood
2003-09-21 15:28 ` Barnowl
2003-09-22 4:18 ` Ryan Underwood
-- strict thread matches above, loose matches on Subject: below --
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-21 10:06 Stas Sergeev
2003-09-22 6:18 ` Ryan Underwood
2003-09-22 7:11 ` Ryan Underwood
2003-09-22 17:11 Stas Sergeev
2003-09-23 4:48 ` Ryan Underwood
2003-09-23 17:08 Stas Sergeev
2003-09-24 4:52 ` 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=20030921000155.70fb78f6.barnowl@uronramp.net \
--to=barnowl@uronramp.net \
--cc=linux-msdos@vger.kernel.org \
--cc=nemesis-lists@icequake.net \
/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