Fixing GRUB with boot-repair

So this other day I decided it was time to install Windows cause I had the need for some tools not running greatly under Wine, and with my SSD, dualbooting is a whole less hassle than it used to be. No more waiting 5 minutes  for booting. After reading up on how to make this work, as Windows will for sure erase grub from the MBR (master boot record), it seemed pretty easy to get grub installed the right way again. So I installed Windows 7, took about an hour, then decided I would try to reinstall grub. I plugged in my live-USB and followed these simple steps:

This launched boot-repair which looks like this:

boot-repair

At first I tried the Recommended repair, but my setup is kinda awkward, I have one SSD disk with Ubuntu and Windows 7 on them, and one HDD for data, one ext2 partition and one NTFS partition.

So the Recommended repair didn’t work, so I clicked the Advanced options.

boot-repairadv

Here I just checked off the Place GRUB into option to sda (my SSD), and everything installed correctly. I rebooted, and now it all works as intended again.

Editing hosts file on Windows 7

By default, you’re not allowed to edit the hosts file (c:\windows\system32\etc\drivers\hosts) on Windows 7. It will give you an error message telling you you are not permitted to perform this action when you try to save the file after making changes. To make changes, click the startmenu, search for notepad (or notepad++ as I’m using here), and select Run as administrator. This will give you the permissions you need to save the file.

 

Run as administrator

Virtualbox with Atheros AR9285 as network adapter

Today I once again desided to try a few Linux distributions, mostly to use as a testing server.

The VirtualBox setup screen
VirtualBox
I landed on VirtualBox as ny virtualization solution, and got down to it. Installation went great, and I got everything running. I set up the network solution as a bridged connection with the wireless network card on the host as the connection point with my hom erouter.

Now, everything works jolly for a variable amount of minutes, and the wireless card in Windows7 starts searching for my SSID. If I’m lucky it connects again, and everything works for a few minutes, then the same procedure again. And if I’m not lucky, I end up with a “spinning” connection, constantly connected but not connected.

I can’t really wrap my head around what’s causing this, cause in my mind the wireless should have stopped working imidiately, and not after a couple of minutes?

Now, this is when I’m using it as a bridged connection. So I tried to switch it over to NAT… And now it worked for 30 minutes without a single hickup… The conclution is, I guess, that in the end I myself is the only one to blame. NAT was the default option, and I just had to go and change it…

But still, it doesn’t work with a bridged connection. That’s something that’s still a grudge in my book!