I'd appreciate one of the gurus taking a look at the problem reported in detail here. Four days since I lost use of an ancient but much loved
program (PaintShop Pro 8), and running out of ideas to recover it.
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/paintshop-pro-8-suddenly-will-not-run/2e1409a9-0615-4877-ad84-ff4be4c8a489?rtAction=1723114654048
Terry, East Grinstead, UK
I'd appreciate one of the gurus taking a look at the problem reported in detail here. Four days since I lost use of an ancient but much lovedIf you have so many mfc42 dlls lying around, I understand that the wow64 is a dupe for reasons, but
program (PaintShop Pro 8), and running out of ideas to recover it.
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/paintshop-pro-8-suddenly-will-not-run/2e1409a9-0615-4877-ad84-ff4be4c8a489?rtAction=1723114654048
Terry, East Grinstead, UK
On 8/8/24 10:02 AM, Terry Pinnell wrote:
I'd appreciate one of the gurus taking a look at the problem reported inIf you have so many mfc42 dlls lying around, I understand that the wow64 is a dupe for reasons, but
detail here. Four days since I lost use of an ancient but much loved
program (PaintShop Pro 8), and running out of ideas to recover it.
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/paintshop-pro-8-suddenly-will-not-run/2e1409a9-0615-4877-ad84-ff4be4c8a489?rtAction=1723114654048
Terry, East Grinstead, UK
I'd think a lot of the others a simply not used. I'd look at your PATH variable and are any of
those 'dupes' in those paths? You could more them aside temporarily.
I'd appreciate one of the gurus taking a look at the problem reported in detail here. Four days since I lost use of an ancient but much lovedCreate a new Windows profile and try to run your App. It might just run
program (PaintShop Pro 8), and running out of ideas to recover it.
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/paintshop-pro-8-suddenly-will-not-run/2e1409a9-0615-4877-ad84-ff4be4c8a489?rtAction=1723114654048
Terry, East Grinstead, UK
I'd appreciate one of the gurus taking a look at the problem reported in detail here. Four days since I lost use of an ancient but much loved
program (PaintShop Pro 8), and running out of ideas to recover it.
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/paintshop-pro-8-suddenly-will-not-run/2e1409a9-0615-4877-ad84-ff4be4c8a489?rtAction=1723114654048
Terry, East Grinstead, UK
On 08/08/2024 15:02, Terry Pinnell wrote:
I'd appreciate one of the gurus taking a look at the problem reported inCreate a new Windows profile and try to run your App. It might just run
detail here. Four days since I lost use of an ancient but much loved
program (PaintShop Pro 8), and running out of ideas to recover it.
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/paintshop-pro-8-suddenly-will-not-run/2e1409a9-0615-4877-ad84-ff4be4c8a489?rtAction=1723114654048
Terry, East Grinstead, UK
in a new/fresh windows profile. By Windows profile I mean create a new
local account on your machine.
G/L
On Thu, 8/8/2024 10:02 AM, Terry Pinnell wrote:
I'd appreciate one of the gurus taking a look at the problem reported in
detail here. Four days since I lost use of an ancient but much loved
program (PaintShop Pro 8), and running out of ideas to recover it.
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/paintshop-pro-8-suddenly-will-not-run/2e1409a9-0615-4877-ad84-ff4be4c8a489?rtAction=1723114654048
Terry, East Grinstead, UK
Libraries can be loaded from multiple places, as far as I know.
A local instance of a library (in the Program Files) could override a system instance.
I do not know the details of the decision tree for that (the search order).
Using Procmon, could show the loading process, and where the
code was coming from. You start ProcMon running, just before
you try to open PSP8.
https://learn.microsoft.com/en-us/sysinternals/downloads/procmon
A filter using ReadFile and CreateFile, will help display
the relevant parts and cut out some of the noise. The tool
likes to record everything, then you filter to display
the things you want or like. The capture tick box in
the FIle menu (hard to read), stops capture when you believe
the event desired, has occurred, and now it is time to analyze it.
You may have "abandoned hope" too quickly. A Repair Install
may have removed some of your MFC42 instances (Repair Install by running >setup.exe off the mounted Win10 ISO9660). But you really
need to check whether any MFC42 instance is in the PSP8 Program Files
storage area. And the Process Monitor (procmon.exe or procmon64.exe)
run, will help document for you, what it is trying to load.
The "Jump To" function in Process Monitor, should help open the
File Explorer folder to the relevant place, when you see an instance.
Program Files is owned by TrustedInstaller. You cannot replace a
file in there, while in Windows. You could do it from Linux, EXCEPT
if "new style compression" reparse point is applied to something.
This typically prevents a user from working in System32 via Linux.
It is possible to globally disable compression, and stop that from
happening. You could use fsutil to stop compression, just before
a Repair Install, for example. And that may help reduce the amount
of material which is inaccessible to humans.
fsutil behavior set disablecompression 1 # disable (at least) new compression, on all drives.
# You can still compress with 7Zip or WinZip of course.
# This setting refers to NTFS compression.
There used to be a way to elevate yourself to TrustedInstaller,
but MSFT broke it. That's why I can no longer tell you how
to do that.
Paul
Thanks Jack, I hadn't tried that. I'm usually put off by the thought
that, if the problem does *not* occur, what then?
On 8/8/2024 9:02 AM, Terry Pinnell wrote:
I'd appreciate one of the gurus taking a look at the problem reported in
detail here. Four days since I lost use of an ancient but much loved
program (PaintShop Pro 8), and running out of ideas to recover it.
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/
paintshop-pro-8-suddenly-will-not-run/2e1409a9-0615-4877-ad84-
ff4be4c8a489?rtAction=1723114654048
Terry, East Grinstead, UK
PSP 9 still works OK for me. Hope you get it figured out.
On 8/9/2024 5:49 AM, Terry Pinnell wrote:
Thanks Jack, I hadn't tried that. I'm usually put off by the thought
that, if the problem does *not* occur, what then?
Indeed. It's become standard advice with Windows, Firefox,
etc to just create a new profile, but that can be a vast job.
I was having trouble with Firefox the other day. I wondered
whether it could be malware. First it couldn't reach anything online,
but other software could. Then it kept running after it was closed.
I tried re-installing. I tried updating. Nothing helped.
No, I didn't create a new profile. It would take hours to get
the new profile up to speed and then it would just be the same
as the old profile, anyway!
Finally I tried disabling my 4 extensions. That worked. Why did
the problem happen so suddenly? I have no idea. Though I had
noticed that it seemed to be taking longer to reach websites.
So I updated the extensions and now it's fine. I don't expect to
figure it out.
I once wrote a program that wouldn't start. It turned out that it
was quitting as soon as it opened. With filemon and regmon (the
earlier, more sensible versions of procmon) I finally figured out that
I was enumerating printer fonts at startup and no printer was
connected. When I switched to enumerating screen fonts it was
fine.... But something suddenly going south without any system
changes is more mysterious.
For what it's worth, I'm running PSP5 on Win10. No glitches. I
also have PSP16, but Corel made that one and they made a
bloated mess of it. So unless I need to do something like work
with RAW format I usually just stick with PSP5.
On Thu, 8/8/2024 10:02 AM, Terry Pinnell wrote:
I'd appreciate one of the gurus taking a look at the problem reported in
detail here. Four days since I lost use of an ancient but much loved
program (PaintShop Pro 8), and running out of ideas to recover it.
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/paintshop-pro-8-suddenly-will-not-run/2e1409a9-0615-4877-ad84-ff4be4c8a489?rtAction=1723114654048
Terry, East Grinstead, UK
Libraries can be loaded from multiple places, as far as I know.
A local instance of a library (in the Program Files) could override a system instance.
I do not know the details of the decision tree for that (the search order).
Using Procmon, could show the loading process, and where the
code was coming from. You start ProcMon running, just before
you try to open PSP8.
https://learn.microsoft.com/en-us/sysinternals/downloads/procmon
A filter using ReadFile and CreateFile, will help display
the relevant parts and cut out some of the noise. The tool
likes to record everything, then you filter to display
the things you want or like. The capture tick box in
the FIle menu (hard to read), stops capture when you believe
the event desired, has occurred, and now it is time to analyze it.
You may have "abandoned hope" too quickly. A Repair Install
may have removed some of your MFC42 instances (Repair Install by running >setup.exe off the mounted Win10 ISO9660). But you really
need to check whether any MFC42 instance is in the PSP8 Program Files
storage area. And the Process Monitor (procmon.exe or procmon64.exe)
run, will help document for you, what it is trying to load.
The "Jump To" function in Process Monitor, should help open the
File Explorer folder to the relevant place, when you see an instance.
Program Files is owned by TrustedInstaller. You cannot replace a
file in there, while in Windows. You could do it from Linux, EXCEPT
if "new style compression" reparse point is applied to something.
This typically prevents a user from working in System32 via Linux.
It is possible to globally disable compression, and stop that from
happening. You could use fsutil to stop compression, just before
a Repair Install, for example. And that may help reduce the amount
of material which is inaccessible to humans.
fsutil behavior set disablecompression 1 # disable (at least) new compression, on all drives.
# You can still compress with 7Zip or WinZip of course.
# This setting refers to NTFS compression.
There used to be a way to elevate yourself to TrustedInstaller,
but MSFT broke it. That's why I can no longer tell you how
to do that.
Paul
As you're another 'legacy' user, I'd be interested to hear if you've
found an alternative since Corel closed down their PSP community forums?
As reported earlier, I now thankfully have PSP 8 running again.
But I'm still baffled by the proliferation of files with the same name.
On 14/8/2024 at 16:09 I made an arbitrary edit in PSP8 and saved it. A
search of my C: drive shows there were 13 files of that name accessed.
Some of them a mere 1KB.
https://www.dropbox.com/scl/fi/qg1ej3jvc2c22kuwab3fo/MFC42-DLL-ManyVersions.jpg?rlkey=x90aan72xtn998khgyl9xk9lj&raw=1
Terry, UK
On Thu, 8/15/2024 3:34 PM, Terry Pinnell wrote:
As reported earlier, I now thankfully have PSP 8 running again.
But I'm still baffled by the proliferation of files with the same name.
On 14/8/2024 at 16:09 I made an arbitrary edit in PSP8 and saved it. A search of my C: drive shows there were 13 files of that name accessed.
Some of them a mere 1KB.
https://www.dropbox.com/scl/fi/qg1ej3jvc2c22kuwab3fo/MFC42-DLL-ManyVersions.jpg?rlkey=x90aan72xtn998khgyl9xk9lj&raw=1
Terry, UK
C:\Windows\servicing\LCU is Last Cumulative Update. This is a folder that allows
your Patch Tuesday to be rolled back.
C:\Windows\WinSxS is the side-by-side maintenance tree. It keeps more than one
version of library. "Things" are hard-linked from here.
C:\Windows\SysWOW64 is a version of the file actually in use :-) C:\Windows\System32 is a version of the file actually in use :-)
Notice how WinSxS has two files which are hard-linked, into those last two directories.
The files have the same size. The rest of the files are a "supporting cast of characters".
You can delete the contents of LCU. It could have a couple folders in it.
You could toss those in the trash, and all that does (side-effect) is not being able to roll back. There can be 200,000 files in LCU.
You can delete the contents of LCU. It could have a couple folders in it.
You could toss those in the trash, and all that does (side-effect) is not
being able to roll back. There can be 200,000 files in LCU.
Does Windows' Disk Cleanup remove these system files?
On Fri, 16 Aug 2024 04:44:43 +0000, ant@zimage.comANT (Ant) wrote:
You can delete the contents of LCU. It could have a couple folders in it. >>> You could toss those in the trash, and all that does (side-effect) is not >>> being able to roll back. There can be 200,000 files in LCU.
Does Windows' Disk Cleanup remove these system files?
I tried deleting these once. Win10 refused to boot. I restored from a
Macrium backup.
I believe Disk Cleanup manages these so I just leave them alone.
Does Windows' Disk Cleanup remove these system files?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 361 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 123:30:50 |
| Calls: | 7,716 |
| Files: | 12,861 |
| Messages: | 5,727,956 |
