http://discussion.brighthand.com/showthread.php?s=&threadid=121234

Q: I'm always running into the dreaded "Network Card not found" error message with my WM2003SE e80x... I can fix it by isabling Today plug-ins, but I do hope there's an easier way... (NOTE: please note that this blog post contains a generic overview of disabling/enabling SIP's too (and other tricks). That is, it's not only meant for Toshiba e80x users but anyone encountering Wi-Fi/BT memory shortage problems.) A: This has been a topical and often-asked question ever since WM2003SE + Widcom BT stack-enabled PDA's have surfaced - they have exactly the same problem (with the exception that the BT unit often refuses to start even when there're absolutely no Today plug-ins). The case is the same with the WM2003SE-upgraded e800, as far as its Wi-Fi unit is concerned. Unfortunately, as far as I know, it's impossible to enlarge the memory area available for the Today plug-in/system driver heap. It would definitely cure this problem; therefore, we have to play with the meager memory we have and try to "stuff in" as many drivers and Today plug-ins there as possible. First, if you have a Today launcher, I recommend this full-blown Today launcher roundup (alternatives: iPAQ HQ, AximSite, PPC Magazine, FirstLoox, BrightHand); I've also measured the runtime RAM needs of the tested Today plug-ins. If you check out the numeric RAM usage results, you see that you can, for example, have better results with, say, cLaunch or the Today plug-in of Resco Explorer than with, say, the much more memory-hungry Spb Pocket Plus or iLauncher. In addition to playing with Today plug-ins and disabling them one by one to find out which uses the most memory and trying to find a better, less memory-hungry alternative (and the traditional soft reset),

As I've done quite much work with custom word completion dictionaries (WCD for short), I've been writing quite much on this subject (see for example this and this blog entry/link collection to my other, related articles) and know the limitations of the current, default WCD model. This is why I was really delighted to see TextPlus for Windows Mobile 1.1 by SmartCell Technology – it, as it's independent of the built-in, really restricted Windows Mobile word completion dictionary model, really offers a lot.

This app is really good. I've played quite extensively with it and, so far, like it very much. It's so much better than the 9000 byte-restricted dyncompdict.dat-based built-in custom (user-creatable/-input-based) word completion dictionary.

Its documentation, dictionary creation-wise, is far from perfect, though – without a great deal of testing and discovery, it's not obvious how custom dictionaries should be created. The following is a quick course on how this should be done.