PDA

View Full Version : SWDEPEND.INI & ISDEPEND.INI



NewsArchive
10-04-1996, 12:00 AM
I just recently moved from the Microsoft Setup Wizard to InstallShield
Express. In the past I have had plenty of problems during the setup
process that I was able to trace back to Microsoft's SWDEPEND.INI file. I
have had to make changes to this file to ensure some controls (like Crystal
Reports) installed and registered themselves properly. I noticed that
there is a SWDEPEND.INI and ISDEPEND.INI file in a directory under the
InstallShield directory. Can anyone give me some information on how
InstallShield uses these files as opposed to the SWDEPEND.INI in the
Windows directory? I am very interested in understanding where
InstallShield goes to identify what additional files are needed for each
control.

Thanks in advance,

Matt K.
mkrzy@msn.com

NewsArchive
10-09-1996, 12:00 AM
Matt Krzysiak <mkrzy@msn.com> wrote
> I just recently moved from the Microsoft Setup Wizard to InstallShield
> Express. In the past I have had plenty of problems during the setup
> process that I was able to trace back to Microsoft's SWDEPEND.INI file.
I
> have had to make changes to this file to ensure some controls (like
Crystal
> Reports) installed and registered themselves properly. I noticed that
> there is a SWDEPEND.INI and ISDEPEND.INI file in a directory under the
> InstallShield directory. Can anyone give me some information on how
> InstallShield uses these files as opposed to the SWDEPEND.INI in the
> Windows directory? I am very interested in understanding where
> InstallShield goes to identify what additional files are needed for each
> control.

SWDEPEND.INI and ISDEPEND.INI are used during runtime to register files.
Express does not use any SWDEPEND.INI files from the windows directory.

Ritesh

NewsArchive
05-22-1997, 12:00 AM
Matt,

I too have had problems with CRYSTL16.OCX that I traced back to
SWDEPEND.INI. Here is what your CRYSTL16.OCX entry needs to look like:

[CRYSTL16.OCX]
Register=$(DLLSelfRegister)

[CRYSTL16 OCX]
Src=<WINSYS16DIR>
Uses1=CRYSTL16.OCX
Uses2=CRPE.DLL
Uses3=CRXLATE.DLL
Uses4=uxddisk.dll
Uses5=uxfdif.dll
Uses6=uxfrec.dll
Uses7=uxfsepv.dll
Uses8=uxftext.dll
Uses9=pdbdao.dll
Uses10=pdctdao.dll
Uses11=pdirdao.dll
Uses12=pdsodbc.dll
Uses13=PDBBND.DLL
Uses14=MFCOLEUI.DLL

Note that the first entry has a "." between the filename and the
extension, while the second does not. This is Very Important (and was the
source of all my problems)! The first entry tells InstallShield to
register this file, while the second lists all of the files that accompany
the file.

Regards,

Steve Locke
HBO & Company, Inc

Matt Krzysiak <mkrzy@msn.com> wrote in article
<01bbb223$8a95e760$ddb02399@chimchim>...
> I just recently moved from the Microsoft Setup Wizard to InstallShield
> Express. In the past I have had plenty of problems during the setup
> process that I was able to trace back to Microsoft's SWDEPEND.INI file.
I
> have had to make changes to this file to ensure some controls (like
Crystal
> Reports) installed and registered themselves properly. I noticed that
> there is a SWDEPEND.INI and ISDEPEND.INI file in a directory under the
> InstallShield directory. Can anyone give me some information on how
> InstallShield uses these files as opposed to the SWDEPEND.INI in the
> Windows directory? I am very interested in understanding where
> InstallShield goes to identify what additional files are needed for each
> control.
>
> Thanks in advance,
>
> Matt K.
> mkrzy@msn.com
>