8thString

You might observe the following Gtk warnings when running QNX Momentics 6.5.0 on Ubuntu 13.10 64-bit. (qde:9636): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine", (qde:7229): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (qde:7229): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks", To fix, run the following command. $: sudo apt-get install gtk2-engines-murrine:i386 gtk2-engines-pixbuf:i386 gtk2-engines:i386

c:\>vboxmanage dhcpserver add --netname qnxnet --ip 192.168.100.1 --netmask 255.255.255.0 --lowerip 192.168.100.10 --upperip 192.168.100.100 --enable Keyword: VirtualBox, DHCP, internal

$: sudo do-release-upgrade References: http://askubuntu.com/questions/110477/how-do-i-upgrade-to-a-newer-version-of-ubuntu

Followed installation instruction from  http://fsharp.org/use/windows/  to install F# using option #2. Installation was not smooth (could be because of my internet connection). Retried several times with few workarounds (delete corrupted files, install files manually, etc). Tried to create a new F# project with all default values, running it failed with the message Build failed. MSBuild operation failed Build: 1 error, 0 warnings Took me several days (tried several minutes a day to check logs, tweak settings, etc). Finally found a workaround. In Project | [project] Options | Main Settings , ensure that " Use MSBuild build engine (recommended for this project type) is unchecked . Tags: F# Xamarin Studio Windows 8.1

The host machine experienced a power failure, when a guest machine was started up it failed with error message below. Failed to open a session for the virtual machine MACHINENAME. ahci#0: The target VM is missing a device on port 0. Please make sure the source and target VMs have compatible storage configurations [ver=6 pass=final] (VERR_SSM_LOAD_CONFIG_MISMATCH). It seems like Virtualbox virtual machine configuration was corrupted. Looking at the virtual machine settings noticed that the virtual HD attached to the SATA port was gone. To workaround this case, re-attached the latest snapshot to the VM. Use Virtual Media Manager to determine the correct UUID.

Got a Windows 7 SP1 32-bit Pro machine that have seen various large applications already. So I am not sure if the security policy of the machine is the default. When trying to mount a Samba share got the error message below. System error 58 has occurred. The specified server cannot perform the requested operation. This was done via net use \\<ip>\share . Mounting the share via Windows Explorer yields nothing, just a long wait for nothing. The fix for my case was to change Security Settings | Local Policies | Security Options | Microsoft network client: Digitally sign communications (always) to disabled . You have to reboot the machine for the changes to take effect. References: http://social.technet.microsoft.com/Forums/windows/en-US/5dd9991b-78e7-4fa3-b17c-366e4ae0092f/cant-connect-to-samba-from-windows-7-vista-xp-ok-many-popular-solutions-tried-without-success?forum=w7itpronetworking

Microsoft changed course and released Windows 8.1 to MSDN and TechNet users earlier than planned. It was made available last Sept 8, 2013 . This got me excited to play with this latest version. Downloading the ISO was quite frustrating as I can't use Firefox Download Them All plugin, just does not work. Downloading via IE10 was also painful but there is a workaround. VirtualBox also released 4.2.18 last Sept 6, 2013. This must be good, two good products released in the past few days. Upgrading of VirtualBox didn't work the first time. I have to do a repair to get it to work. So essentially, I have to install it twice. Installing of Windows 8.1 into VirtualBox was nonevent. But getting guest additions was challenging. I had to read lots of blogs including VirtualBox 4.2.18 release forum discussion topic . So, how did I get guest addition auto-resize to work? I have to install guest additions *twice*! This is what was working for me: Install guest additions... then re