View Full Version : Static Scan...
NewsArchive
04-10-2008, 01:55 AM
Hi friedrich,
Making a new project, Files and Folders, adding only the .exe, Static
Scan... it to detect (mostly) the C60xxx.dlls to include, it did not detect
some aplication dlls
May be its a bug or I´m doing something wrong?
--
Saludos / Regards,
Alberto Michelis
ARMi software & technology
www.armi.com.ar
NewsArchive
04-10-2008, 01:55 AM
Alberto,
> Making a new project, Files and Folders, adding only the .exe, Static
> Scan... it to detect (mostly) the C60xxx.dlls to include, it did not
> detect some aplication dlls
> May be its a bug or I´m doing something wrong?
Two possible reasons:
1. The application DLLs are filtered (listed in sbscan.ini or userscan.ini)
2. The application DLLs are not statically linked but dynamically.
Hope this helps.
Friedrich
--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910
"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes
-- Official Comodo Code Signing and SSL Certificate Partner
NewsArchive
04-10-2008, 01:56 AM
Thanks Friedrich,
All the apps dll were added the same way to the main app when I add an
external procedure.
Is there a way to see the way they are linked?
--
Saludos / Regards,
Alberto Michelis
ARMi software & technology
www.armi.com.ar
NewsArchive
04-10-2008, 01:56 AM
> All the apps dll were added the same way to the main app when I add an
> external procedure.
> Is there a way to see the way they are linked?
If the DLLs are "loaded" at application startup then they are statically
linked. And in this case Static Scan would detect all of them. If no error
is reported (e.g. because dependency files are not found) then all
statically linked DLLs are listed (excluding the filtered DLLs of course).
Friedrich
NewsArchive
04-10-2008, 01:56 AM
Sorry, I dont understand.
How can I look into my clarion app and see the way they are linked?
--
Saludos / Regards,
Alberto Michelis
ARMi software & technology
www.armi.com.ar
NewsArchive
04-10-2008, 01:57 AM
All the DLLs in the Module tab of Clarion are External Dynamic Link Library
(DLL)
Some are scaned an some not.
Any Idea?
--
Saludos / Regards,
Alberto Michelis
ARMi software & technology
www.armi.com.ar
NewsArchive
04-10-2008, 01:57 AM
> All the DLLs in the Module tab of Clarion are External Dynamic Link
> Library
> (DLL)
> Some are scaned an some not.
> Any Idea?
The only think I know is that it's not a bug in SetupBuilder. There was no
source code modification in Static Scan for 10 years now (this module comes
from SetupBuilder 3).
Perhaps the DLLs not listed are not used from that application? If there
would be a scan error then you would have received an error message from the
Scan wizard.
You can zip the files up and send it to us (and let us know which files are
not listed). Then we can tell you which files are not statically linked.
BTW, there is no need to include the Clarion runtime files.
Friedrich
NewsArchive
04-10-2008, 01:58 AM
You could also cross-check with Dependency Walker and load the application
and it will tell you if there are missing DLLs. I don't think I've run
across a scenario where it missed one. I guess running the app in profile
mode would pick those up.
--
Russell B. Eggen
www.radfusion.com
Skype Clarion chat: http://tinyurl.com/2273lm
NewsArchive
04-10-2008, 01:58 AM
> You could also cross-check with Dependency Walker and load the application
> and it will tell you if there are missing DLLs. I don't think I've run
> across a scenario where it missed one. I guess running the app in profile
> mode would pick those up.
Good idea!
Friedrich
NewsArchive
04-10-2008, 01:59 AM
Sent... admin.dll is not listed
--
Saludos / Regards,
Alberto Michelis
ARMi software & technology
www.armi.com.ar
NewsArchive
04-10-2008, 01:59 AM
Not received yet, but please check the SBSCAN.INI <g>
I wrote in my first reply:
> 1. The application DLLs are filtered (listed in sbscan.ini or
> userscan.ini)
> 2. The application DLLs are not statically linked but dynamically.
admin.dll is listed as Windows core component ;-)
That means it was 1) ;-)
--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910
"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes
-- Official Comodo Code Signing and SSL Certificate Partner
NewsArchive
04-10-2008, 02:00 AM
Yes, you are right, as usual <g>
Then we cant name a dll with any of the sbscan.ini names?
--
Saludos / Regards,
Alberto Michelis
ARMi software & technology
www.armi.com.ar
NewsArchive
04-10-2008, 02:00 AM
You can't make user.exe either <g>
--
Russell B. Eggen
www.radfusion.com
Skype Clarion chat: http://tinyurl.com/2273lm
NewsArchive
04-10-2008, 02:01 AM
Alberto,
> Yes, you are right, as usual <g>
> Then we cant name a dll with any of the sbscan.ini names?
Well, you have a few options <g>
1. Deselect the "Filter" checkbox option (not recommended)
2. Comment-out the admin.dll in sbscan.in (not recommended)
3. Rename your admin.dll (recommended)
I remember a discussion some years ago in the Clarion newsgroups where a DLL
file named admin.dll caused big trouble (because of Windows File
Protection). I can't find the thread right now, but I think someone
contacted Microsoft and they recommended not to use "core system file names"
at all.
Friedrich
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.