|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by mark876543 in Windows XP Operating System, Microsoft Operating Systems, Microsoft Windows Operating Systems
My system runs clean with no virus. It is a raid-0 pair for the C drive. Win XP. I want to multtiboot to a SATA drive for testing. Using Acronis Trueimage I restore my good working C image onto the test drive. If I leave the original C drive unplugged, everything works fine when booting to the test drive. No viruses!! Please do not post links saying that this error message is caused by virus! The problem begins as soon as I have reconnected the original raid pair and am booting to the test drive. Windows sees the "new" hardware and installs it. Shortly after reboot, I get the dreaded svchost error-close message then things start locking up. Looking at the error details it mentions G:......svchost.exe. The G drive is the original C drive. Windows is getting confused as soon as it sees the original C drive. Probably there is some type of drive identifier that's the same since it was sort of cloned. I used to multiboot without this trouble. I know I could fix it by rebuilding from scratch on the test drive, but the whole point is to avoid all that trouble. For some reason Windows is partially looking at the original drive even though I said boot to the test drive. Maybe it's something they screwed up in SP3, I don't think it used to do that.
20091111-EE-VQP-89 / EE_QW_2_20070628