Hello, It's me again.
I have tested the Wi-Fi driver, and it doesn't appear to work. I suspect this may be because the install program for my card installs two windows "Services" provided by "Alpha Systems" or some such company. I had hoped that these were just "helpers" or were used to support the bundled connection software, but weren't need for the WZC interface of XP, but I don't know now. I would be happy to try to implement any ideas you may have, so you don't have to go and buy this card or something. I would be happy to provide any related information you might request as well. (BTW, to find the drivers, browse to: http://support.dlink.com/ and click the leftmost drop-down list and select "DWL", then on the right, select "G520". Note that is with an initial "G", and without a plus (+) at the end.) I used the .cat, and .inf, .sys, and .dll files that were provided in the .zip file on this site, and put them in the "pebuilder3.13/drivers/net/D-Link DWL-G520 folder". Upon booting up the CD however, my card was not detected.
I have a text printout of the "Unknown Devices" program provided on the CD, but I won't include it here. Let me know if there is someplace I can submit it.
One last thing: The same error message (and program crash) that occured on my brother's system, also appears to be happening on system for my built-in Nvidia N-Force2 wired ethernet device on my system. (Motherboard=ECS N2U400-A)
I wonder if you guys should open-up a special forum specifically made for submission of DeviceList.txt files created by the "Unknown Devices" app. That program gives all of the nitty-gritty info needed to track-down drivers for some of this stuff.
Another program of interest: Belarc Advisor. http://www.belarc.com/
This program "is free for personal, non-commercial use". Even if it is not re-distributable, someone could provide instructions for creating a plug-in for end-user inclusion and/or users could be asked to install it as a method of identifying certain hardware. This product actually only knows what windows knows, but it might come in handy for turning-up info on devices that the desktop OS knows about, but that don't work in PE/UBCD4Win.
I know, I'm incredably verbose, especially regarding computer stuff. In my defense: It is worse in person!
--Aaron