Try this:
Extract the installer with any LZMA extractor
From command line, run setup.exe with logging:
setup.exe -log:“C:\path\that\exists” -loglevel:6
Follow through until it errors out, attach the log files.
I am starting to wonder if my NVIDIA was hacked and if there is a virus inside of it.
Perhaps it’s better until you guys figure it out ;)
Also I don’t want to install any corrupted drivers… my system is already in a bad shape lol.
Well I am a bit curious to what the problem could be and what your command does so I will try it if that helps you out diagnose the problem. I already ran it so if there was a virus inside of it then my PC would be already infected. So here goes…
The first time it produced this file: LOG.RunDll32.EXE.log
Now that it’s running the full install this file is gone… perhaps it was deleted.
Anyway, here is another hypothesis/explaination why it might report corruption:
Perhaps the production release installation is conflicting with the release candidate 5.5 which is also still installed. It does show “installer2” not sure if that’s normal.
It’s installing right now… once it’s done I’ll upload the new full logs to a sub folder called: “full logs”.
So far it’s installing… so so far so good. Another hypothesis could be that it simply saw that suspicious file and then aborts installation… Perhaps somebody forgot to delete that file… or perhaps there is a slight problem with the installation.
The CPU is running at 1.0 ghz to prevent any overheat and shutdown during these hot summer days… so it’s gonna take a while ;)
Installation seems to have gone somewhat successfull except it has the same problems as the candidate release. It has issues with shortcuts, and probably visual studio installation links/shortcuts/plugins.
Perhaps I installed visual studio in a different folder but doesn’t seem like it. I do like installing cuda toolkit into a different folder as well… but for now I installed in default folder to try and prevent any problems.
So I think you guys need to figure out the short cut problems. I took some screenshots and uploaded it to my drive to illustrate the problems.
Full installation log and screenshots can be found here… it’s quite large: 12 MB… (I did do some back and forth switching between installation window and textpad editor this causes some more log output):
Another commercial another problem… at least with visual studio 2012…
It can’t find some assembly… problably caused by the shortcuts missing.
I know how to solve this problem… by re-installing nsight individually or so… but this is just to illustrate the problems with the installation package… which should have taken care of all of this.
See problem8.png.
Also trying visual studio 2010… it seems to have the same problem… see problem9.png
Clicking fix it probably don’t help. See problem10.png. Also see problem11.png.
I think all of these problems might be caused by some tool.
This log seems to contain errors relating to shortcuts: LOG.NVCPLSetupInt.exe.log
I am gonna skip screenshotting any other problems… cause it’s getting out of hand… I don’t want my webdrive to end up with all these screenshots… so by now it should be clear what the problem is.
Perhaps that tool is conflicting with my VHD images… one image is being used as temp storage… but not sure if that is the problem. I think C:\temp is being used and not the vhd image. Might have to check path variables ;) vhd image/virtual disks… might have write permission problems. It seems to claim “out of space” in some logs… that might be causing the tool to fail or it’s another problem with the tool. setup was run from ms-dos prompt without administrator priviliges… which could also be a problem… access was given as needed… perhaps the tool needs to ask for administrator permissions first.
