Regarding the support of USB devices: it seems like the compatibility problem with Kingston devices is no longer restricted to Kingston devices, as the chipset used in my new Toshiba 16GB USB disk appears to have been also used in a Kingston 16GB disk. This Toshiba 16GB disk seems to be having the same problems as Kingston devices: writing anything to it may corrupt the disk. I have also managed to once observe reading fail, so it could be a sign that data is not being transferred properly between the PS2 and the USB device. The activity indicator LED is also always seen blinking, even if nothing is accessing the USB disk (i.e. when uLaunchELF is left alone). With older revisions of USBHDFSD (prior to any of my modifications in 2014), the problem seems to (although it is known to be there) be non-existent. But ever since I modified fat_WriteFile() to not read sectors that would have their content entirely replaced, the problem seems to be occurring more requently. The change was made, for better performance. So for best reliability, perhaps it would be best to avoid such devices. This does not only apply to POPStarter, but to any piece of homebrew software that supports USB Mass Storage Devices.