msdarmawan
4th July 2005 03:29 UTC
how to add version tabsheet into DLL files (not executable installer)
Hi, I'm a newbie, this is my first installer script and also my first unsolved error. please help.
I Have a dll file which doesn't have version info tablesheet, when I try to compile a script installer using upgrade a DLL macro, it return an error since my dll doesn't have version info tablesheet.
How can I add version info into my DLL file ? (just to set a dummy version to make upgrade DLL macro work), or
is there any error trap to ignore upgrade DLL macro from detecting a DLL that doesn't have version information ?
I have search the forum, but I only found "Adding a Windows Version Info Tabsheets to NSIS installer executables" topics. Looks like it doesn't solve my problem.
Thanks in advance, your information is valuable for me.
Best regards,
MSDarmawan
Mæster
4th July 2005 06:00 UTC
Thats a strange dll without version information. Did you tried to right click on your dll > Version Tab?
However, try to register your dll on your system to find out if your dll could/should be registered or not. If not you wont have to use the dll macro - you just could copy it to the destination path.
Just run the following command in START > RUN:
regsvr32.exe "[YourPathToDLL]\yourdll.dll"
You will get a message which says, if the registering was successful or not. If not you just could copy your file.
msdarmawan
4th July 2005 08:17 UTC
It returns an error message. it says :
the dll was loaded, but the DllRegisterServer entry point was not found.
This file can not be registered
Do I have to just copy to the system directory without registering ???
Mæster
4th July 2005 08:53 UTC
> Do I have to just copy to the system directory without registering ???
Yes, thats right.
onad
4th July 2005 09:47 UTC
one could theoretically patch a DLL to add Version resource. But since you are new to it, it will cost you some effort to undersand this technique.
Basicly you can take a resource editor and add Version resource and than save the DLL again.
Your second option is to do a MD5 Checksum on the DLL to see if it another version an couple the MD5 Checksum to the version in a valuetable in you installerscript.
Success