Page 1 of 1

Run-time error about $PROGRAMFILES$

Posted: Thu Jan 17, 2008 4:38 pm
by Underdog
In my last post, I had trouble compiling the package. The solution given to me worked. But now I have this problem. First of all, let me say that when I compile I have the install files put out on the network where another test computer can see them. This is the error when trying to install on that other computer:

---------------------------
Orem Application Toolbar
---------------------------
Error

Could not access network location $PROGRAMFILES$\\OremCity.
---------------------------
Retry Cancel
---------------------------

I have verified that this other computer has the PROGRAMFILES environment variable defined, but it's certainly not a network location. And it appears that all of my uncompressed files are in weird-named folders (a handful of hex numbers per folder name).

How can I resolve this?

Posted: Fri Jan 18, 2008 3:03 pm
by Alex_Ronquillo
Sorry,

Can you extend a little your scenario explanation. Please provide drive descriptions, files location, etc.

Further Explanation

Posted: Fri Jan 25, 2008 5:09 pm
by Underdog
I put the file out on U:\\TestInstalls

U: translates to \\\\Orem3\\Sys\\Users\\AS4RWD

I run the file on the other computer from E:\\Users\\AS4RWD\\TestInstalls

E: translates to \\\\Orem3\\Sys


But drive letters shouldn't matter, should they? After all, this is an uncompressed install package where I would think the installer uses relative paths. After all, all the files are in subfolders of the setup executable.

File Attached:

<a>VistaOATInstallError.bmp

File Attached:

VistaOATInstallError.bmp

Posted: Mon Jan 28, 2008 4:47 pm
by Alex_Ronquillo
Make sure the following line is presnet in your script:

Code: Select all

Get Folder Location System->Program Files Directory into PROGRAMFILES

Solution - Rebuild

Posted: Mon Feb 04, 2008 11:41 am
by Underdog
Frustrated with my install project, I simply started from scratch and the new install works. Since I have the free version, I don't have access to the script.