How I introduced a 27-year-old computer to the web
keacher.com
keacher.com
Of course they did, it's not in HTTP/1.0, it's in HTTP/1.1.
However, I recently had to implement a minimal HTTP client. I assumed Host: was in HTTP/1.0, but unfortunately it wasn't and I had to implement the minimal portion of HTTP/1.1 required for compliance.
In that experience I learned how incredibly difficult it is to get things on and off of computers this old. Even though I lived through all the advances, my mind has a much rosier picture of the capabilities of old hardware than is actually true. Similar to this author, I had to rely on serial connections and some utilities developed by the Amiga emulation community running in Windows on an old PC to actually get it to work. And boy was it slow to move data. It took something like 48 hours to move about 80 megabytes of data. I was worried that was too long for such a machine to be running, but it held out. One of the partitions did have a tiny bit of corruption, but I was overall surprised to find most of the data intact.
Sadly, my shoebox full of disks is probably never to be recovered. Both floppy drives seem to be failing and reading Amiga floppies on modern hardware is possible, but an expensive pain.
The big difference for me was that my old Amiga 600 has a PCMCIA card slot in it. I bought a modern (and very cheap) SD card reader that fit it and copied the necessary device driver over to the Amiga via a floppy. Thankfully it was already set up to read PC disks.
After that copying files (and the entire HD image) to and from my PC was straightforward - the driver even supports VFAT long filenames. I was impressed with the whole thing.
I had a similar issue with the Amiga's floppy drives, and was surprised to discover that some software called "AMI Alignment System" seemed to get the internal drive working fine again. I'm not sure if it worked some magic or just loosened up the drive a bit; either way it let me read my old disks again. It might be worth a try.
Pff, hard drive? In my day, everything we ever coded was stored on cassette tapes. We never needed the computer itself to get them back, just a tape player, special software [1], and the good fortune that solar flares hadn't eaten all the bits yet.
It was only over a decade later that I realized how crazy it was that she bought that for him, given that it was (a) $600, and (b) she knew absolutely nothing about computers.
Was a pain in the ass finding one that was tight enough to stay on and not to tight just just stop anything moving but got it eventually.
Might be worth popping the lid off and checking yours?
However, in ~2000 there was a mechanism discovered whereby you can take two PC 3.5" floppy drives and get a ROM from an Amiga disk. The way it worked is you have one PC disk that will be destroyed, and you instruct the floppy controller to do a low-level floppy-to-floppy copy operation from the Amiga disk to the (burner) PC disk. The CPU will listen in on the copy and get the full Amiga disk image, while the PC disk gets overwritten with junk.
I used this mechanism and saved all my old Amiga files, and happily play many of my old games (awesome retro demo-scene crackers/trainers included! yea!) using the UAE emulator to this day.
I think "sacrificed" is more appropriate here.
Any thoughts on how one would go about this? I guess one would need an ISA (IIRC) network interface and some DOS ethernet drivers?
Incidentally, the only 286 I ever owned was actually a board that I got for the Amiga that plugged into the CPU socket with the unholy alliance of a 286 + Motorola CPU. You could use them at the same time to run PC stuff and Amiga stuff. It was a hack of hacks. But it worked!
It was not. It was the precursor to IDE, where the drive was just a disk and head actuator, and all the magnetic signal decoding electronics were onboard an ISA card plugged into an ISA slot.
What was initially offered as the first "IDE" was taking the analog electronics on that ISA card and moving them onboard the drive and just "extending" (essentially) the ISA bus out to the drive.
Web server running on C64: http://www.c64web.com/
OS with TCP stack running on C64: http://en.wikipedia.org/wiki/Contiki
People often forget that it's not the power of hardware that matters, but the power of hardware divided by the crap the software makes it do.
My first was a Kaypro II with 64kb of RAM, 191kB floppy drive, and a 2.5MHz Z80. I just looked up some videos of them running and the memories came flooding back. Good times.
Just imagine what computing power we'll have in another couple of decades and how silly what we have right now will seem.
http://en.m.wikipedia.org/wiki/Zilog_SCC
LocalTalk wasn't speedy and we were pretty thrilled when we got macs that could support 10/t ethernet, but there was a distinct charm to LocalTalk. (like, the terminators for the cabling consisting of a resistor sticking out of an rj-11 jack!)
I still have a few Dayna Ethernet to LocalTalk bridges I the garage...
Linux CP210x method described in http://bb.osmocom.org/trac/wiki/Hardware/CP210xTutorial
FTDI application note on non-standard baudrates: http://www.ftdichip.com/Documents/AppNotes/AN232B-05_BaudRat...
Also, there is more older machine connected to internet that these MAC : http://www.youtube.com/watch?v=-ECnN7jdgA4
view-source:http://www.mundoviejuno.com/pong.htm
http://www.mundoviejuno.com/pong.js
You're playing Pong on your own machine, implemented in jQuery UI. The 286 is just serving the static files.
My mouse probably has more computing power now.... :-)
http://www.mundoviejuno.com/bios286.png
http://www.mundoviejuno.com/terminal.js
Of course it is cool to see an old 286 serving anything, even static pages like this...
I created a network card for my MSX computer a year ago; it has less than half the cpu speed of this Plus. I really like working on that machine; adding hardware, writing bits of software. I said it before, but it's like a Bonzai tree. Because it's not really possible to do something commercial on it anymore, unlike on anything modern, my brain stops thinking commercially and that's a good feeling which I don't seem to have when touching any modern computer/board. Using the latter I always get business ideas and then it suddenly went from playing to work. Which is not bad because I like that, but sometimes I want to just play.
This. People wax nostalgically all the time how fast running Star Writer or something was back in the day, and how "bloated" modern OSs have become, without understanding that those old PCs did 1/1000 of the things modern computers do, and even those simple stuff (running a text processor) was slow compared to today's standards...
I think people justifiably feel a bit peeved that word processors ran acceptably fast on a 286, and run acceptably fast on a modern multi-core many GHz machine, and yet the added functionality isn't that useful for most people.
A useful analogy would be library functions. A new Python doesn't need to know its C Language Interface to use a library that relies upon it.
And so software does do very much more than it used to do, and that's what people talk about when they talk about bloat.
I could install a minimal Arch, with JWM, and Abiword, and run everything from RAM and get blazing fast operation. But it is odd that modern software, even though it's so feature rich, is also so slow.
Put another way, even if I never embed spreadsheets in my documents, if Abiword cannot deal with the embeded Excel spreadsheet that my client sends me, then Word's ability to deal with it is not bloat.
And if my alternative to editing the client's input numbers directly in the Word document she sent is to deal with a PDF and manipulate dumb text manually, then Word isn't running slowly.
Well, if the abillity to spell check as you type, see the formatting of the document as you work with the actual fonts et al, embed images and graphs etc isn't "that useful" to them, then they can always run something like WordPad or Notepad++.
Whereas some of today's IDEs and language-layered-on-a-VM experiences aren't nearly so fast. Granted they're working much harder. But the end-user experience is not always faster these days.
Still, not comparable. That means that TP had to work on the memory, and not touch disk (else it wouldn't be speedy at all).
Which probably means that the libraries available would be miniscule. A decent graphics (or even math) lib can be well over 1MB. Did you got much out of that era TP besides the ability to use the core language structures?
But no, the programs weren't toys. They were an order of magnitude more complex than most of today's smart phone apps. And in fact, PCs were the smart phones of their day -- a fun size version of what had been considered "real" computing, initially not taken seriously, but destined to evolve quickly.
Also you had direct access to the hardware -- there weren't ten layers of virtualization, protection, and APIs in between. You could do near-realtime things, very low latency. I think that's part of what contributed to the subjective experience being quite fast... provided you didn't need to hit the floppy disk!
A decent graphics/math lib written in TP could be much smaller than 1MB. There's tons of 64k demos written with Turbo Pascal (it helps that it has inline asm). By which I mean "decent" for that era. Say, a functional SVG engine would be something different of course.
The math lib would probably also have to spend bytes on certain functionality that we'd today consider "core language".
Here as well, a proxy was used to get around the Host Header problem.
We kept it for 9 years but it developed a quirk where the monitor wouldn't turn on. The only way to make it light up was to grab the Mac Plus and squeeze it, so everyone used to joke that my Apple computer was lonely and needed a hug.
...or maybe not, as this C64 web browser(!) shows: http://csdb.dk/release/?id=30400
And here's a press release about a tiny web server, with a small stack. http://www.eurekalert.org/pub_releases/1999-08/UoMa-Ucsg-100...
> In terms of technology, the achievement is not only in connecting a small computer on the Web, but also in the size of the network software that is running on the chip, according to Shri. The computer consists of an iPic TCP/IP stack running on 256 bytes of memory, using its own equally tiny operating system. Despite the small size, the TCP/IP stack is fully compliant with the requirements of the relevant standards. It is connected to the Internet through a serial port. Because the machine is a Web-server, it does not need a keyboard or display, but is operated from another computer using a Web connection.
http://theandrewbailey.com/article/119/Project-Twentieth-Cen...
http://theandrewbailey.com/article/120/Project-Twentieth-Cen...
[1] it was (what would now be called) an all-in-one, and it came with some Windows 3.1 thing called TabWorks. And before anyone asks, no, I didn't program on the thing. Not every programmer has programmed since he was in diapers. Also, Windows didn't come with a programming environment back then and search engines sucked ass.
That machine had a long lifetime for us. We upgraded the RAM as far as it would go, replaced the HD... even added one of those AMD "586" coprocessors.
It wasn't upgraded (except possibly RAM), and we had it from about 1995/6 until 1999, when my dad got a Pentium 166 that was surplus from an office move.
[1] http://www.daggert.net/Folio/Programming/Presage/LodeRunner/...
Not as old as this, but I wrote a guide nearly 10 years ago on installing Apache on Apple Unix (OSX is not the first Unix from Apple) on a Quadra[1].
"Sixteen megabytes? Luxury."
I'm still developing for it in my spare time ... http://vimeo.com/70784619 (very little progress yet)
(Edit: Removed a bit about the Amiga being a knockoff, as mobile reading led me to conflate this article with the one about the Amiga emulator.)