Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!ut-emx!ccwf.cc.utexas.edu From: daveh@ccwf.cc.utexas.edu (David H. Huang) Newsgroups: comp.sys.apple2 Subject: Re: GS/OS and lower case Message-ID: <44890@ut-emx.uucp> Date: 1 Mar 91 01:58:54 GMT References: <7734@crash.cts.com> Sender: news@ut-emx.uucp Reply-To: daveh@ccwf.cc.utexas.edu (David H. Huang) Organization: The University of Texas at Austin Lines: 30 In article cmcurtin@bluemoon.uucp (Matthew Curtin) writes: >mikef@pro-harvest.cts.com (Mike Fleming) writes: > >> GS/OS's ProDOS FST stores filenames the same as ProDOS 8 always did--in all >> upper case. The difference is that GS/OS (And any P8 program--suck as >> Shrinkit 3.2-- that knows about it) uses the VERSION and MIN ^^^such >> VERSION as flags to determine weather a character should be upper or lower >> case. > >Really? I read (Gary Little's ProDOS 8 and GS/OS Reference, I think) that >not only can GS/OS understand LOWER CASE, but it could also understand the >slash (/) character as a legitimate for filenames, as GS/OS actually uses >colon (:) to separate directories, but haven't been able to get that to >work.... Why? GS/OS CAN understand lowercase, but ProDOS can't (at least not in the filename itself). So, the ProDOS FST puts the lowercase info in the version flags. Same thing with the "/" in filenames. GS/OS does allow "/"s in filenames, but ProDOS doesn't. The slash will be used as a directory separator if the volume name starts with a slash. If the volume name starts with a colon, a slash will be used as part of the filename, if possible. Also, how are you trying to use the colon as a separator? It works fine for me within the parameter lists for GS/OS calls. You can't use the colon in Prodos 8 programs though... -- David Huang | Internet: daveh@ccwf.cc.utexas.edu | "Slight accidents with funny rays UUCP: ...!ut-emx!ccwf.cc.utexas.edu!daveh | can have serious consequences" America Online: DrWho29 |