Hi There,

didn't add any new questions to the test, but I did configure it to be 60 questions and take random questions out of the 135 which are there at the moment. Will add some more this week, but I had a busy weekend and a birthday party today, so I was occupied for most of the day.

I decided to make my machine dual boot and not the conventional way, because I don't have a USB stick available at the moment and I don't have writable DVD's at the moment either. 

I have a Dell machine (E6410) and have 2 disks in there, one is a Modular Bay HDD and is 120GB in Size. SO I took that one to be my main Linux disk. This way I can just pick the Bios bootloader to start from the Modularbay HDD instead of fooling around with a Grub2 bootloader and also decreasing the risk to mess up my Windows 10 system, which is spinning just rigth for me at the moment (Will need it to run Cubase, Roland Studio Capture and stuff like that, so as long as I can't run that on a Linux machine I am stuck with Windows anyway)

So how did I manage this to begin with? I tried to figure out how to start ISO's from a HDD and found pretty soon that I needed grub for that again and needed a running Linux machine to do that in the first place. What I done in the past and will do again is to configure VirtualBox to use my entire drive to install Linux on. Google it to find stuff about it, but here is the "monkey" trick, because VBox doesn't have it out of the box. You should go to a command prompt and CD to the following location:

CD C:\Program Files\Oracle\VirtualBox

There you can run the following (make sure you run CMD as an admin btw)

VBoxManage internalcommands createrawvmdk -filename "C:\Users\[username]\Path\to\VMs\[yourVMfilenamehere.vmdk]" -rawdisk \\.\[Your Target Drive here]

To find what the name of your target drive is you can go the Disk manager and check the number on the left hand side:


So in my case it is Disk 1 and the name will be \PhysicalDrive1 and will look similar to this: "C:\Users\[username]\Path\to\VMs\[yourVMfilenamehere.vmdk]" -rawdisk \\.\PhysicalDrive1

Another hint, you need to run VBOX as an admin otherwise it will salute you with an error that it can't open de vmdk file to begin with.

Then a second hint, make sure you delete the partition and leave it Unallocated as in the screenshot above, otherwise (at least mine did) Linux will error out that it can't write to it, BLK errors etc. I had it formatted with exFat and a drive letter assigned to it in Windows and I guess Windows kept it in use.

At the moment I am in the middle of installing Kali Linux to it, and all seems to go well now as I am writing this.

When I installed successfully I will update this article or write another tomorrow

Have fun and keep things simple ......!