Difference between revisions of "LiveUSB"

From ReactOS Wiki
Jump to: navigation, search
m
m (Use the Jira template)
Line 1: Line 1:
{{Warning|With current versions of ReactOS, USB support is '''NOT''' advanced enough to successfully boot and ReactOS will crash when it begins loading system USB drivers. See e.g. [https://jira.reactos.org/browse/CORE-7826 CORE-7826]. The following details for older versions are left here for historical reference and for use in the future when this feature becomes supported again.}}
+
{{Warning|With current versions of ReactOS, USB support is '''NOT''' advanced enough to successfully boot, and ReactOS will crash when it begins loading system USB drivers. See e.g. {{JIRA|7826}}. The following details for older versions are left here for historical reference and for use in the future when this feature becomes supported again.}}
  
 
== Preamble ==
 
== Preamble ==

Revision as of 04:44, 26 October 2016

Icon speedy deletion.png Warning: With current versions of ReactOS, USB support is NOT advanced enough to successfully boot, and ReactOS will crash when it begins loading system USB drivers. See e.g. CORE-7826. The following details for older versions are left here for historical reference and for use in the future when this feature becomes supported again.


Preamble

Revision r55555 of ReactOS introduced support for USB devices, and after some time it became possible to run the OS from a USB drive. In revision 55714 ReactOS was successfully installed and running from Patriot Xporter XT 8Gb USB stick. LiveCD revision 55995 has also been successfully executed from the same device using USB 1.1 OHCI.

Note: To install on a USB-HDD, it is preferable to use Bootcd; and for a USB flash drive, it is preferable to use LiveCD. Differences between installing on USB-HDD or USB flash drive are minor, but keep in mind that the resources (speed and storage space) of a USB flash drive can be much more limited than those of a hard drive. Flash drives also often have a limited lifetime of read and writes before they become damaged or unusable.

For more convenient use or testing of LiveUSB mode, you need to know the following things:

  • If you install bootcd, the first phase of installation to a virtual HDD in a virtual machine is much faster than directly to the USB-stick. Therefore later in this article we will consider how to transfer files needed to start the second phase of the installation from a virtual machine to a flash drive/USB-HDD.
  • If you install ReactOS to a USB-drive and install the MBR/VBR using the installer (without formatting the disk), then it is likely that the system will be unable to boot. If you wish to boot more than just ReactOS from a USB drive, please refer to the second paragraph of this article.
  • You also need a motherboard capable of booting a USB drive. This guide assumes you have one and that it is already configured.

Installing the system to a USB-drive

This process is now extremely simple thanks to Rufus! Rufus is a Windows/ReactOS application. If you use a different system, you'll need to seek an alternate method (like GRUB for Linux and BSD users, or diskutil for Mac users).

  1. Get the latest version of Rufus from http://rufus.akeo.ie/
  2. Download a current livecd or bootcd image of ReactOS
  3. Run Rufus (give admin rights if asked), and setup like this:
    1. Select your USB drive from the Device drop-down menu
    2. Select "Create a bootable startup disk using"
    3. Choose "ISO Image" from that drop down menu
    4. Click the disk icon next to that drop down menu, and select the .ISO file
    5. (Optional) tweak the other Rufus settings – ONLY if you know what you're doing
  4. Click "Start" in Rufus. Acknowledge that this operating will erase everything currently on your USB drive. Wait a few moments while Rufus does its magic.
  5. Try to boot. (Please do not use a computer where you store important data in order to avoid data loss!)

If it works (hooray!) do NOT let ReactOS change the filesystem or the boot record. Doing so will render ReactOS unbootable until you repeat the above process.

If it doesn't work (damn) it could be either due to a bug in the USB driver or because of a system regression (or regression of driver). Try to use a working revision (check the beginning of the article). If they work then you're dealing with a regression. Please report about it to the developers. If they also do not work then your USB controller or USB drive is not yet supported. Please report this too as a new bug.

References