Hi!
18-Янв-2005 11:36 [EMAIL PROTECTED] (Alain) wrote to
freedos-devel@lists.sourceforge.net:
A> I eny case here is the axplanation about may and can:
A> He can do that. => He is phisicaly able to do that.
A> He may do that. => 1) He is allowed to do that. or 2) Pehaps he will
A> chose to do that
Arkady V.Belousov escreveu:
Huh. For me, with my poor self-teached English, all above sounds as
mumba-yumba. :)
First of all, let me state that your english is much much better then
when we startd tlaking about cute mouse. In fact I see that now you
understand most enghish idioms and stran
Hi!
16-Янв-2005 04:15 [EMAIL PROTECTED] (Michael Devore) wrote to
freedos-devel@lists.sourceforge.net:
>>MD> As far as UMB's, I'm not sure if turning off the A20 line affects memory
>>MD> mapping from physical odd-address Mb. Seems like it should,
>> Michael, strange to see such sentences f
At 04:19 AM 1/16/2005 +0300, Arkady V.Belousov wrote:
MD> As far as UMB's, I'm not sure if turning off the A20 line affects memory
MD> mapping from physical odd-address Mb. Seems like it should,
Michael, strange to see such sentences from you. A20 is a pin of (186
and higher) CPU, which used
Hi,
Arkady V.Belousov escribiÃ:
MD> I don't think it affects anything important.
MD> As far as UMB's, I'm not sure if turning off the A20 line affects memory
MD> mapping from physical odd-address Mb. Seems like it should,
Michael, strange to see such sentences from you. A20 is a pin of (186
an
Hi!
12-Янв-2005 17:46 [EMAIL PROTECTED] (Michael Devore) wrote to
freedos-devel@lists.sourceforge.net:
>>MD> Nothing on an application level should need to disable A20 and if it did,
>>MD> it would crash things loaded in a UMB due to loss of memory access, not to
>>---
Hi!
13-Янв-2005 23:11 [EMAIL PROTECTED] (AITOR SANTAMARIA MERINO) wrote to
freedos-devel@lists.sourceforge.net:
>>ASM> .486p
>>ASM> What happens in that case if I have a pure 386?
>>Nothing wrong, unless you use in your source some 486-specific
>>instruction and try to execute it on 386.
ASM>
Hi,
- Mensaje Original -
Remitente: Michael Devore [EMAIL PROTECTED]
Destinatario: freedos-devel@lists.sourceforge.net
Fecha: Jueves, Enero 13, 2005 1:21am
Asunto: Re: [Freedos-devel] Questions on EMM386 (part2 and last)
>At 03:57 PM 1/12/2005 +0300, Arkady V.Belousov wrote:
&
Hi,
- Mensaje Original -
Remitente: "Arkady V.Belousov" [EMAIL PROTECTED]
Destinatario: freedos-devel@lists.sourceforge.net
Fecha: Miércoles, Enero 12, 2005 2:12pm
Asunto: Re: [Freedos-devel] Questions on EMM386 (part2 and last)
>Hi!
>4-ñÎ×-2005 01:00 [EMAIL P
At 03:57 PM 1/12/2005 +0300, Arkady V.Belousov wrote:
MD> Nothing on an application level should need to disable A20 and if it did,
MD> it would crash things loaded in a UMB due to loss of memory access, not to
--^^^ HMA ?
MD> mention DOS image loaded high going
Hi!
4-Янв-2005 20:05 [EMAIL PROTECTED] (Michael Devore) wrote to
freedos-devel@lists.sourceforge.net:
>>Can freedos be use in a real-time environment successfully?
Yes, of course, because DOS itself doesn't uses machine resources until
you call it explicitly. On the other side, DOS is not a
Hi!
3-Янв-2005 19:20 [EMAIL PROTECTED] (Michael Devore) wrote to
freedos-devel@lists.sourceforge.net:
>>local_disable_a20:
>> mov ax,1
>> mov bl,0
>> retf
MD> Nothing on an application level should need to disable A20 and if it did,
MD> it would crash things loaded in a UMB due to loss of m
Hi!
4-Янв-2005 01:00 [EMAIL PROTECTED] (Aitor Santamarэa Merino) wrote to
freedos-devel@lists.sourceforge.net:
ASM> (1) This one is easy:
ASM> .486p
ASM> Does this mean to use 486-specific instructions (that is, not to
ASM> complain if one comes across 486-specific instructions)?
This one j
Hi!
3-Янв-2005 22:11 [EMAIL PROTECTED] (Alain) wrote to
freedos-devel@lists.sourceforge.net:
>> the next remaining big todo for EMM
>> is to have XMS/EMS shared memory pools,
A> Is this really important? Do many people need this on OLD hardware?
This not relates to "old hardware". "Shared p
if the real-time is INSIDE your program: yes
if you want a real-time-OS to run many programs: no
Alain
[EMAIL PROTECTED] escreveu:
Can freedos be use in a real-time environment successfully?
Chris
---
The SF.Net email is sponsored by: Beat the pos
At 06:01 PM 1/4/2005 -0500, Chris wrote:
Can freedos be use in a real-time environment successfully?
Kind of depends on your task priority needs and data collection, interface,
latency, and throughput requirements. You could use FreeDOS for a
stock-ticker program without fear, but I would stay a
Can freedos be use in a real-time environment successfully?
Chris
---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://
At 02:05 PM 1/4/2005 +0100, Aitor Santamaría Merino wrote:
Michael Devore escribió:
Now one more future wishes question: I guess that after Michael's
excellent work through VCPI and VDS, the next remaining big todo for EMM
is to have XMS/EMS shared memory pools, does it mean that EMM's XMS
manag
Hi Michael,
Thanks for your reply.
Michael Devore escribió:
Now one more future wishes question: I guess that after Michael's
excellent work through VCPI and VDS, the next remaining big todo for
EMM is to have XMS/EMS shared memory pools, does it mean that EMM's
XMS manager is enlarged to XMS fu
At 01:00 AM 1/4/2005 +0100, Aitor Santamaría Merino wrote:
.486p
Does this mean to use 486-specific instructions (that is, not to complain
if one comes across 486-specific instructions)? What happens in that case
if I have a pure 386?
A 386 won't kick out a 486 protected instruction to be emulate
Aitor Santamaría Merino escreveu:
[...]
Now one more future wishes question: I guess that after Michael's
excellent work through VCPI and VDS,
Yes, indeed :)
the next remaining big todo for EMM
is to have XMS/EMS shared memory pools,
Is this really important? Do many people need this on OLD hard
Hi,
I've been further reading more concisely the sources of EMM386, and came
up with more questions, this time the last ones (I don't go into the
detail of knowing exactly every single line of the EMM manager, for
example; I just want to understand its functioning). I hope you can help
me this
Hi,
Michael Devore escribió:
As it is currently a quite active development project, any nontrivial
changes to EMM386 unrelated to fixing a verified bug should be sync'ed
through me or Tom. Unannounced code changes to EMM386 could make
Michael cry and misbehave.
Sure :)
Aitor
---
Hi,
Thanks to all (Jeremy, Tom, Eric, Arkady), I just reply to Arkady
because it's more convenient for the replies...
Arkady V.Belousov escribiÃ:
Hi!
3-ÐÐÐ-2004 19:12 [EMAIL PROTECTED] (Aitor SantamarÑa Merino) wrote to
[EMAIL PROTECTED]:
ASM> (2) What is the meaning of this structure? How much m
At 07:12 PM 12/3/2004 +0100, Aitor Santamaría Merino wrote:
Hi there,
I have started reading EMM386.ASM (not the latest "hot" version, but the
previous one, not many changes I assume), and although I haven't yet
finished, I think I'd need a couple of hints on some things there. BTW
quite an inte
Hi!
3-Дек-2004 19:53 [EMAIL PROTECTED] (tom ehlert) wrote to Aitor Santamarэa
Merino <[EMAIL PROTECTED]>:
>> (5) In the startup of the driver, it is set 00AAh into memory
>> 0040h:0072h, but I can't find references to this BIOS variable, what is
>> that?
te> it's LPT4. and scince ther's no LPT4,
Hi!
3-Дек-2004 19:12 [EMAIL PROTECTED] (Aitor Santamarэa Merino) wrote to
[EMAIL PROTECTED]:
ASM> (2) What is the meaning of this structure? How much memory does it
ASM> weight actually, or how does the assembler determine that? (the bit that
ASM> I ignore is the (?))
ASM> RES_STACK SEGMENT PARA
Aitor Santamaría Merino wrote:
I can't answer anything emm386 specific, but maybe this'll help a little
until Michael/Tom/? answers.
Hi there,
I have started reading EMM386.ASM (not the latest "hot" version, but the
...
(2) What is the meaning of this structure? How much memory does it
weight act
Hello Aitor,
I leave the rest to michael, but
> (4) What are those special comments/marks for? What are they indicating?
> They are all over the sources
> ; (*-9-*)
> ; (#-9-#)
that's historic, kind of pre-diff;
it was published (printed) in several versions, and the later ones
had
; (*-9-*)
Hi there,
I have started reading EMM386.ASM (not the latest "hot" version, but the
previous one, not many changes I assume), and although I haven't yet
finished, I think I'd need a couple of hints on some things there. BTW
quite an interesting pierce of work! :-)
I suppose some of them are relat
30 matches
Mail list logo
