Jump to content

Recommended Posts

Posted

Ahah...

 

ok... starting to get somewhere here..

 

Speaking the cricksoftware tech bod I got this little nugget.

 

Replace the text to speech files with do nothing EXE files...

 

Run the workstation setup.exe with the silent switch which is a /s (edited as the tech gave me the wrong info!) and that should work silently and then you can install the msttsa22L and SPCHAPI files seperately using their own /Q quiet switches.

 

Still early days but useful info all round :)

Posted

ok... after all that I think I've got a reasonably good solution here.

 

Basically you rename your MSSpeech exe files to something appended with -orig.exe.

 

Then use SciTE to create a little AutoIT script that calls each of the renamed files in turn using the /Q switch to shut them up.

 

compile these AutoIT scripts to exe's that are the same as the originals were before (ie: SPCHAPI.exe and msttsa22L.exe) and make sure they're in the same place as the originals.

 

After than you just create a wrapper MSI for the Workstation Installer with the /s switch to make that silent too and bobs your aunties live in lover..

 

 

Still have to test this on a GPO install but it works pretty quietly so far...

 

 

There's a few other things to watch out for "filepath.dat" but I might as well pop all that lot into a Wiki document so i'll not repeat it all here.

 

8)

Posted
Serious Deja Vu! You're nearly there by the sounds of it. I found that sometimes the silent switches don't quite work though and needed an adhoc function in my AutoIt script to watch for file overwrite confirmations and automatically hit OK/YES.
Posted
Serious Deja Vu! You're nearly there by the sounds of it. I found that sometimes the silent switches don't quite work though and needed an adhoc function in my AutoIt script to watch for file overwrite confirmations and automatically hit OK/YES.

:) I can imagine... I think the tech at Cricksoft had your old call log when he was trying to remember what to do :D

 

I'll probably refine that script a little to do as you said, ie: look out for overwrites, etc.. but so far it seems to work and as far as my primary install on fresh machines go it's a winner :)

 

If you have the old scripts though I'd sure be interested in seeing how you did it :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...