Re: VirtualAlloc generates Undefined Instruction exception

1) NEVER change the common code, ALWAYS clone it before modifying it.
2) Don't use VirtualAlloc directly unless you absolutely have no other
option (That would be a truly exceptionally rare case)
3) It's likely that code is being called before it is safe to call
VirtualAlloc, you, therefore, need to create static mapping entries in
OEMAddressTable and access the device via it's uncached static mapped
address.

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com


.

Relevant Pages

  • Re: How to make new vbridge.lib after modifying vbridge.c?
    ... NEVER CHANGE THE MS COMMON CODE IN PLACE - It's a disaster waiting to ... happen that will hit you at the worst possible time ... Clone the code into your BSP or project. ... smaillet at EmbeddedFusion dot com ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Where are COMMON DLLs placed?
    ... you shouldn't mod the common code. ... you can run build -c in the folder you modified to generate the lib file ... where <public project name> is the folder name of the subdir of PUBLIC you ... the actual module you are modifying. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Check R/W time CF card at Driver
    ... Key word there is CLONE. ... NEVER modify the MS common code in place. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: how can i build platform common/public libs without clean before build?
    ... Steve's golden rule of Windows CE development #1: ... If you need a modified version CLONE it first. ... smaillet at EmbeddedFusion dot com ...
    (microsoft.public.windowsce.platbuilder)
  • Re: IDE Disk initial Failed!
    ... We should probably make clear that modifying the COMMON code in-place isn't ... Copy it and create your own special driver for the ... Paul T. ...
    (microsoft.public.windowsce.platbuilder)