Dual Boot Windows and Linux: Single and Multiple Hard Drives

The internet is full of technical articles, many of which are way too complicated for the average computer user who just wants to solve a simple problem. If you pay close attention, the internet is also a place where the “gurus” spend a lot of time yelling for help in discussion boards and forums. So don’t feel bad, nobody has all the answers.

So you want to dual boot Windows and Linux on the same computer–it is really quite easy. I only have enough room here to tell you the most common way to do this on a single hard drive or using multiple hard drives. Obviously then, there are many ways to get the job done, but there are some critical things you should know. Let’s start with some critical information.

Windows and Linux: Same Hard Drive

The windows operating system MUST occupy the master boot record (MBR). Linux, on the other hand does not have to. In this scenario, you must install windows first! After Windows has been successfully installed, then you can install Linux. This is critical! The Linux “boot loader” is called GRUB. When you install Linux–MAKE SURE YOU DO NOT INSTALL THE LINUX BOOT LOADER TO THE MBR.

Configure the Windows Boot Loader: A Two Step Process

It is also possible to use GRUB to dual boot Windows and Linux on the same drive but this is a bit more complex–the Windows boot loader will get the job done. In the following commands, you will create a copy of the Linux boot sector and then save it in a file in the top level directory under Windows (C:).

Step 1: Linux

From the shell in your Linux installation (boot from your installation disks):

Execute the following shell command, replacing /dev/hda3 with the location of your Linux boot partition.

shell# dd if=/dev/hda3 of=/bootsect.lnx bs=512 count=1

Copy the new file–bootsect.lnx–to a floppy disk and reboot to Windows.

Step 2: Windows

Copy bootsect.lnx to C: in Windows. Then execute the following command at the DOS prompt.

C:> attrib -H -R -S boot.ini

Edit boot.ini so that the first two lines are:

[boot loader]

timeout=30

After the last line, add:

c:bootsect.lnx=”Start Linux”

That’s it, you are done! Reboot your machine and you will see a menu allowing you to select either Windows or Linux. Congratulations.

Windows and Linux: Two Hard Drives

This is also quite easy. In this case, you will boot to the Linux drive. We will add Windows to the Linux boot loader (i.e., GRUB). GRUB is my favorite boot loader.

Edit the /boot/grub/grub.conf file. One of the very first lines should contain:

timeout=30

After the last line add:

title Start Windows

map (hd1) (hd0)

map (hd0) (hd1)

rootnoverify (hd1,0)

makeactive

chainloader +1

Reboot your machine to the Linux drive and you will see a menu allowing you to select between Linux or Windows. Nice work!

This article is obviously short and does not include any explanations of how these commands work. There are variations on what I have shown here depending on your hardware setup, but I believe that these are the most common and should get the job done nicely. I would be happy to direct you to additional resources if this does not work for you.

Copyright 2005 Majella.us



Source by David Picella

Windows 10 Error 0xc000021a

The 0xc000021a error stands for “STATUS_SYSTEM_PROCESS_TERMINATED” – basically meaning that Windows encountered an error so deep within the system that it was unable to continue running.

It displays as a BSOD (Blue Screen of Death) when you turn on your system, and is generally triggered when you upgrade a Windows 10 PC.

Blue Screens of Death are a famous element of Windows (with many people citing the problem starting with Windows 95) – causing the system to unexpectedly crash (and show a “blue” error screen).

Whilst trivial for many people, the BSOD actually represents a problem deep within the heart of the Windows system.

Either some element of the software stack, or its connection to the system’s hardware, has caused an error so grave that Windows cannot continue operating.

The most typical BSOD errors occur as a result of driver issues. This error is caused by a botched Windows Update.

Causes

The main causes of the error include:

  • Windows Update didn’t complete successfully (but left files on your system)
  • The Update files installed on your PC did not completely overwrite the old ones
  • Your system may have blocked certain installation processes from completing (antivirus etc)

Typically, the following files will be at fault:

  • winlogon.exe – responsible for logon/log off protocols within Windows 10. If it’s damaged in any way, it will cause issues such as the one you’re experiencing
  • csrss.exe – used by Windows to manage graphical interactivity for the system. If this is damaged, corrupted or out of date, errors such as you’re experiencing will show

Because it’s a BSOD (otherwise known as a “STOP” error), we will need to ensure we can apply fixes outside the normal operating environment of Windows.

This can be achieved using the steps below:

Solution

The way to fix the error is to make sure that you have all the “startup” files/settings repaired properly…

1. Perform “Startup Repair”

The first step is to ensure you’re able to run a “startup repair” on Windows 10.

Startup repairs are designed to provide a clean set of “boot” records – allowing for resolutions to the likes of issues as you’re experiencing…

  • If you can gain access to your system, you need to restart it into “Startup Repair” mode
  • To do this, you need to click onto “Start” > “Power” button (left “charms” menu) + hold SHIFT and press “Restart”
  • This will bring up the “Windows Recovery Environment” (blue screen) which will provide a number of options with the system
  • Click on “Troubleshoot” > “Advanced Options” > “Startup Repair”
  • This will perform the repair (will take some time) and then restart your system
  • If the problem persists, move onto step 2
  • If you cannot gain access to your system (IE the error appears after boot), you need to gain access to “Startup Repair” through the “forced boot” method
  • Unlike previous versions of Windows, W10 cannot just be rebooted into the “Recovery Environment” screen – it has to be triggered
  • The best way to do this is boot up your system 3 times (each time, it needs to fail)
  • On the fourth time, it should show the Recovery Environment (blue) screen
  • From the options that show, click on “Troubleshoot” > “Advanced Options” > “Startup Repair”
  • Let the process occur and then it should restart your system

2. Resolve BCD, SFC and DISM issues

If the above does not work (which won’t for 40% of cases), you’ll need to resolve the various issues with many of the core elements of the Windows system.

To do this, you need to gain access to CMD – which has to be done through the “Windows Recovery Environment” screen we should have seen in step 1…

  • If you have access to Windows, click onto “Start” > “Power” > hold “SHIFT” + click “Restart”
  • If you don’t have access to Windows (IE the error shows at boot), you’ll want to boot up 3 times – on the fourth, it should show the recovery environment screen
  • This will bring up the blue “Windows Recovery Environment” screen, from which you should click “Troubleshoot” > “Advanced Options” > “Command Prompt”
  • This will load up the black CMD window which most people should be familiar with

From here, you’ll then want to type the following commands:

  • “sfc /scannow” + press “Enter”
  • “DISM /Online /Cleanup-Image /RestoreHealth” + press “Enter”
  • “bootrec /rebuildbcd” + press “Enter”

After doing this, restart.

If the error was with the boot records of Windows, you should see it repaired.

3. Perform “Repair” Install

Now, Windows 10 doesn’t work in the same way as Windows 7/8.

Back the day, you used to be able to perform a “Repair Install” – which meant that if you had any issues with your system, you’d basically be able to keep all your files etc – whilst Windows would totally refresh itself.

This has been replaced in W10 with the “Reset Installation” feature.

Reset installations are difficult to access, but do provide you with the ability to “flush” out any of the bad updates from your system – which should solve the blue screen error you’re experiencing…

  • If you don’t have a valid Windows 10 installation medium (DVD or USB), you need to obtain one
  • To do this, browse to your favourite search engine and look for “Windows 10 Media Creation Tool”
  • Click on the Microsoft link and download the tool (it’s not very big)
  • After saving the tool to your system, open it
  • Select “Create installation media for another PC”
  • Choose the appropriate language and system architecture (make sure it’s exactly the same as the system you have installed)
  • Follow the steps to create the media (USB strongly recommended)
  • Restart your system and boot it from the USB
  • On the initial setup screen, enter your language and other preferences, then select Next
  • Select “Repair your Computer”
  • On the “Choose an Option” screen, select “Troubleshoot”
  • From the list that appears, click on “Reset This PC”
  • Resetting your system keeps your personal files but often removes applications and drivers you may have added to the system
  • Apart from the inconvenience of having to refresh these files, you should get the system working again with it

Obviously, this seems like a lot – whilst you would be able to get the installation running if you had access to the system itself, if you don’t – the above is the next best process.

At this point – if the error persists, it means that you have further issues which have to be resolved (which could also indicate hardware difficulties).

Whilst there are a number of ways to do this, the real underlying issue is that it’s likely you have some specific issue with your computer or setup. To this end, you’ll be better talking to someone with actual experience of your specific system, either from a direct hands-on approach, or through the Internet.

You should look for someone to help on one of the help communities (Microsoft Answers will be good for this), as well as any further issues with the likes of local repair guys. Obviously, a repair guy is likely going to incur cost.



Source by Richard Peck

Installing Linux – Linux Tips For New Users

About 4 years ago, I was fed up with Microsoft, and had known about Linux, heard that it wasn’t that easy install and use, but I figured I’d give it a go anyway. It’s not hard at all, that might have been 10 or 12 years ago. In any case, once I found Ubuntu, one of the most popular and easiest to use Distros (versions) I had found MY Linux. And it wasn’t hard to install or use. AND It’s even more easy to get going today then it was 4 years ago.

It’s easy enough to go to the Ubuntu website, and DL the latest copy in an ISO image format and burn that to disk. But you don’t feel geeky enough to burn your own ISO image? Or if you don’t have a wildly fast Internet connection. You can always go to shipit.ubuntu.com and request a CD. OR purchase a magazine at a Borders or other book store that has a rack of computer magazines, but usually you’ll find some Linux magazine that includes a CD that has a distribution on it. It may or may not be Ubuntu. If you’re not shy of getting into things there’s many other distributions to choose from. They’re referred to as Distros tho among the Linux Community. Don’t get hung up on this, there is plenty of time to find out what these things are, I want to keep this simple for the new person who would like to check things out. And for that reason, I will focus on Ubuntu, the most widely used and popular desktop Linux to date. Fedora, the free Version of Red Hat Linux comes in second.

If you go to DistroWatch.com you’ll see many Distros listed, and the most popular downloads, where you can also purchase a disk to be sent by mail, and most of all Reviews of different Distributions.

Wow! You’ve made it this far, but some things need to be explained, so you have some idea of what is what.

Now, you’ve got your Ubuntu disk in your hands? What’s cool is that it’s a “Live CD”. Meaning that you can reboot your computer off of the CD-ROM and it will start a Live Session of Linux on your machine, without changing a thing to your hard drive. You can also install it to a Thumb Drive and run it off of that too, that’s much faster than the CD Rom. You can run the standard Desktop version of Ubuntu with as little as 256k, but it’s geared more towards machines with 1 gig or more of RAM. IF your machine ran XP, or a newer version of Windows, Ubuntu will run just fine with those specs. There is also the slight chance that the hardware of your computer isn’t supported well by the Linux Kernel and those issues will take additional addressing. Ubuntu’s online community and their forums, are usually fairly good about giving one a hand at solving an issue.

OK, it’s time to re-boot, and let your computer boot off of the DVD/CD-ROM. You’ll see Linux loading up, and Viola! you’ve got it running on your computer off of the live CD.

You can click on the install icon on the desktop, and you’ll be taken through the process of installing it on your hard drive, a USB stick and boot off of that, or use the WUBI installer and run Linux inside of Windows, as a program. This is much slower as your computer has to run two Operating systems at the same time, via an emulator. I tried it, and it was just to sluggish for me. Running it off of the Live CD is OK, but you won’t be able to save any of your settings. So, I’d suggest installing it to a 5-10 gig hard drive partition. Or a USB stick. Included in the install process is Gparted, and open source disk partitioner, that works very well. So you don’t have to bother with trying to make room on your hard drive prior to booting up Ubuntu.

So in review, the best way to install Linux you need to:

  • Get a Live CD
  • Boot your Computer into Linux, and check it out, surf the web, etc..
  • Install Linux from the Live CD to Your Hard drive, USB Stick, or use WUBI.

Please take note, that the Ubuntu installer will make Ubuntu the default Operating system when you re-boot, you can easily change this from within Ubuntu, but I’d hate for you to be surprised, and not know how or where to get it to boot back into Window’s if that’s what you’d like to do.

Also. Don’t do this, if you’ve got sensitive data that you don’t want to lose. Always backup, and remember any time you’re changing around with your computer’s partitions, there could be an error and you can suffer data loss.



Source by Randy Noseworthy

HP Password Reset – I Forgot My HP Laptop Password

Can you help me with my HP password reset? I just forgot my HP laptop password! I usually heard such kinds of complaint forHP laptop password reset.

Solution 1: Login HP laptop from other accounts with administrator rights

If you know other accounts which have admin privilege, you can use them to login your PC and reset the lost passcode. Take HP Windows XP Laptop Recovery as an example:

A. Boot your PC from Safe Mode by pressing F8 when PC stars.

B. Login the accessible account with administrator privileges.

C. Start – Local Users and Groups – lusrmgr.msc in the Search box – ENTER.

D. Local Users and Groups – choose Users.

E. Right click the account needed to reset password, and then select Set Password.

F. Input and confirm the new passcode.

Solution 2: HP password bypass by Ophcrack

Ophcrack is an easy Windows password recovery tool available online. You just need visit its site to download an ISO image file online. With a CD, you burn the file into to it and insert the CD into your HP laptop’s drive. Restart the system; you can recover your code easily.

Solution 3: DIY a HP password reset disk

It is popular for PC users to DIY their own passcode reset disk. They often refer to tools for Windows password recovery. Let’s take one of the most common tools – Windows Password Recovery Basic as example. Just 3 steps:

Step A. Burn a.iso file into a blank CD/DVD or USB Flash Drive;

Step B. Boot the burned CD/DVD or USB Flash Drive from the PC lost password;

Step C. Reset a new HP password.

Solution 4: HP password recovery with passcode reset CD/DVD or USB

It is the last but not the least solution to recover HP Windows password. Create password reset disk for your PC once we set password for our PC. Take HP Windows 7 as example to finish the disk as followings:

A. Insert a USB Flash Drive or floppy into PC.

B. Open User Accounts: Start – Control Panel – User Accounts and Family Safety – User Accounts.

C. On the left pane, choose “Create a password reset disk”, and then “Forgotten Password Wizard” will come up.

D. Click “Next” and then follow the instructions to create a passcode reset disk to get rid of troubles resulted from Windows 7 forgot passcode.

Now, to unlock HP password will never disturb you. Keep the disk in a safe place. One day, if you locked out of PC by your forgotten passcode, you can use the disk to help you for many times.

E. On the password incorrect prompt interface, click OK and close the message box.

F. Click Reset Windows Password and then insert the passcode reset disk (or other removable media).

G. Follow the steps in the Password Reset Wizard to create a new password.

H. Log on with the new passcode.

Share these solutions, especially, the last one with your friends who use PC. For security, these tips on HP laptop password reset will help us with forgot HP laptop password.



Source by Cather Lily

Booting Your Arnova 10 G2 Into Recovery Mode

Are you an owner of an Arnova 10 G2? If so, then you know that these 10 inch tablets are perfect for surfing the web but, with their stock Android OS they don’t have too much more to offer. Thankfully, some very talented people found ways to root the 10 G2 allowing us to make administrative modifications or permitting the replacement of the stock Android operating system. There are even methods to installing Google Play, previously known as Google Market, and this alone has made the 10 G2 worth owning. Adding Google Play has leveled the practicality playing field for this device. Although, it can’t quite compete with quad-core power monster tablets with their high definition screens, it’s still a great tablet for $130, if you are willing to root it.

Rooting has become an almost effortless task for most devices with the advent of 1 click style rooting software. For the users out there that stumble upon this article and don’t know what “rooting an Android device” means; let me tell you. Rooting is a process that gives you, the user, administrative privileges on an Android operating system powered device. This allows you to circumvent restricted features, in the 10 G2’s case, removing bloat ware (unwanted applications that typically cannot be removed) or changing your ROM (a data file that is a version of the whole Android operating system.)

The Process

Here are the steps to gaining recovery mode access to your Arnova 10 G2:

  1. Plug the power cable and USB cable into your Arnova 10 G2. You should plug the other end of the USB cable into the computer and the power into the wall socket.
  2. Stick a paperclip into the reset slot and hold the reset button down.
  3. Push and hold the Volume + key. So now you are depressing the reset button and the Volume + button.
  4. Wait 15 seconds and release the reset button, but still hold the Volume + key.
  5. Give the device a few moments to cycle on. The screen will remain black. This black screen is the only visual proof that the Arnova is in recovery mode. You can release the Volume + button.

That’s it! You can now add your drivers and run your recovery software so that you can install a custom ROM or even the stock ROM which is located at Arnova’s support page.

There are lots of places to find information on the rest of the process. I implore you to search for different ROM’s and test them out. Some are great and some are even greater. Find what works for you and most of all, best of luck!



Source by TJ Moynihan

Creating a Win7RescuePE

This tutorial is a guide to create a Win7RescuePE, bootable as either a CD/DVD or as a UFD (USB Flash Drive). Win7RescuePE is a project that can be downloaded and run within the WinBuilder utility to create boot disks based on WinPE 3.0, while also providing a user-friendly Windows environment to work from.

Requirements:

Build source: Building a Win7RescuePE boot disk will require a Microsoft Windows7 DVD (32 bit only). 64 bit Windows7 DVDs are currently not supported.

You can use free available Windows7-RC1.

Installed Windows Advanced Installation Kit (Windows AIK).

Windows AIK is available from Microsoft for free, and can be downloaded, burned to a DVD, and then installed in Windows from the DVD. It is available for download when you type “WAIK” on Google.

Build environment: A Windows XP or later operating system (32 or 64 bit) is recommended.

Build utility: WinBuilder is the program that actually builds the boot disk. From within WinBuilder, Win7RescuePE itself can be downloaded. It is necessary that you use WinBuilder 077 RC 2 or above. The WinBuilder download page can be found by typing “WinBuilder” at Google as well.

Hard drive space: Approximately 2 GB of free space is required during the Win7RescuePE build process. Installing Windows AIK requires up to 1.5 GB of free space.

Memory (RAM): The target system requires a minimum of 256 MB, with 512 MB or more recommended.

As a further clarification, the Win7RescuePE boot disk can be built from a Windows 64 bit OS, but it cannot be built using a 64 bit Windows7 DVD as the source.

The remainder of this tutorial covers the steps required to create a bootable Win7RescuePE CD/DVD or UFD. The procedure was written while using WinBuilder 077 RC 2 and Win7RescuePE, and was tested on both Windows XP SP3 and Windows7-RC1 as the build environment.

Step 1: Download and install WinBuilder

Download WinBuilder from the link below. Version (077 RC 2 as of this writing) is recommended.

The WinBuilder download page will look similar to the the screenshot below:

The WinBuilder download will be in the form of a zip file containing one file (WinBuilder.exe). Extract this file to the folder where you want to run WinBuilder from. It is recommended that you create a new folder in the root of a drive, such as C:WinBuilder, D:WinBuilder, etc., and extract WinBuilder.exe there. It is also recommended that the path to the folder and folder name itself do NOT contain any spaces, as this can cause problems under some circumstances.

Step 2: Start WinBuilder and download Win7RescuePE

Start WinBuilder by executing WinBuilder.exe. If running from Windows Windows7, WinBuilder will need to be run as administrator by right clicking WinBuilder.exe and choosing Run As Administrator.

Since no projects yet exist in the WinBuilder folder, it should go immediately to the Download Center screen as shown below.

Since Win7RescuePE is a new project, you must add the download server to WinBuilder.

You can do that by selecting a available project, and then pressing the Add a new web server button. Name of new web server is: rescue.w07.net/Projects

See screenshot below.

Select updates.boot-land.net and rescue.w07.net/Projects in the bottom-right section. For the first try, it is recommended that you leave “Recommended” selected in the drop down list, and leave all other items as they are by default. Select the Download button to start downloading Win7RescuePE. The screenshot below shows the download in progress:

If you get one or more messages stating that a file cannot be found or downloaded, acknowledge the message and let the download complete with the missing file(s). Then select Download from the main WinBuilder screen, and choose Download again on the Download Center screen. Doing this should cause WinBuilder to download just the missing file(s) so that you now have a complete Win7RescuePE installation.

If you want to start the Win7RescuePE download over again from the beginning, close WinBuilder, delete everything in the WinBuilder folder except WinBuilder.exe, and then run WinBuilder again to start over.

When finished with the Win7RescuePE download, the main WinBuilder screen will look as shown below:

Step 3: Install Windows AIK

Windows AIK will be required to build the Win7RescuePE boot disk.

Windows AIK can be downloaded from the Microsoft web page.

The file downloaded from Microsoft will be an ISO file, approximately 1.3 GB in size. Once downloaded, burn the ISO file to a DVD with a utility such as BurnCDCC. This utility can be downloaded from Terabyte Unlimited.

To start the install, insert the DVD and wait for the Windows AIK welcome screen to appear. If the DVD doesn’t autorun when inserted, you can open the DVD drive in an Explorer window, and the double click startcd.exe. Be sure to note the installation requirements on the welcome screen, which specify which versions of Windows (and Service Pack levels) are supported by Windows AIK.

Select Windows AIK Setup from the welcome screen menu. After some initialization and the license agreement screen, the following dialog will come up:

The defaults shown above will work fine with Win7RescuePE. Be sure to check the required disk space before proceeding by using the Disk Cost button. Clicking Next will start the install. At completion, the following screen will appear:

Windows AIK requires both the.NET Framework and MSXML 6.0 to be installed. If they are not already installed on the system, Windows AIK Setup will detect this, and request that you install either/both of these items first. Both are available to install from the same DVD, and appear on the welcome screen menu as.NET Framework Setup and MSXML 6.0 Setup.

Step 4: Configure Win7RescuePE before building the boot disk

Start up WinBuilder to the initial screen, which should show the Win7RescuePE project available. Note again that if running from Windows Windows7, WinBuilder needs to be run as administrator by right clicking WinBuilder.exe and choosing Run As Administrator.

With the Win7RescuePE item highlighted in the left pane, click on the Source button at the top. The Paths configuration screen will now be visible as shown below:

The key item on this screen is the Source directory, which tells Win7RescuePE where to find the source for building the boot disk. The Target directory and ISO file items can be left as they are by default.

If using a Windows7 DVD as the source, insert the DVD in a drive, and use the browse button in the Source directory dialog to select the drive letter for the Vista DVD. In the screenshot above, the F: drive is the Windows7 DVD. For convenience and a somewhat faster build, you can also copy the contents of the Windows7 DVD to a drive/folder of your choice on the hard drive, and then specify that location in the Source directory dialog. For example, if you copy the contents of the DVD to the folder D:Windows7, then that location should be specified in the Source directory dialog.

Next, select the Script button at the top, and then select Configuration in the left pane. This brings up the Configuration screen for Win7RescuePE as shown below:

The settings shown above are recommended for the first build.

Next, expand the Build section in the left pane, and highlight the 0 – PreConfig item.

If you installed Windows AIK to a location other than the default of “C:Program FilesWindows AIK”, then use the browse button to select the folder where it is installed. The screenshot below reflects the default installation location.

Step 5: Build the Win7RescuePE boot disk (the ISO file)

This step will build the boot disk and create the Win7RescuePE ISO file, which will be created (by default) in the ISO folder under WinBuilder, and will be named Win7RescuePE.iso. Please note that creating Win7RescuePE on a USB flash drive will require some additional steps after this one. Those steps will be covered in Step 8 below.

Highlight the Win7RescuePE item at the top of the left pane, and select the Play button at the top-right of the screen to start the build. The Win7RescuePE main screen is shown below as a reference:

The screenshot below shows the build in progress:

When the build completes, a Build Successful message box will be shown:

Click OK to complete the build. If you are creating a UFD rather than a CD/DVD, you can move on to Step 8 at this point. Otherwise, continue below to create the CD/DVD.

The file Win7RescuePE.iso will be created in the ISO folder as shown below. The actual size of the file will depend on the configuration options chosen, as well as the source (Windows7 DVD).

The ISO file can be burned to CD/DVD by using a CD/DVD burner application capable of burning ISO files.

Step 6 (optional): Create the Win7RescuePE boot disk as a USB Flash Drive (UFD)

Once you have completed Steps 1 through 7 above, you are now ready to create a bootable UFD.

Expand the Finalize section in the left pane, and then highlight the Copy to USB-Device item. On the right, select the Script button, which will bring you to screen shown below:

Plug in the UFD (if not already plugged in) and determine its Windows drive letter. At the bottom of the screen above, use the browse button to select the root directory of the UFD (the example above has it set to G:).

To go ahead and create the UFD, select the “Make USB boot device” item. After a short time, you will be prompted to format the USB drive. Click OK to continue. The HP USB Storage Format Tool window will come up, as shown in the screenshot below.

In the Device field, carefully select the target UFD device from the drop down list. Double check that you select the correct device since all USB drives on the system will be listed.

In the File system field, select NTFS (recommended), and then select Quick Format under Format options.

Check the settings carefully (especially the Device), and then select Start to format the drive. Before the format actually starts, there will be a confirmation screen where you can cancel the format if necessary:

When the format completes, a summary screen will be displayed as shown below:

Click OK, and then Close the format dialog to continue. If you use Grub4Dos as bootmanger, a screens as shown below will be appear.

After selecting your UFDD, and pressing Install, the process of setting up the UFD to boot, and copying the required files to it will be continued.

During the file copy process, the screen below will be shown (shows file copying in progress):

At completion, there will be an All Done message as shown below:

Click OK to finish. The UFD device is now ready to boot. You will need to set the UFD as the boot device in order to boot from it. Typically this can be done by either by going into the BIOS setup and changing the boot order, or by selecting the UFD device from a menu of boot devices that can be brought up (on some systems) at boot time by pressing a hot key.

The Win7RescuePE Desktop:

Booting and initializing Win7RescuePE will typically take from 1 to a few minutes, depending on the system, how the boot disk was configured, and what type of device it is booting from. A UFD will boot faster than a CD/DVD on most systems.

The Win7RescuePE desktop will look similar to the screenshot below, depending on the options selected in the Win7RescuePE configuration. The PENetwork utility (shown on desktop below) can be used to configure the network and map network drives if needed.

Additional Information: Optimizing For Size

If you would like to reduce the size of the boot disk to achieve a faster boot time, as well as require less RAM, some/all of the following configuration items can be considered:

In the NET section, uncheck all items except PENetwork. If you do not require PENetwork (for mapping network shares), that can also be unchecked.

Uncheck the entire APP section.

Uncheck the entire Tweaks section.

Uncheck the entire Addons section.



Source by Nuno Brito

Turn a Physical Linux or Windows Machine Into A Virtual Machine for Free

We will be focusing on creating this masterpiece in the Windows environment, but don’t worry the same principles can be used in any operating system that can run Virtual Box.

List of Software and Hardware needed:

Software:

-Virtual Box and Extension Pack

-Windows 7 or higher PC or most any Linux Distro

-Redo Backup and Recovery ISO

-YUMI installer

Hardware:

-USB flash drive

-USB hard drive

The overall benefits of performing this procedure is three fold. One, cost savings on power, climate control and space required will be seen instantly. Two, manageability and scalability dramatically increases due to working with virtual disks and virtual networks that can scaled up or down with finer grained control. Three, redundancy and faster disaster recovery that is provided by cloud services. Especially when tied into your already existing network infrastructure for a seamless transition when disaster strikes.

While this process can be completed in numerous ways with different software, this is the way that I am familiar with and all the tools needed are free.

Sounds daunting? No sweat, but where do we start first?

Well, we need to get an image of the physical machine onto removable media (USB hard drive). I recommend a USB hard drive vs. just a USB flash drive due to the space the image will take up. We will also need a USB flash drive at least 2 GB in size to use as a bootable media for Redo Backup and Recovery.

Plug the USB hard drive into your USB port and open up the folder structure. Create a folder in a location that you can remember I.e D:”Your Computer’s Name”. This is the location where we will install the files from our initial physical image copy to. After this is complete, eject your USB hard drive by right clicking on the “Safely Remove Hardware” icon in your taskbar and click on Eject “whatever your USB hard drive is named”, unplug the USB HDD.

Next, we need to create a bootable USB to load Redo Backup and Recovery on. Download a small program called “YUMI”. YUMI will create a bootable USB flash drive for Redo Backup and Recovery on it. Also grab a copy of Redo Backup and Recovery, save both files to your desktop or location of choice.

Now, run YUMI and choose your USB flash drive from the list (Remember to choose your USB drive and not your USB HDD that should be unplugged anyway!). Choose “Redo Backup and Recovery” from the software list that you can create an installer for. Click the “Browse” button to look for the Redo Backup and Recovery.iso to include on the install. Finally click on “create” to start the bootable Redo Backup and Recovery bootable USB creation process. When this is done, YUMI will ask you if you want to add any more distros, just say “no”. Eject your USB out of the computer using the “Safely Remove Hardware” icon in your taskbar and click on Eject “whatever your USB flash drive is named” and unplug the USB flash drive. Please keep Redo Backup and Recovery.iso we will need it later.

Make sure that the physical computer that you would like to virtualize is in a powered down state, if not please power down the computer. Insert only the USB flash drive into the computer. Power up the computer and press the correct key to access to boot menu or make sure that the USB drive is set to boot before the computers internal hard drive. Choose the USB entry to boot from, YUMI should now load. Choose the entry for “Tools” then “Redo Backup and Recovery”. Press enter on the Redo menu to start the mini recovery O/S. When Redo Backup and Recovery is loaded, insert your USB HDD and give it about 20 seconds.

Open Redo Backup and Recovery Software:

1. Choose “Backup”

2. Choose your disk to backup (your physical computer’s disk)

3. Choose your partitions to backup (typically it would be all partitions and MBR)

4. On the “Destination Drive” screen choose “Connected directly to my computer” and click browse.

5. Locate the file folder we made earlier I.e D:”Your Computer’s Name” click OK.

6. Choose a name for the disk image. I will usually choose the date, click next. The backup process will take anywhere from 1 hr to 3 hrs depending on hard drive capacity and computer speed.

Congratulations, at this point you have made a full backup of your physical machine. Please click “Close” on the Redo and Recovery Backup program and choose the power button in the bottom right corner of your screen. Select “Shutdown” and let the computer shutdown. Remove both USB flash drive and USB HDD and boot up any computer that has Windows 7 or higher installed on it.

Now, lets turn that physical machine into a virtual machine!

Open up Virtual Box and choose “New”. Give your Virtual Machine a name and choose the type of virtual machine it will be as well as the version. Choose your memory size, I usually a lot 2 GB=2048 MB if I plan on running it on a machine that has 4 GB of ram physically installed. Create a new hard drive, choose VHD as the hard drive file type, click next. Choose “Dynamically allocated” for the storage, click next. Give your VHD hard drive a name, I will usually name it by whats running on it, hence name it what you named your computer. Make the VHD hard drive large enough to store your operating system, I will usually choose 200GB to be on the safe side. Again this depends on how big your physical machine’s data was. You are now returned to the Virtual Box Manager screen with your new VM present. Make sure your Virtual Box extension has been installed. Obtain the extension for your software version and install it like so:

In Virtual Box, click File–>Preferences–>Extensions–>Add Package–>Locate extension file and select it. It will be automatically installed.

Prepare the conversion! Use only Option A or Option B:

Option A: If you can get USB support working in Virtual Box:

Make sure that you have installed the extension pack and setup USB access properly, if you are having some troubles, refer to the Virtual Box document here:

https://www.virtualbox.org/manual/ch03.html#idp55342960

In Virtual Box, click on your VM name and choose “Settings” at the top, choose “Storage”. Click on the empty CD/DVD icon and then the CD/DVD icon on the right under “Attributes” and select your Redo Backup and Recovery ISO and click “OK”. At this point you have the Redo Backup and Recovery.iso at the ready and a blank VHD to install to. All you need to do now is insert your USB hard drive and skip over Option B because you do not need to perform it.

Option B: If you cannot get USB support to work in Virtual Box. No problem, its what happened to me so I found a way around it.

In Virtual Box, click on your VM name and choose “Settings” at the top, choose “Storage”, choose “Add hard disk” next to Controller:Sata or Controller:IDE whatever you have. Choose “Create new disk”, choose VHD and again make it 200GB Dynamically allocated and name it “Installer”. Underneath “Storage Tree” click on the empty CD/DVD icon and then the CD/DVD icon on the right under “Attributes” and select your Redo Backup and Recovery ISO and click “OK”. At this point you have the Redo Backup and Recovery.iso at the ready and a blank VHD which is named after your computer and another black VHD named Installer. Now close Virtual Box and right click on “Computer” and choose “Manage”. Left click on “Disk Management” then right click on “Disk Management” again and choose “Attach VHD”. Browse for the location of your Installer VHD that you created in Virtual Box, usually in the “My Documents” folder and click okay. Now you can copy the physical computer backup image that we took earlier from D:”Your Computer’s Name” to Installer VHD. After the contents have been copied, right click on computer management again and click on “Detach VHD”. Open up Virtual Box and proceed to the next step.

Lets Convert This Thing!

Once you have either USB support or the Installer VHD setup and the Redo Backup and Recovery ISO mounted. Press “Start” on your VM name in Virtual Box. You will be met the familiar Redo Backup and Recovery boot menu, press enter to proceed. Launch the Backup and Recovery program if it did not start automatically. Choose “Restore”. In a nutshell, you will choose where your Image backup is “The Source Drive” (your USB HDD or Installer VHD if applicable) and where to install the image (blank VHD named after your computer). After you have chosen to install into the blank VHD, confirm the prompt to overite any data and let the recovery process begin. After this is finished, click close and shutdown Backup and Recovery as you did before. The VM should stop running. Click on “Settings” from the Virtual Box Manager and unmount the Backup and Recovery ISO and the Installer VHD if applicable. Leave your VHD with the name of your computer or whatever you named it and click on “OK” to go back to the Virtual Box Manager. Click on “Start”, you should now be looking at a fully virtualized version of your physical computer!

Celebrate the many uses of this power little VHD!

You can transport this VHD and include it in any Virtual Box VM instance or even VMware if you are so inclined. You can run it on your local premises or deploy it in the cloud. A cloud instance of this VM would either require running Virtual Box on your cloud computing instance, or running it natively in your cloud computing space if the hosting provider supports it.

Common Gotchas and Troubleshooting:

Q: When trying to run my Linux based virtual machine, I get ” not syncing: VFS: Unable to mount root fs on unknown-block(0,0) “?

A: This is because in the backup and recovery process all the entries for hda##, hdb## and so forth have been converted to sda## extc. First, copy your precious VHD so you won’t lose your work if something goes wrong. Then all you will have to do is mount Backup and Recovery ISO, start your VM again and bring up a terminal session. Mount the Root partition and edit the entries in GRUB or Lilo to the proper boot device. For example: in GRUB, the entries are included in menu.Ist and fstab. In Lilo they are included in /etc/lilo.config and then /sbin/lilo -v to write the changes.

Q: When trying to run my Windows based virtual machine I get a boot error?

A: Obtain a copy or a Windows disc and mount it inside of Virtual Box making sure it is set to boot first. Choose the “Repair” option. Choose “Start Up Repair” and let it run. If this does not do the trick, go back into the “Repair” option and choose “Command Prompt”. Try these commands one at a time, shutting down and unmounting the Windows disc each time to check if the problem has been corrected:

bootrec.exe /FixMbr. Then restart to see if resolved. If no result, try:

bootrec.exe /FixBoot. Then restart to see if resolved. If no result, try:

bootrec.exe /RebuildBcd. Then restart to see if resolved. If no result, try:

You may have to remove your BCD folder by running these commands one line at a time without quotes:

“bcdedit /export C:BCD_Backup

c: <—- Only if your Windows installation is installed on C:

cd boot

attrib bcd -s -h -r

ren c:bootbcd bcd.old

bootrec /RebuildBcd”



Source by David T Goodwin

How To Quickly Make A Bootable USB Stick With FreeBSD

Install FreeBSD, or use an existing FreeBSD installation, and follow these steps:

1) First, you need to prepare and format your USB stick:

fdisk -BI /dev/da0
bsdlabel -B -w da0s1
newfs -U -O1 /dev/da0s1a
boot0cfg -v -B da0
(“-U -O1” [“O” like in Olympus, not zero] is for UFS1 which provides much faster copying than UFS2; if you decide for UFS2, type “-U -O2” – but expect that the copying will be slower)

2) Then mount it: mount /dev/da0s1a /usb
3) Copy all directories (FreeBSD) to the stick
4) After copying, modify the /usb/boot/loader.conf (explained below)
5) In the /boot directory on your USB stick you must have MFS (Memory File System – mfsroot.gz), which you will make (instructions are below)
6) Modify your /etc/fstab in MFS and put the following line (only) there:
/dev/md0 / ufs rw 0 0
7) After you boot your computer with the stick, you will be in the MFS environment from which you will mount your USB stick with mount_nullfs (described below)

Modification of /boot/loader.conf on your USB stick

You must have the following lines in your /boot/loader.conf (some lines are optional):

mfsroot_load=”YES”
mfsroot_type=”mfs_root”
mfsroot_name=”/boot/mfsroot”
nullfs_load=”YES”
splash_bmp_load=”YES”
vesa_load=”YES”
geom_uzip_load=”YES”
geom_label_load=”YES”
bitmap_load=”YES”
bitmap_name=”/boot/splash.bmp”
snd_driver_load=”YES”
kern.maxfiles=”25000″
kern.maxusers=”64″
vfs.root.mountfrom=”/dev/md0″

# Additional filesystem drivers

udf_load=”YES”
linux_load=”YES”
fuse_load=”YES”
ntfs_load=”YES”
ext2fs_load=”YES”
reiserfs_load=”YES”

Making your own MFS

FreeBSD, after the kernel boots, can use the root file system in memory (mfsroot_load=”YES” command in /boot/loader.conf will do the trick). To build such a memory file system, type the command:
dd if = /dev/zero of = mfsroot bs = 1024k count = 42

The mfsroot file of about 40 MB in size will be created. You need to format it, mount it and copy the most important files into it from your FreeBSD system (/bin, /sbin, /etc, /root….):

mdconfig -a -f mfsroot md0
newfs /dev/md0
mount /dev/md0 /mnt

Once copied, you must unmount it and gzip it: gzip mfsroot

Optionally, you can chroot it to see if everything works, then copy the mfsroot.gz to /usb/boot onto your USB flash drive (or disk). If you think it may be a problem to pick the most important files for your MFS (from your FreeBSD installation), search for mfsbsd in Google and either use its toolset or the MFS image alone (contained in the downloadable ISO of mfsbsd).

After booting from the USB stick (you will jump into MFS), you must mount the physical USB stick:

/sbin/mount -o ro /dev/da0s1a /usb
/sbin/mount_nullfs /usb/boot /boot
/sbin/mount_nullfs /usb/usr /usr

The above commands will help you use the big /usr directory on your USB stick instead of the /usr dir in MFS. mount_nullfs /usb/boot /boot is optional, as in your MFS/boot directory only the following files are needed for the little MFS to boot (/boot/kernel directory in MFS): geom_label.ko, geom_uzip.ko, zlib.ko a their debug symbols (zlib.ko.symbols, etc.). By mounting the /usb/boot dir via mount_nullfs into the /boot directory in your MFS you will be able to load kernel modules.



Source by Juraj Sipos