Re: WM 5.0: how to automatically run a process in the background.
- From: <John>
- Date: Mon, 24 Oct 2005 17:29:30 -0700
> What are you talking about? device.exe doesn't have "space" to be left or
> not left.
There is 32 mb/process limit, which is practically exhausted in device.exe,
which hosts more than 110 DLLs on some recent PDAs (like JasJar).
As the result, any attempt to load even a tyny additional DLL often (or
always fails)
with error code 14 (out of mem). Even worse, sometimes third party drivers
get loaded in before some essential system drivers, so the device fails to
boot.
This is a known problem (somebody from MS told that),
but nothing can be done for now. Just don't write unnecessary drivers.
Service.exe has only about 60 DLLs and I never had (yet) out of memory
errors there. It does not mean that everybody should start wirting services
- otherwise it will be over as well.
> The Mobile2Market program is designed for "small" developers and signing
> isn't hard. If you want to work in this space, it's part of the cost of
> doing business.
Yes, you are right, I have a driver and it is signed.
But Frank just wanted to create a background process,
so I wanted to warn him about this extra cost.
John
.
- Follow-Ups:
- References:
- WM 5.0: how to automatically run a process in the background.
- From: Frank
- Re: WM 5.0: how to automatically run a process in the background.
- From: <ctacke/>
- Re: WM 5.0: how to automatically run a process in the background.
- From: John
- Re: WM 5.0: how to automatically run a process in the background.
- From: <ctacke/>
- WM 5.0: how to automatically run a process in the background.
- Prev by Date: Re: BitBlt in landscape mode
- Next by Date: Re: BitBlt in landscape mode
- Previous by thread: Re: WM 5.0: how to automatically run a process in the background.
- Next by thread: Re: WM 5.0: how to automatically run a process in the background.
- Index(es):
Relevant Pages
|
