At 06:37 PM 8/4/2006 +0200, Japheth wrote:
> The issue is of minor general interest, since most FD users will
>use FD Himem and FD Emm386 with the standard parameters.
I've finally been able to duplicate a problem with DOOM under VPC 2004 set
at 512M, but not under straight FreeDOS with 1.5G fr
At 02:36 PM 8/4/2006 +0200, Japheth wrote:
>or if another Emm386 compatible XMS host is used (MS Himem or QHimem2),
>which lacks this (NO)X2MAX32 parameters at all
Incidentally, if anyone wants to see why HIMEM/XMS managers should support
a /X2MAX32 option, I have available a copy of the
Eric Auer <[EMAIL PROTECTED]> wrote on 08/04/2006 04:04:33 PM:
# > to merge its CONFIG.SYS into FDCONFIG.SYS. After that, I issued
# > "del config.sys", and received:
# >
# > Invalid Opcode at 5B00 1118 0292 147C 1482 3A43 435C 4EF4 4946 2E47
5953
# > 0053
#
# Possibly because you had DOSLFN
I've just installed yesterday's test ISO under Virtual PC 2004 SR1, and
have run into an issue with it.
I started up FD using option 3 (XMS only), and ran the MS LanMan setup
program. When I was done, I used EDIT to clean up the AUTOEXEC.BAT and
to merge its CONFIG.SYS into FDCONFIG.SYS. After
Hi!
4-Авг-2006 21:17 [EMAIL PROTECTED] (Japheth) wrote to
freedos-user@lists.sourceforge.net:
>> J> (apparently gives problems with extended keys).
>> Which ones?
J> As you possibly know, by reading port 60h you send the keyboard controller an
J> "interrupt acknowledged" signal, so it can se
> J> (apparently gives problems with extended keys).
>
> Which ones?
As you possibly know, by reading port 60h you send the keyboard controller an
"interrupt acknowledged" signal, so it can send the next byte. On real
hardware this takes some time (some microseconds at least), but qemu is
Hi!
4-Авг-2006 11:40 [EMAIL PROTECTED] (Michael Devore) wrote to
freedos-user@lists.sourceforge.net:
MD> However, it appears that the entire intent of this scouring of source code
MD> and run of changes was to eventually force a conflict by taking offense
MD> where none was intended or to refuse
Hi!
4-Авг-2006 18:37 [EMAIL PROTECTED] (Japheth) wrote to
freedos-user@lists.sourceforge.net:
J> hosts). So I did some research, found a bug and described in Bugzilla - IMO
J> sufficiently detailed for someone interested in the matter - what I've done
J> and that I was able to fix it.
Compl
Рш!
4-Авг-2006 18:50 [EMAIL PROTECTED] (Japheth) wrote to
freedos-user@lists.sourceforge.net:
>> But I agreed, that there not enough explanations what changed. For
>> example, I see, that eliminated call to INT 67/3F - but no commented why.
>> Also, I not see explanation, if move reading key
>
> In Japhet' source, I see _at least_ one important change: you eliminate
> "retf 2", but forgot "ret 2" in NEW15 (where you explicitly STI before
> exit). This not need any demonstrations.
>
> But I agreed, that there not enough explanations what changed. For
> example, I see, that e
At 06:37 PM 8/4/2006 +0200, Japheth wrote:
>The test case you are requesting, yes, sure, I didn't do that yet, since
>dealing with a fixed bug is like reading the newspaper of the day before
>yesterday. Compare this my lack of interest with your's not wanting to
>provide
>a working build environ
At 08:29 PM 8/4/2006 +0400, Arkady V.Belousov wrote:
>you. In Japhet' source, I see _at least_ one important change: you
>eliminate "retf 2", but forgot "ret 2" in NEW15 (where you explicitly STI
>before exit). This not need any demonstrations.
Nor was it reported.
> But I agreed, th
> Are you willing to do that trivial task and
> demonstrate an actual interest in helping to correct the issue, or will you
> just preach and post here?
Neither nor. The issue is of minor general interest, since most FD users will
use FD Himem and FD Emm386 with the standard parameters. For me
Hi!
4-Авг-2006 10:29 [EMAIL PROTECTED] (Michael Devore) wrote to
freedos-user@lists.sourceforge.net:
>>Since the error is evident in my eyes, I will not spent any more time to
>>proove this. But indeed there is no need to wait, and for those who might run
>>into the problem as I did, you can down
At 10:29 AM 8/4/2006 -0500, I wrote:
>At 01:22 PM 8/4/2006 +0200, Japheth wrote:
> > >
> > > Barring the fileset I requested, or other testable indication that your
> > > problem occurs with anyone else, I should not think that would be a
> > > problem. In other words, no need to wait for EMM386
At 01:22 PM 8/4/2006 +0200, Japheth wrote:
> >
> > Barring the fileset I requested, or other testable indication that your
> > problem occurs with anyone else, I should not think that would be a
> > problem. In other words, no need to wait for EMM386 3.0 - codenamed "The
> > Arkady Factor".
>
>Si
Hi!
4-Авг-2006 07:12 [EMAIL PROTECTED] (Blair Campbell) wrote to
freedos-user@lists.sourceforge.net:
>> I think, build subsystem _should_ be _added_ before "final" EMM386
>> version will be released - else, because "no more permanent, than
>> temporary", EMM386 may never get build subsystem,
Hi... I guess freedos-devel would be better than
freedos-user or off-list mails for this... Anyway ;-).
>> In other words, if you have more than 32 MB XMS2...?
> I don't know, once I had found the technical reason for the bug I
> stopped examine all possible configurations (with the exception o
I don't think it's too hard for a developer to add his makefile
himself. Lots of the FreeDOS source packages come without makefiles
or batch files.
On 8/4/06, Arkady V.Belousov <[EMAIL PROTECTED]> wrote:
> Hi!
>
> 3-Авг-2006 17:53 [EMAIL PROTECTED] (Michael Devore) wrote to
> freedos-user@lists.s
Hi!
3-Авг-2006 17:53 [EMAIL PROTECTED] (Michael Devore) wrote to
freedos-user@lists.sourceforge.net:
>>the final FD 1.0 should probably wait for upcoming Emm386 v2.22 to be
>>released :) .
MD> Barring the fileset I requested, or other testable indication that your
MD> problem occurs with anyone
I have been made aware that there is no description of the error I was
refering previously here on the list. That's true, sorry, it was described in
BugZilla. But a brief overview is:
- it requires Himem + FD Emm386 to be loaded
- it occurs when FD Himem has been started with parameter /NOX2MAX3
>
> Barring the fileset I requested, or other testable indication that your
> problem occurs with anyone else, I should not think that would be a
> problem. In other words, no need to wait for EMM386 3.0 - codenamed "The
> Arkady Factor".
Since the error is evident in my eyes, I will not spen
22 matches
Mail list logo
