@jaclaz Well done and thanks for the spreadsheet... I guess your batch file will probably be even more useful in the future. I also noticed that link, and usb.if reminded me of a .csv file, too. But I had no clue, why "1516" was untraceable in it, so I regarded it as useless due to its mysterious format . Today I had a conversation with CnMemory's support. I thought it would perhaps be useful for Maximus' NUSB, if I could figure out the PIDs of the other three Skymedi/CnMemory USB sticks (512MB, 2GB, 4GB), so the whole "Core" product line could be supported by NUSB, not only the 1GB version. The employee I had on the phone claimed that he had successfully tested all four "Core" sticks (512MB, 1GB, 2GB and 4GB) in conjunction with Windows 98 SE and NUSB24/NUSB30... As I confirmed, that it had not worked for me, he said it would sometimes also depend on ones USB controller, respectively its driver. I cannot deny that, since I am still using an old VIA USB 1.1 Controller (+VIA Hyperion 4.47 +USB 1.1 Filter Patch 1.10 and otherwise it is working fine). But he also told that CnMemory's "Core" sticks are inconsistently equipped with chips from three different manufacturers . What a mess . That means the sticks he had tested might possibly be essentially different from mine, although all belong to the same product line. So no conclusion is possible at all. I don't want to test the latest VIA Hyperion Drivers, since VIA themselves do not recommend them for Windows 98 machines and older chipsets ( http://www.viaarena.com/default.aspx?PageI...&CatID=1110 ). Also, I actually don't need a USB 2.0 controller at the moment (except for testing). So if here is somebody, who has a stick with a VID_1516 and a PID_8628 (can be found within Win 98 SE's registry, after it was once successfully attached) and had it working with Windows 98 SE and NUSB24 (or prior) without any additional entries in usbstor.inf: SHOUT. These sticks are most likely concerned: 1) CnMemory "Core" line, 2) ValGear "GXT" line. Pirates