HKLM\Init and MFC Application



I'm new to Windows CE development, so I apologize if I'm overlooking some
very obvious things, but I'm having some difficulty in my initial attempts at
customizing a WinCE OS image.

I'm using WinCE 5.0 and Platform Builder as well as EVC++ 4.0SP4. What I've
done is create an MFC application in EVC. I'm trying to use this as a shell
replacement instead of explorer.exe since ultimately I'll be making a
dedicated HMI device.

I created a new platform in Platform Builder and added the options I'd need
for my app (standard SDK, MFC, etc.). I've used this to create and export an
SDK for EVC which is what I built my MFC application against. That builds
and runs on the emulator from EVC.

Next, I created a new project called MyMFCShell in platform builder. I
modified the sources file and changed targettype to "NOTARGET." I created a
MyMFCShell.reg file as follows:

IF IMGMFCSHELL
[HKEY_LOCAL_MACHINE\Init]
"Launch50"="MyMFCShell.exe"
"Depend50"=hex:14,00,1e,00
ENDIF

Finally, I changed postlink.bat to copy the executable from my evc output
directory to the flat release directory, along with the .reg file.

At startup, I see the kernel launching the application, but instead of
coming up properly, I see a message box that says "50 was not found." Note
that I DO call ::SignalStarted(_wtol(m_lpCmLine)) from InitInstance() in
MyMFCShell. Also, if I change the launch key from Launch50 to Launch99 say,
the message box says "99 not found." I've even tried calling
SignalStarted(50) directly in case the command line was somehow getting
messed up by some default behavior in CWinApp, but to no avail.

Any help would be greatly appreciated.


--
Jay Daniel
.



Relevant Pages

  • Re: Further Attempts
    ... > include an MFC app built in EVC into my operation system image. ... >> I created a new platform in Platform Builder and added the options I'd ... if I change the launch key from Launch50 to Launch99 ...
    (microsoft.public.windowsce.platbuilder)
  • Re: HKLMInit and MFC Application (further clarification)
    ... You might try compiling your MFC application with eVC, not PB, and just add ... > If I REMOVE the entry for MyMFCShell.exe from the .bib file, ... >> At startup, I see the kernel launching the application, but instead of ...
    (microsoft.public.windowsce.platbuilder)
  • RE: HKLMInit and MFC Application (further clarification)
    ... the MyMFCShell project from platform builder didn't ... > I'm using WinCE 5.0 and Platform Builder as well as EVC++ 4.0SP4. ... > At startup, I see the kernel launching the application, but instead of ...
    (microsoft.public.windowsce.platbuilder)
  • Re: HKLMInit and MFC Application (further clarification)
    ... I actually DO compile the program in EVC. ... something to do with the MFC dll, but I'm not sure how the "50 was not found" ... > be a problem with the MFC DLL (I assume you're using the MFC as a DLL ... >>> I created a new platform in Platform Builder and added the options I'd ...
    (microsoft.public.windowsce.platbuilder)
  • Further Attempts
    ... include an MFC app built in EVC into my operation system image. ... > I'm using WinCE 5.0 and Platform Builder as well as EVC++ 4.0SP4. ... Also, if I change the launch key from Launch50 to Launch99 say, ...
    (microsoft.public.windowsce.platbuilder)