PDA

View Full Version : Dao350.dll & msrd2x35.dll not being registered



NewsArchive
04-23-1997, 12:00 AM
I have a VB5 app that I am using Installshield Express Pro 1.11a to install
it. I am including a number of files in the install including Dao350.dll
and msrd2x35.dll. These files are installed okay on the target computer
but they are not being registered. I have to register the files by hand
using regsrv32.exe. Why isn't Installshield properly installing and
registering these files? This is a big problem since any program that I
wish to install that has these files won't run without some manual
tickering with the install.

Anyone know what is going on or how to fix it?

Thanks,
-Joel

<//////////////=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=\\\\\\\\\\\\\\>
/ Joel Bierling \
/ President of Abstraction, Phoenix Data Systems \
/ Calvin College's CS Club -Middle Eastern Archaeology: \
/ jbierl00@calvin.edu Photography & Computer Programming \
/ www.calvin.edu/~jbierl00/ www.calvin.edu/~jbierl00/phoenix.htm \
<//////////////=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=\\\\\\\\\\\\\\>

NewsArchive
04-23-1997, 12:00 AM
Express automatically self register's files whose version information
contain the "OLESelfRegister" string. Both the DLLS you have specified
do not have this string and hence you need to workaround this problem
by crearing the following entries anywhere in the swdepend.ini file
under the OBJS\VB4 directory (assuming that you have selected the
VB4 project type):

[DAO350.DLL]
Register=$(DLLSelfRegister)

[MSRD2X35.DLL]
Register=$(DLLSelfRegister)

Joel Bierling <jbierl00@calvin.edu> wrote in article
<01bc4fff$e33753c0$d7446ec6@universe>...
> I have a VB5 app that I am using Installshield Express Pro 1.11a to
install
> it. I am including a number of files in the install including Dao350.dll
> and msrd2x35.dll. These files are installed okay on the target computer
> but they are not being registered. I have to register the files by hand
> using regsrv32.exe. Why isn't Installshield properly installing and
> registering these files? This is a big problem since any program that I
> wish to install that has these files won't run without some manual
> tickering with the install.
>
> Anyone know what is going on or how to fix it?
>
> Thanks,
> -Joel
>
> <//////////////=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=\\\\\\\\\\\\\\>
> / Joel Bierling \
> / President of Abstraction, Phoenix Data Systems \
> / Calvin College's CS Club -Middle Eastern Archaeology: \
> / jbierl00@calvin.edu Photography & Computer Programming \
> / www.calvin.edu/~jbierl00/ www.calvin.edu/~jbierl00/phoenix.htm \
> <//////////////=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=\\\\\\\\\\\\\\>
>
>

NewsArchive
04-23-1997, 12:00 AM
Thanks for answering. Any idea why MS distributes dll's that don't have
this string?

Within this swdepend.ini file I also see that there are what appears to be
dependancy listings. I think dao350.dll depends on vbajet32.dll and
msjet35.dll. How would I add those to the list?

You also mention that this must be a VB4 project type. I'm not sure if it
is because I just copied this install from a previous install that I had
made. I'm pretty sure that was a VB4 install but how can I make sure? I
see within the .iwz file that it says:
DevTool=for Visual Basic 4.0
Is this what makes it a VB4 project type? In the General Options dialog it
does also have a list for VB objects so I guess this is a VB4 project. If
I changed the DevTool entry would that change the project type to something
else?

If all this information is in a FAQ somewhere please let me know and I'll
gladly read it.

Thanks,
-Joel

Rajesh Ramachandran <rajesh@installshield.com> wrote in article
<01bc4fca$17d98250$8c46b1cc@drain>...
> Express automatically self register's files whose version information
> contain the "OLESelfRegister" string. Both the DLLS you have specified
> do not have this string and hence you need to workaround this problem
> by crearing the following entries anywhere in the swdepend.ini file
> under the OBJS\VB4 directory (assuming that you have selected the
> VB4 project type):
>
> [DAO350.DLL]
> Register=$(DLLSelfRegister)
>
> [MSRD2X35.DLL]
> Register=$(DLLSelfRegister)

NewsArchive
04-23-1997, 12:00 AM
Joe,

> Within this swdepend.ini file I also see that there are what appears to
be
> dependancy listings. I think dao350.dll depends on vbajet32.dll and
> msjet35.dll. How would I add those to the list?

Just include vbajet32.dll and msjet35.dll to your installation
and ISX will copy these files. But make sure the target directory you
specify
is where DAO350.dll would look for these files in. After copying all the
files ISX would
start registering the files. If an executable has got "???SelfRegister"
string in its
version info ISX will do it automatically. If the string is not present in
there
you will have to put an entry in SWDEPEND.INI to self-register
[Executable name]
Register=$(???SelfRegister) // ??? could be EXE or OLE or DLL
ISX traverses all the executables copied and checks for "???SelfRegister"
string
in the version info. If not found it checks in the SWDEPEND.INI. This is to
support
older SelfRegistering files because they did not have this info in the
version info.

> You also mention that this must be a VB4 project type. I'm not sure if
it
> is because I just copied this install from a previous install that I had
> made. I'm pretty sure that was a VB4 install but how can I make sure? I
> see within the .iwz file that it says:
> DevTool=for Visual Basic 4.0
> Is this what makes it a VB4 project type? In the General Options dialog
it
> does also have a list for VB objects so I guess this is a VB4 project.
If
> I changed the DevTool entry would that change the project type to
something
> else?

If you change "for Visual Basic 4.0" to something else ISX will assume
the project as Generic Windows project.

Note:
You can carefully modify ISDEPEND.INI and SWDEPEND.INI to
change the behaviour of a particular project type.

Raja

NewsArchive
04-23-1997, 12:00 AM
Joel Bierling <jbierl00@calvin.edu> wrote in article
<01bc5076$a92b1ff0$d7446ec6@universe>...
> Thanks for answering. Any idea why MS distributes dll's that don't have
> this string?
Beats me. There are many other OCXs and DLLs which do not have
this string.
>
> Within this swdepend.ini file I also see that there are what appears to
be
> dependancy listings. I think dao350.dll depends on vbajet32.dll and
> msjet35.dll. How would I add those to the list?
You don't have to bother listing the dependencies under the section created
for self-registration.Infact Express ignores the Usesx entries under this
section. Listing the dependencies is only required for Express objects.

> You also mention that this must be a VB4 project type. I'm not sure if
it
> is because I just copied this install from a previous install that I had
> made. I'm pretty sure that was a VB4 install but how can I make sure? I
> see within the .iwz file that it says:
> DevTool=for Visual Basic 4.0
> Is this what makes it a VB4 project type? In the General Options dialog
it
> does also have a list for VB objects so I guess this is a VB4 project.
If
> I changed the DevTool entry would that change the project type to
something
> else?
Yes. DevTool is what determines your project type. Changing DevTool to
something
else would switch your project type but this could also result in the loss
of integrity
of the .iwz file. If you use any Express objects then switching project
types by
just changing the DevTool entry could cause problems.

NewsArchive
04-23-1997, 12:00 AM
Express automatically self register's files whose version information
contain the "OLESelfRegister" string. Both the DLLS you have specified
do not have this string and hence you need to workaround this problem
by crearing the following entries anywhere in the swdepend.ini file
under the OBJS\VB4 directory (assuming that you have selected the
VB4 project type):

[DAO350.DLL]
Register=$(DLLSelfRegister)

[MSRD2X35.DLL]
Register=$(DLLSelfRegister)

Joel Bierling <jbierl00@calvin.edu> wrote in article
<01bc4fff$e33753c0$d7446ec6@universe>...
> I have a VB5 app that I am using Installshield Express Pro 1.11a to
install
> it. I am including a number of files in the install including Dao350.dll
> and msrd2x35.dll. These files are installed okay on the target computer
> but they are not being registered. I have to register the files by hand
> using regsrv32.exe. Why isn't Installshield properly installing and
> registering these files? This is a big problem since any program that I
> wish to install that has these files won't run without some manual
> tickering with the install.
>
> Anyone know what is going on or how to fix it?
>
> Thanks,
> -Joel
>
> <//////////////=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=\\\\\\\\\\\\\\>
> / Joel Bierling \
> / President of Abstraction, Phoenix Data Systems \
> / Calvin College's CS Club -Middle Eastern Archaeology: \
> / jbierl00@calvin.edu Photography & Computer Programming \
> / www.calvin.edu/~jbierl00/ www.calvin.edu/~jbierl00/phoenix.htm \
> <//////////////=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=\\\\\\\\\\\\\\>
>
>

NewsArchive
04-23-1997, 12:00 AM
Thanks for answering. Any idea why MS distributes dll's that don't have
this string?

Within this swdepend.ini file I also see that there are what appears to be
dependancy listings. I think dao350.dll depends on vbajet32.dll and
msjet35.dll. How would I add those to the list?

You also mention that this must be a VB4 project type. I'm not sure if it
is because I just copied this install from a previous install that I had
made. I'm pretty sure that was a VB4 install but how can I make sure? I
see within the .iwz file that it says:
DevTool=for Visual Basic 4.0
Is this what makes it a VB4 project type? In the General Options dialog it
does also have a list for VB objects so I guess this is a VB4 project. If
I changed the DevTool entry would that change the project type to something
else?

If all this information is in a FAQ somewhere please let me know and I'll
gladly read it.

Thanks,
-Joel

Rajesh Ramachandran <rajesh@installshield.com> wrote in article
<01bc4fca$17d98250$8c46b1cc@drain>...
> Express automatically self register's files whose version information
> contain the "OLESelfRegister" string. Both the DLLS you have specified
> do not have this string and hence you need to workaround this problem
> by crearing the following entries anywhere in the swdepend.ini file
> under the OBJS\VB4 directory (assuming that you have selected the
> VB4 project type):
>
> [DAO350.DLL]
> Register=$(DLLSelfRegister)
>
> [MSRD2X35.DLL]
> Register=$(DLLSelfRegister)

NewsArchive
04-23-1997, 12:00 AM
Joe,

> Within this swdepend.ini file I also see that there are what appears to
be
> dependancy listings. I think dao350.dll depends on vbajet32.dll and
> msjet35.dll. How would I add those to the list?

Just include vbajet32.dll and msjet35.dll to your installation
and ISX will copy these files. But make sure the target directory you
specify
is where DAO350.dll would look for these files in. After copying all the
files ISX would
start registering the files. If an executable has got "???SelfRegister"
string in its
version info ISX will do it automatically. If the string is not present in
there
you will have to put an entry in SWDEPEND.INI to self-register
[Executable name]
Register=$(???SelfRegister) // ??? could be EXE or OLE or DLL
ISX traverses all the executables copied and checks for "???SelfRegister"
string
in the version info. If not found it checks in the SWDEPEND.INI. This is to
support
older SelfRegistering files because they did not have this info in the
version info.

> You also mention that this must be a VB4 project type. I'm not sure if
it
> is because I just copied this install from a previous install that I had
> made. I'm pretty sure that was a VB4 install but how can I make sure? I
> see within the .iwz file that it says:
> DevTool=for Visual Basic 4.0
> Is this what makes it a VB4 project type? In the General Options dialog
it
> does also have a list for VB objects so I guess this is a VB4 project.
If
> I changed the DevTool entry would that change the project type to
something
> else?

If you change "for Visual Basic 4.0" to something else ISX will assume
the project as Generic Windows project.

Note:
You can carefully modify ISDEPEND.INI and SWDEPEND.INI to
change the behaviour of a particular project type.

Raja

NewsArchive
04-23-1997, 12:00 AM
Joel Bierling <jbierl00@calvin.edu> wrote in article
<01bc5076$a92b1ff0$d7446ec6@universe>...
> Thanks for answering. Any idea why MS distributes dll's that don't have
> this string?
Beats me. There are many other OCXs and DLLs which do not have
this string.
>
> Within this swdepend.ini file I also see that there are what appears to
be
> dependancy listings. I think dao350.dll depends on vbajet32.dll and
> msjet35.dll. How would I add those to the list?
You don't have to bother listing the dependencies under the section created
for self-registration.Infact Express ignores the Usesx entries under this
section. Listing the dependencies is only required for Express objects.

> You also mention that this must be a VB4 project type. I'm not sure if
it
> is because I just copied this install from a previous install that I had
> made. I'm pretty sure that was a VB4 install but how can I make sure? I
> see within the .iwz file that it says:
> DevTool=for Visual Basic 4.0
> Is this what makes it a VB4 project type? In the General Options dialog
it
> does also have a list for VB objects so I guess this is a VB4 project.
If
> I changed the DevTool entry would that change the project type to
something
> else?
Yes. DevTool is what determines your project type. Changing DevTool to
something
else would switch your project type but this could also result in the loss
of integrity
of the .iwz file. If you use any Express objects then switching project
types by
just changing the DevTool entry could cause problems.