www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/09/01/16:16:33

From: pjfarley AT dorsai DOT org (Peter J. Farley III)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Rebuilding gcc - "c-parse.gperf" not found
Date: Mon, 01 Sep 1997 04:04:08 GMT
Organization: None
Lines: 74
Message-ID: <340a3b80.10574464@snews.zippo.com>
References: <3409d234 DOT 8669182 AT snews DOT zippo DOT com> <19970901031201 DOT XAA01966 AT ladder02 DOT news DOT aol DOT com>
NNTP-Posting-Host: news.newsdawg.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Wow!  Now *that* is nice news to hear!  Many thanks, friend.

Let me repeat your statements, so I see if I understand them
correctly.  Placing this entry in the registry under Win95 will
disable the creation of *initial* numeric suffixes (as with the
creation of a "longname" file that is the first of it's 8.3 flavor),
and files subsequent to the first of a given 8.3 name *will* result in
creation of 8.3 names with numeric suffixes (like ~1, ~2, etc.).

So if I do this:

C:\echo textstuff > win95longfile.nameandstuff

it would create (I'm guessing here) a file name set like this:

WIN95LON.NAM  ===========>>  win95longfile.nameandstuff

And then I do this:

C:\echo moretextstuff > win95longfile.namesandall

it would create a file name set like this:

WIN95L~1.NAM  ===========>>  win95longfile.namesandall

And if I do it again, with:

C:\echo yetmoretext > win95longfile.namesforsale

I'll get this:

WIN95L~2.NAM  ===========>>  win95longfile.namesforsale

Please confirm, if you have the time.  And again, many thanks!

Peter

mvrable AT aol DOT com (MVrable) wrote:
<Snipped>
>Yes, in fact there is a way to do this.  To do this, you will need to
>create the small file below (the exact name doesn't matter) and give
>it an extension of .REG.  Then, right-click the file in explorer and
>select "Merge" from the context menu.  After this has been done, the
>file itself should no longer be necessary and can be deleted.  (If you
>prefer, you could go in and edit the registry directly, but the method
>detailed above is probably easier.  Don't say I didn't warn you.)
>
>-----BEGIN REALNAME.REG-----
>REGEDIT4
>
>[HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\FileSystem]
>"NameNumericTail"=hex:00
>-----END REALNAME.REG-----
>
>What this will do is add a single entry into the system registry that
>tells Windows 95 not to append the "~1" endings onto the short 8.3
>filenames.  If several files would have the same short filenames,
>however, Windows will have to add "~1", "~2", etc. to come up with a
>unique filename.
>
>Unfortunately, this only affect files that are created after this is
>put into affect, and not before; you might have to un-zip all the
>original files again to re-create the files with new "real" short file
>names.
>
>(Just another side note: I believe that the installation instructions
>for Emacs mention this fix and say that it is necessary if you are
>planning to run Emacs under both short- and long- filename
>environments.  Can't confirm this at the moment though, as I can't
>seem to find the installation instructions for Emacs...)


----------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org)

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019