Can't Install on Sansa e260 Using a Mac

[Sqary]

I'm trying to install on a Sansa e260 v1 using a Mac, and I can't get it to work (two different machines). The Utility correctly identifies the device, but I then have to manually set the mount point. When I then try to run the install, I get the following messages:

Could not open Sansa
Could not open Sansa
Searching for Sansa
Permission for disc access denied!
This is required to install the bootloader

I've searched the forums but could only find this problem for someone with a Windows machine, and the solution doesn't fit the Mac.

I also tried using sansapatcher, but on both machines it failed, and then the OS thought it was corrupted and would not let me run it again.

One final detail: The device was originally an e260R that was factory refurbished to an e260 (before I bought it).

Thanks for any help!

[saratoga]

Permission for disc access denied!

Are you running it at root? 

One final detail: The device was originally an e260R that was factory refurbished to an e260 (before I bought it).

If its an e260R, you have to go through the install process for that device. 

[Sqary]

I don't know what you mean by "running it at root" in the context of a Mac.

It isn't supposed to be an e260R anymore, and the installer doesn't detect it as that. It also has the MSC/MTP options for USB, which indicates it is not an R. However, I did wonder about that. The installer didn't seem to have an option for e260R--what should I do if I wanted to try that?

[saratoga]

I don't know what you mean by "running it at root" in the context of a Mac.

Check Google, it's been so long since I used osx I can barely remember it.

It isn't supposed to be an e260R anymore, and the installer doesn't detect it as that. It also has the MSC/MTP options for USB, which indicates it is not an R.

Then you're following the right instructions. The e200r has a more complex installation process.

[__builtin]

I don't know what you mean by "running it at root" in the context of a Mac.

I think saratoga meant to run it as the root user (the "superuser"). Try running the utility from a command line, prefixed with the "sudo" command.

[Sqary]

That did the trick--thank you! Perhaps the User Manual could reflect the need to run it that way.

[saratoga]

That did the trick--thank you! Perhaps the User Manual could reflect the need to run it that way.

This is actually in the user manual.