Windows 8 build 7850 Milestone 1 screenshots

By now you probably heared about the Windows 8 build 7850 Milestone 1 leak. You can find it fairly easily on the Net, the filename is 6.1.7850.0.winmain_win8m1.100922-1508_x86fre_client-enterprise_en-us.iso. The leak is an x86 version of the Enterprise Edition. I have not looked for, or found any other versions. Here are some screenshots. I just couldn’t keep the hilarious background from you guys =)

Nothing exciting though. Mostly the same as Windows 7. The only obvious thing I noticed, was the avatar icon on the far right of the taskbar. I’ll wait for future leaks to check out more of the differences and changes.

I installed it in a VirtualBox 4.04 VM with a SAS HDD Controller, SATA DVD Drive, the ICH9 chipset, IO/APIC and the Intel PRO/1000  MT Desktop NIC. The Oracle VM VirtualBox Guest Additions installed without problems. Had to do the install mostly with the keyboard though. But after that was done, my mouse was working correctly.

Advertisements

BlackBerry Bold 9780 ‘BlackBerry AppWorld is having trouble connecting to the BlackBerry AppWorld server’

After switching from my BB Bold 9700 to a 9780, I was unable to connect to the BlackBerry AppWorld server. I did receive update notifications, but was unable to install them. My Facebook app also stopped working, telling me it couldn’t contact the server(s). At the time, BB OS6 was still very new, so I decided to install some newer beta builds to see if it would solve my issue. I upgraded all the way up to the current build 6.0.0.526 over time, but my problem wasn’t solved.

I tried another Google search today in Dutch instead of in English and while browsing I came across a BB KB article that actually gave the solution, hurrah! I will paste the solution here as a mirror in case the KB article will be taken down on the BB site, just like what happens to so many Microsoft KB articles:

Overview

The following error message appears when BlackBerry App World™ is started:

BlackBerry AppWorld™ is having trouble connecting to the BlackBerry AppWorld™ server. Verify your network connections and try again.

CollapseEnvironment
  • BlackBerry® smartphones that operate on CDMA networks
  • BlackBerry App World™ storefront 1.1.0.20 to 1.1.0.33, and 2.0.0.36 to 2.1.0.39
  • DT 396908
  • DT 568190
  • DT 629799
  • DT 853259
  • DT 1059029
CollapseCause

There are multiple causes for this error.

CollapseResolution

Cause 1

Some wireless service providers using the CDMA network are not able to connect correctly using earlier versions of BlackBerry App World.

Resolution 1

To resolve this issue, update to the most current version of BlackBerry App World™.


Cause 2

Multiple e-mail addresses are associated with PayPal®. At this time, BlackBerry AppWorld™ does not support the association of multiple e-mail addresses with PayPal on the same BlackBerry® smartphone.

Resolution 2

This is a previously reported issue that is being investigated by our development team. No resolution time frame is currently available.

Note: See the workaround at the bottom of the KB.


Cause 3

You are using a BlackBerry® 8830 World Edition smartphone with a roaming Subscriber Identity Module (SIM) card.

Resolution 3

Remove the roaming SIM card from the BlackBerry® smartphone.


Cause 4

The account setup for the BlackBerry® ID has not completed.

Resolution 4

This is a previously reported issue that is being investigated by our development team. No resolution time frame is currently available.

Note: See the workaround at the bottom of the KB.


Cause 5

BlackBerry® smartphones that have handheld software 6.0 have a setting that will permit insecure renegotiations which has been incorrectly set.

Resolution 5

  1. Change the setting to permit insecure negotiations by completing the steps below:
  2. From the Home Screen of the BlackBerry smartphone select Options
  3. From the Options menu select Security
  4. Next, select Advanced Security Settings
  5. Select TLS
  6. If the box labeled Permit Insecure Renegotiations is unchecked, then select the checkbox to enable this setting
CollapseWorkaround

Cause 2

Create a new PayPal user name that is associated with a single e-mail address.


Cause 4

Complete the setup of the BlackBerry® ID by performing the steps below:

  1. Go to http://appworld.blackberry.com/webstore.
  2. In the upper right area of the website, click the Sign In link.
  3. This will open a BlackBerry ID login page. Use your existing BlackBerry ID account to log in.
  4. If the account page or sign up page is presented, complete the details for this to finish the BlackBerry ID registration process.

The one that did the trick for me was Resolution 5. Although I’m quite a paranoid internet user, I can’t recall disabling this option. I’m pretty sure it was the default setting in OS6. Pretty annoying. I hope this blog will help spread the solution to other annoyed BB OS6 users =)

Remote Desktop RDP error 516 after virtualizing a Windows Server 2003 server

After virtualizing another server into our vSphere environment, I was unable to connect to it through the Remote Desktop Protocol/Client (mstsc.exe). The error code was 516. This is a generic error code, that just means there was no listener found on the specified IP address on port 3389. The decription of the error already makes some suggestions how to fix it.

  1. Check if RDP is enabled.
  2. Check if the computer is turned on.
  3. Check if the computer is (physically) connected to the network and check the VLAN config.

After I made sure these three points were correct, I still wasn’t able to connect. A ‘netstat -a’ on the server showed me that no process was listening on port 3389.

I checked the Terminal Services Configuration, and everything made sense. The ‘Microsoft RDP 5.2’ icon had a red cross and threw a sensible error about a missing network adapter.

The previous admin had selected the network adapter from the drop down list on the Network Adapter tab of the properties of the RDP-Tcp Connection. Weirdly enough, there was only 1 physical NIC in the server, so I still can’t quite understand why. But anyways, I selected the option ‘All network adapters configured with this protocol’, to avoid identical problems in the future, and everything was working again =)

%d bloggers like this: