> I can't duplicate the XMS memory block fragmentation with DOOM or anything
> else handy, so whatever's happening depends upon the gameplay or memory
> configuration or moon phase or any of the usual suspects.
The errer has been described in Bugzilla more accurately. Especially it is
mentioned
> Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386/ are the files
> emmx220.zip, EMM386 version 2.20 memory manager, mostly executable files;
> and emms220.zip, source code files.
Thanks :-).
> This release of EMM386 and HIMEM has several changes and fixes, two of a
> low-level nature, b
Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386/ are the files
emmx220.zip, EMM386 version 2.20 memory manager, mostly executable files;
and emms220.zip, source code files.
This release of EMM386 and HIMEM has several changes and fixes, two of a
low-level nature, but at a guess, relati
On Tue, 25 Jul 2006, Michael Devore wrote:
> Here's my initial problem with this idea: it works when you get step
> outside of the Qemu DOS sandbox. Plus it works (or worked) in Bochs, since
> I remember testing it under Linux a year or two ago when trying to figure
> out what the heck was going
Japheth wrote:
>> environment. Even better would be a good explanation for why the problem
>> only manifests itself with that specific environment and application.
>
> I've looked into the Qemu BIOS code for int 15h, ah=C2. Usually the code
> found
> in "real" BIOSes is programmed very "defens
At 09:22 AM 7/26/2006 +0200, Japheth wrote:
> > environment. Even better would be a good explanation for why the problem
> > only manifests itself with that specific environment and application.
>
>I've looked into the Qemu BIOS code for int 15h, ah=C2. Usually the code
>found
>in "real" BIOSes i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello
>>> out what the heck was going on with CTMOUSE and Qemu. And it only seems to
>>> fail with CTMOUSE and not other programs which use interrupts a lot more
>>> creatively. (I should check VPC 2004 now and see which side of the fence
>>> it fal
I think that is what happend to me (twice) with freedos instalation very
long ago. Ofcourse at the time no-one could help me and the problem is
non-reproductible because it fixes itself!
I vote against this and ih favor of some warning message so that the MBR
only gets written in the end if som
I was just installing freedos.
Seems that fdisk doesn't allow you to change between FAT16 and FAT32.
When you choose FAT32 support on an 800MB image, it will create a FAT32
partition automatically.
Maybe there should be a message indicating this?
Imre
PS. it stops halfway the installation, b
> EA> You said that the "if no MBR 55aa found, replace ALL code and
> EA> partition data in the MBR with an empty MBR" function in FDISK,
> EA> which has caused a lot of data loss in the past, would be
> EA> necessary to handle wiped / new / virtual harddisks properly.
> EA> Who would like to help
Eric Auer schreef:
> Hi all,
>
> for extra fun, I traced through the installer batch
> files in the new fdbasecd (1.0 preview 2 cdrom iso)
> tonight... The new ISOLINUX 3.11 still did not like
> me (hangs on boot), but I could again use the special
> boot diskette... The cdrom driver liked my dvd d
Hello Michael,
>>INT xx enters the interrupt handler with IF cleared, so this should be
>>done also when being rerouted through the v86_monitor; looks like a
>>plain bug to me
>> > Changing a long-standing fundamental behavior to fix a single problem in a
>> > virtual environment with one progra
At 02:22 PM 7/26/2006 -0500, I wrote:
>I can't duplicate the XMS memory block fragmentation with DOOM or anything
>else handy, so whatever's happening depends upon the gameplay or memory
>configuration or moon phase or any of the usual suspects.
Okay, I can get minor XMS free block fragmentation
Hi!
27-Июл-2006 13:37 [EMAIL PROTECTED] (Japheth) wrote to
[email protected]:
>> This is bug.
J> Don't choose so rude words! Be more polite! Instead say: "This could be
J> improved possibly?"
:) _Violating specifications_ is a bug, especially if it leads to
hangs. Thi
> This is bug.
Don't choose so rude words! Be more polite! Instead say: "This could be
improved possibly?"
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the ch
Hi!
26-Июл-2006 07:01 [EMAIL PROTECTED] (Imre Leber) wrote to
[email protected]:
>>out what the heck was going on with CTMOUSE and Qemu. And it only seems to
>>fail with CTMOUSE and not other programs which use interrupts a lot more
>>creatively. (I should check VPC 2004 now a
Hi!
25-Июл-2006 21:48 [EMAIL PROTECTED] (Japheth) wrote to
[email protected]:
>> QEMU has never liked CTMOUSE under FreeDOS, and possibly MS-DOS. I don't
>> know why.
J> when I modify emm386.asm, proc v86_monitor, so that the IF in real-mode is
J> cleared for all interrupts rou
17 matches
Mail list logo
