FWIMG01.DAT

[jscarney]

I ran into this same problem yesterday, checking the show hiden files folder option does not expose the files. However, you can do this instead...

In the path box of the windows explore show type F:/GBSYSTEM

it should show that folder.

make a copy of the entire GMSYSTEM folder and name it GBSYSTEM.ORIG

type F:/GBSYSTEM/FWIMG in the windows explorer path box

drop the new boot file into that directory and overwrite the old.

remeber you now have GBSYSTEM.ORIG if you want to restore the old stuff.

[sionnsar]

A newbie question before I dive in:

The directions say to rename FWIMG01.DAT to FWIMG01.DAT.ORIG (they're pretty specific about this name) -- my question is why?  I see two possibilities:

1. This is somehow recognized by the Gigabeat when it searches for FWIMG01.DAT, which isn't there.  (This is by an apparently missing step in the uninstall directions I read -- they didn't say to rename this file back.)

or

2.  It's critical for the dual-boot capability I just learned about by reading this thread.

[rosco_pc]

Hi Sionnsar,

This is to allow the bootloader to restore the original file. You do this by pressing 'volume +' when booting. This allows you to restart the GB with the original firmware when something goes wrong (very useful).

[sionnsar]

Thanks!  If that's in the startup message, I'll just note 5 (or so) seconds is not enough time to observe and respond.  

(IMHO some of the default values need to be tweaked towards "newbie" and away from "expert" -- speaking as a newbie.)

[Llorean]

That "message" contains debug information, not instructions. Instructions come in the manual.

As well, right now Rockbox isn't released, so it would be somewhat silly to adjust things away from "easy development" toward "easy use" until close to a release version.

[sionnsar]

Fair enough, Llorean.  Not that I have lots of time for it, but I'd like to provide input on / work on the Gigabeat manual -- sometimes the newbie sees things that the experienced / initial developers miss.  Where/how do I sign up?

[Llorean]

The simplest method is to just download a copy of the manual, and if you see sections that you feel could be changed for the better, offer either a patch (for the .tex sources of the manual) or a plaintext rewrite of the section on our patch tracker. Patches for the manual are treated the same as patches for the software itself. See the "patches" link on the left side of the page here.

[sionnsar]

Thanks, Llorean!  I'll be inputting changes.  Gosh, haven't been to SourceForge in a long time...

[Llorean]

We don't use sourceforge...

[sionnsar]

That's odd.  I am quite sure I read "use your sourceforge login" when looking around over there.  I'll have to check again when I have some proposed changes/additions.

[Llorean]

The "use your sourceforge login" was in regards to when we moved from sourceforge to our own tracker. If you'd posted previously on our tracker, you used the sourceforge login initially during the transition.