#214 7-zip Self-Extracting Install Issue

[Anonymous]

Ran into this very frustrating bug just now. I always
have my computer as tidy as possible, so naturally I
keep all of my programs on a seperate partition. I went a
step further than some and changed the %
ProgramFiles% variable to point to "D:" (no quotes). It
seems the installer has a problem with this, because
there is no back-slash at the end of the drive letter. I
understand how a back-slash would be expected, but
until now I have never ran into any problems with not
having it, and after doing some looking I came to the
conclusion that no back-slash is better.

The install went without a hitch after adding a backslash
to the path.

I know this is very minor but it was also very frustrating
trying to find the problem.

Email: jager336 AT fastmail DOT fm

[Nobody/Anonymous]

Logged In: NO

Oh yeah, I knew there was something I left out.

Running Windows XP Proffessional w/ SP1a

[Nobody/Anonymous]

Logged In: NO

In DOS semantics, a drive letter path without a backslash
after the colon uses the present working directory of that
drive as a reference point. Each DOS drive letter has its
own working directory. Omitting the backslash in an
environment variable would seem to lead to unpredictable
results, depending on the application's pwd for that drive.
Therefore, it's best to use a trailing backslash when you
mean the root directory.

[Nobody/Anonymous]

Logged In: NO

Ah, OK. I'll admit I found it a bit odd after reading that it
appeared better to be without a backslash for the root of a
drive, but as I said I have had no problems until this install so
I assumed it was an issue with the installer as opposed to the
data in the value.

That and I ran into a program that automatically added a
backslash to it's install path (thus leading to two backslashes
for my configuration had I put one in the first place), which
helped contribute to my reasoning.

Nonetheless I just had to reinstall after becoming infected
with something, and I'm using a backslash now to see how
that works out.

Thank you for the information :-)

PS: About the infection, it seems there is a new
virus/worm/trojan on the loose, that has no information as of
yet and is not detected by any of the several scanners I
used, so you may want to be careful (though it could have
just had it's entry point changed) Still, better safe than sorry.