From: mharris AT blackwidow DOT saultc DOT on DOT ca Date: Sat, 15 Feb 1997 00:31:54 -0500 (EST) Reply-To: mharris AT blackwidow DOT saultc DOT on DOT ca To: "Colin W. Glenn" cc: "'OpenDOS newsgroup'" Subject: Re: [opendos] BAD Filesystems 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, 14 Feb 1997, Colin W. Glenn wrote: > > On Thu, 13 Feb 1997, Colin W. Glenn wrote: > > CTRL-J in PINE. > > Or add a verification: ARE YOU SURE! [Y/N] And then after you type 'YES' out in full and hit enter, it asks you to type in the volume label from C: in DOS for confirmation. > > > We could call them something else, call them DLD, Dynamicly Loaded Driver. > > > > How about the extension ".Dynamically_Loaded_Driver_Module". > > This would put an end to 8.3 forever! You could have for > > example: > > > > IFSLOAD > > C:\DOS\Installable_Filesystems > \Extended_Filesystem_Number_2.Dynamically_Loaded_Driver_Module > > MOUNT C: HDA3: /T=ext2 > > > > Sorry, that one didn't quite fit on the screen. > (you're excused) > > This _jams_!!, by utilizing the algorithm I proposed of using the first > four characters of the first word in the filename, and secondary letters > as needed to complete the filename, then using either the first three > letters or the first letter of the first three words as the extension: > > Extended_Filesystem_Number_2.Dynamically_Loaded_Driver_Module > > becomes EXTEFN~2.DLD to a dos 8.3 program! What if I allready have a file called EXTEFN~2.DLD in that directory? I mean the chances are very small, however I could simply create one just to prove my point. Then the algorithm would break. A better method is the mangled name method that DOSemu uses in LREDIR. > > Sorry, that one didn't quite fit on the screen. > > Which does bring up an interesting rule for EFN's, keep them short enough > to fit on the screen! ;) > > Hey! another maybe wish for OpenDOS, instead of regular line-wrapping, > smart breaking at either '/' or '\'. Too much? \ would be interpreted as a directory path, so if you said: COPY FILE1.txt \ It would go to the next line and wait for you to type in more instead of copying the file to the root dir. / would be interpreted as a switch character, so if you said: COPY FILE.TXT .. / It would complain that an invalid switch was present. I believe that COMMAND.COM / 4DOS allready allow you to do what you are suggesting by pressing a control character at the end of a line. In plain ole COMMAND.COM without DOSKEY, I think that it is the ESC character although it has been 5 or 6 years since I remember. 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 EMACS: Escape Meta Alt Control Shift :o)