![]() It is like permanently alpha software, which means things can break and then get fixed again and depending on which minor number release you install, and whether the defaults in VirtualBox have changed since _that_ was last updated, you might get something that works or not. I’ve found installing ReactOS a bit of a raffle too. “The ReactOS team currently targets Windows 2003 Server as the official compatibility target.” I believe the ReactOS target is like Win 2003 Server or thereabouts, 32 bit, same age as xp. However, if you really want to roll your sleeves up, you can have extra control using the VBoxManage command ilne see: If you look for VirtualBox at you’ll see Looks to me like you should have the VESA modes - these do top out at 1280×1024. Of course, your guest cannot give you higher resolution or screen size than your host and hardware can handle! I don’t know your circumstances, and I’m not really an expert, but I would say that if you have enough video resources and you have guest additions installed, then you probably need to configure your guest system, much as you would if running on bare metal. I use VMs almost solely for documents, so I never need high-end performance, eg games or video rendering and editing.īecause VB does not emulate any specific video card, you may find that to get the modes you need you’ll have to install the guest addtions. So you can increase video RAM and enable acceleration if you want. If you open the VirtualBox GUI manager, you can click on Display (‘Screen’ on some versions) and have a look at the graphics system of your VM. There are 2 sides to it - the emulated hardware, and the drivers in your guest system. But I was running it on a machine with a small screen so I could not ask for much! Umm… I’ve never had problems with screen resolution. Having said that, all the applications I wanted to be able to run can run on wine. ![]() (l) I’m not going to bother automating it, I’ll just put a readme on the ReactoS desktop. ![]() (g) Typed x: to move to X:, the shared folder. (f) Opened command prompt on guest and typed C:\> net use x: \\VBOXSVR\vbshare (e) In a terminal, needed to assign the folder a drive letter. (d) Double-clicked ‘My network places’ on the ReactOS desktop and there it was, called \\VBOXSVR\vbshare. (b) In VB manager, added that folder in Share Folders menu. Made sure users had read/write permissions. (a) Opened explorer in guest and double clicked on additions x86 exe file in the cdrom directory. (12) Devices menu of VB - inserted guest addtions. (11) It wanted to install a driver but could not. (a) Watched as it interrogated the hardware and installed some devices. (8) Removed cd rom image from virtual drive. (e) Chose default bootloader installation. (d) Chose default to put OS in C:\ReactOS I chose to do a full format not a ‘quick’ one. ![]() (5) Storage - put the Reactos ISO in the virtual drive. Select SoundBlaster 16 under Audio and PCnet-Fast III on NAT under Network. Apparently should be able to use guest additions from Win 32 bit, 2003-era. (2) and downloaded both disk images starting with iso rather than LiveCD. Host is 32 bit Debian 8.4 Netbook with 1 GB RAM and 250 GB HD. (1) Installed VirtualBox $ apt-get install virtualbox dkms Not on VB5.1 because the older versions are what the Debian repo provides. ReactOS 4.5 on VirtualBox 4.3.x on Debian 8.x. This is so simple there’s no need for step-by-step instructions, but I kept notes so I might as well post them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |