Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
I've still got an Amiga, a 1500; that has a awe-inspiring 20MB drive. I loved the Commodore machines, very innovative.
Those pics of the open cabinets (with the laterally-oriented platters) were probably 3380's or the original 3390's. If I recall correctly, they had two disk volumes defined per "spindle", and were belt-driven.
The 3330 and 3350 models were more like the size of washing machines, while 3380 and 3390 were more refrigerator-sized.
Yep.. those were 3380E's.. we started to upgrade to 3380K's and got bit by the problem with the bearings that seemed to plague a lot of the K units.. eventually went to 3390, but by then I was involved with the install of a set of STK Nearline tape silos..
I kept my Amiga 4000. Kept a luggable C64. Everything else including 3 other C64's, an Amiga 500, 6 or 7 something, 1200, and 3000 are gone. I really loved my Commodores.
Haven't loved a computer since, even the Mac I did work on for Saturday Night Live. Yes, I was contracted to interface their Macs with their IBM midrange System 36 back in the nineties. But my boss got to fly to New York to install the equipment and software. :(
Edited to add 'back in the nineties'.
FWIW, I still have my original IBM-PC full-height single-side 160 KB floppy drives that went for $540 each. And the two half-height dual-sided double-density drives I replaced them with two years later. My take is that the PC explosion in the 80s really lit a fire on disk drive design and performance.
For the mainframe trivia buffs - the IBM 3380 was designed as a fixed-block architecture (FBA) device. Then the MVS support staff said count/key/data was so ingrained in the OS that they couldn't work with FBA. So the 3380 ended up with a 32-byte block size and firmware to handle count/key/data. . .If you check the docs on block sizes, record and key lengths you will see that the magic number '32' shows up everywhere. :-)
SSD do not need to be defragged. Defragging is actually bad for them.
Had a 500; the 4MB RAM I bought for it cost me £400 (insane huh? Although not as insane as the fact the PC (IBM types) wouldn't manage that much at that time iirc.); I traded it in for the 1500 I still have. The 4000 I bought developed a fault, that took the company months to fix. Never worked properly afterwards, and I ended up moving over to the dark side. I considered a Mac, but desided that I didn't like paying extra for the privilidge; I regretted it for about three or four years, haven't done since that. And yeh a Commodore 64.
Only windows style defragging. The way windows does it is not the only way, nor the most efficient.
Kendall
heh.. true that, which is why one got still allocated space in cylinders and tracks, with extents as needed....even if FBA would have made it much simpler..
Out of curiosity, why are Targas being used? I thought that was an extinct format created by AT&T that went away when digital TV and higher resolutions came in.
Do you use an external peice of software to defrag, if so which one?
The best way to defrag is to use another disk. I use a custom script to move the files to another disk, when the original disk is empty, the files are moved back. Depending on how it is done, there are a maximum of 2 writes to each cell, if the original move "clears" the cell, or only 1 write if the original data are simply overwritten. I do not have Windows active when doing this, it happens from a Linux environment so that "special" or locked files don't halt the process.
Kendall
Thanks ok not for the likes of me then. LOL
A similar thing can be done with Windows Explorer, as long as you don't select the user's "system" areas (registry and such). You can move all of your files to an external USB disk, then have WIndows copy them back. A big plus is that you get a Backup copy in the process. 2 advantages for the price of 1 operation. When you copy them back, NTFS will try to put the files into contiguous blocks as they are written. Since most of the files that change are "user" files this will resolve a lot of fragmentation. Don't forget to empty your "temp" folders before copying the files back (don't forget about C:\Windows\Temp). This will get you even more contiguous space and even less fragmentation.
Kendall
And on the subject of backups ...
Saw a guy lifting one out by the handle when the lid came off. Lid went flying across the room as he swooped down and caught the platters with both forearms before they hit the floor. Never knew an old fat guy could move so fast. Now I'm old and fat, and I envy him.
I have 5 SSD drives in my system and have had them for about 3 years.
The warranty is for 5 years on all of them.
I am not worried.
Also have a 2 TB pocket drive that I never leave the house without. Seagate Slim
23 years of work on it.
Defrag on my C Drive takes about a half hour. It is 1TB. Also where my Drop Box folder it located.
Also using Drop Box Pro so all my scene changes are backed to the cloud as soon as I save a version.
In other words, SSD drives are pretty well time tested.
At least in my case.
One quote for the 60 TB drive is about $10,000.00 per unit.
Not yet available for the average consumer.
That is 4 times the cost of my system!
Tom
Oh sweet thanks Kendall
telling about memories is like showing cat pics on this forum
If I cleaned up my storage space usage I probably could get by with 1 GB or maybe not, DAZ & Poser & Unity Asset storage usage grows fast and if I ever start taking pictures again, or heaven forbid, videos, then I'd probably best go with 2GB with 2GB backup or even 4GB. Prices have to come down though 1st.
I once fried an extremely expensive 4MB bespoke memory board in the early 1990s. I guess that was a technical predecessor of this SSD technology. They just laughed and I didn't get fired. That was a great place to work.
I've posted pics of the punchcard driven IBM 360-20 that was my first computer at NASA. My first personal computer was the good ol' VIC-20, followed quickly by the C-64 :)
And my current mainPC now has over 20TB of storage... 6 internal and the rest in externals... While my ASUS Slate travels with 3 TB in externals...
So 60TB would sound pretty good if my IT guy would stop telling me how unsafe SSD is as an archival medium... :(
OF post - feel free to ignore - back in 1976 I had 4 order entry terminals, 3 billing terminals, and 2 program development terminals running on a Burroughs B-3700 under MCP-V (pronounced "Master Control Program 5" and my hatred for Roman numerals in OS versions started there . . .). The B-3700 had 350 KB (yes, Kilobytes) of memory and 100 MB of disk - in 5 modules that combined to a unit 4 foot tall, 4 foot deep, and close to 12 foot long. And we ran batch production on it during the day as well.
Now my render system has 64 GB of memory and 14.5 TB of disk space, spread over 9 drives. . .
Drooling over hard drives is bad for the drives...wet and slobbery drives tend to fail quickly.
FWIW, I priced 2 TB ssd the other day; I can get three 2 TB hard drives for the price of one 2 TB ssd.
Looks like I'll keep waiting for the price to come down.
What I'd really like is an IBM DS8100 - but I don't have the room for a two-rack 1.5 ton system, and the cost of a dual-feed 240 volt 50 amp three-phase power hookup would bankrupt me.
...now what would get me drooling is a GPU with 32 GB of HBM2 memory.
Wow ! massive drive, would hate to lose all my data, if that drive ever decides to malfunction.