search

DavidBrenner3 / VMUB

A tool for testing boot configurations on USB drives
197 stars 43 forks source link

VMUB will not run VBox version 6 - get --startvm error #6

Open steve6375 opened 5 years ago

steve6375 commented 5 years ago

The new version 6 of VBox does not work with VMUB 1.72 image

steve6375 commented 5 years ago

Workaround for VBox v6: VMUB - Options - VirtualBox - Exe Path = C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe

steve6375 commented 5 years ago

Better workaround for VBox v6 (--startvm error):

  1. In VMUB - Options - VirtualBox - change Exe Path to C:\Program Files\Oracle\VirtualBox\VMUB.cmd

  2. Run an Admin cmd shell

  3. cd \Program Files\Oracle\VirtualBox

  4. Create a new file in the \Program Files\Oracle\VirtualBox folder called VMUB.cmd

Notepad VMUB.cmd and type and save the following text:

@echo off if "%1"=="" start VirtualBox.exe if not "%1"=="" start VirtualBoxVM.exe %*

[Edit]Note: This does not lock the USB drive however and so does not work properly![/Edit]

Willstar44 commented 4 years ago

Better workaround for VBox v6 (--startvm error):

  1. In VMUB - Options - VirtualBox - change Exe Path to C:\Program Files\Oracle\VirtualBox\VMUB.cmd
  2. Run an Admin cmd shell
  3. cd \Program Files\Oracle\VirtualBox
  4. Create a new file in the \Program Files\Oracle\VirtualBox folder called VMUB.cmd

Notepad VMUB.cmd and type and save the following text:

@echo off if "%1"=="" start VirtualBox.exe if not "%1"=="" start VirtualBoxVM.exe %*

thanks heaps working for me on MX linux

steve6375 commented 4 years ago

I found this had a problem though as it was not actually locking the USB drive to allow write access, Accesses were still in snapshot mode because the volume was not locked.

So VMUB locks the USB drive for sole access and then runs VBox. If you run a cmd file then the USB drive is no longer locked and so it does not work properly.

e.g.

  1. Boot to grub4dos in VBOX 6 using VMUB and new VMUB.cmd
  2. Use grub4dos to change a file on the USB drive (e.g. echo ddd > /existingfile.txt
  3. Reboot and check /existingfile.txt - it will be unaltered!

With no cmd and VBox 5 the file will be permanently altered, so this defeats the main purpose of VMUB which was to get locked write access to the USB drive!

Therefore we have to use VBOX v5 for proper functionality.

Willstar44 commented 4 years ago

hehe yes I have just found that out , i thought I broke my USB lol , for some reason when using MX 19 it doesn't work for me on 5,0 but does work on 6.0 but MX Linus just updated from 18.3 which work 5.0

Willstar44 commented 4 years ago

h

I found this had a problem though as it was not actually locking the USB drive to allow write access, Accesses were still in snapshot mode because the volume was not locked.

So VMUB locks the USB drive for sole access and then runs VBox. If you run a cmd file then the USB drive is no longer locked and so it does not work properly.

e.g.

  1. Boot to grub4dos in VBOX 6 using VMUB and new VMUB.cmd
  2. Use grub4dos to change a file on the USB drive (e.g. echo ddd > /existingfile.txt
  3. Reboot and check /existingfile.txt - it will be unaltered!

With no cmd and VBox 5 the file will be permanently altered, so this defeats the main purpose of VMUB which was to get locked write access to the USB drive!

Therefore we have to use VBOX v5 for proper functionality.

how does a noob like me revert back so I can use my USB?

steve6375 commented 4 years ago

Just install VBOX v5 and change path back to VirtualBox.exe