Main Forum > Tweaking.com Support & Help

Log file

<< < (2/3) > >>

Shane:
On the root of the Windows drive (Normally C:) you will see a tweaking.com folder  :wink:

Shane

MarkAtHome:
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).

Shane:
The problem looks at the system variable for the drive that Windows is on and puts the logs on that drive :wink:

Shane

MarkAtHome:

--- Quote from: Shane on February 05, 2013, 11:14:13 am ---The problem looks at the system variable for the drive that Windows is on and puts the logs on that drive :wink:

Shane

--- End quote ---
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?

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

Navigation

[0] Message Index

[#] Next page

[*] Previous page