Unfortunately,I'm still where I was when I wrote my June 3rd post. I've reviewed the potential solutions, made changes to power settings, adjusted minimum volume level to 50, changed USB cable (was, and still is a single 6' cable), changed the power cable,
although a "special" cable which I have a couple extras, and also changed the power source/outlet from my UPS to straight wall-power per Bose recommendation. Nothing has helped. When booted, the first sound wav file played is clear, the second a bit distorted,
and from there, the quality just deteriorates and cuts out completely within 15 seconds of playing test sounds via Sounds/Playback. If I disable the sound, I can come back hours later, enble the sound, and it will work as described at boot time. In other words,
the sound doesn't "logically" deteriorate until sound is actually played on the Bose. I've found only two methods of recovery. Either power-cycle the Bose, waiting ~30 seconds between removal of power, and plugging back in; or rebooting Win-7 Pro. Either will
work without the other. The important piece of this puzzle is that the sound worked PERFECTLY when running Vista 64-bit Home Premium. At one point, I had both the Vista system disk installed, and the separate Win-7 Pro system disk. I could easily switch back
and forth. The Bose consistently was solid on the Vista OS, but consistently failed on the Win-7 Pro OS. That one change of switching OS's was all it took to make, or break the Bose. Unfortunately, I've since overwritten the Vista OS disk. Perhaps it used
a driver that I could have migrated to Win-7 Pro. Also, if I use the puck on the Bose, and use a headset, the sound is fine. Go figure.
At this time, I do not have my headset to try the experiment stated in the above post, although what I did with the headphones earlier on accomplishes the same thing. I don't believe that the Bose is going to sleep itself. When the sound just degrades
from the start to a point where it cuts out, it almost indicates a bus contention problem. With the Bose being its own USB Composite Device, per the Device Manager, and NOT under a root hub as originally configured at build time, there's nothing left to compete
for the bus.
Bottom line is that all is the same since my June post.