PDA

View Full Version : Another OC25.DLL question/problem



NewsArchive
06-27-1997, 12:00 AM
Hi,
I am using 2.01 InstallShield Express. My target is Windows 95 and NT (ie.
32 bit). Our app uses a 3rd party product that is 16 bit (a problem in
several regards). I install most DLLs into <winsysdir>. I install all the
16 bit DLLs (and all other support files for the 3rd party app) into
<winsys16dir>.

Basically, all goes well. I know that ISX cannot register OC25.DLL
automatically since it's a 16 bit DLL. I, therefore, call to an extension
to register it via regsvr.exe. This all works fine.

My issue is that I don't want my customers to see "The following dlls could
not self-register: OC25.DLL". This displays in an "ERROR" message box.

This message is followed a few seconds later with a "registration
successful" message after it is registered via the extension.

I not comfortable editing the dll to remove the auto-registration string.
(I'm not sure Microsoft would smile on this practice.)

I've tried removing the line "GroupXFileYReg=1" from the .iwz file. ISX
just puts it back.

Any ideas?

Thanks

Jim Williamson
MIDS, Inc

jimw@midsinc.com

NewsArchive
07-01-1997, 12:00 AM
Jim,

Try the following:
Compress the file inside of the SUPPORDIR and then run Regsvr.exe as an
extension to register this file. To register the file when it is in the
SUPPORDIR use the following:
[Program Files]\REGSVR.EXE <SUPPORTDIR>\soc25.dll
Similar method can be used if you include the file as uncompressed on
disk1--this would then
require an extension or a batch method to copy the uncompressed file to the
target.
I hope the above helps.
Dan
Jim Williamson <jimw@midsinc.com> wrote in article
<01bc8318$2eeeffc0$2b2b55ce@jimw.midsinc.com>...
> Hi,
> I am using 2.01 InstallShield Express. My target is Windows 95 and NT
(ie.
> 32 bit). Our app uses a 3rd party product that is 16 bit (a problem in
> several regards). I install most DLLs into <winsysdir>. I install all
the
> 16 bit DLLs (and all other support files for the 3rd party app) into
> <winsys16dir>.
>
> Basically, all goes well. I know that ISX cannot register OC25.DLL
> automatically since it's a 16 bit DLL. I, therefore, call to an
extension
> to register it via regsvr.exe. This all works fine.
>
> My issue is that I don't want my customers to see "The following dlls
could
> not self-register: OC25.DLL". This displays in an "ERROR" message box.
>
> This message is followed a few seconds later with a "registration
> successful" message after it is registered via the extension.
>
> I not comfortable editing the dll to remove the auto-registration string.

> (I'm not sure Microsoft would smile on this practice.)
>
> I've tried removing the line "GroupXFileYReg=1" from the .iwz file. ISX
> just puts it back.
>
> Any ideas?
>
> Thanks
>
> Jim Williamson
> MIDS, Inc
>
> jimw@midsinc.com
>
>