[<<]Message[>>]    [<<]Author[>>]    [<<]Subject[>>]    [<<]Thread[>>]

Number   :  4770
Date     :  2003-06-08
Author   :  Garry Deane
Subject  :  Re: Installing Xxcopy
Size(KB) :  2


--- In xxcopy@yahoogroups.com, "ray_mccormick" 
> Hi
> 
> Many thanks for the rapid reply, though I don't quite 
> follow your reasoning when you appear to claim "if I 
> say it won't work, it won't" 
> 
> My posting contained the statements:
> "In the case of xxcopy, installation is then as simple as 
> double-clicking on the 'install.bat' file (in the Windows 
> Explorer folder still open). 
> 
> "I have not had any problems with this and have just 
> installed 2.84.4 by this process.."
> 
> I should be more explicit and say that I have *always* 
> installed Xxcopy in this way without problem.
> 
> Surely, if 'install.bat' is run in this way it will first 
> look in the same folder for the referenced 'xxcopy.exe' 
> before looking in (other) folders on the path. This is 
> quite different from invoking 'install.bat' or 
> 'xxcopy.exe /install' in a (so-called) dos box. 
> 
> Just in case it makes any difference, I am using W2kSP3, 
> though I have used this procedure with WinME; 
> downloads are to a new sub-folder of 
> F:\Internet\InternetDownloads\Programs&Updates\

Ray,

you're right that the default behaviour when double clicking on a 
batch file in explorer will be to make that directory current and the 
install will proceed correctly. In that regard there's no problem 
with simply clicking on install.bat.

However this default behaviour can and does change depending on the 
user's setup. I'm not sure of all the ins and outs but I am aware 
that you can't always rely on the current directory being the same as 
that of the executing batch file. One such case is when the batch 
file is executed via a UNC path. Another is if the user has AutoRun 
commands (W2k/XP) which execute whenever Cmd starts. I'm sure there 
are others. There have been situations in the past where new users 
have said things like "I clicked on install and nothing happened. A 
black screen flashed by briefly but it was too fast for me to see 
what it said." This sort of thing is symptomatic of the current 
directory not being the same as the install directory.

The usual reply to the above scenario is: open a cmd/command window; 
change directory to the directory where install is located, type 
install then things should proceed normally. The previous install.bat 
made this CD to the same directory as install.bat necessary.

Maybe I should leave it to Kan to reply but it would be my guess that 
when he replied to you, he was probably thinking more in terms of 
running install.bat from a Cmd/Command window and forgot that 
explorer's default double click behaviour will usually work OK.

Garry



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.