[Sunday, March 13, 2005 1:20 AM]

Once again, there's a fair chance I have no clue whatsoever about how SB5
expects me to handle some things. That said, I don't see a clear way around
an interaction between SB ROOT and the CSIDL * directories and setting up
variable based folders in the GUI.

I have some stuff that must live in CSIDL APPDATA\[PRODUCTNAME]. In File and Folders I add a folder named %USER APP DATA FOLDER% under Always Install and set that variable early in the script to CSIDL APPDATA\[PRODUCTNAME]. Simple enough.

SB wants to create SB ROOT\USER APP DATA FOLDER, but fails because
CSIDL APPDATA contains a fully qualified path (as it should). The result is
SB trying to create c:\c:\...

Three string functions later I have a proper path created, but realize that I
am not aware that the drive to which CSIDL APPDATA and SB ROOT each refer are guaranteed to match. I'm guessing that SB ROOT contains either the drive on which the OS resides, or more likely the drive for SB INSTALLDIR. In either case mixing SB ROOT and CSIDL * paths seems problematic.

In another case I have got to be doing it wrong, as this is too simple. I
have another case of a variable based folder, but this one is user selected.
It can exist on the local machine, or any device accessible to the user via
an UNC. Again, I add the folder variable to Always Install and SB creates:

:: Create Folder % SB ROOT\%USER SELECTED PATH%

So what expectations has SB5 of these paths I need to feed it? I haven't
tested the UNC case, but as best I can tell with everything else Create
Folder and Install File used via the GUI are going to blindly prepend
SB ROOT to whatever they're fed.

--
Best regards,

Mark