![]() ![]() ![]() Only downside is that the 32 bit memory model will limit what data sets can be analysed, but with a single CPU doing the number crunching you probably want to stay away from multi-gigabyte data sets anyway. I had to use the compatibility mode in Win8.1 to install QV, but that's fine.Īll in all, QV Desktop 11.20 SR5 is now running fine in VirtualBox. The hardware dependent portion of the Windows kernel is dubbed 'Hardware. It is also assumed that a suitable virtual disk image (either VDI or VMDK for VirtualBox > 1.4) is already present. Then upgraded to Win8.1.īUT looking closer it turns out that the Win8.1 client running in VirtualBox is indeed a 32 bit one, even though the virtual machine itself is configured as a 64 bit VM.Īfter changing the VM client type to Win8.1 (rather than Win8.1 64 bit) and enabling PAE in the VM, I could actually install the 32 bit version of QlikView. We assume that either a physical Windows installation or a VMware image is the source of migration. I was under the impression that I moved to a 64 bit Win8 installation (as I chose not to keep any data or config from the WinXP setup). ![]() Step 4: Select the amount of memory that you want to allocate to VM. Select the Operating System Windows and Version Windows 8, click Next. Step 3: Type the Name for the Virtual Machine. Step 2: Click Next on the New Virtual Machine Wizard. The VirtualBox image started off as a WinXP image (32 bit), which was upgraded to Win 8. Step 1: Open Oracle Virtual VirtualBox, Click on New from the main window. It turned out to be a mix of different things causing this: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |