**** BEGIN LOGGING AT Sun Jan 26 02:59:59 2014 Jan 26 04:20:09 Hi i have a doubt unrelated to maemo. What is Libc? Jan 26 06:08:41 ~ping Jan 26 06:08:44 ~pong Jan 26 06:27:02 ~pong Jan 26 06:27:04 ~ping Jan 26 06:27:20 hmm Jan 26 06:27:30 2 instances of infobot running in the same channel... Jan 26 06:36:06 DocScrutinizer05: Hi. Were you the fellow who wrote dbus-scripts? Can I ask how to trigger a script when I get a SMS? I tried putting text into /etc/dbus-scripts/dbus-scripts-settings but it doesn't seem to work, although it does work for a trigger of "do this when the keyboard slides open or closed". Jan 26 06:36:49 no Jan 26 06:37:05 I just used dbus-scripts Jan 26 06:37:43 well, I dunno the dbsu msg format for an inbound SMS Jan 26 06:38:11 Oh. Ok. How do you know what to put to trigger for a given trigger? E.g. what did you use as your trigger for dbus-scripts, and how did you find that info? Jan 26 06:38:41 I'm reading the available DBus signals at http://wiki.maemo.org/N900_dbus , but am not sure how to translate that to something that dbus-scripts can understand. Jan 26 06:38:41 I use dbus-monitor and spot the message I'm interested in Jan 26 06:39:06 DocScrutinizer05: Oh, dbus-monitor. I was using dbus-scripts --debug, but maybe that's not the format I'm interested in. Jan 26 06:39:11 Will try that. Thx. Jan 26 06:39:17 yw Jan 26 06:42:52 wish I could tee the output of dbus-monitor to file and also watch it on standard output. Jan 26 06:43:05 But I don't see the output until the tee is done. Jan 26 06:51:17 So, the output of dbus-monitor looks like "signal sender=:1.22 -> dest=(null destination) serial=2088 path=/org/freedesktop/Telepathy/Connection/ring/tel/ring/text23; interface=org.freedesktop.Telepathy.Channel.Type.Text; member=Received" How does that translate to what I put in dbus-scripts? Jan 26 06:51:49 I tried "/home/user/sh/logdate.sh[ a test script I wrote] * * org.freedesktop.Telepathy.Channel.Type.Text Received *" but that didn't seem to do anything Jan 26 07:01:28 looks about right though Jan 26 07:02:37 compare to slide-open Jan 26 07:05:25 "/etc/dbus-scripts-scripts/playswoosh * * org.freedesktop.Hal.Device Condition ButtonPressed cover" Jan 26 07:06:08 is your script 755? Jan 26 07:06:36 Maxdamantus: I'm not sure eMMC image contains other partitions Jan 26 07:07:05 ~jrtools Jan 26 07:07:08 I think they're created on the first boot by Maemo Jan 26 07:07:10 jrtools is probably http://wiki.maemo.org/User:Joerg_rw/tools Jan 26 07:07:36 http://wiki.maemo.org/User:Joerg_rw/tools#increase_size_of_.2Fhome_-_if_you_like_that Jan 26 07:08:00 mydocs, home, swap Jan 26 07:08:10 Oh Jan 26 07:23:29 Yeah, I saw that partitioning scheme description. Jan 26 07:24:11 So I guess the included FAT32 filesystem is meant to be the prefix of the target eMMC device. Jan 26 07:25:48 and they made it 250 MiB to make sure they had enough zeroes. Jan 26 07:41:05 assuming when you plug the N900 into a USB port while the OS is normally running, it acts as a USB mass storage device for the SD card or something, what does it use to implement that? Jan 26 07:41:25 or does it not do that? Jan 26 07:47:26 * Maxdamantus doesn't get much useful stuff when Googling something like `linux usb mass storage client` Jan 26 07:48:29 but would it be implemented in the kernel, or in userspace, or is there a special chip that acts as the mass storage device client using the SD card, so the software doesn't have any control over it? Jan 26 07:49:11 g_file_storage Jan 26 07:50:00 Sounds like a starting point, thanks. Jan 26 07:50:06 (It's a kernel module) Jan 26 07:50:41 but not one in Linus' source tree? Jan 26 07:53:07 seems to be referred to briefly there. Jan 26 07:54:14 Ah, it was renamed to g_mass_storage Jan 26 07:54:24 USB_MASS_STORAGE Jan 26 07:54:33 (the config option) Jan 26 07:55:11 well, replaced by. Jan 26 08:00:14 Hm. Wonder what's special about simulating writable CD drives. Jan 26 08:00:25 maybe they have to use ATA too. Jan 26 08:00:34 (or SCSI) Jan 26 09:34:26 Saw the guy who accidentally mounted something in /usr Jan 26 09:34:31 $ sudo umount /usr Jan 26 09:34:32 -bash: /usr/bin/sudo: No such file or directory Jan 26 09:37:53 in Maemo? Jan 26 09:38:04 there seems to be a busybox binary in /bin Jan 26 09:38:19 /bin/busybox umount /usr Jan 26 09:39:23 oh, nvm, need root. Jan 26 10:38:24 Oorgle! Jan 26 12:47:39 DocScrutinizer05: Sorry, had to put my kid to sleep, and then I went to sleep too. Jan 26 12:48:24 DocScrutinizer05: Do you have anything in your dbus-scripts that is triggered by a connection of some sort, rather than button pressed? E.g. when the phone rings, or when it hooks up to internet wifi, or something? Jan 26 12:49:12 I want to compare your dbus-script-settings to what I see on dbus-monitor or dbus-script --debug. Jan 26 12:50:32 The dbus doesn't seem to generate the same sort of event if I just compare it to slide-open ... in fact, sliding the keyboard open doesn't seem to generate any signal at all on dbus-scripts --debug. I even tried run-standalone.sh dbus-scripts --session --debug to check the session bus instead of the system bus. Jan 26 12:51:28 My script is 755, because it is correctly triggered by the keyboard slideopen (in dbus-scripts) but not by receiving an SMS. Jan 26 13:00:21 sorry, gotta reboot; will be back soon. Jan 26 13:18:32 okay, back. :P Jan 26 13:33:04 kwtm: look here: http://maemo.org/community/maemo-developers/problem_with_dbus-scripts_and_phone-sms/ and here: http://wiki.maemo.org/Phone_control .....search for 'IncomingSegment' Jan 26 14:38:11 xes: Thx for the links. I looked at Phone_control already but will look more closely at the IncomingSegment as you suggest. Jan 26 19:51:48 I know that this is a really weird thing, but is it possible to set up passthrough on the camera through usb? Jan 26 19:51:51 basically turn the n900 into a webcam Jan 26 19:53:24 if you find a usb gadget driver.. Jan 26 19:57:25 cool Jan 26 19:57:31 I'll try to find that Jan 26 20:04:33 prolly easier to pipe a gstreamer stack thru USB-network. Or simply use fuse or whatever remote filesystem to access /dev/camera Jan 27 00:33:44 You won't be able to network /dev/camera. Jan 27 00:34:17 You'd need something that knows how to use /dev/camera on the phone, and something on the other side that knows how to talk to that. Jan 27 00:34:30 Linux doesn't work like Plan 9 :( Jan 27 00:34:56 Silly memory-changing ioctls and stuff. Jan 27 00:44:45 aaah yes Jan 27 00:44:48 right Jan 27 00:44:56 so it's gstreamer then Jan 27 00:46:36 or writing to a "streamable" file on Neo900, and make that file a pipe if you want Jan 27 00:46:54 s/file/file format/ Jan 27 00:46:54 DocScrutinizer05 meant: or writing to a "streamable" file format on Neo900, and make that file a pipe if you want Jan 27 00:47:50 Someone needs to write a Plan 9/Inferno mobile OS. Jan 27 00:47:51 * DocScrutinizer05 wonders if the default mp4 format can get "streamed", i.e. playback start before end of file written and file closed Jan 27 00:48:10 I saw a project that got some basic stuff done for it in Inferno. Jan 27 00:48:35 so they had files you used to make calls and send/recieve SMSes, on some Android phone. Jan 27 00:48:38 inferno sounds concerningly similar to fiasco ;-P Jan 27 00:48:40 and a simple UI for them. Jan 27 00:49:13 Fiasco the thing I've noticed mentioned a few times in trying to figure out Maemo? Jan 27 00:49:22 seems those devels really like that stuff they do, eh? ;-P Jan 27 00:49:45 the firmware images are caled "fiasco image2 Jan 27 00:49:52 s/2/"/ Jan 27 00:49:52 DocScrutinizer05 meant: the firmware images are caled "fiasco image" Jan 27 00:49:56 Right, that's where I saw it. Jan 27 00:50:07 ~flashing Jan 27 00:50:08 [maemo-flashing] http://wiki.maemo.org/Updating_the_tablet_firmware Jan 27 00:50:09 so .. what does "fiasco image" mean? Jan 27 00:50:54 I guess they had an idea of tongue in cheek naming it like "flask" and same time "desaster" Jan 27 00:51:11 well, what does the "fiasco" bit refer to? Jan 27 00:51:21 why would it not be suitable to call it a "maemo image" or something? Jan 27 00:51:30 don't ask me Jan 27 00:51:36 ask Nokia ;-) Jan 27 00:52:17 Wiki mentions there's an L4 microkernel family called "Fiasco" .. probably unrelated. Jan 27 00:52:36 Openmoko called their uBoot moko-dirty, Nokia called theirs NOLO which is about the same in Finnish language I heard Jan 27 00:53:17 moko is something in your nose, in Spanish - that for sure been not intended though Jan 27 00:53:22 Mm .. apparently "nolo" is awkward/embarrassed. Jan 27 00:54:06 * Maxdamantus ymmärrän vähän suomea. Jan 27 00:54:21 ymmärrä* Jan 27 00:54:34 ymmärtää Jan 27 00:54:46 helvetti Jan 27 00:55:01 * DocScrutinizer05 wonders hwy he can't help giggling each time he's seeing such words with lots of ää and ou Jan 27 00:55:01 close enough Jan 27 00:55:23 "kääkättää" Jan 27 00:55:40 works each time :-D Jan 27 00:56:12 höyryjyrrä Jan 27 00:56:16 * Maxdamantus wonders if he spelt that right. Jan 27 00:56:22 Funny word. Jan 27 00:56:23 jyrä Jan 27 00:56:30 again, close enough :-) Jan 27 00:56:40 Kiitos. Jan 27 00:59:09 Nobody would give me a decent answer when I asked why the image bundle was called "fiasco". I think they didn't know as all they said was "well, at this point it /is/ a disaster, right". Jan 27 00:59:54 Heh. Jan 27 01:01:21 Hmm .. maybe I'll see if I can port those guys' Inferno/Android project to N900 and make a better shell for it. Jan 27 01:01:27 some time. Jan 27 01:05:45 thinking about bygone times, it's a shame I didn't make a backup copy for n810's fte tool Jan 27 01:08:23 fte? Jan 27 01:09:31 field test (environment?), a simple tool to monitor power usage of certain components such as gps and display, dump lots of status data etc. Jan 27 01:10:04 yeah, cool stuff. We could use such thing Jan 27 01:10:32 for now best we got is Jan 27 01:10:37 ~bq27k Jan 27 01:10:47 and ~zztop Jan 27 01:11:03 ~bq27k-detail Jan 27 01:11:03 it has been said that bq27k-detail is http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27k-detail2 Jan 27 01:11:11 ~zztop Jan 27 01:11:16 talking of which, doesn't the n900 cssu(-thumb)'s power menu widget use bq27k? Jan 27 01:11:19 ~zzztop Jan 27 01:11:19 hmm... zzztop is - the better and even FOSS powertop - http://wiki.maemo.org/Zzztop Jan 27 01:12:19 power menu widget? Jan 27 01:12:26 power menu power widget Jan 27 01:13:18 if you don't know what I'm talking it's probably because I don't know what I'm talking about Jan 27 01:13:26 well, some system status area applets use the bq27200.ko kernel driver resp the sysnodes it provides. Alas this breaks bme Jan 27 01:14:35 Pali's bme-replacement uses bq27200 too, but it's no problem since it's integrated with bme replacement obviously Jan 27 01:15:05 I haven't really been an active user of n900 from hacker's point of view... I used to use advanced power foo, which annoyingly made the power widget in power menu clickable and I decided to get rid of it, even if the stock widget wouldn't show charge percentage. Jan 27 01:15:24 other battery applets may use sysnodes of direct I2C interface to bq27200 hardware, just like bq27k-detail2 Jan 27 01:15:36 Some time after that I switch to CSSU-thumb, and not too long ago the power widget changed. Now I'm not completely sure which one I have. ;-) Jan 27 01:16:15 sorry, can't help ;-) Jan 27 01:16:41 My original point was that the widget I now have, reports completely bogus "full charge" level. Right now it says the battery is at 1015 mAh, and full charge is at 167 mAh. Jan 27 01:17:03 lol, blame pali Jan 27 01:17:21 obviously it doesn't bother me /that/ much, because it's been like this for maybe a month and I still haven't even looked into it Jan 27 01:17:56 when you start to bother, you might want to calibrate your bq27200 chip Jan 27 01:18:09 I suppose. the last time I did that was two years ago. Jan 27 01:18:10 there's a convenient script for that on my server Jan 27 01:18:37 nect to bq27k-detail2 Jan 27 01:18:41 next* Jan 27 01:19:23 ok, no soooo next: http://maemo.cloud-7.de/maemo5/patches_n_tools/calibrate-bq27k.sh Jan 27 01:19:26 I think it used to take me roughly 80 minutes to drain the battery Jan 27 01:19:51 the script does that overnight while you're sleeping Jan 27 01:20:31 particularly when you switch the screen backlight to "always on" Jan 27 01:21:03 umm, do I want to run the script when I rely on n900 to wake me up? Jan 27 01:21:15 hmm, not really Jan 27 01:21:25 rather wait til next saturday ;-) Jan 27 01:21:33 I mean, when I was doing this manually I had maybe five seconds to connect the charger once power chip was done Jan 27 01:21:50 though the script *should* restart charger and not even reboot the device Jan 27 01:22:18 that's what the script looked like, but based on my previous experience... Jan 27 01:22:30 well, I can wait Jan 27 01:22:35 thanks for the script Jan 27 01:22:36 sure, when you cut through battery in 80min, your headroom after calibration is pretty short Jan 27 01:23:19 with the script you can go for a better and saner maybe 5h to discharge Jan 27 01:23:55 sounds good Jan 27 01:24:01 this should extend the time from calib to shutdown to several minutes Jan 27 01:24:30 I must admit that draining the battery that quickly left kind of wrong Jan 27 01:24:43 felt, even Jan 27 01:24:55 :nod: Jan 27 01:25:12 and calibration isn't really accurate either Jan 27 01:25:20 battery capacity depends on load Jan 27 01:25:33 at least I left the keyboard slider open to help dissipate the heat Jan 27 01:25:36 high load reduces effective capacity Jan 27 01:26:18 maybe I'll give the script a go at work Jan 27 01:26:29 like, on double power consumption your battery doesn't last 1/2 but maybe only 0.4 times as long Jan 27 01:26:43 but before that I'll have to catch some sleep. need to be at work in ~six hours. Jan 27 01:26:56 n8, sleep well Jan 27 01:27:11 any feedback re script welcome Jan 27 01:27:45 oh, right, "fastcharger" here refers to high-amp wall charger? Jan 27 01:28:13 mine says 1.2 amps Jan 27 01:28:21 suffices Jan 27 01:29:07 just nake sure to cd to the dir where bq27200.sh lives before you start the calib cript - it uses relative pathnames to bq27200.sh Jan 27 01:30:08 I think I'll manage with bourne shell scripts :-) Jan 27 01:31:09 in fact, I'm slighly surprised to see no bashisms in there Jan 27 01:31:51 lots of unnecessary semicolons, though Jan 27 01:32:25 anyway, thanks :-) Jan 27 01:33:13 I love ; ;-) Jan 27 01:33:49 actually they are remants from me testing that as a oneliner in N900 xterm Jan 27 01:34:40 when it worked I added a echo ' to left side and a '>calibrate.sh to right Jan 27 01:35:11 and then inserted a bit of formatting but obviously didn't remove the surplus ; Jan 27 01:39:16 actually I should beautify that script a bit, eventually Jan 27 01:39:53 and printing a message about screen going dark and how to switch it on again, just before screen blanks, is a bit ... :o) Jan 27 01:41:22 well, i wrote it for kerio Jan 27 01:41:55 just to demonstarte I know better way to calibrate bq27k chip than estel's method Jan 27 01:42:18 :-D Jan 27 01:53:43 DISPLAY=:2; (for ((x = 0; x < 500; x++)); do (urxvt +rv -bg "#$(for ((x = 0; x < 3; x++)); do echo -n $((echo 'obase = 16'; echo $((RANDOM % 256))) | bc | sed 's/^.$/0&/'); done)" &); done) Jan 27 01:53:47 This is fun. Jan 27 02:03:32 Maxdamantus: fuck you Jan 27 02:04:56 cool Jan 27 02:05:13 if that does what I think it does.. Jan 27 02:05:36 :2 is meant to be a display running Hildon. Jan 27 02:05:44 remove the & and replace that with -e sleep .5 Jan 27 02:06:07 it's a forkbomb otherwise Jan 27 02:06:20 r00t|home: nah, pretty good idea of what goes on. Fork bomb-ish that keeps spawning urxvt with a random bg color riht? Jan 27 02:06:23 right* Jan 27 02:06:28 well, it doesn't grow exponentially, but opening 500 terminal emulators isn't a nice idea really Jan 27 02:06:28 Well, it's not a replicating forkbomb. Jan 27 02:06:41 yeah, that's why I said -ish, since it does end Jan 27 02:06:50 that's still a pain to close out though :P Jan 27 02:07:05 killall urxvt Jan 27 02:07:10 assuming you don't have any others running. Jan 27 02:07:30 rxvt is my main terminal... Jan 27 02:07:39 i did pkill -f \\+rv tho' Jan 27 02:07:46 * Maxdamantus runs everything in tmux, so can just restart the terminal emulator and reattach. Jan 27 02:07:49 (from ssh) Jan 27 02:08:42 r00t|home: you have some serious security issues if you're just running shell code that people paste in irc :P Jan 27 02:08:56 i' tired :P Jan 27 02:09:22 i did look over it, and i saw that it doesn't loop infinitely... but i missed the & at the end because you hid it next to the ) Jan 27 02:09:29 ah Jan 27 02:09:44 s/you/he/ Jan 27 02:09:46 r00t|home meant: i did look over it, and i saw that it doesn't loop infinitely... but i missed the & at the end because he hid it next to the ) Jan 27 02:10:23 and i didn't expect people to post forkbombs on #maemo really... especially dedicated maemo forkbombs... Jan 27 02:14:28 xterm -fg black -bg \#$(printf %x%x%x $((RANDOM%0xff)) $((RANDOM%0xff)) $((RANDOM%0xff))) Jan 27 02:15:04 printf is a shell builtin, unlike bc, and loop unrolled... and why open FIVEHUNDRED of them??? Jan 27 02:16:01 but that can give you colours like #aaaa Jan 27 02:16:21 %02x Jan 27 02:16:46 can alternatively write it again more efficiently with bc/sed. Jan 27 02:17:10 what would be better would be automatically picking a matching high-contrast foreground color Jan 27 02:17:18 meh, cbf Jan 27 02:22:52 also, for such stuff, i usually run Xnest :1 -noreset ... while sleep .1 ;do DISPLAY=:1 xsetroot -solid $(printf \#%02x%02x%02x\\n $((RANDOM%0xff)) $((RANDOM%0xff)) $((RANDOM%0xff))); done Jan 27 02:25:26 for ((z = 0; z < 10; z++)); do echo 'obase = 16'; for ((x = y = 0; x < 3; x++)); do y=$((y*256 + RANDOM%256)); done; echo $y; done | bc | sed 's/^.$/0&/; s/^..$/0&/; Jan 27 02:25:28 s/^...$/0&/; s/^....$/0&/; s/^.....$/0&/;' | while read w; do (xterm -fg black -bg "#$w" &); done Jan 27 02:25:33 meh, got cut off. Jan 27 02:25:45 one bc process, one sed process, no inbuilt printf. Jan 27 02:26:08 cut in half* Jan 27 02:26:46 still silly to use bc and sed when printf will do Jan 27 02:27:15 still don't get why you'd open so many Jan 27 02:27:33 I imagine some people might be inclined to claim that spawning hundreds of terminals with random background colours is already silly. Jan 27 02:28:05 Just to see how much laggier Hildon was with that many windows. Jan 27 02:28:07 the effect might look good... maybe more so if you add a little lsd Jan 27 02:28:23 but it's just running on a computer, not an N900. Jan 27 02:28:56 well, i guess launching 500 terminal emulators will lag pretty much any system, if opened in a loop like that Jan 27 02:29:10 I should try it on my desktop, that'll be a fun test Jan 27 02:29:12 Hm. Didn't lag my system. Jan 27 02:29:17 8 core 4 ghz, 16 gigs ram :P Jan 27 02:29:33 Tekk_: and no mozilla products running, eh? :P Jan 27 02:29:33 4 core 3.6 GHz, 32 gigs ram Jan 27 02:29:41 r00t|home: not unless I need to Jan 27 02:29:52 <-- 2-core 4gig ram Jan 27 02:29:58 <-- goes sit in a corner and cry Jan 27 02:30:09 r00t|home: my laptop is 2 core and 2 gig Jan 27 02:30:21 my Mozilla-based browser is currently using 8.7% of RAM with 179 tabs. Jan 27 02:30:23 mine too... well, one of mine Jan 27 02:30:23 I just happened to upgrade my desktop this winter :) Jan 27 02:30:49 Yeah, two weeks ago I was using a 4-core with 3 GiB of RAM. Jan 27 02:31:09 I had another 1 GiB stick, but the slot on the motherboard is broken. Jan 27 02:31:15 ram's so cheap nowadays... Jan 27 02:31:20 I know. Jan 27 02:31:21 maybe i should upgrade sometime Jan 27 02:31:25 That's why I bought 32 GiB of it. Jan 27 02:31:31 but what for... just so mozilla can eat all the ram... Jan 27 02:31:52 more RAM seems more important to me than a faster X Jan 27 02:32:05 a faster X just means some things get done slightly quicker Jan 27 02:32:19 more RAM means more things can be potentially done (without taking excessive amounts of time) Jan 27 02:32:31 you mean X window system or X as in random system component? Jan 27 02:32:43 X as in a random system component Jan 27 02:32:50 sure Jan 27 02:33:18 actually the last system i bought was an atom with 4gig ram Jan 27 02:34:14 http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dn2800mt.html Jan 27 02:34:55 great system for most general purposes Jan 27 02:36:07 I saw a nice second-hand motherboard the other day that I could use with my previous computer. Jan 27 02:36:22 wonder if I should buy it. Jan 27 02:36:40 Might replace my current Pentium 3 router. Jan 27 02:36:53 my router is a 586... Jan 27 02:38:12 (other advantage of that intel board is, it runs off a single DC power source, notebook supply instead of bulky atx supply) Jan 27 02:38:45 Hmm .. though I was planning on doing something with the parallel port at some point. Jan 27 02:39:11 none of my other computers have parallel ports/headers Jan 27 02:39:14 waht? and even if so, there a re pcie parallel port cards Jan 27 02:39:23 *what Jan 27 02:39:57 seeing if I can use the analogue sticks on this PS2 controller. Jan 27 02:40:54 when it's plugged into a PSX→USB adapter, the analogue just turns off straight away. Jan 27 02:41:01 and the controller doesn't work at all in an actual PS2. Jan 27 02:41:50 maybe I'll just buy a PS3 controller (don't intend on getting a PS3) Jan 27 02:41:52 so just to try it the parport joypad driver Jan 27 02:42:03 *with the Jan 27 02:42:11 I'd like to play Ape Escape again (probably in a PSX emulator) Jan 27 02:42:35 Possibly. Jan 27 02:42:51 There's another utility as well, that works in userspace. Jan 27 02:43:05 and can also communicate with PSX cards Jan 27 02:44:23 the usual way to go nowadays is microcontrollers with usb hookup... granted, more complex than just wiring to a parport Jan 27 02:45:13 Indeed :\ Jan 27 02:46:15 though motherboards still do have serial headers .. not sure why you can't theoretically use UART. Jan 27 02:46:36 The Linux IR thing works over UART. Jan 27 02:47:06 but serial interfaces are easier to replace with usb, not timing critical, unlike the partport abuse Jan 27 02:47:08 (that sends signals at something like 44 kHz) Jan 27 02:47:51 (using the DTR pin) Jan 27 02:49:32 ape escape was psx? Jan 27 02:49:36 Yes. Jan 27 02:49:37 I always thought it was dc Jan 27 02:50:25 I think they might've released something for that. Jan 27 02:50:39 but the first game (which I have the disc for somewhere) was PS1. Jan 27 02:51:13 * Maxdamantus has only played the first one. Jan 27 02:51:50 Hm. Maybe they didn't make one for DC. Jan 27 02:52:04 should port all that parport using stuff to something like http://www.ebay.com/sch/i.html?LH_BIN=1&_nkw=CY7C68013A&_sop=15&_rdc=1 **** ENDING LOGGING AT Mon Jan 27 03:00:00 2014