Problem creating OCX registry settings - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

BobM
Posts: 11
Joined: Tue Aug 22, 2006 9:05 am

Problem creating OCX registry settings

Hi,

I added an OCX file under Application Folder.
The source of the file is like...
"E:\NBDEVVC\bin\unicode release\NBCopyViewerW.ocx"

I then set the file properties to Auto register dll, Extract registration info from native library.

The registry entries have the path to the source file rather than the APPDIR path, and instead of being a full file name, it is an 8.3 name...
CLSID.{....}.InprocServer32:(Default)
E:\NBDevVC\bin\UNICOD~1\NBCOPY~1.OCX

This I would expect to be
[APPDIR]NBCopyViewerW.ocx


When I move the source ocx file to a path without a SPACE, the InprocServer32 is specified as...
[APPDIR]NBCOPY~1.OCX


So I think the SPACE in the source path is stuffing AIs ability to replace the source path with the destination [APPDIR].

Also, why is the filename of the ocx shortened to 8.3?

TIA
Bob
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi Bob,

Yes, you are right, in some cases the paths are not replaced with the formatted paths. We will investigate this issue, I add this on our TODO list. Thank you for bringing this to our attention.

Until then you can use the "Self register native library" option. With this option the file will be registered at install time.

Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
Quadiago
Posts: 71
Joined: Thu May 31, 2007 9:07 am

Hi there

I am getting the same problem, and it is really giving me some pains. I really hope you'll be albe to sort it out soon. I've seen that in some cases fullstops in the path also mess things up.

Thanks!
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi,

We are aware of this issue and will be fixed in a future version of AI. I'm afraid I cannot give an ETA. Until then you can modify the extracted information in the "Registry" page and replace the hard coded paths with Formatted.

Or you can use the "Self register native library" option. In this case the file is registered at install time by Windows Installer.

Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com

Return to “Common Problems”