- Thread Author
- #1
Hi.
Been using Windows 7 Beta and on release date downloaded Win 7 RC through Technet.
Using it as my primary OS until er... well today.
I have a logitech 4000 webcam, I plugged it in and without fail the RC grabbed the files from the web and installed the camera. However there was no control of the camera outside of an app that uses it, such as MSN live messenger or skype etc.. So I grabbed the installation files to the quickcam studio on the logitech site for Vista x64 (assumed this was the closeset match).
Program would run and unzip but before installation would say "this product is not designed for your OS" and it would promptly quit. I decided to emulate Windows Vista x64 with SP2 in this case and ran the program with admin rights. This proved to be quite a major disaster, to say the least. As the application tried to install it ran through normal procedures but in very slow time. Every time the installer tried to do something to the system, various applications would crash and cause memory page fault errors saying the memory couldnt be read.
This affected regedit, the windows fault logging / reporting utility, the login GUI menu system, wdm,exe and quite a few various other critical executable files. The installation did not complete, by this time I was a bit worried about all the constant errors so powered off the machine and turned it back on.
Windows 7 RC now actually boots, but all the files mentioned and more must be utterly corrupt. Upon logging in the screen goes to black, the circular mouse cursor just spins conintuously and over the period of about 5 minutes various critical services and executables die on their asses with the message about memory not being able to be read.
Whilst I can see that this is my fault and I can't really lay blame with the OS for this happening I'm a little distrubed at the options I have presented to me when trying to recover the system.
I booted off the DVD and hit "repair my system". The auto check assumes everything is perfectly fine as it says the OS "Booted last time around" and that's where it stops checking, even when all the critical system files are absoultely stuffed. I managed to get a command prompt up and ran a thorough chkdsk on the installation drive and it found 0 errors. I tried to go back to the main installation prompt for Win 7 and there is no "repair" feature.
Now this boggles my mind, back in the days of XP you could run the recovery console, but better still you could enter the installation process again and point the installer at the partition / installation of windows. It would then go off and verify/copy back over all the system files it believed to be corrupt or otherwise, thus restoring windows back to normal without any issue at all.
7 years on an 2 iterations of Windows later and as far as I can see this feature has been totally removed.
The automatic "check my system and repair it" functions seem to be totally useless if vital system files corrupted and there doesn't seem to be any choice at all to run a repair of this fashion? The only thing left for me is an option that says to install windows to the same partition where the existing installation will be renamed as Windows.old, which I REALLY do not want to do.
Am I missing something here?
Can someone set me straight and tell me how the hell I'm supposed to recover the system with these tools?
They seem completely useless to me.
PS- I have no system restore points to revert to, I feel I shouldn't have to rely on system restore points when there should be an option to repair like XP had...
Paul
Been using Windows 7 Beta and on release date downloaded Win 7 RC through Technet.
Using it as my primary OS until er... well today.
I have a logitech 4000 webcam, I plugged it in and without fail the RC grabbed the files from the web and installed the camera. However there was no control of the camera outside of an app that uses it, such as MSN live messenger or skype etc.. So I grabbed the installation files to the quickcam studio on the logitech site for Vista x64 (assumed this was the closeset match).
Program would run and unzip but before installation would say "this product is not designed for your OS" and it would promptly quit. I decided to emulate Windows Vista x64 with SP2 in this case and ran the program with admin rights. This proved to be quite a major disaster, to say the least. As the application tried to install it ran through normal procedures but in very slow time. Every time the installer tried to do something to the system, various applications would crash and cause memory page fault errors saying the memory couldnt be read.
This affected regedit, the windows fault logging / reporting utility, the login GUI menu system, wdm,exe and quite a few various other critical executable files. The installation did not complete, by this time I was a bit worried about all the constant errors so powered off the machine and turned it back on.
Windows 7 RC now actually boots, but all the files mentioned and more must be utterly corrupt. Upon logging in the screen goes to black, the circular mouse cursor just spins conintuously and over the period of about 5 minutes various critical services and executables die on their asses with the message about memory not being able to be read.
Whilst I can see that this is my fault and I can't really lay blame with the OS for this happening I'm a little distrubed at the options I have presented to me when trying to recover the system.
I booted off the DVD and hit "repair my system". The auto check assumes everything is perfectly fine as it says the OS "Booted last time around" and that's where it stops checking, even when all the critical system files are absoultely stuffed. I managed to get a command prompt up and ran a thorough chkdsk on the installation drive and it found 0 errors. I tried to go back to the main installation prompt for Win 7 and there is no "repair" feature.
Now this boggles my mind, back in the days of XP you could run the recovery console, but better still you could enter the installation process again and point the installer at the partition / installation of windows. It would then go off and verify/copy back over all the system files it believed to be corrupt or otherwise, thus restoring windows back to normal without any issue at all.
7 years on an 2 iterations of Windows later and as far as I can see this feature has been totally removed.
The automatic "check my system and repair it" functions seem to be totally useless if vital system files corrupted and there doesn't seem to be any choice at all to run a repair of this fashion? The only thing left for me is an option that says to install windows to the same partition where the existing installation will be renamed as Windows.old, which I REALLY do not want to do.
Am I missing something here?
Can someone set me straight and tell me how the hell I'm supposed to recover the system with these tools?
They seem completely useless to me.
PS- I have no system restore points to revert to, I feel I shouldn't have to rely on system restore points when there should be an option to repair like XP had...
Paul