To: opendos AT delorie DOT com X-Comment-To: Travis Siegel Cc: fd-dev AT topica DOT com References: Message-Id: <2.07b7.GDDU.GE774O@belous.munic.msk.su> From: "Arkady V.Belousov" Date: Thu, 31 May 2001 15:41:12 +0400 (MSD) Organization: Locus X-Mailer: dMail [Demos Mail for DOS v2.07b7] Subject: Re: Proposal for new partition type IDs for use with future DOSes Lines: 31 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r X-MIME-Autoconverted: from 8bit to quoted-printable by postbox.mos.ru id f4VC16825068 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id IAA13103 Reply-To: opendos AT delorie DOT com X-Comment-To: Travis Siegel Салям! 31-Май-2001 03:11 tsiegel AT softcon DOT com (Travis Siegel) wrote to opendos AT delorie DOT com: TS> I don't have a problem with any of this proposal or the info contained in TS> it. In fact, I think it would be a very good idea to create some sort of TS> standard and get to it before microsoft does so that it won't foul it up TS> afterwords. If M$ decises to "standardize" something, even if this already standardized by others, no one prevents them from this. :( TS> However, in the long filename section you suggest using TS> something similar to 4dos descript.ion files. Woouldn't something TS> resembling how unix handles long file names be more appropriate here? I Unix based not at FAT file system. TS> mean it's been around for years already, everyone knows it works, and TS> there'd be plenty of support for it already. Other than that, I TS> wholeheartedly applaud your initiave (except I'd really like to see TS> anything with an ascii value less than 33 be illegal in filenames) I think, space in filename is not very bad thing - but OS should allow to use quotes to shield from its splitting function. TS> However, I don't think I'll garner much support on this front, so treat it TS> as only a personal wishlist item. :)