Re: erase *.tmp also lists *.tmpl files - how to avoid
Jonathan de Boyne Pollard
erase *.tmpdeletes both files. How can I avoid this?
Use
a different command interpreter, turn off short filenames, or don't
use wildcards with the ERASE command.
Stefan Kanthak
[ gibberish HTML ]
Crossposts over DIFFERENT hierarchies are EVIL!
Stop posting HTML! Use properly formatted text/plain instead, as
recommended in <http://www.ietf.org/rfc/rfc1855.txt>!
And correct your Web page: the registry setting Win95TruncatedExtensions
(which causes the trouble here) was introduced with NT4!
Stefan
Jonathan de Boyne Pollard
Crossposts over DIFFERENT hierarchies are EVIL!
Codswallop. Cross-posting is a good thing, and there's nothing
inherently wrong about cross-posting to newsgroups in different
hierarchies. Indeed, the reasons for not cross-posting to,
say, every comp.os.msdos.* newsgroup are reasons for
cross-posting to newsgroups in different hierarchies where Win32
command interpreters and their search wildcards are discussed.
Stop posting HTML! Use properly formatted text/plain instead, as recommended in RFC 1855!
You clearly haven't read that RFC. Here's a hint, kiddo: The
reason that you won't find anything in the RFC supporting your daft
notion is that it's a daft notion, based upon folk wisdom that has
passed through a Chinese Whispers effect. The actual, true, division
in Usenet is between text and binaries, wherein
hypertext falls very much on the text side. It is binaries
that one shouldn't post to text newsgroups, not hypertext.
Binaries are MIME body part types like audio/*, video/*,
and image/*. The text/* body part types
are, as the designation states, text.
And correct your Web page: the registry setting Win95TruncatedExtensions (which causes the trouble here) was introduced with NT4
Clearly, since you obviously read it to follow the hyperlink in it,
that message wasn't the "gibberish" that you are trying to pretend it
to have been. It's always amusing when the people post responses such
as thise where they undermine themselves in their very posts. The
all-time favourite is foolishly posting "Usenet is ASCII." (It isn't,
of course, and this is a 25-year-old FAQ
answer.) in a non-ASCII character set, with gobsmackingly
clue-deficient "Usenet is
American." silliness coming a close second, but you're doing fairly
well with this runner up.
Microsoft, on the page hyperlinked to, says Windows NT version 5.2
and later, by the way. You should take this up with Microsoft.
Stefan Kanthak
Your attribution line is missing!
> Crossposts over DIFFERENT hierarchies are EVIL!
>
> Codswallop. Cross-posting is a good thing, and there's nothing inherently wrong about cross-posting to newsgroups in different
hierarchies. Indeed, the reasons for not cross-posting to, say, every comp.os.msdos.* newsgroup are reasons for cross-posting to
newsgroups in different hierarchies where Win32 command interpreters and their search wildcards are discussed.
Your line length sucks!
Crossposting over DIFFERENT hierarchies is EVIL!
microsoft.* originates ONLY on msnews.microsoft.com, which but does not
carry alt.* and comp.*.
>
>
> Stop posting HTML! Use properly formatted text/plain instead, as recommended in RFC 1855!
>
> You clearly haven't read that RFC.
Oh yes, especially the parts that read:
| - Make things easy for the recipient.
| - Limit line length to fewer than 65 characters and end a line
| with a carriage return.
> Here's a hint, kiddo: The reason that you won't find anything in the RFC supporting your daft notion is that it's a daft notion,
based upon folk wisdom that has passed through a Chinese Whispers effect. The actual, true, division in Usenet is between text and
binaries, wherein hypertext falls very much on the text side. It is binaries that one shouldn't post to text newsgroups, not
hypertext. Binaries are MIME body part types like audio/*, video/*, and image/*. The text/* body part types are, as the
designation states, text.
Your line length still sucks!
> And correct your Web page: the registry setting Win95TruncatedExtensions (which causes the trouble here) was introduced with NT4
[ even more gibberish ]
>
> Microsoft, on the page hyperlinked to, says Windows NT version 5.2 and later, by the way. You should take this up with Microsoft.
And you can't even read Microsoft web docs right.
Get a copy of the NT4 resource kit docs.
PLONK
Stefan
Al Dunbar
one of the guidelines it proposes for NetNews use is:
- Don't get involved in flame wars. Neither post nor respond
to incendiary material.
/Al
"Stefan Kanthak"
<dont.delete-this.don...@expires-2010-03-31.arcornews.de>
wrote in message
news:4b9ec619$0$6732$9b4e...@newsspool2.arcor-online.net...
Tim Meddick
Don't let the [control freaks] drag you down!
==
Cheers, Tim Meddick, Peckham, London. :-)
"Jonathan de Boyne Pollard" <J.deBoynePoll...@NTLWorld.COM> wrote in
message news:IU.D20100315.T...@J.de.Boyne.Pollard.localhost...
>
>
> < clipped >
> ...................It is binaries that one shouldn't post to text newsgroups, not
> hypertext.........
> < clipped >
>
>
Konrad Kullig
"Win95TruncatedExtensions"=dword:00000000
Note: This works for all file copies created after this change in the registry.
"Jonathan de Boyne Pollard" <J.deBoynePoll...@NTLWorld.COM> schrieb im Newsbeitrag news:IU.D20100315.T...@J.de.Boyne.Pollard.localhost...
orpy
Konrad Kullig wrote:
> "Jonathan de Boyne Pollard"
> <J.deBoynePoll...@NTLWorld.COM> schrieb im Newsbeitrag
> news:IU.D20100315.T...@J.de.Boyne.Pollard.localhost...
> erase *.tmp
> deletes both files. How can I avoid this?
> Use a different command interpreter, turn off short filenames, or
> don't use wildcards with the ERASE command.
cutting off the third answer, that no way solves the problem in the object,
i have interest in the other solutions:
what does "different command interpreter" mean? I don't know, can you tell
me something about?
Anyway, does turning off short filenames really work for this problem?
Steve Fabian
| cutting off the third answer, that no way solves the problem in the
| object, i have interest in the other solutions:
|
| what does "different command interpreter" mean? I don't know, can
| you tell me something about?
Microsoft's and IBM's command.com (as well as its clones in DR-DOS, FreeDOS,
etc.), MS' CMD.EXE for Windows NT+ and IBM's CMD.EXE for OS/2 are command
interpreters (or using better terminology command processors). So is every
"shell" of the *nix world. JP Software's 4DOS.COM (a version distributed as
NDOS.COM with Norton Utilities), 4nt.exe and tcc.exe are substantially more
sophisticated command processors for the PC/MS-DOS and MS Windows platforms,
which have an internal option to turn off processing short filenames.
| Anyway, does turning off short filenames really work for this
| problem?
Yes. That option prevents a file which has both an LFN and an SFN from being
processed based on its SFN. In JPsoft's command processors there are
functions to convert between the LFN and SFN. Note that two files with the
same long file name and extension, but in different directories, may have
different SFNs in those directories. JPsoft's command processors for
PC/MS-DOS (4dos.com) and OS/2 (4os2.com) are now unmaintained freeware.
Fully maintained free JPsoft command processors are also available for the
WinXP and later MS platforms ("limited edition" versions) which support
searching for LFNs only.
--
HTH, Steve
--- news://freenews.netfront.net/ - complaints: ne...@netfront.net ---
Jonathan de Boyne Pollard
erase *.tmpdeletes both files. How can I avoid this?
Use a different command interpreter, turn off short filenames, or don't use wildcards with the
ERASEcommand.cutting off the third answer, that no way solves the problem in the object, i have interest in the other solutions:
what does "different command interpreter" mean? I don't know, can you tell me something about?
Indeed, and I already have. If you re-read the message that you
indirectly replied to, you'll find that it contains a hyperlink to a
WWW page that names one of the alternative command interpreters that
one can use, and that in its turn hyperlinks to that command
interpreter's documentation where you can find out even more. I've
restored the hyperlink in the quotation in this message.
Anyway, does turning off short filenames really work for this problem?
Yes. Here is the problem not occurring on an NTFS volume on a Windows NT system with short filenames disabled:
[c:\test]rem > test.tmp1[c:\test]dir /x/m/k10-03-18 4:46 <DIR> . 10-03-18 4:46 <DIR> .. 10-03-18 4:46 0 test.tmp1 [c:\test]cmd /c erase *.tmp Could Not Find C:\test\*.tmp [c:\test]erase *.tmp 4NT: The system cannot find the file specified. "C:\test\*.tmp" 0 files deleted [c:\test]
Notice the lack of a short filename for the search wildcard to
match. I've run both command interpreters, to show that this is not a
command interpreter artefact. Moreover, 4NT here is a significantly
out-of-date version, that pre-dates the feature that turned off SFN
searching (which was introduced quite a few years ago). As mentioned
on the WWW page, the current versions, that have that
feature, will ignore search wildcard matches for short filenames even
for files created with short filenames, such as files on FAT
volumes and files created on NTFS volumes before one turned off short
filename creation.
Tim Meddick
What you are doing is turning off the [Win95] effect of not recognising filename
extensions greater than three characters - i.e. "Truncated Extensions"
Thus, even though Win95 had Long File Names (the first Win ver to do so) it did not
recognise, for example, the difference between *.tmp and *.tmpl files.
So turning OFF the registry setting (i.e. setting it to zero)
"Win95TruncatedExtensions" you thereby enable WinXP to always recognise the
difference between a three and a four-letter filename extension!
If the setting is ON (i.e. set to 1) then WinXP will treat *.tmp and *.tmpl files as
if they were the same. Therefore, make sure it is set to zero :
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"Win95TruncatedExtensions"=dword:00000000
==
Cheers, Tim Meddick, Peckham, London. :-)
"orpy" <or...@urcaurca.tirulero> wrote in message
news:4ba15b2e$0$821$4faf...@reader5.news.tin.it...
Jonathan de Boyne Pollard
>
> You are not turning off short filenames to cure the problem.
>
> What you are doing is turning off the [Win95] effect of not
> recognising filename extensions greater than three characters - i.e.
> "Truncated Extensions"
>
> cutting off the third answer, that no way solves the problem in the
> object, i have interest in the other solutions:
>
Xe wasn't asking about what M. Kullig suggested, but about turning off
short filenames.