The Commodore 64 didn’t have an operating system in the traditional sense that we now think of one. It most certainly did have a method of interacting with the user and handling I/O, including disk files. But the way it all worked seems strange today. Here’s what made the native Commodore 64 operating system different, and the alternatives that surfaced during the 64’s long life.
Windows 10 uses homegroups, but if you have systems that don’t understand homegroups and want to share a Windows 10 printer by UNC (the old school way to share a network printer), it’s not obvious how to go about doing it.
I couldn’t find a way from the GUI, but it’s still possible to share the printer from a command line.
One of the new features of Windows 10 is better file compression, which was intended to help Windows fit better in low-resource devices like tablets. But it’s helpful on computers with SSDs too. But for whatever reason that option doesn’t show up on mine.
But you can still compress your system files even if the Disk Cleanup utility (which you can also launch from the Free up disk space by deleting unnecessary files control panel) doesn’t show the Compress system files option.
The bane of my existence as a sysadmin was .NET. It would corrupt itself randomly, sometimes taking with it this awful CA product written in .NET that nobody else wanted anything to do with.
In my day I’d reinstall service packs and the latest patches and one of the six things we tried would fix it. I rarely knew which one. But that was five years ago. Today, as long as you’re running .NET 4.5.1 or earlier, Microsoft has an automated tool that repairs it. You can run it as a GUI app or from a command line or script. Curiously, it doesn’t support 4.5.2 yet–maybe that means 4.5.2 doesn’t break. We can dream, right?
Normally I’d say upgrade to 4.5.2 since its end of life is in 2023, as opposed to 2016, but until the fix gets revised to support 4.5.2, I won’t blame you for staying back on 4.5.1. Availability is 1/3 of security, after all.
My tips for using Sysinternals’ Du.exe were well received last week, and my former coworker Charlie mentioned a GUI tool called Windirstat that I had completely forgotten about. For the command-line averse, it’s an incredibly useful tool.
But there’s one thing that Du.exe does that makes the CLI worthwhile. It will output to CSV files for further analysis. Here’s the trick.
DU -L 1 -Q -C \\SERVERNAME\C$\ >> servers.csv
Sub in the name of your server for servername. You have to have admin rights on the server to run this, of course.
For even more power, run this in a batch file containing multiple commands to query multiple servers, say, in your runup to Patch Tuesday. Open the file in your favorite spreadsheet, sort on Directory Size, and you can find candidates for cleanup.
I bought a Raspberry Pi over the weekend intending to turn it into a retro gaming system. I’d rather not have a mess of systems and cartridges out for my kids to tear up and to constantly have to switch around at their whims; a deck-of-cards-sized console with everything loaded on a single SD card seems much more appealing.
I followed Lifehacker’s writeup, which mostly worked. My biggest problem was my controllers. NES and SNES games would freeze seemingly at random, which I later isolated to trying to move to the left. It turned out my Playstation-USB adapter didn’t get along with the Pi at all, and was registering the select and start buttons when I tried to move certain directions, pausing the game.
When I switched to a Retrolink SNES-style pad, the random pausing went away. The precision reminded me of the really cheap aftermarket controllers of yore for the NES and SNES. I concluded my controller, which I bought used, was worn out. Ultimately I ended up switching to a Logitech controller, which worked well. Read more
One of my former supervisors now works for a security vendor. He told me the other day that someone asked him, “Does your company have anything so I don’t have to patch anymore?”
The answer, of course, is that there’s nothing that gets you out of ever having to patch anymore. To some degree you can mitigate, but there’s no longer any such thing as a completely friendly network. The reasoning that you’re behind a firewall doesn’t work anymore. On corporate networks, there’s always something hostile roaming around behind the firewall, and you have to protect against it. If you’re on a home network with just a computer and a router, your computer and router attack each other from time to time. That’s the hostile world we live in right now. Patching is one of the fundamental things you have to do to keep those attacks from being successful.
That said, there are things you can do to patch less. Read more
Phoenix is more realistic. Every problem every shop I’ve ever worked in is in that shop, plus some I’ve (luckily) only heard about. But unlike Office Space, it has solutions beyond burning the building down. Read more
Mark Stephens, a.k.a. Robert X. Cringely, wrote last week about his disappointment in Ashton Kutcher’s movie Jobs, about the late Apple co-founder and CEO.
Here’s the most important part of his quasi-review:
[S]omething happened during Steve’s NeXT years (which occupy less than a 60 seconds of this 122 minute film) that turned Jobs from a brat into a leader, but they don’t bother to cover that. In his later years Steve still wasn’t an easy guy to know but he was an easier guy to know. His gut for product was still good but his positions were more considered and thought out. He inspired workers without trying so much to dominate or hypnotize them.
Indeed. Read more