>>But what about DmReleaseResource? It does nothing now >>but in the future will I need my app to call this? > >Yes, you should call it. Great, then how? Right now I only keep a global PTR to the locked resource in memory; that's why the cleanup code calls MemPtrRecoverHandle(). Should I: a) Keep the HANDLE in a global as well b) Use some trick of the OS to determine the 'mocked' handle created to this locked, ROM-based resource? THanks, Alan (on behalf of Dan)
- Re: Flash Errors (REAL cause) Dan Hewins
- Re: Flash Errors (REAL cause) David Fedor
- Re: Flash Errors (REAL cause) Dan Hewins
- Re: Flash Errors (REAL cause) David Fedor
- Re: Flash Errors (REAL cause) Bob Ebert
- Re: Flash Errors (REAL cause) Alan Pinstein
- Re: Flash Errors (REAL cause) Bob Ebert
