Static scan question

[NewsArchive]

Hi All

When I compile under windows 7 professional and then build a install file
with setup builder and install the application on a vista machine the
application gives a error that it failed to initialize however it installs
and runs on windows xp and windows 7 machines. The application is installed
under program files with the data stored under shared documents. However if
i take the application that was complied on the windows 7 machine and then
build the install on a vista or xp machine the program will run on xp,
vista, and windows 7. The only thing I notice is when I get setup builder to
do a static scan on the windows 7pc it shows the software needs a whole lot
of system 32 dlls all starting with API-MS_win_core.

C:\Clarion6\BIN\c60ascx.dll
C:\Clarion6\BIN\c60dosx.dll
C:\Clarion6\BIN\c60runx.dll
C:\Clarion6\BIN\c60tpsx.dll
C:\Clarion6\Examples\HowTo-ABC\Browses\abcbrws.exe
C:\Windows\system32\API-MS-WIN-Service-Core-L1-1-0.dll
C:\Windows\system32\API-MS-WIN-Service-Management-L1-1-0.dll
C:\Windows\system32\API-MS-WIN-Service-Management-L2-1-0.dll
C:\Windows\system32\API-MS-WIN-Service-winsvc-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Console-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-DateTime-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-DelayLoad-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Interlocked-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-LocalRegistry-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll
C:\Windows\system32\KERNELBASE.dll

This even appears if I build a install from the clarion examples with no
third party. I assume i have something set wrong in windows 7 for setup
builder.

I have installed windows 7, clarion and setup builder from scratch

Any help would be very much appreciated
TIA
Trevor Cox
Simple Computing
Clarion 6.3 Enterprise 9056
Setup Builder 7.0.2762

[NewsArchive]

Hi Trevor,

> This even appears if I build a install from the clarion examples with no
> third party. I assume i have something set wrong in windows 7 for setup
> builder.
>
> I have installed windows 7, clarion and setup builder from scratch

All the 'api-ms-win-core' and 'api-ms-win-service' DLLs are a result of the
new Windows 7 kernel architecture changes. They contain exported functions
of many well-known WIN32 APIs. You do not distribute these DLLs to your
customers.

Hope this helps.

Friedrich

[NewsArchive]

Yep. All clear now.

I assume it would to okay to add these files to the sbscan.ini file for
filtering purposes.

Many thanks Friedrich.

Trevor

[NewsArchive]

Hi Trevor,

> Yep. All clear now.
>
> I assume it would to okay to add these files to the sbscan.ini file for
> filtering purposes.

I would suggest to add these files to USERSCAN.INI.

I think we'll add the new 'api-ms-win-core' and 'api-ms-win-service' DLLs to
the standard SBSCAN.INI in the next SB7 maintenance build.

Friedrich

[NewsArchive]

Okay thanks for thank

Trevor