--- Log for 24.06.103 Server: calvino.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16p1 Started: 1 month and 11 days ago 00.01.35 # I only see one place where ROM is read from 00.01.47 # and that's 0x020000fc or some such place 00.02.17 # Stevie[FP]: that's the one 00.02.18 # <[IDC]Dragon> that is the hardware mask (and version following that) 00.02.55 # The archos engineers should have great fun reading the irc logs. 00.03.20 # <[IDC]Dragon> Probably they get grey hair right now. 00.03.51 # <[IDC]Dragon> With me potentially generating hundreds of service claims ;-) 00.03.53 *** Saving seen data "./dancer.seen" 00.04.00 Quit tracktheripper ("Leaving") 00.04.20 Join tracktheripper [0] (jirc@ACA320AA.ipt.aol.com) 00.06.15 # <[IDC]Dragon> Linus, do you know anything about the set of mask values? (repeating myself) 00.06.58 # i know some, yes 00.07.27 # <[IDC]Dragon> Would you tell me (please)? 00.07.32 # i don't think it is a mask after all 00.07.41 # <[IDC]Dragon> anyway. 00.08.03 # i think it is two bytes with the version number of the two boards 00.08.38 # i have gathered some data from quite a few users 00.08.53 # <[IDC]Dragon> are those different for Player/Recorder/FM as the main branches? 00.09.13 # <[IDC]Dragon> Can you email me that? 00.10.07 # they are different, yes (i have no data for the fm though) 00.10.38 # <[IDC]Dragon> I can ask somebody with an FM. 00.11.08 # you want data for the fm? 00.11.36 # <[IDC]Dragon> Yo got one? What does it say for hardware mask? 00.11.48 # my fm is the only one with 0x0304 00.11.55 # (in my survey) 00.12.10 Join Stevie-O [0] (~whatsit2u@65.114.136.196) 00.12.21 # (pc=0x09009350) > r b 0x020000fc 00.12.21 # (0x020000FC)=0x05 00.12.31 # anything else ye desire? 00.13.10 # a beer? 00.13.12 # that's from one with 1.30j on the fw 00.13.30 # sorry, no tap emulation yet 00.14.12 Quit _aLF ("bye") 00.14.37 # [IDC]Dragon: see hwcompat.[ch] 00.17.31 # <[IDC]Dragon> That tells me how it's read. but not which values are out in the field, right? 00.19.08 # that tells how we use the hw mask to adapt to the different hw versions 00.20.59 # <[IDC]Dragon> OK, currently USB and MAS polarity, all on the same bit. 00.21.08 # yes 00.21.20 # and ATA address 00.21.59 # <[IDC]Dragon> That's defined, but I don't see it being used. 00.22.23 # no, we don't use it 00.22.34 # we autodetect that 00.22.54 # the hw mask survey was done long after we wrote the ata autodetection 00.22.55 # <[IDC]Dragon> Sounds better! 00.23.25 # <[IDC]Dragon> Can I get the results of that survey, please? 00.23.45 # it's in my pda, and i can't sync in linux (yet) 00.24.07 # <[IDC]Dragon> Any time, not now. I appreciate it. 00.24.54 # sure 00.25.02 # <[IDC]Dragon> Thanks! 00.25.58 # <[IDC]Dragon> Tomorrow I'll try downloading Rockbox via my UART monitor. I'm curious if that will run. 00.26.22 # <[IDC]Dragon> Question of enough initializations. 00.26.57 # well 00.27.06 # do you want to know what it initializes? 00.27.14 # ;) 00.27.17 # <[IDC]Dragon> If it runs, the way is clear for flashing. If not, it will be difficult to debug. 00.27.39 # hmm, indeed 00.27.57 # do you have a way to reflash the original FW if it doesn't work? 00.28.30 # <[IDC]Dragon> Currently, I don't need to flash, just load it into DRAM. 00.28.40 # oh 00.28.42 # ok 00.28.47 # well 00.28.48 # I gotta run 00.28.53 # cya l8r 00.29.00 # <[IDC]Dragon> But yes, I could reflash (if that damn chip arrives) 00.31.29 # <[IDC]Dragon> Folks, I'd like to go to bed, see you later! 00.31.35 # cu 00.31.57 # <[IDC]Dragon> (And thanks for all) 00.32.18 Quit [IDC]Dragon ("Leaving") 00.38.33 Join tracktheripper1 [0] (jirc@AC9C1C0D.ipt.aol.com) 00.42.31 Join ^gizz^ [0] (~nico@lns-th2-2f-81-56-186-54.adsl.proxad.net) 00.42.45 # <^gizz^> hi all 00.42.53 # 'ello 00.44.54 # * tracktheripper1 is very upset because Sokoban doesn't work anymore for me 00.45.08 Quit tracktheripper1 ("Leaving") 00.45.26 Join tracktheripper1 [0] (jirc@AC9C1C0D.ipt.aol.com) 00.46.18 # <^gizz^> linus, I have a hardware question for you :-) 00.46.20 Quit tracktheripper1 (Read error: 104 (Connection reset by peer)) 00.46.30 Quit Stevie-O (Read error: 113 (No route to host)) 00.47.13 # <^gizz^> do you think it would be feasible/not to hard to wire a second hdd on the archos ATA bus ? 00.47.57 # it would be a lot of work 00.48.14 # <^gizz^> not worth the result you mean ? 00.49.06 # i mean that it would require a hw mod, and some ATA driver hacking 00.49.20 # <^gizz^> hmm 00.50.07 # <^gizz^> recently I saw the prices of standalone hdd for CF backup, and they were so high I got this idea.. 00.50.17 Join tracktheripper1 [0] (jirc@AC9B9C90.ipt.aol.com) 00.50.38 # the current ata driver expects only one hs on the bus 00.50.43 # hd 00.50.47 # <^gizz^> linus : for you, what would be the hardest ? hw or driver mod ? 00.50.58 Quit tracktheripper (Read error: 110 (Connection timed out)) 00.51.01 # driver 00.51.05 # <^gizz^> argh 00.51.30 # i'm not sure that the originsl firmware can handle it either 00.51.37 # <^gizz^> sure 00.51.45 # i guess they autodetect as well 00.51.55 # so the second drive will confuse them 00.52.15 # <^gizz^> btw : 00.52.33 # <^gizz^> what if I put two FAT32 parts on my rockbox, 00.52.39 # <^gizz^> with files on both 00.52.45 # <^gizz^> what about the fs root ? 00.52.55 # <^gizz^> (for rockbox of coure) 00.52.57 # <^gizz^> course 00.53.10 # the second partition will be ignored 00.53.14 # <^gizz^> ok 00.53.23 # <^gizz^> just listed in the hw menu right ? 00.53.28 # yup 00.53.32 # <^gizz^> => 00.54.08 # <^gizz^> I imagined that if it could handle both, it could be feasible to mod rockbox to handle two drives :-/ 00.55.47 # it's not the FAT driver that is the proble, it's the ATA driver 00.56.22 # <^gizz^> last question about that crap : if you decided to do this mod yourself, what time would it take to do it ? (rough approx) -- because if I try to do it, I've got to get it to work before 12. julyy :-/ 00.56.57 Quit tracktheripper1 ("Leaving") 00.57.08 Join tracktheripper [0] (jirc@AC9B9C90.ipt.aol.com) 00.57.20 # does anyone have issues with SOKOBAN? 00.57.21 # <^gizz^> ata : you mean that hw speaking, there is no problem connecting two disks, but the sw (driver) is not aware at all ? 00.58.37 # i guess so 01.02.14 # <^gizz^> ok, g'night everyone ! thx linus ! 01.02.54 # nite ^gizz^ 01.03.05 Part ^gizz^ 01.12.53 Quit tracktheripper ("Leaving") 01.30.24 Quit BoD[] (calvino.freenode.net irc.freenode.net) 01.30.24 NSplit calvino.freenode.net irc.freenode.net 01.30.24 Quit Stevie[FP] (calvino.freenode.net irc.freenode.net) 01.30.24 Quit mbr (calvino.freenode.net irc.freenode.net) 01.30.24 Quit Hadaka (calvino.freenode.net irc.freenode.net) 01.30.36 NHeal calvino.freenode.net irc.freenode.net 01.30.36 NJoin BoD[] [0] (~BoD@m198.net195-132-85.noos.fr) 01.30.40 Join Naked [0] (naked@aka.pp.htv.fi) 01.30.43 Nick Naked is now known as Hadaka (naked@aka.pp.htv.fi) 01.30.44 NJoin mbr [0] (~mb@stlx01.stz-softwaretechnik.de) 01.39.01 Join Stevie-O [0] (whatsit2u@user-2inimbh.dialup.mindspring.com) 01.39.30 # * Stevie-O yawns 01.39.45 # tired? 01.42.06 # yeah 01.42.27 # I'm certain I'm doing something wrong with ATA emulation 01.42.47 # me too :-) 01.43.06 # I wasn't aware you were emulating an ATA device :P 01.43.22 # I get a whole crapload of ATA resets on startup 01.45.27 # [freenode] -lilo(levin@lilo.staff.freenode)- [Global Notice] Hi all. We're experiencing severe attacks and we'll be shutting down the network piece by piece. Thanks. 01.46.16 # euh 01.46.50 # yuck 01.48.25 # shuting down the network 01.48.26 # Stevie-O: i'm very sure that the archos firmware probes the ata for master/slave 01.53.15 # hmm irc.freenode points to 127.0.0.1... 01.53.42 # LinusN: but it's doing a LOT of resets 01.59.05 # oh 01.59.30 # maybe it times out or something? 02.00.15 # not likely, since my emulator reacts instantly as far as the program can tell 02.00.51 # oh well 02.01.21 # but how does the firmware detect the timeout? 02.01.26 # timer interrupt? 02.01.41 # hmm 02.01.45 # not sure 02.02.10 # but then 02.02.15 # the firmware is REALLY braindead 02.02.21 # haha 02.02.21 # it does like 20 consecutive reads of the status register 02.02.26 # it doesn't do anything with the value 02.02.28 # it just reads it 02.02.54 # 0x0901C424: 0x6210 read_ata({0x06000206} sel: 1, 0x016: CS1=A CS0=n A=0x06 R=Status2) = 0x40mov.b @r1, r2 ; (0x06000206) = 0x40 02.02.55 # 0x0901C426: 0x6210 read_ata({0x06000206} sel: 1, 0x016: CS1=A CS0=n A=0x06 R=Status2) = 0x40mov.b @r1, r2 ; (0x06000206) = 0x40 02.02.55 DBUG Enqueued KICK Stevie-O 02.02.55 # 0x0901C428: 0x6210 read_ata({0x06000206} sel: 1, 0x016: CS1=A CS0=n A=0x06 R=Status2) = 0x40mov.b @r1, r2 ; (0x06000206) = 0x40 02.03.04 # yeah i have seen that 02.03.35 # i still wonder why on earth it does that 02.03.42 # oh 02.03.45 # I had a theory 02.03.55 *** Saving seen data "./dancer.seen" 02.04.01 # the original Player firmware has background noise 02.04.13 # during quiet portions of mp3s 02.04.13 # right? 02.04.50 # i believe it is the recorder, but yes 02.05.10 # and i'm pretty sure it's the i2c that does it 02.06.48 # but it supposedly doesn't happen under Rockbox? 02.07.12 # because the rockbox i2c implementation is a lot faster, thus higher in frequency 02.07.35 # i2c is used to transfer the commands 02.07.50 # but I thought the data was transferred through some other method 02.07.53 # and to read the RTC 02.08.08 # the archos firmware reads the rtc a lot 02.08.44 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 02.08.44 # * Stevie-O notes that the archos firmware is krap 02.08.46 # and it reads the peak meter from the MAS frequently 02.09.56 # What if they had a bug in their bitswap routine? 02.10.00 # an off-by-one sort of thing 02.10.33 # if the bitswap fails, the sound output would be muted 02.10.51 # I don't know 02.10.57 # if it was an off-by-one 02.11.07 # the CRC check would fail 02.11.07 # *most* of the mp3 data would be valid 02.11.23 # and the entire frame would be discarded 02.11.25 # the mp3 data itself has a crc check? 02.11.34 # yes, optionally 02.12.09 # I thought that was just the frame data 02.12.37 # oh well, I don't know crap 02.12.50 # yes, ecah frame has a CRC 02.12.51 # each 02.13.13 # and the CRC is calculated from the entire frame contents 02.14.28 # mkay 02.14.32 # well it was just a theory :P 02.16.46 # what does it do before the ATA reset? 02.18.11 # hm 02.18.30 # probes the proper address 02.18.40 # at least I'm assuing that that's what it's probing 02.18.46 # write_ata({0x06000102} sel: 1, 0x00a: CS1=n CS0=A A=0x02 R=SCount, 0x55) 02.18.48 # write_ata({0x06000103} sel: 1, 0x00b: CS1=n CS0=A A=0x03 R=Sector, 0xaa) 02.18.56 # read_ata({0x06000102} sel: 1, 0x00a: CS1=n CS0=A A=0x02 R=SCount) = 0x55 02.18.56 # read_ata({0x06000103} sel: 1, 0x00b: CS1=n CS0=A A=0x03 R=Sector) = 0xaa 02.19.13 # right before that it access the RTC 02.19.54 # writes the alarm date 02.20.09 # (I guess that's to turn off any 'wakeup alarm' already scheduled) 02.21.40 # oic 02.23.31 # 0x40 => SQWE (Square Wave Enable) 02.24.32 # that is the backlight 02.26.58 # yeah 02.27.03 # then it writes 0x10 to the RTC register 'SQW' which sets a 32768 Hz square wave output 02.27.14 # which I assume is the closest thing to solid ON that they have 02.27.21 # yup 02.27.26 # I wonder 02.27.31 # if we set it to 16384Hz 02.28.29 # I wonder 02.29.05 # would the blacklight use half as much power? 02.29.32 # i guess not, since the duty cycle is still 50% 02.29.50 # hmm 02.29.55 # true 02.29.57 # it will just flicker more 02.30.14 # ok 02.30.27 # so just before doing the ATA stuff 02.30.30 # it turns on the backlight 02.30.57 # I hate serial interfaces :P 02.31.15 # long log, eh? 02.31.27 # actually I have code to limit that output 02.31.36 # it's the fact that they take so damn long to emulate 02.31.45 # so it probes, and then what? 02.31.47 # read memory: 1 instruction to emulate 02.31.51 # oh 02.32.01 # write_ata({0x06000106} sel: 1, 0x00e: CS1=n CS0=A A=0x06 R=Dev/Head, 0xa0) 02.32.01 # DEV/HEAD: select device 0 02.32.01 # write_ata({0x06000206} sel: 1, 0x016: CS1=A CS0=n A=0x06 R=DevCtrl, 0x0c) 02.32.01 # Device Control Register: SRST=1 nIER=0 02.32.01 # ATA reset start... 02.32.27 # then it reads the alternate status register 24 times (throwing away the value) 02.32.48 # ok 02.33.00 # or maybe it pays attention the 24th time 02.33.03 # anyway 02.33.03 # write_ata({0x06000206} sel: 1, 0x016: CS1=A CS0=n A=0x06 R=DevCtrl, 0x08) 02.33.03 # Device Control Register: SRST=0 nIER=0 02.33.09 # then it turns off the reset 02.34.34 # then 24 more useless reads of the alternate status register... 02.34.34 # and then? 02.34.51 # then another reset 02.35.14 # what do you return on the alt_status reads, then? 02.36.32 # here 02.36.32 # http://www.qrpff.net/~stevie/jbremu/jbremu_ata.log.bz2 02.37.14 # circa line 708 02.43.29 # hmmm 02.46.02 # it's strange that it resets tha ata that many times, but it does seem to continue after that 02.46.29 # yeah 02.46.38 # hmmm 02.46.42 # * Stevie-O posits a theory 02.46.47 # they didn't get it right the first time 02.46.57 # the only way they could pull it off was to reset a whole buncha times 02.47.23 # and they never bothered to figure out what they were doing wrong 02.48.11 # still, it resets, does a few IDENTIFY and READ_MULTIPLE, and then goes back to the reset stage again 02.48.11 # the Windows and BIOS way: it works, just leave it 02.49.23 # yup. 02.49.43 # gotta sleep now 02.49.48 # ok 02.49.50 # cya l8r 02.49.55 # cu tomorrow 02.49.58 Part LinusN 03.31.33 Quit BoD[] ("dodozitude") 03.31.34 Quit elinenbe (Read error: 104 (Connection reset by peer)) 03.40.18 Quit Jet8810 ("Client exiting") 04.03.56 *** Saving seen data "./dancer.seen" 04.42.56 Join diddystar5 [0] (Lee@AC850056.ipt.aol.com) 04.43.28 Part diddystar5 ("Client exiting") 04.46.30 Join elinenbe [0] (trilluser@user-0cev103.cable.mindspring.com) 04.49.33 Join thu [0] (~thu@h24-87-64-169.vc.shawcable.net) 05.27.35 Join earHurts [0] (~zic@pool-138-88-68-139.res.east.verizon.net) 05.28.01 # anybody here understand electricy? 05.33.15 # no 05.33.30 # you plug one end of the cable into the socket 05.33.32 # what about formatting disks? 05.33.34 # the other end into the archos 05.33.42 # what about it? 05.34.17 Quit hardeep ("BitchX: its magically delicious!") 05.34.21 # windows wants to "write a signature" to my new disk. 05.34.32 # what's that? 05.34.33 # uhm 05.34.34 # no idea 05.34.55 # it's been years since i did more than a format c: \u 05.35.30 # me too 05.36.52 # windows can't seem toi use a disk unless a signature is written. 05.37.28 # 11574.0740740741/365 05.37.35 # er doh 05.38.28 # know about electricty, psyco? 05.38.54 # voltage is pressure, amps is current 05.39.06 # great. 05.39.26 # you familiar with the mechanical design of the fm recorder? 05.39.44 # well it's got buttons and a harddrive 05.40.09 # great. 05.40.42 # okay, it's got a battery. the battery top is metal under plastic. 05.41.03 # the metal contacts, among other things, the outer case. 05.41.15 # why is this NOT a problem? 05.41.49 # why would it be? 05.42.50 # um, ok, why don't I get the current into me when I touch the case. 05.43.02 # because there's no voltage between you and the case? i dunno 05.43.10 # please don't tell me it,s the thin and disappearing veneer of paint 05.43.57 # earHurts: maybe they're considering a zapper module 05.44.03 # for self-defence 05.44.06 # heh 05.45.21 # you need an electromotive force, given by a difference of voltage, to produce a current 05.45.25 # i think 05.45.55 # yeah, I'm pretty ignorant about the subject 05.46.03 # and so the difference in voltage can be either something with an excess of electrons vs something with a diffiency, or it could also be an excess or defficiency vs. the ground state 05.47.27 # in the latter case, one of the contacts for the voltage difference is a ground, which is either litteraly connected to the earth, or is just the biggest conductor you can connect it to 05.48.03 # in an electric guitar the ground is provided by the player 05.48.22 # in many things it's provided by the casing, and sometimes whoever/whatever is holding the casing 05.48.49 # and there's probably lots wrong with all i just said, but i think it answers your question heh 05.49.02 # yeah, ok, so the electricty follows the path of least resistance to the opposite battery pole, and that's never me? 05.49.34 # heh 05.50.00 Quit adi|home (calvino.freenode.net irc.freenode.net) 05.50.00 NSplit calvino.freenode.net irc.freenode.net 05.50.00 Quit dw|gone (calvino.freenode.net irc.freenode.net) 05.50.06 # well you're only touching one pole 05.50.11 # you're not part of the circuit 05.50.14 # the question came up when I opened the archos 05.50.24 # I replaced the hdd 05.50.55 NHeal calvino.freenode.net irc.freenode.net 05.50.55 NJoin adi|home [0] (~adi|home@as5300-11.216-194-24-173.nyc.ny.metconnect.net) 05.50.55 NJoin dw|gone [20] (dwihno@h193180246067.kommunicera.umea.se) 05.50.58 # gave myself a shock, i think 05.51.07 # really? 05.51.20 # i didn't know there was enough voltage in these little things to shock 05.51.21 # heh 05.51.47 # not sure. tingle and a littlw burn in my left hand 05.52.04 # a little sore now, an hour later. 05.52.21 # might ahve been a spontaneous muscle spasm. 05.52.46 # the hdd has a plastic wrap on it. 05.53.02 # I replaced it without the wrap. 05.53.26 # *shrug* 05.53.26 # before i relized I should put the NEW drive in. heh 05.53.38 # heh 05.54.52 # what drive did you get? 05.55.15 # fujitsu 60. it's formtiing via usb now 05.55.31 # how much? 05.55.39 # $170 05.55.54 # heh 05.56.09 # not a fortune but a lot more than an ide drive 05.56.25 # now if I've broken the arcos, it's $340 total 05.56.38 # if I wouldn't be expecting to crash/lose my archos I'd get one too 05.56.46 # did you zap your unit? 05.57.13 # of course, if the shock had given me another heart attack, the cost would have been more 05.57.19 # zap the unit? 05.59.16 # yeah 05.59.39 # what do you mean? 05.59.56 # how did you break your archos? 06.00.58 # I didn't. but in replacing the drive I bent the case and broke a solder point. 06.02.01 # oh I see 06.02.32 # but if it works, I have 55gb 06.04.00 *** Saving seen data "./dancer.seen" 06.05.11 # it will never be enough 06.05.15 # no matter how much space you have 06.07.46 # yeah. 06.08.01 # I another year I'll get a 120 06.08.23 # are there 120G notebook drives? 06.08.37 # in another year there will be. 06.09.05 # true 06.09.21 # I'll probably replace this archos at some point 06.09.25 # because of the limited interface 06.09.38 # I almost crashed my car a few times trying to find a track 06.09.51 # actually I crashed it into the sidewalk once 06.09.53 # the ipods are twmpting, but I have faith in Rockbox 06.10.04 # rockbox rulez but the hardware is limited 06.10.07 # the display is too small 06.10.11 # I don't skateboard 06.10.32 # a bigger display would be excellent 06.39.22 Join OliverKlozoff [0] (whatsit2u@user-2inimbh.dialup.mindspring.com) 06.39.23 Quit Stevie-O (Read error: 54 (Connection reset by peer)) 06.40.14 # stevie? 06.45.17 # he ain't here no more 06.45.47 # I though he was also OliverKlozoff. 06.48.04 # * OliverKlozoff wonders if anybody's said that out loud yet 06.48.22 # yeah, yeah, we get it 06.48.43 # know anything about electricty? 06.49.03 # electricity? 06.49.08 # yeah. 06.49.14 # population 1820 06.49.34 # the archos batter connects tot the case. I'm wondering why that's ok. 07.11.51 # it's OK because archos doesn't care about their product? 07.14.15 # erm. 07.14.38 # w2k won't let me format a drive >32gb 07.14.46 # yes? 07.14.53 # that's documented somewhere 07.15.12 # yes, it's by freakibg design!! 07.15.19 # yes 07.15.22 # bill knows freaking best 07.15.33 # I'm uncertain as to what design they're referring to 07.15.37 # so use mkdosfs 07.15.55 # will that do fat32 07.15.58 # ? 07.16.01 # ... yes 07.16.05 # use -F 32 07.16.09 # not fat16 07.16.30 # not in cygwin. 07.16.41 # is there a cygwin build? 07.17.19 # what do you mean not in cygwin? 07.18.25 # it's not in my cygwin path 07.18.38 # so I assume it doesn't exist 07.19.08 # ... 07.19.15 # you have to GET IT and COMPILE IT 07.19.24 # oh. 07.19.26 # right 07.19.44 # crap 07.21.14 # you know 07.21.16 # i swear 07.21.21 # these people are fucking worthless 07.22.26 # which? 07.23.06 # who? 07.23.07 # the people who have webpages mentioning that 'by design Windows 2000/XP won't format a drive over 32gb' 07.23.21 # instead of say, supplying a damn program that WILL 07.25.09 # i say .. thats their own fault for using windows ;) 07.25.47 # yeah, it's my own damn fault. 07.25.50 # ahem 07.26.15 # but by design. asses. 07.26.50 # I can't boot 98, it won't see the usb drive. 07.26.52 # i think you mean 'by brain damage' 07.26.56 # http://www.han.de/~jum/mkdosfs/ 07.28.00 # there ye go 07.28.07 # thank you oliver! 07.28.17 # yw. 07.28.19 # you google better than do I! 07.28.35 # * earHurts has 5 tabs open 07.28.42 # all googling 07.30.39 # the hell of it is, windoze went through the entire 55gb -- BEFORE it complained about the size. 07.30.41 # i've got practice 07.30.48 # HAHAHHAA 07.30.51 # the archos got really, really hot. 07.30.52 # you're kidding 07.31.01 # nope 07.31.22 # omfg 07.31.24 # took nearly an hour even with usb 2.0 hi speed 07.31.26 # you should email microsoft 07.31.54 # how do i attach a clue stick to email in outlook? 07.32.01 # im not sure 07.32.31 # I use Mozilla 07.32.32 # kidding 07.32.50 # ;) 07.33.15 # have you seen the latest screenshawts? 07.36.01 # of mozilla mail? 07.36.33 # mozilla is sloww 07.36.46 # lol, no 07.36.49 # http://www.qrpff.net/~stevie/jbremu/revelation.jpg 07.36.51 # does it allow skins? I never like netscape mail's look 07.37.08 # mmm emulator 07.38.01 # eww windows though 07.38.08 # usb working? how do I attach a cable to the emu? ;) 07.38.09 # I want an emu for linux 07.38.22 # earHurts: actually that was usb not working 07.38.27 # it was stuck on 'on' mode 07.38.30 # i want stevie to make biaries available 07.38.40 # sweet, stevie 07.38.43 # http://www.qrpff.net/~stevie/jbremu/fixedadc.jpg <- fixed ADC 07.38.50 # shit 07.39.01 # mkdosfs is done? 07.39.06 # * thu shudders at the windows interface 07.39.13 # how can you switch around all that mess? 07.39.21 # did it not physically write the disk? 07.40.27 # earHurts: your format was really going overkill 07.40.27 # thu: alt+tab 07.40.32 # how many times? :P 07.40.37 # a lot 07.40.45 # hehe. fixedadc is what I just saw for real 07.40.52 # http://www.qrpff.net/~stevie/jbremu/charged.jpg 07.41.06 # wait 07.41.13 # you ran it and you got that message? 07.41.18 # Oliver, I think I missed your last transmission 07.41.26 # hmmm 07.41.36 # yeah. after I added the new disk 07.41.41 # I wonder if Z or Linus have ever really used it 07.41.50 # http://www.qrpff.net/~stevie/jbremu/charged.jpg 07.42.37 # I wonder if mkdosfs has a bug 07.42.41 # * OliverKlozoff wouldn't be all that shocked 07.43.46 # windows sees the volume, with the right size, 55gb 07.44.06 # now we copy >20 gb to it. 07.44.43 # http://www.qrpff.net/~stevie/jbremu/charging.jpg 07.44.52 # chkdsk? 07.45.10 # good idea 07.45.33 # then we reformat M: and Z: into a single drive. 07.45.47 # I just copied Z/*.* to I: 07.45.57 # mark and zibowski? 07.46.02 # I copy m: to archos 07.46.10 # music and zips 07.46.34 # then I have 40gb on the expanded M 07.46.43 # to 'mirror' the archos 07.47.26 # mk 07.47.39 # mk? 07.47.44 # mk 07.47.58 # I need the src to daemontools 07.48.20 # dunno what daemontools is 07.48.32 # that's OK, I do 07.48.33 # :P 07.48.40 # chkdsk says the new volume is RAW?? 07.48.40 # it involves my emulator 07.49.43 # so i thought 07.51.36 # i can't say i really get the point of an emulator for the archos.. but im just glad it makes ppl happy :) 07.52.25 # will make debugging easier 07.52.36 # shrugs 07.52.50 #