Tweaking.com Support Forums
Main Forum => Tweaking.com Support & Help => Topic started by: etaf on January 21, 2013, 05:49:36 am
-
Just ran the program on my vista PC to see how it worked out
and wondered is there any log file of changes made at all ?
thanks
-
Which program? I have over 30 on the site lol
Shane
-
Thanks , sorry about that
Windows Repair (All in One) v1.9.6
-
It only creates log files of any errors. As for what each repair does there is info on each repair in the program. You can also read each of them in the program folder under repairs_info :wink:
Shane
-
Thanks - I had some failed info on the screen
It only creates log files of any errors
where are the log files put ?
thanks for thehelp
-
On the root of the Windows drive (Normally C:) you will see a tweaking.com folder :wink:
Shane
-
Ah, so that's where the logs are. Briefing looking at them, please consider checking the registry and/or environment for folder locations, before running a module that requires them to exist on a specific drive (e.g. "C"), when they have already been moved (e.g. "D")... Using system variables would require much less effort. :wink:
Note that I only ran a couple of them to see what they might do, and I do occassionally move folders originating on Drive-C to/from Drive-D, etc., depending upon my current storage configuration, and testing (SSD vs HD, pertaining to apps being looked at).
-
The problem looks at the system variable for the drive that Windows is on and puts the logs on that drive :wink:
Shane
-
The problem looks at the system variable for the drive that Windows is on and puts the logs on that drive :wink:
Shane
Gotcha. So if I am following you, you only access the SYSTEMDRIVE variable, rather than all variables provided by the DOS/CMD SET command, yes?
-
Each batch file I have it set like this
"set path=%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem"
The program pulls its own system variables from the API
sWindowsDriveLetter & "\Tweaking.com_Windows_Repair_Logs\_Windows_Repair_Log.txt"
Shane
-
Each batch file I have it set like this
"set path=%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem"
The program pulls its own system variables from the API
sWindowsDriveLetter & "\Tweaking.com_Windows_Repair_Logs\_Windows_Repair_Log.txt"
Shane
There are a lot more variables than that... :wink:
What do you do with %programfiles%, %ALLUSERSPROFILE%, and especially %APPDATA%? Don't forget %CommonProgramFiles%, %CommonProgramFiles(x86)% and %CommonProgramW6432% -- these could be on a drive other than "C".
I know that it is your program and you can do with it as you see fit. Personally, I do not favor programmers hardcoding file locations, but it is certainly your call.
-
What do you do with %programfiles%, %ALLUSERSPROFILE%, and especially %APPDATA%? Don't forget %CommonProgramFiles%, %CommonProgramFiles(x86)% and %CommonProgramW6432% -- these could be on a drive other than "C".
Those are for use in bat files, which my program uses those when needed. There are also API's that my program pulls the information from that the program needs, not the bat files. Those commands dont work in program code there is also no command for bat files to simply pull the Windows drive, it will pull the folder but not the drive, you have to use the system API to pull them. Right now the program pulls the API to pull the Windows folder location. From that it can see what drive letter it is on and for now puts the log files on the drive that the Windows folder is on.
I plan on adding more options down the road as the program has become rather popular and I am getting a lot of request for things. So the program is still growing :-)
Shane