I double checked the mComm code because I didn't remember if I had
addressed this. If the file is larger than 64k I only return the first
two bytes of the file size. So while it will work with files larger than
64k, the file size is definitely a little screwy. But I guess when you
exceed the limits that is to be expected.
Kurt
On Sat, Jun 2, 2018, at 1:19 PM, John R. Hogerhuis wrote:
> It's not in Laddie code. I found an old post regarding my DLPilot
> source (that I cannot find at the moment).>
> So I guess I need to incorporate this into LaddieAlpha for >64k files
> to work fully.>
> "OK, I found my DLPilot source. Based on that, TPDD files can be
> larger than 64K!>
> Here's the code to format directory-related requests. It clearly has
> support for > 64K size files.
>
> void format_11 (const UInt8 *namep, UInt16 name_len, UInt32 file_len)> {
> outchar (0x11);
> if ((file_len <= 65535) || (*namep) == 0)
> outchar (0x1C);
> else
> outchar (0x1E);
> outchars (namep, name_len);
> if ((*namep) == 0)
> outchar (0);
> else
> outchar ('F');
> outchar ((file_len >> 8) & 0xFF); //$$ ????
> outchar (file_len & 0xFF);
> if (file_len <= 65535)
> {
> outchar (0x9D);
> }
> else
> {
> outchar ('P');
> outchar ((file_len >> 24) & 0xFF); //$$ ????
> outchar ((file_len >> 16) & 0xFF);
>
> }
> outchar (checksum (resp, resp_len));
> }
>
>
>
> On Sat, Jun 2, 2018 at 9:23 AM, John R. Hogerhuis
> <[email protected]> wrote:>>
>>
>> On Sat, Jun 2, 2018 at 9:14 AM Kurt McCullum
>> <[email protected]> wrote:>>> __
>>> The file size is returned as two bytes per the protocol. As long as
>>> it returns a value less than 64k you should be fine as the packets
>>> don't care about how many are sent.>>>
>>> Kurt
>>>
>>
>>
>>
>> I remember there being 4 bytes of file size, though the upper 2 bytes
>> showed up elsewhere in the packet. Took some sleuthing. Unless I’m
>> making it up. I’ll look at laddie code.>>
>>
>> — John.
>>
