Vivid Abstractions Where Programming Becomes An Abstraction

24Mar/131

How to fix: Windows Phone 8 Driver Not Found

So yeah this took me some time to figure out so here we go:

Hardware-IDs:

USB\VID_045E&PID_F0CA&REV_0100&MI_01
USB\VID_045E&PID_F0CA&MI_01

I am using Windows 7 64-bit.

Problem: Upon connecting the Windows 8 Phone, there are 2 drivers to be installed. One installs succesfully, the other one is left with a yellow exlamation mark in the Device Manager.

1. Get yourself the Windows Phone USB drivers e.g. from here

2. Unzip the folder.

3. Open the "WmZuneSerUSB.inf" file with Notepad/Editor.

4. Change the lines
[Microsoft.NTx86]
%DeviceDesc% = WINMOBIL, USB\Vid_045E&PID_04EC&MI_01

[Microsoft.NTamd64]
%DeviceDesc% = WINMOBIL, USB\Vid_045E&PID_04EC&MI_01

to

[Microsoft.NTx86]
%DeviceDesc% = WINMOBIL, USB\VID_045E&PID_F0CA&REV_0100&MI_01

[Microsoft.NTamd64]
%DeviceDesc% = WINMOBIL, USB\VID_045E&PID_F0CA&REV_0100&MI_01

5. Save the inf file.

6. Go into the Device Manager, right-click the device with the exclamation mark, "Update drivers", "Search on computer", and navigate to the folder you unzipped and which includes your updated .inf file. Click on "Next" and you should be good to go.

24Nov/1110

How to fix: “You are logged in from a region we do not allow someone to play from.”

"You are logged in from a region we do not allow someone to play from."

If you look at the log files you can see, after you start the Launcher it will download an update in the background. Patience is a virtue.

01111241954 ERROR  ManifestComplete:patcher/http://manifest.swtor.com/patch/patcher.patchmanifest
201111241954 INFO   Manifest: patcher, current=-1/upcoming=-1/required=23
201111241954 INFO   ManifestState=Download: patcher, current=-1/upcoming=-1/required=23
201111241954 INFO   Download: http://127.0.0.1:54263/app/download.solidconfig
201111241954 INFO   Download: http://cdn-patch.swtor.com/patch/patcher/patcher_-1to23.solidpkg

So just be patient, the launcher will restart automatically to finish the update. This is all being done in background so you won't notice anything. You can check the log files for updates.

  1. Go into your C:\Program Files (x86)\Electronic Arts\BioWare\Star Wars - The Old Republic
  2. Delete patcher.version
  3. Delete launcher.settings
  4. Open launcher.exe and wait until it restarts. Check the log files for more information!

Enjoy :)

25Apr/110

How to: Fix Scrolling Bug In Age of Empires 2

I have researched this problem a little bit and it is obvious that it is a conflict with the Microsoft Zune software. My guess is that it has to do with the Zune driver because everything I tried with Process/Services did not work.

Option 1:
Uninstall the Zune software.

Option 2 (if you want to keep the Zune software like me):
Restart your computer but don't open the Zune software. This bug only occurs after you run the Zune software for the first time.

Enjoy.

14Dec/091

GetAsyncKeyState not working? Look here!

Especially when running on a 64-bit system you may run into problems. To ensure your application works on 32-bit and 64-bit you have to make some small changes to the API declaration.

To make something clear: Even though it says "user32.dll" it is actually a dll with 64-bit functions. The 32-bit version of it is in the WOW64 folder.
wrap-lines: true
This is the code I am using:

using System.Runtime.InteropServices;
    static class VKeyboard
    {
        [DllImport("user32.dll", CharSet = CharSet.Auto, SetLastError = true)]
        public static extern IntPtr GetAsyncKeyState(IntPtr vKey);
        public static bool CheckKeyDown(System.Windows.Forms.Keys vKey)
        {
            return 0 != ((Int64)GetAsyncKeyState((IntPtr)vKey) & 0x8000);
        }
    }

To call this just use:

if (VKeyboard.CheckKeyDown(Keys.ControlKey))
{
//do something
}

The integer types were changed to IntPtr because IntPtr is a wrapper that changes depending on the system (32-bit or 64-bit). You can change vKey as well to IntPtr to save the typecast but I like the "Keys." calling method.

Enjoy.

22Oct/092

How To Fix: “A Disk Read Error Occurred” – “Error Loading Operating System”

"A Disk Read Error Occurred. Press CTRL+ALT+DEL to restart"

or

"Error Loading Operating System"
This is only one solution because this problem can be caused many reasons.

My symptoms were that I had to restart my computer multiple times after Post-Bios until I could finally start into Windows. Inside Windows, it sometimes locked up when the Hard Drive was under heavy use. I exchanged the cables but it did nothing. Now today I unplugged the Slave Drive and it worked! My Primary Hard Drive (Master) hosts the Operating System and the Secondary Hard Drive (Slave) as a file reservoir. It seems that the Secondary Hard Drive (since they share one cable) did not properly pass the data through the cable from my Primary Hard Drive to the Motherboard. Try it out for yourself!

   
SEO Powered by Platinum SEO from Techblissonline

Page optimized by WP Minify WordPress Plugin