Setup file could not be created
Posted 26 December 2003 - 06:36
When I am creating the setup file, the setup file will stop at this line: Extracting COM data from 5 component(s). Actually the whole program is still not in "Not Responding" stage, but it seem like after 1 or 2 hour, the setup progress output still show the same line and seem like it's not moving on.
Yet, sometimes(maybe lucky enough but rarely happen), when Installshield show the same line : Extracting COM data.... There is a blank window pop up, once I close the window the setup goes on and complete.
I know this might not be a very difficult problem for you guys, but as a new user, I am just stumbled here. Please help.....!!!!!!
Posted 27 December 2003 - 12:00
Posted 30 December 2003 - 10:05
If you have set a file that is not self-registering to COM extract at build the setup creation can hang. The blank message box you see are usually error messages from DLL's or EXE files that cannot complete the self-registration (usually becasue a file that is needed for registration to succeed cannot be located - often language resources).
Posted 05 January 2004 - 09:27
Can you pls elaborate? THankX
Posted 05 January 2004 - 20:47
You can also open a command prompt, navigate to the directory where the COM file is located and try to register it manually:
For a dll:
> regsvr32.exe YourComFile.dll
For an EXE file:
You should not see any error messages after typing in these commands and pressing enter (if the files are really COM files and they register properly).
Posted 06 January 2004 - 09:18
I dont understand much about dependency.
I have already run dependency walker, and I have found a lot of error icon on my dll, do i need to register all that? it's too many and impossible for me to do it one by one. so how?
and really look like most of the file is language related file, guess it's not important rith? can i explicitly exclude those file in installshield?
Edited by biao81, 06 January 2004 - 10:11.
Posted 06 January 2004 - 18:41
For your application to work correctly it should be able to "find" all the dll's listed as "not found" in the screen shot you added. This sometimes means that you need to add a merge module to install system components or various runtime files.
You should make sure "COM Extract" is not enabled for any files that aren't COM components in the first place. To identify a COM component, open it in Dependency Walker and ensure that you see the functions "DllRegisterServer" and "DllUnregisterServer".
Posted 06 January 2004 - 18:45
Posted 07 January 2004 - 03:35
And although as you say, there is error message, but even the error exists, my application still can run perferctly on my client computer, so it's ok.
And for what u have mention about Dependecy Walker, i;m too unfamiliar with it to follow the instruction.
Posted 16 June 2004 - 13:41