Re: bootloader correction needed

ian douglas wrote: I just don't want to try flashing a 4MB firmware file if it's going to kill my H320, I've got a 90 minute commute ahead of me... :o) Then don't try it. You will be the first to patch 1.04 with Rockbox. Linus

Re: bootloader correction needed

Hi ian, the 4 MB scrambled file is fine. I had that too. the discriminator parameter to scramble.exe to specify the device is simply "-iriver". I think all irivers (with rockbox up to now) have the same scrambeling. To be drop-dead-sure, you should compare the md5 checksum. That's what it's made

Re: bootloader correction needed

Don't mind my little conversation with myself ... I'm really not schizophrenic or anything. Just making notes on what I'm trying, hopefully someone can spot my mistake. $ tools/mkboot -h300 H300-104.bin bootloader-h300.bin H300-104-rockbox.bin Wrote 0x3fcfd7 bytes in H300-104-rockbox.bin $ ls -

Re: bootloader correction needed

Okay, grabbed the latest mkboot.c and that worked ... now when I re-scramble the .bin I created it comes out at 4MB, is that right? I would have thought it'd compact back to a ~2MB firmware file? -- Ian Douglas blogs & photos: http://www.w98.us/ ian douglas wrote: http://www.rockbox.org/twiki

bootloader correction needed

http://www.rockbox.org/twiki/bin/view/Main/IriverBoot says that I need to run mkboot as such to patch the firmware: # tools/mkboot -h300 H300.bin bootloader/bootloader.bin new.bin When I try that, I get this: $ tools/mkboot -h300 H300.bin bootloader-h300.bin H300.bin -h300: No such file or dir

IRiver crashes :(

Hi, I have had my iriver H140 crash twice today, both times on selecting a new tune (the loading box is still up when it bombs). Both times I was near the end of one track, and used the remote to select a second track. I Cant be too specific about the version I had on before that worked, but one

Re: Odd button behaviour (new info)

On 12/8/05, Ronald Teune <[EMAIL PROTECTED]> wrote: > On Wed, 07 Dec 2005 23:49:40 +0100, Jens Arnold <[EMAIL PROTECTED]> > wrote: > > The OFF button is one of the two buttons that are not connected > And what's the other button? It seems to happen more often after an "ON" > press than after a pres

Re: Odd button behaviour (new info)

On Wed, 07 Dec 2005 23:49:40 +0100, Jens Arnold <[EMAIL PROTECTED]> wrote: On 07.12.2005, Jerry Van Baren wrote: My suggestion is to check for changes to the button voltage conversion levels in button.c: Than

Re: Simplified and uniform volume handling - asking for opinions

On 12/8/05, [IDC]Dragon <[EMAIL PROTECTED]> wrote: > > I don't think I've ever seen any audio playback equipment of any kind > > offer clipping prevention. > > Haha, I just envision how odd it would be if my amp would start turning > other knobs as I crank up the volume... lol. That's a good one.

Re: Simplified and uniform volume handling - asking for opinions

> I don't think I've ever seen any audio playback equipment of any kind > offer clipping prevention. Haha, I just envision how odd it would be if my amp would start turning other knobs as I crank up the volume... Jörg -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Sat

Re: Simplified and uniform volume handling - asking for opinions

On 08.12.2005, Magnus Holmgren wrote: >> My patch removes clipping prevention altogether (like we had >> it on Archos Recorders & Ondios for years, btw). > And makes fade on stop pretty ugly (sounds get chopped rather > than change smoothly), it seems... :) Oooops, that's a bug. I forgot to adju