Please correct USB changing procedure

[rjalex]

Please correct me if I'm getting any of the following wrong.

Problem description: installed 3.13 on Fuze+ on my Mac, copied some music onto it and then gave it as a present to my son which has a Win7 computer. He sees no hard disk mounting. I guess it could be some USB mode difference between Mac OS and Win7. Would want to teach him how to switch to MSC USB mode to be sure he sees it.

Procedure: Hold left button while powering on to boot to OF, go to Settings->System setting and find a way to change USB mode to MSC. Turn off and power up again and you'll go back to Rockbox !

Is this correct ?

I'm asking since I can't try as he has the Fuze+ now.

Thanks in advance.

[toehser]

The original firmware MSC setting has _no_ effect on Rockbox.

Rockbox _only_ supports MSC mode, anyway.

Windows 7 and 8  people seem to be having problems.

Worth looking into, I guess, it is on my to-do list to see if I can replicate some of these issues with Windows 7 or 8 in a virtual machine.

More likely a Windows quirk than a Rockbox quirk, though who knows...

If he boots to original firmware (holding down "left" I think during boot), does Windows 7 see the drive then?  Or neither with RB _or_ Win?

[Alan P-Ten]

Installed Rockbox two days ago. I'm having the same issue.

I have a new Sansa Clip Zip firmware 01.01.21 and installed Rockbox 3.13 using a Windows XP SP2 desktop. (I also have iPod drivers (no iTunes) installed.)

Original Firmware: USB mode set to Automatic by default.  Windows recognizes the Sansa as a "Portable Media Device" without drive letter assignment.  Windows Media Player will sync to Sansa (although occasionally Windows won't recognize until a reinsert).

Installing Rockbox: Must set USB mode to MSC before install. (Took a couple hours to figure that out  )

I assume above is normal.

Boot to Rockbox: Appears to be random (no common pattern I can discern), sometimes my computer will not recognize the Sansa.  I must boot into the original firmware (USB has reverted back to Automatic) and must reset USB mode to MSC.  Only then will Sansa/Rockbox be recognized by the computer.

This appears counter to the "The original firmware MSC setting has _no_ effect on Rockbox."

Is there a USB mode setting in Rockbox that I'm missing?

I'll continue investigation to see if I see a pattern and will let you know what I uncover.  My old and flaky computer does seem to take an inordinate amount of time to assign a drive letter.  At the moment, boot to original firmware/USB Mode set procedure works and is only a minor annoyance.

[saratoga]

I must boot into the original firmware (USB has reverted back to Automatic) and must reset USB mode to MSC.  Only then will Sansa/Rockbox be recognized by the computer.

This appears counter to the "The original firmware MSC setting has _no_ effect on Rockbox."

If you're booting into the Sandisk firmware, then you are running the Sandisk firmware and not Rockbox.  Basically you're saying that when you run the Sandisk firmware, changing settings in the Sandisk firmware changes settings in the Sandisk firmware.  The quote above is saying something different, that changing settings in the Sandisk firmware won't change anything in rockbox, which is true.

I'll continue investigation to see if I see a pattern and will let you know what I uncover.  My old and flaky computer does seem to take an inordinate amount of time to assign a drive letter.  At the moment, boot to original firmware/USB Mode set procedure works and is only a minor annoyance.

USB is significantly more broken in 3.13 than the current build.  If you want to investigate this, at least update to the current build or no one is going to care about what you find.

[Alan P-Ten]

Thanks for the quick reply.

My mistake.  I associated the Sansa firmware USB setting with Windows assignment of a drive letter.  Further testing, shows that the unplug and reinsertion process appears to make the difference. (That and the patience to wait long enough for Windows to get it's act together.)

I used the latest release 3.13 because I assumed that the dev build was not ready for general release (aka unstable).  But if your recommendation is to load the dev build, then I'm willing to provide user feedback.