Srowi

Big THX! works now. Don't know where i saw it that way, but it always worked fine (even in RunOnceEx.cmd) except for the AutoIt-Script.

hi, you can also just creae a acdsee.mst file if you want. Works fine here!

hi, i'm trying to automate the installation of some prog with AutoIt. But i always get some error (i guess with the syntax): Run ("progA.msi") works fine, but while the follwing works fine on command line, it breaks the script: Run ("progA.msi TRANSFORMS=progA.mst /qr") doesn't work. Already tried quoting the mst, but didn't work. (all files in the same directory) I already search for examples, but couldn't find anyting... thx!

hi again, thx for that link, but i know how msi's are installed. Looked like the trouble was a dirty uninstall of acdsee, so that the msi was generated different (so that it worked only on the actual but not on the clean winxp).

hi again, thx for the tip, found out, that only uninstalling the existing copy (what the Installtailor forces to do) isn't enough. So i created the mst within the vmware-environment where it didn't work before and voila.. now it works fine.

yeah, sry for the typo, i got the right extension, but that has nothing to do with the error i get. The weird thing is, after installing and deinstalling ACDSee manually, the command from the first post works flawless.

hi everybody, after being a long time read-only user, i now have a problem which i can't fix. I have created a ACDSee.mft with "WISE InstallTailor", which works fine when i run it on my workstation. But when i run it in VMWare from the file RunOnce.cmd like this: ACDSeePowerPack.msi TRANSFORMS=ACDSeePowerpack.mft /qn" the installer always complains about the mft not being in the right place or being corrupt. When WinXP is installed, an i try to run it from the console, it gives me the same error. But if i run it without the mft, deinstall it, then it works fine unattended...? What could be he problem here? I'm a little lost with this..