On 11/29/16 12:50, Travis Siegel wrote:
>
> Because, apparently the nasm being called isn't in c:\devel\nasm, so
> change the path in the nasm.bat file to point to the proper place, and
> the problem should be solved. Either solution will work.
>
But why the batch file in the first place? It
On 11/24/16 00:59, Mateusz Viste wrote:
>
> Hi,
>
> Your problem is related to the fact that your "nasm" command doesn't call
> nasm.exe directly. Instead, it calls a batch file named nasm.bat which
> has been placed in your %PATH% by the FDNPKG installer. This nasm.bat
> file is pretty straig
On 08/26/16 14:12, H. Peter Anvin wrote:
>
> Memdisk already supports being a disk number other than 0x00 or 0x80,
> and the DL register will reflect that. However, I was thinking of
> provided a more explicit hint, so that scripts can reply on the
> ramdisk being, say, R:
>
On August 26, 2016 12:26:52 AM PDT, Eric Auer wrote:
>
>Hi HPA! The boot sector takes a BIOS drive number of the
>to-be-booted drive from the MBR, which can take it from
>the BIOS. There also are patches to take the MBR item by
>pointer from the MBR, but those are not used by default.
>
>So I gues
On 01/13/16 08:33, Eric Auer wrote:
>
> Hi HPA and Joao,
>
> support for EXT3 in the kernel would indeed be large/complex.
>
> Only supporting EXT3 READS already would take circa 10 kB of
> code, taking the size of the EXT2/3/4 GRUB module as example.
>
> I like MEMDISK bootable ramdisk style:
On 08/14/15 15:00, Till wrote:
>
> Quoting João Jerónimo :
>
>> Wouldn't it be better to use a redirector? This can be done with a TSR.
>>
>> João Jerónimo
>>
>
>
> A TSR redirector would be great for assigning an EXT3 drive to a drive
> letter for standard I/O operations. However a kernel d
I wanted to ask: to what degree does FreeDOS implement the redirector
interface? Are there any known incompatibilities?
The reason I am asking is that I started a project that I was never able
to find time finish (and don't expect to have any more for the
forseeable future) to write a 9pfs redire