Paul,
My m$ wireless USB mouse worked fine before but I applied your change anyway just to confirm your excellent work. So it was no surprise to me that the mouse worked just fine after rebooting.
However, knowing what can happen if I ASSUME that the change took effect, I proceeded to verify that the present version of /etc/rc.d/rc.local0 indeed contained your change at line 192 ... YES ... it did !!!

For those wishing to test both USB keyboard and USB mouse detection using the Class/Subclass/Protocol method, I have added a second modified rc.local0 file as an attachment to the first post in this thread.

Just remastered a CD and I'm calling my friend in a couple minutes. I'll give you a post back after the "zboard" test.

I did just test a Dynex USB mouse that I have. It works great with the new method.

Will this stuff "plug-n-play" after it's all tested? i noticed it didn't just get recognized when I plugged it in, but only when it's booted. Does puppy have some type of loop somewhere or event that can load up drivers when USB connections are made? Maybe even a Load USB Devices button in the Wizards menu would be sufficient if the other option isn't available.

I switched to Puppy 2.12 recently. I was confused in problem with my USB mouse in it. using your tweaks I resolved It. I switched to Puppy 2.12 recently. I was confused in problem with my USB mouse in it. Using your tweaks I resolved it. Further I had a problem with it's detection,some power supply was laking in it. Then severally it was happened that mouse can't not work for a while & then it start working._________________Where there is will there is way.