Noobcomputermaker
New Member
- Joined
- May 17, 2006
- Messages
- 445 (0.07/day)
Processor | AMD Opteron 165 Denmark 2592.7 MHZ ht 2.59ghz dual core |
---|---|
Motherboard | DFI Landparty Nf4 SLI-DR |
Cooling | 2 case fans heatsink/fan for cpu: Zalaman |
Memory | OCZ 2GB (2 x 1GB) 184-pin DDR SDRAM DDR 400 (PC 3200) |
Video Card(s) | Gigabyte geforce 7600gt 256MB GDDR3 PCI EXPRESS x16 SILENT PIPE II/ LEAD FREE |
Storage | SEAGATE BARRACUDA 7200 250 GB |
Display(s) | SAMSUNG 204B-Black Black 20.1" 5ms LCD Monitor with Height, Pivot, Tilt Adjustments |
Case | Thermaltake SHARK VA7000BWA Black Aluminum ATX Full Tower Computer |
Power Supply | Antec NeoPower NeoHE 550 ATX12V 550W |
Software | Windows xp Home sp2 |
Alright I am still having an issue with installing Bootcamp.
First I solved the "boot camp x64 is unsupported"
1. Right click computer
2. Select manage
3. Select Local Users and Groups
4. Select Users Folder
5. Double click administrator
6. Uncheck Account is disabled
7. Apply
8. Log off, then log on as Admin.
Now I have a new Issue with getting the following message during Boot Camp install
"A system restart is pending. Complete the restart and then retry this installation."
Solution : http://pc-mac-linux.blogspot.com/2008/11/restart-pending-with-bootcamp-drivers.html
My only problem is after I follow the steps in that solution, which involve :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager and delete or rename the PendingFileRenameOperations
In Regedit I go to that specific address and this value date is always coming back into the PendingFileNameOperations registery file:
Value Data: \??\C:\Windows\NV37603704.TMP\nvsvc.ini
Everytime I start bootcamp I have to install a nvidia driver off the start, usually there are always restarts with nvidia drivers, could this be why it always says there is a pending restart?
If i could figure out why that Value data keeps coming back, i can fix it and finally install the bootcamp drivers.
Thanks guys
Edit: I have confirmed that it must be the bootcamp installation itself that is causing the Value data, I have deleted the value in the reg file, restarted, checked the registery, no PendingFileNameOperations, then i tried installing Bootcamp64 again, Nvidia installed a driver, then it went back to boot camp, then The restart is pending message came back. So I checked the registery again, and the Value data is back. How do I fix this when bootcamp itself is causing it?
First I solved the "boot camp x64 is unsupported"
1. Right click computer
2. Select manage
3. Select Local Users and Groups
4. Select Users Folder
5. Double click administrator
6. Uncheck Account is disabled
7. Apply
8. Log off, then log on as Admin.
Now I have a new Issue with getting the following message during Boot Camp install
"A system restart is pending. Complete the restart and then retry this installation."
Solution : http://pc-mac-linux.blogspot.com/2008/11/restart-pending-with-bootcamp-drivers.html
My only problem is after I follow the steps in that solution, which involve :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager and delete or rename the PendingFileRenameOperations
In Regedit I go to that specific address and this value date is always coming back into the PendingFileNameOperations registery file:
Value Data: \??\C:\Windows\NV37603704.TMP\nvsvc.ini
Everytime I start bootcamp I have to install a nvidia driver off the start, usually there are always restarts with nvidia drivers, could this be why it always says there is a pending restart?
If i could figure out why that Value data keeps coming back, i can fix it and finally install the bootcamp drivers.
Thanks guys
Edit: I have confirmed that it must be the bootcamp installation itself that is causing the Value data, I have deleted the value in the reg file, restarted, checked the registery, no PendingFileNameOperations, then i tried installing Bootcamp64 again, Nvidia installed a driver, then it went back to boot camp, then The restart is pending message came back. So I checked the registery again, and the Value data is back. How do I fix this when bootcamp itself is causing it?