Author: Maurice Ruckman

Posted on

Import VirtualBox Image into Parallels

Guide: Converting Virtual Box virtual machine to Parallels Desktop.pdf

Solution

  • In the VirtualBox Manager, right-click on VM > Clone. ...
  • Launch the new clone of your VM,
  • Uninstall Guest Editions:
    $ sudo ./VBoxLinuxAdditions.run uninstall
  • Shut down the Guest OS properly. ( ..., Restart to make sure it's gone
  • Open Parallels Desktop (in the Applications folder) and choose File > Open.
  • Select  the *.vbox file from VirtualBox
  • Wait till conversion will be completed.

Refer: https://kb.parallels.com/122851

Posted on

Pizza Dough / Pizza Bread

Pizza Dough

1 cup AP Flour 120 g
1 cup Bread Flour 120 g
1 tbls Softened Butter 14 g OR 2-1/4 tsp Olive Oil
1 tbls Sugar
1 tsp Yeast
1 tsp Salt

1/2 cup and 1 tbls Water 105-110F, Microwave water 25 secs microwave

Pizza Bread

Make the above recipe, but it in two containers and keep in the refrigerator for 2+ days.

Lightly dust parchment paper with flour, gently take out of container and set down, touch top with excess flour from board.

Preheat oven to 425, while it's heating cut slits on top of dough about 1" apart diagonally.

Bake for 20 minutes

Posted on

Windows 10 God Mode

Refer: https://www.howtogeek.com/402458/enable-god-mode-in-windows-10/

Create a new folder in Windows 10 and name it to the following:

GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}

Posted on

Repair Corrupt VirtualBox .vbox File

Error in VirtualBox VBOX

These are the steps that VirtualBox takes when it writes a new Vbox file. Each step is contingent on the last one being completed without errors.

  • Write a temporary file with ".vbox-tmp" extension.
  • Delete any existing ".vbox-prev" file.
  • Rename existing ".vbox" file to ".vbox-prev".
  • Rename ".vbox-tmp" to ".vbox".

Have not tried these yet

The error that comes after the corruption of the vbox XML file is usually caused when the system locks up; thus preventing the virtualization software from finalizing the writing out to its file of configuration. The error probably implies that the <VirtualBox> opening tag on the line 2 of the file did not have any corresponding </VirtualBox> closing tag at the file’s end.

The fastest method of finding out if this is exactly what has caused the problem in your case; you can locate your vbox XML file for the Guest Operating System, whose home directory location is inside the folder of ‘VirtualBox’ in the ‘Machines’ folder in the ‘Name-of-Your-Guest-OS-Directory’ folder, saved as ‘Name-of-Your-Guest-OS.xml file’

The cause of the problem and the emergence of the error message could probably be simply that the XML file was badly corrupted whose repair process is easy and quick and might take only a minute to be repaired.

  • Open the .vbox XML file in a text editor
  • Then, go to that file’s last line
  • On not seeing any closing tag of </VirtualBox>, it is confirmed that your XML file is corrupt.
  • Now, initiate by adding this closing tag at the end of the file
  • And then, from there, try and work your way back.
  • Look through the file for the <Opening Tags> which do not have any needed </Closing Tag>
  • Another way is to use some XML validation service
  • Just after a few rounds of the three easy steps of Copying -> Pasting -> Validating, you can successfully repair corrupt vbox XML file.

Refer: https://www.bitrecover.com/blog/repair-corrupt-virtualbox-vbox-file/

Download Notes: [ repair-corrupt-virtualbox.pdf ]

Posted on

Delete Empty Directories

Refer: https://unix.stackexchange.com/questions/46322/how-can-i-recursively-delete-empty-directories-in-my-home-directory

The find command is the primary tool for recursive file system operations. Use the -type d expression to tell find you're interested in finding directories only (and not plain files).
The GNU version of find supports the -empty test, so

Print all empty directories below your current directory.
find . -type d -empty -print

After you've verified that this is selecting the correct directories, use -delete to delete all matches:
find . -type d -empty -delete

Posted on

Issues with Virtual Box – File Not Found

Refer: https://forums.virtualbox.org/viewtopic.php?f=6&t=75068

These are the steps that VirtualBox takes when it writes a new Vbox file. Each step is contingent on the last one being completed without errors.

  • Make a backup of the temporary file with ".vbox-tmp" extension.
  • Delete any existing ".vbox-prev" file or change it to -BAK001 extension
  • Rename existing ".vbox" file to ".vbox-prev".
  • Rename ".vbox-tmp" to ".vbox"

Refer: https://www.techprevue.com/virtualbox-inaccessible-file-not-found/

iii) Out of the above-mentioned issues, "File not found" is the most common one. During that situation, you can go to the location of the file. One of the possibilities is that you might find suffixes after the extension .xml for eg. .xmlmog or .xmlemf. So if you are looking for file abcd.xml it actually exists there by name abcd.xmlemf and hence your system was unable to find the file abcd.xml because it did not exist. Now what you can do is, simply copy the file and paste it in the same location and rename it with extension just .xml. This would solve the issue of an inaccessible "file not found" error.