Related
Windows VISTA Config guide
NOTE: Vista Rom update Utility(attached at the end of post #4) is required when Flashing Roms on Windows Vista.
To Download This Guide as a PDF, click HERE
To Send This Guide as an E-Mail, Click HERE
To Print This Guide, Click HERE
Written by MrVanx <<ALL CREDIT GOES TO THIS MAN. This is a direct Copy of the original document.
Wednesday, 18 April 2007
(Thanks to invictive for the screenshots and testing) << I LINKED TO HIS SCREENSHOTS
UPDATE: Please try downloading the latest WMDC first before attempting anything in this section of the guides. you will find the latest version HERE .
To follow this guide please make sure you have a copy of WinRAR installed, I will refer to the Windows Mobile Device Centre as the WMDC for ease of reading. If you do not have the WMDC installed please go here to install it first.
One problem with windows VISTA is that it uses the new "Windows Mobile Device Centre" and not activesync which we are used to, thus our standard RUU programs will not upgrade our Hermes devices as in windows XP. This guide will show you how to configure VISTA to work just the same as XP with our RUU programs.
For this guide firstly you need to download the new drivers:
Drivers for Windows Vista x32
Drivers for Windows Vista x64
NOTE:: If you are using a x64 bit computer, you will need to boot up with driver signing enforcement turned off. To accomplish this, you will need to press F8 during boot up. If you do not do this, the 64 bit drivers will not install properly and this tutorial will not be of any use to you.
Extract the contents to a folder on your desktop, call this folder "AS_DRIVERS". It contains the drivers from activesync which we will use instead of the native VISTA WMDC drivers when the device is in bootloader.
Now you must enter the bootloader on your device, to do this press and hold both the side ok button and the power button then put your stylus into the hole on the bottom of the device, your device will reset and show the red blue green bootloader screen. LEAVE THE DEVICE IN BOOTLOADER MODE and connect it using the USB cable to your VISTA PC.
Now navigate into the WMDC (Start>All Programs>Windows Mobile Device Center) and click on the "connection settings" menu icon.
In the connection settings menu untick "allow USB connections" then press OK. Now exit the WMDC and return to the desktop, go into the start menu and type "Services", this will take you into the local services dialogue and show a list of all services either running or registered with your pc.
Scroll down the list and make sure these services are present:
Windows Mobile-based connectivity
Windows Mobile 2003-based connectivity
If these services are not started then double click each one and set them to Automatic start by clicking the "startup-type" drop-down menu and selecting automatic then click the start button in the same window, apply the setting by pressing OK. Now return back to the desktop again.
Go into the start menu and type "Device Manager" then run, this will take you into the device manager. Click the "+" symbol next to "Mobile Devices" and double click on "HTC USB Sync". This will bring up the properties of the currently connected device (the hermes in bootloader).
Go to the "Driver" tab and click "Update Driver".
Click "Browse My Computer for Driver Software".
Select "Let me pick from a list...."
Click the "Have Disk" button.
Click "Browse" and navigate to the AS_DRIVERS folder we created earlier.
Vista x32 users select the file "wceusbsh.inf" Vista x64 users select the file "wceusbshx64.inf" Then click Open.
click next and the driver will be installed (wait a moment).
Press close and escape back to the desktop now.
Now we must stop the WMDC process, start the task manager by pressing Ctrl+Shift+Escape.
Click the WMDC line and click "End Process". In the confirmation window, again press End Process.
Now re-enter the WMDC and re-enable USB connections (click connection settings and tick the box "enable USB connections").
Your RUU programs for HardSPL/Radios/WM6 ROMs should now run as desired once you are synced with WMDC. Since we have updated the driver which Vista uses when the device is in bootloader mode.
NOTE:: This technique is still in testing so if you have any issues please post in the official thread. Until we find another way to get RUU working with vista you may need to revert back to XP for upgrading your Windows Mobile Based Device.
Thanks!
I saw this same article somewhere else and already did this
Thanks for posting this here though! Also, it helps to use the windows mobile device center 6.1 update. It works both on my desktop Vista Ultimate computer and my mom's home premium laptop
Also, a little sidenote, if you want windows mobile device center to display your own phone as the image instead of the standard PDA/PPC Phone/Smartphone image when you sync follow these steps:
Disable USB connections in Windows Mobile Device Center
Uninstall the drivers for your device from device manager
Save the image you want to use as an icon file called sync.ico
Save the icon to the windows folder on your ppc
Disconnect your PPC and enable USB connections again
Wait for the computer to reinstall the device driver and it will sync with the new icon
Sorry, I don't remember who first suggested this. I take NO credit for this whatsoever.
Woooooooooow !!!
dharvey4651
Awesome!
Must say,cudn't have been better than this,commendable job.
zabardast_1 said:
dharvey4651
Awesome!
Must say,cudn't have been better than this,commendable job.
Click to expand...
Click to collapse
Thanks. It took me a while to type up but as long as it benefits the community, it was worth it.
thanks you very much for the write up
great bro, i will add it to TNT notes
works nice, but the Vista update tool is out of date. Cant flash my Wizard with it.
Doesn't work with G4.
neonkoala said:
Doesn't work with G4.
Click to expand...
Click to collapse
Have you tried my tutorial on how to dual boot your computer so that it has Vista and XP on it? I started having problems with my phone not flashing properly after like 2 weeks. I installed a few Windows updates and then the drivers stopped working so I set up my computer to have Vista and XP on it so that I can use Vista on a daily basis and only use XP when I'm working on my phone.
neonkoala said:
Doesn't work with G4.
Click to expand...
Click to collapse
Anybody have found a Vista Update Utility for G4?
Thanks!
This got my G4 to finally stop giving me connection errors in the boot loader!
Now I can finally get my G4 unbricked
I used the shelltool successfully in Vista 32bit, but the world isn't liking me for flashing in 64bit so far... Either way, thanks!
Also, you might want to update the tutorial to tell 64bit users to boot up with driver signing enforcement turned off (Press F8 on boot up) else the 64bit drivers won't take.
frazell said:
Thanks!
This got my G4 to finally stop giving me connection errors in the boot loader!
Now I can finally get my G4 unbricked
I used the shelltool successfully in Vista 32bit, but the world isn't liking me for flashing in 64bit so far... Either way, thanks!
Also, you might want to update the tutorial to tell 64bit users to boot up with driver signing enforcement turned off (Press F8 on boot up) else the 64bit drivers won't take.
Click to expand...
Click to collapse
Thank you very much for that piece of input. I will definitely update the tutorial as per your advice to better assist 64bit users.
Thanks again, Dan.
The Vista RUU doesn't crash as I was used to, but it doesn't run either (with a prophet that is) it 's complaining about "beeing outdated".
Are there any solutions yet known for this inconvenience? Thanks in advance!
Vista RUU
Is there a newer version of the ROM update utility? The one posted above doesn't run, but, rather, just complains that it's out of date!
The driver method detailed above works great (with the caveat for x64 users that they have to disable the driver signing restriction), but unfortunately I'm still no further along because I can't seem to find an RUU that will work!
If anyone knows of one that really works on Vista, please pass it one. (I've searched through all these postings, but none seem to work!)
Thanks much for the detailed driver instructions!
Thanks for the Vista instructions, helps me out! but I ran into a problem degradeing to unlock my CID. Im not sure its me,software,and/or myphone but I got a invalid Vender ID error 294. I am using a wizard 8125 for this and using Vista. This is my first time, but im loaded on knowlaege unless i missed somthing. Thanks in advance.
Still no luck with Vista!
Has anyone found a complete method to flash on Vista? As posted above, the RUU included with this thread doesn't work. It gets most of the way through and then, just before starting to flash, gives a "This utility is out of date" error and exits.
Again, the driver instructions given in this thread are sound, but without a working RUU they only give you half of the solution for flashing on Vista.
I have successfully flashed using Shelltool, but it works sporadically at best.
Does anyone have a start to finish solution?
I followed the instructions given in this forum and they seemed to work perfectly for me.
here is my 2 cents though i had initially flashed my device using the origional t-mobile rom (SPL/IPL 3.08 radio 2.69) and it worked without any problems. It was only when i tried flashing with a cooked rom that it gave me problems.
Here are the RUU file from that rom and hopefully someone can figure out why it worked
Yesterday i had a problem with a Win XP computer where the ADB driver just didn't want to install. The worst part was that on that particular PC it worked correctly some time ago.
After a lot of digging around I've found out that the problem was that somehow the "WDF01005" (which is actually "Microsoft Kernel-Mode Driver Framework Feature Pack 1.5", on some sites it was listed as "KMDF Coinstaller 1.5") was not installed. Of course, searching the net for it didn't get me any closer to a solution.
Anyways, to make a long story short, i managed to fix it by creating the uninstall registry entry for it, it seems that i did have it installed (or maybe i had a newer version installed) all along just that the reg-entry got deleted.
Here's the reg file :
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Wdf01005]
"SystemComponent"=dword:00000001
(just save it into "fix_wdf01005.reg" and double click it to install it with Regedit, or you can add the key manually and add a DWORD value with the name "SystemComponent" and value of 1.)
So, if you ever get the error that Windows XP cannot install the "Android Platform Sooner Single ADB Interface" driver then you might want to see if you have the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Wdf01005" key as it is used by the driver installation and if it's missing then it fails and the driver is not installed.
I hope it helps others too,
P.S. i just tested, it worked for my Samsung phone too, it also failed to install the Android ADB driver and thus the ADB command said "error : device not found", now it worked correctly, it even found the drivers it needed through Windows Update so i didn't have to install anything manually.
Thank you so much! This worked like a charm!
My Windows XP used to work with adb, now it fails to install it.
Then I read this thread and now adb is working happily on my Samsung Galaxy Gio!
Thanks!
Thanks man.
you really helps me a lot.
[sorry for bad english]
instructions for domies...
Can you tell me exactly how do that, please? I'm having the same issue. The file doesn't exist in my registry. How do I get it?
Thanks. You're a blessing.
hi i have not problem with installation in my windowx xp...but its takes too long...i think some time 10 to 20 mins..so is there any way to install adb driver installation fast...plz suggest me solution...thnks and advance
TL;DR: I need update logs or an idea what path might be missing that breaks the 8.1 update!
Hi all, strange for me to be asking for help here but it happens...
I've finally gotten my ATIV S (SGH-T899M) into a state where I'm willing to upgrade it to WP8.1. However, I am unable to do so. I've been able to install a few updates, but the actual 8.1 update won't install. The error I get (under the "Update status" line in Settings -> Phone Update: "The update was downloaded, but couldn't be opened. (80070003)"
The error code is an HRESULT or NTSTATUS wrapper around Win32 error code 3, which is ERROR_PATH_NOT_FOUND. Note that this is distinct from FILE_NOT_FOUND (2); you only get error 3 when a part of the path to a given file (or directory) is missing. I've searched online for any information about this error with regards to updates, to no avail. It does sometimes happen with Windows Updates on PC, but the instructions for resolving that aren't easily mappable to the phone.
Phone's current status:
OS version: 8.0.10532.166 (this is the pre-8.1 version; as I said, I did get some updates)
Firmware revision: 2212.13.11.2 (this is the Samsung GDR 3 version, except modified to not overwrite WP8Diag.xap or FCRouter, etc.; see http://forum.xda-developers.com/showthread.php?t=2537241)
Hardware revision: 15.3.1.0
Radio software: 2212.13.11.2
Radio hardware: 0.0.0.0
Bootloader version: 13.08.14.16
Chip SOC version: 1.5.32
Phone was originally branded for Telus Mobility in Canada, and still has signs of that in DeviceTargetingInfo (language is 0809 instead of 0409, for example, and MobileOperatorName is LUS-CA). It was factory SIM-unlocked and brand new when I got it. It is developer-unlocked, interop-unlocked, capability-unlocked, and has been subjected to numerous additional hacks; I've reversed a few that I can think of which could possibly impact the update (like messing with files in the System32 directory) but I probably missed a few of those.
Here's what happens when I try to update:
If Preview For Developers is not enabled, it does "Checking for updates" then says I'm up to date.
If PFD is enabled, it checks for updates and then, if I'm on WiFi, downloads the update CABs.
It then enters the "Preparing to install" step. This is very slow in some places, stalling for minutes at a time at some percentages, but eventually reaches 97%.
It then stops the update process with the error message in bold above.
It does NOT ever tell me what the update is.
It does NOT reboot, or even offer to reboot, at any point.
The "Check for updates" button re-appears and can be used to start the process over again.
So... any ideas or suggestions? I'd prefer to avoid a hard-reset if possible, simply because of the amount of time it would take to restore the phone to the condition I state I want it in, but I'll do one if nothing else works. Things I'm particularly looking for, in descending order:
1) Anybody else who has experienced this problem and found a solution (and what that solution is).
2) Any log files I could check to see what it was trying to do when the error occurred (ideally with the path that caused the error).
3) Anybody else who has encountered this problem but not gotten past it; we can compare what changes we made to our phones.
4) Anybody else who has a reasonably similarly-modified phone but has not experienced this error and was able to install 8.1 (so we can compare what we did to our phones, and I can possibly crib files off you).
Hope somebody can help! Thanks.
GoodDayToDie said:
TL;DR: I need update logs or an idea what path might be missing that breaks the 8.1 update!
Hi all, strange for me to be asking for help here but it happens...
I've finally gotten my ATIV S (SGH-T899M) into a state where I'm willing to upgrade it to WP8.1. However, I am unable to do so. I've been able to install a few updates, but the actual 8.1 update won't install. The error I get (under the "Update status" line in Settings -> Phone Update: "The update was downloaded, but couldn't be opened. (80070003)"
The error code is an HRESULT or NTSTATUS wrapper around Win32 error code 3, which is ERROR_PATH_NOT_FOUND. Note that this is distinct from FILE_NOT_FOUND (2); you only get error 3 when a part of the path to a given file (or directory) is missing. I've searched online for any information about this error with regards to updates, to no avail. It does sometimes happen with Windows Updates on PC, but the instructions for resolving that aren't easily mappable to the phone.
Phone's current status:
OS version: 8.0.10532.166 (this is the pre-8.1 version; as I said, I did get some updates)
Firmware revision: 2212.13.11.2 (this is the Samsung GDR 3 version, except modified to not overwrite WP8Diag.xap or FCRouter, etc.; see http://forum.xda-developers.com/showthread.php?t=2537241)
Hardware revision: 15.3.1.0
Radio software: 2212.13.11.2
Radio hardware: 0.0.0.0
Bootloader version: 13.08.14.16
Chip SOC version: 1.5.32
Phone was originally branded for Telus Mobility in Canada, and still has signs of that in DeviceTargetingInfo (language is 0809 instead of 0409, for example, and MobileOperatorName is LUS-CA). It was factory SIM-unlocked and brand new when I got it. It is developer-unlocked, interop-unlocked, capability-unlocked, and has been subjected to numerous additional hacks; I've reversed a few that I can think of which could possibly impact the update (like messing with files in the System32 directory) but I probably missed a few of those.
Here's what happens when I try to update:
If Preview For Developers is not enabled, it does "Checking for updates" then says I'm up to date.
If PFD is enabled, it checks for updates and then, if I'm on WiFi, downloads the update CABs.
It then enters the "Preparing to install" step. This is very slow in some places, stalling for minutes at a time at some percentages, but eventually reaches 97%.
It then stops the update process with the error message in bold above.
It does NOT ever tell me what the update is.
It does NOT reboot, or even offer to reboot, at any point.
The "Check for updates" button re-appears and can be used to start the process over again.
So... any ideas or suggestions? I'd prefer to avoid a hard-reset if possible, simply because of the amount of time it would take to restore the phone to the condition I state I want it in, but I'll do one if nothing else works. Things I'm particularly looking for, in descending order:
1) Anybody else who has experienced this problem and found a solution (and what that solution is).
2) Any log files I could check to see what it was trying to do when the error occurred (ideally with the path that caused the error).
3) Anybody else who has encountered this problem but not gotten past it; we can compare what changes we made to our phones.
4) Anybody else who has a reasonably similarly-modified phone but has not experienced this error and was able to install 8.1 (so we can compare what we did to our phones, and I can possibly crib files off you).
Hope somebody can help! Thanks.
Click to expand...
Click to collapse
I've seen this happening with many people. The only way is reset.
Huh. I didn't see any news about it, at all, when I searched. Lots of stories about *other* update errors for WP8.1. Lots of stories about this particular error when installing Windows updates on normal Windows (none of which, sadly, had helpful suggestions for the phone). When you say "many people" do you mean in general, or just lots of people with interop-unlocked ATIVs?
I would really like it if the source of the problem could be identified and fixed, but Microsoft seems unlikely to be helpful here. It's probably a really simple problem - a config file that needs to be edited, a folder created (we can do that), a registry value changed, something like that - but oh well. I can back up my app data, and my SMS are backed up automatically, so I suppose in the big scheme of things there's no reason *not* to do this... I just don't like it, and consider it a waste of time.
On the other hand, if I have to hard reset anyhow, I might take the opportunity to install a custom CSC. I normally try to stick as close to stock ROM as possible - making only runtime changes, basically - but it's quite possible that some of the changes I've made will *already* persist after reboot (part of why I'm hesitant to blindly hard-reset; what if it doesn't fix anything and is just a waste of time?). It would be nice to get some of the feature perks of the custom CSC though.
I had almost the same problem getting the error 80070003.
view those two posts if you are interested
post 217
post 218
Thanks, but that's.. mot actually very encouraging. I have the SGH-T899M, and as far as I know we still don't have a leaked ROM from one of those.
I also got the "Your phone couldn't be updated" message. But the code was: 80188308.
Any takers?
Phone's current status:
OS version: 8.0.10532.166 (with the three xml files....)
Firmware revision: 2216.14.01.2
Hardware revision: 3.19.1.0
Radio software: 1621.14.11.2
Radio hardware: 0.0.0.7
Bootloader version: 13.07.12.14
Chip SOC version: 2.0.15
-tdecision10
GoodDayToDie said:
Thanks, but that's.. mot actually very encouraging. I have the SGH-T899M, and as far as I know we still don't have a leaked ROM from one of those.
Click to expand...
Click to collapse
I've been trying to look into what's going on with the error message.
I found the particular error string within DuErrorsUIRes.dll. IDS_DU_ERROR_PREINSTALL_FAILED.
With that said, the only files that use the DuErrorsUIRes.dll are \PROGRAMS\DUACLIENT\DuaClientSettings.dll and \PROGRAMS\DUACLIENT\DuaNotification.exe.
I'm not good AT ALL with ASM, but you can either grab those files from your phone or grab them from the emu and load them into IDA and track it down.
I know that the code is the 6th code in the list that corresponds with the update error text.
Sorry I'm not able to help much, but hopefully this is of SOME value to you.
Thanks, Snickler. That's an approach I hadn't considered. Since the error code just means "Path not found" I was trying to think of paths it might attempt to access which could, for some reason, be missing from my phone... but working from the other end might work better.
Windows 10 Windows Technical Preview is available for more than a week. Since i have an extra old 40gb hdd for the shift, i decided to give it a try, and i can say that it works perfectly well. Everything works including touchscreen, wifi, bluetooth, modem, etc.
However installing the drivers may be a little tricky. Here are the steps:
1. Download Windows Technical Preview from microsoft website (download the x86 version)
2. Extract the .iso file to a usb stick (i used power iso to do that)
3. Plug the stick to the shift and boot from it
4. Follow on screen instruction to install windows
5. When done copy the drivers for the shift (you have the download link bellow the video ) to a stick
6. First install "VistaECDrvV" in compatibility with windows vista (right click on the file - properties - compatibilty tab- run this program in compatibility mode for: - select windows vista (service pack 2) !! do that for all of the drivers) - restart later
7. Install "TouchScreen"
After installing touch screen driver the touch should work - give a restart
8. Install "Synaptics MicroPad" - restart later
9. Install "shagctrl" ignore the Microsoft .NET Framework missing error - restart later
10. Install "Marvell Wifi driver" - restart later
11. Press the Win+R key combination and type msconfig in the run box and hit enter - switch over to the boot tab, and click on the Safe Boot check box - select minimal -apply -ok - restart
13. With windows booted in safe mode navigate to C:\Windows\System32\drivers right click on "sdbus.sys" -> properties -> security -> advanced -> owner TrustedInstaller click on change -> in the field labelled "enter the object name" type your username -> ok -> apply -> ok -> now back on security tab edit permissions -> click on users -> check all boxes from "permissions for users" tab on allow -> apply -> yes -> ok. Now delete "sdbus.sys"
14. Copy the "sdbus.sys" from the archive that i attached here to C:\Windows\System32\drivers
15. Press the Win+R key combination againg and type msconfig in the run box and hit enter - switch over to the boot tab, and unthick the Safe Boot check box - apply -ok - restart
16. You should have wifi working now - If you cannot find any wifi networks, as it was in my case, go to device manager - right click on the "Marvell sd8686 Wireless LAN SDIO Adapter" (the one without the exclamation mark if you have two) - properties - advanced - from the property box select 802.11D support - on the value box value box select enable. Your wifi should work ok now.
17. Install the "sherry driver 1.3" for the best performance of the video card.
18. That's it! enjoy
What i like most about windows 10 is that it have a "card view" of the running apps just like maemo 5 on noka n900, or the blackberry 10 os. Overall it runs a little better than windows 7 and similar with windows 8.1.
Maybe i will install it as a replacement for windows 8.1 update 1 on the main 120 gb hdd
Here is a small video to see how it runs:
Download HTC X9500 DRIVERS
ryu1 said:
Windows 10 Windows Technical Preview is available for more than a week. Since i have an extra old 40gb hdd for the shift, i decided to give it a try, and i can say that it works perfectly well. Everything works including touchscreen, wifi, bluetooth, modem, etc.
However installing the drivers may be a little tricky. Here are the steps:
1. Download Windows Technical Preview from microsoft website (download the x86 version)
2. Extract the .iso file to a usb stick (i used power iso to do that)
3. Plug the stick to the shift and boot from it
4. Follow on screen instruction to install windows
5. When done copy the drivers for the shift (you can find them on this forum) to a stick
6. First install "VistaECDrvV" in compatibility with windows vista (right click on the file - properties - compatibilty tab- run this program in compatibility mode for: - select windows vista (service pack 2) !! do that for all of the drivers) - restart later
7. Install "TouchScreen"
After installing touch screen driver the touch should work - give a restart
8. Install "Synaptics MicroPad" - restart later
9. Install "shagctrl" ignore the Microsoft .NET Framework missing error - restart later
10. Install "Marvell Wifi driver" - restart later
11. Press the Win+R key combination and type msconfig in the run box and hit enter - switch over to the boot tab, and click on the Safe Boot check box - select minimal -apply -ok - restart
13. With windows booted in safe mode navigate to C:\Windows\System32\drivers and delete "sdbus.sys" and "dumpsd.sys"
14. Press the Win+R key combination againg and type msconfig in the run box and hit enter - switch over to the boot tab, and unthick the Safe Boot check box - apply -ok - restart
15. When booted in normal mode copy the files from the "wififix" archive, that i attached to C:\Windows\System32\drivers and restart
16. You should have wifi working now - If you cannot find any wifi networks, as it was in my case, go to device manager - right click on the "Marvell sd8686 Wireless LAN SDIO Adapter" (the one without the exclamation mark if you have two) - properties - advanced - from the property box select 802.11D support - on the value box value box select enable. Your wifi should work ok now.
17. Install the "sherry driver 1.3" for the best performance of the video card. Search it on google.
18. That's it! enjoy
What i like most about windows 10 is that it have a "card view" of the running apps just like maemo 5 on noka n900, or the blackberry 10 os. Overall it runs a little better than windows 7 and similar with windows 8.1.
Maybe i will install it as a replacement for windows 8.1 update 1 on the main 120 gb hdd
Here is a small video to see how it runs:
Click to expand...
Click to collapse
Thanks alot, I am going to install it now
http://www.mediafire.com/download/c9g6a23223zr3sk/sherry1.3.2betaGMEGSE.rar
Excellent how-to. Clear and precise.
For those who want to perform it: taking a look at ryu1's comment in Post#14 is crucial!
You bring shift to future.
Also an interesting Video- as i see you've only 1GB RAM installed, and nevertheless your Shift runs pretty fast-
faster than mine with 2GB and Win7U.
Network connection, connection to SnapVue... i'm really amazed.
How long does it take to boot, and what about GPS?
Think i'll create a new partition on my 128GB SSD and run Win10 from there.
How large do you think should it be?
B-44 said:
Excellent how-to. Clear and precise.
You bring shift to future.
Also an interesting Video- as i see you've only 1GB RAM installed, and nevertheless your Shift runs pretty fast-
faster than mine with 2GB and Win7U.
Network connection, connection to SnapVue... i'm really amazed.
How long does it take to boot, and what about GPS?
Think i'll create a new partition on my 128GB SSD and run Win10 from there.
How large do you think should it be?
Click to expand...
Click to collapse
Well, i'm sure gps work ok (at least on the windows mobile side) but didn't tested on the windows 10 side.
For booting, i'm sure it take less than 1 minute, but don't know the exact time.
If you want to make a partition for win10, that should be at least 10 gb.
It would be really nice to see how it will run on your shift with 2gb of ram.
Please post the result if you install it
Made 20GB... had been frequently suggested for win8
Now taking a look if I've got a spare usb stick.
Maybe I'm missing something here. On my X9500 I can't get by the error about the 800 MHz processor. Maybe you are on a different model?
Same thing occured with win8 if i recall right... early releases worked fine, and later ones also came up with this problem. (It may have been with BenQ MID S6 instead Shift, I'll try to find out.)
Don't know if there had been some workaround.
As MS is continuously working on it, it may depend on the releases' date.
Mine dates october 20th, but i won't be able to test until next weekend.
If ryu1 doesn't have another idea, it may be useful to share the release he uses.
The processor should always be the same.
edit: Post#86
http://forum.xda-developers.com/showthread.php?t=1264742&page=9
What error are you talking about? i installed windows 8, then 8.1 and now 10 but never got any error about cpu.
Are you sure you didn't download the 64 bit version?
Win 10 Technical Preview lists as a requirement:
Processor: 1 gigahertz (GHz) or faster
Error complained about lower specification.
It was the 32-bit version.
"error" may be the wrong word.
The problem had been discussed in the thread i have linked above.
Again: it may be interesting to know the date of release.
ryu1 said:
What error are you talking about? i installed windows 8, then 8.1 and now 10 but never got any error about cpu.
Are you sure you didn't download the 64 bit version?
Click to expand...
Click to collapse
Maybe i've got it...
in your how-to you say "Plug the stick to the Shift and boot from it".
You mean plug it in, start your shift, enter boot options and select usb stick to boot from, right?
I had prepared my usb stick with powerISO, plugged it in, opened my stick in devicemanager and doubleclicked "Install".
And ran into "your device won't be able to run Win10 because of less than 1GHz".
Maybe this was my mistake, and i won't have this problem when booting from stick.
Will report asap.
That's it..
Just do what daddy told us
(And DON'T use windows installer.)
I haven't finished installation completely,
but right now i must say speed is amazing!
As some drivers are automatically installed to volume "C" i think i'll switch the names of C and X
(the partition i'm installing to), reinstall all drivers and then switch back.
edit: obsolete, win has done it by itself
Sorry for the delay, but i am very bussy these days. Anyway the installation mus be done by booting from usb stick, not via installer.
I have allready installed windows 10 on the main hdd instead of windows 8.1. There are a few things i forgot to mention on the first post, when booting into safe mode to delete the "dumpsd" and "sdbus" files you'll need permission to delete them. Just follow this instructions to change the permission: http://www.askvg.com/guide-how-to-take-ownership-permission-of-a-file-or-folder-manually-in-windows/
That's what i just was about to ask you, as i am stuck at this point...
Will try later and report
Tomorrow.
edit: Think you should for your own sake update your initial post, concerning boot process and rightsmanagement.
Further visitors won't follow the whole thread and'll bomb you with questions.
B-44 said:
"error" may be the wrong word.
The problem had been discussed in the thread i have linked above.
Again: it may be interesting to know the date of release.
Click to expand...
Click to collapse
Oh, by error I meant I received an error message when trying to do the install the way I had tried it. I will read the new information posted here, thanks all.
Finished installation yesterday, everything was fine, quick'n'clean when suddenly wifi stopped working.
Marvell shows error code 10 and winupdate seems to have installed a different adapter.
SD adapter same error.
Had a similar experience when i installed win7, but there i already had a restore point to return to,
and since then everything was fine.
Will make a clean reinstallation, and after adding the wififix disable wifi to avoid possible system updates
and create a basic restore point i can return to each time winupdate kills something.
Preview build 9879
Anyone managed to get the latest build to work. Mine gives a message that my display resolution is too low and stops the upgrade.
Shame really as this works very well on the Shift, and with rumours that win 10 could be free it would have been a good o/s for this computer.
Please post code 0f builtversion.
Build 9860
The games and the launchers were working fine, but then after not playing for few days when I tried opening the Counter Strike: GO, I first noticed that error. Thought restarting would solve the issue and went to play Red Dead Redemption 2. But the next day too there was the same error. Then when I tried starting Steam, there was the same error.
I have tried almost all the mentioned solutions found on the web, except the Clean Installation part, none of them has worked so far. So far have found the errors on all Steam related games and Origin PC related games. Rockstar Games and the launchers work perfectly fine.
As far as I know, I did uninstalled some of the Microsoft Build Tools while installing Visual Studio 2019. This might have caused the issue. But I cannot pinpoint the exact cause.
What I've tried so far
Re-installing all Visual C++ Redistributable from 2005 - 2019
Re-installing Dirext X
Updating the dll files
Running All-In-One Runtime packs (Visual C++)
Checking hard drive for corrupted files with sfc /scannow and chkdsk commands
Device Info: Asus ROG Strix G15 - 533QM, 16 GB RAM, Nvidia RTX 3060, 1 TB nVme SSD, Windows 10 (19044.1415)
I am really sorry if this wrong forum for this.
Have you tried either uninstall steam or origin after uninstall Microsoft visual c++?
Those will reinstall missing components.
not exactly in that order... i will try doing that and inform here... thanks for the suggestion
Ok , Resetting the PC (deleting everything) worked for me... Clean Windows Installation should work too..
This is how to fix Origin error 0xc00007b- unable to start correctly:
Open the start menu and search for ‘CMD’.
Right-click it, and hit run it as administrator.
When it opens, type in: ‘chkdsk c: /f /r’ and hit Enter. Type the command without the quotation.
Type in ‘Y’ and hit Enter again.
Restart your PC.
Once your system has restarted, try to install Origin, or launch it once more, depending on for what this error occurred.
Hope this helps.
{Mod edit: Quoted post has been deleted. Oswald Boelcke}
I re-installed Windows, and that solved the issue for me...
{Mod edit: Quoted post has been deleted. Oswald Boelcke}
yes I did that... I did uninstall and re-install Steam, but that did not solve it... Clean Windows installation did solve it though