Unless I'm completely off my rocker, I thought I had seen that usbprinter.device or class?
Not
completely off your rocker
I'm guessing you saw usbprinter.class, which in turn creates usbprinter.device in memory.
Back to the original problem, the only thing I can really think of is somehow grabbing the region of memory that the device is loaded into. Scout can probably help identify regions, but the whole process might be easier under emulation.
Not sure why you'd want to do this though. If the problem is that a program/utility needs a device name but insists on a disk-based file, there are workarounds, usually involving hex-editing a config file. Works for Envoy
