Hi Celine

Sounds simple enough. You must have installed H2Reg on
your system so please look at that as an example

h2Reg.exe is in
C:\Program Files\Helpware\H2Reg\
while I install H2Reg_cmd.ini with my source files here
C:\Program Files\Helpware\H2Reg\h2help\

So I run in INNO installer I run
"{app}\H2Reg.exe" with param "-r cmdfile={app}\h2help\H2Reg_Cmd.ini"

Alternatively all paths in your cmd file are relative to the cmd file location.

in my cmd file I have

[Reg_Namespace]
;<nsName>|<nsColfile>|<nsDesc>
hw.h2reg|COL_Master.HxC|H2Reg.exe Documentation

If I kept my cmd INI in the same folder as H2Reg.exe then I would
have to adjust
all paths in the cmd file

eg.

[Reg_Namespace]
;<nsName>|<nsColfile>|<nsDesc>
h2help\ hw.h2reg|COL_Master.HxC|H2Reg.exe Documentation

Does that help?

The <UserDir1> type placeholders is just a way you can pass in a path
for the cmd file to use.

H2Reg.exe -r "UserDir1=d:\path1"

[Reg_Namespace]
;<nsName>|<nsColfile>|<nsDesc>
<UserDir1>\ hw.h2reg|COL_Master.HxC|H2Reg.exe Documentation

You can also do things like

[Reg_Namespace]
;<nsName>|<nsColfile>|<nsDesc>
<programfilesdir>\helpware\ hw.h2reg|COL_Master.HxC|H2Reg.exe Documentation

Rob


At 03:43 AM 8/05/2009, you wrote:


>Hello
>
>I'm trying to register files located in folders other than where the
>executable and ini are located. The problem is that the collection
>files and the HxS files are located in different directories. I read
>the documentation on the UsSerDir user-defined directory script
>shortcuts do not fully understand how to use them and whether they
>apply in what I need to do. I'm ok with placing the H2Reg files
>elsewhere that these could perform the registration. I thought that
>it might be easier to reach paths defined from a higher level rather
>than moving up in the structure. The structure of what I need to
>register is as follows:
>
>H2RegFolder
>HxSFilesFolder
>Folder
>CollectionFilesFolder
>
>Regards
>
>Celine
>
>


[Non-text portions of this message have been removed]