--- Log for 29.06.104  Server: kornbluth.freenode.net  Channel: #rockbox
--- Nick: logbot_  Version: Dancer V4.16p1  Started: 1 month and 14 days ago

00.03.10 Quit    d4nGeRoUs (Read error: 110 (Connection timed out))
00.09.17 ***     Saving seen data "./dancer.seen"
00.49.20 #       <midk> hey amiconn, are you around?
00.49.30 #       <amiconn> Yups
00.49.45 #       <midk> you suggested the european date mode for the clock, correct?
00.49.52 #       <midk> which was DD.MM.YYYY?
00.50.15 #       <amiconn> yes, correct.
00.50.35 #       <midk> is it still a "correct" european date if it's DD.MM.YY?
00.50.59 #       <midk> or is DD.MM.YYYY more correct?
00.51.16 #       <amiconn> Yes it is (short date), although I don't like it (personally)
00.51.32 #       <midk> what about on two lines
00.51.34 #       <midk> DD.MM
00.51.35 #       <midk> YYYY
00.51.52 #       <midk> that is the best way i can make it work in the clock
00.51.53 #       <amiconn> Should be ok.
00.51.58 #       <midk> excellent, thanks
00.55.56 #       <midk> dammit. i hate these bugs.
00.56.13 #       <midk> 24h time readout: 31:57:49
00.56.33 #       <amiconn> funny...
00.57.00 #       <midk> and
00.57.04 #       <amiconn> Btw: your old clock doesn't show the seconds correctly since I fixed snprintf()
00.57.06 #       <midk> 12 is 19:57:xx
00.57.18 #       <midk> yes, i am releasing the final update today..
00.57.27 #       <midk> if i can fix this bug
00.57.53 #       <amiconn> Please define "today" ... damn time zones
00.58.06 #       <midk> umm
00.58.11 #       <midk> within the next 6 hours probably
00.58.24 #       <midk> up to 8 hours.. that's when i start getting sloppy :)
01.05.40 #       <midk> FXIED
01.05.42 #       <midk> fixed*
01.05.45 #       <midk> AHAHAHAHa i am good.
01.07.31 Nick    midk is now known as qwm2 (~Zakk@c66-235-14-120.sea2.cablespeed.com)
01.08.07 Nick    qwm2 is now known as qwm (~Zakk@c66-235-14-120.sea2.cablespeed.com)
01.08.18 Nick    qwm is now known as midk (~Zakk@c66-235-14-120.sea2.cablespeed.com)
01.22.56 Join    Nibbler [0] (nibbler@port-212-202-73-96.dynamic.qsc.de)
02.03.27 Part    amiconn
02.03.28 Quit    Nibbler (Read error: 104 (Connection reset by peer))
02.09.18 ***     Saving seen data "./dancer.seen"
02.11.32 Join    xam [0] (~xam@beast.ipv6.t.la)
02.49.52 Nick    AciD is now known as AciD` (~acid@longchamp44-1-82-67-133-87.fbx.proxad.net)
02.55.42 Join    yeft [0] (nospinzone@pcp08615553pcs.benslm01.pa.comcast.net)
02.55.47 #       <yeft> oh dear...
02.55.52 #       <yeft> anyone here
02.57.16 #       <midk> m
02.57.17 #       <midk> e
02.57.20 #       <midk> the GRAMMAR BOT
02.57.32 #       <yeft> hahah i got a soldering iron
02.57.34 #       <yeft> and i soldered
02.57.41 #       <yeft> and i dont think it worked
03.05.27 #       <midk> don't*
03.05.28 Quit    yeft (Read error: 104 (Connection reset by peer))
03.21.55 #       <midk> any coders around?
03.46.31 #       <hardeep> coding gives you cancer
03.46.44 #       <midk> darn - i must be dead :)
03.47.08 Join    Nibbler [0] (nibbler@port-212-202-73-96.dynamic.qsc.de)
03.47.24 Quit    AciD` ("Segmentation fault (core dumped)")
03.55.47 Part    xam
04.09.22 ***     Saving seen data "./dancer.seen"
04.26.07 Quit    hardeep ("[BX] Reserve your copy of BitchX-1.0c19 for the Sony Playstation today!")
04.47.59 Quit    Nibbler (Read error: 104 (Connection reset by peer))
06.03.37 Join    midknight2k3 [0] (~Zakk@c66-235-14-120.sea2.cablespeed.com)
06.03.57 Quit    midk (Nick collision from services.)
06.03.58 Nick    midknight2k3 is now known as midk (~Zakk@c66-235-14-120.sea2.cablespeed.com)
06.04.14 Join    midknight2k3 [0] (~Zakk@c66-235-14-120.sea2.cablespeed.com)
06.09.25 ***     Saving seen data "./dancer.seen"
06.16.06 #       <midk> wtf.
06.16.09 Quit    midknight2k3 ("just STOP it arspy")
06.16.15 #       <midk> oh lol
06.26.13 Join    Nibbler [0] (nibbler@port-212-202-73-96.dynamic.qsc.de)
06.53.29 Join    LinusN [200] (~linus@labb.contactor.se)
06.54.40 #       <midk> heya linux
06.54.42 #       <midk> GAH
06.54.44 #       <midk> LinusN.
06.55.25 #       <LinusN> yo
06.56.15 #       <midk> working on a very intuitive help screen.
06.56.24 #       <midk> then, *rubs hands together*, my CLOCK WILL BE COMPLETE
07.01.45 #       <LinusN> you've been saying that for the last 4 months :-)
07.01.55 #       <midk> i said before july :D
07.02.37 #       <midk> yay my help screen will rock.
07.02.51 #       <midk> sure, they have to go through a few paragraphs on a small lcd.. but who cares
07.02.53 #       <midk> it's just the USER.
07.03.16 #       <midk> wow.. just text displaying is expanding my clock significantly
07.04.09 #       <midk> tacking on 40 lines of text bumped it from 17.7kb to 18.5kb.
07.04.13 #       <midk> D:
07.04.20 #       <midk> sounds sort of weird..
07.06.44 #       <midk> *decides not to include a "how to read binary" tutorial
07.14.25 Quit    elinenbe (" Like VS.net's GUI?  Then try HydraIRC -> http://www.hydrairc.com <-")
07.33.49 Quit    Nibbler (Read error: 104 (Connection reset by peer))
07.35.59 Join    yeft [0] (nospinzone@pcp08615553pcs.benslm01.pa.comcast.net)
07.36.11 #       <yeft> ok
07.36.19 #       <yeft> my fmr is in front of me
07.36.22 #       <yeft> and in pieces
07.36.25 #       <yeft> and im desparate
07.36.29 #       <yeft> deperate
07.36.41 #       <yeft> my first soldering attempt failed...
07.37.30 #       <midk> desperate*
07.37.40 #       <yeft> i fixed it
07.37.44 #       <yeft> and not in the mood hahaha
07.37.45 #       <midk> deperate?
07.37.45 #       <midk> no.
07.37.50 #       <yeft> oh
07.37.53 #       <yeft> damnitttt
07.37.58 #       <midk> damnit*
07.38.05 #       <midk> sorry yeft, no more from grammarbot.
07.38.37 #       <LinusN> yeft: what are you soldering?
07.39.00 #       <yeft> the luggs
07.39.06 #       <yeft> the tabs conencted to the pcb
07.39.13 #       <LinusN> shouldn't be too hard
07.39.36 #       <yeft> it isnt...
07.39.38 #       <yeft> but it didnt work
07.39.39 #       <yeft> hahha
07.39.56 #       <LinusN> can you see if the battery connectors make good contact to the battery?
07.40.44 #       <LinusN> if not, bend them slightly towards the battery
07.41.01 #       <yeft> ok
07.41.04 #       <LinusN> and clean them, and the battery
07.41.27 #       <yeft> with...
07.42.27 #       <LinusN> some alcohol, maybe
07.42.47 #       <yeft> haha soap wont do?
07.42.53 #       <LinusN> hehe, no
07.44.11 #       <midk> *watches yeft use soap anyways
07.44.11 #       <midk> LD
07.44.14 #       <midk> ;D*
07.45.11 #       <yeft> ahaha
07.45.11 #       <midk> LinusN, clock.c has moved into its last 100 builds. 
07.45.12 #       <yeft> ok
07.45.14 #       <midk> what a touching moment.
07.45.32 #       <yeft> ok...cleaned
07.46.45 #       <LinusN> make sure that both battery connectors make contact
07.47.36 #       <LinusN> did you figure out how to put the battery lid back on?
07.47.59 #       <yeft> battery lid?
07.48.23 #       <yeft> oh yeah that bar...
07.48.33 #       <LinusN> that "bar" is vital
07.48.44 #       <yeft> yes i have it ,,,
07.50.00 #       <yeft> both make contact
07.50.08 #       <yeft> and i have the lid, and cna put it back on
07.50.44 #       <LinusN> and it still doesn't work?
07.53.25 Join    yeft2 [0] (nospinzone@pcp08615553pcs.benslm01.pa.comcast.net)
07.53.25 Quit    yeft (Read error: 104 (Connection reset by peer))
07.53.28 #       <yeft2> grr?
07.53.30 #       <yeft2> ok
07.53.32 #       <yeft2> umm
07.53.41 #       <yeft2> do i have to resolder to see if it works?
07.53.54 #       <LinusN> yes
07.54.16 #       <yeft2> : /
07.55.39 #       <midk> boohoooooo
07.55.41 #       <midk> i mean
07.55.42 #       <midk> good luck
07.55.52 #       <midk> i never really resoldered my points on my old fm
07.57.36 #       <LinusN> old fm? you have a new one?
07.57.50 #       <midk> no, i have no more fm
07.57.56 #       <midk> on the fm i used to have.
07.58.01 #       <yeft2> what do you have now?
07.58.05 #       <midk> rec15
07.58.20 #       <midk> woohoo i am like finished coding
07.58.23 #       <midk> now for the boring part
07.58.25 #       <midk> TESTING it.
07.58.40 #       <yeft2> ok
07.58.47 #       <yeft2> im assuming 15 watts
07.59.04 #       <midk> ?
07.59.08 #       <midk> was that directed at me?
07.59.10 #       <yeft2> soldering iron
07.59.17 #       <midk> ohk
07.59.19 #       <yeft2> it was directed to the room
07.59.25 #       <midk> ...why...
07.59.33 #       <midk> well why would i know
07.59.37 #       <midk> i'm just the GRAMMAR BOT
07.59.38 #       <yeft2> cause anyone can input
08.00.15 #       <midk> hm LinusN, will you pretend to be an end user and betatest my clock?
08.00.19 #       <midk> :))
08.00.36 #       <LinusN> upload it to the patch tracker
08.01.34 #       <midk> just a moment
08.01.40 #       <midk> i think i will add in some default values
08.01.55 #       <midk> if there is no settings file or there is an old settings file it just sort of picks random settings
08.02.02 #       <midk> lol
08.05.23 #       <yeft2> heheh it loaded
08.05.27 #       <yeft2> but thats happened before
08.05.28 #       <midk> works??
08.05.30 #       <midk> oh.
08.05.39 #       <yeft2> and then ive put it back together ..and pooooooo
08.09.29 ***     Saving seen data "./dancer.seen"
08.10.37 #       <yeft2> see now its all back together and i cant get past the first rockbox screen
08.11.35 #       <yeft2> remind me to start the archos hate club, once i stop buying their products
08.11.46 #       <midk> hahahahahahahahaha. ha.
08.12.34 #       <LinusN> yeft2: are you sure you don't have a short to ground somewhere?
08.13.14 #       <yeft2> ahhahah...and in yeft terms
08.13.15 #       <LinusN> for example, does it work without the cover?
08.13.20 #       <yeft2> yes
08.13.26 #       <yeft2> well it did
08.14.13 #       <midk> YES
08.14.17 #       <midk> my reset_settings function WORKS
08.14.18 #       <midk> HA.
08.14.23 #       <midk> that will teach you.
08.14.24 #       <yeft2> haha it works better without the cover, i get the back light
08.16.21 #       <LinusN> interesting, the fm recorder has a much lower headphone amplification, haven't noticed that until now...
08.16.43 #       <yeft2> IO4:illinstr
08.16.48 #       <yeft2> at 5400000000000000000
08.17.14 #       <yeft2> hahah im typn with my left hand holding the cover on the battery
08.17.28 #       <midk> tape it.
08.18.00 #       <yeft2> your assuming i have tap
08.18.02 #       <yeft2> tape
08.18.05 #       <midk> you don't?
08.18.08 #       <midk> *stares
08.18.09 #       <yeft2> haha i do
08.18.13 #       <midk> oh lol
08.18.52 #       <LinusN> yeft2: the chassis should not make contact with the edges of the pcb
08.19.14 #       <yeft2> ...
08.19.16 #       <yeft2> ohh
08.19.32 #       <LinusN> only the tabs should make contact to their respective pad
08.19.35 #       <yeft2> ohh got lots of pretty error messages
08.19.50 #       <yeft2> thats a lot better...
08.20.08 #       <yeft2> hey what if i use tape...to border the chasis and the pcb
08.20.31 #       <LinusN> sure
08.23.23 #       <yeft2> oh my word
08.23.28 #       <yeft2> its alive!!!
08.23.59 #       <yeft2> and its dead
08.24.21 #       <LinusN> praise the lord! :-)
08.25.15 #       <dwihno> Praise pepsi!
08.25.23 #       <LinusN> you should be able to find a pressure sensitive spot on the pcb
08.26.18 #       <yeft2> ?
08.26.27 #       <midk> PRESS THINGS
08.26.28 #       <midk> UNTIL IT WORKS
08.26.56 #       <yeft2> hehehe were back to the original error message!
08.27.11 #       <midk> YAYAYAYAYAYAYAYA
08.27.23 #       <LinusN> btw, look closely at the solder pads to see if any of them are loose
08.28.11 #       <LinusN> my fm had a solder pad that was broken off the PCB
08.28.22 #       <yeft2> ...oh...
08.28.25 #       <LinusN> (after my not-so-mild treatment)
08.28.33 #       <midk> LOL
08.28.43 #       <midk> did you fix it LinusN?
08.28.50 #       <LinusN> disassembled it quite a lot back then
08.28.53 #       <LinusN> yes i fixed it
08.29.04 #       <midk> yay.
08.29.21 #       <LinusN> had to replace all the radio wires as well :-)
08.29.26 #       <midk> really?
08.29.48 #       <midk> i'd have to consider your actions 'molestation' in that case :)
08.29.48 #       <LinusN> the insulation melted when i unsoldered the top cover of the radio
08.30.07 #       <LinusN> that cover was a bitch to remove
08.30.11 #       <yeft2> where is the radio
08.30.19 #       <midk> oh, the golden cover?
08.30.25 #       <LinusN> it's inside, below the lcd
08.30.28 #       <LinusN> yes
08.30.29 #       <midk> i recall it gold.
08.30.47 #       <midk> linusn is an FMR molester!
08.30.49 #       <midk> *posts to the list
08.30.50 #       <LinusN> indeed
08.31.04 #       <midk> yeft2, your fm is not safe.
08.31.28 #       <LinusN> well, my fm still works :-)
08.31.30 #       <yeft2> my fm is about alive as the pope
08.31.43 #       <LinusN> oh, that dead, eh?
08.31.51 #       <midk> LinusN, who's to say you won't take your escapades further on unknowing yeft2's poor fm?
08.32.28 #       <yeft2> and then it becomes necrofelia
08.32.29 #       <midk> AHA!! I HAVE SPOTTED ONE MINOR COSMETIC ERROR!!
08.32.48 #       <LinusN> midk: face it, you will never finish the clock plugin
08.32.56 #       <midk> *jumps on the code
08.32.59 #       <midk> AHAHA!!! I HAVE FIXED IT!!!
08.33.02 #       <midk> linusn...
08.33.14 #       <midk> hmm
08.33.19 #       <midk> i think my checkboxes are a bit too wide?
08.33.25 #       <midk> *taps fingers momentarily
08.33.38 #       <midk> or maybe i should do away with the mode selector.. :D
08.33.42 #       <yeft2> i shoulda taken newmp3technology up on their offer when they offered like 50 bucks for the thing
08.33.51 #       <midk> OMG
08.34.00 #       <midk> COSMETIC ERROR!!!!
08.34.04 #       <midk> *jumps on the code
08.34.27 #       <yeft2> so how much is my harddrive worth any of you
08.34.45 #       <midk> *offers $10
08.34.50 #       <midk> yeft2> sold!!
08.34.59 #       <midk> excellent, i will email you details on address
08.35.19 #       <midk> you pay shipping.
08.35.41 #       <yeft2> oh jeez
08.36.08 #       <yeft2> ill package you...a 20 and a 6
08.36.13 #       <yeft2> howse that sound
08.36.19 #       <midk> ooooh
08.36.27 #       <midk> $5
08.36.30 #       <midk> yeft2> sold!
08.36.36 #       <midk> yay... 
08.36.38 #       <yeft2> who can guess what genius manufacturing company landed me witha 20gb and a 6gb harddrive???
08.36.40 #       <LinusN> yeft2: quitter!
08.36.49 #       <yeft2> i am!
08.36.50 #       <midk> HA LINUSN CALLED YOU A QUITTER
08.36.53 #       <midk> yeft
08.36.59 #       <midk> ship it to me i'll fix it for ya.
08.37.07 #       <yeft2> hahah ... will ya now?
08.37.14 #       <yeft2> youll make fun of what it looks like...haha
08.37.15 #       <midk> we haven't yet defined 'fix'
08.37.16 #       <yeft2> its a mess
08.37.17 #       <midk> but yes,
08.37.32 #       <midk> let's see a photo,.
08.37.37 #       <yeft2> hahah ok 1 sec
08.37.40 #       <midk> yayyy
08.37.54 #       <midk> you know what ..
08.37.59 #       <midk> i am going to create a bullet time archos,.
08.38.09 #       <midk> with an ipod shooting at it
08.38.12 #       <midk> AHAHHAHAHa. ha.
08.39.27 #       <yeft2> it looks normal in the pic
08.39.27 #       <midk> ok LinusN, if i haven't mentioned that i have uploaded my clock within about 20 minutes, let me know.
08.39.30 #       <midk> Hadaka, sure.
08.39.38 #       <midk> oops.
08.39.41 #       <midk> ha , sure.
08.41.40 #       <LinusN> yeft2: given up on repairing it?
08.41.51 #       <yeft2> basically yes
08.41.58 #       <LinusN> come on...
08.42.12 #       <midk> he's a quitter.
08.42.35 #       <yeft2> bahaha
08.42.41 #       <midk> dern. my counter is a bit slow...
08.42.48 #       <yeft2> ok
08.42.50 #       <midk> i wonder if anyone notices
08.42.52 #       <yeft2> i wont quit
08.43.04 #       <yeft2> if you can tell me what s goin on with this screen
08.43.11 #       <yeft2> it says PADR:8A7F
08.43.21 #       <yeft2> PBDR:B8BF
08.43.24 #       <midk> it loses about 2 seconds a minute
08.43.30 #       <yeft2> AN0:3FF
08.43.34 #       <LinusN> try to push the solder pads, one at a time, to see if anything happens
08.43.35 #       <yeft2> AN1:3FF
08.43.49 #       <midk> LinusN, is it ok if i include an inaccurate timer in my clock?
08.43.55 #       <LinusN> yeft2: those figures aren't interesting at this point
08.44.05 #       <LinusN> midk: inaccurate timer?
08.44.17 #       <midk> a counter.. press f2 to start/stop, hold to reset
08.44.25 #       <LinusN> a stopwatch?
08.44.28 #       <midk> it loses 5 seconds per 2 minutes
08.44.29 #       <midk> sort of
08.44.36 #       <midk> just a small counter if needed
08.44.39 #       <midk> to time i guess...
08.44.41 #       <yeft2> any idea what those numbers are
08.44.46 #       <LinusN> yeft2: yes i have
08.44.48 #       <midk> i want to implement maybe a countdown feature for it.
08.45.01 #       <yeft2> may i be enlightened please :)
08.45.06 #       <LinusN> midk: an alarm clock feature maybe?
08.45.11 #       <yeft2> holy god 
08.45.14 #       <yeft2> it loaded again
08.45.28 #       <LinusN> yeft2: those are values from the digital and analog ports of the cpu
08.45.30 #       <midk> LinusN: like?
08.45.44 #       <LinusN> like "wake me up at 08:00"
08.45.50 #       <midk> yes but.. how to wake up?
08.45.52 #       <midk> with a sound?
08.45.59 #       <LinusN> a sound, or some music
08.46.34 #       <yeft2> linus, im listening to my music...
08.46.36 #       <yeft2> this is good
08.46.39 #       <midk> was the alarm plugin ever merged?
08.46.56 #       <LinusN> alarm plugin?
08.47.00 #       <midk> it could be cool to combine them
08.47.01 #       <midk> yes...
08.47.08 #       <yeft2> but im afraid this probablly wont last
08.47.25 #       <midk> LinusN, http://sourceforge.net/tracker/index.php?func=detail&atid=439120&group_id=44306&aid=901816
08.47.36 #       <LinusN> yeft2: squeeze the device on various places
08.47.53 #       <yeft2> to see what happen
08.48.19 #       <LinusN> yes
08.48.29 #       <yeft2> heh i squeezed
08.48.31 #       <yeft2> and it died
08.48.42 #       <LinusN> so find out where the "sweet spot" is
08.49.03 #       <yeft2> my archos just loaded twice in a row
08.49.07 #       <yeft2> a miracle has happened here
08.49.17 #       <midk> no, LinusN has happened here.
08.49.31 #       <yeft2> that too
08.50.09 #       <yeft2> ok i got my sweet spot
08.51.57 #       <midk> fix it.
08.52.23 #       <yeft2> do i get time mk??
08.52.30 #       <midk> no.
08.55.53 #       <midk> gee, thanks, LinusN - now i feel like i can't release the clock without an alarm feature :)
08.56.36 #       <LinusN> midk: i can't see why you are so fixated with this "release"
08.56.50 #       <LinusN> we have daily builds and CVS for a reason
08.57.05 #       <LinusN> we develop things incrementally
08.57.09 #       <yeft2> oh yeah
08.57.11 #       <yeft2> mk
08.57.47 #       <yeft2> http://yeft.iconrate.net/106_1102.JPG
08.58.13 #       <midk> i do it all at once.
08.58.35 #       <midk> yeft2, i like the way you focused the camera on the box in the bg 
08.58.38 #       <LinusN> yeft2: that's a helluva blurry picture
08.58.42 #       <midk> HA ITS UGLY
08.59.18 #       <midk> LinusN.. i may have a solution.
08.59.37 #       <midk> instead of an alarm, a countdown function implemented into the counter would do it
08.59.52 #       <LinusN> midk: leave that for the next version
08.59.55 #       <midk> ie.. oh its 12:30, need to be up at 7... *does math... *sets timer for 6:30:00
09.00.11 #       <yeft2> ...
09.00.12 #       <LinusN> yeft2: i hope you don't run it without the bumpers
09.00.21 #       <midk> no, i already have the counter engine.. even though it would probably wake you up at like 6:45
09.00.26 #       <yeft2> oh jessus why
09.00.37 #       <LinusN> because they also work as insulators
09.00.46 #       <yeft2> oh my word
09.01.10 #       <yeft2> ok
09.01.17 #       <yeft2> i just got an error that said DEADBEEF
09.01.21 #       <yeft2> this thing is making fun of me
09.01.26 #       <midk> yreally?
09.01.27 #       <LinusN> midk: this counter, how come you don't base it on the clock?
09.01.39 #       <midk> LMAO did it say DEADBEEF?
09.01.45 #       <midk> LinusN, but *how*?
09.01.46 #       <yeft2> yes
09.01.50 #       <yeft2> it said deadbeef
09.01.50 #       <midk> LMFAO
09.01.55 #       <midk> TAKE PICTYURE
09.01.57 #       <midk> too late?
09.02.00 #       <yeft2> maybe if i get it again
09.02.02 #       <LinusN> DEADBEEF is the hex value I fill the stack with to detect stack overflow
09.02.03 #       <midk> damn you.
09.03.14 #       <LinusN> damn me?
09.03.27 #       <midk> yeft*
09.03.40 #       <midk> LinusN, may you elaborate on your clock-based counter?
09.03.48 #       <midk> fairly interested in a counter that doesn't lose 2 seconds a minute
09.04.06 #       <midk> that's 2 minutes an hour
09.04.22 #       <midk> 12 minutes for 6 hours
09.04.33 #       <midk> i was right.. it would lose about 15 minutes for 6 1/2 hours.
09.04.37 #       <LinusN> midk: how is the resolution of you counter?
09.04.45 #       <LinusN> seconds?
09.04.49 #       <midk> yes
09.04.55 #       <midk> button scans at HZ/8
09.05.04 #       <midk> so i just do ++ and then divide that number by 8
09.05.10 #       <midk> which ends up with about a second per second
09.05.19 #       <midk> yet.. it's nowhere near perfect or accurrate
09.05.23 #       <midk> accurate.
09.05.23 #       <LinusN> but you update the clock every second, right?
09.05.28 #       <midk> yes
09.06.31 #       <yeft2> ok now 
09.06.37 #       <yeft2> reasons to give up...
09.06.44 #       <midk> 1) NONE
09.06.46 #       <yeft2> 1) its three in the morning
09.06.56 #       <yeft2> 2) it barely works SOMETIMES out of the case
09.06.56 Quit    midk (Read error: 104 (Connection reset by peer))
09.07.11 #       <yeft2> 3) i need it to be usable on an airplane
09.07.13 Join    midk [0] (~Zakk@c66-235-14-120.sea2.cablespeed.com)
09.07.47 #       <yeft2> (for 8 hours nonetheless(
09.07.49 #       <midk> wtf.
09.07.51 #       <midk> anyways did i miss anything?
09.08.06 #       <yeft2> 4) ive been looking for an excuse for a PVP anyway
09.08.20 #       <yeft2> 5) ive solder these tabs into retardation
09.09.03 #       <yeft2> reasons to not quit...
09.09.21 #       <midk> actually
09.09.22 #       <midk> QUIT
09.09.24 #       <midk> so you send it ot me
09.10.01 #       <yeft2> hahah i may never come back to this IRC if i send it to you
09.10.13 #       <midk> who cares, you never come around anyways, :(
09.11.17 #       <yeft2> nnot till i had a serious problem :)
09.11.33 #       <midk> right
09.11.36 #       <midk> you just USE us
09.11.53 #       <yeft2> heheh
09.12.01 #       <yeft2> midk
09.12.14 #       <yeft2> you would make so much fun of me for the way these tabs look
09.12.23 #       <midk> i dont care i want it bad.
09.12.24 #       <midk> fine
09.12.25 #       <midk> $2
09.13.41 #       <yeft2> ...
09.13.48 #       <midk> $5 then
09.14.34 #       <yeft2> .............
09.14.35 Join    Nibbler [0] (nibbler@port-212-202-73-96.dynamic.qsc.de)
09.14.47 #       <yeft2> woah
09.14.52 #       <yeft2> just found out something really coo
09.14.54 #       <yeft2> cool
09.15.39 #       <midk> UM
09.15.40 #       <midk> $10
09.15.54 #       <midk> LinusN are you around?
09.16.16 #       <LinusN> i am
09.16.25 #       <midk> i demand help
09.16.31 #       <LinusN> yeft2: you could donate it to the rockbox project :-)
09.16.36 #       <midk> NO DONATE IT TO ME
09.16.43 #       <midk> i am fmrless
09.17.00 #       <yeft2> hahaha
09.17.09 #       <yeft2> then linus will make fun of me!
09.17.23 #       <midk> he already did with his DEADBEEF code D:
09.17.23 #       <LinusN> midk: there is some code that checks if the clock has changed, right?
09.17.26 #       <yeft2> ill buy my taz and never come around these parts again'
09.17.38 #       <midk> LinusN, no... i just display current_time->tmsec
09.17.50 #       <midk> er
09.17.50 #       <LinusN> ah, ok
09.17.50 #       <midk>         second = current_time->tm_sec;
09.18.10 #       <LinusN> so you update the entire screen every 1/8 sec
09.18.27 #       <midk> yes
09.25.50 #       <yeft2> you know what helps me when im stuck on something
09.26.39 #       <midk> yes?
09.32.07 #       <yeft2> going to the bathroom
09.32.21 #       <midk> i have no use for the bathroom right now
09.32.38 #       <midk> LinusN were you coming up with some idea or should I just try and finish it up?
09.38.57 Join    scott666 [0] (~scott666@c-24-245-58-48.mn.client2.attbi.com)
09.39.04 #       <LinusN> midk: you should base the counter either on the tick counter or the clock itself
09.39.17 #       <midk> i have no preference
09.39.21 #       <midk> how would i base it on the tick counter?
09.48.49 #       <midk> *clicks teeth
09.48.53 #       <midk> may be on clock 2.3 then
09.52.13 #       * LinusN is in a meeting
09.52.26 #       <midk> ok.. sry..
09.52.44 #       <LinusN> midk: when you start the counter, save the current tick value
09.53.08 #       <midk> yah....
09.53.18 #       <LinusN> the counter is then (current_tick - saved_tick) / HZ
09.53.30 #       <midk> YAY TYTY
10.00.31 Join    Bagder [241] (~dast@labb.contactor.se)
10.01.03 #       <midk> hey Bagder
10.01.13 #       <midk> LinusN, if you come around: there is probably no way to pause it, mm?
10.01.15 #       <Bagder> hi
10.03.06 #       <Zagor> midk: pause time? hmm, not easily no :)
10.03.22 #       <midk> hey Zagor
10.03.30 #       <midk> :) ... hmm.. i need some way to pause it.
10.04.49 #       <LinusN> midk: when you pause, save the current tick again
10.05.02 #       <midk> ok
10.05.35 #       <LinusN> when you resume, recalculate the saved_tick again, compensating for the paused time
10.05.56 #       <LinusN> essentially: saved_tick = saved_tick + paused_time
10.06.32 #       <midk> so.. save the current tick to "saved_tick" for example when paused, then resave it again when unpaused?
10.08.36 #       <midk> well i figured out how to reset it... :)
10.09.32 ***     Saving seen data "./dancer.seen"
10.12.32 #       <midk> ok resetting is now out of the way.. still not sure how to pause
10.12.51 #       <midk> you want to say like
10.13.01 #       <midk> save current tick to saved_tick when paused
10.13.10 #       <midk> save current tick to saved_tick_2 when resumed
10.13.18 #       <midk> calculate the difference; store in paused_time
10.13.28 #       <midk> then continue with the counter, just -= paused_time?
10.20.26 #       <LinusN> have a start_tick and a pause_tick
10.20.44 #       <LinusN> start_tick is set when you start the counter
10.20.52 #       <LinusN> pause_tick is set when you pause
10.21.06 #       <LinusN> when you resume:
10.21.31 #       <LinusN> start_tick = start_tick + (current_tick - pause_tick)
10.24.07 #       <LinusN> you then only update the displayed counter if pause == false
10.25.59 #       <LinusN> yeft2: any progress?
10.26.09 #       <midk> ok linus, i think i've got it
10.27.44 #       <yeft2> ...
10.27.45 #       <yeft2> no
10.27.49 #       <midk> DAH
10.27.52 #       <midk> *head is mixing up.
10.28.21 #       <yeft2> did find a nice panasonic mp3 cd player
10.28.24 #       <yeft2> for the temporary
10.28.29 #       <midk> lol
10.28.55 #       <yeft2> well im gonna clearn up and go to sleep
10.29.06 #       <yeft2> night all...and RIP my AJB6000 and FMR
10.29.50 Quit    yeft2 ("Leaving")
10.31.11 #       <midk> hmm, not working
10.31.24 #       <midk> oh
10.31.28 #       <midk> well actually.
10.31.33 #       <midk> sort of
10.32.20 #       <midk> it starts up sort of weird
10.32.27 #       <midk> it shows 0:00:-2
10.32.32 #       <midk> resetting it to 0 works... 
10.32.48 #       <midk> then from there counting, pausing and unpausing works flawlessly
10.33.19 #       <midk> oh there.
10.33.28 #       <midk> oh there again!
10.33.31 #       <midk> see look
10.33.41 #       <midk> i start the clock - counting is false
10.33.47 #       <midk> shows up as 0:00:00 just fine
10.33.56 #       <midk> starting the counter then shows 0:00:-2
10.34.06 #       <midk> resetting it shows 0:00:00 again
10.34.17 #       <midk> but starting the counter once more has it count correctly, etc
10.35.52 Join    amiconn [0] (~jens@pD95D11A3.dip.t-dialin.net)
10.36.18 #       <midk> hi amiconn
10.36.35 #       <amiconn> hi all
10.37.57 #       <midk> hey LinusN...
10.38.34 Join    oxygen77 [0] (~Chris@pauguste-7-82-66-87-78.fbx.proxad.net)
10.38.43 #       <midk> hey oxy :)
10.38.50 #       <oxygen77> hey midk
10.38.55 #       <oxygen77> :)
10.39.05 #       <oxygen77> what are you doing here ;)
10.39.13 #       <midk> lol - rockboxing :D
10.39.22 #       <oxygen77> :))
10.39.48 #       <LinusN> midk: you'll have to think for yourself a little
10.39.59 #       <midk> i am.. it's not coming to me.
10.40.02 #       <LinusN> current_tick is updated 100 times a second
10.40.15 #       <midk> what is the value of HZ?
10.40.15 #       <LinusN> think about how you can use it
10.40.16 #       <midk> 100?
10.40.19 #       <LinusN> HZ is 100
10.41.34 #       <midk> hmm
10.41.42 #       <midk> oh.. well... 
10.41.42 #       <midk> just a sec
10.42.02 #       <midk> possibly need to calculate pause tick at startup because it it paused right away?
10.42.18 #       <LinusN> stopped and paused is not the same thing
10.42.36 #       <midk> oh, that must be where we are mixed up then
10.42.39 #       <LinusN> it could be, of course
10.42.42 #       <midk> what do you define, stopped?
10.42.45 #       <LinusN> it depends on your code
10.42.53 #       <LinusN> stopped is "not running"
10.42.57 #       <midk> i have either counting or not counting.
10.43.02 #       <LinusN> paused is "running, but paused"
10.43.11 #       <midk> you could say not counting is paused or you could say it is stipped
10.43.25 #       <LinusN> still, you can recalculate pause_tick
10.43.30 #       <midk> pause isn't a good definition
10.44.09 #       <midk> you can't define "paused" as "running but paused"
10.44.11 #       <midk> anyhow...
10.44.11 #       <LinusN> if you treat paused and stopped the same, you will not know when and how to recalculate pause_tick
10.44.30 #       <midk> i have bool counting! that is all i know!
10.44.47 #       <LinusN> then deal with it
10.45.01 #       <midk> ok
10.45.09 #       <midk> would you say that not counting is paused or it is stopped?
10.45.28 #       <LinusN> not counting is "not counting" in your choice of implementation
10.45.38 #       <midk> you've not yet defined 'paused'.
10.46.28 #       <LinusN> first of all, if you want it to be accurate, you can't treat it as a "counter"
10.46.52 #       <midk> what would you suggest then?
10.47.00 #       <LinusN> it it supposed to act as a stopwatch?
10.47.07 #       <midk> i suppose so.
10.47.12 #       <midk> yes.
10.48.33 #       <LinusN> think of it as an accumulator, to where you add the passed time between "start" and "stop"
10.49.14 #       <midk> add the passed time?
10.49.18 #       <midk> do you mean subtract?
10.49.28 #       <LinusN> no, the acc starts at 0
10.49.42 #       <midk> right
10.50.08 #       <LinusN> when you start it, you display the acc + the current passed time since the start
10.50.32 #       <midk> ok...
10.52.28 #       <LinusN> when you stop, you update the acc
10.53.01 #       <midk> ok....
10.55.44 #       <midk> well i'm really tired. maybe we should take out the counter for this release.. i've got no idea how to do what needs to be done
10.56.36 #       <LinusN> midk: repeat after me: "incremental development...incremental development"
10.56.50 Join    [IDC]Dragon [0] (~c2af7555@reladm.kharkov.net)
10.56.55 #       <midk> if you've got a solution i hope you can let me know, taking out the counter involves changing all sorts of help texts
10.56.58 #       * Bagder joins in the chant
10.57.14 #       <Bagder> now, isn't that a song? ;-P
10.57.18 #       <LinusN> midk: the acc approach is really simple
10.57.19 #       <[IDC]Dragon> hey, full house again!
10.57.36 #       <midk> LinusN, i think i get what you were saying, but i don't see how ti applies to a stopwatch or timer
10.57.57 #       <LinusN> the acc starts at 0
10.58.06 #       <midk> like a stopwatch.
10.58.14 #       <LinusN> when you start, you set start_tick = current_tick
10.58.34 #       <LinusN> now, the passed time since start is (current_tick - start_tick)
10.59.02 #       <midk> i think the reason it's confusing is because i have differently named variables.
10.59.08 #       <LinusN> on the screen, you display (acc + passed_time)
10.59.27 #       <LinusN> when you stop, acc += passed_time
10.59.51 #       <LinusN> when you reset, acc = 0
11.00.21 #       <LinusN> you only add passed_time to the displayed value if running==true
11.00.59 #       <LinusN> if(running)
11.01.14 #       <LinusN> displayed_value=acc+passed_time
11.01.15 #       <LinusN> else
11.01.19 #       <LinusN> displayed_value = acc
11.01.51 #       <LinusN> or:
11.01.54 #       <LinusN> if(running)
11.02.04 #       <LinusN> passed_time = current_tick - start_tick
11.02.05 #       <LinusN> else
11.02.10 #       <LinusN> passed_time = 0
11.02.16 #       <LinusN> your choice
11.02.23 #       <midk> ok so just a moment here
11.03.02 #       <midk> i have the ints... start_tick, passed_time, acc, and displayed_value?
11.03.36 #       <LinusN> sounds like a way to go
11.03.57 #       <LinusN> "acc" could very well be "counter"
11.04.24 #       <midk> ok then
11.04.25 #       <midk> counter it is
11.04.34 #       <midk> i have bool counting as well
11.04.39 #       <LinusN> good
11.04.39 #       <midk> should that become bool running?
11.04.55 #       <LinusN> running or counting, whatever
11.05.06 #       <midk> ok, i'll keep it at counting.
11.05.32 #       <LinusN> so, "reset" will be: counter = 0;
11.05.50 #       <LinusN> same as you have it now, i guess
11.05.55 #       <midk>             case BUTTON_F2 | BUTTON_REPEAT: /* reset counter */
11.05.55 #       <midk>                 counter = 0;
11.05.57 #       <midk> ?
11.06.15 #       <LinusN> yes
11.06.23 #       <midk> ok
11.06.36 #       * Bagder asks no questions
11.06.43 #       <LinusN> start counter:
11.06.47 #       <midk> you better stay silent.
11.06.49 #       <midk> :)
11.06.50 #       <LinusN> counting = true;
11.07.00 #       <LinusN> start_tick = current_tick;
11.07.07 #       * [IDC]Dragon wonders which lesson this is
11.07.10 #       <midk> haha that's exactly what i've got
11.07.25 #       <midk> now just for displaying it right?
11.07.33 #       <LinusN> stop counter:
11.07.34 #       <midk> wait, what happens when we stop it?
11.07.37 #       <midk> yeah
11.07.49 #       <LinusN> counter += passed_time;
11.07.55 #       <LinusN> counting= false;
11.08.15 #       <midk> we haven't calculated passed_time yet though
11.08.19 #       <midk> or i haven't.
11.08.32 #       <LinusN> we do that all the time
11.08.44 #       <midk> not in my code.. i must've neglected something
11.09.43 #       <LinusN> as often as you can, do:
11.09.50 #       <LinusN> if(counting)
11.10.08 #       <LinusN>    passed_time = current_tick - start_tick;
11.10.09 #       <LinusN> else
11.10.14 #       <LinusN>    passed_time = 0;
11.10.22 #       <LinusN> and:
11.10.36 #       <LinusN> displayed_value = counter + passed_time;
11.12.13 #       <LinusN> [IDC]Dragon: i'm implementing the MDB finetuning
11.12.52 #       <LinusN> two parameters are a frequency, 30-300Hz and 50-300Hz respectively
11.13.05 #       <LinusN> in 10Hz steps
11.13.48 #       <LinusN> the current settings code does not permit scaling, so we waste some bits in the rtc
11.14.16 Quit    scott666 ("i'll be back...eventually...")
11.15.11 #       <midk> LinusN, just one last thing, looks like somewhere we forgot to divide the result or somesuch... looks like it needs to be divided by ten
11.16.23 #       <midk> or
11.16.28 #       <midk>  / 100.
11.17.19 #       <LinusN> midk: of course, the counter is counting 1/HZ seconds
11.17.53 #       <LinusN> so seconds = displayed_value / HZ;
11.18.16 #       <midk> void show_counter(void)
11.18.16 #       <midk> {
11.18.16 #       <midk> 	if(counting)
11.18.16 DBUG    Enqueued KICK midk
11.18.16 #       <midk> 	{
11.18.16 #       <midk> 		passed_time = *rb->current_tick - start_tick;
11.18.17 ***     Alert Mode level 1
11.18.17 #       <midk> 	}
11.18.21 #       <midk> 	else
11.18.23 #       <midk> 		passed_time = 0;
11.18.25 #       <midk>     displayed_value = counter + passed_time;
11.18.27 #       <midk>     count_s = displayed_value / HZ;
11.18.43 #       <LinusN> looks ok
11.18.50 #       <midk> one last thing...
11.18.53 #       <midk> oh lol
11.18.54 #       <LinusN> except for the insane indentation
11.18.57 #       <midk> i just said one last thing.
11.19.05 #       <midk> ?
11.19.22 #       <midk> doesn't really look like that.. some reason it looks different in xchat.
11.19.33 #       <midk> anyways... VERY last thing.. dividing into minutes and seconds
11.19.35 #       <LinusN> you use TAB characters, right?
11.19.41 #       <midk> i replace them
11.19.49 #       <midk> is this better?
11.19.50 #       <midk> void show_counter(void)
11.19.50 #       <midk> {
11.19.50 ***     Alert Mode level 2
11.19.50 #       <midk>     if(counting)
11.19.50 ***     Alert Mode level 3
11.19.50 #       <midk>     {
11.19.51 ***     Alert Mode level 4
11.19.51 #       <midk>         passed_time = *rb->current_tick - start_tick;
11.19.53 #       <midk>     }
11.19.55 #       <midk>     else
11.19.57 #       <midk>         passed_time = 0;
11.19.59 #       <midk>     displayed_value = counter + passed_time;
11.20.01 #       <midk>     count_s = displayed_value / HZ;
11.20.03 #       <midk> yes, it is.
11.20.12 #       <midk> i wrote a simple macro that will replace tabs with four spaces to save you the time. :D
11.20.41 #       <LinusN> midk: would be better to make the editor not use TAB's at all, don't you think?
11.20.55 #       <Bagder> tabs are pure evil
11.20.56 #       <midk> anyways.. i have count_s, count_m, and count_h which end up in char count_text like this
11.20.56 #       <midk>     rb->snprintf(count_text, sizeof(count_text), "%d:%02d:%02d", count_h, count_m, count_s);
11.20.59 #       <midk> and no, can't fix that
11.21.15 #       <LinusN> lame editor indeed
11.21.22 #       <midk> :\
11.21.39 #       <Bagder> emacs is your friend
11.21.45 #       <LinusN> midk: i'll leave the hour and minute calculation as an exercise for you
11.21.45 #       <Bagder> :-)
11.21.48 #       <midk> later later.
11.21.55 #       <midk> LinusN, i've got it worked out
11.21.58 #       <midk> just one problem i'm having
11.22.10 #       <midk> which value do i subtract from to reduce seconds
11.22.15 #       <midk> seems like "passed_time"?
11.22.31 #       <LinusN> you only work on displayed_value
11.22.50 #       <midk> we work on passed_time when we reset it..
11.23.05 #       <LinusN> displayed_value is the value to display on screen
11.23.10 #       <midk> ok, so..
11.23.11 #       <midk>     if(count_s >= 60)
11.23.11 #       <midk>     {
11.23.11 ***     Alert Mode level 5
11.23.11 #       <midk>         displayed_value -= 60;
11.23.11 ***     Alert Mode level 6
11.23.11 #       <midk>         count_m += 1;
11.23.11 ***     Alert Mode level 7
11.23.11 #       <midk>     }
11.23.22 #       <LinusN> no, no, no
11.23.38 #       <midk> aw.
11.24.12 #       <LinusN> displayed_value is the total number of ticks since you last reset the counter
11.24.21 #       <midk> oh yeah
11.24.27 #       <midk> then its
11.24.36 #       <midk> displayed_value -= (60*HZ)
11.24.38 #       <midk> :D
11.24.43 #       <LinusN> nooooooo
11.24.54 #       <LinusN> don't change displayed_value
11.25.02 #       <midk> change count_s?
11.25.11 #       <midk> count_s -= 60.
11.25.52 #       <LinusN> hours = displayed_value / TICKS_PER_HOUR;
11.26.16 #       <midk> *clicks teeth
11.26.33 #       <midk> i calculate how many ticks per hour?
11.26.53 #       <Bagder> HZ * 3600
11.26.57 #       <midk> that's 
11.26.57 #       <midk> 360000
11.27.01 #       <midk> WRONG
11.27.03 #       <midk> oh
11.27.04 #       <midk> right.
11.27.26 #       <LinusN> you seem to think that count_m and count_h are counters themselves
11.27.38 #       <LinusN> they shouldn't be
11.27.42 #       <midk> well ok so we have hour and minute taken care of
11.27.50 #       <midk> what about taking away from second every 60 then?
11.28.08 #       <LinusN> listen:
11.28.28 #       <LinusN> displayed_value is the only thing you need
11.28.46 #       <LinusN> it tells you how many ticks have passed since you started counting
11.28.50 #       <LinusN> ok?
11.29.07 #       <midk> yes....
11.29.36 #       <LinusN> all you need now, is to calculate how manu hours, minutes and seconds that is
11.30.11 #       <midk> i thought that's what i had earlier
11.30.15 #       <midk> but you say this is more correct?
11.30.16 #       <midk>     count_s = displayed_value / HZ;
11.30.16 #       <midk>     count_m = displayed_value / (HZ*60)
11.30.16 ***     Alert Mode level 8
11.30.16 #       <midk>     count_h = displayed_value / (HZ*3600)
11.30.20 #       <midk> except for count_s.
11.30.43 #       <midk> if(count_s >= 60) count_s -= 60;
11.30.55 #       <LinusN> what you had earlier was an attempt to have an "hour" counter
11.31.28 #       <LinusN> or rather, three separate counters
11.31.38 #       <LinusN> count_s, count_m and count_h
11.32.11 #       <LinusN> my approach is to have one single counter, in this case "displayed_value"
11.32.12 #       <midk> right
11.32.28 #       <midk> ohhkay.
11.32.40 #       <LinusN> from that you can calculate how many hours, minutes and seconds that represents
11.32.44 #       <midk> so remove count_s, -m, -h?
11.32.51 #       <LinusN> keep them
11.32.55 #       <LinusN> and do this:
11.33.27 #       <LinusN> count_h = displayed_value / (HZ*3600);
11.34.20 #       <midk> i just posted tjat.
11.35.52 #       <midk> ok so that takes care of hours 
11.36.07 #       <midk>     count_m = displayed_value / (HZ*60)
11.36.08 #       <midk> ?
11.36.37 #       <midk> oh wait
11.36.40 #       <midk> WAITWAIT
11.37.10 #       <midk> ha HA
11.37.11 #       <midk>     count_m = (displayed_value / (HZ*60)) - (count_h * 60);
11.37.18 #       <midk> LinusN is that good or what
11.38.16 #       <LinusN> should be count_h * HZ*3600, shouldn't it?
11.38.40 #       <midk> oh, forgot we were dealing with ticks
11.39.00 #       <midk>     count_m = (displayed_value / (HZ*60)) - (count_h * HZ*3600);.
11.39.53 #       <midk> aaannd... 
11.39.53 #       <midk>     count_s = (displayed_value / HZ) - (count_m * HZ*60);
11.40.17 ***     Alert Mode OFF
11.42.49 #       <midk> aw
11.42.55 #       <midk> was working well until it hit 1 minute
11.43.02 #       <midk> then it turned into 0:01:-5
11.45.55 #       <LinusN> easy approach:
11.46.10 #       <LinusN> displayed_value = displayed_value / HZ
11.46.18 Join    lImbus [0] (~manuel@kernel.cycos.net)
11.46.25 #       <midk> but then it will count past 60 won't it?
11.46.38 #       <LinusN> count_h = displayed_value / 3600;
11.46.48 #       <midk> 360000 you mean?
11.46.56 #       <LinusN> count_m = displayed_value % 3600 / 60
11.47.09 #       <LinusN> count_s = displayed_value % 60
11.47.21 #       <midk> are you sure about that 3600 is all
11.47.33 #       <LinusN> midk: no, 3600, since i just divided displayed_value by HZ
11.47.33 #       <midk> 3600*HZ = 360000
11.48.49 #       <LinusN> 11.46.10 #       <LinusN> displayed_value = displayed_value / HZ
11.49.05 #       <midk> ohh okay
11.49.32 #       <midk> void show_counter(void)
11.49.32 #       <midk> {
11.49.32 #       <midk>     if(counting)
11.49.32 #       <midk>     {
11.49.32 #       <midk>         passed_time = *rb->current_tick - start_tick;
11.49.33 ***     Alert Mode level 1
11.49.33 #       <midk>     }
11.49.35 #       <midk>     else
11.49.47 #       <midk>         passed_time = 0;
11.49.49 #       <midk>     displayed_value = counter + passed_time;
11.49.53 #       <midk>     displayed_value = displayed_value / HZ;
11.49.55 #       <midk>     count_s = displayed_value % 60;
11.49.57 #       <midk>     count_m = displayed_value % 3600 / 60;
11.49.59 #       <midk>     count_h = displayed_value / 3600;
11.50.01 #       <midk>     rb->snprintf(count_text, sizeof(count_text), "%d:%02d:%02d", count_h, count_m, count_s);
11.50.03 #       <midk> that should do.
11.52.29 #       <LinusN> try it
11.52.34 #       <midk> truing
11.52.39 #       <midk> 0:00:25
11.52.41 #       <midk> *waits
11.52.42 #       <midk> 35*
11.52.48 #       <midk> :44
11.52.53 #       <midk> :48
11.53.02 #       <midk> :57
11.53.06 #       <midk> yay
11.53.07 #       <midk> 1:01
11.53.09 #       <midk> YAY
11.53.10 #       <midk> go linusn!!!
11.53.17 #       <midk> *falls asleep now
11.53.34 #       <midk> now all i have to do is fix the reset code
11.53.43 #       <midk> oh, moment.
11.55.47 #       <midk> EXCELLENT
11.55.51 #       <midk> it is READY for RELEASE!!
11.56.12 #       <midk> even excellenter.. it counts even while at help or mode selector
11.56.48 #       <midk> well linus, extra thanks again
11.56.52 #       <midk> time to release and go to bed
11.57.23 #       <LinusN> sleep tight
11.57.41 #       <midk> thankyou.
11.59.34 ***     Alert Mode OFF
12.02.10 #       <midk> ok LinusN, uploaded
12.03.19 #       <midk> in the morning I *may* end up coding a count-up or -down screen, you will see it on the patch tracker at about 18:30 - 20:30 your time.. 
12.03.51 #       <midk> so please don't merge anything until 20:30-ish has passed.. if i have updated it i will upload it, if there is no update that means i have not coded it and you can merge the latest 6/29/04.
12.04.02 #       <midk> thanks for your help again, and good night.
12.04.06 Nick    midk is now known as midk|zZz (~Zakk@c66-235-14-120.sea2.cablespeed.com)
12.04.06 DBUG    Enqueued KICK midk|zZz
12.06.51 #       <LinusN> lunch time
12.09.34 ***     Saving seen data "./dancer.seen"
12.24.31 Ctcp    Ignored 2 channel CTCP requests in 45 minutes and 50 seconds at the last flood
12.24.31 #       * oxygen77 is away: chui pas là
12.41.22 #       * oxygen77 is back (gone 00:16:51)
12.41.22 Quit    Nibbler (Read error: 104 (Connection reset by peer))
12.43.33 Part    oxygen77 ("Cho")
12.56.40 Nick    mbr_ is now known as mbr (~mb@stz-softwaretechnik.com)
13.57.55 Join    Christi-S [0] (~christi@client-519-p-2-lns.glfd.dial.virgin.net)
13.58.59 #       * Christi-S waves.
14.00.20 #       <Christi-S> Updated my firmware today (using the Windows installer ;) ) now that I have a working display again and it tells me I'm not running the latest Rolo.  What's changed, and does one have to go through all the palava of flashing 2.2 then updating again?
14.05.32 #       <LinusN> just rolo the firmware file in the root
14.06.10 #       <Christi-S> Oh.  Thought I'd done that. Weird.
14.07.01 #       <Bagder> what does it say exactly?
14.07.35 #       <LinusN> [IDC]Dragon: u there?
14.08.22 #       <Christi-S> Hint: You're not using the latest bootloader.  A reflash is recommended but not required.
14.08.39 #       <Christi-S> That's when you play the .UCL file
14.08.39 #       <Zagor> i have that too. never bothered me :)
14.09.00 #       <Bagder> that's when you've flashed with the older bootloader
14.09.02 #       <Zagor> i don't remember exactly what the change is
14.09.29 #       <LinusN> Zagor: the older boot loader can't boot with a flat battery
14.09.35 ***     Saving seen data "./dancer.seen"
14.10.11 #       <Christi-S> So does one have to download the bootloader packages and drop back to 2.2 for a bit to fix it then?
14.11.40 #       <Bagder> wine is a pretty big thing
14.11.58 #       <Bagder> the source tarball is 10MB
14.12.02 #       <Christi-S> Yeah, that it is.
14.12.13 #       <Christi-S> Don't you have a package of some kind you can install?
14.12.23 #       <Christi-S> ISTR in't about 6MB compiled.
14.12.23 #       <Bagder> perhaps
14.12.32 #       <Bagder> but it'll put my in upgrade hell
14.12.35 #       <Bagder> put me
14.12.45 #       <Christi-S> Ah, right.  What you running?
14.12.54 #       <Bagder> redhat 7.2 in this case
14.13.07 #       <Christi-S> Ah, no idea how to solve this for redhat.
14.13.15 #       <Bagder> I go the tarball route
14.14.06 #       <Bagder> we'll see where that'll take me ;-)
14.14.53 #       <Christi-S> Hopefully it's not too hideous.
14.15.14 Join    scott666 [0] (~scott666@c-24-245-58-48.mn.client2.attbi.com)
14.15.28 #       <Christi-S> If it were Debian I'd suggest using the latest Debian build script to make a backport package for yourself.  No idea how you'd do that in Redhat.
14.15.47 #       <Bagder> if it were debian, it would be easy ;-)
14.16.43 #       <[IDC]Dragon> LinusN: I'm here
14.17.42 #       <Christi-S> Well true.  I just googled for a backported Wine and installed the latest one I could find (which wasn't all that recent, but did the job).
14.19.05 #       <[IDC]Dragon> Christi-S: feel free to ask me about flashing
14.19.08 #       <LinusN> [IDC]Dragon: was just wondering if you know how much room there is for a 1206 LED soldered on the side
14.19.34 #       <[IDC]Dragon> LinusN: Jens rather recommended 0805
14.19.57 #       <[IDC]Dragon> I thought 1206 would fit, but haven't really tried
14.20.30 #       <Christi-S> [IDC]Dragon - I wanted to know if one had to use the 2.2 firmware flash packages in order to update to the latest Rolo (which doesn't appear to be the one on my disk).
14.20.37 #       <[IDC]Dragon> it may be very fragile, because the sideways mounting makes it stick out pretty far
14.21.06 #       <[IDC]Dragon> Christi-S: not rolo, but the flash loader
14.21.44 #       <Christi-S> Sorry - thought they were mostly the same code. Excuse my ignorance.
14.21.53 #       <[IDC]Dragon> rolo is a feature of Rockbox which enables it to "play" .ajz
14.22.15 Part    Bagder
14.23.18 #       <[IDC]Dragon> the flash loader has nothing to do with that, it unpacks the .ucl into RAM
14.23.46 #       <Christi-S> They're both in some sense firmware loaders, hence the confusion.  But anyway - do I need to use the firmware flash packages in order to update the flash loader?
14.24.10 #       <[IDC]Dragon> yes please.
14.24.37 Join    Nibbler [0] (nibbler@port-212-202-73-96.dynamic.qsc.de)
14.24.45 #       <[IDC]Dragon> you can update to a daily build .ucl straight away
14.25.10 #       <[IDC]Dragon> just place the .bin file(s) from the pack in your root
14.25.45 #       * Christi-S nods. You going to update the version of the firmware flash packages at some point?
14.26.08 #       <[IDC]Dragon> yes, with every "stable" release
14.26.17 #       <Christi-S> Ah, right.
14.26.31 #       <Christi-S> Which is still waiting for me to get off my arse and do something with the manual.
14.26.38 #       <Christi-S> Can I claim I got distracted?
14.26.39 #       <[IDC]Dragon> ;-)
14.27.13 #       <[IDC]Dragon> I always enjoy distracting myself when facing certain work
14.29.10 #       <Christi-S> You don't mention where the images are in FlashingRockbox.  Is that deliberate?
14.29.28 #       <[IDC]Dragon> ?
14.29.54 #       <Christi-S> On the wiki. The guide to flashing doesn't tell you where to get the files.
14.30.41 #       <Christi-S> Fortunately I appear to have put the details in BlindFAQ. Go me. ;)
14.30.41 #       <LinusN> haha
14.30.42 #       <[IDC]Dragon> the more simple and up to date documentation is this: http://rockbox.haxx.se/twiki/bin/view/Main/BlindFlashing
14.31.22 #       <Christi-S> (Probably copied from your post of BlindFlashing to the list a while back.)
14.31.41 #       <[IDC]Dragon> yes, Linus was so kind.
14.34.04 #       <[IDC]Dragon> Christi-S: I dont's see the links in FlashingRockbox either, must have happened whil wiki-ing the article
14.38.04 #       <[IDC]Dragon>  Then it's not bound to a certain Rockbox version.
14.38.04 #       <[IDC]Dragon> Maybe I should release the flash image with 2 copies of Archos software.
14.38.27 #       <[IDC]Dragon> Anybody can play the .ucl he/she likes thereafter.
14.39.04 #       <LinusN> [IDC]Dragon: http://www.wirelessity.ch/shop/catalog/product_info.php/products_id/1802%7B6%7D32
14.39.05 #       <[IDC]Dragon> (oops, above two lines got swapped)
14.40.05 #       <LinusN> [IDC]Dragon: btw, can i extract the original archos firmware from the flash? (lost my backup)
14.40.25 #       <[IDC]Dragon> looks good, how much is a CHF?
14.40.32 #       <Christi-S> There's a bunch of original firmwares on BlueChip's site.
14.41.14 #       <LinusN>  100 CHF (Switzerland Franc) = 63.434 EUR (European Currency Units Euro)
14.41.20 #       <[IDC]Dragon> LinusN: you woudn't need a backup if the content is still in your flash
14.41.33 #       <LinusN> i want to upgrade my boot loader
14.41.46 Join    Bagder_ [241] (~dast@labb.contactor.se)
14.41.51 #       <Zagor> we should try to not have to distribute the archos firmware. we're not allowed to.
14.41.52 #       <scott666> archos .bins arent allowed to be posted on the rockbox site, right?\
14.42.07 #       <scott666> damn you zagor
14.42.08 #       <[IDC]Dragon> OK, flash the full image
14.42.09 #       <scott666> lol
14.42.10 #       <Zagor> :)
14.42.39 #       <Christi-S> [IDC]Dragon - I'd stick with a one rockbox image, particularly if has has speech support.  (Once speech support for plugins is done, it'll be perfect because then flashing should become pretty much as easy for a blind person as for a sighted.)
14.43.07 #       <[IDC]Dragon> that wasn't my point
14.43.28 #       <LinusN> [IDC]Dragon: the full flash image contains the archos fw?
14.43.53 #       <[IDC]Dragon> I mean, if I distribuste a flash image and twice Archos software in it, it's independent of any Rockbox version.
14.44.10 #       <[IDC]Dragon> LinusN: yes, in the front part.
14.44.40 #       <LinusN> badness, i don't think we're allowed to do that
14.45.00 #       <LinusN> which version btw?
14.45.06 #       <[IDC]Dragon> I got Archos' blessing from ther chief developer
14.45.13 #       <LinusN> aha, ok then
14.45.28 #       <[IDC]Dragon> verbally
14.45.37 #       <LinusN> 1.28?
14.45.52 #       <[IDC]Dragon> for all the models, it's the latest I could get hold of
14.46.05 #       <[IDC]Dragon> for recorder, it's 1.28
14.46.28 #       <[IDC]Dragon> but there once was somebody posting he had 1.29
14.46.46 #       <[IDC]Dragon> unfortunately he had not kept a backup
14.48.07 #       <Christi-S> Weird - I get "Wrong plugin" when I try to run firmware_flash.
14.48.54 #       <[IDC]Dragon> make sure you have a consistent version, including plugins
14.49.21 #       <[IDC]Dragon> rolo into it, or start with F+On
14.49.22 #       <Christi-S> It *ought* to be.
14.49.31 #       <Christi-S> I'll clean up + reinstall.
14.52.06 #       * Christi-S wonders if perhaps it's a bug in the Windows installer. Is firmware_flash different for different recorders?
14.52.31 #       <[IDC]Dragon> yes
14.52.52 #       <[IDC]Dragon> well, I think
14.54.37 #       <Christi-S> Seems likely.  Arse.  I'll have to special case it - the installer assumes that plugins are consistent over the recorder models.  Hopefully this is true for all other plugins.
14.54.59 #       <Christi-S> Hmm - what about rockbox_flash?
14.54.59 #       <[IDC]Dragon> why do you assume that?
14.55.13 #       <Christi-S> Seemed like a good idea at the time?
14.55.39 #       <Christi-S> Plus reduces the size of the archive if you're not carrying around three copies of the same code.
14.56.07 #       <Christi-S> Seems to work for other plugins.
14.56.17 #       <[IDC]Dragon> firmware_flash has a model check, to protect you from flashing the wrong image
14.56.54 Nick    Bagder_ is now known as Bagder (~dast@labb.contactor.se)
14.56.56 #       <[IDC]Dragon> rockbox_flash is not so critical, since it only updates the second copy.
14.57.06 #       <[IDC]Dragon> No checks there.
14.57.08 #       <Christi-S> It must be the same code though - I've already successfully run the recorderv1 plugin on my FM.
14.57.44 #       <[IDC]Dragon> you're probably right, the plugin API is the same.
14.58.08 #       <[IDC]Dragon> "normal" plugins should only be interested in that API.
14.58.19 #       <Christi-S> That's what I'd have thought.  So what's the machine dependency in rockbox_flash?
14.58.42 #       <[IDC]Dragon> As I said, to protect you.
14.59.02 #       <[IDC]Dragon> firmware_flash  I mean, sorry.
14.59.23 #       * [IDC]Dragon opens up the code
14.59.55 #       <Christi-S> I meant firmware_flash, sorry.
15.00.04 #       <Christi-S> Bah,  now I'm confusing myself.
15.00.31 #       <Christi-S> Right.  I'll just confirm this.
15.00.36 #       <[IDC]Dragon> I should have giveen them more distinct names
15.04.55 #       <Bagder> "Please ensure that your X server is running and that $DISPLAY is set correctly."
15.04.57 #       <Bagder> sigh
15.05.09 #       <Christi-S> Annoying, isn't it.
15.05.25 #       <Christi-S> Especially as all the output of ISCC is on the command line.
15.05.32 Join    AciD [0] (~acid@longchamp44-1-82-67-133-87.fbx.proxad.net)
15.06.05 #       <Bagder> ... and I'm on a windows box far away, logged in over ssh ...
15.06.33 #       * LinusN has now reflashed with the new boot loader
15.06.47 #       <dwihno> a new boot loader(?)
15.06.59 #       <LinusN> [IDC]Dragon: spelling mistake: it's "sure", not "shure"
15.07.10 #       <LinusN> in firmware_flash.c
15.07.16 #       <[IDC]Dragon> LinusN: I do that all the time
15.07.19 #       <Christi-S> [IDC]Dragon - any reason why the firmware_flash can't just check that the firmware image is appropriate for your archetecture, or does it actually need different code for different architectures (ie is the flashing procedure different on a v1 and an FM)?
15.07.25 #       <[IDC]Dragon> hard to shake
15.08.20 #       <[IDC]Dragon> LinusN: feel free to fix, I have no cvs possibility here
15.08.55 #       <Christi-S> bagder: vnc?   You might be able to leave a minimal X server running with that without needing a connection.
15.08.58 #       <[IDC]Dragon> Christi-S: The image file is different for the models
15.09.33 #       <Bagder> Christi-S: I have an xserver on my cygwin here too
15.09.51 #       <Bagder> but I'll try more later on anyway
15.10.21 #       <Christi-S> [IDC]Dragon: Do you mean the .bin files?
15.10.33 #       <[IDC]Dragon> yes
15.10.36 #       <Christi-S> Or something actually in firmware_flash.rock
15.11.03 #       <[IDC]Dragon> not really
15.11.29 #       * Christi-S nods. So theoretically, firmware_flash from the v1 should run on the fm, right?
15.12.15 #       <LinusN> [IDC]Dragon: committed
15.12.29 #       <Christi-S> (It doesn't.)
15.13.09 #       <[IDC]Dragon> Christi-S: I'm just paranoid. There is no good way to check the model the plugin is running on.
15.13.41 #       <[IDC]Dragon> So I stamp it at compile time.
15.13.58 #       <Christi-S> Ah - well it would mean I'd have to special case firmware_flash in the installer.  Any chance you'd consider taking that out?
15.14.29 #       <[IDC]Dragon> sor safety, no.
15.14.34 #       <[IDC]Dragon> for
15.14.53 #       <[IDC]Dragon> ah, and the filename it uses is different per model
15.15.19 #       <Christi-S> OK - never mind.  Probably a good idea to have support for architecture specific plugins anyway, in case anyone writes a plugin for the radio, say.
15.16.01 #       <[IDC]Dragon> the player has a different set of plugins anyway
15.16.17 #       <[IDC]Dragon> the API is a lot different there
15.16.18 #       <Christi-S> Supports there for the player already.
15.16.37 #       <[IDC]Dragon> so you have a second set
15.17.14 #       * Christi-S nods. I don't want to duplicate all of the recorder plugins three times though.
15.17.50 #       <[IDC]Dragon> maybe the packing can be done in a smart way, by the script(s)
15.18.24 #       <[IDC]Dragon> like, if there are identical plugins, use a link
15.18.36 #       <Christi-S> Yeah, that's what I'll have to do.  I'm trying to build in as few dependencies as possible though, because I don't want every upgrade breaking the install scripts.
15.18.50 #       <Christi-S> Hardcoding file names was something I've managed to avoid till now.
15.19.04 #       <Bagder> then check for binary diffing files
15.19.13 #       <Christi-S> Oh, ISWYM.
15.19.31 #       <Christi-S> Bagder - good plan.  I can always md5sum each plugin.
15.19.35 #       <[IDC]Dragon> that's what I meant, yes
15.20.01 #       * Christi-S sighs. Oh, but writing that in sh is going to be fun. I *knew* I should have used Perl.
15.20.08 #       <Bagder> haha
15.20.44 #       <[IDC]Dragon> you can use Perl in sh...
15.20.52 #       <Christi-S> True.
15.21.08 #       <Bagder> md5sum -c checks the checksum
15.21.13 #       <Bagder> it isn't that hard to do in sh
15.21.28 #       * Christi-S nods. I just like to bitch.
15.21.37 #       <Bagder> although I think going perl will be easier in the long run
15.21.59 #       <[IDC]Dragon> so many script languages to choose from...
15.22.14 #       <[IDC]Dragon> how about Ruby?  ;-)
15.23.21 #       <Christi-S> Well, the idea was to keep it as lightweight as possible so as not to use too much resources.
15.23.30 #       <Christi-S> That's why I originally went for sh rather than perl.
15.23.45 #       <lImbus> perl is not a resource ;-)
15.24.44 #       <dwihno> perl \o/
15.25.53 #       <Christi-S> Oh, f***, I'm still getting a "you're not using the latest bootloader" error message after rerunning firmware_flash.
15.26.19 #       <[IDC]Dragon> foulmouth!
15.26.38 #       * Bagder washes Christi-S's mouth with soap ;-)
15.26.38 #       * dwihno never did ruby
15.26.45 #       * dwihno never did Ruby Wax ;)
15.26.51 #       <dwihno> SOAP? :)
15.27.14 #       <[IDC]Dragon> are you sure you got the 2.2 image from my webspace?
15.27.42 #       <LinusN> Christi-S: i just updated my boot loader and it worked for me
15.27.57 #       <Christi-S> Just making certain now.
15.28.57 #       <Christi-S> No, appears I didn't.  Weird - I'm sure I opened it from Mozilla.
15.29.40 #       <Christi-S> No, I tell a lie.  It's definitely filestamped today.
15.29.53 #       <Christi-S> Linus - what model JB do you have?
15.31.21 #       <LinusN> i have a recorder v1
15.31.24 #       <Christi-S> OK - that's unconvincing. The firmware-fm.bin timestamp is March.
15.31.39 Join    mroizo [0] (~chatzilla@kabel219106.mobiel.utwente.nl)
15.31.48 #       <[IDC]Dragon> did I goof?
15.31.58 #       <Christi-S> [IDC]Dragon - it's possible, yes.
15.32.02 #       <Christi-S> Could you check?
15.32.13 #       <[IDC]Dragon> not until tonight
15.32.27 #       <Christi-S> Either that or something bloody weird is happening with caches.
15.33.28 #       <[IDC]Dragon> timestampt is march 12th for all of them
15.34.03 #       <Christi-S> OK - this is getting weirder.
15.34.33 #       <Christi-S> So I *do* have the most recent firmware loader installed but rockbox_flash claims I haven't?
15.34.40 #       <[IDC]Dragon> 2.2 was released march 11th, so this is plausible
15.34.59 #       <Christi-S> Aha - unless rockbox_flash is architecture dependent too.
15.35.28 #       * [IDC]Dragon feels a clue
15.36.15 #       * Christi-S sighs. I'm glad I found this rather than a user. ;) Would've been hell to debug via someone else.
15.36.58 #       <[IDC]Dragon> rockbox_flash is architecture dependent too.
15.37.14 #       <[IDC]Dragon> for the sole reason to chech the bootloader.
15.37.21 #       <[IDC]Dragon> check
15.38.06 #       <[IDC]Dragon> so you got the wrong one, not for your model
15.39.29 Join    Rachael-hispo- [0] (~christi@client-165-p-2-lns.glfd.dial.virgin.net)
15.40.40 Nick    Rachael-hispo- is now known as Christi-S- (~christi@client-165-p-2-lns.glfd.dial.virgin.net)
15.40.57 #       <Christi-S-> Bah - I detest dialup.
15.42.07 #       <Christi-S-> Right.  All fixed.  Now I just need to figure out how to rewrite the installer.
15.53.37 Quit    mroizo ("Chatzilla 0.9.64a [Mozilla rv:1.7/20040614]")
15.56.50 Quit    Christi-S (Read error: 110 (Connection timed out))
15.58.55 Part    LinusN
16.05.02 Part    Bagder
16.09.39 ***     Saving seen data "./dancer.seen"
16.11.00 Quit    ka__ ("Leaving")
16.20.19 Quit    Christi-S- ("If I were actually witty, this quitline would be funny.")
16.20.33 Join    ka__ [0] (~tkirk@65.216.194.2)
16.55.17 Quit    [IDC]Dragon ("no fate but what we make (EOF)")
16.55.31 Join    mo1e [0] (~aarruda@12.33.239.250)
16.55.52 #       <mo1e> hello everyone
16.56.14 #       <mo1e> i'm a bit confused on flashing my v2
16.56.25 #       <mo1e> i can't seem to find where to get the BIN file...
16.58.45 Quit    AciD (Read error: 104 (Connection reset by peer))
17.19.08 Quit    Nibbler (Read error: 104 (Connection reset by peer))
17.21.50 Part    Zagor
17.23.22 Join    dstar5 [0] (lee@ACC734D7.ipt.aol.com)
17.35.10 Quit    c0utta (kornbluth.freenode.net irc.freenode.net)
17.35.10 NSplit  kornbluth.freenode.net irc.freenode.net
17.35.10 Quit    dwihno (kornbluth.freenode.net irc.freenode.net)
17.35.10 Quit    tomMeditates (kornbluth.freenode.net irc.freenode.net)
17.36.22 NHeal   kornbluth.freenode.net irc.freenode.net
17.36.22 NJoin   c0utta [0] (~c0utta@47.cust4.sa.dsl.ozemail.com.au)
17.36.22 NJoin   dwihno [0] (~dw@81.8.224.89)
17.36.22 NJoin   tomMeditates [0] (~kaboofa@66.92.66.5)
17.42.32 #       <mo1e> i'm a bit confused on flashing my v2
17.42.34 #       <mo1e> i can't seem to find where to get the BIN file...
17.44.48 Join    top_bloke [0] (~ekolb_pot@0-1pool36-18.nas12.oakbrook1.il.us.da.qwest.net)
17.49.14 #       <dstar5> ?
17.49.36 #       <dstar5> are you talking about the bin file you flash?
17.49.56 #       <mo1e> yes
17.50.12 #       <dstar5> it is in the zip file you download
17.50.52 #       <mo1e> i downloaded the daily build...
17.51.31 #       <mo1e> it's not in there...
17.51.33 #       <dstar5> no, it is in the zip file you flash with
17.51.39 #       <dstar5> hold on, ill give you a link
17.53.23 #       <dstar5> humm.. wher is that link
17.54.11 #       <dstar5> are you updating your flash? or have you already flashed rockbox?
17.54.29 #       <mo1e> upgrading
17.54.38 #       <mo1e> shouldn't the how to include a link or something
17.55.14 #       <dstar5> ohh, then what you do is look for a .ucl file
17.55.20 #       <dstar5> and just "play" it
17.55.33 #       <dstar5> (it is in the daily build)
17.55.59 #       <mo1e> ohhh ok
17.56.05 #       <mo1e> so the bin is really just the bootloader?
17.56.11 #       <dstar5> yes
17.56.18 #       <mo1e> gotcha
17.56.26 #       <dstar5> :)
17.56.32 #       <dstar5> gluck
17.57.17 #       <mo1e> i was always a bit confused
17.57.20 #       <mo1e> but now i understand
17.58.52 #       <mo1e> how come the newer versions have that bar on the bottom that tell you what the F keys do?
17.58.58 #       <mo1e> can that be disabled?
17.59.17 #       <dstar5> yes, look in the settings
17.59.33 #       <dstar5> some people wanted it, i find it annoying myself
17.59.43 #       <mo1e> i guess the selected font isn't written to saved config files
18.01.10 #       <mo1e> or maybe it is...
18.01.11 #       <mo1e> hmmm
18.01.26 #       <mo1e> there are more settings since version 2.2
18.01.39 #       <dstar5> yes
18.01.55 #       <dstar5> i recommend almost always to use daily builds
18.03.15 #       <mo1e> i've just been hesitant due to bugs, but it seems like rockbox is pretty solid 
18.03.39 #       <dstar5> bugs are nothing to really worry about
18.03.56 #       <dstar5> they do happen somtimes, but usualy, you want even notice them
18.04.07 #       <dstar5> and if you do, they will not harm your unit
18.04.15 #       <mo1e> yup
18.04.17 #       <mo1e> the Anti-Skip buffer....what does this setting actually do?
18.04.47 #       <dstar5> it starts the disk buffering early, incase it will have trouble loading
18.05.44 #       <mo1e> ah
18.06.34 #       <mo1e> does voice work automatically or is there something i have to do....
18.09.40 ***     Saving seen data "./dancer.seen"
18.19.12 Join    pfavr [0] (pfavr@dyna218-088.nada.kth.se)
18.25.09 Quit    lImbus ()
18.27.20 #       <dstar5> voice?    you need to download voicefonts
18.27.23 #       <dstar5> hi pfavr
18.27.39 #       <pfavr> hi dstar5 
18.40.03 Quit    midk|zZz (kornbluth.freenode.net irc.freenode.net)
18.40.03 NSplit  kornbluth.freenode.net irc.freenode.net
18.40.03 Quit    Hadaka (kornbluth.freenode.net irc.freenode.net)
18.40.03 Quit    Ka_ (kornbluth.freenode.net irc.freenode.net)
18.41.20 NHeal   kornbluth.freenode.net irc.freenode.net
18.41.20 NJoin   midk|zZz [0] (~Zakk@c66-235-14-120.sea2.cablespeed.com)
18.41.20 NJoin   Ka_ [0] (~tkirk@pcp04776551pcs.howard01.md.comcast.net)
18.41.20 NJoin   Hadaka [0] (naked@naked.iki.fi)
18.58.27 Join    AciD [0] (~acid@longchamp44-1-82-67-133-87.fbx.proxad.net)
18.58.51 Join    Nibbler [0] (nibbler@port-212-202-73-96.dynamic.qsc.de)
19.04.17 Nick    midk|zZz is now known as midk (~Zakk@c66-235-14-120.sea2.cablespeed.com)
19.04.17 DBUG    Enqueued KICK midk
19.17.42 #       <dstar5> bye pfavr
19.17.46 #       <dstar5> thanks for your hel0p
19.17.49 #       <dstar5> help
19.17.56 #       <pfavr> cu
19.18.02 #       <dstar5> bye mids
19.18.05 Quit    dstar5 ("Leaving")
19.28.31 Quit    midk ("just STOP it arspy")
19.30.32 Join    midk [0] (~midk@c66-235-14-120.sea2.cablespeed.com)
19.33.58 Quit    pfavr ("ChatZilla 0.9.61 [Mozilla rv:1.7/20040624]")
19.49.37 Quit    Nibbler (Read error: 104 (Connection reset by peer))
19.49.43 Quit    midk (Remote closed the connection)
19.51.49 Join    midk [0] (~Zakk@c66-235-14-120.sea2.cablespeed.com)
20.09.44 ***     Saving seen data "./dancer.seen"
20.36.14 Quit    AciD (Read error: 104 (Connection reset by peer))
21.03.35 Quit    top_bloke (Read error: 104 (Connection reset by peer))
21.27.53 Join    Strath [0] (~mike@dgvlwinas01pool0-a215.wi.tds.net)
21.32.14 Join    AciD [0] (~acid@longchamp44-1-82-67-133-87.fbx.proxad.net)
21.34.08 Join    Nibbler [0] (nibbler@port-212-202-73-96.dynamic.qsc.de)
21.34.21 Join    dstar5 [0] (lee@ACC36A88.ipt.aol.com)
21.35.02 Quit    dstar5 (Client Quit)
21.59.02 Part    amiconn
21.59.38 Join    amiconn [0] (~jens@pD95D11A3.dip.t-dialin.net)
22.09.39 Quit    midk (Read error: 104 (Connection reset by peer))
22.09.44 Join    midknight2k3 [0] (~Zakk@c66-235-14-120.sea2.cablespeed.com)
22.09.47 ***     Saving seen data "./dancer.seen"
22.11.22 Nick    midknight2k3 is now known as midk (~Zakk@c66-235-14-120.sea2.cablespeed.com)
22.11.22 Quit    mo1e (Read error: 104 (Connection reset by peer))
22.24.52 Join    kagami [0] (firewall-u@mmc.mtmercy.edu)
22.25.06 #       <kagami> hello I have a small question
22.25.28 #       <midk> perhaps if you ask it will be answered
22.25.55 #       <kagami> how do you get rid of the *panic* screen it seems like my jukebox is frozen up
22.26.03 #       <midk> hold your off button
22.26.05 #       <kagami> is there a restart button?
22.26.09 #       <midk> what model?
22.26.12 #       <midk> fm/v2?
22.26.42 #       <kagami> oh hah dang it was that simple
22.26.49 #       <midk> :)
22.26.56 #       <kagami> I guess you have to hold it for like 5 seconds instead of 3
22.27.00 #       <kagami> haha
22.27.05 #       <kagami> well thanks anyway
22.27.08 #       <midk> yeah
22.27.10 #       <midk> hold 5 to reset
22.27.18 #       <midk> 3 will turn it off if it isnt locked up
22.27.20 #       <midk> or more like 2..
22.27.20 #       <kagami> you are an incredibly smart man
22.27.25 #       <midk> haha :)
22.27.33 #       <kagami> thankyou 
22.27.33 #       <midk> i read the manual. :D
22.27.36 #       <kagami> :)
22.29.02 #       <kagami> hmm I also have nother question
22.29.26 Join    dstar [0] (lee@IC104.library.oregonstate.edu)
22.29.31 #       <midk> DSTAR DSTAR
22.29.32 #       <kagami> how do I get windows to recognize my USB device, when it says nothings plugged in you know?
22.29.33 #       <midk> surely.
22.29.51 #       <midk> is it on and plugged in and at usb screen?
22.30.08 #       <kagami> yeah it has a big ol USB icon on the screen
22.30.21 #       <kagami> but windows says theres no external device
22.30.30 #       <midk> hmm
22.30.32 #       <kagami> like no new harddrive to play with man
22.30.36 #       <midk> :)
22.30.45 #       <midk> um.. maybe <windows><break>
22.30.50 #       <midk> pause/break*
22.30.55 #       <midk> hardware,
22.30.57 #       <midk> device manager
22.30.59 #       <kagami> what the
22.31.03 #       <midk> see if it's under Unknown Devices
22.31.12 #       <kagami> how do i get there?
22.31.18 #       <midk> hold windows, press pause/break
22.31.22 #       <midk> like alt+f4
22.31.23 #       <kagami> windows xp
22.31.26 #       <midk> yeah.
22.31.29 #       <kagami> no its not
22.31.31 #       <midk> windows key next to ctrl.
22.31.41 #       <midk> pause next to scroll lock and num lock
22.32.09 #       <kagami> oh right
22.32.11 #       <midk> plug it in btw.
22.32.23 #       <midk> make sure your batteries aren't low
22.32.25 #       <kagami> man that says thats controlled only under the system administrator
22.32.40 #       <midk> ?
22.32.42 #       <kagami> they arent low man
22.32.42 #       <midk> dah
22.32.49 #       <midk> hmm
22.32.55 #       <kagami> this isnt my computer
22.32.57 #       <midk> so nothing happens when you plug it in?
22.33.00 #       <kagami> its my boss's
22.33.01 #       <midk> no daDA sound?
22.33.10 #       <kagami> he doesnt know I'm in here now
22.33.24 #       <kagami> not as far as windows is concerned
22.33.35 #       <midk> hmmmm
22.33.50 #       <kagami> stupid thing
22.33.59 #       <midk> but it probably works on your computer, right?
22.34.14 #       <kagami> hey is archos charging when its hooked up to the USB?
22.34.15 #       <amiconn> midk: U versioning me?
22.34.19 #       <midk> yes it is
22.34.20 #       <kagami> does that work to charge too?
22.34.24 #       <midk> amiconn: ... *looks away
22.34.26 #       <midk> :)
22.34.28 #       <midk> i did, yes.
22.34.33 #       <kagami> oh, cuzz it looked like it
22.34.34 #       <kagami> anyway
22.34.45 #       <kagami> yeah it works on my computer
22.34.59 #       <midk> hmm
22.35.01 #       <midk> very weird then
22.35.08 #       <midk> try a different usb port?
22.35.36 #       <kagami> ok
22.36.26 #       <kagami> man stupid thing
22.36.33 #       <kagami> nevermind
22.36.49 #       <midk> ok
22.36.50 #       <midk> sry
22.37.04 #       <kagami> it is being a pain in the butt
22.37.26 #       <kagami> do you think he will be mad if I destroy his computer?
22.37.53 #       <kagami> or maybe drop it out the window?
22.38.05 #       <kagami> cuzz it deserves it.
22.38.23 #       <midk> umm
22.38.24 #       <midk> probably.
22.38.37 #       <kagami> how sure of this are you?
22.39.15 #       <midk> about... 100% sure
22.39.20 #       <kagami> hey I got nother question
22.39.41 #       <kagami> is theres a version of tetris that is vertical, not horizontal for Rockbox
22.39.57 #       <midk> no.. but i was trying to code it earlier..
22.40.09 #       <midk> i'll probably work on it today since i've finished my clock update
22.40.29 #       <kagami> cuzz tetris blocks dont normally fall horizontally
22.40.42 #       <kagami> ok man
22.40.48 #       <kagami> you can do it I know you can
22.40.54 #       <kagami> :)
22.41.03 #       <amiconn> midk: What happened to breakout btw?
22.41.27 #       <midk> amiconn: nothing... i need linusn to merge a function that allows me to speed up keypress repeat rate
22.41.38 #       <midk> i have no idea on the status of that.
22.42.11 #       <amiconn> Ahh, the keypress thingy...
22.42.21 #       <midk> yah
22.52.20 Quit    kagami ()
23.12.33 Join    midknight2k3 [0] (~Zakk@c66-235-14-120.sea2.cablespeed.com)
23.12.53 Quit    midk (Nick collision from services.)
23.12.55 Nick    midknight2k3 is now known as midk (~Zakk@c66-235-14-120.sea2.cablespeed.com)
23.13.41 #       <dstar> hi midk
23.14.04 #       <midk> yo dids.
23.24.27 Join    LinusN [200] (~linus@labb.contactor.se)
23.24.37 #       <amiconn> Hi LinusN
23.24.42 #       <LinusN> yo
23.25.10 #       <amiconn> Did you read the reports on my ata test 2?
23.25.18 #       <LinusN> midk: tetris is rotated 90 degrees for a very good reason
23.25.29 #       <LinusN> amiconn: yes, looks promising
23.25.36 #       <amiconn> Especially Pedro's reply is promising...
23.25.39 #       <midk> LinusN: yes...
23.25.42 #       <LinusN> exactly
23.25.43 #       <midk> but it COULD be vertical, no?
23.26.04 #       <LinusN> of course it can, but it will be smaller
23.26.10 #       <midk> right.
23.26.21 #       <LinusN> we rotated it (and the buttons) to use the screen better
23.26.22 #       <amiconn> LinusN: A question - could you look up if some special people are still subscribed to the ml?
23.26.23 #       <midk> i think people are willing to sacrifice a bit of block size for verticalness
23.26.27 #       <midk> well i will have an option for it,.
23.26.45 #       <LinusN> midk: the wjole point is that you should rotate the jukebox
23.27.05 #       <midk> but if you don't want to?
23.27.12 #       <midk> i don't like placing my hand(s) on the right
23.27.24 #       <midk> *i* prefer playing it horizontal without rotating it
23.27.30 #       <midk> but.. i am very different from most.
23.27.40 #       <LinusN> maybe an upside-down option?
23.27.48 #       <amiconn> lol
23.28.04 #       <midk> let's just have normal, rotated 90, 180 and 270 options.
23.28.04 #       <LinusN> for lefties
23.28.08 #       <midk> lol
23.28.12 #       <midk> i use both hands
23.28.44 #       <LinusN> amiconn: who are you looking for?
23.32.00 #       <amiconn> I have a theory about these corruptions (I had them back in March already, but Jörg though that it is unlikely)
23.32.12 #       <midk> LinusN, if i code a vertical option, would it be rejected?
23.33.54 Join    hardeep [0] (1098@208.247.65.237)
23.34.08 #       <LinusN> midk: no
23.34.31 #       <LinusN> amiconn: tell me
23.35.21 #       <amiconn> The corruption occurs with Hitachi DK23CA disks, but _only_ on v1 Recorders with mask 0x0102.
23.35.23 #       <LinusN> midk: is the clock ready to merge?
23.37.31 #       <amiconn> Although the single different bit to the more widespread 0x0302 is the lcd bias, I think because 0x0102 is definitely a different hardware revision, the ata delay circuits may be a bit different also.
23.38.05 #       <LinusN> amiconn: doesn't sound too unlikely
23.42.13 Part    LinusN
23.42.15 Join    LinusN [200] (~linus@labb.contactor.se)
23.42.39 Join    silencer [0] (~silencer@dyn-213-36-104-14.ppp.tiscali.fr)
23.42.56 #       <amiconn> LinusN: Furthermore, either one of the facts that the writing is now optimized also, the reading is different (and even faster) than back in Feb, or some other change in ata.c makes it work now for 0x0102 masked recorders
23.43.11 #       <LinusN> spooky
23.44.13 #       <amiconn> LinusN: There are a number: You changes to the ata_reset behaviour (to bash the rld problem), my no-spindown-by-the-disk change...
23.44.36 #       <LinusN> ah, of course
23.54.53 #       <amiconn> LinusN: My theory is backed by the fact that 2 of the 3 reporters of fs corruption happen to have a v1 Recorder with mask 0x0102 and Hitachi DK23CA (of the 3rd I don't know the mask)
23.55.34 #       <amiconn> Another user (from Sweden :)) happens to have the same disk with a 0x0302 masked recorder, and reported noo problems.
23.55.41 #       <amiconn> *no
23.55.52 #       <LinusN> henrik backe, no?
23.55.56 #       <amiconn> yup
23.56.27 #       <LinusN> so, if your theory is correct, we can adapt by checking the mask
23.56.31 #       <LinusN> if needed
23.56.41 #       <amiconn> if needed, yes
23.57.15 #       <amiconn> I asked Pedro to check with real use for a while if he dares...
23.57.25 #       <LinusN> yeah, saw that