[syslinux] COM32

Mortaza Doulaty mortaza.doulaty at gmail.com
Thu Jun 17 01:18:11 PDT 2010


Maybe some bug: I've a file named 'somthing.config' which resides in
Windows/System32/ in a FAT32 partition, surprisingly I can not access to it,
failing with errno=2, but I can access any other files in that location. Is
the problem caused by its name and extension which is not in 8.3 format?

On Thu, Jun 17, 2010 at 10:29 AM, Mortaza Doulaty <mortaza.doulaty at gmail.com
> wrote:

> >>Writing to anything on the local filesystem (except the ADV) is the
> invalid argument.
>
> Is ADV 'Tru64 UNIX Advanced File System'?
>
> So for writing to FAT partition there is no easy way, I should try to
> implement one, is this the case?
>
>
> On Wed, Jun 16, 2010 at 4:34 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
>
>> On Wed, Jun 16, 2010 at 06:06, Mortaza Doulaty
>> <mortaza.doulaty at gmail.com> wrote:
>> > To be more specific about the error, the file pointer (after trying to
>> > create a new file) is NULL and the error no is: 22 which is 'Invalid
>> > argument'.
>> >
>> > I tried reading from a file from the same location, it succeeded.
>> >
>>
>> Writing to anything on the local filesystem (except the ADV) is the
>> invalid argument.  You can't write to the FILE pointer as it points
>> towards a file.  I believe you could write to the FILE pointer if it
>> pointed towards stdout or stderr.  Some BIOSs are buggy hence writing
>> is disabled.
>>
>> There have been discussions on writing to the serial port and a TFTP
>> server (PXELINUX only) but I can't be certain of their status.  I know
>> HPA implemented something that made collecting a key piece (or set) of
>> diagnostic data easier than copying character for character something
>> on the screen (purely electronic in some way).
>>
>> > On Wed, Jun 16, 2010 at 1:54 PM, Mortaza Doulaty
>> > <mortaza.doulaty at gmail.com>wrote:
>> >
>> >> Hi,
>> >>
>> >> I've started my sample COM32 module, as the first step, I tried to
>> write to
>> >> a file in bootloader's file system itself.
>> >> When I call this module, the first printf (which prints an initial
>> message
>> >> on the console) works, but it hangs there. No file is created and the
>> >> program seems to hang.
>> >>
>>
>> --
>> -Gene
>>
>> "No one ever says, 'I can't read that ASCII(plain text) e-mail you sent
>> me.'"
>>
>> _______________________________________________
>> Syslinux mailing list
>> Submissions to Syslinux at zytor.com
>> Unsubscribe or set options at:
>> http://www.zytor.com/mailman/listinfo/syslinux
>> Please do not send private replies to mailing list traffic.
>>
>>
>



More information about the Syslinux mailing list