From: mvrable AT aol DOT com (MVrable)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Rebuilding gcc - "c-parse.gperf" not found
Date: 1 Sep 1997 03:12:51 GMT
Lines: 46
Message-ID: <19970901031201.XAA01966@ladder02.news.aol.com>
NNTP-Posting-Host: ladder02.news.aol.com
References: <3409d234 DOT 8669182 AT snews DOT zippo DOT com>
Organization: AOL http://www.aol.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

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

> [snip]
> Hmm-m-m.  I wonder if it is possible to have a Win95 long-name file
> with a nice, normal 8.3 "real name".  E.G., if the long name is
> c-parse.gperf, the 8.3 name would still be "c-parse.gpe", not
> "c-pars~1.gpe",  but the long name would be "c-parse.gperf".  Probably
> not, but it's a nice thought.  Not likely that M$ made it that easy
> for DOS folk, is it?
> [snip]

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...)

--------------------
Michael Vrable
mvrable AT aol DOT com