Re: Platform builder executable won't run in Windows explorer

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Paul

You are right that those dlls are in .\Windows folder on my target. I took
the two dependent dlls out of the .\release folder. This has no effect. I
still get the same error when I try to run.

Thanks
--
Don


"Paul G. Tobey [eMVP]" wrote:

I believe that your problem is related to the release folder stuff. Copy
just the EXE (the other DLLs are almost certainly built into the device ROM
and found in the ROM filesystem in \Windows), to the RAM filesystem (\,
maybe). Then try running it.

Paul T.


"Don" <Don@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:74EAE19F-0386-488D-AB72-056CAED058F6@xxxxxxxxxxxxxxxx
Hi Paul

Both the Dlls are in the shared .\release folder. On the target running
Windows CE it is .\Release and on my XP machine where I am running
Platfrom
builder and deploying the Window CE image over ethernet the directory is
called
C:\WINCE500\PBWorkspaces\AXYZMiniITX\RelDir\VIACN_x86_Release.
I don't think I copied these dlls there. I used a board support package
for my MiniITX hardware when I built the OS and wrote an executable called
pciemum.exe and the dlls just happen to be in this folder.
--
Don


"Paul G. Tobey [eMVP]" wrote:

Both are in the folder you're trying to run from? You copied coredll.dll
to
some other folder? Not a good idea! If the EXE is built into the OS and
is
in the \Windows folder, that's one thing, or if you copied it there,
that's
OK. Please be specific.

Paul T.

"Don" <Don@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EFB23DE4-1099-4DF6-89D2-D45EA5DEEBCE@xxxxxxxxxxxxxxxx
Hi Paul

I used Depends on my exe and the dependencies it uses are coredll.dll
and
ceddk.dll.
Both of these files are in the folder I am tring to run from.

Do you have any other suggestions?

Thanks
--
Don


"Paul G. Tobey [eMVP]" wrote:

Obviously, no one could know what component an EXE that we don't have
source
for or build instructions for is missing!

Use depends.exe, which comes with various tools, including Visual
Studio,
to
see what DLLs your EXE depends upon. That's the most-likely cause, a
DLL
that gets built-in in DEBUG builds and not in RETAIL builds (or a DLL
that's
in the Release folder during DEBUG and where you have Release folder
access
allowed, and not in the OS in RETAIL).

Paul T.

"Don" <Don@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A31CF064-D1FD-4D3B-B0EA-2243DCA43B9B@xxxxxxxxxxxxxxxx
Hi

I am building an executable through Platfrom Builder 5.0.
It's name it pciemum.exe. I am able to run my executable by choosing
Target/Run Programs in the Platform builder GUI over ethernet but
when
I
try
to run it through Windows Explorer by clicking on the exe on my
target
hardware I get the following error:

Cannot file 'pciemum' (or one of its component(s). Make sure the
path
and
filename are correct and that all the required libraries are
available.

Does anyone know what the componant is that I am missing?

Any help here would be greatly appreciated
Thanks

--
Don









.

Relevant Pages

  • Re: Platform builder executable wont run in Windows explorer
    ... I believe that your problem is related to the release folder stuff. ... just the EXE (the other DLLs are almost certainly built into the device ROM ...
    (microsoft.public.windowsce.embedded)
  • Re: Platform builder executable wont run in Windows explorer
    ... You are right that those dlls are in .\Windows folder on my target. ... If the EXE is built into the OS ...
    (microsoft.public.windowsce.embedded)
  • Re: Platform builder executable wont run in Windows explorer
    ... On the target running ... Windows CE it is .\Release and on my XP machine where I am running Platfrom ... I don't think I copied these dlls there. ... pciemum.exe and the dlls just happen to be in this folder. ...
    (microsoft.public.windowsce.embedded)
  • Re: Platform builder executable wont run in Windows explorer
    ... Copy the target EXE that you want to run ... You are right that those dlls are in .\Windows folder on my target. ...
    (microsoft.public.windowsce.embedded)
  • Re: essential OS/2
    ... I had to spend time identifying the missing modules and retrieving them from another partition. ... Now I move those program specific dlls back to the folders where the program was installed. ... I am using TVFS and I add the location of these dlls to the list of folders that I append to libpath virtual folder that TVFS creates. ... I have to run which & find duplicated on the libpath to control the common named dlls. ...
    (comp.os.os2.misc)