TOPIC: MICROSOFT WINDOWS
Running Windows 7 within VirtualBox
With all the fanfare that surrounded the public beta release of Windows 7, I suppose that the opportunity to give it a whirl was too good to miss. Admittedly, Microsoft bodged the roll-out by underestimating the level of interest and corralling everyone into a 24-hour time slot, with one exacerbating the other. In the event, they did eventually get their act together and even removed the 2.5 million licence limit. Thus, I suppose that they really needed to get 7 right after the unloved offering that was Vista, so they probably worked out that the more testers that they get, the better. After, it might be observed that the cynical view that the era of making people pay to "test" your products might be behind us and that users just want things to work well if not entirely faultlessly these days.
After several abortive raids, I eventually managed to snag myself a licence and started downloading the behemoth using the supplied download manager. I foresaw it taking a long time and so stuck with the 32-bit variant so as not to leave open the possibility of that part of the process using up any more of my time. As it happened, the download did take quite a few hours to complete, but this part of the process was without any incident or fuss.
Once the DVD image was downloaded, it was onto the familiar process of building myself a VirtualBox VM as a sandbox to explore the forthcoming incarnation of Windows. After setting up the ISO file as a virtual DVD, installation itself was an uneventful process, yet subsequent activities weren't without their blemishes. The biggest hurdle to be overcome was to get the virtual network adapter set up and recognised by Windows 7. The trick is to update the driver using the VirtualBox virtual CD as the source because Windows 7 will not recognise it using its own driver repository. Installing the other VirtualBox tools is a matter of going to Compatibility page in the Properties for the relevant executable, the one with x86 in the file name in my case, and setting XP as the Windows version (though Vista apparently works just as well, I played safe and depended on my own experience). While I was at it, I allowed the file to run under the administrator account, too. Right-clicking on executable files will bring you to the compatibility troubleshooter that achieves much the same ends but by a different route. With the Tools installed, all was workable rather than completely satisfactory. Shared folders have not worked for, but that might need a new version of the VirtualBox software or getting to know any changes to networking that come with Windows 7. I plan to stick with using USB drives for file transfer for the moment. Though stretching the screen to fit the VirtualBox window was another thing that would not happen, that's a much more minor irritation.
With those matters out of the way, I added security software from the list offered by Windows with AVG, Norton and Kaspersky being the options on offer. I initially chose the last of these but changed my mind after seeing the screen becoming so corrupted as to make it unusable. That set me to rebuilding the VM and choosing Norton 360 after the second Windows installation had finished. That is working much better, and I plan to continue my tinkering beyond this. I have noticed the inclusion of PowerShell and an IDE for the same, so that could be something that beckons. All in all, there is a certain solidity about Windows 7, though I am not so convinced of the claim of speedy startups at this stage. Time will tell and, being a beta release, it's bound to be full of debugging code that will not make it into the final version that is unleashed on the wider public.
Useful keyboard shortcuts for managing the window sizes of Windows applications
Maximising and minimising windows is all part and parcel of using window-based user interfaces, so it's nice to know that there are keyboard shortcuts that reduce the need to use your mouse all the time. Here are a few that work on Windows:
Alt+Space+N Minimise
Alt+Space+X Maximise
Alt+Space+R Restore (set to default)
System error codes for Windows
Windows system error codes can be indecipherable, so it's useful to have a list. Microsoft has one on its Microsoft Learn website that may help. However, the decodes may not as explicit as I would like, but they're better than nothing when you don't get anything other than the number.
A year in the making…
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.
When desktop.ini files appear on the Windows Vista desktop...
Being an experienced computer user, 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 way in which we want them to function. Well, I'm glad that Linux is the linchpin of my home computing world...
A pleasant surprise…
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?

Do I still need serial numbers?
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
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.
Troubleshooting missing HAL.DLL and boot configuration issues in Windows XP
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. Because I thought that there might be hard disk confusion, I 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. However, 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
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.