🚀 go-pugleaf

Don Sterner wrote:
> 
> In article <HW$fNyAhCbrzEwcQ@swindon-fc.demon.co.uk>,
> Chris.King@swindon-fc.demon.co.uk.mars says...
> >
> >On Sun, 22 Jun 1997 at 23:34:16 in article <33AD0DB8.417DC62D@xtra.co.nz
> >>, Loren Brookes <wbrook@xtra.co.nz> writes
> >>I did areally stupid thing... I changed 'Program Files' to 'Progra~1'
> >>when trying find out why the DOS search program I was writing, would not
> >>recogonize the the directory. When I changed it back to 'Program files',
> >>the DOS name changed to 'Progra~2' :<
> >>
> >>How do I change it back again ???
> >
> >Rename progra~2 to something short like cheesey
> >
> >Rename cheesey to program files. Eg:
> >
> >ren progra~2 cheesey
> >ren cheesey "Program files"
> >--
> 
> OK, now what are you going to do with all the registry and parameter file
> entries, and the shortcut files that point to progra~2?
> 
> d.

Hopefully, as in my case, the effects of the original error are
immediately apparent and you fix it before you accumulate any spurious
"PROGRA~2" references. If not, then you've got a real mess (probably
requiring mass editing of the registry or restoration from a backup). In
my case, Norton Utilities was the only software (I think) that used the
"PROGRA~1" reference instead of the full long filename and the problem
was immediately apparent upon rebooting the machine (lots of "couldn't
find .dll ..." and "couldn't find file ..." errors).

However, this is kind of an insidious error that isn't immediately
apparent and can lead to a totally botched registry if not promptly
rectified.

Live long, and prosper
Jerry L. Gubka