This year, school is getting serious for my 8-year-old son, Gregory: he’s in the third grade. For the first time, he’s having to deal with real grades for his homework, plus regular quizzes and tests. And later on this year, he’ll face his first standardized test (the Texas Assessment of Knowledge and Skills, or TAKS) as well. He shares a classroom at Cactus Ranch Elementary with 18 other kids, but they have only one general use laptop for the whole group there (the kids do have more general access to computers in the library, and some classes issue laptops to students from cart set-ups for their use as well). His classroom PC is an elderly Dell D630 Latitude that’s on the last phases of its lifecycle — I volunteer in the library once a week, and the school IT guy also works there; he tells me they’re getting ready to upgrade to Vostro models running Windows 7 in 2013.
So I’m loaning my son’s teacher a couple of additional laptops for the kids to share in his classroom. One is my old and trusty Dell D620 Latitude that’s been upgraded with an OCZ Agility 3 SSD, 4 GB RAM, and a T7200 CPU (which puts it on par for processing with the D630, but where its SSD blows the doors off that unit). The other is my equally old and sometimes not-so-trusty HP HDX9203, aka “The Dragon.” I decided to roll the Dragon back to Vista SP2 and it’s been running like a champ ever since. However, Vista’s odd and seemingly random Windows Update behavior hasn’t let me believe I’ve finally caught up with all the updates: with 148 of them installed over the past two days, it’s been a dizzying sequence of download-install-reboot the entire time. Even so, Windows Update now claims I’m completely caught up. We’ll see.
The D620 has an adequate 14″ screen.The HP has a huge and vibrant 20″ screen.
I’m still debating as to whether or not I should install Paragon’s terrific $20 Migrate OS to SSD utility on the Dragon, and then use it to move the OS over to the spare OCZ Vertex 2 nominal 120 GB (actual 111 GB in Windows Explorer) drive I’ve got lying around. There’s no doubt this would speed things up significantly on the Dragon, just like the Agility 3 did for the aging D620, which laughably melds a processor rated at 5.1 in Windows Experience with a drive rated at 7.8! But there are few things you can do to an older laptop to keep it usable that are better than this, so my real question is: do I want to let the Vertex 2 walk out the door, or do I have something better I can do with it? Right now all of my laptops and desktops boot from SSDs already, so perhaps not…
Introduces students to the concepts, terminology, protocols, and services that the Transmission Control Protocol/Internet Protocol (TCP/IP) suite uses to make the Internet work. This text stimulates hands-on skills development by not only describing TCP/IP capabilities, but also by encouraging students to interact with protocols. It provides the troubleshooting knowledge and tools that network administrators and analysts need to keep their systems running smoothly. Guide to TCP/IP, Fourth Edition covers topics ranging from traffic analysis and characterization, to error detection, security analysis and more. Both IPv4 and IPv6 are covered in detail.
Ed brings veteran IP and networking expert Jeff Carrel into the mix on this book, where he served as lead author. Look for greatly expanded coverage of IPv6, lots of interesting hands-on labs and exercises, and an improved real-world focus on configuring and managing IP and IP services in the workplace in this latest edition. It’s bound to be a big hit, not just in the classroom, but on reference bookshelves for networking professionals everywhere.
When I got the news yesterday that the latest 10.8 version of OS X, aka “Mountain Lion,” was available, I jumped on the opportunity to download and install the new OS upgrade for a mere $19.99 at the Apple Store. I’m not sure if it was heavy demand for the approximately 4 GB download file, or online Internet traffic related to the Olympics (the US women’s soccer team played a very strong French team, and managed to beat them 4-2), but it took nearly two hours for me to download the file. I’ve downloaded similarly-sized .ISO files from MSDN many times before, and it has seldom taken more than 45 minutes to an hour for those downloads to complete.
Home screen for the OS X Mountain Lion installer Screen cap from Ars Technica review
But once I got the file downloaded, the install was a breeze. I fired off the download package, and it took me through the rest of the process in about an hour (half an hour or so to unpack the files and prep the machine for the actual OS install, and another half-hour to perform the installation). So far, the handiest tip I’ve seen in using the slightly altered UI is to place two fingers next to each other near the right edge of the touchpad: this calls up a “fat scrollbar” at the right-hand side of a scrolling window and makes scrolling very easy. Other than that, I haven’t yet noticed too many other dramatic changes except that iCloud is better integrated. In fact, I’ve gone ahead and sprung for a big enough storage subscription to cover all of my iDevices–iPod, iPad, and two iPhones–under a single iCloud account now.
I’ve read other reports online that have recommended against the upgrade, and mentioned that older MacBook Airs run more sluggishly on Lion and Mountain Lion than they did on Leopard. I have a 2010-vintage 13″ model with a 2.13 GHz Intel Dual-Core CPU, 4 GB (2x2GB) DDR3-1067, and the same Nvidia GeForce 320M that’s in my HP dv6t Quad Core notebook, which Apple seemingly uses to better effect than HP does. I haven’t really noticed anything like this, but perhaps that’s because I bought the unit used from an Apple employee who had already installed Lion on this machine. At any rate, it’s somewhat faster than my older dual core notebooks, and not too much slower than my quad-core notebooks, so I have nothing to complain about.
For more information on the latest OS X version, I heartily recommend John Siracusa’s mammoth and detailed review for Ars Technica, which digs very deeply into what’s new with and how best to tweak settings and configuration data. There’s also a nice article on the Ars Technica site entitled “How to create a bootable, backup Mountain Lion install disk” on a USB flash drive or optical disk. Warning: you’ll need to do this BEFORE you install the new OS, because the last bit of that process cleans up the file you need to manipulate to create the backup install image (wish I’d read the article before pulling the trigger on my install, in fact…sigh).
This weekend, I had the chance to rebuild and repair an extremely finicky Windows PC on loan to a friend. It is an HP Dragon (model number HDX9203) that HP released in 2008 prior to the release of Windows 7 (October 2009) as a Windows Vista-based “killer media machine.” It includes an AVerTV cable interface for TV access, a Blu-ray player, a hefty-for-the-time T9500 Core 2 Duo processor, and a huge 20.1″ LCD display.
HP’s Dragon is Huge but Gorgeous
When I say the machine is big, I’m not kidding. It’s dimensions are 18.7″ (47.5cm) x 13.36″ (33.95cm) x 2.3″ (5.85cm), and it weighs over 15 pounds (6.8 kg). It’s packaged as a laptop, with a special hinge between the keyboard base and the screen, that enables the screen angle to be altered independently of the angle of the hinge with respect to the base. Don’t get it? It lets you pull the screen closer so that you can position it right past the top edge of function keys on the keyboard (as shown in the preceding photo), even though the edge of the lower deck itself is about 2.5″ further back. The screen also has a 1980 x 1200 native resolution, and offers very good brightness and color output. I’ve watched plenty of movies and Blu-rays on it, and it’s a great personal media station for sure.
The problems with this machine were its cost (these units cost $3,200-4,000 when sold in 2008, depending on configuration and components), size (enormous), and weight (no way you could hold this on your lap for any length of time). Battery life is less than 2 hours (less than 90 minutes when watching videos on DVD or Blu-ray), and thus, it more or less requires a wall socket nearby at all times. By the time Windows 7 got released in October of 2009, HP had apparently decided to orphan and abandon this capable but monstrous media PC. They never updated the drivers for Windows 7, and they never really kept up with Vista on that machine terribly seriously, either.
I went ahead and upgraded the machine to Windows 7 anyway, and was ultimately able to get everything working except for the Authentec AES2501 fingerprint scanner, and the AVerTV miniHDTV TV tuner card. I did have to fiddle about with graphics, media card, and network drivers, because I couldn’t count on getting the latest and greatest Windows 7 drivers to work on this machine. Most of HP’s Vista drivers for this machine peter out around 2008, though there are a couple of items with 2009 dates, and I found another HP driver for a different Vista PC with a 2011 date that actually worked on the Dragon as I re-installed Vista and found my way to a functional and reasonably current set of drivers this weekend — mostly by virtue of a painstaking process of trial and error. I bounced between the HP Support pages, various manufacturer download sites (Intel, Marvell, and nVidia), and the DriverAgent driver scanner utility that has become an important element in the top tray of my PC maintenance and upkeep toolbox.
In the end, I was able to get all but three of the drivers for the Dragon running Vista current as per DriverAgent’s scans. I had to stick with a 2010 version of the nVidia 8800M GTS driver, and go with the AES2501 driver that Windows Update supplied for me (later updates were available through DriverAgent and Authentec itself, but didn’t work). Same for the AVerTV tuner card as well: newer drivers were available, and would install on the machine, but rendered the tuner useless.
It ended up taking me the better part of two full days to get Vista installed (about 2 hours) and up-to-date (150 updates took almost ten hours to download, install, and in some cases re-install when first tries failed). Getting the drivers right took about another 7-8 hours, but mostly because I tried to get as current as possible, then backed off to what worked, through trial and error. This was a case where letting Windows pick the “iffy” drivers (video, TV, and fingerprint scanner) would have been my best strategy from the get-go. But I didn’t figure that out until the course of events rubbed my nose in this realization. Live and learn, I guess!
But now the machine is back in fine form, and running Media Center properly. I can return it to my buddy, knowing that he can put the machine to work as it was intended to be used. For some reason or another, I find this immensely satisfying. It is too, too bad that HP didn’t support an upgrade to Windows 7 for this machine, though. What I cobbled together for Windows 7 on my own — thanks in large part to the wealth of information available on the Notebook Review HP HDX 9000 DRAGON Owners Lounge (see Part 1 and Part 2 for thousands of posts, many informative, especially the instructions and links at the beginning of Part 2) — worked well enough for desktop and test use, though it did not work as a fully-functional media center. And in re-reading the Owners Lounge Part 2 stuff just now, I find myself oddly tempted to try a Win7 install again, as several users have indeed gotten everything to work under that OS, and it sounds pretty fast with an SSD as the boot drive. Hmmm….
Since the introduction of Windows Vista in 2006, Windows Gadgets have made colorful and useful additions to Windows desktops everywhere. At this moment, Windows Gadgets work on Windows 8 as well as on Windows 7 and Windows Vista. But a planned discussion of profound security vulnerabilities in the Gadget architecture at the upcoming Black Hat DEFCON Conference(July 21-26, Caesars Palace) appears to spell doom for these desktop denizens.
Win8 Gadgets
What you see in the screen capture to the left comes from one of my Windows 8 test machines running the Release Preview: my Lenovo X220 Tablet with touchscreen. I’ve found the CPU Usage and Network Meter gadgets from AddGadgets.com to be particularly useful over the years. I also use the analog clock that’s built into the Windows base gadget set, and a handy little gadget called Shutdown as well. That last item is useful because I tend to remote into my test (and other family member) PCs over the network, and it gives me the ability to shut down or restart those machines quickly and easily through a remote desktop session.
But as security researchers Mickey Shkatov and Toby Kohlenberg have discovered (as reported by Ryan Naraine “Security flaws signal early death of Windows Gadgets,” ZDNet), the gadget interface is rife with points of vulnerability that could lead to attack. Hackers could, in fact, take over a system through a malicious gadget foisted on unsuspecting users, or by direct attack on gadgets already running on a Windows desktop. From there, a successful exploit could lead to the attacker obtaining the same level of system privileges and access that attaches to the current logged-in user account. Because so many users routinely log in with system admin privileges, this effectively transfers complete system control to the attacker.
The details aren’t completely clear yet — I guess we’ll have to wait for the presentation and demonstration at DEFCON — but Microsoft has already issued a security advisory (Vulnerabilities in Gadgets could allow remote code execution). This web page includes two “Fix It” tools numbered 50906 and 50907. Because MS fails to describe what these tools do, I learned by experimentation that 50906 disables gadgets (and the Windows Sidebar in Vista), while 50907 turns them back on again.
It might be simpler for users with admin privileges who manage their own systems to simply remove all gadgets from their desktops, and not to add any new ones. I’m not sure it’s necessary to disable underlying support for gadgets if none are running. Apocalyptic warnings aside, I’m going to leave my gadgets up and running until more information emerges from the upcoming DEFCON conference. I need to better my understanding of the nature of the vulnerabilities that already-installed gadgets can pose before I do anything more. Frankly, I’m not sure that a gadget I’ve been using for years actually poses a security risk on my heavily firewalled home network, so I’m willing to wait and learn more about the potential risks of ongoing exposure before I wipe my desktops clean of these helpful bits of software.
It is interesting to understand that Microsoft will do away with the gadget interface, rather than attempting to repair its security issues. The company had already indicated it was deprecating gadgets in Windows 8 (though I discovered to my relief that they still worked on the Developer Preview release late last year, and have continued to use them anyway). However, it now seems likely that they will disable the Gadget interface in the upcoming RTM and GA releases for Windows 8. Thus, production versions of the new OS cannot fall prey to whatever security vulnerabilities gadgets might pose. It should be interesting to mull over what these researchers have learned, and what they’ll reveal, to decide if even trusted gadgets must go on Windows Vista and 7.
I am sorry to see this happen to gadgets. If it turns out they must be removed from my desktops, I’ll also be sorry to see them go. I’ll report back again later this month after the word on gadget vulnerabilities comes out in more detail.
[Note added on 11/18/2013: Thanks to an article I read recently by Deb Shinder, as recounted in a recent post to my Windows Enterprise Desktop blog entitled “Say! You CAN user Gadgets in Windows 8…” I’m very pleased to report that, thanks to 8GadgetPack, you can restore and use Gadgets in the Windows 8 and 8.1 environments. Whoopee! You may do this at your pleasure; I am doing it on several of my Windows 8 and 8.1 machines already.]
If your Windows 7 install has been around long enough, it will pick up various bits and pieces of leftover install information. The Windows Deployment Image Servicing and Management (DISM) tool includes a plethora of command line options that work on a running operating system (in addition to its more common use in setting up images for automated Windows deployments). For use on an active OS, however, your best reference is to start up cmd.exe using “Run as administrator” then type dism /online /? at the command line for a complete listing of commands and options.
In particular the command DISM /online /cleanup-image /spsuperseded is a handy one to know, because it gets rid of superseded install packages left in the wake of a service pack or other major update. It was designed as a post-SP-install cleanup tool, but I’ve run it on several systems that were built from the Windows SP1 slipstream install media, and it still found elements to remove from the installed image, as shown in this screen capture:
DISM removed two packages from my post-SP1 slipstreamed Windows 7 Ultimate installation
This recovered about 3 GB of disk space on my primary production machine — a welcome capability on the 120 GB SSD drive that I’m watching carefully to make sure it maintains at least 25% free disk space, to give the OS and applications room to breathe. On the other hand, if you run it on some systems, you’re more likely to see a result like this one, when DISM finds nothing to clean up on your behalf:
Nothing to clean up on my Lenovo T520 running Win7
Still, it’s a useful post-SP-install trick to keep up your sleeve. Another SP for Windows 7 is pretty likely to appear around the same time that Microsoft ships Windows 8 (late October is when that should happen, say most pundits). If this doesn’t do your system any good now, it will surely come in handy after you install the next SP!
In this case, MYSOD stands for “Mustard-yellow screen of death” and it just hit me this morning on a new-ish production machine on which I’m having video driver problems. It’s got an Nvidia GeForce GTX 460 graphics card in an Asus P6X58D-E socket 1366 motherboard with 24 GB of RAM, an OCZ Vertex 2 SSD, and various other odd’n’ends. The driver version is the latest WHQL (301.42, aka 8.17.13.142) and there are a dazzling number of potential causes for my recent but not so-very-welcome experience. My only other tangible symptom is from Event Viewer, which reports Error code 4101 “Display driver nvlddmkm stopped and has successfully recovered.” This turns out to be a distressingly long-standing and popular problem for Vista and Windows 7, with a long and distressingly ominous list of potential causes and fixes.
Event viewer details for the 4101 video driver error
My searches for enlightenment have turned up some incredibly humorous stuff, however. Thus for example, I found the unwittingly hilarious “Screen of death” page on Wikipedia. It lists many colors of the rainbow for this symptom of hard and irremediable system crash, not all of which are for Windows, but when taken altogether create a lovely rainbow of hues for failure and distress. In addition to the Blue Screen of Death (BSOD) and the Black Screen of Death, both of which I’ve experienced in my days mangling and messing with Windows, I also found a Green Screen of Death (Xbox), Red Screen of Death (Game consoles and early Vista versions), the Purple Screen of Death (signals a fatal kernel error in the VMware ESX server). There’s even a white screen of death (Apple iPhones and iPads, among other systems) and — wait for it — a yellow screen of death that “… occurs when an ASP.NET web application encounters a problems and crashes.” I was surfing the Web, with a boatload of open IE Windows when the MYSOD hit me this morning, so maybe it’s involved. But I don’t really think so…
It was clearly something with my graphics driver. My researches so far have turned up the following possible causes, which in turn suggest various fixes:
Bad graphics drivers: but alas, this problem has plagued me for the past four WHQL updates to the Nvidia drivers, and I’m not sure if I want to roll back into 2010 to fix a problem that fixes itself (it does recover automatically, except for my MYSOD today).
Bad memory module: I’ve run memtest86 and gotten a clean bill of health on all six of my brand-new G.Skill 4 GB modules, and the system will run Prime95 with all cores maxed indefinitely at reasonable temps (under 70°C). I know memory controllers sometimes freak when all slots are occupied, and I’ve maxed memory on this motherboard to be sure, but I don’t see a lot of traffic about memory issues for this motherboard, so I’m going to leave the RAM in for the time being.
I’ve tinkered with the Registry, and added a long time-out (10 seconds) to the Timeout Detection and Recovery (TDR) issue that is often associated with the 4101 error code in combination with the nvlddmkm.sys fail and recover error message (see this great discussion on SevenForums “Help me configure registry correctly to solve TDR issue” for more info). Hasn’t made a lick of difference in my case, though…
I’ve asked the TweakTown guys for any insight they might care to contribute, and continue noodling around with my system as I have time and energy for such things. This is one of the things about Windows that truly drives me bananas, but that also helps to keep me busy and to guarantee full employment to legions of Windows support staff and technicians. Go Microsoft!
Anybody who’s followed my Windows experiences and commentary already knows I think the Sysinternals guys (Mark Russinovich and Bryce Cogswell, primarily, but also a host of others over the years) hung the moon when it comes to great tools and utilities. I was recently pondering how to get over the “What did I forget?” hump in finally upgrading my primary desktop from 4 to 12 GB of RAM, and thus also from Windows 7 Ultimate 32-bit to its 64-bit counterpart, when my research led me to their free tool named Disk2VHD.
In the past quarter, I’ve replaced the boot drives on my three primary notebook PCs with el-cheapo ($149) OCZ-3 Agility 120 GB SSD drives. In turn, that has left me with three 500 GB 2.5″ drives that I can still use, but no longer want for primary notebook HDs. That left me casting about for a solution to put these babies back to work at minimal expense with maximum results. Here’s what I found to meet my needs: a 5.25″ drive bay that accommodates four 2.5″ drives in the standard form factor, and supports both SAS (Serial-Attached SCSI) and SATA drives in a single, heavy-duty brushed aluminum enclosure. It’s available on Newegg for a modest $55, and on Amazon for $60. Here’s an introductory photo of the device, straight from the manufacturer’s Website:
Each of the drive sleds holds a standard 11mm 2.5" HD, or larger if you remove the sled top
OK, so I finally got my three production notebooks upgraded from conventional spinning hard disks to SSDs. All three of the source drives were 7,200 RPM SATA II drives: two from Seagate (one a Momentus plain-vanilla, the other a Momentus XT), along with a Hitachi 7K500 model. Of the three, the Momentus XT was far and away the fastest, but it couldn’t begin to match the OCZ Agility 3 SATA III 120GB drive that replaced it. I took advantage of a special sale to pick mine up for about $150 each on Newegg. Right now they’re priced at $155 with a $30 rebate to bring the price down to $125.
It took me a while to whittle these machines’ drives down to an acceptable level of disk space for the transfer. I recount this exercise in a couple of upcoming articles (one for InformIT.com, the other for InputCreatesOutput.com; no links yet but I’ll plug them in as they become available). Here’s a quick before-and-after snapshot:
Table 1: Notebook System Disk Holdings (Before & After)
Laptop
Before Clean-up
After Clean-up
HP dv6t
72.9 GB
52.8 GB
Dell M11X
48.2 GB
33.1 GB
Dell D620
35.4 GB
27.7 GB
I used the “Clone Disk” tool in Acronis True Image Home 2012 to transfer the contents of each conventional HD to its SSD replacement. Although the HP dv6t has the faster processor, the Dell M11X supports SATA 3 and outperforms the HP on I/O. All in all, the real proof for the value of the exercise comes from some before and after system timings, as shown in Table 2.
Table 2: Notebook System Timings (Before & After)
Timing Point
Dell D620 (Before/After)
Dell M11X (Before/After)
HP dv6t (Before/After)
BIOS alert
00:03 / 00:03
00:03 / 00:03
00:08 / 00:07
Windows 7 Starting
00:11 / 00:07
00:32 / 00:19
00:12 / 00:09
Login Prompt
00:53 / 00:23
01:07 / 00:32
00:40 / 00:12
Desktop appears
01:20 / 00:35
01:44 / 00:42
01:13 / 00:19
Soluto value
01:49 / 00:42
02:26 / 00:42
02:22 / 01:02
Shutdown
00:20 / 00:07
00:18 / 00:06
00:22 / 00:10
Here’s what I take away from this recent adventure. First and foremost, you get the biggest win in performance after Windows starts loading and the systems start banging their drives for all they’re worth. Second, there’s a clear correlation between the I/O interface hardware and overall disk subsystem performance: the Dell D620 which has the oldest SATA controller, saw a jump from 5.9 to 6.9 in the Windows Experience value for the disk data transfer rate. The HP dv6t has a faster SATA II controller and leaped from 5.9 to 7.4, but the MX11 with its SATA III support surged from 5.9 to 7.9 (which is as high as Windows Experience values currently go). Third, some of the best benefits from SSD use come after the OS has booted: applications open and close much more quickly, and shutdown takes no more than half as long as it once did. I like it!
