I’ve just gotten my system (Ubuntu-Mate 16.04) reinstalled on a msdos partition in Legacy Mode, and I seem to be faced with two, irreconcilable conflicts:
I have a Windows program that will not run under wine (including winetricks, PlayOnLinux or CrossOver) so my only option seems to be virtualbox. I’ve installed virtualbox 5.1.14. When trying to install Windows XP in a virtual machine, the installation crashes along with ubuntu (all desktop icons turn white). I’m able to close all windows and reboot. I go back to virtualbox. Delete the Windows XP virtual machine and start over. Same thing. The install program crashes. From my google search it seems that there is (or have been) some issues with virtualbox on a Linux machine in Legacy mode. I don’t know if these have been resolved, but would appreciate any insights here.
The easy solution might appear to be to install Mate in UEFI mode on a GPT partition, but this leads to the second part of my dilemma - I have an Nvidia graphics card. Installing Mate in UEFI results in poor graphics resolution with the nouveau driver and installing the Nvidia drivers crashes the system.
Surely there must be some way to get this to all work together short of installing a new graphics card. Any suggestions?
My understanding of this is as follows: when I install ubuntu, because I have an nvidia card, I have to use nomodeset at grub. Once ubuntu is installed, nomodeset is no longer required if I'm using the nouveau drivers. However, to use the nvidia drivers in UEFI mode grub has to be permanently set to nomodeset.
This would certainly be my preferred solution as I could go back to a UEFI bios setting with a GPT partition. Does anyone watching here have any experience with this with an nvidia card?
I use Ubuntu 16.04 and in my Software Boutique it is “Virtualbox” and “Virtual Machine Manager”. So, I don’t have VMware in my Boutique.
If you decide to install VMware, it comes as a “.bundle” installer. To install programs that come as a “.bundle” for Ubuntu, see below:
One thing to note: don’t delete the “.bundle” installer after you have installed it. If you ever want to uninstall the package, you need to run the “.bundle” installer again and it will give you the option to remove the installed program.
Okay, did you use a DVD to do your install and did you burn it at the slowest possible speed?, if you used a USB stick, did you fully format it to FAT32?.
I did format the USB stick to FAT32. I used Startup Disk Creator in the Control Center and this is how my USB stick looked afterwards: It seems to have been reformatted to FAT16 by Startup Disk Creator.
Also, I keep getting the following warning. As you can see from the above screenshot, gparted in reporting the stick at 57.7 GB, but it's only a 14.4 GB.
I haven't been able to figure out a way to correct this. Does it make any difference?
I've reformatted USB stick, installed unetbootin and installed ubuntu to USB using unetbootin. Here's screenshot using gparted after all completed. Disk size now being reported correctly and error messages no longer showing up. Does this mean I probably have a faulty install of ubuntu?
I have had nothing but problems using unetbootin , in fact I don’t think its ever worked for me.
I ended up using rufus from within windows or using disks found in most linux Os
I've reformatted my usb twice (the second time took over an hour because I overwrote everything with 0s), and used unetbootin to burn the iso image to disk.
Neither time did unetbootin create a bootable usb. I've tried installing mintstick without luck. I also tried disks, but got the same disk layout and error messages (disks reformatted my usb to FAT16) as when using Startup Disk Creator.
I've also tried to use udisks2. Synaptic says it's installed , but I can figure out how to run it. Any thoughts?
