Session Start: Tue Apr 20 00:00:00 2010
Session Ident: #glitchpc
[00:00] * Now talking in #glitchpc
[00:00] * Topic is 'Welcome to #glitchpc chat. Profanity, trolls, and impersonation are not welcome here. Street1 has become a Silent Keyboard. http://www.legacy.com/obituaries/savannah/obituary.aspx?page=lifestory&pid=139870551'>
[00:00] * Set by jacky on Tue Mar 02 11:03:23
[03:34] * Guest55762 is now known as Mulreay
[06:09] * pottsi (Mibbit@pottsi.staff.mibbit.net) has joined #glitchpc
[06:39] * Mulreay (mulreay@7E84C309.A34D3407.C48A7639.IP) Quit (Quit: Smoke me a Kipper I'll be back for breakfast!)
[08:28] * sonicrules1234 (sonicrules@mib-6494DB2B.lsanca.dsl-w.verizon.net) has joined #glitchpc
[08:33] * sonicrules1234 pokes BC_Programming
[08:58] * pottsi (Mibbit@pottsi.staff.mibbit.net) Quit (Quit: http://www.mibbit.com ajax IRC Client)
[09:11] * pottsi (Mibbit@pottsi.staff.mibbit.net) has joined #glitchpc
[09:14] * pottsi (Mibbit@pottsi.staff.mibbit.net) Quit (Quit: http://www.mibbit.com ajax IRC Client)
[09:14] * pottsi (Mibbit@pottsi.staff.mibbit.net) has joined #glitchpc
[09:30] * jacky (the_kink@mib-A14E492C.slsbmd.east.verizon.net) has joined #glitchpc
[09:30] * ChanServ sets mode: +o jacky
[09:32] <sonicrules1234> Ohai jacky
[09:32] <@jacky> sonicrules1234: Hello
[10:06] * pottsi (Mibbit@pottsi.staff.mibbit.net) Quit (Quit: http://www.mibbit.com ajax IRC Client)
[10:30] <@jacky> be back later
[10:30] * jacky (the_kink@mib-A14E492C.slsbmd.east.verizon.net) has left #glitchpc
[11:04] * sonicrules1234 (sonicrules@mib-6494DB2B.lsanca.dsl-w.verizon.net) Quit (Quit: G2G, tutor is here)
[11:12] * jacky (the_kink@mib-A14E492C.slsbmd.east.verizon.net) has joined #glitchpc
[11:12] * ChanServ sets mode: +o jacky
[12:28] * jack_test (the_kink@mib-A14E492C.slsbmd.east.verizon.net) has joined #glitchpc
[12:30] * jacky (the_kink@mib-A14E492C.slsbmd.east.verizon.net) Quit (Ping timeout)
[12:30] * jack_test is now known as jacky
[12:30] * ChanServ sets mode: +o jacky
[12:47] * Calum (Mibbit@mib-1B5B96EA.leic.cable.ntl.com) has joined #glitchpc
[12:47] * ChanServ sets mode: +o Calum
[12:47] <@Calum> hey guys
[12:49] <@jacky> Calum: Hello
[12:49] <@jacky> Good afternoon(evening)
[12:49] <@jacky> as usual, I'm soon to be leaving for a while.. heheeh
[12:50] <@jacky> notice how much faster my words get to you, today?
[12:50] <@jacky> :)
[12:50] <@jacky> :)
[12:51] <@Calum> good eening (afternoon)
[12:51] <@Calum> *evening...typing not up to scratch heh
[12:51] <@Calum> heh, machine up and running?
[12:52] <@jacky> I'm on it now.
[12:52] <@jacky> here's your laugh for today
[12:52] <@jacky> ready?
[12:52] <@jacky> heheeh
[12:52] <@jacky> 
[12:52] <@Calum> sure
[12:52] <@jacky> stayed up too late... lots to do... organize, learn, figure out
[12:52] <@jacky> of course
[12:52] <@jacky> decided to run memtest, overnight
[12:52] <@jacky> like we'd talked about
[12:53] <@jacky> did that... booted it.. watched it start
[12:53] <@jacky> decided to switch off monitor
[12:53] <@jacky> no need to leave it on
[12:53] <@jacky> went to bed
[12:53] <@jacky> woke up at normal time...
[12:53] <@jacky> couldn't get back to sleep
[12:53] <@jacky> so... I got up
[12:53] <@jacky> a little punchy... but hey... I've done it before
[12:53] <@jacky> heh
[12:53] <@jacky> go to check machine
[12:53] <@jacky> can't get monitor on
[12:53] <@jacky> !!
[12:54] <@jacky> all sorts of things go trhough my head
[12:54] <@jacky> maybe the bios had some sort of powermanagement stuff... heck, I don't know...
[12:54] <@jacky> and.. I suppose it was instinctive habit...
[12:54] <@jacky> I hit the ESC key
[12:54] <@jacky> boing!
[12:54] <@jacky> I heard it reboot
[12:54] <@Calum> hehe
[12:54] <@jacky> sigh....
[12:55] <@jacky> finally, I found the switch. It's right behind the damn indicator light
[12:55] <@jacky> of course... all the records.... gone
[12:55] <@jacky> so... I'll be running it again tonight, I guess
[12:55] <@jacky> heheheh
[12:55] <@Calum> that's typical heh....I've done similar things before
[12:55] <@jacky> might as well laugh about it...
[12:56] <@Calum> it's either that or cry :)
[12:56] <@jacky> I ran OCCT for no longer than 10 to 12 minutes, so far
[12:56] <@jacky> I didn't try to digest it's options yet
[12:56] <@jacky> just ran it, as it was
[12:56] <@Calum> cool
[12:56] <@jacky> no.. warmer
[12:56] <@jacky> hehehee
[12:56] <@Calum> heh
[12:56] <@Calum> temps ok?
[12:56] <@jacky> get this... yesterday... idle was around 32C
[12:56] <@jacky> today, it is around 27 28
[12:56] <@jacky> like right now
[12:56] <@jacky> isn't that odd?
[12:56] <@jacky> anyway
[12:57] <@jacky> I think it slowly crept up to 40C and leveled off
[12:57] <@jacky> how long woul dyou expect it to need to run, to level off at max temp to be attained?
[12:57] <@Calum> different ambient temps maybe? Anyway, 40C or so sounds great
[12:57] <@Calum> normally 5-10 minutes
[12:57] <@jacky> how long do you recommend, when testing a new machine?
[12:57] <@Calum> if it seemed to level off at 40C I wouldn't imagine it creeping higher, not by any significant amount
[12:58] <@Calum> well, as you're running at stock speeds and you (will) have tested the RAM, an hour should be more than enough
[12:58] <@jacky> oh.. ok
[12:58] <@jacky> and.. what am I lookin gfor?
[12:58] <@jacky> is it obvious?
[12:58] <@Calum> I go overkill on testing things though heh
[12:59] <@Calum> yes, if it fails the red and green buttons will flash, and it will say error detected
[12:59] <@jacky> what is an hour then? normal or overkill?
[12:59] <@Calum> overkill
[12:59] <@jacky> ok. heh
[12:59] <@jacky> any config'ing you recommend
[12:59] <@jacky> or just click "On" ?
[13:00] <@Calum> there aren't any options you'd need to change, just hit the green button and let it go ahea
[13:00] <@Calum> *ahead
[13:00] <@jacky> I can't seem to get into a lot of it anyways...
[13:00] <@jacky> cpu:occt is where it starts
[13:00] <@jacky> and I can't get into "options" for example
[13:00] <@jacky> is there a trick to it?
[13:01] <@Calum> no trick...should just go right in, that's odd
[13:01] <@jacky> wait.. it is running now... could that hold it back
[13:01] <@jacky> brb
[13:01] <@jacky> phone...
[13:01] <@jacky> sorry
[13:01] <@Calum> if it;s running a test, you can't access options, no. And np
[13:01] <@jacky> wrong num
[13:01] <@jacky> brb
[13:03] <@jacky> ok... now it is just the gpu tests (2) that I can't get into.. and I seem to remember during install, that it said I didn't have enough gpu to be able to use it
[13:03] <@jacky> refresh me... what is linpack ?
[13:03] <@jacky> I think you told me once...
[13:04] <@Calum> linpack is a more intensive test, it stresses the CPU more than anything else
[13:04] <@jacky> which do you run, for an hour?
[13:04] <@Calum> if you can't access the GPu tests, you most likely just need to update DirectX, that's usually the issue
[13:05] <@Calum> Either would be fine...I ran Linpack on mine because I needed to test for max temperature and because I was overclocking
[13:05] <@jacky> would that.. Direct X ... have been part of the latest drivers?
[13:05] <@jacky> ok on either
[13:05] <@Calum> nope, it's a separate download/update
[13:05] <@jacky> I need to fill you in on drivers
[13:05] <@jacky> remember.. that I'd said that I had trouble with the ones we d/l'd?
[13:05] <@jacky> I paid attention this time
[13:05] <@Calum> ah right
[13:05] <@jacky> I used Macrium, and put back the base install
[13:05] <@jacky> and started again
[13:06] <@jacky> installed chipset, vga and lan... from the downloads, ok
[13:06] <@jacky> it is the sound driver that won't install
[13:06] <@Calum> ah
[13:06] <@jacky> says that it can't find the device
[13:06] * camerongray (camerongra@mib-71D78700.plusnet.pte-ag2.dyn.plus.net) has joined #glitchpc
[13:06] <@jacky> the one on the CD.. .installs fine though
[13:06] <@Calum> interesting....
[13:06] <@jacky> and.. I thought I had rather low volume... until about an hour ago... whamo! it came up
[13:06] <@Calum> hi cameron
[13:06] <@jacky> dunno...
[13:06] <@jacky> camerongray: Hello
[13:07] <@jacky> Calum: also need to fill you in on memtest
[13:07] <@jacky> we left off.. at using slots 1 and 3, correct?
[13:07] <@Calum> yes
[13:07] <@jacky> I ran CPU-Z and something caught my eye
[13:07] <@jacky> Single channel mode
[13:07] <@jacky> not in dual chan mode
[13:07] <@jacky> :(
[13:07] <@jacky> so... I moved it back to 1 and 2
[13:07] <@jacky> and... that put it in dual chan mode
[13:08] <@jacky> so.. now I'm back to thinking that the markings on mb and color of slots is correct, and not the manual
[13:08] <@jacky> heheehe
[13:08] <camerongray> hi guys
[13:08] <@Calum> heh...how weird
[13:08] <@jacky> and... ran memtest for one pass worth... and it passed.. that was early yesterday
[13:08] <@jacky> that means... (what changed?).... that I'm thinking that your advice on the ram voltage was the key
[13:08] <@jacky> what do you think?
[13:09] <@Calum> could well be, yes...odd that it would work in the other slots, somehow dual/single channel must affect the voltage requirements but I have no idea why or how.
[13:09] <@jacky> it worked... that is, didn't error... but defeated the dual chan mode
[13:10] <@jacky> maybe it was "right on the edge" and dual chan mode put it over
[13:10] <@jacky> dunno
[13:10] <@Calum> maybe
[13:10] <@jacky> but, it is one to chalk up and learn
[13:10] <@jacky> maybe someday, it will save you some time and worry
[13:10] <@jacky> heheeh
[13:10] <@Calum> heh
[13:10] <@jacky> check this out: http://www.newegg.com/Product/Product.aspx?Item=N82E16813131398
[13:10] <@jacky> and read what is the very first remark
[13:10] <@jacky> he didn't say what KIND of mem though
[13:10] <@jacky> maybe I was lucky, after all... eh/
[13:10] <@jacky> ?
[13:11] <@Calum> interesting....
[13:11] <@jacky> If you are not using 1.5v memory, you MUST CHANGE THE VOLTAGE IN BIOS or you will burn through several $100 in memory sticks before you figure it out.
[13:11] <@jacky> that?
[13:11] <@jacky> right
[13:11] <@jacky> you saw it?
[13:11] <@Calum> yes
[13:11] <@jacky> just to be sure we saw the same thing
[13:11] <@jacky> I wonder what voltage his was, before he changed it?
[13:11] <@jacky> I mean.. I guess he too, was on Auto
[13:11] <@Calum> weird that he knows enough to build a machine but not to change the bios.....
[13:12] <@jacky> I didn't get that from it
[13:12] <@Calum> I would chalk that up to someone not having a clue, to be honest. Want my guess as to what happened?
[13:12] <@jacky> apparently he did change it, just not as the very first thing
[13:12] <@jacky> sure.. love to hear your comments
[13:13] <@Calum> I'd guess he clocked the memory up, and didn;t change voltage from auto...it overvolted the memory and burnt it out. Or....he means "burn through" as in "buy new kits" as whatever he had wasn't working
[13:14] <@jacky> Yes.. "burn through" means "to ruin"
[13:14] <@jacky> and.. I don't know why he says no way to set timing
[13:14] <@jacky> wait!
[13:14] <@jacky> I do know
[13:14] <@jacky> it is off screen
[13:14] <@jacky> you must scroll down
[13:14] <@jacky> one of the few, in setup, like that
[13:14] <@jacky> I missed it a few times, too
[13:14] <@jacky> want to bet?
[13:14] <@jacky> heheheeh
[13:15] <@Calum> heh, could well be
[13:15] <@jacky> questions on occt
[13:15] <@Calum> (Mibbit is lagging badly again for me, sorry)
[13:15] <@jacky> "monitoring"
[13:15] <@jacky> cpu 1 and 2
[13:15] <@jacky> what *is* that number?
[13:16] <@jacky> they are both exactly the same, and when they change a bit, they do it at the same time... staying exactly the same
[13:16] <@Calum> it's the temp of each core
[13:16] <@Calum> I'd guess, anyway....
[13:16] <@jacky> *exactly* the same?
[13:16] <@jacky> always?
[13:16] <@jacky> and several degrees diff from speedfan's report
[13:17] <@Calum> well, that does seem odd, yes
[13:17] <@jacky> by the way... countdonw timer is down to 47 min
[13:17] <@jacky> so I guess it has been running for 12 min?
[13:17] <@jacky> speedfan says 43C
[13:17] <@jacky> on 1
[13:17] <@jacky> and
[13:17] <@Calum> sems like it yes
[13:17] <@jacky> 26 on the other
[13:17] <@jacky> oh!
[13:17] <@jacky> that's what I wanted to ask you
[13:18] <@jacky> how do you make occt do the other processor?
[13:18] <@Calum> it should do it automatically
[13:18] <@jacky> need to let it run longer then?
[13:19] <@jacky> you said something about blinking lights... the green light blinks steadily, all the time. Normal?
[13:19] <@Calum> OCCT does vary the usage...it will go to 0%, 25%, and 100%, maybe other %s as well...that might be what you're seeing in terms of temps
[13:19] <@Calum> yes, normal
[13:19] <@jacky> core 2 has never gone up yet
[13:19] <@jacky> at all
[13:20] <@Calum> weird
[13:20] <camerongray> jacky: Sorry to interrupt but what is the code to change your nickserv password?
[13:20] <@jacky> I don't like 'weird'... not at this stage
[13:20] <@jacky> heheeheh
[13:20] <@jacky> camerongray: brb with it
[13:21] <@Calum> heh...well I don't know what else to say, OCCT has always just worked for me and stressed all available cores
[13:21] <@jacky> /msg nickserv help set password
[13:21] <@jacky> will get you brief help on it
[13:21] <camerongray> thanks
[13:21] <@jacky> that'll save you digging through the menus
[13:21] <@jacky> Calum: heheeh
[13:21] <@jacky> ok... I'll keep messing with it
[13:22] * camerongray (camerongra@mib-71D78700.plusnet.pte-ag2.dyn.plus.net) Quit (Quit: )
[13:22] <@jacky> I do need to find some way.. .to find out that the second core works though
[13:22] <@BC_Programming> whats OCCT?
[13:22] <@jacky> hello BC_Programming
[13:22] <@BC_Programming> hello ppl
[13:22] <@Calum> try the Linpack test on OCCT...just in case
[13:22] <@jacky> Calum: ok
[13:22] <@jacky> for this core.. it seems to have leveled off at 43C today
[13:23] <@Calum> BC - OCCT is a stress test, or to be more accurate a few, in one application
[13:23] <@jacky> stopping that test now
[13:23] <@jacky> and temp is coming down already
[13:23] <@BC_Programming> Calum: thx
[13:23] <@Calum> np
[13:23] <@Calum> yeah, I;d expect it to drop quickly
[13:23] <@jacky> BC_Programming: you got my pm that I left you?
[13:23] <@jacky> hehehe
[13:24] <@Calum> when Linpack puts it to 100% load...watch it shoot up heh
[13:24] <@jacky> running
[13:25] <@jacky> in Taskmanager... should I be able to see it on a graph in there, too?
[13:25] <@BC_Programming> jacky: oh didn't see it till you mentioned it, heh
[13:25] <@Calum> yes
[13:25] <@jacky> BC_Programming: I left not long after.. never said a word
[13:25] <@jacky> heheeh
[13:25] <@jacky> Calum: ok.. will check
[13:26] * camerongray (camerongra@mib-71D78700.plusnet.pte-ag2.dyn.plus.net) has joined #glitchpc
[13:27] <@jacky> Calum: well.. if I'm understanding task manager correctly, it is loading both cpus at the same time
[13:27] <@Calum> is the temp going up though?
[13:27] <@jacky> yet speedfan is not budging... so, perhaps speedfan just can't report on this chip?
[13:28] <@Calum> maybe so...or maybe one temp sensor is stuck, it happens
[13:28] <@jacky> temp1 is now back up... 44 this time
[13:28] <@jacky> temp 2... still on 26
[13:28] <@Calum> has it ever budged from 26?
[13:28] <@jacky> the temp sensor is internal, in the cpu?
[13:28] <@Calum> yes as far as I know
[13:28] <@jacky> good question... I will pay more attention now
[13:28] <@jacky> I don't *think* so though
[13:29] <@Calum> it may start reporting at a high enough temp...it may not. Not heard of this happening with AMD's but it was fairly common with one of Intel's lines
[13:29] <@Calum> don't worry about it though, the second core will be within 5C, tops, of the other core
[13:29] <@jacky> that one core would not report at all/
[13:29] <@BC_Programming> my core 1 and 2 temps are nearly 10 degrees lower then core 3 and 4
[13:29] <@Calum> that the sensor would be stuck
[13:30] <@jacky> I just want to be sure that the second is working, is all.
[13:30] <@jacky> not sure how to go about that
[13:30] <@Calum> task manager confirms that....you could also run, say, 7-zip's benchmark, with 1 thread then with 2
[13:30] <@BC_Programming> run a couple programs that are working in the bg, and then check task manager
[13:30] <@Calum> if the score goes way up, you can confirm the second core is working
[13:30] <@jacky> as for the feel of the machine... I can't tell it... when it hits 100%.. .no diff here.. no lag at all.. Should there be?
[13:31] <@Calum> not necessarily
[13:31] <@jacky> wow
[13:31] <@BC_Programming> depends, could be 100% of just one CPU
[13:31] <@jacky> heeh.. not used to this
[13:31] <@BC_Programming> heh, I know how you feel sorta
[13:31] <@Calum> and me
[13:31] <@jacky> Calum: is the benchmark built into 7 zip?
[13:31] <@BC_Programming> I felt the same way both when I switched to the 1.6ghz from my K6-2 as well as when I switched to my quad core
[13:32] <camerongray> Sorry to barge in but you could use the speedfan chart. It will show small changes - e.g. 23.1 to 23.4 - That is too small to make an effect on the main screen
[13:32] <@Calum> yes
[13:32] <@jacky> just installed it a bit ago
[13:32] <@jacky> brb
[13:33] <@jacky> hmm..
[13:33] <@jacky> occt says Error detected
[13:33] <@jacky> should I have not played with 7zip?
[13:33] <@Calum> not at the same time as running OCCT...
[13:33] <@jacky> ok
[13:33] <@jacky> ok
[13:33] <@jacky> heheh
[13:35] <@jacky> ok..
[13:35] <@jacky> when I do 1 thread... with 7 zip benchmark
[13:35] <@jacky> it appears on both graphs, in task manager
[13:36] <@Calum> as using around 50% total, right?
[13:36] <@jacky> it is all over.. up and down...
[13:36] <@jacky> but average?
[13:36] <@jacky> by eye?
[13:36] <@jacky> ok... around 50%
[13:37] <@Calum> cool...that's normal then, it's just spread across the cores but is in effect using just one
[13:37] <@Calum> change it to 2 threads, and it should use around 100
[13:37] <@jacky> brb
[13:37] <@BC_Programming> heh, jacky is obsessive compared to me- I just check task manager, see the right number of CPU usage charts, and call it a day, :P
[13:38] <@Calum> heh
[13:38] <@jacky> Calum: yep.. still some up and down... but much closer to 100%
[13:38] <@Calum> cool
[13:38] <@jacky> BC_Programming: I had a scare.. with bad components
[13:38] <@BC_Programming> I see
[13:38] <@jacky> I don't want to miss something else, y'know?
[13:38] <@jacky> sigh
[13:39] <@jacky> 7zip does not seem to cause as much heat though
[13:39] <@Calum> it wouldn't
[13:39] <@jacky> ok
[13:40] <@jacky> ok... I need to get going, to take care of some things...
[13:40] <@jacky> Calum: will you be around tomorrow?
[13:40] <@Calum> I should be
[13:40] <@jacky> if I don't flub the over night memtest again
[13:40] <@jacky> I'll fill you in
[13:40] <@jacky> heh
[13:40] <@Calum> heh
[13:40] <@jacky> Calum: oh.. what I was saying to BC a while ago
[13:41] <@jacky> Ralphy appeared on freenode
[13:41] <@Calum> hah
[13:41] <@jacky> in the #eggdrop chan
[13:41] <@jacky> asking questions
[13:41] <@BC_Programming> yeah he's some masterhacker
[13:41] <@jacky> he probably doesn't know it, bu tthe guy that was answering him
[13:41] <@jacky> I think he owns www.egginfo.com
[13:41] <@jacky> or one of them, anyway
[13:41] <@jacky> and, I've talked to him.. goes by "simple"... he's a very ok guy, and smart
[13:42] <@jacky> Ralphy was on his good behavior, I guess
[13:42] <@jacky> and, I think he spied me
[13:42] <@jacky> spoke to me twice
[13:42] <@jacky> I never said a word there, today
[13:42] <@jacky> :)
[13:42] <@BC_Programming> haha
[13:42] <@Calum> heh
[13:42] <@BC_Programming> SNM was here a few days ago, haven't laughed that hard in a long time
[13:43] <@BC_Programming> there was a long time that I just responded to him with "yes" or "no"
[13:43] <@jacky> Justjoe has not been on, since April 8
[13:43] <@jacky> apparently, lc pissed him off, somehow
[13:43] <camerongray> I remember SNM in my chan, I actually bookmarked the log it was so funny
[13:43] <@jacky> heh
[13:43] <@BC_Programming> oh yeah
[13:44] <@BC_Programming> it was in codingcafe, not glitchPC
[13:44] <@jacky> Catch you all later. Calum, and all : Thanks
[13:44] <@jacky> :)
[13:44] <@BC_Programming> cya
[13:44] * jacky (the_kink@mib-A14E492C.slsbmd.east.verizon.net) has left #glitchpc
[13:56] * Calum (Mibbit@mib-1B5B96EA.leic.cable.ntl.com) Quit (Quit: http://www.mibbit.com ajax IRC Client)
[14:25] * camerongray (camerongra@mib-71D78700.plusnet.pte-ag2.dyn.plus.net) Quit (Quit: )
[15:53] * pottsi (Mibbit@pottsi.staff.mibbit.net) has joined #glitchpc
[17:28] * jacky (the_kink@mib-A14E492C.slsbmd.east.verizon.net) has joined #glitchpc
[17:28] * ChanServ sets mode: +o jacky
[17:33] * GlitchPC (Mibbit@mib-3E0BE34.hsd1.nj.comcast.net) has joined #glitchpc
[17:33] * ChanServ sets mode: +q
[17:33] * ChanServ sets mode: +o GlitchPC
[17:34] <@GlitchPC> BC_Programming, you here?
[17:34] <@GlitchPC> Hello, jacky
[17:35] <@jacky> oh I see how it is... him, you ask... me, you just assume
[17:35] <@jacky> I see
[17:35] <@jacky> <g>
[17:35] <@GlitchPC> heh
[17:35] <@BC_Programming> oh I'm here
[17:35] <@GlitchPC> BC, I think I have it whipped
[17:35] <@jacky> there you go!
[17:35] <@jacky> hehehe
[17:35] <@GlitchPC> I'm now showing
[17:35] <@BC_Programming> good
[17:35] <@jacky> (back under my rock....)
[17:35] <@GlitchPC> lol
[17:36] <@GlitchPC> Going to rename the forum Chat link up top to IRC Chat
[17:36] <@BC_Programming> ok
[17:36] <@GlitchPC> The link in the toolbar will be named forum chat
[17:37] <@GlitchPC> Guests cannot use the toolbar chat...and you should be able to IM through the chat window
[17:37] <@BC_Programming> ok
[17:37] <@GlitchPC> nice article btw
[17:37] <@BC_Programming> yeah I just muddled through getting those games to work
[17:37] <@BC_Programming> huge PITA, couldn't find anything online about it... but now there is, heh
[17:46] * GlitchPC (Mibbit@mib-3E0BE34.hsd1.nj.comcast.net) Quit (Quit: http://www.mibbit.com ajax IRC Client)
[18:05] * Mulreay (mulreay@8D2B375A.A34D3407.C48A7639.IP) has joined #glitchpc
[18:16] * pottsi (Mibbit@pottsi.staff.mibbit.net) Quit (Quit: http://www.mibbit.com ajax IRC Client)
[19:59] * hello2u (WillieTheF@mib-DB5A063A.washdc.east.verizon.net) has joined #glitchpc
[20:00] * jacky (the_kink@mib-A14E492C.slsbmd.east.verizon.net) has left #glitchpc
[20:50] * hello2u (WillieTheF@mib-DB5A063A.washdc.east.verizon.net) Quit (Quit: )(Quit: )(Quit:)(Quit: "Outside of a dog, a book is man?s best friend. Inside of a dog it?s too dark to read." - Groucho Marx)