I have my suspicions about the cause of this. I think it is related to the byte swapping algorithm and packet size adjustments required by it. I will address this issue as soon as I have the time. This could also be causing issues seen by x86 users trying to use puppy on Linux 2.6 desktops.
There have been a few other internal changes to some of the USB protocol handling. In particular, the protocol packet size constraints are now easier to follow and will actually cause an error, rather than issuing a command with truncated payload. This is unlikely to affect any legitimate use, since the check will only come into effect if the combined length of all command arguments in a packet reaches about 64kB.
Puppy is approaching a 1.1 release. Once the rename bug is sorted out, puppy will be tagged as
PUPPY_1_1and a new beta package will be pushed.