Error while build target image

  • Thread starter Thread starter Tenko
  • Start date Start date
T

Tenko

I get this error while build target image:

Error 5 (0x5) in "Microsoft VBScript runtime error":
Invalid procedure call or argument
An internal error occurred while building the run-time
image.
Code = 0x800a0005
Description = Invalid procedure call or argument

What this mean?
How can I fix it?
Is the target image correct generated?
 
Tenko said:
I get this error while build target image:

Error 5 (0x5) in "Microsoft VBScript runtime error":
Invalid procedure call or argument
An internal error occurred while building the run-time
image.
Code = 0x800a0005
Description = Invalid procedure call or argument
Click to expand...
Are you using any FBA Command or scripting in any of your component.I
recall getting this error before .
 
I get this error while build target image:

Error 5 (0x5) in "Microsoft VBScript runtime error":
Invalid procedure call or argument
An internal error occurred while building the run-time
image.
Code = 0x800a0005
Description = Invalid procedure call or argument

What this mean?
How can I fix it?
Is the target image correct generated?
Click to expand...

What's in the configuration? Did this config ever work properly? How
did you generate the configuration? Can you simply open a new blank
config, check deps, then build without errors?
 
Hello Jon,

I hope this are answers to yours questions:
Can you simply open a new blank config, check deps, then
Click to expand...
build without errors?

No, i get the same error Code=0x800a0005
How did you generate the configuration?
Click to expand...

Just add my component (a sample application in user mode)
and resolve dependecies
Did this config ever work properly?
Click to expand...

No, when I try to start it get the error

Windows could not start because the following file is
missing or corrupt:
What's in the configuration?
Click to expand...

A configuration based on Standart PC component.
If You want I will send a list of all components to You.


If this will be useful to You:
I run evaluation version of XP Embedded Studio with SP1 on
Windows 2000 with SP2.
When try to run Dependency Walker on one of files in image
i get the errors:
1. The procedure entry point DeactivateActCtx could not
be located in the dynamic link library KERNEL32.dll
2. Cannot find the file 'X:\path\xxx.dll' (or one of its
components). ....

Regards Tenko.
 
Hello Jon,

I hope this are answers to yours questions:

build without errors?

No, i get the same error Code=0x800a0005


Just add my component (a sample application in user mode)
and resolve dependecies


No, when I try to start it get the error

Windows could not start because the following file is
missing or corrupt:
<Windows root>\system32\hal.dll
Please re-install a copy of the above file
Click to expand...

The only thing in the configuration is your custom component? No
hardware components? The error message you listed is caused by a
missing computer component - Standard PC, ACPI PC, etc. If you don't
have any HW components in your configuration, you won't be able to boot
anything.

Run TAP.EXE on your device, import the PMQ file into Component Designer
to create a HW component, import that component into your database, then
add it to your configuration. Then check dependencies and rebuild.
 
Hello Jon,

I install the Embedded tools on Windows XP and everything
is ok. Maybe is some kind of bug or incompatibility with
Windows 2000 of Embedded tools.
Thank You for help me.

Regards Tenko.
 
Back
Top