111–120 of 280 posts
The effect this question has on people is because they remember some information which most of the users today don't know as they have never used that technology. So what technology of today will become so obsolete that you would remember your age?
> "Please Insert Disk 13" OH GOD WHERE IS DISK 13, I CAN'T FIND DISK 13. - Jeff 16 hours ago I have exactly this memory as well. My first computer was a Compaq Deskpro Portable. It had a 5.25" floppy drive and a 40 MB hard disk. It was an embarrassment of riches - how could you ever fill up 40 whole mega bytes? Between that and my custom AUTOEXEC.BAT file, I was set. As it happens, I still have most of the files I cr…
> "Please Insert Disk 13" OH GOD WHERE IS DISK 13, I CAN'T FIND DISK 13. - Jeff 16 hours ago I have exactly this memory as well. My first computer was a Compaq Deskpro Portable. It had a 5.25" floppy drive and a 40 MB hard disk. It was an embarrassment of riches - how could you ever fill up 40 whole mega bytes? Between that and my custom AUTOEXEC.BAT file, I was set. As it happens, I still have most of the files I cr…
I hauled the luggable down from the attic and plugged it in. The only things that worked were the fan and the power indicator light. I guess 25-plus years of San Antonio summers weren't exactly the best thing for the electronics. Off to Goodwill it went.
My first computer didn't have disk drives at all - it used standard audio cassette tapes in standard audio cassette machines. I remember feeding the audio into an oscilliscope and reverse engineering the format used on the tape, then writing Z80 machine code (I didn't have an assember - I wrote actual hex opcodes and fed them into a program I wrote that read hex and poked the values into memory) to create tapes that…
A few years ago I went back to school for a bit. One day I was sitting with my classmates, average age about 18, discussing our first computers. I mentioned I got started on a Vic 20 with a tape drive. Suggested someone, "Was that so you could listen to music while you coded?". Took some effort to convince them I wasn't pulling their leg when I told them that it was used to save programmes to
The computer used removable media: 12" removable "Diablo" 5MB hard drive platters. One had four user basic on it, one had single user basic, and one was locked away with the software for grading students.
Memory management was primitive: BASIC ran in RAM, and if you used single user basic, you had 4x the RAM and therefore room for 4x the program. When swapping drives, you had to boot the computer by toggling the CPU's three instructions into the front panel.
I wrote a massive Star Trek adventure game in single user basic. Friends would actually creep into the lab overnight so they could play by themselves.
Earlier quoted context omitted.
Yep, or vice versa, put a bit of tape over the hole to make disks writable that weren't intended to be. Good times!
USB drives could use such a feature. write-lock : prevent it from beint written (and acquiring viruses) read-lock : prevent it from being read (and passing viruses), only showing the free space and being able to write only in the free space
As far as I remember the A and B drives were used for floppy disks. In the olden days home computers didn't have hard drives, and typically either had a single or dual floppy drive. With a dual drive you could do fancy things like make backup copies, without having to repeatedly store data to RAM and swap source and destination floppies. In the 1980s home computers typically didn't have enough memory to store the ent…
Earlier quoted context omitted.
I started out with an Amiga before moving to the PC. The Amiga (while still dealing with device-roots) at least had a more flexible system. fd0: was floppy 1. If you had an additional drive, that would be fd1: etc. The best part was that you could also access devices by file-system label, so if you needed to make sure you were accessing not only a floppy, but the device labelled "WorkbenchExtras" you would simply do…
Don't forget the ASSIGN utility which created new device roots from one (or more!) existing folders, or with deferrment i.e. when assigning Fonts: to df0:Fonts, the OS remembers the disk referred to, and will ask you for that specific disk if you remove it and subsequently access Fonts:. It made working with floppies a lot more pleasant. SUBST on Windows is similar, but with 1/10th of the power and just single drive…
I just thought it might be slightly out of scope for the discussion at large, so I decided not to include it ;)