A lot of netizens in the process of installing Vista, the blue screen will appear when restarting, the reason is very simple: no SATA driver is loaded.
Originally this type of problem is to modify the hard disk settings in the BIOS, set the hard disk to compatibility mode, without Archi mode. As a result, friends on the Internet said that they couldn't fix it. After research, it was originally possible to manually add SATA drivers and registration information to the Vista temporary directory from XP after the installation was restarted.
First of all, our central idea is to manually add our own disk controller driver (nonsense) in the Vista installation directory. This requires 2 steps to complete:
1. In the temporary installation directory of Vista, place our own driver file.
2, add our own driver key value in the Vista registry. (Mao Chairman Education teaches us: Be kind to people, you secretly add a large number of documents under the directory of people, how to inform people: Hello, Vista~~ even in your directory, add even baby files, installed Remember to add it even! If you miss a ~~, then you will die to see it.)
Ok, with the theoretical foundation, we will act!
Normally install Vista under XP until the first reboot, blue screen after reboot (normal -_-". Re-enter XP to operate.
No.1: Put your own disk The driver files are copied to the relevant location in the Vista temporary directory.
Specifically: *.sys files are placed in windows\\system32\\drivers in the Vista temporary directory, *.inf and other files are put into Vista temporary Windows\\inf in the directory.
No.2: How to modify Vista's registry? We need to use the current XP system's registry database as a temporary place to operate. Just create a temporary folder: I The location is under c:\
aid. Then open the registry, find all the key values of the driver you want to install in XP and save all of them in the file sata.reg. Copy sata.reg to c:\\ Under raid.
Then create a new text file a.txt in the raid folder. Open a and add the following content (//after my words do not need to write):
if not exist system Goto end
copy system system.bak //back up system file
reg load hklm\\hk97sys system //Write the contents of the system file to Hkey_LOCAL_MACHINE\\hk97sys, hk97sys is a temporary new key.
regedit /s SATA.reg //will sata Add the value of .reg to the current registry and save the system file.
reg unload hklm\\hk97sys //Remove the hk97sys key value added in the current registry.
Browse //Let you See the result oh~
:end
Save a.txt after writing and rename it to a.cmd. Ready to operate. Will the windows in the Vista temporary directory The file named system under \\system32\\config is copied to the c:\\sata directory. (Why should I copy the system file? Because that stuff is the location of the registry database.)
Execute a.cmd. If the prompt is successful, copy the current system file back to its original location to overwrite the original file. So we will add our own driver information to the Vista registry.
Shut down and restart the computer to enter the Vista installation. Program, if there is no blue screen, congratulations! . (I have succeeded in pulling halfway here!)
Continue to install the program. The second automatic restart. After rebooting - blue screen! Quickly analyze the cause, N brain cells agree that it is still a driver problem! The original work was only to deal with Vista's installer. However, the system files of Vista on the hard disk are now copied from the Vista installation CD! (The installation CD is not included!) Not the stuff in the previous Vista temporary directory. . .
It’s easy to know the reason, let’s reapply. Only this time the object is no longer a temporary directory for Vista. It is the disk where the Vista system is located (even in the E disk, everyone changes according to their own situation).
No.1: Copy your own disk driver files to the relevant locations in the Vista system directory.
Specifically: *.sys files are placed in E:\\windows\\system32\\drivers, *.inf and other files are placed in E:\\windows\\inf.
No.2. Copy the file named system under E:\\windows\\system32\\config to the c:\\sata directory. Execute a.cmd. If the prompt is successful, copy the current system file back to its original location to overwrite the original file.
Shut down again to restart the computer and enter the Vista installer. If there is no blue screen, congratulations! . (I’m successful here!)
Then? Then wait for ~~~ for 20 minutes, then the Vista system will appear in front of you!
Problem: Vista system crashes when it starts to scroll bar, scroll bar can not ent
The launch of Vista RC1 has raised expectations for a new generation of operating systems. Although
This article describes how to disable autoplay in Windows Vista, and no longer pops the autoplay dia
Windows Vista uses the product serial number—or key, Product Key, CD Key, and fut
Unlocking other Windows systems to upgrade Vista
Adjust the number of frequently used programs under VISTA
Regaining space from Windows Vista system recovery
Set stereo mix recording method under Vista
In-depth experience of Windows Vista 5472 operating system new features
Modifying the text size under Vista causes the text in the program to be incompletely resolved.
*.theme and *.msstyles type Vista desktop theme guide
Vista crack method depth summary (currently a total of 7 methods)
New file right-mouse vista system restore folder options disappear right mouse
Solution for Scanning Fax Problems in Vista System
Repairing Vista with Startup Repair
The whole process of installing the virtual machine under Vista system
What should I do if the win 10 system cannot be activated and restarted automatically?
How to create the Win10 system taskbar toolbar?
Windows XP Say goodbye to the first anniversary of countdown
Problems that should be noted after closing Windows XP automatic update
How to set up win7 sharing? Win7 system settings LAN sharing tutorial
Win7 Permissions Get Win 7 Management Permissions
Last year, 13% of Windows/IE security patches were played. No overall ratio
Four reasons lead to the emergence of "virtual memory is not enough"