[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ADT long filename bug?
- Subject: Re: ADT long filename bug?
- From: "IceMan" <toomuch@spam.here>
- Date: Thu, 29 Dec 2005 23:29:01 GMT
- Newsgroups: comp.sys.apple2
- Organization: [Infostrada]
- References: <fbWsf.21457$eD5.356365@twister2.libero.it> <dp1jfm$q4v$1@unlnews.unl.edu>
- Xref: g2news1.google.com comp.sys.apple2:2743
Ed,
"Ed Eastman" <noone@nowhere.net> wrote in message
news:dp1jfm$q4v$1@unlnews.unl.edu...
> I think the main reason I never have issues is that I always name my DSK
> files without spaces or extra characters and under 15 chars in length,
> just to be safe. Sort of a ProDOS/ MSDOS hybrid.
One example of file which manifested this problem/bug was
"super_zaxxon.dsk" - this would hang ADT on the PC after the "file not
found" error. Renaming it to "szaxxon.dsk" worked fine.
> Hmm, I'm sitting here thinking about it and a thought pops into my head.
> Is he specifying the extension? The newer OS does not show the
> extension but the transfer does require it.
Yes I am.
> I'm still thinking about this and it hits me that you may need to
> transfer the 'short name' instead of the long name of the file.
> abcdef~1.dsk instead of ABCDEFGHI.dsk. This is what worked under Win98
> for me.
Well, the workaround is a simple rename - that's fine for me. The
strange thing is that the DIR command from the Apple lists all the lonf
filenames flawlessly, so it looks as if there's a bug somewhere on the PC
side. Infact, the PC side ADT says it cannot find the truncated "filename"
not the correct long filename - this is what made me realize it was a long
filename problem.
In any case, I am happy never-the-less!
Luke