From: Paul Shirley Newsgroups: comp.os.msdos.djgpp Subject: Re: why are dir.h's file defines so small? Date: Sun, 26 Jul 1998 13:45:09 +0100 Organization: wot? me? Lines: 35 Message-ID: References: <1998072600112200 DOT UAA09619 AT ladder03 DOT news DOT aol DOT com> NNTP-Posting-Host: london.netkonect.net Mime-Version: 1.0 NNTP-Posting-Date: 26 Jul 1998 13:36:11 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk In article <1998072600112200 DOT UAA09619 AT ladder03 DOT news DOT aol DOT com>, OoHOSEoO writes >#define MAXPATH 512 >#define MAXDRIVE 3 >#define MAXDIR 250 >#define MAXFILE 250 >#define MAXEXT 9 Correct values for Win32 should be: #define MAXPATH 260 #define MAXDRIVE 3 #define MAXDIR 256 #define MAXFILE 256 #define MAXEXT 256 Personally I would bump the MAXPATH value up a bit for safety, because djgpp could conceivably not honour the Windoze 260 char limit in some circumstanes (but this is just speculation;) 256 is the absolute maximum length of each entry in a VFAT directory. If you plan on using URLs try MAXPATH=1024. In article <199807260114 DOT VAA20247 AT delorie DOT com>, DJ Delorie writes >JGPP is a DOS compiler. Those are the correct values for MS-DOS. If >you think they should be different, post a diff to >djgpp-workers AT delorie DOT com with your rationale. ...but those are wrong for LFN enabled Dos in a DOSbox, since djgpp supports LFNs it should use correct LFN values for safety. --- Paul Shirley: my email address is 'obvious'ly anti-spammed