Hello Matt
Can you please send us your AXT file so that we can look into the 1st issue where P in "Program Files" ends up as "rogram files"?
I haven't heard about this kind of problem before.
Another thing you can try to investigate further into this problem is by looking into the Inc file that gets created during the conversion. Check if the Inc file has "Program Files" or "rogram Files"
Now to the second issue, axt file is made up of different sections. For example
[File Copy]
Flag=Update Create
Source=%SOURCE_PATH%\\1.fil
Target=%TARGET_PATH%\Apps\ACH\BANKER.ICO
Or in some cases it can be
[File Copy]
Flag=Update Create
Source=%SOURCE_PATH%\\1.fil
Target=F:\Apps\ACH\BANKER.ICO
Now what happens during conversion process is that we create a property in the Property table, for example we will create a property in Property table DIRPROPERTY1=F:\ instead of hard coding the path. Similarly if TARGET_PATH is referred to C: we will create a property DIRPROPERTY1=C:\
So that when you run the installation your files go DIRPROPERTY1\Apps\ACH\Banker.ico
Now when you will launch the msi package, msi engine will try to resolve these properties and if the value of these properties is not resolved right you will get the error you are getting today. For example if F:\ on your machine do not exist you will get the error and installation will fail.
There are couples of way to fix this problem. First thing you can do is when the conversion is done go to the Direct Editor in developer then go to Property table and change the value of these properties to whatever you want. For example if you don't have F:\ on your machine you can change it to C:\ or D:\.
Second thing you can do is by running the package from command line and specifying new values to these properties from command line.
msiexe /i C:\test.msi DIRPROPERTY1=C:\
Thanks
Amber
