From: mharris AT blackwidow DOT saultc DOT on DOT ca Date: Tue, 11 Feb 1997 08:53:04 -0500 (EST) Reply-To: mharris AT blackwidow DOT saultc DOT on DOT ca To: Jonathan Tarbox - SSG cc: "'opendos AT mail DOT tacoma DOT net'" Subject: Re: [opendos] Filesystems/Long Filename API In-Reply-To: Message-ID: Organization: Total disorganization. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-opendos AT mail DOT tacoma DOT net Precedence: bulk On Fri, 7 Feb 1997, Jonathan Tarbox - SSG wrote: > > Now, we are all decided that we want *SUPPORT* for other FS's.. That > is it comes default using FAT because the average user will not > need/want anything other.. Possibly supporting VFAT by default might be > an option also since alot of us, myself including have Win95 also > install on my system. > > But we are also discussing the method in which to support the LFN's for > 'legacy' apps in 8.3 format. Now instead of using several patches to > this and that, why not keep the Win95 LFN API and add our own support in > it to handle the other FS's. Because the W95 method is a hack, is written by M$ and I *DONT* use W95 and don't want to inherit another M$ hack. I want to see a new API that FIXES this DOS/Win braindamaged method for once and for all. Also, the W95 8.3 name mangler doesn't do a very good job at it since if you move a file between 2 directories, it is possible for the 8.3 name to change in the process. The 8.3 names should be UNIQUE for every file. > The thing is, true we all hate the way Win95 hashes the Long Filename > down to 8.3 standard, but if we then change this method for OD will not > Win95 not comprehend it when we go back into Windows? What's so hard to > have our DIR and other basic DOS internal commands to list both the LFN > and hashed 8.3 name.. We can make our GOOD NEW API's 8.3 hashed names available to W95 via the W95 LFN API, or we could put the ACTUAL long filenames into the W95 LFN API. Personally, I think that OpenDOS should REMAIN just THAT, DOS! Let W95 features be added as hack patches for those that want them, and let OpenDOS progress on its own into a more powerful OS without adding more and more hacks and kludges. > Also, the 4DOS file descriptions would be an awesome addition to the > basic OD install... This is a *GREAT* FANTASTIC idea! I recommended this to Bob Stout (the guy who puts together the SNIPPETS C package) and he added support for 4DOS descriptions right away. I noticed that some other commercial software includes 4DOS descriptions as well. I'm willing to create such a file if no one else is. I might need a hand determining what some of the files are though. > BTW - These are opinions.. I'm looking for compatibility between all of > my OS that I use (I'm a Tech Support Specialist, I support em all > basically: DOS, All Windows, OS/2, Mac, Linux.. Well, when DOS gets the IFS, you'll certainly get compatibility! And if they do it right it wont be a hack either! > I love System Commander(TM) for multi-booting..) So far, so do I. Maybe Caldera could buy SC too! Also they could buy 4DOS and release the sources. :o) Mike A. Harris | http://blackwidow.saultc.on.ca/~mharris Computer Consultant | My webpage has moved and my address has changed. My dynamic address: http://blackwidow.saultc.on.ca/~mharris/ip-address.html mailto:mharris AT blackwidow DOT saultc DOT on DOT ca Want the DR-DOS source code? Visit Caldera's website: www.caldera.com