home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.lang.pascal.borland      Borland Pascal was actually pretty neat      2,978 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 1,459 of 2,978   
   Dr John Stockton to All   
   Re: Detecting whether a file has a Long    
   11 Mar 05 23:46:52   
   
   From: spam@merlyn.demon.co.uk   
      
   JRS:  In article , dated Fri, 11   
   Mar 2005 07:05:22, seen in news:comp.lang.pascal.borland, Jason Burgon   
    posted :   
   >"Dr John Stockton"  wrote in message   
   >news:6itSE1Dt3LMCFwGH@merlyn.demon.co.uk...   
   >   
   >> ISTM that what you say implies that in WinME a traditional DOS 32-byte   
   >> entry may contain a mixed-case 8.3 name.  If that applies to floppies   
   >> written to by WinME, I'd expect problems in reading them on a classical   
   >> system.   
   >   
   >No. The SFN (standard DOS) entry will contain only 8-bit, DOS codepage   
   >dependant uppercased characters. The LFN "cooked" entries (that are almost   
   >transparent to standard DOS) will contain Unicode/ISO-10646-1 16-bit   
   >characters of any case.   
   >   
   >IIRC, if an 8.3, DOS compatible, all-uppercase, 7-bit ASCII-only filename is   
   >created by Win9x/ME (and possibly NTxx as well on FAT drives), then no LFN   
   >entries will be created for that file/folder. Because VFAT is   
   >case-preserving, this means that if the file/folder name contains any   
   >lowecase characters (or chars > #127, or...), then an LFN entry has to be   
   >generated.   
      
   Just to clarify : you're saying that there's no problem with the case of   
   letters in floppies because [my understanding of] FV is wrong.   
      
           But the SFN entry contains bytes, not characters; it is the   
           visual interpretation which is codepage dependent (so #$E5,   
           which I called sigma, could be seen as Otilde or nhacek or ???   
      
   However, you are saying that the presence of (codepage 437; shift-and-3   
   to us) #156 = £ (GBP), which behaves normally in true DOS, is enough to   
   generate a LFN entry in Win32?  If so, that may be a case of having an   
   LFN that does not necessarily need to be counted as such.   
      
   AIUI, the presence of ~ in position 7 of DIR output does not prove that   
   the file has a LFN entry (one can create file ABCDEF~1.EXT in pure DOS);   
   and the absence does not prove that it does not (one can create file A.b   
   in Win32).   
      
   --   
    © John Stockton, Surrey, UK.  ?@merlyn.demon.co.uk   DOS 3.3, 6.20; Win98. ©   
    Web   - FAQqish topics, acronyms & links.   
    PAS EXE TXT ZIP via     
    My DOS   - also batprogs.htm.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca