Technology Tales

Adventures in consumer and enterprise technology

TOPIC: MICROSOFT WINDOWS

A year in the making…

17th January 2008

It was a year ago that I set this blog on the go. Then, I was exploring the possibilities offered by WordPress.com. After some months, I decided that I wanted to make my own decisions rather than have them, so I went independent in June. Between those dates, some big launches took my attention: Windows Vista, Office 2007 & CS3 come to mind. All the while, my experience of UNIX, Oracle and other such matters kept growing more and more. In the latter half of the year, I finally made the leap from Windows to Linux on the home computing front, a decision that taught me a lot and one that I don't regret. Other subjects featured from time to time as well; my musings on web development and blogging made their appearance too. 2007 was a packed year on the technology front, and 2008 is only just getting under way. There's a Vista laptop, and I am already picking up ideas for posts, though I am not going to force them out like I might have tried to do last year. 2008 may be a spot more leisurely, but I hope that it's just as interesting.

Desktop.ini on the desktop?

14th January 2008

Being an experienced computer, I set Windows Explorer to display hidden files when using a Windows PC. However, on my Vista-empowered laptop, that causes two desktop.ini files to appear on the desktop, one for all users and one for my user account. And displaying hidden files does not seem to be something that you can do on a folder by folder basis. With XP, this did not cause hidden files to appear on your desktop like this, so the behaviour could be seen as a step backwards. A spot of googling exposed me to some trite suggestions regarding re-hiding files again, but deleting them seems to be the only way out. Despite the dire warnings being issued, there didn't seem to be any untoward problems caused by my actions. For now, I'll see if they stay away, yet episodes like this do make me wonder if it is time for Microsoft to stop treating us like idiots and give us things that work the in which we want them to function. Well, I'm glad that Linux is the linchpin of my home computing world...

A pleasant surprise…

4th December 2007

Yesterday, when taking the screen grab for my post on Quanta Plus, I did the Alt + Print Screen shuffle as usual. However, when I did so, I was greeted with a dialogue box asking me where I wanted to store the PNG file that was to be produced and what I wanted to call it. The operation was as swish as that. On Windows, the screenshot gets stuffed into the clipboard for you to extricate it with your graphics editor of choice, so this was an interesting surprise. It's the sort of thing that can make a good impression, and it is striking that Linux seems to be ahead of Windows on this one. Who said Linux was less than user-friendly?

Saving screenshots in Ubuntu

Do I still need serial numbers?

19th November 2007

My spot of bad luck with Windows in August highlighted the importance of hanging on to serial numbers for software that I had purchased over the internet and downloaded. Though I could get at the ones that I needed, they were retained in a motley mix of text files and emails; one even was rediscovered by pottering back to the website of the purveyor. While the security of the installation files themselves was another matter of some concern, I was rather more organised in that regard. Both of these are things that need checking before Windows falls to pieces on you and needs to be reinstalled. Of course, human nature, being what it is, means that we often find ourselves picking up the pieces after a calamity has struck when a spot of planning would have made things that bit easier.

Linux does make life easier on this front: commercial applications are anything but the dominant force that they are in the world of Windows. That means that serial numbers are few and far between, and I only need the one for VMware Workstation. The mention of VMware brings me to my retention of Windows, so knowing where serial numbers are located remains a good idea. Even so, I cloned my Windows VM so that any Windows restoration following a destructive crash should be a quicker affair. Now that I am a Linux user, Windows crashes should not encroach as much on my home computing any more and Linux should be more stable anyway...

Repairing Windows XP

21st October 2007

I have been having an accident-prone time of it with Windows XP recently, and have had plenty of reason to be thankful for the ability to perform a repair installation. Here are the steps:

  • Pop the installation disk into your PC's DVD drive and reboot the PC.
  • If you have your PC set it up to boot from DVD's in its BIOS, then you at least will have the option to do this. You may find that this happens by default, but I needed to tell it to do the deed.
  • Select normal installation from the first menu that is presented to you by the installer.
  • Accept the licence agreement.
  • Press R at the next menu and that'll repair the installation.
  • Follow all the menus from there on; it'll be all the usual stuff from here on in, and there should be no need to reactivate Windows or reinstall all of your other software afterwards.

There is a repair option on the first screen (step 3 above) but this takes you into the dark recesses of the command line and isn't what I was needing. I do have to say that they do leave the required option late on in the installation process and that assumes on users having a risk taking streak in them, something that definitely does not apply to everyone. If your boot.ini file is not well, you may find yourself needing to do the full installation and that wipes the slate clean for you, extending the recovery process.

HAL.DLL: a roadblock on the resurrection of a poorly PC

2nd August 2007

My PC is very poorly at the moment and Windows XP re-installation is the prescribed course of action. However, I have getting errors reporting missing or damaged HAL.DLL at the first reboot of the system during installation. I thought that there might be hard disk confusion and so unplugged all but the Windows boot drive. That only gave me an error about hard drives not being set up properly. Thankfully, a quick outing on Google turned up a few ideas. I should really have started with Microsoft, since they have an article on the problem. About.com has also got something to offer on the subject and seems to be a good resource on installing XP to boot: I had forgotten how to do a repair installation and couldn't find the place in the installation menus. In any event, a complete refresh should be a good thing in the long run, even if it will be a very disruptive process. While I did consider moving to Vista at that point, bringing XP back online seemed the quickest route to getting things back together again. Strangely, I feel like a fish out of water right now, but that'll soon change...

Update: It was, in fact, my boot.ini that was causing this and replacement of the existing contents with defaults resolved the problem...

Windows Sysinternals

5th June 2007

In an earlier post, I wondered about command line management of Windows processes. Well, I have since located the sort of tools that I was after as part of the Windows Sysinternals toolkit. It began as an independent endeavour and continued as such until Microsoft acquired them in 2006. You can find out more about the process utilities here, and the whole Sysinternals suite can be downloaded in a single package.

Is Windows 2000 support finished?

30th March 2007

At work, we still use Windows 2000 on our desktop and laptop PC’s. This may (or may not) surprise you, but the XP upgrade seems to have been thought a premature move, only for Vista to turn up later than might have been expected. Now that Microsoft is winding down support for Windows 2000, thoughts have started to turn to a Vista upgrade, but the realisation soon dawned that a move to Vista was a major one, and it now looks as if we will be on Windows 2000 for a little while yet, until 2008 at least.

I, too, have Windows 2000 lurking around at home as a testing platform, not a work copy I hasten to add, and software vendors increasingly are not supporting the operating system any more. Symantec is one of these, with the 2006 versions of its products being the last ones to support Windows 2000. Initially, I was left with the impression that Kaspersky was the same, but this does not seem to be the case. While the open-source community can continue their supply of productivity applications such as OpenOffice, the GIMP and so on, it is the security side that is of most concern as regards the future of Windows 2000. That said, its successors are not the prime targets for cracking, but shared code could mean that it falls foul of the same exploits.

I have yet to notice it with the hardware that I am using, but hardware advances may yet put paid to Windows 2000 like they did to members of the Windows 9x line, especially when you consider that the operating system dates from 1999. Then again, you may find that you don’t need the latest hardware, so this might not affect you. This is not all that unreasonable given that the pace of technological progress is less frenzied these days than it was in the nineties, when Windows 95 was more or less out of date by the turn of the millennium. Having the gold OEM version of Windows 95 as the basis for a Windows 9x upgrade treadmill meant that my move into the world of NT-based operating systems was a clean break with a full version of my new operating system and not its upgrade edition.

Nevertheless, there remains a feeling that Windows 2000 is being cut off prematurely and that it could last a while longer with a bit of support, even if there is a feel of the late nineties about the thing. After all, Windows 2000 probably still supports a lot of what people want to do and without the Big Brother tendencies of Vista too.

Is Vista’s DRM a step too far?

16th February 2007

If it isn’t enough that Vista’s licensing legalese has being causing raised blood pressure, its use of DRM technology is arousing passionate outbursts and outpourings of FUD. The fact that DRM has been part of the Windows has been included in Windows since the 1990’s does nothing to quell the storm. One thing that needs to be pointed out is that the whole furore entails the delivery of protected content to consumers. Microsoft would no doubt approve of the line that if there was no protected content, then there would be no need to worry. However, there is a sizeable number of people who do not trust Microsoft to keep to its word and are making their feelings known.

The embodiment of the issue is Microsoft’s incorporation of HDCP into 64-bit Vista. It is an Intel standard that is on the market, with users already having bad experiences with it. The problems surround the need to ensure that protected video is not intercepted while a movie is being played, and this involves the hardware as much as the software. The result is that you need a compatible monitor that will have the correct inputs so that DRM can be employed. Some also suggest that this is not the end of the matter as regards hardware compatibility and the list can grow long enough that a whole new PC looks like a good idea.

At the heart of this debate is a paper written by Peter Gutmann of the University of Auckland, in which the consequences of Microsoft’s implementation are examined. The idea of a system with an alternative agenda to that which you have is hardly enthralling: neither using CPU time to monitor DRM and the locking down hardware are particularly attractive. Such is the exposure that this article has received that even Microsoft has had to respond to it. The point that they try to make is that decoding of protected content occurs in a sandbox and does not affect anything else that might be going on in the system. Unfortunately for them, many of those adding comments to the piece take the chance to launch a broadside on the company; some of the vitriol is certainly successful when it comes to trying to put me off Vista. To Microsoft’s credit, the negative comments remain, but it far from helps their attempted rebuttal of Gutmann.

Though the main fuel for the negativity is not Gutmann’s paper per se but a lack of trust in Microsoft itself, all of this despite its Trustworthy Computing initiative. The question goes like this: if the company uses DRM for video and audio, where else could it use the technology? The whole licensing debate also furthers this, and it is at this point that the fear, uncertainty and doubt really goes into overdrive, no matter how much effort is expended by people like Ed Bott on debunking any myths. Users generally do not like software taking on itself to decide what can and cannot be done. Personally, I have experience of Word’s habits of this nature in the past, and they were maddening: trying to produce my doctoral thesis with it went OK until I tried pulling the whole thing together using a master document; I backtracked and made PRN files for each chapter so that it wouldn’t change; LaTeX would never have done this….

What is the point of all of this DRM? It looks as if Microsoft clearly feels that it is necessary to pitch the PC as an entertainment content delivery device to continue growing their revenues in the home users market. Some would take this idea even further: that it is control of the entertainment industry that Microsoft wants. However, to do so, they have gone with strong DRM when there exists a growing backlash against the technology. And then there’s the spectre of the technology getting cracked. In fact, Alex Ionescu has found a potential way to fool the Protected Media Path (called Protected Video Path in a ComputerWorld Security article) into working with unsigned device drivers. Needless to say given the furore that has been generated, but there are others who are more than willing to take the idea of cracking Vista DRM even further. A recent remark from a senior Microsoft executive will only encourage this.

I must admit that I remain unconvinced by the premise of using a PC as my only multimedia entertainment device. Having in the past had problems playing DVD’s on my PC, I nowadays stick to using a standalone DVD player to do the honours. And I suspect that I’ll do the same with HD video should I decide to do watch it; it’s not that high on my list of priorities. In fact, I would be happier if Microsoft made a version of Vista with and without protected HD capability, and they do: 32-bit Vista will not play protected HD video. And it avoids all the hackles that have caused so much controversy too, allowing an easier upgrade in the process. The downsides are that the security model isn’t as tough as it is in the 64-bit world and that maximum memory is limited to 4 GB, not an issue right now, it more than likely will become one. If you are keen on Vista, the 32-bit option does give you time to see how the arguments about the 64-bit world run. And if hardware catches up. As for me, I’ll stick with XP for now.

Is Vista licensing too restrictive?

15th February 2007

There are things in the Vista EULA that gave me a shock when I first saw them. In fact, one provision set off something of a storm across the web in the latter part of 2006. Microsoft in its wisdom went and made everything more explicit and raised cane in doing so. It was their clarification of the one machine, one licence understanding that was at the heart of the whole furore. The new wording made it crystal clear that you were only allowed to move your licence between machines once and once only. After howls of protest, the XP wording reappeared and things calmed down again.

Around the same time, Paul Thurrott published his take on the Vista EULA on his Windows SuperSite. He takes the view that the new EULA only clarified what in the one XP, and that enthusiast PC builders are but a small proportion of the software market. Another interesting point that he makes is that there is no need to license the home user editions of Vista for use in virtual machines because those users would not be doing that kind of thing. The logical conclusion of this argument is that only technical business users and enthusiasts would ever want to do such a thing; I am both. On the same site, Koroush Ghazi of TweakGuides.com offers an alternate view, at Thurrrott’s invitation, from the enthusiast’s side. That view takes note of the restrictions of both the licensing and all the DRM technology that Microsoft has piled into Vista. Another point made is that enthusiasts add a lot to the coffers of both hardware and software producers.

Bit-tech.net got the Microsoft view on the numbers of activations possible with a copy of retail Vista before further action is required. The number comes in at 10, and it seems a little low. However, Vista will differ from XP in that it thankfully will not need reactivation as often. In fact, it will take changing a hard drive and one other component to do it. That’s less stringent than needing reactivation after changing three components from a wider list in a set period, like it is in XP. While I cannot remember the exact duration of the period in question, 60 days seems to ring a bell.

OEM Vista is more restrictive than this: one reactivation and no more. I learned that from the current issue of PC Plus, the trigger of my concern regarding Windows licensing. Nevertheless, so long as no hard drive changes go on, you should be fine. That said, I do wonder what happens if you add or remove an external hard drive. On this basis at least, it seems OEM is not such a bargain then and Microsoft will not support you anyway.

However, there are cracks appearing in the whole licensing edifice and the whole thing is beginning to look a bit of a mess. Brian Livingston of Windows Secrets has pointed out that you could do a clean installation using only the upgrade edition(s) of Vista by installing it twice. The Vista upgrade will upgrade over itself, allowing you access to the activation process. Of course, he recommends that you only do this when you are in already in possession of an XP licence, and it does mean that your XP licence isn’t put out of its misery, apparently a surprising consequence of the upgrade process if I have understood it correctly.

However, this is not all. Jeff Atwood has shared on his blog Coding Horror that the 30 grace activation period can be extended in three increments to 120 days. Another revelation was that all Windows editions are on the DVD, and it is only the licence key that you have in your possession that will determine the version that you install. In fact, you can install any version for 30 days without entering a licence key at all. Therefore, you can experience 32-bit or 64-bit versions and any edition from Home Basic, Home Premium, Business or Ultimate. The only catch is that once the grace period is up, you have to license the version that is installed at that time.

There is no cracking required for any of the above (a quick Google search digs loads of references to cracking of the Windows activation process). Though it sounds surprising, it is none other than Microsoft itself who has made these possibilities available, albeit in an undocumented fashion. And the reason is not commercial benevolence but the need to keep their technical support costs under control, apparently.

That said, an unintended consequence of the activation period extensibility is that PC hardware enthusiasts, the types who rebuild their machines every few months (in contrast, I regard my main PC as a workhouse and I have no wish to cause undue disruption to my life with this sort of behaviour but each to their own… anyway, it’s not as if they are doing anyone else any harm), would not ever have to activate their copies of Vista, thus avoiding any issues with the activation limit of 1 or 10: an interesting workaround for the limitations in the first place. And all of this is available without (illegally, no doubt) using a fake Windows activation server, as has been reported.

With all of these back doors inserted into the activation process by Microsoft itself, it makes some of the more scary provisions look not only over the top but also plain silly: a bit like using a sledgehammer to crack a nut. For instance, there is a provision that Microsoft could kill your Windows licence if it deems that you breached the terms of that licence. It looks as if it’s meant to cover the loss in functionality at the end of the activation grace period, but it does rather give the appearance that your £370 Vista Ultimate is as ephemeral as a puff of smoke: overdoing that reminder is an almost guaranteed method of encouraging power users jump ship to Linux or another UNIX. And the idea of Windows Genuine Advantage continually phoning home doesn’t provide any great reassurance either. However, it does seem that Microsoft has reactivated XP licences over the phone when reasonable grounds are given: irredeemable loss of system, for example. That ease and cost of technical support returns again. There is a corollary to this: make life easy for Microsoft, and they won’t bother you very much, if at all. Incidentally, if they ever did do a remote control kill of your system, the whole action would be akin to skating on legal thin ice. And I suspect that they may not like making trouble for themselves.

I think I’ll let the dust settle and stay on my XP planet while in a Vista universe. As it happens, Paul Thurrott has a good article on that subject too.

  • The content, images, and materials on this website are protected by copyright law and may not be reproduced, distributed, transmitted, displayed, or published in any form without the prior written permission of the copyright holder. All trademarks, logos, and brand names mentioned on this website are the property of their respective owners. Unauthorised use or duplication of these materials may violate copyright, trademark and other applicable laws, and could result in criminal or civil penalties.

  • All comments on this website are moderated and should contribute meaningfully to the discussion. We welcome diverse viewpoints expressed respectfully, but reserve the right to remove any comments containing hate speech, profanity, personal attacks, spam, promotional content or other inappropriate material without notice. Please note that comment moderation may take up to 24 hours, and that repeatedly violating these guidelines may result in being banned from future participation.

  • By submitting a comment, you grant us the right to publish and edit it as needed, whilst retaining your ownership of the content. Your email address will never be published or shared, though it is required for moderation purposes.