Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - jpm

Pages: 1 [2] 3 4 ... 7
Sorry for the delay - was out of town.

If you run msconfig and select the boot tab … then click "base video" it should boot correctly in safe mode.

The program pulls form system variables for the reparse points so you should be fine - however spreading the system over three drives is different and I would maybe not use the reparse point feature going forward.  We can however fix them manually if there is an issue.

if you boot into windows and run 'msconfig' there is an option to select "safe boot". Click that and reboot and you should come into safe mode.

The tweaking program also has an option to force safe mode.

Those are normal errors and can be ignored.

Right. I believe that errors out if the folder / file / whatever is already there or permissions are wrong.  If the roaming is working fine than you can just ignore that.

the last update of the repair program fixes some rather tough update issues. Try those repairs and see if it helps.

Open the program, click Backup tools.  On the registry backup line, the last button is the options Click that, then the settings tab and click the schedule button. That should do it for you.

Next to the load picture button is a gear button. Click that for settings and you can set it to print left.

Its a permissions issue on your computer.  Basically you need to verify that the directories needed were created and if not create them . Then verify that the permissions are set to full for those directories.

You should not compress files in the system32 folder. Most likely those files are locked and that is why they are not compressing.

36 Support & Help / Re: Codejock.Controls error
« on: May 30, 2018, 05:46:35 pm »
Either the antivirus is sandboxing the control or the control is not in the program folder. Can you look in that folder and see if it is there?  Likely you have a bad download and should reinstall.

37 Support & Help / Re: C: drive is now an X: drive
« on: May 30, 2018, 05:10:09 pm »
I removed your name and phone number - you shouldn't do that. :)

Ok. first there is absolutely nothing in the program at all that can change the boot drive.

If you are in windows It's hard to say why windows did this - but it did it prob because of the image you made OR that the original system had a x: backup partition.

but this is the fix

If you are in the dos window from the rovery enviromen t - the dribve letter assigment may be normal.

How are you getting to the dos window?

There may be a security issue where you can't run certain programs in the  system32 directory. (some antivirus apps will do that to protect hijacks.)

go to C:\Windows\System32\osk.exe. and copy the osk.exe to another folder and see if it works.

If so, just make a short cut to the new copy and you should be fine.

The program cannot delete data - except the file cleaner.  What is missing?

That looks and smells like a driver problem.

Did you notice this after you updated a set of drivers? If so uninstall and revert.

General Computer Support / Re: Windows Installer - Error 2203
« on: April 15, 2018, 07:46:10 am »
There is most likely a problem with the permissions of your %Temp% folder. Giving SYSTEM modify permissions should fix that.

Can you navigate to the folder and see if perhaps it is checked read only?

 :evil: LOL  :evil:

I'm on it

No - looks like an error from the inference.

You don't need to reboot the machine, just retsrt the program.

Are you sure the checkbox for "change log location" is selected?

Jeez, this thread seems to be getting personal and surprisingly argumentative.

All I did was tell you my position.    I value my privacy a lot.

Not, the latest update of the MS virus checker did not fix the install.   

I actually don't care.  I just passed on my own thought process about why I was unwilling to whitelist the program.  And I am taken aback that you think there is something that is wrong with that.

But again, I don't care.  It's not worth my time to deal with it.  I still can't use Tweaking even though it's the only program in my computer that stopped working. And yes, I still believe that it is not my responsibility to deal with the clash between MS and Tweaking.  Tweaking represented itself as working closely with Microsoft, but obviously it isn't.  Again, after updating MS and Tweaking, it still doesn't work.  And honestly I don't care because this was never personal for me, just something to chat about.   Bye. Rani

It may have been read personally but I didn't intend it so. I agree with you. As an end user it is not your worry to get involved - it's our problem.

My issue with the whole "false positive" industry. This crap happens all the time and although Tweaking is always clean when someone sees a detection from a Microsoft is always will hurt our rep, weather we are right or wrong.

If you click the information window - it should show you where that error is being generated.

49 Support & Help / Re: Windows Run/RunOnce Registry key
« on: March 29, 2018, 01:53:39 pm »
It isn't really needed to run every time you start but if you like follow this:
Press the “Win + R” key combination;
 Enter: “shell:Startup” , without quotes in the boox and click enter. The start up folder will open.

Open a new exploer window and go to C:\Program Files (x86)\\Windows Repair (All in One) and right click on Repair_Windows.exe -- choose copy.

Then go back to the start up folder and right click to "paste shortcut"/ On the nex t boot it will start.

LOL --- Told ya it was better to pour a Guinness than to deal with this. :)

Yeah - we have a new version due to. Should be a fun week.

Pages: 1 [2] 3 4 ... 7