This one’s quite simple, but I’m always glad to make a new website, especially for a good cause:
This is a great help for families who are in need in our district — please check it out and consider helping these folks this Thanksgiving or Christmas.
This one’s quite simple, but I’m always glad to make a new website, especially for a good cause:
This is a great help for families who are in need in our district — please check it out and consider helping these folks this Thanksgiving or Christmas.
Slingshot recently rolled out several Windows 10 Pro systems for a customer, and discovered their existing GPO’s firewall rules weren’t enough to allow RDP from within the LAN.
Susan’s post Windows 10 and SBS/Essentials Platforms showed how to do it as a one-off. But I wanted a GPO! Google let me down, returning a lot of confusion and complicated workarounds. (I shared this with Susan and she blogged it, which reminded me of my own blog, duh, so here it is!)
I went exploring GPO, and found the right setting under the Advanced Firewall section: Computer Configuration->Windows Settings->Security Settings->Windows Firewall with Advanced Security->Inbound Rules->New Rule->Predefined->Remote Desktop – RemoteFX :

That’s it! Tested and confirmed working in production.
(Note: this is in addition to the usual rules at Computer Configuration->Administrative Templates->Network Connections->Windows Firewall->Domain Profile)
Last December I grabbed a deal on a cheap HP Stream laptop for my family. It’s been a nice little convenience screen, but with gotchas:
1) Tiny hard drive – 30GB total, with 10 gone to Windows (as expected). Then HP took another 10 for their partition.
→ So just 10GB for you! A few apps later and even OneDrive cannot save you.
2) Tiny RAM – 2GB, but only 0.7GB available idling. HP complicated the 2GB also by bizarrely installing 64-bit Windows (against Microsoft’s recommendation) and wasting its limited RAM.
→ Multiple users? “Please log out instead of switch user, honey”.
3)…and none of it is upgrade-able.
→ Well, you can do like I did and add a big fast SD card for more storage, but that’s about it.
T
hen Windows 10 came out, and it’s generally great. It extended Win8’s unified Microsoft logins, and rolled in what was formerly Live’s Family Safety features, making it great for families. And with the Start Menu back, I now have no worries about moving cheese for business users. So to me, the Windows 10 upgrade is an automatic yes for any Windows 8 systems or new PCs.
Add 10 to the above challenges, and of course I wanted to kill seven in one blow! Specifically, 1) move to Windows 10, 2) reclaim drive space from HP’s extra partition, and 3) reclaim RAM from HP’s dumb 64-bit choice. (Alright, 3 in one blow, whatever).
That brings us to a month ago, when I started this blog post….
TL;DR: 2/3 ain’t bad. Success on #1 for drive space. No-go on RAM.
Problem: HP provides NO 32-bit drivers for the Stream. Result: non-working touchpad.
Many hours of reinstalling various editions of Windows, and every other trick I’ve learned over 20+ years, and I got Device Manager looking happy, but with no valid chipset drivers (I believe Intel’s Trusted Execution Engine Interface is the main culprit) to expose the touchpad device to Windows. Actually, I saw a dramatic difference on RAM usage (about 25% more available), but no working touchpad (which is critical for a convenience device like the Stream). I’ll leave that sad story there — if you want more, lemme know.
But there’s still the upgrade and the drive!
Problem #2: Not enough free-space to do the upgrade.
I ran into several snafus with this, but we can get around that! Here’s how:
Unfortunately, it’s still high RAM usage (I’m currently at 72% with a single Chrome tab open and nothing else running), but it’s significantly more free drive space and Windows 10. Heck of an ordeal, but a worthwhile improvement.
My wife, handier with money, loves leaving the num lock on.
I, handier with prose and software coding, want it off. (In fact, I always set the BIOS default to off on any computer).
Our kids could go either way, and have complained about it not being “right” when they switch user.
But since I moved our family PC to Windows 10 a couple months ago, I noticed it remembers each users’ last num lock setting. Hey cool! …But Google admits no knowledge of this feature. Am I just the lucky first guy to notice?
Regardless, this is another fine UI touch that Windows has invented in the last 5-10 years.
(Now if OS X would just get off their laurels and notice/copy them — oh hey Aero Snap anyone?)
NCH VideoPad is an excellent “free” video editor.
I would recommend VideoPad heartily if NCH didn’t crap on their own work.
But unfortunately “free” needs those scare quotes, because its installer just behaves badly. Here’s how, and my answer to each:
Windows Registry Editor Version 5.00 [-HKEY_CLASSES_ROOT\docfile\Shell\NCHconvertdoc] [-HKEY_CLASSES_ROOT\docxfile\Shell\NCHconvertdoc] [-HKEY_CLASSES_ROOT\htmlfile\Shell\NCHconvertdoc] [-HKEY_CLASSES_ROOT\NitroPDFReader.Document.3\Shell\NCHconvertdoc] [-HKEY_CLASSES_ROOT\odtfile\Shell\NCHconvertdoc] [-HKEY_CLASSES_ROOT\rtffile\Shell\NCHconvertdoc] [-HKEY_CLASSES_ROOT\wpdfile\Shell\NCHconvertdoc] [-HKEY_CLASSES_ROOT\wpfile\Shell\NCHconvertdoc]
(Save as a reg file and run it, or manually delete those paths yourself.)
It’s a shame — VideoPad has a paid premium version with more features, and I would recommend it heartily if NCH didn’t crap on their own work.
Possible alternative: it looks like <a href=”http://portableapps.com/node/19682″>you can make VideoPad Portable.</a> That certainly keeps it clean.
Behold!
The white first fuse,
Potential Bound.
Watch the fiery light as it ignites,
Prometheus is released.
Witness white grow green
soon the fuse, the unseen
not shorter but stronger.
More imminent but longer
is the time when finally,
after the lively sparks have pushed (burned?) their way through the hard outer shell the explosion happens showering the landscape with itself,
living shrapnel,
until at last,
it is again
buried in the soil.
-Rob Eberhardt, ~1997
I’ve added a Redirect to keep the old feed working, but some readers may not handle a 301 (and it may disappear someday too!) Please update your RSS feed to https://blog.throbs.net/feed/ !
Now, with all this effort to build a platform, expect me to climb it and start sharing again!
“500 (Internal Server) Error
…that Go Daddy is furiously working to correct.”
It’s been a long time coming, but Go Daddy finally forced my hand by upgrading my dasBlog install to death.
(FYI: Go Daddy no longer has web or email support – chat or phone only. Because people don’t want options.)
The phone rep at least got me to a useful error and told me they finally moved off IIS6 (Windows 2003?!). When I figured out dasBlog can’t run on IIS7 (why not 8??) without a rebuild, it was obviously time.
SO, here I am rebuilding into WordPress. Content is in, but no skin and many links are broken. Sorry for the mess :T But onward!
Update:
Other than some rough design edges, I’m done! Thanks to Reeves Little‘s tremendous how-to Migrating from Dasblog to WordPress, and Bob Craven‘s illustrated supplement Hello WordPress, Good Bye dasBlog, it was quite straightforward.
And to be fair, the Wordpress world has great addins for absolutely everything I’d’ve otherwise Macguyvered together: importing, HTTP redirection, link checking, contact forms (and those are just migration-related). I’ve built a lot of WordPress sites for other folks, but now the cobbler’s child finally has shoes too!
These are a few of my favorite things,
…that Google has yanked out from under my feet.
And let’s not forget Gmail’s Activesync. (That’s why I switched to Outlook.com, and happily).
Why are geeks still trusting Google? We should know better by now.
You can remember dozens of other loved ones in The Google Graveyard