How To Recover From ‘Testing Memory’ System Halt After Installing Comodo Time Machine

Comodo Time Machine is a fantastic product. Allowing you to completely ruin your Windows operating system, and then restore it back as good as new with the click of a button (well, maybe more than one click). By that I mean its great software for being able to roll back after your kids have just destroyed the OS directories or you have suffered damage by a virus.

For most users, the installation is a breeze and Comodo Time Machine does it’s job. Unfortunately, this is not the case for all of us.

I’ve been installing Comodo Time Machine on systems for a little while now, and more than once, after the initial installation, I get the following error message upon boot up:

Testing Memory <Hexadecimal Value>...

Something went wrong. I don’t know exactly what, and perhaps a helpful reader can fill us in, however at this point, it would seem all is lost. Now, I’ve only tested this so far on PCs with Windows Vista and Windows 7. So if you have Windows XP, you made need to use a little additional effort.

If you have Windows 7 or Windows Vista, possibly like me, your first thought was ‘No worries, I’ll use the System Repair Utility on the my installation media’. This won’t work. ‘Startup Repair’ won’t be able to solve the issue, and neither will rolling back to a ‘System Restore’ point. It simply won’t work, yet.

Even though this is a problem for you, as far as your computer and operating system are concerned, there is no issue. Which is correct. Yes, Comodo Time Machine has failed to install correctly (of which there are many reasons why this may occur, one being lack of space on drive ‘C:’), however that has not really done any harm to your PC. You just simply can’t get into Windows!

If you have Windows 7 or Windows Vista, yes Startup Repair can help you, but first you have to give it something to repair. I was pretty desperate when this first happened to me, and I actually ended up re-installing the entire system. Not the second time around though. No way was I re-installing, especially since I didn’t have a backup of my clients system, and I was working on site without additional PCs to help my efforts.

In come Hirens Boot CD. Admittedly, you could use any number of rescue boot CDs out there on the internet, I happened to have Hirens Boot CD 10.0 which had exactly the tools I needed. In CD/ISO form, Hirens boot CD does contain some software that others would call ‘commercial’ thus I can’t provide you with a download link to the ISO. However, this page, and this page, should get you on the right track.

Once you have the CD prepared (or USB Key), place it in your computer, and boot from it. Most recent computers are capable of booting from a USB device or CD-ROM. In fact, I don’t think I’ve ever come across a computer that couldn’t boot from CD-ROM, and I’ve worked on some old PCs!

Don’t try booting the ‘MiniXP’ It’s a little over kill for what we are going to do, although it is a very VERY responsive Windows XP based environment with most of the tools available. MiniXP runs entirely from memory, meaning you can remove the CD or USB Key once it has finished booting! Neat huh?!

Choose to ‘StartBootCD’. At the ‘Hirens All in 1 BootCD 10.1 Menu’ menu, you’ll need to use your keyboard to select option 9, then select option 1, then select option 2. You should now have MBRtool loaded.

This program requires just a little understanding about the configuration of your HDDs in your computer. For simplicity sake however, if your computer only has one HDD with only one partition on it, the following instructions will work just fine. If your computer has multiple HDDs, and you don’t boot from the otherwise known as the ‘first HDD’ then you need to pay attention to the screen and modify the instructions below accordingly. Feel free to ask for help in the comments below.

Enter 4 and press [Enter]

Enter 6 and press [Enter]

Enter 0 and press [Enter] (Zero)

Enter o and press [Enter] (O, as in the circled shaped letter for Orange) <– This final step will wipe your MBR straight away, no questions asked. If you are feeling concerned, nervous or worried at this point, I suggest you reboot again and use another program on the CD called ‘ghost’ to clone your HDD in its current state to a safe location.

Remember, I said we need to give Windows 7 / Windows Vista Startup Repair tool, something to fix? Well, now it has something to fix!

Press the [ESC] key three times to return you to the DOS prompt. Remove the CD/USB, put your Windows 7 or Windows Vista installation media in the drive and type: reboot (followed by a press of the enter key). Be sure to boot from your newly inserted installation media again.

After selecting your language, Time and currency format and Keyboard or input method, click Next. Click the text link ‘Repair your computer’. The ‘System Recovery Options’ window will appear. Don’t be alarmed at the fact that it doesn’t detect your installed operating system (Windows 7 or Windows Vista), this is what we want!

Click the next button, and from the main menu choose ‘Startup Repair’. This process should only take a few seconds. If you want some assurance it worked, click the ‘Click here for diagnostic and repair details’ link and scroll to the bottom. You should see something like this:


Root cause found:
----------------------------
MBR is corrupt
Repair action: Disk metadata repair
Result: Completed succesfully. Error code = 0x0
Time taken = ####ms
----------------------------
----------------------------

Click the Close button and click the Finish button. Your system should automatically reboot. If not, click the Restart button.

Hopefully you are now staring at your Windows 7 / Windows Vista logon screen or desktop!

For Windows XP Users

 Thankfully Windows XP has something  a little less evolved, but no less powerful called ‘The Recovery Console’. To access it, you’ll need an original Windows XP (SP1/2/3) installation media disc. Boot from the media and when prompted, press the R key.

When you are asked for the Administrator password, enter it. If you are on Windows XP Home, and you’ve never configured an Administrator password, chances are it’s blank, so just press enter. This may apply to some Windows XP Professional users as well.

At the prompt, assuming you have Windows XP installed to C:\> type:

fixmbr

Ignore the warnings, unless you understand what they are (your situation couldn’t get any worse at this point anyway), and press the [Y] key followed by pressing the [Enter] key.

Type:

exit

to leave the recovery console and reboot. Hopefully you are now staring at your Windows XP Logon screen or desktop!

Why Does This Work?

When you install Comodo Time Machine, it makes a modification to your HDD MBR (Master Boot Record) telling your computer to first boot Comodo Time Machine (instead of your Windows OS), which in turn is configured to boot your Windows OS. When we use MBRtool to erase your MBR, we then use one of the options above to rebuild or repair your MBR. Regardless of Windows XP, Vista or 7, your MBR will be repaired/rebuilt to only boot your Windows OS again! By passing Comodo Time Machine altogether.

What About Comodo Time Machine?

It’s up to you. If you try again and it fails, you know now you have a way to get things working again. Having said that, I’ve had an almost 100% success rate when installing Comodo Time Machine again the second time around. I don’t why sometimes it fails the first time around like it does, it just does.

Any comments, improvements or criticism is welcome.

Kudos to qmchenry at Tech-Recipes for the Windows XP Recovery Console instructions, where you can find additional comments and instructions about it’s use.

Can’t Access Windows 2000 or Windows XP File and Printer Shares From Windows 7

Can’t access file shares and shared printers on your Windows 2000 or Windows XP Machines from Windows 7? The solution is below. I had this issue for a few days and finally, after searching through heaps of forum threads and posts, stumbled across the solution. The solution was originally posted on Windows Client Tech Centre forums (by a user known as ‘shooda‘).

On your Windows 7 Machines:

  1. Access the ‘Run’ command (otherwise known as the run box). If you can’t see it in your Start Menu, try enabling it in the ‘Superbar’ (the Task Bar) properties or on your keyboard press the ‘Windows’ (WIN) key and the ‘R’ key at the same time.
  2. Type: gpedit.msc (press enter or click OK)
  3. Make your way down through Computer Configuration
    1. Windows Settings
      1. Security Settings
        1. Local Policies
          1. Security Options
          2. And double click on ‘Network security: LAN Manager authentication level’
            1. Click the drop down box and select the option ‘Send LM & NTLM Responses’
            2. Click OK
  4. Close the Local Group Policy Editor.
  5. Done! Try accessing file and printer shares on your Windows 2000 and Windows XP machines from your Windows 7 machines.

More information (as technical as it is) can be found here.

VMware Server 1.0.9 on CentOS 5.3

The contents of this guide should work perfectly fine on a base (yes that’s base, not bare bones) only installation of either CentOS 32/64 bit or RHEL 5.3 32/64 bit. If you have any troubles, please do leave a comment and I’ll do my best to assist you. This guide assumes you are setting up your machine to be a server, although the steps will work just fine on a machine configured to be a desktop.

Install CentOS 5.3 32/64 Bit

If you haven’t installed CentOS 5.3 already, you should do so. Kinda hard to use VMware Server 1.0.9 without an operating system. Most people want the host OS to have as little additional crap as possible. In regards to that, during the installation, make a point of not installing any additional packages, or package groups except the ‘Base’ group (oh and leave the base group in it’s default state, don’t go ticking on any extras, you’ll make the installation install more dependancies thus more crap). So in other words, only the ‘Base’ group should be ticked, untick the rest!

Nope, you won’t have any GUI, and even if you did, you still have to do the rest of the configuration at the command line anyway. VMware Server 1.0.9 host with GUI = bad idea, unless of course your host is also your desktop.

Once installed, configure your host as you like it from the ‘firstboot’ screen and than login as root. Here’s a few tips.

  • Disable any services you aren’t using.
  • Disable SE Linux
  • Unless you’re going to configure and use it with VMware Server 1.0.9 machines, disable ip6tables
  • Don’t go configuring special firewall rules just yet, leave that until later.

Even though it’s the host, its’ software should still be up to date. Issue the following command and download any updates.

yum update

Updates finished? Awesome! Lets reboot the server and start the next step afresh.

shutdown -r now

Install VMware Server 1.0.9 Required Components.

Plenty of you will argue about what you do and don’t need to complete the install. Well, I’ve completed this configuration of server with VMware Server more times than I care to remember now, and sometimes I needed all of these packages and sometimes I didn’t. No, I didn’t bother to find out why. Do you know why? Great! Put it in the comments!

Login in as root and issue the following commands one after the other. Yes, you can issue them all at once if you’re clever, I like to take my time, in case the worlds explodes.

yum install kernel-devel
yum install kernel-headers
yum install libXtst*
yum install xinetd
yum install gcc*

On a couple of occasions, I needed the following package – It could have been when I was using CentOS 5.3 64Bit

yum install libXdmcp-devel
yum install libXrender*

What does the ‘*’ mean? It means grab any packages that start with ‘anytextbeforethe*’

Installed all the packages? Fantastic! Lets reboot the server and start the next step afresh.

shutdown -r now

Install VMware Server 1.0.9

How you get the installation package of VMware Server 1.0.9 onto your server is up to you. Here are a few tips.

  • Download VMware Server 1.0.9 Here or Here
  • Make sure you register for a VMware Server serial number or numbers. It’s free.
  • You can use WinSCP to transfer VMware Server 1.0.9. to your server (it uses SSH). Get it Here or Here.
  • You could use the wget command with the direct link above, directly on your server, like this:
    • wget -c http://download3.vmware.com/software/vmserver/VMware-server-1.0.9-156507.i386.rpm
  • Burn it to a CD
  • Burn it to a DVD
  • Transfer it to a USB Drive

Once you have the VMware Server 1.0.9 installation file on your server, installing is pretty straight forward. If you’ve never installed a RPM file before, pay attention, people go to university for this stuff. Make sure you are logged in as root, and issue the following:

rpm -ivh VMware-server-1.0.9-156507.i386.rpm

Easy, no?

Depending on the power of your server, it may take a few minutes to install. Once installed, we have one last final step. No need to reboot this time!

Configuring VMware Server 1.0.9

Issue the following command. If some or none of the required packages are not installed, this will tell you straight away.

vmware-config.pl

or if you are so inclined:

/usr/bin/vmware-config.pl

Both do the exact same thing. Don’t run both (either by concatenating them both together or one after the other), that would just be silly and make you leave a comment about how you ran both and got an error message.

NB: If you are told that some packages or components are missing, I suggest going back and re-issuing the ‘yum’ commands above in the section ‘Install VMware Server 1.0.9 Required Components‘. Before you issue any commands, press ctrl-c to quit the setup program and return to the command prompt.

If you see something like the following, you are good to go:

Making sure services for VMware Server are stopped.

Stopping VMware services:
   Virtual machine monitor                                 [  OK  ]

You must read and accept the End User License Agreement to continue.
Press enter to display it.

The configuration settings of VMware Server 1.0.9 is now up to you. Here are a few tips:

  • Accept the agreement, type Y or Yes and press the enter key.
  • The defaults are all fine.
  • In most cases, Bridged networking is what you are after, so say ‘No’ to host only and NAT (unless you know what they are and you are going to use them)
  • Sometimes the installation would tell me that port 902 is unavailable. This is not true. Override by typing in 902, otherwise you’ll need to remember 904 (or whatever other number you select) and type it in every time when you use the VMware Server 1.0.9 client. Not cool.
  • At the very least, choose your own location for the storage of VMware Server 1.0.9 servers. I always put mine in /home/vmware (because I have /home on a separate partition)
  • Put your Serial Key in now, rather than later.

Installation and Configuration is now complete! If you need any further help / assistance, please, feel free to leave a comment

Proxmox OpenVZ Server 2 NICs 2 Gateways

These are two solutions that worked for me. They are by no means the only solutions.

My Predicament.
A server (a Dell SC440), with two physical network interfaces. Our office has two ISP connections (DSL broadband). We have the one internal network range (192.168.1.0/24) with two gateways (1.254 and 1.221).

I have installed Promox on the server. I wanted to be able to choose which gateway the guest containers used, instead of them being locked into using the same gateway as the host server. Some of the guest OS containers will host services via the first ISP, and the others will host services via the second ISP. (obviously with firewall rules etc configured in our gateways). So the container gateway entries need to point to their respective ISP/Gateway.

Note: While the security advantage of venet over veth is certainly worthwhile in a hosting environment (and others as well), in my case, we have two hardware firewalls that haven’t let us down yet, and there is little to no concern for the possibility of an internal hacker (there are only three of us!)

Continue Reading Proxmox OpenVZ Server 2 NICs 2 Gateways