PocketMatrix

Tell him to do do a hard reset and back up his data. In that order.


Seriously though, just have him back up his data and hard reset. It can't be a device issue, because like you said it worked on your beta testers device. He or some other program has messed something up in the OS or something. Hell, ask him if he even has tried a soft reset. Also ask him if his 16MB of data is allocated to storage memory or program memory.

Have him checksum the file, perhaps it's getting corrupted? This happened to me, no matter how many times I downloaded it from how many people, the file would always come out with the wrong checksum, and thus be corrupted. I ended up downloading the file onto my Linux box, and doing everything on there.

Read the section in this article about DLL load order on Pocket PCs.

Why don't you call GetLastError after LoadLibrary fails to determine why it failed?

Dan East

Digby, the second sentence in that document contains the word "leverage" used as a verb. That tired, cliché word has been so overused in corporate techno-babble that the mere glimpse of it makes me nauseous.

You know, the other day while at the grocery store I overhead the person in front of me checking out. The cashier said "That comes to $7.95, how would you like to leverage funds against that?" The customer replied "I'm going to leverage my bank card today. Oh, and please leverage paper packaging material against my purchases." Yep, I hear the word "leverage" used every friggin day in the real world.

Sorry, just had to get that out.

Dan East

Heh... yeah, exactly what a technical article about OS internal architecture needs - more marketing babble.

Lots of similarly humorous blather .

Hmm. Are you loading the dll more than once? That may result in an ERROR_ALREADY_EXISTS error.

Dan East

No, I'm only calling LoadLibrary once.

That's odd. Try creating a test app that only loads that DLL and does nothing else, and let that user give it a try.

Dan East