Skip to main content

The Floppy Disk - one step closer to death

The old dinosaur of the tech world comes a little closer to finally popping its clogs.  Sony, pretty much the last company still manufacturing floppy disks will stop from March of next year.

In various forms the old floppy disk drive (often abbreviated to FDD) has been around since around 1971.  It started then with IBM’s 8” disk/drive.  Shugart (who I think became Seagate?) brought out the 5.25” disk/drive around 1976.

HP brought out the 3.5” disk/drive in 1982.  This format had the longest life and one still encounters them from time to time.  I recently had to use one to load a RAID driver onto a PC.

File:Floppy disk 2009 G1.jpg

In some respects the 3.5” disk was fantastic: light, small, fairly physically robust, cheap, decent storage capacity for the ‘80s.  However, in other respects it was diabolical: magnetically sensitive, sensitive to dust, it wore down over time, by the mid to late ‘90s it was annoyingly short on capacity.

If you want to know more have a look at the Wikipedia entry here:  http://en.wikipedia.org/wiki/Floppy_disc

For more info also have a look at the Engadget entry here:  http://www.engadget.com/2010/04/26/sony-shutting-down-japanese-floppy-disk-sales-by-march-2011-kil/

Comments

Popular posts from this blog

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more...  but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box:  \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in:     UPDATE tbSingletonData     SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS

Print Management Console Missing

I've encountered a few Windows 11 machines lately, some brand new, that haven't had the Print Management Console installed. Trying to run it from the Run menu using "printmanagement.msc" didn't work either. The fix is to run this from a command prompt:  dism /Online /add-Capability /CapabilityName:Print.Management.Console~~~~0.0.1.0

DNS Dynamic Updates & DNS Scavenging

I was encountering an issue at a customer's site where the DNS records of their client PCs often would be behind or out of sync with the records in DHCP.  Usually the IP address would be older in DNS and this was causing issues with scripts executing and network tools correctly resolving client PC hostnames to their correct IP addresses. I realised I needed to make some changes to their dynamic DNS updating configuration.  After a lot of reading through Microsoft's documentation and various online forums, this is what I ended up configuring.  Hopefully this may help someone, some day: - Make the DHCP server a member of the "DnsUpdateProxy" group -  Create a new user account, in the "Users" OU, called "dnsdynamicupdates"   - This new user only needs to be a member of the "Domain Users" group - no special privileges   - Make the password strong and set it to never expire - Set this new user as the credentials used by the DCHP server in IPv4...