Sep 24, 2014

Wireshark hanging on Windows 8.1 at startup

After upgrading Windows 8 to Windows 8.1 my wireshark freezed on every startup without showing up the main window.
The only workaround was to deinstall wireshark including wincap and installing it again. But after the nex reboot, it freezed again.

After searching around i found the following fix, with cured this problem:

inside the registry you have to change the DWORD start in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\npf

from 0 or 1 to 2. After that wireshark will start properly even after reboots....

Another possible solution are to issue these commands as administrator:
sc start npf
sc config npf start= delayed-auto

Jun 19, 2014

Android Update: 4.4.3

After nearly everyone upgraded to 4.4.3 my device came up with the icon for upgrading android to its next version:

For a complete history of all updates visit this posting.

Jun 11, 2014

FritzBox 7270: CLIP stops working after upgrading to FritzOS 6.05 (problem solved)

After upgrading to FritzOS 6.05 CLIP stopped working with my analog phone.
The settings looked quite ok: (Telefonie -> Telefoniegeräte -> bearbeiten -> Merkmale des Telefoniegeräts)

This basic feature was certainly not shipped without testing. So this has to be a problem of data/parameter migration.
After unchecking CLIP, doing a reboot and checking the box again CLIP, it worked like before...

May 20, 2014

Mounting VMWare-Volumes/Disks with Debian

Some time ago a vmware server did not recognize any more a data disk. This disk was formatted with vmfs v3 (enter the vmware server via ssh and type mount..). First thing i did, was creating an image of this disk, to play around without any danger of data loss.

There is a good article how to mount vmfs, but on debian i had to install the package otherosfs.

After i installed this package, i got the following error:

root@debian:/tmp# vmfs-fuse image /mnt/vm
VMFS VolInfo: invalid magic number 0x00000000
VMFS: Unable to read volume information
Trying to find partitions 
But: Do not worry about this error message. The image was mounted on /mnt/vm and accessible without any problem...