Surfing With Your Commodore 64 163
Anonymous Squonk writes: "Computer Workshops Inc. has released a web browser for the Commodore 64! Sure, you have to have a UNIX shell account to use it, but this is the first time I've seen a C64 browse the web with full HTML 1.0 and GIF/JPEG support. I hear that Java and Javascript support is just around the corner..." And Flash! And VRML! Well, maybe not.
Re: Who cares? (Score:1)
everywhere.
sweet! (Score:1)
Apple // has had this for awhile.... (Score:2)
Re:My error in strategic judgement... (Score:3)
Re: Who cares? (Score:2)
wouldn't be new. (Score:2)
the bbs, of course, was running on a 102, and had a couple of useful files (including one that let you use your pc clone as a disk over the serial port [which was how the 50k 3.5" disk connected anyway]).
hawk, who still has his 102
why? (Score:2)
hawk
don't need to modify lynx (Score:2)
hawk
uhh, your timeline is *really* bad (Score:2)
> little bit more attention to improving the C-64 (by adding good disk drives and slots),
>the Apple II would not have become as popular as it did.
that's just plain silly.
The C64 is *much* later than the Apple II. The apple II had achieved it's popularity long before the Vic-20. By the time the 20 had come out, the move away from 8 bits was already underway; it used newer technology to build an old-style machine cheaply.
THe apple was geared for both home and business; the vic-20 and C64 were toys from beginning to end. Popular toys, but thye never had any spirations at other markets.
Also, part of the cost reduction was by removing slots and not having drives. The Vic was *not* a new design; it was a stripped down PET with color. The C64 was a vic with 64k.
hawk
apple had about 6 colors (Score:2)
APple used 7 bits for on/off, and the other bit did a half-bit shift to tinker with the color trap. Add that to which bits next to one another were used, and an 8 bit byte produced 7 bits in six possbile colors (though most pattern/color combos didn't exist). This was done with almost no hardware about 10 years before the C64.
hawk
Foul! (Score:2)
hawk
Re:And not only that... (Score:1)
Their books contained complete, annotated ROM listings of the kernel, basic, and 1541 drive code.
Nab Commodore's official book (with schematics! holy shit!), plunk down another hundred or so for the Abacus publications, and a copy of Glenn Bredon's MOST excellent Merlin assembler, and Voila! Joo are in bidness!
Oh. As an aside, I have to mention that C64 basic and Applesoft were almost identical under the hood.
For a desperate game port of code written in basic (no, not mine. I'm an assembler kind of guy) I was placed in a position that required that I get Blitz's (a C64 Pcode type compiler) runtime to run on Apple II.
Merlin for the apple provided a utility that would disassemble and comment the Applesoft Roms for you.
Going back and forth between the resulting listing, and Abacus' own, I got that sucker running like a champ on the apple. Almost all of the major routines were the same; I had to patch a bit here and there, and redefine a BUNCH of memory locations, but in the end, it all Just Worked(tm).
Man.. I miss those days.. (sob!)
Re:And not only that... (Score:1)
Anticipating the obvious question "what about all the Peeks an Pokes..?"
I had to massage this guy's basic by hand and recompile.
Major pain in the ass. That compiler was SLOOOWWW.
The C64 ROCKED as a hacker maschinen! (Score:2)
How about all the hardware features that went virtually unused by practically everyone, Commodore, included?
There was that REALLY neat synchronous serial port built into the VIA chip that was pulled out the back IO connector.
I was doing C64<>Apple II game ports at the time, and needed to transfer files back and forth. I cobbled together a cable that linked the C64 and the apple game connector and wrote assembly routines that shook hands at either end.
I got transfer speeds of about 50kbaud both ways over that sucker. Not too shabby for 1mhz processors
And how about running fastloader code *in the disk drive*? And diddling the interleave factor when formatting to speed things up even further? Or storing data in unused directory sectors to save space?
Whoa. Getting a woody just thinking about it!
Then there's all the neat things you can do with a vertical blank or scanline interrupt!
Of course, there's the SID chip also..
Oh, gawd! Somebody stop me!
Re:C-64? (Score:1)
::grin::
I have two C64s [www.iki.fi] (I bought the other last summer - damn, that newish creamy case of C64G is sexy!) and one VIC-20... I still use the C64s a lot, but somehow I only use VIC-20 for playing Jupiter Lander.
VMware is your friend (Score:2)
Sad to say, that's probably your best bet for getting a decent browser under Linux.
Re:flash?? (Score:2)
Especially if you're using the brain-damaged Linux Flash plug-in. It has the nice feature that, when it starts, it grabs the audio device. If it can't get it, it blocks on it, wedging Nyetscape solid until it gets its way.
Having to stop your MP3 player because some site has a Flash ad on it is not the sign of a well-designed system.
Computer Workshops INC?? (Score:3)
Re:Apple // has had this for awhile.... (Score:2)
C-64 Floppy Disk Drive? (Score:1)
--
Re:How's this work? (Score:1)
Amen. Indeed, why don't we all say that to anybody that isn't working on something that's important to us personally?
Anything, anywhere, will be unimportant to somebody else somewhere else. That includes you, me, and our dogs too.
Re:OT: Posting and the Slashdot effect (Score:1)
Maybe take PNG or Jpeg pictures of the page, then you are not using thier html code. (-;
Just start cacheing the damn webpages.
Re:C-64? (Score:1)
Yes, it did have sound, although I remember it being the Dancing Robot, not the Dancing Demon.
Re:C-64? (Score:1)
OT: Posting and the Slashdot effect (Score:5)
Another is "The Wave" (C-64 graphical web browser) (Score:2)
I got a peek at many C-64 and 128's running GEOS, and even better: "Wheels"
That GUI ran another program, a browser called "The Wave" See: http://www.luckyreport.com/expo.html
"Now you can enjoy graphical web browsing on your Commodore 64 or Commodore 128."
http://www.ia4u.net/~maurice/gbrowse/wave.html
http://videocam.net.au/~colinjt/wave.html
Naturally the above code is tight and efficient assembly language.
Most C-64 programs are smaller than the icons above.
The Wave browser is smaller than the banner ad!!!
Alas, few on Slashdot will ever run this kind of code, let alone generate it.
But such code would easily fit in thier Cache!
Way too much time on your hands.... (Score:1)
Re:CMD To Discontinue Commodore Production (Score:1)
Oops, we did it again!
Centsible Software buys out Software inventory of CMD.
*Company buyout # 27*
Give them a try...
Jethro
Java? (Score:1)
Javascript, I can believe. But Java? Sorry, this is bad SF, I just can't suspend my disbelief.
Not that I don't believe a machine with the power of a C64 could (conceivably) run Java if someone really wanted to write a JVM. But when you start talking about in the context of a web browser, then it would need all the usual libraries too, and there's just no way that much bloat will fit in a C64.
---
Re:Java is not available already? (Score:1)
I knew you would regret not getting that 16K RAM expansion cartridge. If only you had...
---
Re:uhh, your timeline is *really* bad (Score:1)
Yes and no. I knew several people who got into Apples when the IIe came out, which was contemporary with the C64. Apple was still getting new users in '82 and later.
---
Re:Don't laugh (Score:1)
It could be done, but are you sure you'de really want it? Just boot it, then take some kind of memory snapshot, and burn it on a ROM. Then write a startup BIOS that instead of loading a boot sector from disk, restores the ROM image. There might be a few I/O gotchas, but they could be dealt with somehow.
The major downside to something like this is that your running system is really carved in stone. Want to change (or fix!) something in your kernel, add a device driver, etc? Oops.
---
Re:And not only that... (Score:2)
Yup, Abacus "Anatomy of the C64" ruled, mainly due to the comment ROM disassembly appendix.
I bought Merlin on July 2nd 1984, and it was the best 37.95 + tax I ever spent. Fun story: about a year and a half later, I was at high school and a teacher wanted to use an Apple IIe to display a timer on the screen so that he could drop things in front of it and take slow-motion movies showing the motion with a time index running on the IIe's screen in the background (for a physics class, I guess?) So I volunteered and then said, "Hm.. I need an assembler." Someone coughed up a pirated program called Big Mac and I dived in. No one was shocked that I knew 6502, but how the heck did I learn Big Mac's line editor so quickly? The secret: it was the same program as Merlin. Glen Bredon was a cross-platform dude.
Oh yeah, as for the timer: the IIe's Green Screen's phosphors were too persistant, so each frame's final digits just looked like blurred eights. Whoops. :-)
---
Re:Java is not available already? (Score:2)
Re:Java is not available already? (Score:2)
Java is not available already? (Score:5)
Re:All I need... (Score:2)
--
The glory of the C64 (Score:3)
LUnix (Fully functioning SLIP-TCP/IP stack for C64) [netsurf.de]
GeckOS/A65 [6502.org] (Multitasking Unix-ish OS for C64s)
Lemon [lemon64.com] for a good stockpile of C64 warez.
Re:CMD To Discontinue Commodore Production (Score:1)
Re:uhh, your timeline is *really* bad (Score:2)
Well, Commodore might not have had any aspirations at other markets, but readers of (say) Compute! magazine would know that many peripheral add-on companies did not have the same limitations in vision. :-) So I know you could get "accounting" software for at least the 64,
which pretty much boggles the mind.
But I think my favorite item along these line was the really fast mobius strip casette loop as a replacement for RAM product (primarily for the Vic 20, as I recall). If this sounds completely nutty to many readers that's because it was. You really had to have been there.
Bzzt! The C64 was a lot more than a vic with 64K. For one thing, the C64 had something almost like real sound, and not just a way to buzz the speaker. :-) The color graphics were also much more capable; 98% of vic 20 graphics were generated via special characters from the keyboard.
For all six of you who really want to know more on the technical specs of these machines, you might try this page full of Commodore "Business" Machines trivia [www.hut.fi]
Re:C64 Specs (Score:1)
_______
Scott Jones
Newscast Director / ABC19 WKPT
Re:Apple // has had this for awhile.... (Score:1)
Re:SuperCPU (Score:1)
A cricual point that you seem to be missing is that software is written in a very different way for a very small system like the C64. Of course it is significantly less functional, but a lot of software worked sufficiently well and ran sufficiently quickly for the stock C64 nearly 20 years ago at 1 MHz (its slow disk drive is a different issue).
When you run this style of software on a processor that runs 20 times faster, WHAMO! It suddenly runs 20 times faster. Whereas modern software follows Gates' law ("every 18 months, the speed of software halves"), and its speed never really increases, only its whiz-bangedness.
The 65816 in the SuperCPU is also a 16-bit processor vs. the 8-bit 6510 (6502). This is a significant potential increase as well, similar to the modern transition from 32 to 64 bits.
Re:Don't laugh (Score:1)
Hey, you could also use Little Red Reader! [csbruce.com]
My error in strategic judgement... (Score:5)
Re:And not only that... (Score:2)
A complete description of a modern computer in all its complexity would likely fill a bookshelf. Just the latest draft of the ATA specification [t13.org] is about the same thickness, when printed double-sided, as the Apple IIe Technical Reference Manual I got back in 1987, which provided complete schematics, specifications, and even source code for the ROMs (except for the BASIC interpreter, and if Apple hadn't gotten that from M$, it probably would've been published too).
Psion has also nice browsers (Score:1)
But the Psion web browser rocks. And Opera is even better.HTML 4 works. Javascript works. On 5MX, Java is also fully supported. And dithered pictures don't look that ugly. And it renders just as fast as Mozilla on my Celeron 450.
Assembly language and optimization. This point has been forgotten by today's developpers for servers and desktop computers.
When I coded demos on Atari ST, 1 cycle was 1 cycle (actually 4 on 68000), and it should never been lost, or another crew would have done better than your. And when you only have 512 K RAM total, you have to save bytes, too. Code was unpacked and generated on-the-fly, and every piece of hardware was used at its best. For instance, I used the sound hardware to draw 3D (actually to erase the virtual screen by sampling with no volume) . Generated code, precalculations, memory moves, self-modified code, pre-shifted line segments and sprites, etc. This was tricky, this was a hell to debug and to understand when you didn't fully design the code. But it was hard to do faster. We could spent one entiere year just to save some cycles in order to have the best sprite or line routine of all crews.
Today's workstations have 500x more memory that Atari ST had. Their CPU is 200x faster. And the graphic and sound chips are also able to do amazing things without the need of the main CPU (playing a soundtrack module at 16khz + fullscreen took just about 80% of the CPU time per VBL on Atari...) . So why don't we have applications that are at least 200x faster ?
Because there are no more real coders. Just programmers. People sometimes care about algorithms, not about the code itself. And nobody seems to have interest in assembly language. High-level bloated slow languages like Perl and PHP rules the world (no flame here : I love Perl, but the fact is that the same thing could be 100x faster in execution. But 100x longer to code, yes) . I can't imagine what wonderful things we could have on our PC today if everything was coded like good old demos.
And big projects can be coded in pure assembly. The GfA-Basic and Devpac 2 were powerful development kits (interpreter/compiler/assembler/debugger) and 100% pure assembly. The same things goes for HP48 projects. 100% Saturn assembly (hi HP freaks ! HPdream is talking to you !), and there were monster projects (like the meta-kernel, now in newer HP calculators) . Some big demos also needed a lot of source code, twice the size of the linux kernel source code. And it worked. Fast.
Coding in pure assembly nowadays may sound like regression. But maybe fast and lazy programming to get a just-working but slow and bloated result is also a regression.
wow (Score:2)
There are some people with WAY too much free time on their hands, and I salute you.
I gotta get back to working on my Honda CVT entirely out of LEGO now.
C64 Specs (Score:1)
Re:How's this work? (Score:1)
:wq
Re:flash?? (Score:1)
sigh... (Score:1)
Guess I'll have to go and find one from somewhere - maybe some museum will have one
Re:Don't laugh (Score:1)
Re:Don't laugh (Score:1)
Thanks for that info. IMO, Jay Miner was a digital graphics pioneer who was way ahead of his time. He should be revered by all and remembered for his significant contribution to the microcomputer revolution.
Re:C64 Specs (Score:1)
Very interesting. I stand corrected. I take it that, by interlacing, you mean it was possible to interrupt the raster and change color registers on the fly. Thanks raynet.
Re:Don't laugh (Score:1)
Chris, you are a true believer. I admire your loyalty to the past. It was fun to write 6502 assembly code for those puppies, wasn't it?
Re:Don't laugh (Score:1)
Now that's REAL power!
I can feel your joy.
The 128 is booted, with my text editor loaded and running before the Macintosh has even loaded it's first line of Extension and Control Panel icons. To print labels on the Mac, I have to load a relatively huge program.
Now this is one of my major complaints regarding today's desktop machines. It takes way too long to boot them and get them to speed. I wish someone would do something about that, although I doubt it can be remedied.
Yes, I still use a slide rule, except for those problems that require more than three decimal place answers. Then I use my Texas Instruments SR-40, the "upscale" version of the classic TI-30 "Electronic Slide Rule" calculator. Nothing says "MATHEMATICS" quite like a red LED display.
Dude! With a little bit of creative thinking, you could start a new techie religion. May I suggest you encase your oldest computer in a clear acrylic block, turn it into an idol of worship, and have your flower-children pray and burn candles and incense to it. Also make them wear a gold-plated 6502 chip on the front of their caps. The slide rule is their cross, of course.
Have fun. Don't ever throw away any of that stuff. In a few years it may have archaelogical importance.
Re:Don't laugh (Score:1)
Wasn't that a deliberate design decision having to do with overall instruction speed?
Re:Don't laugh (Score:1)
I see what you mean. Instead of ROM, how about low-power, battery backed CMOS RAM? This way, the system is never really down even when the power is off. The BIOS would have code to restore things like I/O settings to last session and update date/time related stuff if necessary. Just a thought.
Don't laugh (Score:2)
I am fascinated by the early history of the microcomputer. Does anybody out there still remember the Rockwell AIM-65 computer, a single board 6502 machine with a 20-character LED readout, a keyboard and a calculator roll-printer all attached to the board?
Holy moses! (Score:2)
No way! FULL HTML 1.0 support? Way to bring the C64 into the early 1990s! Where's my copy of Netscape Mosaic 0.9.2?
--
Re:How's this work? (Score:2)
Cool. I can turn my $2000 PC into a disk drive for my 20 year old piece of shit Commodore 64. Sign me up baby! Will this work on the Vic-20?
To answer your sarcastic question, yes it works for the Vic-20 also. The 1541 drive uses a serial interface that was present on most of the 8-bit Commodore machines. So you could use the same drive on the 128, PET, VIC, and so on.
As far as the general attitude of "why the hell don't you work on something more important?", I think people that still hack old machines are like people that still restore classic cars - they do it because they can. People who want to do stuff like port a Web browser to a machine that has no practical purpose are like people who climb mountains for no reason other than to say they did. Don't knock it - someday you'll be pining for the old days, too.
-J
Re:How's this work? (Score:5)
Most people still hacking at C64's use a cable that goes from the printer port on a PC to the drive cable on the 64. It's called an x1541 cable. You run a small bit of software on your PC, and then your C64 thinks your PC is a disk drive. The PC program lets you load and save image files of 1541 disks. So you could pull down a bunch of disk images from the 'net to your PC's drive, and your C64 would treat them as floppy disks in the 8 drive or 9 drive or whatever. It's pretty cool, especially considering about a million of those tiny little SS/SD disk images could be downloaded in seconds on a 56K modem...
-Jon
All I need... (Score:5)
Re:SuperCPU (Score:2)
From the site...
It must not be compared with a PC which just runs a bit faster after an upgrade. A P300 only runs about 3 times faster than a P100. A SuperCPU-C64 runs 20 times faster than a stock C64!
Wow!! That's amazing! If these guys are as good at making CPUs as they are at math, then we're in for some fun......;)
nlh
Impressive? I have my doubts... (Score:2)
After I was done I skimmed around in my (dusted) software archive and stumbled across NovaTerm; a completely modular build terminal program for the C64 which offered anything you'd need. You need one side of a 5.25" disk for it (it will take up aprox. 80%) and the other side can be used as a datadisk. Because it was modular its functions expanded; right up to full ZModem support.
Taken that into consideration and the total size of the ppp stack in the Linux kernel I must admit not being very impressed by this project. I'm sure that if the novaterm developers we're still at it there would be a lynx style Internet access for the C64 ages ago. Maybe it could even evolve into full blown graphical support, who knows.
Basicly; this looks nice but I'm sure the C64 can do much more.
Oh Man! (Score:1)
Could you imagine a Beo...
Ah, forget it!
Re:Suicide case. (Score:1)
My kingdom for that flexibility/simplicity on any other PC OS...
Re:flash?? (Score:1)
Re:Just submit the Google cached version (Score:1)
Re:Suicide case. (Score:1)
Surfing Moral Equivalent (Score:2)
This has got to be the moral equivalent of impressing Real Surfer Dudes by hanging ten off one of those dinky 2 ft styrofoam dog paddle boards (like I used in the kiddie pools.)
Dammit... (Score:3)
The Wave by Maurice Randall (Score:1)
Re:Java is not available already? (Score:2)
flash?? (Score:2)
And how 'bout a Shockwave player for Linux, huh?
Just submit the Google cached version (Score:4)
story submitter could check an option that would allow for "Google" style mirroring of the page(s)
A very frequent suggestion [slashdot.org]. Here's how to implement it: When you're submitting a story that links to a low-monthly-bandwidth web site, insert www.google.com/search?q=cache: right after the http:// in the URL. That way, viewers get a Google cached version with a link at the top to the most current version.
Re:sigh... (Score:2)
Guess I'll have to go and find one from somewhere - maybe some museum will have one :)
In fact, a museum does have one, but they are saying totally wrong things [trulyfree.net] about them.
It makes me wonder who payed for that exhibit cough! Intel cough!.
Suicide case. (Score:3)
Great. (Score:2)
Re:Sure... (Score:2)
Maybe you should've gotten the 16K expansion module? I still have one laying around here...
Re:C-64? (Score:2)
Then there was the Tandy Color Computer Model I [computingmuseum.com] - Much later and with a 6809 and entirely incompatible with the original Trash-80s.
Re:Quick! (Score:2)
http://www.w3.org/History/1994/WWW/Journals/CACM/
Sure... (Score:2)
Re:Don't laugh (Score:3)
The custom chip set for the Amiga was designed by Jay Miner who also did the graphics chip set for the Atari 8-bit machines. I don't think he had come over to Commodore when the C64 was being designed, but I'm not sure and can't turn up anything on a web search. I also don't know if he is still alive. The Atari 800 and the Amiga were great machines in their day. If he is dead, I'll belatedly mourn his passing.
Re:C-64? (Score:3)
Re:C-64? (Score:2)
One was aimed at the home computing market, the other was a "business machine" (with accompanying price tag)
Re:C-64? (Score:2)
Re:C-64? (Score:2)
uh....
In some ways, sure... but not so in others. The TRS-80 series (Mod 1, etc) were a different class than the CoCo. No chicklet keyboards on the Mod series, for starters...
I wonder... (Score:2)
Of course, it's a neat idea, but with what computers are going for today, I wonder what I could reasonably use it for. (Don't believe me, go to ebay and search for "IBM Thin Client") Personally, a web server would be better. It would then be really useful for various embedded applications. I could put one in a robotic lawnmower or my refrigerator. I even have an old children's book lying about that details the building of a robot that interfaces with the C64 - in other words, it's dead easy.
Oh, and ahem.... "Could you imagine a Beowulf cluster of these?"
Photoshop for the TRS-80 (Score:5)
Gotta go. I've got to make some hard copies with my snazzy thermal-transfer printer.
I've gone nuts with Photoshoppery [ridiculopathy.com]
Re:They must be using one for their Web hosting to (Score:2)
"Some of LNG's key features (unordered)...
* A simple web server (experimental)"
SuperCPU (Score:5)
C-64? (Score:2)
Re:Java is not available already? (Score:2)
And not only that... (Score:2)
Meanwhile, back in the present, I've probably spent more than a thousand bucks on software and PC documentation over the last 10 years without ever getting anything that resembles a complete description of the hardware.
Assembly Language Rocks (Score:2)
Too true. It's not really that much harder to code a sizeable project in Assembly, if you have a bit of discipline about it. The hardest thing is defining your data structures and sticking to them. You build the "language" as you need it in the form of purpose-built subroutines. I just got finished doing a 12,000 line project for an embedded controller. I socially engineered the manufacturer into giving me a few hooks -- which added about 2 pages to the firmware source code I'm told -- and then supplemented their well-designed but miserably slow BASIC variant with blazingly fast background Assembly. Now this gizmo which can only execute 100 lines or so of BASIC per second is weighing and sorting 150 pieces per minute, doing true weight conversions at 60Hz (the firmware only manages 10Hz due to the use of floating-point math) and doing accurate 60Hz timing which BASIC cannot do.
As one of the engineers said after seeing the video, "Well, I guess you've been telling us this was possible since 1995."
This controller uses a 20 MHz 80186. Its replacement introduced last year uses a 40MHz 80386DX, and my code still runs an order of magnitude faster on the old hardware than BASIC code does on the new board. Another thing I told them back in 1995 -- you may spend a lot of time to write software, but you only have to write it once. When you up the CPU specification it increases the cost of every unit you produce.
Re:Assembly Language Rocks (Score:2)
You miss the point. You are looking at the micro scale; I am looking at a higher level of abstraction -- though not much higher.
I've looked at quite a bit of object code over the years and I am still looking for this compiler that is anywhere near as efficient as a human -- not at stuff like loading the pipelines, but at stuff like figuring out when to use register vs. memory variables and which registers to use (especially important in x86 architecture). Pipeline loading inefficiency is nothing compared to the fact that you used a 16-bit integer variable and did error checking on the subtract operation when the CX register and LOOP would have done the same thing. It is possible to instruct modern compilers to make very tight code but it's almost as much effort as writing the Assembly yourself and very few people know how to do it (or even know that it can be done, or might be worth doing).
Most projects don't warrant being done entirely in Assembly -- my project had to because it was piggyback on a proprietary embedded system and there was no OS and no reasonably fast higher level language to draw on. (Still, about 2,000 of those lines are in the controller's miserably slow BASIC; no use coding user interfaces that don't have to be fast anyway, etc.)
In a more reasonable environment my experience has always been about 80/20, that is 80% of the code in any old high-level language that's available plus 20% really fast assembly, is about as good as 100% assembly. Unfortunately, in Windoze it is a blazing pain in the posterior to use assembly at all.
Which is unfortunate, because I've found that most projects have a few things that happen so often that not doing them in Assembly is really stupid. The engineers on the device I hacked said they had done some statistical analyses and found a few routines that were called so often they bore looking into. One of them was named EVALUATE_KEYWORD. No duh. You don't code the inner loop of an interpreted language in C++; it's only a page or two of Assembly and that will literally give you an order of magnitude improvement. It also helps if you don't use double-precision floating point math throughout regardless of whether it's necessary.
They must be using one for their Web hosting too (Score:5)
Re:C-64? (Score:2)
now somebody else will complete it first!
Well, alot of people still have C64s, they were a nice computer.