Messages

1

Tweaking.com Support & Help / Re: Can't use pro without connection

« on: February 11, 2022, 10:13:49 am »

I wasn't looking for a refund, this software is EXCELLENT!

Yes, he replied to my mail with the same answer. I continued to ask if this will work with an older version of the portable and he replied that it would.

2

Tweaking.com Support & Help / Can't use pro without connection

« on: February 11, 2022, 02:09:04 am »

I find it very frustrating (and unfair) that I can't use my pro version without an internet connection, because the software can't "verify" my code.
Occasionally, the reason I use the software is that I don't have an Internet connection and want to use the software to fix the problem.
It's true that there is a "Fix Network" without the pro, but it seems unfair that at that time I cannot use the software that I paid for with the pro features.

Please tell me if there's something to do about this.

3

Tweaking.com Support & Help / Re: Over 17 hours and still repairing

« on: January 28, 2018, 04:52:51 am »

Ok, did that. Ran the other checks also in safe mode. All seems to be fine now. Thanks!

4

Tweaking.com Support & Help / Over 17 hours and still repairing [SOLVED]

« on: January 27, 2018, 10:35:44 pm »

I'm running a repair that says "THIS MAY TAKE A LONG TIME... STOPPING THIS PROCESS BEFORE IT IS FINISHED CAN CAUSE PROBLEMS"
My question is, how long should I wait? For the past 17 hours it's been stuck on "Step 1 of 3 - Repairing WMI...."
Yes, the CPU usage is active so I guess it IS responding and not completely frozen, but is 17 hours normal for step 1?
The C drive it's repairing is a 500GB SSD.

Please advise what to do.

5

General Computer Support / Re: Unable to create the log file path

« on: May 28, 2014, 11:56:17 pm »

Yes, the code seems ok. No, it does not end up creating the log file.

It actually states:

Code: [Select]

DirPath [in]

    A valid path name. If the final component of the path is a directory, not a file name, the string must end with a backslash (\) character.

Maybe you need to add the back-slash like this?

MakeSureDirectoryPathExists(sLogPath &"\")

Just a thought.

If it were MY code (or open source) I'd add (just to test) the GetLastError function, hoping to get more info on the error. I would also debug using a breakpoint at that function and use F8 to step into it.

Anyway, thanks for the reply!

6

General Computer Support / Re: Unable to create the log file path

« on: May 27, 2014, 11:52:41 pm »

I had already tried different log paths on different drives and am getting the same result. Like I said, it actually DOES run the fixes, even after the warning, so I did all the fixes that have to do with taking ownership of drives and registry - hoping that this was causing the error message - restarted the computer and tried again but got the same error message. Attached are the shots.

p.s. yes, the computer is in Hebrew but as you see in the screen shot, the log path I set has no unicode in it. Also, even if it did, I have the "Language for non-unicode programs" set to Hebrew so that shouldn't be the issue.

7

General Computer Support / Unable to create the log file path

« on: May 27, 2014, 01:34:13 am »

I have no issues about unicode but right before the repairs I get a warning that the repairs won't be repaired because Program is unable to create the log file path. Who cares if it can't create logs? I don't mind to do the repairs without the log! I even ran a "Take ownership" script on the log location and it's NOT read only.