Software Deployment

i've seen problems with poorly formatted INIs but not with Wise ignoring them altogether. Make sure it's not in your "exclusion list." Another alternative I"ve done is to get a clean machine with a "known good" INI and import it into Wise.

Is this an Intuit product by chance?

Yes it is Intuit Product, TurboTax to be precise.

It is very weird because during the capturing process, i can see all ini files, but when the msi is completed they are all gone. I've tried to import the original ini files from that initial capture process but then when running the application it will tell me that prd.ini was modified and ask me to reinstall the application.

double check your inifile table and make sure there are no errors in it.

look at the file after it's installed and see if it looks right.

Also, as I mentioned before, if it's not a good INI file Windows installer can have problems with it.

I had the same problem with TurboTax - please post the contents of your perwin.ini file from the program directory, but DON'T post the serial number info :). More than likely, the problem lies with this file. Upon installation, there are three ini files that are digitally signed. If any of these are changed in any way (or not captured correctly), you will get the error you mentioned. This caused me weeks of frustration so I feel your pain. Intuit of course recommends reinstalling :P They don't understand what it means to package software...

Thanks for sharing. I always try to press for an MSI version. That way it's easy to transform and if it messes up it's a vendor issue (LOL!)
If it's a strange INI file shouldn't you be able to install it as a regular file?

Skaye,

The problem is that when i capture TurboTax i will have no ini files so nothing to modify. Were you able to capture the application with ini files? What did you do. How did you fix your msi?

Thanks,

Hi Sebastian,
have you tried to start the program once, right after installation, but before the final capturing?
Which installer tool is used for the original installer?
Maybe, with a little reengineering, you are able to build CA, which creates this INI-files.
Regards, Nick

Hey there,

You can also find out if the ini file is somewhat " problematic" by simple importing it into the INI file table, compiling and ICE checking, you will usualy get Errors or warnings Back from the INI file table.

This way i select if the INI file should be in the INI file table or just in the File Table as normal File.

and what does the Program Check on this INI file? the Date? or do you have it installed on admin ( full rights ) and tested under user ( limited rights ).

From my experience " file is altered" errors are usualy the wierd form of telling " i cant edit this file " but thats just hands-on Experience.

Regards,

NOxxie

Hi All,
Please let me know why any ini file is included in the file table not in inifile table during capturing of a legacy application?
Also why it should not be included in file table?
Look forward to hear from you all soon.


[font="book antiqua"]
Regards,
Sumi

Captured with what? IS, WPS? AppDeploy Repackager?

If you don't need to change anything in the INI during the install, i.e. if you don't need to use property values to populate any entries in the INI, I'd copy it as a file.

Hi Vbscab,
Thanks for your reply.
I am taking the capture of exe with WPS.
Could you please tell me why it's get captured in file table not in IniFile table?


Regards,
Sumi

The only reasons I can think of is that a) it's not in proper INI format or b) you selected 'Treat as File' during the SetupCapture phase.

hope this will help to aswser to question http://www.symantec.com/connect/articles/best-practices-ini-files

Careful: that article is by a normal forum poster and should act merely as a guide, rather than anything having been written in stone.