Rockbox Technical Forums

Installation / Removal => Manual Installation => Sandisk - Installation/Removal => Topic started by: burlycoots on June 24, 2009, 10:51:34 AM

Title: 250r "No rockbox directory, installation incomplete"
Post by: burlycoots on June 24, 2009, 10:51:34 AM
After installing on a Sansa Rhapsody, all appeared well except for the error message "No rockbox directory, installation incomplete".

I've found this post, but it does not seem clear to me: http://forums.rockbox.org/index.php?topic=15731.0
That is, what is ./rockbox a reference to?

What is confusing in the original directions is this:
9.  Download a recent Sansa e200 build of Rockbox from here and unzip it to the root of your device

Am I to unzip the 251 files right into the root directory of my player, or am I to make a rockbox directory in the root and put the files in there?

I've tried making a rockbox directory in the root of my player and dumping the files there, but had to use recovery mode after the device refused to start up.  Restoration was smooth, back to original with no issues.


Currently after another installation attempt, Rockbox will partially load, but I cannot really do anything; cannot play songs, says my database is empty, etc.  Same error message, No rockbox directory, installation incomplete.

I've followed all directions special to the R model with patching the bootloader and have had no issues.  Everything went as instructed except for step 9 which is unclear to me.  I've tried grabbing the files directly from WinZip (On XP) vs. unzipping them to a folder on my desktop and dropping them.  Same result in either case.

Well, I feel dumb I found the answer to my own question.  Winzip wasn't showing my the whole folder structure, so I used 7-zip instead.  Showed the .rockbox directory which I dumped in the root and all is well.

Maybe someone else will find this useful.
Title: Re: 250r "No rockbox directory, installation incomplete"
Post by: LambdaCalculus on June 24, 2009, 11:04:09 AM
I've found this post, but it does not seem clear to me: http://forums.rockbox.org/index.php?topic=15731.0
That is, what is ./rockbox a reference to?

That's actually an incorrect reference; the folder should be /.rockbox (with / indicating the root folder and .rockbox being the folder name proper). The folder requires the . at the beginning.

Quote
What is confusing in the original directions is this:
9.  Download a recent Sansa e200 build of Rockbox from here and unzip it to the root of your device

Am I to unzip the 251 files right into the root directory of my player, or am I to make a rockbox directory in the root and put the files in there?

Yes, simply extract the zip file into the root of your device's storage. You should have a .rockbox folder in the end, with everything inside of it. After that, Rockbox should load correctly.
Title: Re: 250r "No rockbox directory, installation incomplete"
Post by: cloudycloud on July 22, 2009, 01:22:36 PM
I was having the same difficulty but I was able to 'read between the lines'.

What doesn't seem to be working is make the period in front of the rockbox folder name.

I tried extracting the folder to my desktop and then moving it.
it removed the leading period, it wouldn't let me rename it WITH the leading period

I tried extracting directly to the sansa e250r drive root level.
it removed the leading period, it wouldn't let me rename it WITH the leading period

I tried extracting directly to the removable disk drive
didn't like this at all.

I running windows XP sp3.

what can I do?
NEVER MIND


Downloaded and used Rockbox Installer
it fixed everything and all is working fine now.

Thank you.
Title: Re: 250r "No rockbox directory, installation incomplete"
Post by: Chronon on July 23, 2009, 01:52:11 AM
cloudycloud, I'm glad that Rockbox Utility fixed your problem for you.  This is one reason that we encourage people to use it for installing new builds.  Archiving applications don't all behave uniformly.  Some rename folders or place them in new, unwanted ones. 

By the way, you can rename a folder to begin with "." from the cmd shell.