Silent install of Kidspiration for WinXP

[bmonrad]

Hi,

 

Does anyone have any tips or tricks for a silent/unattended installation of Kidspiration 3, short of repackaging manually?

 

I'm building a new reference image in ConfigMgr/MDT, and hope to let it all be automated.

 

Thanks.

 

-ben

[contink]

I think I have this to handle myself... I'll check when I get back into that school and let you know if I'm right and what tips, if any I can offer.... Would appreciate anything you develop too naturally

[TimJing]

I wish there was a way. We use Wise Packaging Studio to package products that do not allow any sort of automation.

[SYNACK]

I repackaged the earlier version with Winstall LE and packaged up the Text to speech components seporatly. Worked really well in my case, version 3 could very well be different though.

[TimJing]

I repackaged the earlier version with Winstall LE and packaged up the Text to speech components seporatly. Worked really well in my case, version 3 could very well be different though.

 

 

It's almost the same except the new Text to Speech is now an MSI.

[McCoy824]

I have Wise Packaging Studio and was given the task to create a package for this software. When i finish creating the msi file and try to test it I keep getting an error saying that it is failing while trying to access a .dll file. Any ideas?

[TimJing]

I have Wise Packaging Studio and was given the task to create a package for this software. When i finish creating the msi file and try to test it I keep getting an error saying that it is failing while trying to access a .dll file. Any ideas?

 

In the installer folder, goto the Installer Support folder and run the ittsxp.msi before you start the application capture(MS text to speech). And then deploy that MSI along with the new MSI you created with Wise.

[bmonrad]

Sorry for the slow followup -- but I ended up getting a nice response from their tech support.

 

They were happy to provide me new MSIs for Kidspiration and Inspiration, but it turned out they were only for a network installation, so all they did was create a shortcut to a configurable network path.

 

After that, they confirmed that all the required files are installed to the respective Program Files folders and they recommended customizing one reference machine with registration info, etc, and then just capture the Program Files folders.

 

So, aside from installing the TTS components via MSI, there are "officially" no worries about missing any registry entries or other system files in a capture/repackage.

 

-ben