[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Ms-Dos FST
- Subject: Re: Ms-Dos FST
- From: "Paul Grammens" <grammens@svn.net>
- Date: Mon, 1 Apr 2002 10:39:32 -0800
- Newsgroups: comp.sys.apple2
- Organization: Silicon Valley North, Inc. (http://www.svn.net)
- References: <Py_n8.156$2w7.61881506@newssvr12.news.prodigy.com> <3ca65ff1.12697969@news1.sympatico.ca> <AJOp8.38$s_3.275082@news.ntplx.net> <RfZp8.8270$hi7.31391@news-server.bigpond.net.au>
- Xref: archiver1.google.com comp.sys.apple2:18566
Thanks for the explanation, Peter.
-Paul
"Peter Watson" <paw77@NOhotmailSPAM.com> wrote
>
> The problem is that the "long filenames" introduced in Windows 95 and/or
> Windows NT 4 are stored in directory entries with a combination of "type"
> bits that include the "volume label" bit. So older programs like the
MS-DOS
> FST see a long filename and try to process it as a volume label. If you're
> lucky, you'll just see junk in the directory display. If you're unlucky,
> it's nothing that a reboot won't fix! :-)
>
> The workaround is to always give a MS-DOS disk a volume name when you
format
> it. (It's probably not a bad idea in any case!) This means that the volume
> name is always found before any "long filename" directory entries.
>
> Of course, this still doesn't allow you to *see* the long filenames, and
it
> doesn't solve the problem of handling disks with partition maps (like Zip
> disks). And it certainly doesn't allow you to write to the disks! For all
> that you need MUG!, or the original MS-DOS Utilities. ;-)
>