On Sat, 20 Sep 2003, Ryan Underwood wrote:
Hi,
On Sat, Sep 20, 2003 at 10:04:00PM +0400, Stas Sergeev wrote:
Hello.
Ryan Underwood wrote:
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
Hello,
On Fri, Sep 26, 2003 at 11:22:59AM -0400, Justin Zygmont wrote:
WINE does run 16-bit applications to some degree of success. I have some
16-bit programs that it does not run however.
if you want, you could try WABI, I have it and it ran most 16 bit apps
quickly and easily, I was
Hello.
Ryan Underwood wrote:
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.
Just tried under pure DOS - the same
problems. So I suspect it is the os2k386
that is buggy at that point.
Hi,
On Tue, Sep 23, 2003 at 09:08:04PM +0400, Stas Sergeev wrote:
The harm is a waste of time only.
And btw, this was not a shot in the dark.
As both that windows (3.1 and wfwg) are
using a standard mode during the install,
replacing the dosx.exe was the most
obvious thing it seems.
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,
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
Hi Evan,
On Sun, Sep 21, 2003 at 10:28:49AM -0500, Barnowl wrote:
Ryan-
it was the GUI. what kind of magic was need I do not know. The
fellow that did it was a one of those crackpot programers that liked
to recode their Bios so they could over clock the CPU's better. Last I
heard he and 3
One other thing to mention: if the installation is aborted by selecting
an Exit installation or whatever button in the windows portion of the
setup; upon returning to DOS, there is some sort of fatal memory error
in only FreeDOS (DR-DOS and MSDOS are fine):
Invalid Opcode at 7272 E8DF 3293 EC83
On Sat, 20 Sep 2003, Ryan Underwood wrote:
One other thing to mention: if the installation is aborted by selecting
an Exit installation or whatever button in the windows portion of the
setup; upon returning to DOS, there is some sort of fatal memory error
in only FreeDOS (DR-DOS and MSDOS are
Hello.
Ryan Underwood wrote:
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.
With a 16-bit windows? Probably not very usefull.
For each of these, I
Hi,
On Sat, Sep 20, 2003 at 10:04:00PM +0400, Stas Sergeev wrote:
Hello.
Ryan Underwood wrote:
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.
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 [EMAIL PROTECTED] wrote:
Hi,
So, armed with a fresh copy of
12 matches
Mail list logo
