TOPIC: MICROSOFT
Saving Windows Command Prompt & Powershell command history to a file for later useage
15th May 2013It's remarkable what ideas Linux gives that you wouldn't encounter that clearly in the world of Windows. One of these is output and command line history, so a script can be created. In the Windows world, this would be called a batch file. Linux usefully has the history command, and it does the needful for taking a snapshot like so:
history > ~/commands.sh
All the commands stored in a terminal's command history get stored in the commands.sh in the user's home area. The command for doing the same thing from the Windows command line is not as obvious because it uses the doskey command that is intended for command line macro writing and execution. Usefully, it has a history option that tells it to output all the commands issued in a command line session. Unless, you create a file with them in there, there appears to be no way to store all those commands across sessions, unlike UNIX and Linux. Therefore, a command like the following is a partial solution that is more permanent than using the F7 key on your keyboard:
doskey /history > c:\commands.bat
Windows PowerShell has something similar too, and it even has aliases of history and even h. All PowerShell scripts have file extensions of ps1 and the example below follows that scheme:
get-history > c:\commands.ps1
However, I believe that even PowerShell doesn't carry over command history between sessions, though Microsoft is working on adding this useful functionality. While they could co-opt Cygwin of course, that doesn't seem to be their way of going about things.
Upgrading from Windows 7 to Windows 8 in a VMWare Virtual Machine
1st November 2012Though my main home PC runs Linux Mint, I do like to have the facility to use Windows software occasionally, and virtualisation has allowed me to continue doing that. For a good while, it was a Windows 7 guest within a VirtualBox virtual machine and, before that, one running Windows XP fulfilled the same role. However, it did feel as if things were running slower in VirtualBox than once might have been the case, so I jumped ship to VMware Player. While it may be proprietary and closed source, it is free of charge and has been doing what was needed. A subsequent recent upgrade of a video driver on the host operating system allowed the enabling of a better graphical environment in the Windows 7 guest.
Instability
However, there were issues with stability and I lost the ability to flit from the VM window to the Linux desktop at will, with the system freezing on me and needing a reboot. Working in Windows 7 using full screen mode avoided this, yet it did feel as I was constrained to working on a Windows-only machine whenever I did so. The graphics performance was imperfect too, with screening refreshing being very blocky with some momentary scrambling whenever I opened the Start menu. Others would not have been as patient with that as I was, though there was the matter of an expensive Photoshop licence to be guarded too.
In hindsight, a bit of pruning could have helped. An example would have been driver housekeeping in the form of removing VirtualBox Guest Additions because they could have been conflicting with their VMware counterparts. For some reason, those thoughts entered my mind to make me consider another, more expensive option instead.
Considering NAS & Windows/Linux Networking
That would have taken the form of setting aside a PC for running Windows 7 and having a NAS for sharing files between it and my Linux system. In fact, I did get to exploring what a four bay QNAP TS-412 would offer me and realised that you cannot put normal desktop hard drives into devices like that. For a while, it looked as if it would be a matter of getting drives bundled with the device or acquiring enterprise grade disks to main the required continuity of operation. The final edition of PC Plus highlighted another one, though: the Western Digital Red Pro range. These are part way been desktop and enterprise classifications and have been developed in association with NAS makers too.
While looking at the NAS option certainly became an education, it has exited any sort of wish list that I have. After all, it is the cost of such a setup that gets me asking if I really need such a thing. While the purchase of a Netgear FS 605 Ethernet switch would have helped incorporate it, there has been no trouble sorting alternative uses for that device since it bumps up the number of networked devices that I can have, never a bad capability to have. As I was to find, there was a less expensive alternative that would become sufficient for my needs.
In-situ Windows 8 Upgrade
Microsoft has been making available evaluation copies of Windows 8 Enterprise that last for 90 days before expiring. One is in my hands has been running faultlessly in a VMware virtual machine for the past few weeks. That made me wonder if upgrading from Windows 7 to Windows 8 help with my main Windows VM problems. Being a curious risk-taking type I decided to answer the question for myself using the £24.99 Windows Pro upgrade offer that Microsoft have been running for those not needing a disk up front; they need to pay £49.99 while you can get one afterwards for an extra £12.99 and £3.49 postage if you wish, a slightly cheaper option. Though there also was a time cost in that it occupied a lot of a weekend for me, it seems to have done what was needed, so it was worth the outlay.
Given the element of risk, Photoshop was deactivated to be on the safe side. That wasn't the only pre-upgrade action that was needed because the Windows 8 Pro 32-bit upgrade needs at least 16 GB before it will proceed. Of course, there was the matter of downloading the installer from the Microsoft website too. This took care of system evaluation and paying for the software, as well as the actual upgrade itself.
The installation took a few hours, with virtual machine reboots along the way. Naturally, the licence key was needed too, as well as the selection of a few options, though there weren't many of these. Being able to carry over settings from the pre-existing Windows 7 instance certainly helped with this and with making the process smoother too. No software needed reinstatement, and it doesn't feel as if the system has forgotten very much at all, a successful outcome.
Post-upgrade Actions
Just because I had a working Windows 8 instance didn't mean that there wasn't more to be done. In fact, it was the post-upgrade sorting that took up more time than the actual installation. For one thing, my digital mapping software wouldn't work without .Net Framework 3.5 and turning on the operating system feature from the Control Panel fell over at the point where it was being downloaded from the Microsoft Update website. Even removing Avira Internet Security after updating it to the latest version had no effect, and that was a finding during the Windows 8 system evaluation process. The solution was to mount the Windows 8 Enterprise ISO installation image that I had and issue the following command from a command prompt running with administrative privileges:
dism.exe /online /enable-feature /featurename:NetFX3 /Source:d:\sources\sxs /LimitAccess
For sake of assurance regarding compatibility, Avira has been replaced with Trend Micro Titanium Internet Security. The Avira licence won't go to waste, since I have another home in mind for it. Removing Avira without crashing Windows 8 proved impossible, though, and necessitating booting Windows 8 into Safe Mode. Because of much faster startup times, that cannot be achieved with a key press at the appropriate moment because the time window is too short now. One solution is to set the Safe Boot tick box in the Boot tab of MSCONFIG (or System Configuration, as it otherwise calls itself) before the machine is restarted. While there may be others, this was the one that I used. With Avira removed, clearing the same setting and rebooting restored normal service.
Dealing with a Dual Personality
One observer has stated that Windows 8 gives you two operating systems for the price of one: the one on the Start screen and the one on the desktop. Having got to wanting to work with one at a time, I decided to make some adjustments. Adding Classic Shell got me back a Start menu, and I omitted the Windows Explorer (or File Explorer as it is known in Windows 8) and Internet Explorer components. Though Classic Shell will present a desktop like what we have been getting from Windows 7 by sweeping the Start screen out of the way for you, I found that this wasn't quick enough for my liking, so I added Skip Metro Suite to speed up things. Though the tool does more than sweeping the Start screen out of the way, I have switched off these functions. Classic Shell also has been configured, so the Start screen can be accessed with a press of the Windows key. It has updated too so that boot into the desktop should be faster now. As for me, I'll leave things as they are for now. Even the possibility of using Windows' own functionality to go directly to the traditional desktop will be left untested while things are left to settle. Tinkering can need a break.
Outcome
After all that effort, I now have a seemingly more stable Windows virtual machine running Windows 8. Flitting between it and other Linux desktop applications has not caused a system freeze so far, and that was the result that I wanted. There now is no need to consider having separate Windows and Linux PC's with a NAS for sharing files between them, so that option is well off my wish-list. There are better uses for my money.
Not everyone has had my experience, though, because I saw a report that one user failed to update a physical machine to Windows 8 and installed Ubuntu instead; they were a Linux user anyway, even if they used Fedora more than Ubuntu. It is possible to roll back from Windows 8 to the previous version of Windows because there is a windows.old directory left primarily for that purpose. However, that may not help you if you have a partially operating system that doesn't allow you to do just that. In time, I'll remove it using the Disk Clean-up utility by asking it to remove previous Windows installations or running File Explorer with administrator privileges. Somehow, the former approach sounds the safer.
What About Installing Afresh?
While there was a time when I went solely for upgrades when moving from one version of Windows to the next, the annoyance of the process got to me. If I had known that installing the upgrade twice onto a computer with a clean disk would suffice, it would have saved me a lot. Staring from Windows 95 (from the days when you got a full installation disk with a PC and not the rescue media that we get now) and moving through a sequence of successors not only was time-consuming, but it also revealed the limitations of the first in the series when it came to supporting more recent hardware. It was enough to have me buying the full retailed editions of Windows XP and Windows 7 when they were released; the latter got downloaded directly from Microsoft. While these were retail versions that you could move from one computer to another, Windows 8 will not be like that. In fact, you will need to get its System Builder edition from a reseller and that can only be used on one machine. It is the merging of the former retail and OEM product offerings.
What I have been reading is that the market for full retail versions of Windows was not a big one anyway. However, it was how I used to work as you have read above, and it does give you a fresh system. Most probably get Windows with a new PC and don't go building them from scratch like I have done for more than a decade. Maybe the System Builder version would apply to me anyway, and it appears to be intended for virtual machine use as well as on physical ones. More care will be needed with those licences by the looks of things, and I wonder what needs not to be changed so as not to invalidate a licence. After all, making a mistake might cost between £75 and £120 depending on the edition.
Final Thoughts
So far, Windows 8 is treating me well, and I have managed to bend to my will too, always a good thing to be able to say. In time, it might be that a System Builder copy could need buying yet, but I'll leave well alone for now. Though I needed new security software, the upgrade still saved me money over a hardware solution to my home computing needs and I have a backup disk on order from Microsoft too. That I have had to spend some time settling things was a means of learning new things for me but others may not be so patient and, with Windows 7 working well enough for most, you have to ask if it's only curious folk like me who are taking the plunge. Still, the dramatic change has re-energised the PC world in an era when smartphones and tablets have made so much of the running recently. That too is no bad thing because an unchanging technology is one that dies and there are times when significant changes are needed, as much as they upset some folk. For Microsoft, this looks like one of them, and it'll be interesting to see where things go from here for PC technology.
Adding a Start Menu to Windows 8
16th October 2012For all the world, it looks like Microsoft has mined a concept from a not often recalled series of Windows: 3.x. Then, we had a Program Manager for starting all our applications, with no sign of a Start Menu. That came with Windows 95 and I cannot see anyone mourning the burying of the Program Manager interface either. It was there in Windows 95 if you knew where to look, and I do remember starting an instance, possibly out of curiosity.
Every Windows user seems to have taken to the Start Menu, regardless of how big it can grow when you install a lot of software on your machine. It didn't matter that Windows NT got it later than Windows 9x ones either; NT 3.51 has the Program Manager too, and it was NT 4 that got the then new interface that has been developed and progressed in no less than four subsequent versions of Windows (2000, XP, Vista & 7). Maybe it was because computing was the preserve of fewer folk that the interchange brought little if any sign of a backlash. The zeitgeist of the age reflected the newness of desktop computing, and its freshness probably brought an extra level of openness too.
Things are different now, though. You only have to hear of the complaints about changes to Linux desktop environments to realise how attached folk become to certain computer interfaces. Ironically, personal computing has just got exciting again after a fairly stale decade of stasis. Mobile computing devices are aplenty nowadays, and it no longer is a matter of using a stationary desktop PC or laptop, even if those brought their own excitement in the 1990's. In fact, reading a title like Computer Shopper reminds me of how things once were with it's still sticking with PC reviews while others are not concentrating on them as much. Of course, the other gadgets get reviewed too, so it is not stuck in any rut. Still, it is good to see the desktop PC getting a look in an age when there is so much competition, especially from phones and tablets.
In this maelstrom, Microsoft has decided to do something dramatic with Windows 8. It has resurrected the Program Manager paradigm in the form of the Start screen and excised the Start Menu from the desktop altogether. For touch screen computing interfaces such as tablets, you can see the sense of this, but it's going to come as a major surprise to many. Removing what lies behind how many people interact with a PC is risky, so you have to wonder how it will work out for all concerned.
What reminded me of this was a piece on CNET by Mary Jo Foley. Interestingly, software is turning up that returns the Start Menu to Windows 8. One of these is Classic Shell, and I decided to give it a go on a Windows 8 Enterprise evaluation instance that I have. Installation is like any Windows program, and I limited the options to the menu and updater. At the end of the operation, a button with a shell icon appeared on the desktop's taskbar. You can make the resultant menu appear like that of Windows XP or Windows 7 if you like. There are other settings like what the Windows key does and what happens when you click on the button with a mouse. By default, both open the new Start Menu, and holding down the Shift key when doing either brings up the Start screen. This is customisable, so you can have things the other way around if you so desire. Another setting is to switch from the Start screen to the desktop after you log into Windows 8 (you may also have it log in for you automatically, but it's something that I do not think anyone should be doing). While the Start screen does flash up, things move along quickly; maybe having not appear at all would be better for many.
Classic Shell is free of charge and worked well for me, apart from that small rough edge noted above. It is also open source and looks well maintained too. For that reason, it appeals to me more than Stardock's Start8 (currently in beta release at the time of writing) or Pokki for Windows 8, which really is an App Store that adds a Start Menu. If you encounter Windows 8 on a new computer, then they might be worth trying should you want a Start Menu back. Being an open-minded type, I could get along with the standard Windows 8 interface, yet it's always good to have choices too. Most of us want to own our computing experience, it seems, so these tools could have their uses for Windows 8 users.
Widely differing approaches
28th January 2012The computer on which I am writing these words is running Linux Mint with the Cinnamon desktop environment, a fork of GNOME Shell. This looks as if it will be the default face of GNOME 3 in the next version of Linux Mint, with the MGSE dressing up of GNOME Shell looking more and more like an interim measure until something more consistent was available. While some complained that what was delivered in version 12 of the distribution was a sort of greatest hits selection, I reckon that bets were being hedged by the project team.
Impressions of what's coming
By default, you get a single panel at the bottom of your screen with everything you need in there. However, it is possible to change the layout so that the panel is at the top or there are two panels, one at the top and the other at the bottom. So far, there is no means of configuring which panel applet goes where, as was the case in Linux Mint 11 and its predecessors. However, the default placements are very sensible, so I have no cause for complaint at this point.
Just because you cannot place applets doesn't mean that there is no configurability, though. Since Cinnamon is extensible, you can change the way that time is displayed in the clock, as well as enabling additional applets. It also is possible to control visual effects, such as the way new application windows pop up on a screen.
GNOME 3 is there underneath all of this, though there's no sign of the application dashboard of GNOME Shell. The continually expanding number of slots in the workspace launcher is one sign, as is the enabling of a hotspot at the top right hand corner by default. This brings up an overview screen showing what application windows are open in a workspace. The new Mint menu even gets the ability to search through installed applications, together with the ability to browse through what's available.
In summary, Cinnamon already looks good, though a little polish and extra configuration options wouldn't go amiss. An example of the former is the placement of desktop numbers in the workspace switcher, and I already have discussed the latter. It does appear that the Linux Mint approach to desktop environments is taking shape with a far more conventional feel than the likes of Unity or GNOME Shell. Just as Cinnamon has become available in openSUSE, I can see it gracing LMDE too whenever Debian gets to moving over to GNOME 3 as must be inevitable now unless they take another approach such as MATE.
In comparison with a revolution
While Linux Mint are choosing convention and streamlining GNOME to their own designs, it appears that Ubuntu's Unity is getting ever more experimental as the time when Ubuntu simply evolved from one release to the next becomes an increasingly more distant memory. The latest development is the announcement that application menus could get replaced by a heads-up display (HUD) instead. That would be yet another change made by what increasingly looks like a top-down leadership, reminiscent of what exists at Apple. While it is good to have innovation, you have to ask where users fit in all of this when Linux Mint already has gained from what has been done so far and may gain more again. Still, seeing what happens to Ubuntu sounds like an interesting pastime, though I'm not sure that I'd be depending on the default spin of this distro as my sole operating system right now. Also, changing the interface every few months wouldn't work in a corporate environment at all, so you have to wonder where Mark Shuttleworth is driving all this, though Microsoft is engaging in a bit of experimentation of its own. We are living in interesting times for the computer desktop, so it's just as well that there are safe havens like Linux Mint, too. Watching from afar sounds safer.
A little look at Windows 8
6th November 2011Even if it has been a little while, I have managed to set up a VirtualBox virtual machine to have a look at the Developer Preview of the next version of Windows, something that I and others continue to call Windows 8 though Microsoft has yet to confirm the name. When I tried the installation before, it failed on me, though that may have been due to having an earlier release of VirtualBox on my machine at that time. 4.1.14 has a preset for Windows 8 and I also happened to notice that it can create virtual hard disks that can be used with competitors like VMWare, Parallels and Virtual PC too. It's an interesting development, even if I am left wondering why you'd need to do that when VirtualBox runs on most platforms anyway.
To get back to Windows 8, the installation ran near enough without any intervention apart from stating the language you wanted to use, U.K. English in my case. On startup, the operating system presents you with a lock screen that you need to get out of the way so you can log in. It can be dragged out of your way, or you can double-click on it or use the carriage return key to get rid of it. Quite why someone thinks it's a good extra is a little beyond me, when a log in screen would suffice. Logging in gets you the new start menu or, as I prefer to think of it, screen. By default, there are a good few Metro apps installed, though I decided to rid myself of most of them.
Regarding those apps, one irritation could be that there isn't that obvious a way to switch away from them to something else. Thankfully, ALT+TAB does seem to work and it has the most instantaneous effect. Otherwise, using the Windows key or hovering over the bottom-left corner of the screen to get the menu that brings up the start screen. From the PC user's point of view, I could see this needing a little more thought because it took a little while for me to figure out what to do. Closing Metro apps isn't an option either unless you resort to the Task Manager to do so. Microsoft appears to want to leave them open from the point at which you start them until the PC is shut down. It's a design decision that leaves me unconvinced, though; thoughts of rogue apps running riot on a system come to mind. Then, a stop button could be handy.
There is no start menu as we have come to know it any more with the start screen replacing it. However, it is possible to limit what's on there to the software that you use most often and rearrange panels as you'd like them to be. Apart from hosting shortcuts for starting applications, it also acts as a task switcher like the task bar in Windows 7 and there is one of those in Windows 8 too when you jump to the desktop; handily, there's a panel for that too. Installing Firefox added a panel to the start screen, so a little thought has gone into such a common situation, and that's just as well. Still, there's more work to be done because, currently, there's no way of changing the background colour of the start screen without resorting to a hex editor or third party tools. Still, since you can pick your own picture for the lock screen, things are not all locked down on you.
A preview of IE 10 is included and, apart from the occasional artifact when displaying one of my websites, it seems to work well enough, as does Windows Explorer. However, aside from these and a smattering of Metro apps, the Developer Preview does feel barer than previous versions of Windows. However, it does appear that applications like Notepad, PowerShell and the Command Prompt are on there, yet you need to search for these. That also means that you need to know about them too, so I'd suggest a better way of browsing the applications that are available too. This is one of the weaknesses of Ubuntu's Unity interface, and you need to search in the Dash to find them. Just starting to type in the Metro start screen (and other screens too, it seems) in Windows does trigger the completion of a search box, much like what happens in the GNOME Shell Activities screen on systems with GNOME 3. While it's good to see good ideas being reused from elsewhere, Microsoft might do well to note that you still can browse lists of applications in GNOME 3 too.
Shutting down Windows 8 also is seemingly more convoluted than is the case with Windows 7. Logging off and then powering off from the log in screen is one approach, and that was my early impression of GNOME 3 too. With the latter, I later discovered a status menu plugin that added in the option where it was accessible or that using the ALT key when clicking the status menu when the plugin wouldn't work would do what I needed. Without logging off from Windows 8, you can do a shutdown using the sidebar that appears on selecting Settings from the menu that pops up on hovering near the bottom-left corner of the start screen or the Start button of the task bar of the desktop. Then, look for the power icon and select what you need from the menu that clicking on this icon produces. Of course, you may find that the ALT+F4 key combination when issued while on a clean desktop is the cleanest of all.
All in all, the Developer Preview of the next release of Windows looks fairly usable. That is not to imply that there aren't things that need changing. Aside from this being an early sight of what may be coming to us Windows users, it isn't unknown for Microsoft to roll back on a radical move to make it more palatable to the user community. After all, it has to watch how it treats the corporate market too. The strong possibility of there being alterations is one thought that needs to be shared with those who are inclined to lose their tempers at the moment and I have seen comments with unpleasant language out there on the web (none of that here, please, by the way). As for me, I like to look ahead to be forewarned about what's coming my way in the world of computing. What I have seen so far of the next Windows release is reassuring, though there are rough edges such as PC shutdown and Metro app switching, yet Microsoft cannot commit commercial suicide either, so these have to be fixed. It appears that the world of Microsoft operating systems is in flux, with the company's keeping a firm eye on the world of mobile computing, with tablets being a major concern. While others may disagree, I can see Windows 8 working well on conventional PC's and that's no bad thing.
All Change?
19th September 2011Could 2011 be remembered as the year when the desktop computing interface got a major overhaul? One part of this, Windows 8, won't be with us until next year, but there has been enough happening so far this year that has resulted in a lot of comment. With many if not all the changes, it is possible to detect the influence of interfaces used on smartphones. After all, the carry-over from Windows Phone 7 to the new Metro interface is unmistakeable.
Two developments in the Linux world have spawned a hell of an amount of comment: Canonical's decision to develop Unity for Ubuntu and the arrival of GNOME 3. While there have been many complaints about the changes made in both, there must be a fair few folk who are just getting on with using them without complaint. Maybe there are many who even quietly like the new interfaces. While I am not so sure about Unity, I surprised myself by taking to GNOME Shell so much that I installed it on Linux Mint. It remains a work in progress, as does Unity, but it'll be very interesting to see it mature. Perhaps a good number of the growing collection of GNOME Shell plugins could make it into the main codebase. If that were to happen, I could see it being welcomed by a good few folk.
There was little doubt that the changes in GNOME 3 looked daunting, so Ubuntu's taking a different approach is understandable until you come to realise how change that involves anyway. With GNOME 3 working so well for me, I feel disinclined to dally very much with Unity at all. In fact, I am writing these words on a Toshiba laptop running UGR, effectively Ubuntu running GNOME 3, and that could become my main home computing operating system in time.
For those who find these changes not to their taste, there are alternatives. Some Linux distributions are sticking with GNOME 2 as long as they can, and there apparently has been some mention of a fork to keep a GNOME 2 interface available indefinitely. However, there are other possibilities such as LXDE and XFCE out there too. In fact, until GNOME 3 won me over, LXDE was coming to mind as a place of safety until I learned that Linux Mint was retaining its desktop identity. As always, there's KDE too, but I have never warmed to that for some reason.
The latest version of OS X, Lion, also included some changes inspired by iOS, the operating system that powers both the iPhone and iPad. However, while the current edition of PC Pro highlights some disgruntlement in professional circles regarding Apple's direction, this does not seem to have aroused the kind of ire that has been abroad in the world of Linux. Is it because Linux users want to feel that they are in charge and that iMac and MacBook users are content to have decisions made for them so long as everything just works? Speaking for myself, the former description seems to fit me, though having choices means that I can reject decisions that I do not like so much.
At the time of writing, the release of a developer preview of the next version of Windows has been generating a lot of attention. It also appears that changes are headed for Windows users too. However, I get the sense that a more conservative interface option will be retained and that could be essential for avoiding the alienation of corporate users. After all, I cannot see the Metro interface gaining much favour in the working environment when so many of us have so much to do. Nevertheless, I plan to get my hands on the developer preview to have a look (the weekend proved too short for this). It will be very interesting to see how the next version of Windows develops, and I plan to keep an eye on it as it does so.
It now looks as if many will have their work cut out if they are to avoid where desktop computing interfaces are going. Established paradigms are being questioned, particularly as a result of touch interfaces on smartphones and tablets. Wii and Kinect have involved other ways of interacting with computers, too, so there's a lot of mileage in rethinking how we work with computers. So far, I have been able to deal with the changes in the world of Linux, but I am left wondering about the changes that Microsoft is making. After Vista, they need to be careful and they know that. Maybe, they'll be better at getting users through changes in computing interfaces than others, but it'll be very interesting to see what happens. Unlike open source community projects, they have the survival of a massive multinational at stake.
Restoring the MBR for Windows 7
25th November 2010During my explorations of dual-booting of Windows 7 and Ubuntu 10.10, I ended up restoring the master boot record (MBR) so that Windows 7 could load again or to find out if it wouldn't start for me. The first hint that came to me when I went searching was the bootsect command, but this only updates the master boot code on the partition, so it did nothing for me. What got things going again was the bootrec command.
To use either of these, I needed to boot from a Windows 7 installation DVD. With my Toshiba Equium laptop, I needed to hold down the F12 key until I was presented with a menu that allowed me to choose from what drive I wanted to boot the machine, the DVD drive in this case. Then, the disk started and gave me a screen where I selected my location and moved to the next one where I selected the Repair option. After that, I got a screen where my Windows 7 installation was located. Once that was selected, I moved on to another screen from I started a command line session. Then, I could issue the commands that I needed.
bootsect /nt60 C:
This would repair the boot sector on the C: drive in a way that is compatible with BOOTMGR. Though this wasn't enough for me, it was something worth trying anyway in case there was some corruption.
bootrec /fixmbr
bootrec /fixboot
The first of these restores the MBR, and the second sorts out the boot sector on the system drive (where the Windows directory resides on your system). In the event, I ran both of these and Windows restarted again, proving that it had come through disk partition changes without a glitch, though CHKDISK did run in the process, but that's understandable. There's another option for those wanting to get back their boot menu, and here it is:
bootrec /rebuildbcd
Though I didn't need to do so, I ran that too, but later used EasyBCD to remove the boot menu from the start-up process because it was surplus to my requirements. That's a graphical tool that has gained something of a reputation since Microsoft dispensed with the boot.ini file that came with Windows XP for later versions of the operating system.
Sometimes it's a small change that matters...
24th January 2010Firefox 3.6 is now available and others are going on about more striking features, but it's a small change that I have noticed, which happens to be a good one too. Middle-clicking on a link in a tab used to open a new one on the right hand of the tab bar. Now, the new tab opens next to the one where the click was clicked, which is a good thing if you are previewing blog posts. It was something that Internet Explorer already did, so it's good to see cross-fertilisation of useful features; yes, Microsoft can come up with good ones too from time to time. Though not likely to make major headlines, this is the type of thing that makes for a better user experience, and a few of them together can be more beneficial than some big shiny new feature. In life, it's often the little things that make all the difference.
Understanding Outlook's 32 KB rule limit: What happens when you upgrade from Outlook 2000 to Outlook 2007
12th January 2010A move from Outlook 2000 to Outlook 2007 at work before Christmas resulted in deactivated Outlook rules and messages like the following when I tried reactivating them:
One or more rules could not be uploaded to Exchange server and have been deactivated. This could be because some of the parameters are not supported or there is insufficient space to store all your rules.
The cause is a 32 KB size limitation for all rules associated with your Exchange server account before Exchange 2007. With the latter, the default size increases to 64 KB and can be increased further to 256 KB by manual intervention. Though this wouldn't be a big issue if you had the option to store rules locally on your own PC, but that was removed after Outlook 2000, therefore explaining why I first encountered it when I did.
Microsoft has a useful article on their support website containing suggested remedies which aren't all as extreme as deleting some rules either. Consolidation and shortening of rule names are other suggestions, and you should never discount how much space the "run on this machine only" parameter takes up either. Still, Microsoft made an odd design decision that caused this issue, not that it is their first or even last such choice.
So you just need a web browser?
21st November 2009When Google announced that it was working on an operating system, it was bound to result in a frisson of excitement. However, a peek at the preview edition that has been doing the rounds confirms that Chrome OS is a very different beast from those operating systems to which we are accustomed. The first thing that you notice is that it only starts up the Chrome web browser. In this, it is like a Windows terminal server session that opens just one application. Of course, in Google's case, that one piece of software is the gateway to its usual collection of productivity software like Gmail, Calendar, Docs & Spreadsheets and more. Then, there are offerings from others too, with Microsoft just beginning to come into the fray to join Adobe and many more. As far as I can tell, all files are stored remotely, so I reckon that adding the possibility of local storage and management of those local files would be a useful enhancement.
With Chrome OS, Google's general strategy starts to make sense. First create a raft of web applications, follow them up with a browser and then knock up an operating system. It just goes to show that Google Labs doesn't simply churn out stuff for fun, but that there is a serious point to their endeavours. In fact, you could say that they sucked us in to a point along the way. Speaking for myself, I may not entrust all of my files to storage in the cloud, yet I am perfectly happy to entrust all of my personal email activity to Gmail. It's the widespread availability and platform independence that has done it for me. For others spread between one place and another, the attractions of Google's other web apps cannot be understated. Maybe, that's why they are not the only players in the field either.
With the rise of mobile computing, that kine of portability is the opportunity that Google is trying to use to its advantage. For example, mobile phones are being used for things now that would have been unthinkable a few years back. Then, there's the netbook revolution started by Asus with its Eee PC. All of this is creating an ever internet connected bunch of people, so having devices that connect straight to the web like they would with Chrome OS has to be a smart move. Some may decry the idea that Chrome OS will be available on a device only basis, but I suppose they have to make money from this too; search can only pay for so much, and they have experience with Android too.
There have been some who wondered about Google's activities killing off Linux and giving Windows a good run for its money; Chrome OS seems to be a very different animal to either of these. It looks as if it is a tool for those on the move, an appliance, rather than the pure multipurpose tools that operating systems usually are. If there is a symbol of what an operating system usually means for me, it's the ability to start with a bare desktop and decide what to do next. Transparency is another plus point, with the Linux command line having that in spades. For those who view PC's purely as means to get things done, such interests are peripheral, and it is for these that the likes of Chrome OS has been created. In other words, the Linux community need to keep an eye on what Google is doing but should not take fright because there are other things that Linux always will have as unique selling points. Even though the same sort of thing applies to Windows too, Microsoft's near stranglehold on the enterprise market will take a lot of loosening, perhaps keeping Chrome OS in the consumer arena. Counterpoints to that include the use GMail for enterprise email by some companies and the increasing footprint of web-based applications, even bespoke ones, in business computing. In fact, it's the latter that can be blamed for any tardiness in Internet Explorer development. In summary, Chrome OS is a new type of thing rather than a replacement for what's already there. We may find that co-existence is how things turn out, but what it means for Linux in the netbook market is another matter. Only time will tell on that one.