(before someone, e.g. Eric complains, mind that I was forced to use webmail in this
message, so I have no control over the format of the message)
- Mensaje Original -
Remitente: "Arkady V.Belousov" [EMAIL PROTECTED]
Destinatario: [EMAIL PROTECTED]
Fecha: Martes, Junio 22, 2004 11:41a
>Hi!
>22-éÀÎ-2004 13:00 [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote to
>[EMAIL PROTECTED]:
>>>ASM> using EMM386 to provide UMBs, you may get troubles with DMA
>because of
>>>ASM> the mismatch of linear and physical addresses.
>>>FD currently compares buffer address (in dsk.c and blockio.c)
>w
Hi,
I post here because I am unable to test standalone FreeDOS, and I seem to remember
someone complained about this, can someone test whether the problem affects standalone
FreeDOS (so that I refer to DOSEMU) (I'm not at my best testing conditions now, but
would be grateful to be able to run
Hi,
>
>Hello.
>I have three questions:
>1. Does freeDOS have a ramdisk and if so how do I use it?
Try TDISK:
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/ramdisk/
(up to mirrors)
>2. What does execrh do?
Execute a device driver request packet. That is, catch a devic
Hi Bernd,
>Any idea for a compressed COUNTRY.SYS file? Kernel decompression
>code
>overhead should be minimal.
>28KB uncompressed versus 5KB compressed is quite a difference, for
>bootdisks.
>I have no idea how all the NLS/country/codepage stuff works, except
>COUNTRY=031,858,C:\FDOS\BI
Hi,
>> What does the German version of MS-DOS expect for yes/no?
>it expects J(a) or N(ein), but the question is also
> Sind Sie sicher ?
>> The Spanish one expects "S" and "N", so it is
>> actually translated.
>but the question is probably
> Es usted seguro ?
>and not
> Are you sure ?
>
>tom
Hi,
>Hi!
>4-îÏÑ-2004 17:52 [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote to
>[EMAIL PROTECTED]:
>ase> Divide tools in three types:
>ase> (a) Those that implement the national settings (that is the
>character you
>ase> use for thousand separators, etc) and codepages for the kernel
>(filena
Hi,
Finally I am trying to implement the APPEND command in BC, with the resident code
written in NASM. However, I get the following strange behaviour:
(1) I am able to GET the int21h handler, to hook it, and to JMP to the old int21h
handler. However, if I try to CALL it (of course I PUSHF b
>Hi Alain,
>> Only one program is missing and that is a Scan-Disk (written as 2
>words)
>> utility for Fat32. For what I kow, DOSFSCK is working and need
>only a
>> small fixes in the read sector.
>I strongly disagree. Our SCANDISK for FAT1x is completely defunct,
>so we
>have no SCAND
>Of course! Neither do we call LBACACHE a SMARTDRV, don't we?
>If we can live without a true SMARTDRV, we can live without a true
>SCANDISK too.
The case is not comparable either. I seem to recall (Alain was it you?) that it was
mentioned copyright issues over the label "SMARTDRV", but I don
Hi,
>Hi!
>1-áÐÒ-2004 00:22 [EMAIL PROTECTED] (Aitor Santamari'a Merino)
>wrote to
>[EMAIL PROTECTED]:
>>>JL> Just a suggestion, because the program high and low area is very
>>>JL> clear, just a glance can see how many memory it take.
>>> For this should be used option /C (which is ye
11 matches
Mail list logo
