Everhart,Glenn From: Gotfryd Smolik [gotfryd@stanpol.com.pl] Sent: Tuesday, March 10, 1998 1:44 PM To: Everhart,Glenn Cc: Info-VAX@Mvb.Saic.Com Subject: RE: PC CD's with non-VMS filenames On Mon, 9 Mar 1998, Everhart,Glenn wrote: +The problem is that these PC CDs are in violent disagreement +with the ISO standard, in which ~ is not a legal character. It may be +that the RMS mods for ODS5 support will allow these filenames to +be used, but the ISO ACPs for VMS are standards compliant. +Common Microsoft written CDs are not. Totally agree. The first reason is the "~" as standard Windows setting for long filename, but *also* the national character and b.ex. "!" (where are in DOS allowed all time). Have check three WindowsPC bazed CD-R writer program for the (not precise, but in general) known ISO limitation and *all* have "done ok" check (from menu "check for ISO compatibility") for name where in violation of the standard... The DOS/Windows user haven't any chance to properly check if the CD-R image is ISO/HighSierra compliant ! -:( +There is a system interface editor for msdos that I've seen that +causes it not to use ~ in short filenames all the time. May I am miss whay you mean, but IMO you will say about Windows95 (and 98) where have the long file name and save the short-name for old DOS function compatibility. Here are some clickable utilities around, but forcing the system to not use "~" may be done creating/changing (it isn't created by default !) with REGETIT in the key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\FileSystem a value named: NameNumericTail of value= 0 (regedit will automatically convert it to the appriopiate format for longword, don't care). + With that set up, it'd be possible to write CDs that had + less of the offending filenames, ... less but not nothing as you write -:( [...] +I'd recommend using wiz for windows and making zipfiles out of +the stuff. Old good DOS ZIP or PKZIP are not worse -:) [original Arne]: +> > My only solution so far has been to do a wildcard +> > copy (*'s instead og illegal characters) and then +> > copy to a non-wildcard specification on a VMS disk. The "%" also works ! May be a .COM where check that f$parse doesn't return any character and what you find - generating manually the output filename ? The problem is, that here must be a decision *what* a name may have the file under VMS ! +> > COPY, BACKUP, EXCHANGE and PCDISK did not solve the +> > problem. The "output file name" problem ! +> > DIR/FIL reveals FID's, so maybe I could make a program +> > copying using FID as input specification. ...where must resolve exactly the same problem ! Procedure in DCL may do the same (slower...). Haven't you have a PC with CD and SAMBA or Patchworks ? +> > But someone must have had this problem before me ! ...Unresolved ? Have seen here ! Can't check at the time b.ex. if a "~" in directory name is a problem or can also get around with the "%": have check multiple CD-R but all are for directory name ISO standard... Only one (from PC magazine) have one dir with "~" but unfortunately epmty -:( +> Arne [...] Regards - Gotfryd -- ===================================================================== $ ON F$ERROR("LANGUAGE","ENGLISH","IN_MESSAGE").GT.F$ERROR("NORMAL") - THEN EXCUSE/OBJECT=ME $! GS@stanpol.zabrze.pl =====================================================================