On Apr 17, 3:20 pm, s...@antinode.org (Steven M. Schweda) wrote:

> That's a different problem. My complaint was triggered by long names
> on an ODS2 disk. I was assuming that it'd have troubles with the carets
> on ODS5, but apparently it's significantly worse than that.

The real 'fix' is for hp to add a 'unix compatibility mode' to it's
ftp server. Enabled by a logical name perhaps. No GUI FTP client can
read the listings so it's going to have problems manipulating the
files. You can't expect every GUI FTP client to have special code to
deal with ODS5, but you could expect HP to provide a 'unix' compatible
ftp server so all those GUI FTP clients out there work again.

--
-- Carl Karcher, Waisman Computing Services, Waisman Center, UW-
Madison
--

Carl Karcher wrote:
> On Apr 17, 3:20 pm, s...@antinode.org (Steven M. Schweda) wrote:
>> That's a different problem. My complaint was triggered by long names
>> on an ODS2 disk. I was assuming that it'd have troubles with the carets
>> on ODS5, but apparently it's significantly worse than that.
>
> The real 'fix' is for hp to add a 'unix compatibility mode' to it's
> ftp server. Enabled by a logical name perhaps. No GUI FTP client can
> read the listings so it's going to have problems manipulating the
> files. You can't expect every GUI FTP client to have special code to
> deal with ODS5, but you could expect HP to provide a 'unix' compatible
> ftp server so all those GUI FTP clients out there work again.

HGFTP can do that.

Arne

In article <89ec2aa2-ed5f-4cbd-88e6-4e71283e934f@d45g2000hsc.googlegroups.com>, Carl Karcher writes:
>
> The real 'fix' is for hp to add a 'unix compatibility mode' to it's
> ftp server. Enabled by a logical name perhaps. No GUI FTP client can
> read the listings so it's going to have problems manipulating the
> files. You can't expect every GUI FTP client to have special code to
> deal with ODS5, but you could expect HP to provide a 'unix' compatible
> ftp server so all those GUI FTP clients out there work again.

Nope. I expect all those clients out there to start following the
RFC, or maybe an update to the RFC (not likely), instead of all the
vendors having to make up for those who don't follow the RFC.

There's nothing going on with file names on an ODS-5 disk which isn't
handled by the RFC.

Steven M. Schweda wrote:
> From: Marty Kuhrt
>
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=427887
>
>> I'm not sure if this is the same issue, but I've noticed that Firefox
>> doesn't see files with lowercase file name parts, either. It'll see
>> TEST.TXT but not TEST.txt or test.txt.
>
> That's a different problem. My complaint was triggered by long names
> on an ODS2 disk. I was assuming that it'd have troubles with the carets
> on ODS5, but apparently it's significantly worse than that.
>
> I was hoping to generate some interest from someone who already has a
> Mozilla/Firefox build environment set up, as that looked like a
> career-sized project all by itself, which I was hoping that I could
> avoid. (Well, of course I can avoid it, but I'd like to get the stuff
> working properly with VMS, too. Everything's complicated.)

The result was the same with Multinet 5.2, as well. If you want a real
laff on the Mac, try using Safari to do ftp:// stuff. Firefox may be a
bit odd, but Safari won't do it at all (at least in my case).