Skip navigation.

Dietrich Schroff

Syndicate content
Dr. Dietrich Schroffhttps://plus.google.com/101232877473830670008noreply@blogger.comBlogger283125
Updated: 1 week 5 hours ago

Android Update: 5.0

Tue, 2014-11-18 14:27
Today my Nexus 7 got the upgrade to Android 5.0:
 After this upgrade, many things changed, like the system settings:



But everything is slower than before.... ;-(

For a complete history of all updates visit this posting.


Virtualbox: only 32bit guests possible even though virtualization enabled in BIOS / Intel Process Identification Utility shows opposite to BIOS virtualization setting

Fri, 2014-10-03 03:08
Virtualbox on my Windows 8.1 stopped running 64bit guests a while ago. I did not track down this problem. Now some months later i tried again and found some confusing things.
First setting:BIOS virtualization enabled
Intel Processor Identification Utlility in 8.1: virtualization disabled
Second setting
BIOS virtualization disabled
Intel Processor Identification Utlility in 8.1: virtualization enabledWith both settings: Virtualbox runs 32bit guests but no 64bit guests.
 

After some searching, i realized, what was happening:
I added Microsofts Hyper-V virtualization. With that enabled Windows 8.1 is no longer a real host. It is just another guest (the most important guest) on this computer. So with Hyper-V enabled i was trying to run Virtualbox inside an already virtualized Windows 8.1.
After that it was easy: Just disable Hyper-V on Windows 8.1:


And after a restart of Windows 8.1 i was able to run 64bit guests on Virtualbox again....

Wireshark hanging on Windows 8.1 at startup

Wed, 2014-09-24 13:09
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