How To Install Windows Vista On Virtualbox

VirtualBox is a virtual auto for x86 architecture developed by Innotek and maintained by Oracle. In that location are two versions: the total VirtualBox package with a proprietary license and the VirtualBox Open Source Edition (GPL).

It'south easier to configure than QEMU and slightly slower than VMware.

ane Running the ReactOS Live CD
2 Installing the ReactOS Boot CD
- two.one Installing Guest Additions
- two.ii Setting up audio
- two.3 Known Issues
iii Getting debug output
- 3.1 Windows
  - 3.ane.1 Using VMwareGateway
- 3.2 Linux
  - 3.2.1 Using minicom
    - three.ii.1.1 Configuring the series port in minicom
    - iii.ii.1.two Redirect to file (Linux host)
  - 3.2.2 Using socat
    - 3.two.2.1 For viewing only
    - 3.ii.2.2 For an interactive window (eastward.1000. to get a backtrace)
- 3.three Serial port output using com0com
4 Born VirtualBox (low-level) debugger
- 4.1 Activating debugger
- iv.2 Using the debugger
5 Run across also

Notation: VirtualBox 5.2.44 version is highly and strongly recommended. VirtualBox 6.x co-operative is nonetheless very buggy and unstable, causes fake regressions to exist found in ReactOS.

Note: If you lot have any trouble 'capturing' your mouse/cursor within the Ros-VM-window with VirtualBox, start go to the "machine" tab and so select "Disable mouse integration", so click once more on the VM-session you're running to 'capture', and this time it should work.

Note: If you get the error Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT). when attempting to start a Virtual Auto ensure both Hyper-V and Windows Sandbox are unchecked in the "Plow Windows features on or off" department of the Add/Remove Programs control panel applet. (Chop-chop admission it by pressing Win+R and typing appwiz.cpl)

Running the ReactOS Live CD

Note: You tin can't install ReactOS from the Alive CD. You need to use the full installation prototype, which is called ReactOS BootCD.

The post-obit instructions volition guide you through the process of creating a ReactOS compatible virtual automobile in VirtualBox, and mounting the Live CD. The process is demonstrated using VirtualBox iv.2.14 r86644 on Windows 7 x64, but it should be similar on other operating systems, and versions.

Download the latest LiveCD release
Get-go VirtualBox.
Click the 'New' button.
Enter a proper name and set the type to Microsoft Windows. The version should be fix to Windows 2003 (32bit). Click next.
Choose the amount of RAM you wish to allocate to the Virtual Machine. At least 256 MB is recommended.
Add a Virtual Hard Bulldoze, even if you wish to run from CD. A difficult drive is required for booting the organisation. You tin either make a new one, or choose an existing one (if formatted it must exist FAT16/FAT32). Click Create to create your new VM.
Select your new VM and click Settings.
Make sure that you assigned merely 1 core of CPU to ReactOS VM
Go to 'Storage' and select the empty disk IDE controller.
Under Attributes, select your Alive CD image and tick the 'Live CD/DVD' checkbox.
Get to 'System', and make certain that 'Enable I/O APIC' is unchecked.
Become to 'Network', click avant-garde, change the adapter type to 'PCnet-FAST III'. Notation: This step should exist optional now, as Intel PRO/grand network card is supported out-of-the box since ReactOS 0.4.12.
Press OK. You are at present gear up to boot ReactOS.

If you lot are unable to choose the correct screen resolution in ReactOS, so refer to the instructions here. They explain the steps for Windows eight, only information technology should work for ReactOS likewise.

Installing the ReactOS Boot CD

Note: First of all, brand sure you have read Installing ReactOS article.

If you blazon "Reac" as your VM proper noun, VirtualBox will detect that yous are creating a ReactOS virtual machine and assign to information technology a Windows 2003 profile, which is near suitable. Brand sure you are using Virtualbox 5.2.18 version or newer to do good from this feature.

Y'all can customize the amount of RAM you wish to allocate to the Virtual Car. At least 64 MB are recommended.

Note: Intel PRO/chiliad network card is supported out-of-the box since ReactOS 0.four.12. For older ReactOS versions, always select 'PCnet-FAST III'.

After you are done with the installation of ReactOS itself you may want to take Guest Additions likewise.

Installing Guest Additions

Mount the CD-image with guest additions in the CD-Drive and open up the file VBoxWindowsAdditions.exe and follow the setup instructions.

To use the shared folders, follow the instructions on Using shared folders.

Attending: Y'all can simply install the VirtualBox guest additions if your virtual machine is configured with max. 32-64MB graphics retentiveness. Otherwise, an attempt to restart after installing the invitee additions will result in a BSOD on VBoxDisp.dll. You tin adjust the graphics retentiveness in the "Display" section of your VM when information technology is close downward.

Attention: If you desire to install and endeavor Vbox experimental 3d acceleration you should install Vbox additions merely in rubber mode (printing F8 key on boot). Vbox versions 4.Ten or five.X are recommended, because six.1.x has removed 3D dispatch back up for Windows OS'south earlier than Windows vii (ReactOS pretends to be XP or 2003).

Setting up audio

ReactOS has had limited support for sound since the 0.3.9 release, but information technology is recommended to test sound with a trunk build.

In VirtualBox Auto Settings, enable audio and set the following:

Host Audio Driver: Windows DirectSound
Audio Controller: ICH AC97

After installing ReactOS:

Download the Intel Ac 97 driver from ReactOS Application Manager
Extract the files to C:\ReactOS\
Restart the virtual car
Goto Device Director
If the Audio Device is not identified properly, observe the unknown Audio device
Right-Click and cull to Update the Device Commuter
Browse to the C:\ReactOS\inf folder every bit the install location
Update the Audio Device
Reboot ReactOS
Install and start your favorite audio playback or multimedia awarding (e.g. Winamp, VLC, MPlayer)
Open an sound file and play

Sometimes this method does not work. In case:

Download the Intel AC 97 commuter from ReactOS Awarding Director
Excerpt the files to C:\Downloads\
Copy the folders inf and system32 to C:\ReactOS\
Restart the virtual machine
If it worked, you will be able to hear startup sound (retrieve to plough up speakers).

Known Problems

The AC97 Driver just supports PCM Wave Audio in the range 8000-44.100Khz, 16Bit Samples and 2 Channels
Sample rate conversion is not yet supported
The driver has issues when changing the sample charge per unit of the audio stream

Getting debug output

Windows

Steps to be taken:

Fix a series port in VirtualBox.

There are other VM's possible, but they all work more or less the same, and they can all send a debug output to a COM port.

Download VirtualBox, if you oasis't done so yet.
Obviously, to debug/log ReactOS, you too need a ReactOS Debug build. ( You MUST use a Debug build. You will also need 7-Zip to go the ReactOS ISO out of the .7z file.
When the VirtualBox-window opens, click on the tab Settings. Click on Series Ports.

Choose Port Way: Host Pipage, tick the Create Pipe option, Port Path: \\.\piping\ros_pipe. (Y'all may see Connect to existing pipe/socket instead of Create Piping. In this instance, untick information technology.)

IMPORTANT: Don't change the "COM1" port that appears in the Dropdown listbox. Go along it as COM1.

Download and start PuTTY or your own favourite serial terminal (due east.one thousand. HyperTerminal,... )

This is the plan that creates the debug logs. PuTTY can listen to a COM port and write it to file. If you don't know what yous're looking for, get the

"For Windows on Intel x86" putty.exe file. It doesn't need to be installed; you just have to know where you downloaded it to. On Windows Vista and afterwards

information technology must be run as Admin, as anything that is to use named pipes.

Make sure Session is selected on the TreeView on the left. In the main office of the window, nether Connection Type, cull the radiobutton Serial. Nether Serial Line type \\.\piping\ros_pipe. Nether speed, type "115200". Depending on your wish how to log, 1 can go to the TreeView on the left and click on Logging under Session. Under Session Logging, cull All session output.

Log file proper noun indicates where the debug log will be and what it volition be called. Use the Browse button to change the location if y'all like, but brand sure you know where it's existence saved!

Go back to the TreeView on the left and click on Serial (nether Connexion). Set Flow Command to None. PuTTY is now configured. Note that on the main folio of PuTTY you lot tin Salvage/Load configurations which makes it even easier.

Thus, after you elect the series every bit connection type, gear up speed to 115200 baud and put the named pipage path every bit serial line (\\.\pipage\ros_pipe), you lot are fix to get. Of course, instead of ros_pipe, you can use whatsoever unique name, simply mind to follow the \\.\piping\[pipe_name] scheme.

Click on "Open" at the bottom of the PuTTY-window. This activates PuTTY'southward debug-log-creating abilities, which is a black window with a flashing green

cursor. If you tin can run into your PuTTY window in the background, you'll come across lots of text flying past equally PuTTY does its thing. When you've finished with

exploring ReactOS, you'll accept your debug log there. When you close down the virtual motorcar, PuTTY will change to inactive state and display mistake

message, but when you restart the virtual machine, you tin hands reconnect that session by pressing right mouse push button on window top bar and selecting

Restart session.

Offset start ReactOS in DEBUG Fashion in VirtualBox, then open up PuTTY and lookout the log.

Select Debug Manner
ReactOS running + PuTTY output

It has been suggested that in that location might be some slight data loss with pipes nether very heavy output. If one notices this equally being the case, and one intends to be a heavy tester/logger, there is still another way of getting a debug-log to piece of work:

Com0com : This is the VirtualBox/PuTTY bridge. It gives you the pick to have multiple COM port pairs, merely y'all really only need 1 COM port pair. (Virtual Port Pair 0, for instance). Download and install com0com virtual bear redirector. See the com0com tutorial for more info. At the setup window, you'll see the names of the virtual series ports (default: "CNCA0" and "CNCB0"). Be certain to check that the driver for com0com is installed correctly (with Device Manager, for instance). So get-go your VM. In VirtualBox, go to "Settings", "Serial Ports" and set "Port Mode" to "Host Device" in the drib-down box (NOT "Host pipe"). Then, set Port/File Path to "\\.\CNCA0". Next, start Putty; check "Serial" and at the Series line now type "CNCB0", and click on "open". As said earlier, a blackness box should appear, and when you lot run ReactOS in debug mode, the box will fill with text, aka, your log.

IMPORTANT: Make sure to utilise the digitally signed version of the com0com driver on 64-bit versions of Windows Vista and subsequently.

Using VMwareGateway

You need to download the VMwareGateway application. Kickoff it with /r selection to make it run equally a service (in Windows Vista y'all have to use an elevated CMD for this). Y'all can download a x86/x64 build here that does not require VirtualBox to run elevated on Vista/Win7. Side by side you need to beginning the service, using SC command:

sc start vmwaregateway

Sort out whatsoever firewall pop-up if applicative. Finally, utilize your favorite telnet customer to connect to localhost on port 567.

To configure your virtual machine, set it to Host Pipe with the following piping address:

\\.\pipe\vmwaredebug

Make sure you do not mark the Create Pipe box. VMwareGateway has already created it. Debug output should appear in your telnet customer PuttyTel.

Linux

Install VirtualBox package, how to do so will depends on your distribution

On Debian or Ubuntu: sudo apt-get install virtualbox

Patently, to debug/log ReactOS, you also need a ReactOS Debug build. ( You MUST use a Debug build. You will also need 7-Zip to get the ReactOS ISO out of the .7z file.

Set up a serial port in VirtualBox.

Setup a serial port in VirtualBox as shown in the motion picture to the right and below.

When the VirtualBox-window opens, click on the tab Settings. Click on Serial Ports.

Choose Port Mode: Host Pipe, tick the Create Pipage option, Port Path: /tmp/ReactOS-Debug.pipage. (You may see Connect to existing pipe/socket instead of Create Pipage. In this example, untick information technology.)

Of import: Don't change the "COM1" port that appears in the Dropdown listbox. Go on it every bit COM1.

Using minicom

This guide is based on the terminal application minicom. Start install it by typing:

sudo apt-get install minicom

Configuring the serial port in minicom

"sudo minicom -s" volition allow you lot to set your port and save the configuration file (dfl = default)

Choose "Configure serial ports". Name the device unix#pipe_path where "pipe_path" is a file like /tmp/ReactOS-Debug.piping which will be used as pipe betwixt the virtual auto and minicom.

Make sure that pipe_path is exactly the same on both minicom and VirtualBox.

Salve config (dfl) will salve your configure

Exit

now later starting the VM, execute "minicom" without sudo, to run information technology as a normal user

Redirect to file (Linux host)

When running minicom, type Ctrl-A and so L. Type the name of the capture file.

Using socat

For viewing only

socat unix-client:pipe_path stdout

You could too practise this:

socat unix-client:pipe_path stdio

Substitute "pipe_path" with the path of the pipe you lot created using VirtualBox (e.g. "/tmp/ReactOS-Debug.pipage").

In example you want to redirect the socat output to a file y'all tin can employ the post-obit command:

socat -u unix-client:pipe_path stdio Open up:log_file_name,creat,trunc

Where log_file_name is the file you desire to send VirtualBox serial output to.

If ReactOS crashes, y'all should still be able to blazon in the VirtualBox window – east.g. within a debug session. You'll see the input and output on the panel window which socat is running in.

For an interactive window (eastward.chiliad. to become a backtrace)

In ane terminal tab/window do: $socat UNIX-CONNECT:/tmp/ReactOS-Debug.piping PTY,link=/tmp/vbox_term

In an other concluding tab/window exercise: $screen /tmp/vbox_term

Serial port output using com0com

Install and configure com0com according to the com0com guide.

Enable the first serial port for your ReactOS machine. Use port number "COM1", fashion "host device" and port path "COM4" or whatever virtual port y'all created get-go with com0com.

Connect your last application to your second virtual port and start upwardly VirtualBox.

Built-in VirtualBox (low-level) debugger

VirtualBox has a congenital-in debugger. For a detailed clarification, see in the affiliate "12.1.3. The built-in VM debugger" of VirtualBox User Manual help file.

Activating debugger

The VM debugger is available in all regular production versions of VirtualBox, simply it is disabled past default because the average user will have lilliputian use for information technology. At that place are 2 ways to access the debugger:

A debugger console window displayed alongside the VM
Via the telnet protocol at port 5000

The debugger can exist enabled in three ways:

Kickoff the VM straight using VirtualBox --startvm, with an boosted --dbg,--debug, or --debug-command-line statement. Run across the VirtualBox usage assistance for details.

Set up the VBOX_GUI_DBG_ENABLED or VBOX_GUI_DBG_AUTO_SHOW environs variable to true earlier launching the VirtualBox process. Setting these variables (simply their presence is checked) is constructive even when the first VirtualBox procedure is the VM selector window. VMs subsequently launched from the selector will have the debugger enabled.

Fix the GUI/Dbg/Enabled extra data item in config file to truthful earlier launching the VM. This tin can be set globally or on a per VM basis. Per VM basis – change corresponding .vbox file, is an XML-formatted settings of virtual machine.

The paths are:

X:\Users\%username%\.VirtualBox\VirtualBox.xml – for global

XML-node: VirtualBox/Global/ExtraData

...\%VM_NAME%.vbox – for local

XML-node: VirtualBox/Machine/ExtraData

And under the mentioned XML-node add together the next chemical element: <ExtraDataItem name="GUI/Dbg/Enabled" value="truthful"/>

As consequence, a new 'Debug' menu entry will be added to the VirtualBox awarding. This carte du jour allows the user to open the debugger console.

NB.: sometimes this debugger activation requires Windows restart.

Using the debugger

The VM debugger command syntax is loosely modeled on Microsoft and IBM debuggers used on DOS, Bone/2 and Windows. Users familiar with symdeb, CodeView, or the Bone/2 kernel debugger will notice the VirtualBox VM debugger familiar. The near important command is 'help'.

See more at: VirtualBox debugger transmission

See besides

Transfer files from the host Os to the virtual bulldoze

Virtualization software‎ to run ReactOS on
Windows	Bochs \| Hyper-5 \| PCem \| QEMU \| Virtual PC \| VirtualBox \| VMware
ReactOS	Bochs \| PCem \| QEMU \| Virtual PC
Linux	Bochs \| Libvirt \| PCem \| QEMU \| VirtualBox

Source: https://reactos.org/wiki/VirtualBox

Posted by: browningthoureprot.blogspot.com