Mayayana
2/29/2012 2:46:00 PM
I can answer about SAPI. SAPI 5 is on WinXP.
SAPI 4 is very different. If you need to support
SAPI 5 pre-XP it's a long, crazy story. (SAPI 5
is not a redistributable. It's several files and Registry
settings. Microsoft only supports shipping it as
part of an MSI install, but people have created
3rd-party installers.)
If you only need to support XP+ then you don't
have to worry. Just use it. (Unless you want to
specify voices, which is a separate can of worms.)
--
--
"BeeJ" <nospam@spamnot.com> wrote in message
news:jijuij$itr$1@speranza.aioe.org...
| From Win XP basic onward ...
|
| What is normally done?
| (1) A user does not update the OS and I want to install a VB6 app using
| a) Packaged install (say Inno)
| b) reg-free com manifest (MMM) or PDW
| What do I include or what can I include, how do I know?
| (Let's assume the the installer is not smart, or is it?)
|
| e.g. quartz.dll, sapi
|
| (A) probably cannot include in installer.
| (B) do I demand that the user pre-intall DirectX or SAPI?
| Should I check for the .dlls etc or does the installer do that?
|
| Do any of the installers help do this?
| Where do you find the info needed to do any of this?
| I think Inno has the ability to run any .EXE during install so is that
| where something is done?
|
| I have found that even using an installer for one of my apps that if I
| install on a development PC it installs just fine. If I install it on
| a clean XP Pro PC the install completes but the app won't start. This
| I believe is because the VB6 app.exe checks for or tries to load
| missing references etc and just quits without message or warning
| leaving me in the dark. So I am having difficulty determining what is
| wrong. Unfortunately this app uses a lot of references, some that I
| created like ActiveX EXEs and other .dlls from third parties or MS.
|
|