Re: ADT long filename bug?

[Knut Roll-Lund <kr-lund@nogarbage.online.no>]

Hi

The manual: We should probably note some amendments to the next ADT 
manual. I found that it suggests a SSC setting that will not work with 
other comm programs. I would like there to be an explanation around this.

>   Everything works fine except the "long filename" support apparently. When 
> I type in a file longer than 8.3 characters ADT on my apple (receive mode) 
> it says it can't find the file and the ADT client on my PC, running windows 
> 2K, hangs. Specifically the process goes to 100% cpu occupancy, so I need to 
> terminate it. To work around this problem, I simply rename the file to a 
> shorter name and transfer it without problems.

I had to recheck this (didn't look at the code yet). I had the idea that 
it could do long filenames which would be natural because adtwin uses 
winapi.

What I found by trial and error is that it does long filenames but no 
longer than 14 characters including the extension. It has no problems 
with spaces, it is only the length.

Another indication is that even the short name won't work for a long 
filename longer than 14 characters, but works fine if the long name is 
only 14 characters.

This is probably a problem internally in adtwin because it displays the 
name correctly as written on the Apple.

Also the error handling is not good enough in adtwin, you have to 
disconnect and connect again as well as pressing the 'Reset (ESC)' 
button (on Win95... might not work on Win2k with its lack of realtime 
properties any sensible realtimesystem has. I love its splash screen 
'Built on NT technology' knowing that NT stands for 'New Technology').

Also, it seems to be completely case insensitive.

Knut