Hello,
2009/2/4 Eric Auer :
>> FreeDOS KEYB 2.0 (pre4)
>> Critical error: cannot allocate memory.
>> DOS reported error: 8
>
> For DISPLAY, you would expect XMS to be used, but for KEYB?
That is MCB allocate, function 48h.
Used to allocate data in an independent MCB block, so that KEYB is
made in
>> Well, I could introduce a ramdisk but I don't really like to.
>
> You have to. SET /E uses a temporary file for the output of the command,
> just as pipes do.
Yes; in a single-tasking environment, it is difficult to avoid using a
temporary file for pipes, but you could also write a utility to
>>> On read-only media the 'set /e bootdevice=bootdev' will create an error
>>> due to write protection. How this can be solved?
>>
>> Did you set the TEMP or TMP environment variable to a directory on a
>> writable drive?
>
> No, there is no writable device.
>
> Well, I could introduce a ramdisk b
Christian Masloch schrieb:
>> On read-only media the 'set /e bootdevice=bootdev' will create an error
>> due to write protection. How this can be solved?
>
> Did you set the TEMP or TMP environment variable to a directory on a
> writable drive?
No, there is no writable device.
Well, I could in
> On read-only media the 'set /e bootdevice=bootdev' will create an error
> due to write protection. How this can be solved?
Did you set the TEMP or TMP environment variable to a directory on a
writable drive?
--
Create
Eric Auer schrieb:
> Hi Michael,
>
>> I need a variable %bootdevice% (or w/e) pointing to the current
>> session's boot device (A:\ or C:\).
>
> Nice :-)
>
>> Is there such a variable or can you tell me how to set
>> this variable automatic in batch?
>
> I do not remember one, but it is extreme
> I assumed you were talking about the functionality, not
> about the files! For adding FILES into the kernel, you
> would need something like that "very special boot image
> of a ramdisk, inside the kernel binary" which needs extra
> support both in the kernel (to make it visible with some
> drive
