First use the windows universal key VK7JG-NPHTM-C97JM-9MPGT-3V66T to get back to the generic pro version. Than a activate the windows with the new license key.

Using DISM to install Storage Drivers

If you migrate Windows installations between storage adapters, you’re often left with the well known STOP 0x7B INACCESSIBLE_BOOT_DEVICE. This happens because Windows doesn’t yet have the required drivers installed, and/or set as boot-critical.

The dism.exe tool allows us to install (boot-critical) drivers into an offline Windows „image“. Note that an offline Windows „image“ is nothing special – a regular Windows install is a valid Windows „image“.

After a STOP 0x7B, Windows Boot Manager usually sets up fallback boot into WinRE (Windows Recovery Environment). WinRE has a copy of the DISM tool, so you’re good to go. (Cancel the Startup Recovery assistant if you have to.)

Example DISM commands to use from the WinRE (or WinPE) Command Prompt:

Install Microsoft/Generic Storage Drivers

This includes MSAHCI, IntelIDE, AMDIDE, ATAPI, PCIIDE and so on:

dism /image:d:\ /add-driver /driver:d:\windows\inf\mshdc.inf /forceunsigned

(D: is assumed to be the Windows SystemDrive partition.)

Install LSI MegaRAID / SAS/SATA Drivers

dism /image:d:\ /add-driver /driver:d:\windows\inf\megaraid.inf /forceunsigned

(D: is assumed to be the Windows SystemDrive partition.)

Install VirtIO Storage Drivers

If you have the VirtIO drivers ISO mounted, and added the drivers in the Recovery GUI, dism can add them to the offline Windows as well:

dism /image:c:\ /add-driver /driver:d:\win7\amd64\viostor.inf

(C: is assumed to be the Windows SystemDrive partition, and D: is the virtio ISO/CD.)

Im Rahmen eines Hardwaretausches – kann es dazu kommen, dass nach der Windows-Anmeldung eine Aktivierung des Systems erforderlich ist. Wenn sich die Hardware wesentlich ändert, gewährt Windows hierbei keinen Aufschub der Aktivierung.  Eine Möglichkeit ist die Windows-Aktivierung für 30 Tage aufzuschieben. Folgender Befehl ausgeführt im abgesicherten Modus, bewirkt dies:

rundll32.exe syssetup,SetupOobeBnk

Manschmal ist es erforderlich vorher folgende Befehle auszuführen, um die erfolgreiche Ausführung des obigen Befehls zu ermöglichen:

regsvr32 regwizc.dll regsvr32 licdll.dll

1. Start Disk Management (diskmgmt.msc) on your computer and take a closer look at your hard disk. Note the disk number and the partitions.
2. Start DiskPart and select your disk: DISKPART> select disk 0
3. List all partitions: DISKPART> list partition
4. Now, select the hidden partition (see step 1) DISKPART> select partition 1
5. Type DISKPART> detail partition and verify that it is hidden. Remember the Type value, this will be handy if something goes wrong.
6. Set the type of the hidden partition to 07. Type DISKPART> set id = 07 override
7. If everything goes ok, you will receive the following message “Diskpart successfully set the partition ID.“
8. All done. Type Exit to close DiskPart.
9. Check the Disk Management to see witch drive letter has been assigned to the recovery partition.

List of partition types:

• 07 = Windows NT NTFS
• 17 = Hidden
• 27 = OEM Recovery

DiskPart command line syntax and parameters can be found here.

I have now added a automatic bed leveling to my Turnigy Fabrikator 3D printer.
It is running the Marlin Firmware 1.1.0 RC-4

After playing around with Designs, my Icon’s where messed up.
Even a reinstall of an app did not help. After searching on the internet, I found a working solution. Remove app_icons.db app_icons.db-journal with:

cd  /data/data/com.google.android.googlequicksearchbox/databases
rm app_icons.db app_icons.db-journal

Then force stop google app, that forces the repaint of the icons, don’t know if it’s the right way to do it but it works.

Situation

After installing Windows alongside Linux, GRUB has been replaced by the Windows bootloader. How do you get GRUB back into the MBR?

Note „has been“. When openSUSE is installed according to recommendation to keep a neutral MBR that Grub will have been installed to a partition rather than the MBR, which will result in a simpler „repair“ procedure..

Procedure

You have to make sure to be able to boot into openSUSE. You can do this either by using the Rescue System mode on the installation DVD or by using a CD withPlop Boot Manager or Super Grub Disk, for example. Note that you can let boot any ISO on USB with UNetbootin. Then you can repair the Master Boot Record with a few commands:

If using grub2 (default on openSUSE 13.1)

Open a terminal and type commands. Firstly elevate your priviledges (not required in Rescue System mode):

sudo -i

Figure out from the partition table what is your (main) linux partition, e.g. /dev/sda3:

fdisk -l

Then type:

mount /dev/sda3 /mnt
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc # maybe superfluous
mount --bind /sys /mnt/sys # maybe superfluous
mkdir /mnt/mounts # could be needed if booted with rescue openSUSE 13.1
mount --rbind /mounts /mnt/mounts # could be needed if booted with rescue openSUSE 13.1

If this preparation went well, perform the actual change:

chroot /mnt
grub2-install /dev/sda
exit

And if that succeeded,

reboot

If using legacy grub

Open a terminal and type (no ’sudo‘ is required in Rescue System mode):

 sudo /usr/sbin/grub

Then execute the following commands:

 grub> find /boot/grub/stage2 (will show the path of actual grub installation, you will need on the next step)
 grub> root (hdx,y)
 grub> setup (hdx)
 grub> quit

Caution: x represents the disk number and y represents the partition number where GRUB stage2 is installed. The numbering starts at 0. For example, if the first command outputs (hd0,5) you should do root (hd0,5) followed by setup (hd0). After rebooting, the GRUB menu should reappear.

This solution was sourced from please_try_again on the forums.

If a neutral MBR was employed

All that is necessary is to use any available partitioning tool to move the boot flag from the Windows partition to the partition to which Grub is installed. This is easily done with FDISK (which calls the boot flag the active flag) from a DOS boot or from DISKPART or Disk Management from a Windows boot, or using one of the partitioning tools from a generic bootable media such as the Ultimate Boot CD or Hiren’s BootCD.