ReactOS installation experience (real machine and VMware)

Here you can discuss ReactOS related topics.

Moderator: Moderator Team

Bblaauw
Posts: 149
Joined: Mon Aug 03, 2009 12:59 am

Re: ReactOS installation experience (real machine and VMware)

Post by Bblaauw » Wed Aug 12, 2009 11:05 am

Any suggestion to how to hardcode values for paging file in that InitP.c file? I've looked at it, but it's over my head. 100MB max size sounds fine to me, ReactOS shouldnt use paging file much at all on a (virtual?) machine with memory size between 100MB and 4GB or 6GB (if it does then memory manager has issues..).

1 test would be to create a VM with 4GB memory on it, so Windows XP also creates a swapfile of around that size. Next thing, lower VM assigned amount of memory to 128MB or so and install ReactOS and since it refers to the same pagefile.sys as Windows, it should be able to use it without any issues at all.

It would help a lot of ReactOS reported:
* if it's using an already existing pagefile without size modification, or
* if it's modifying an already existing pagefile, or
* if it's creating a brand new pagefile (and hopefully not throwing an old one away first..)

hto
Developer
Posts: 2193
Joined: Sun Oct 01, 2006 3:43 pm

Post by hto » Wed Aug 12, 2009 9:20 pm

Bblaauw wrote: Any suggestion to how to hardcode values for paging file […]
Try to insert

Code: Select all

MaximumSize.QuadPart = InitialSize.QuadPart = 100 * 1048576;
before a call to NtCreatePagingFile().

P.S.: Have you forgot about that FreeLDR Breakpoint crash?

Bblaauw
Posts: 149
Joined: Mon Aug 03, 2009 12:59 am

Re: ReactOS installation experience (real machine and VMware)

Post by Bblaauw » Fri Aug 14, 2009 4:49 pm

Not forgotten it, just not got a decent way to get files into ReactOS on real machine. Only way would be through a FreeDOS diskette or a bootable CD, don't like either solution. USB bootable flashdrives I don't got experience with.
Also doubting if I can reproduce the same error again.

Bblaauw
Posts: 149
Joined: Mon Aug 03, 2009 12:59 am

Re: ReactOS installation experience (real machine and VMware)

Post by Bblaauw » Tue Aug 18, 2009 10:54 am

Closed the issue. Also, your pagefile limiting instruction works just fine. Provided it's a maximum filesize setting, I'd likely have to change it to slightly below 2GB, then provide it as patch.

Bblaauw
Posts: 149
Joined: Mon Aug 03, 2009 12:59 am

Re: ReactOS installation experience (real machine and VMware)

Post by Bblaauw » Wed Sep 23, 2009 8:27 pm

dumping a textfile here so hopefully someone might consider it to be of any use to a wiki page detailling ReactOS in combination with VMware. Most noticeable are the VMware video drivers..even with the installer fixed now in phase 2 setup, I'm not sure the VMWINST program can extract drivers from very latest VMware Workstation tools (requires extracting .cab file from a .msi file, requires expanding the .cab file, extracting its contents, then renaming, and finally installing)

Guess I'll write a followup installation experience once ReactOS 0.3.11 will have been released, be it with fully working FireFox/ Openoffice or not (as were original release design goals).


VMware:

VMware is a company specisialised in paravirtualisation.
For desktop users they have released the following products,
which enable you to run guest operating systems under your
main operating system:
* VMware Player
* VMware GSX Server (free use nowadays)
* VMware Workstation (commercial desktop solution with advanced abilities)

For a guest VM in the Workstation software, the following is true:
(based on latest released product and potential unreleased products)
* processor isn't emulated, but virtualised, so showing intel/amd/via etc
* chipset is an intel 440BX (Pentium2 era)
* graphics card is a custom implementation, with various abilities:
- VGA (textmodes? graphics resolutions?)
- VESA (1.x? 2.x? 3.x?)
- framebuffer
- SVGA
- Direct3d (DirectX 1-11?, might depend on future product released)
- OpenGL (1.x, 2.x, possibly, might depend on future product releases)
* working memory can vary between 4MB and 32GB, incremented in 4MB amounts,
but always at least slightly below system's physical memory.
* Supported mass storage controllers are:
- Intel 440bx IDE controller (x2)
- LSI Logic 53C1010 SCSI controller
- LSI Logic SAS SCSI controller, unknown chip
- Buslogic 895C SCSI controller
* Disks:
- floppy : capacities between 1.44MB and 2.88MB, no custom sizes
- harddisk : capacities between 1GB and 2048GB
- optical drive: capacities between 100KB and 50GB.
writable also if physical disks, no growing ISO writer.
* Audio
- Soundblaster 16 (PCI?)
- ESS1371, PCI
* Supported network controller is a PCI AMD PCnet, including PXE-booting
* USB : various speeds and devices supported, no Isochronous (webcams etc)
technologies: OHCI/EHCI/UHCI/XHCI
- 1.0 1Mbit/s (low speed) : supported
- 1.0 12Mbit/s (high speed) : supported
- 1.1 1Mbit/s (low speed) : supported
- 1.1 12Mbit/s (high speed) : supported
- 2.0 12Mbit/s (high speed) : supported
- 2.0 480Mbit/s (full speed) : supported
- 3.0 5000Mbit/s (extended speed) : -
* Keyboard : PS/2 mode emulated, 83-105keys, Win-key supported, ASCII codes
* Mouse : PS/2 mode emulated, 2-button only
* Serial : Various settings supported, including debug port
* Parallel : Various settings supported, not mapped to USB printer or anything
* System : ACPI etc?


Guest VM drivers provided by VMware:

Most important driver provided by VMware Workstation for your virtual
machine is the SVGA driver, located on a virtual CD-ROM named
"VMware Tools" (on host, C:\PROGRAM FILES (X86)\VMWARE\WINDOWS.ISO).
To get these drivers without running the not always working installer
is tricky:
* VMware Tools (WINDOWS.ISO on host / D: on guest )
-----> VMware Tools.MSI (how to unpack this?)
-----------> SVGA.CAB (how to unpack this?)
------------> _VMX_SVGA.INF
-----------> VMX_SVGA.INF
------------> _VMX_SVGA.SYS.* (expanded? compressed?)
-----------> VMX_SVGA.SYS
------------> _VMX_FB.DLL.*
-----------> VMX_FB.DLL
------------> _VMWOGL32.DLL
-----------> VMWOGL32.DLL
------------> _VMX_MODE.DLL
-----------> VMXMODE.DLL
------------> _VMXOGL64.DLL
-----------> VMXOGL64.DLL

Under Microsoft Windows XP, 32bit, this driver, among others provided by
VMware, should normally install just fine if using the installation setup
located on the CD (D:\setup.exe or D:\vmware tools.msi).


ReactOS:

ReactOS is an opensource operating system which aims to implement the
Win32 API and ABI, thus enabling you to run your Windows applications
on this software. So far it seems to work reasonably inside of emulators
and (para)virtualisation programs, yet real hardware support is very limited.


* processor isn't emulated, but virtualised, so showing intel/amd/via etc
* chipset is an intel 440BX (Pentium2 era), drivers built-in for everything.
* graphics card is a custom implementation, with various abilities:
- VGA driver : 4color 640x480 up to 4color
- SVGA driver : 8color 640x480 up to 32bit color 1920x1200
- VMware driver : 4color 640x480 up to 32bit color 1920x1200,
hardware accelerated, DirectX/ReactX/OpenGL possibly
supported.
Note: ReactOS has special installer for finding,
extracting and installing this driver, but it's outdated,
incorrect, system-crashing and non-functioning,
likely due to incorrect programming and/or changed file
layout of the VMware Tools ISO file.
* Supported memory amounts:
- Maximum recognised memory for ReactOS is theoretically 4GB due to 32bit
- Maximum recognised memory for ReactOS is actually 3100MB due to PCI maps
- Maximum error-free memory for ReactOS is 2GB, due to paging file
being created with same size as system memory. Somehow bootup process is
unable to create 2GB+ files. Maybe ROS is unable to handle 2-4GB files
at all?
- Minimum error-free memory for ReactOS is 20MB-72MB
- Minimum error-free memory for ReactOS bootloader FreeLoader is 8MB
* Supported mass storage controllers are:
- Intel 440bx IDE controller (x2) - UNIATA driver supports this
- LSI Logic 53C1010 SCSI controller - 3rd party driver only, internet
- Buslogic 895C SCSI controller - BUSLOGIC driver supports this
* Disks:
- floppy : capacities between 1.44MB and 2.88MB, no custom sizes.
drive A: not shown in ReactOS (yet setup can create bootfloppy)
- harddisk : capacities between 1GB and 2048GB, FAT12/16/32 only
- optical drive: capacities between 100KB and 50GB
* Audio
- Soundblaster 16 (PCI?) - separate driver required, and working audio stack
- ESS1371, PCI - separate driver required, and working audio stack
* Supported network controller is a PCI AMD PCnet, including PXE-booting
* USB
- 1.0 1Mbit/s (low speed) : supported, NT4-mode keyboard/mouse
- 1.0 12Mbit/s (high speed) : supported, NT4-mode keyboard/mouse
* Keyboard : PS/2 mode emulated, 83-105keys, Win-key supported, ASCII codes
* Mouse : PS/2 mode emulated, 2-button only
* Serial : Various settings supported, including debug port
* Parallel : Various settings supported, not mapped to USB printer or anything
* System : no drivers for system devices, whatever they may be,
and whichever PCI adresses
* Shutdown : non-ATX/APM/ACPI mode only for VMware
(shut down OS, press power button)
* Reboot : works, cleanly shuts down system first
* Logoff : not implemented in any workable way
* Standby : not implemented in any workable way


List of devices for Windows XP (thus also ReactOS to recognize):
------------------------------------------------------------------

hardware ID (xxxx:yyyy) ; name ; description


------------------------------------------------------------------

ReactOS Vmware SVGA installer registry file:



Reactos VMware SVGA driver file locations:
(bonus question: does floppydrive work during phase 2 setup?)









@echo off
if not exist c:\download\nul md c:\download
cdd c:\download

:copyISO
echo Copying VMware Tools for Windows XP
if exist *.iso goto getMSI
copy "c:\program files (x86)\VMware\VMware Workstation\windows.iso" c:\download\windows.iso
goto getMSI

:getMSI
echo Unpacking ISO file to obtain MSI cabinet file
if exist *.msi goto getSVGA
"c:\program files\7-zip\7z" e windows.iso
goto getSVGA

:getSVGA
echo Unpacking MSI file to obtain SVGA cabinet file
if exist SVGA.cab goto getvideo
"c:\program files\7-zip\7z" e "VMware tools.msi"
goto getvideo

:getvideo
echo Extracting files from SVGA cabinet file
echo FIXME: some kind of extract command should go here
goto rename

:rename
for %%x in ( vmwogl32.dll vmx_fd.dll vmx_mode.dll ) do ren _%%x.* %%x
for %%x in ( vmx_svga.cat vmx_svga.inf vmx_svga.sys ) do ren _%%x.* %%x
echo Files unpacked, goodluck installing, whichever way it's done in ROS..
rem Regedit /some_command MyVMsvga.inf

Bblaauw
Posts: 149
Joined: Mon Aug 03, 2009 12:59 am

Re: ReactOS installation experience (real machine and VMware

Post by Bblaauw » Tue May 04, 2010 11:01 pm

Kicking an old topic of myself as it's the same issue.

With the recent improvements in UNIATA stability I'm gonna try installing ReactOS on real hardware rather than in VMWARE, as VMWARE is a mess anyway.

Could someone tell me what the typical installation methodology for Windows and ReactOS is to get a basic working system?
So far I can imagine:
1) install operating system, provide driver for mass storage controller if necessary. Hello floppydrive.
2) install network driver to gain network/internet access. Again that floppydrive that nobody has anymore
3) install drivers and programs from internet, preferably starting with graphics drivers if they can't be provided locally.

VMWARE:
1) Works fine for ReactOS in VMware Workstation 7.1, the only installation method is booting from CD though. I don't know if WinVBlock (Win32 driver for SYSLINUX's MEMDISK ramdisk) might work so you can boot the ReactOS installation ISO without needing physical CD. No floppydrive support in ReactOS since 0.2.5 or so I think? However ReactOS supports the Buslogic driver out of the box.
2) Might be done automatically in VMware, not sure. However, ReactOS supports the used network card out of the box (AMD PCNET?)
3) This is where things get messy. ReactOS has no browser by default, the 'programs downloader' program is listed only in Start Menu, not as a desktop shortcut (like CMD is).
VMware's "tools installation ISO and setup program" doesn't work/run (hanging on missing MSVCRT80 or so), neither is your VMWINST.EXE tool as it doesn't indicate what it expects
(something along the line of "a CD with a directory VMVIDEO at root level, with inside of it, some VMSVGA.SYS", just making this up. Workstation 7 has MSI/EXE file, with inside of it, a CAB file with video drivers)

Real hardware:
1) To be announced: expecting no big trouble
2) To be announced: gonna be a mess, need to find drivers and save them on ROS's FAT32 partition by default I guess. Windows XP-drivers? No public announcement of which operating system drivers ReactOS actually accepts (Win9X? no way. NT4? no way. 2K? maybe. XP? most likely. Vista/7? unlikely). Can't provide drivers on diskette or USB flash drive unfortunately due to lack of support for those, in ReactOS (currently)
3) To be announced: gonna be a mess, if mouse and screen work properly on my Nvidia card, and the driver wants to install at all then. Might require to download Nvidia graphics drivers (200MB installer, no idea how to extract actual drivers) to FAT32 partition in advance. Same reason as [2]

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 7 guests