Related
Hi, my question is about windows mobile sdk 6. When I try to run the example "CECamera" with Visual Studio, Mobile 6.1 Emulator, ActiveSync, and SDK, I get the following error. The emulator starts up, but the program does not load. Then the error is displayed, "Unable to start %CSIDL_PROGRAM_FILES%\CECamera\CECamera.exe The system cannot find the file specified." Anyone know how to fix this? Also I have a camera attached to the computer and am hoping that the device emulator will use it, any help would be greatly appreciated.
The SDK emulators have no camera functionality. Therefore there is no camera.exe or cecamera.exe installed in the rom image that the emulator is running. Besides, the name of the camera program is dependant on the particular software build for that device.
Same goes for Bluetooth and wireless.
The device is being emulated on your PC. The only hardware to which it has access is the directory in File -> Configure : Shared Folder.
Hi Folks,
Brand new to the forum (and, indeed, Android development). I have a Nexus 7, and I'm developing on Windows 7 using Eclipse. To try out the tutorials on the Android site, I attempted to follow their instructions to create a virtual Nexus 7 device. Seemed pretty straightforward. However, when I try to start the deveice, I get the error "Failed to allocate memory:8". It doesn't matter if I put 200 in the "SD Card Size" or select the SD card img file, I get the same message and the emulator is terminated by the application.
I have searched the archive on this forum but can't find anything close to this. Any ideas?
Cran0g said:
Hi Folks,
Brand new ot the forum (and, indeed, Android development). I have a Nexus 7, and I'm developing on Windows 7 using Eclipse. To try out the tutorials on the Android site, I attempted to follow their instructions to create a virtual Nexus 7 device. Seemed pretty straightforward. However, when I try to start the deveice, I get the error "Failed to allocate memory:8". It doesn't matter if I put 200 in the "SD Card Size" or select the SD card img file, I get the same message and the emulator is terminated by the application.
I have searched the archive on this forum but can't find anything close to this. Any ideas?
Click to expand...
Click to collapse
You might not have enough ram in your PC, try 512mb that's as low as you can go for 4.2
Sent from my Nexus 7 using xda app-developers app
IRX120 said:
You might not have enough ram in your PC, try 512mb that's as low as you can go for 4.2
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hello,
I''m new as well and have exactly the same scenario on installing Eclipse on win 7 64 bits and try to learn with a Nexus 7 tablet.
I've tried adding the parameter to set 512mb but I'm still have the same problem. what else can be the problem ?
Thanks for any feedback.
Cran0g said:
Hi Folks,
Brand new to the forum (and, indeed, Android development). I have a Nexus 7, and I'm developing on Windows 7 using Eclipse. To try out the tutorials on the Android site, I attempted to follow their instructions to create a virtual Nexus 7 device. Seemed pretty straightforward. However, when I try to start the deveice, I get the error "Failed to allocate memory:8". It doesn't matter if I put 200 in the "SD Card Size" or select the SD card img file, I get the same message and the emulator is terminated by the application.
I have searched the archive on this forum but can't find anything close to this. Any ideas?
Click to expand...
Click to collapse
Did you solve this issue ?. I have exactly the same problem you have and I couldn't find any answer yet.
Thanks.
nexusnino said:
Did you solve this issue ?. I have exactly the same problem you have and I couldn't find any answer yet.
Thanks.
Click to expand...
Click to collapse
There seems to be a bunch of things that the prior respondents never bothered mentioning
- What version of OS are you using on your PC? (also, 32-bit, or 64-bit?)
- How much RAM is in your PC?
- After you boot up your PC, and have a look with the Windows Task Manager, how much memory do you have in use with your PC sitting idle?
- What version of the Android Developement Tools do you have installed into Eclipse (v21.1 or above)?
- Does your processor have Intel/AMD Virtualization extension support?
- You are *not* attempting to run an emulator under an emulator (e.g. VirtualBox) are you?
- Which API Level and Device are you trying to run from the AVD?
I have a Win7 Pro x64 box, i5 quad-core uP w/ VT-X extensions, 4 GB RAM. When I create (for instance) an "API Level 17" Nexus 7 emulator, the AVD dialog complains:
Android Virtual Device Manager said:
On Windows, emulating RAM greater than 768M may fail depending on the system load. Try progressively smaller values of RAM if the emulator fails to launch
Click to expand...
Click to collapse
Now, the default settings for a Nexus7/API 17 AVD device are 1024 MB RAM (just as with the physical device). When I attempt to run this way, sure enough I get a message
Starting Android Emulator said:
...Failed to allocate memory: 8...
Click to expand...
Click to collapse
but when I edit that virtual machine to use 768 MB, it runs just fine.
Monitoring the physical memory in use:
Windows 7 Pro x64: ~1.0 GB
+ Eclipse (v3.6.2) + AVD : ~ 1.2 GB
+ 768 MB Emulator Running: ~1.7 GB.
I conclude that the "768 MB" limit is some strange interaction between the ADT and Windows - I routinely operate other VMs on my machine that use up to 2 GB of memory.
hope that helps.
bftb0 said:
There seems to be a bunch of things that the prior respondents never bothered mentioning
- What version of OS are you using on your PC? (also, 32-bit, or 64-bit?)
- How much RAM is in your PC?
- After you boot up your PC, and have a look with the Windows Task Manager, how much memory do you have in use with your PC sitting idle?
- What version of the Android Developement Tools do you have installed into Eclipse (v21.1 or above)?
- Does your processor have Intel/AMD Virtualization extension support?
- You are *not* attempting to run an emulator under an emulator (e.g. VirtualBox) are you?
- Which API Level and Device are you trying to run from the AVD?
I have a Win7 Pro x64 box, i5 quad-core uP w/ VT-X extensions, 4 GB RAM. When I create (for instance) an "API Level 17" Nexus 7 emulator, the AVD dialog complains:
Now, the default settings for a Nexus7/API 17 AVD device are 1024 MB RAM (just as with the physical device). When I attempt to run this way, sure enough I get a message
but when I edit that virtual machine to use 768 MB, it runs just fine.
Monitoring the physical memory in use:
Windows 7 Pro x64: ~1.0 GB
+ Eclipse (v3.6.2) + AVD : ~ 1.2 GB
+ 768 MB Emulator Running: ~1.7 GB.
I conclude that the "768 MB" limit is some strange interaction between the ADT and Windows - I routinely operate other VMs on my machine that use up to 2 GB of memory.
hope that helps.
Click to expand...
Click to collapse
=========================================
Thanks for the message; here are the answer to the questions you sent:
1- I have Windows 7 ( 64 bits)
2- 4 GB of Ram
3- When the computer just started and idle use 1.3Gb of Ram
4- I've installed ADT V 22.0.1 - 685705
5- I can't find how to check if the VT-x is enable or not
6- I don't use any kind of Virtual Machine on this computer
7- API level is set to 17, but not sure what you refer to Device or AVD
As an extra comment I have and Nexus 7 that is running 4.2.1, that eventually I would like to test the apps in there.
Thanks for your time and help.
nexusnino said:
=========================================
Thanks for the message; here are the answer to the questions you sent:
1- I have Windows 7 ( 64 bits)
2- 4 GB of Ram
3- When the computer just started and idle use 1.3Gb of Ram
4- I've installed ADT V 22.0.1 - 685705
5- I can't find how to check if the VT-x is enable or not
6- I don't use any kind of Virtual Machine on this computer
7- API level is set to 17, but not sure what you refer to Device or AVD
As an extra comment I have and Nexus 7 that is running 4.2.1, that eventually I would like to test the apps in there.
Thanks for your time and help.
Click to expand...
Click to collapse
@nexusnino
Your setup looks pretty close to mine. Win7/x64, 4 GB. Now that I think about it a little more, I'm not sure if the VT-X processor extensions matter for the emulator, as the Android emulator is an ARM instruction-set emulator, not a true x86 native instruction-set VM.
(In my case, I built my own machine; knowing that I was going to be using VMs a lot, I went through Intel's processor model comparison database and selected an processor model that supports the VM hardware extensions. Intel sells a lot of "i5", "i7" processor model variants. In your case, you would need to find out the exact processor model in your PC to figure out if it has Intel VT-X or AMD/V. But, as I mention above, I'm not certain it is relevant to the Android emulators).
In the AVD (Android Virtual Device) v21.1, when I select Nexus 7, it pre-populates the VM RAM/Heap settings. If I leave RAM at 1024 MB, I get the error 8 message. But if I adjust the VM RAM size downward (e.g. 768 MB), the VM starts correctly. I didn't try other values - the /!\ caution message seems to indicate that other values, possibly higher, might work.
I just updated my ADT (and eclipse plugins) to 22.0.
Same deal on v22.0 as on v21.0 - the emulator errors out (error:8) if I leave the RAM set to 1024, but if I drop it to 768, it starts up just fine.
see attachment image
What happens if you drop the RAM settings down?
bftb0 said:
@nexusnino
Your setup looks pretty close to mine. Win7/x64, 4 GB. Now that I think about it a little more, I'm not sure if the VT-X processor extensions matter for the emulator, as the Android emulator is an ARM instruction-set emulator, not a true x86 native instruction-set VM.
(In my case, I built my own machine; knowing that I was going to be using VMs a lot, I went through Intel's processor model comparison database and selected an processor model that supports the VM hardware extensions. Intel sells a lot of "i5", "i7" processor model variants. In your case, you would need to find out the exact processor model in your PC to figure out if it has Intel VT-X or AMD/V. But, as I mention above, I'm not certain it is relevant to the Android emulators).
In the AVD (Android Virtual Device) v21.1, when I select Nexus 7, it pre-populates the VM RAM/Heap settings. If I leave RAM at 1024 MB, I get the error 8 message. But if I adjust the VM RAM size downward (e.g. 768 MB), the VM starts correctly. I didn't try other values - the /!\ caution message seems to indicate that other values, possibly higher, might work.
I just updated my ADT (and eclipse plugins) to 22.0.
Same deal on v22.0 as on v21.0 - the emulator errors out (error:8) if I leave the RAM set to 1024, but if I drop it to 768, it starts up just fine.
see attachment image
What happens if you drop the RAM settings down?
Click to expand...
Click to collapse
Thanks very much for the very detail post; I've adjust to 768 and I can consistently run without getting the error back.
Much appreciate your time and help.
Paulo
hello xda,..
i was having win7 on ma laptop..recently i have upgraded it to win8 .. my screen clarity has decreased and looks somewhat blur..right now i don have drivers cdto install..so is there any other ways to solve my issue?? pls reply...thanks
my laptop is asus (x5dc)
If you haven't installed the drivers, then your screen probably isn't set to the correct resolution. Go into the screen settings and check that the resolution matches the specs of your laptop.
Keep in mind, without the proper drivers installed, you may not be able to change the resolution.
If you can find the drivers cd, go to asus web site and download a copy of the video drivers.
Move your cursor to the bottom left of the screen on desktop so the little start square appears, right click it and in the menu which appears click "device manager".
This will open the device manager window. In the list that appears will be an option called "display adaptors". Click the arrow next to it to enlarge the options. It should then list what graphics chips are available on the system (in my case on this laptop "Intel (R) HD Graphics 4000", on my desktop NVidia GTX460 and some AMD integrated chipset).
Right click whichever appears (if 2 do this twice, once for each, but do it 1 at a time). Click update driver software. Click "search automatically for driver software". Unless the laptop is older than I think, windows should be able to go off and locate the correct driver for you and install it, you will need an internet connection.
Once that is done, reboot and then go to desktop (you must not skip the reboot). Right click the desktop > screen resolution. In the window which appears set the resolution dropdown box to 1366 * 768, anything else is incorrect for your laptop. The screen might flash a bit as it resizes, thats normal.
Running windows update fully may also update your drivers, its a good idea to try the method above first and then run windows update anyway.
Failing that. ASUS have all the drivers available here: http://support.asus.com/Download.aspx?SLanguage=en&m=X5DC&os=17
thanks... but wen m trying to install the drivers it show's .net framework is needed...and when m installing .netframework it show's d same...and its not installing..
Sent from my A116 using XDA Premium HD app
darshan dazzGeEk said:
thanks... but wen m trying to install the drivers it show's .net framework is needed...and when m installing .netframework it show's d same...and its not installing..
Sent from my A116 using XDA Premium HD app
Click to expand...
Click to collapse
There is something seriously wrong with your windows 8 install if the drivers are claiming to need the .net framework and the .net framework won't install, its built into windows 8.
But if you want to try a manual install of the .net framework:
http://www.microsoft.com/en-us/download/details.aspx?id=21 .NET 3.5
http://www.microsoft.com/en-us/download/details.aspx?id=17718 .NET 4
http://www.microsoft.com/en-us/download/details.aspx?id=30653 .NET4.5 but I doubt required.
But before trying any of those 3 links (which are in the order I would try them), run windows update. The full update, every single important and recommended update. Will probably take hours (on my internet it will actually take 2 days....) but to me it sounds like there is something not right on your system, windows update should fix a few things (like lack of .NET and possibly drivers too) and you can go from there.
I'm new to development, but I thought I'd try my hand at it. I got android studio, and after a little trouble shooting got it to work, but I cannot get the emulator to work. When I try I get the following error: "J:\Users\Tatsuno\AppData\Local\Android\sdk\tools\emulator.exe -avd Nexus_S_API_21 -netspeed full -netdelay none
emulator: ERROR: x86 emulation currently requires hardware acceleration!
Please ensure Intel HAXM is properly installed and usable.
CPU acceleration status: HAX kernel module is not installed!"
I enabled virtualizing in my bios (I hope I did it right, I've never done it before) and attempted to install intelhaxm-android.exe. but when I tried to install that I got the following error: "VT not suported
This computer does not support Intel virtualization Technology (VT-x). HAXM cannot be installed
Please refer to the intel HAXM documentation for more information"
As I understand it, my problem is that my computer isn't acknowledging that virtualizing is enabled. any ideas on how to fix this?
Standard emulator very slow, use Genymotion or some other fast emulator
2/18 Update:
USB charging and controller works, audio probably works. Here's some update on this project:
Battery
Put C:\DPP and C:\EFIESP back. Nokia's driver reads C:\EFIESP\Battery.json in kernel mode (WTF). If you have NokiaEnergyDriver.sys and other PMIC/PEP/MIPI BIF (on some models) drivers installed, you should get battery show up.
Sign drivers?
Yes. Sign everything to prevent bad things from happening. I used a commercial certificate for conveience , but you don't have to do that. Here's a handy script that generates a self-signed certificate and installs it on your phone: https://gist.github.com/imbushuo/4de89ad18a0f538d8ebd18bf6daca56a
Download it, run it as administrator and specify ImageDir to your phone's partition (in mass storage mode). Then sign all your drivers binaries (and catalogs as well) with the fingerprint provided.
When signing your drivers, remember timpstamp all drivers. DigiCert's help documentation is useful for signing binaries.
Turn off UMCI
See https://forum.xda-developers.com/showpost.php?p=36394268&postcount=222. Set UMCIAuditMode key to allow all desktop applications and UMDF drivers load.
Make USB work
You will need several supplemental drivers from Windows Phone: BattFltr.sys, CAD.sys, ufx01000.sys, ufxsynposys.sys (or ufxchipidea.sys, depends on your chipset). Copy registry keys (HKLM\ControlSet001\Services and HKLM\ControlSet001\Enum\ROOT\CAD / HKLM\ControlSet001\Enum\ROOT\BattFltr) add supplemental WDF registry keys. Some files are attached as attachments, so you can take a look to get some idea about that.
Make Windows Store Apps work on unsupported resolution
See my blog post.
---------
While this project is not totally finished (e.g. No Battery status/charging unknown, no cellular, no audio), I decided to post this thread as many people asked me about the tutorial. This is just a brief tutorial, you need to have plenty of time on this to make this happen. Be careful as some steps are very dangerous.
This tutorial is provided AS-IS, without any implicit or expressed warranties. By reading this brief tutorial, you are agreed that you are taking your own risk trying this. I am not responsible for any possible consequences of installing Windows RT or other non-Windows Phone OS on Lumia phones. If your phone ships with Windows 10 Mobile, then this tutorial might not fit you. You can try drivers from other models, but I have no guarantee on this.
General workflow
- Unlock your phone with WPInternals 2.4
- Enter mass storage mode, copy registry files from MainOS partition
- Copy files from DPP partition
- Download Windows RT 8.1 ISO (publicly available on Internet, Google it)
- Download a Lumia 2520 recovery image for some files (I will post these files later)
- Download a Windows Phone 8.1 firmware for your phone
- Extract drivers, re-assembly INF files
- Patch some drivers (see my note)
- Self-sign some drivers (see my note)
- Make sure you know what you are doing: Delete MainOS and Data partition, create new NTFS partition for Windows RT. Do not touch other partitions.
- Apply system image (dism works fine)
- Copy DPP files back (C:\DPP)
- Modify sysprep tasks (see my note)
- Apply BCD configuration
- Boot
- Let OOBE fail once
- Go to mass storage mode again, mount registry and force OOBE run again
- Have fun
Notes on this project
ACPI
Reading ACPI DSDT table will help you understand your phone architecture. ACPI tables are located in PLAT partition. It is easy to extract them with 7-zip (after converting FFU to VHD). To decompile dsdt.aml, you need to download iASL tool, which is available on Internet.
Certain devices, like touch screen or panel, require other devices have driver loaded and enabled. This is not shown in Qualcomm's ACPI implementation. In my case, I need PEP, PEP 3rd, GPIO, BAM, I2C Device, QMUX, Shared Memory drivers loaded to make touchscreen work. It varies by model.
Re-assembly INF files
Mount SYSTEM registry from your phone or FFU, go to DriverDatabase\DriverPackages\<Some Driver Package>, each key in driver package key matches INF sections respectively. See some driver INF files to get some idea.
Remember to check ControlSet001\Service for additional information if necessary. If you are working on Windows Phone 8.1 firmware, check \Windows\System32\Packages to make sure you've got correct files and registry configs. These files are gzipped.
Patch drivers
Certain drivers read DPP partition for device-specific calibration information. While Qualcomm shares the codebase between Windows RT and Windows Phone, DPP partition is handled differently between platforms. You can search Unicode string "PhoneNT" to determine whether drivers read DPP or not.
To fool drivers think they are living in Windows Phone, you can create another multi-string value in the ProductOptions key. I created a value called "AnotherSuite" and filled "PhoneNT" in. Then I modified all "ProductSuite" Unicode strings in drivers to "AnotherSuite". Remember to re-calculate linker checksum (dependencies) and PE checksum.
This is critical to make wireless (Wi-Fi and Bluetooth) subsystem work.
Graphics
DO NOT use user-mode driver module from WP on Windows RT. The Windows Phone Qualcomm GPU driver does not implement DirectX 9, which is required by Windows desktop. Using WP UM driver will crash DWM.
To correctly enable GPU acceleration, use kernel driver and decoder module from your firmware, and user mode driver from Lumia 2520's recovery image. At least this works on Lumia 640 XL.
Touchscreen
Touchscreen works, however, WP driver reports wrong metric system to Windows RT. To workaround this, modify SYSTEM\TOUCH key, make some value larger than expected. See my value for 640XL in attachment.
Remove some sysprep tasks
Remove BCD and WinRE specialization and generalization tasks from sysprep task definition. OOBE will fail still. Boot to mass storage mode, mount SYSTEM registry, change setup type to 1 (see your current OS for ideas about other values), change program path to oobe\msoobe.exe. You should be able to see normal OOBE then.
BCD and Driver Signing
Test signing should be on. Disabling integrity check is recommended (though documentation says this key is ignored prior to Windows 10). Copy catalogs to the new OS, and self-sign drivers you patched.
Kernel Debugger
To enable WinDbg KD, modify your phone BCD:
Code:
bcdedit /store <Path> /dbgsettings usb TARGETNAME:WOATARGET
bcdedit /store <Path> /set {Your OS GUID} Debug On
Connect your phone to PC, start WinDbg, USB kernel debugging, target name "WOATARGET".
Have fun with Windows RT on Lumia, I am going to continue working on audio and battery
Follow
Ty Imbushuo , GREAT WORK
didnt you forgot to make efiesp guid to a efi partition else bcd cant be updated
Is there a way to patch the kernel or a bypass to avoid SECURITY_SYSTEM BSOD on MSM8960 devices?
Thanks for your work. I hope to get a newer Windows Phone soon and try Win10PE, I'm working on a custom shell that hopefully grants it a good experience on handheld devices since we lack ARMv7 ShellExperiences
J0SH1X said:
didnt you forgot to make efiesp guid to a efi partition else bcd cant be updated
Click to expand...
Click to collapse
Qualcomm's firmware is weird, so I didn't do that. (They hard-coded something) Maybe I will try it later with a dev board and see what will happen.
Fantastic job :good:
Is it possible to enable a second external monitor via Miracast ?
What about bluetooth keyboard and mouse ?
Lumia 950/XL should also support 2x monitors ( DisplayPort/HDMI via USB-C ).
It also has more RAM and might run apps better than L640.
imbushuo said:
Qualcomm's firmware is weird, so I didn't do that. (They hard-coded something) Maybe I will try it later with a dev board and see what will happen.
Click to expand...
Click to collapse
thats weired on my 930 this is NEEDED to get rt to boot but weired enough my 640 lte doesnt boot it at alll but sadly i dont get how to reassamble the inf files (im litterally just comparing my compiled touch driver inf with the registry of my 930)
I can not find the windows rt on the Internet. Can I send the file link download?
imbushuo said:
While this project is not totally finished (e.g. No Battery status/charging unknown, no cellular, no r FFU, go to DriverDatabase\DriverPackages\<Some Driver Package>, each key in driver package key matches INF sections res
Click to expand...
Click to collapse
I use google translate so it's hard to follow, it's great when you have a video tutorial, everything is more intuitive and easy.
INF files Qualcomm ARM-based View attachment Inf.zip
prokakavip said:
I use google translate so it's hard to follow, it's great when you have a video tutorial, everything is more intuitive and easy.
Click to expand...
Click to collapse
If you are an end user I would recommend waiting for WPInternals partition dumps for your device
I knew this solution... so they cant make general Qualcomm drivers never. Device specification is nightmare. Better get a hammer and deepmagic
Thank you for all the effort of going through this and providing the information.
Can somebody whoever upload fixed registry files and drivers? i was able to follow all steps successfully (except these parts) but on first boot i just get a blue screen with a sad smiley.
Also, i assumed you meant applying the install.wim image via DISM from the Windows RT 8.1 ISO.
(For those who need more help with this, Google: "Append, apply, and export volume images with a Windows Image (.wim) file",
i'm not allowed to post links due to post count).
Die Anleitung ist jetzt auch in deutsch verfügbar und hier zu finden:
Windows RT 8.1 auf ein Lumia installieren
WPVision.de said:
Die Anleitung ist jetzt auch in deutsch verfügbar und hier zu finden:
Click to expand...
Click to collapse
I registered and it still said i'm not allowed to visit the forum because i dont have permission.
D-V-D-K said:
I registered and it still said i'm not allowed to visit the forum because i dont have permission.
Click to expand...
Click to collapse
That's correct, because you did not follow the guidelines.
The activation for this area is done manually by your first post.
Samuelgames said:
If you are an end user I would recommend waiting for WPInternals partition dumps for your device
Click to expand...
Click to collapse
Can you upload your partition dumps for 640xl?
Removed. Sorry I was being rash.
spavlin said:
INF files Qualcomm ARM-based View attachment 4410518
Click to expand...
Click to collapse
but theese inffiles arent redone from registry
for example touch driver is missing
imbushuo said:
- Download a Lumia 2520 recovery image for some files (I will post these files later)
Click to expand...
Click to collapse
Use at your own risk!
Some Lumia 2520 Firmware And Driver Update 10. 6. 2014:
Code:
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20623735_d3143757b17f94d00f53dc6f3f4dbdf48c36430e.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20624060_4b5dec4829bf5e013bf5e6c045a4ed9367afe88d.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20624064_70ea6951b8f7c7d72963c38e302356f46642ec85.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20624552_3c10b74a53f010a90539ea1e606f562d65a03082.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20626644_7f0f6945d5e0e19e78b3794490990145b98e2c0c.cab
http://au.ds.download.windowsupdate.com/d/msdownload/update/driver/drvs/2014/04/20639225_555ea122b93d34720513db1b344254a0a69a158c.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20639552_08956ac77c46334650fc675794d58325f279ddbb.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20640693_4d4f789e1349e350324fb7e31b60514ae191cb46.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20642401_1278d3d9f4ae8d1903ec0c6f0861ec9912139b96.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20643591_beca8afddf93a8679f6e875f5abfc44f9395975a.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20643598_4a154479fe2ad83eef04c99e96e44b0e88efce8e.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20643814_2d9a86009238af018f92aa76a9be453ef9231424.cab