Windows bootloader damaged?

Using dualboot after the re-install of Debian Microsoft Vista could not be loaded anymore. It left me with a black screen stating that: c:\Windows\system32\winloader could not be found.

– For this I used a vista 64 installcd. (use x86 version if applicable) booted into recovery-mode which did not help me very much. At least it gave me terminal, which was all I needed. After reading through Microsoft technet I found a possible solution for this:
– From the prompt I entered the following command to check the BCD-file:
C:\Windows\System32\bcdedit /store c:BootBCD /enum
(It found my Vista install on C:)

It showed that something had corrupted the BCD-file setting some parameters to “unknown”
After entering these commands it worked again:

c:\Windows\System32\bcdedit /store c:BootBCD /set {bootmgr} device boot
The operation completed successfully.

c:\Windows\System32\bcdedit /store c:BootBCD /set {default} device boot
The operation completed successfully.

c:\windows\system32\bcdedit /store c:BootBCD /set {default} osdevice boot
The operation completed successfully.

Check with:
C:Windows\System32\bcdedit /store c:BootBCD /enum

Reboot!

source: http://technet.microsoft.com/en-us/library/cc709667%28v=ws.10%29.aspx

Debian booting from GPT disk using grub2

Booting debian Linux on GPT disk
I tried to boot from newly installed 6 TB raidvolume. It showed me the grub2 prompt.
No big deal. I used some grub-commands to boot into the system and executed update-grub. Still after a reboot even a grub-rescue prompt appeared.
After booting into the system using grub-commands I ran: grub-install, which showed me this error:

/usr/sbin/grub-setup: warn: This GPT partition label has no BIOS Boot Partition; embedding won’t be possible!.
/usr/sbin/grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub-setup: error: if you really want blocklists, use –force.

Using parted I created a small partition (100 MB) at the end of the raid-volume, in my case partition 3. After this I executed in parted the command: set 3 bios_grub on. This enables the partition as a BIOS Boot partition.

Finally grub-install reported no errors. After rebooting the grub boot menu appeared again.

Howto install Tweepy for python3.2 using debian Wheezy

Setuptools itself doesn’t work on Python 3.X. But you can use Distribute, a fork and a drop in replacement for setuptools in python3

curl -O http://python-distribute.org/distribute_setup.py
sudo python3.2 distribute_setup.py
sudo python3.2 setup.py install

First I used tweepy from: https://code.google.com/p/tweepy/downloads/detail?name=tweepy-1.4-py3.tar.gz

Continue reading

How to download Windows 8.1 ISO with 8.0 retail key

Go here.
Download both the 8.0 and 8.1 installers
Launch the 8.0 installer [Windows8-Setup.exe]
Enter your key for 8.0 and begin downloading
Immediately pause your download at 1% (don’t quit at the estimating time screen), then exit
Launch your 8.1 installer [WindowsSetupBox.exe]
You’ll get an error saying element can’t be found or something like that, you’re ok – just close out
Re-launch WindowsSetupBox.exe
You’re downloading 8.1

Create a Notepad text file and copy the following lines:

[EditionID]
Professional
[Channel]
Retail
[VL]
0

In this case because my installation is for Windows 8.1 Pro edition, I’m specifying “Professional” in the EditionID, for the core edition use the EdtionID Core.
Finally, save the text file as ei.cfg inside the SOURCES folder from the bootable drive you just created with the Windows 8.1 installation files.

This method will basically allow you to install Windows 8.1 Pro or Core edition as a trial for about 30 days without entering a Windows 8 product key during the installation — because, once again, it won’t work –.
But of course you have a valid retail key, so after everything is installed and configured, you can go to PC settings, PC & Devices, PC info, and here you can change and activate your product key.

I used This source.

Zalman ZM-ve300 probs

Message: 1e partition EE

According to Zalman FAQ of the product the previous message should indicate that the legacy MBR is followed by an EFI header and that it could be solved with: In “Disk Manager”, please delete current volume and make a new volume.

Unfortunately it didn’t work.
I was still left with a EFI partition at the beginning of my disk which I could not remove. I don’t know how it got there, I think by mistake connecting it to my MAC and adjusting partitions.
I decided to try diskpart from the commandline:

– Start an elevated CMD prompt
– To list all disks type:

list disk

– determine the disknumber
– select the disk with

select disk x

(where x is the correct disknumber)
– Delete all partitions:

clean

– I discovered that the disk was for some reason a GPT disk. It shouldn’t, so I converted it to MBR with:

convert mbr

Then I created an NTFS partition on the disk using diskmanager.
On that disk I created a directory: _iso en put in all the iso-files I needed
After disconnect en reconnect the drivedisplay no longer showed the error-message and the drive was functional again.

apcupsd

I recently had to replace the batterypack on my APC Smart-UPS 3000 RM, which I ordered from shop4power. It was as cheap as I could get. (And I mean 112 euro is really cheap!)
I had to reinstall apcupsd (latest version I could find) because I could not write the battery-installdate into the EEPROM. I took the package from the Debian unstable repository. I decided to update the apcupsd-cgi scripts package also. The latter presents a statuspage in a webbrowser which is also fancy to have.

Continue reading

wireless hassle

Setup a b43 compatible wifi adapter using /etc/network/interfaces. In this way using desktop networking app is not nescessary and computer connects automatically to the network during boot in the background

sudo apt-get install wpasupplicant firmware-b43-installer b43-fwcutter

Generate wpa-psk key:

wpa_passphrase <your_essid> <your_ascii_key>

Edit /etc/network/interface

auto wlan0
iface wlan0 inet static
address 192.168.X.X #static IP to be used
netmask 255.255.255.0
gateway 192.168.X.X #your gateway
wpa-ssid <essid>
wpa-psk <generated-key>

source: https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx