On Sun, 9 Aug 2015 09:17:15 -0400, "Mayayana"
wrote:

SaveProfileUsingICM
It doesn't help if you spell the function name wrong.

I agree, it doesn't. My apologies. My only excuse is that it was
written in fine grey text on a charcoal background.

I'm not an expert on this, but for what it's worth:

1) It seems to be trying to delete an old copy
and running into a bug in the software.
Maybe a dummy file of the same name would
satisfy that.

When all this started it was trying to delete an existing copy of
Dell U2410-1.icm but no success. I tried renaming the profile it was
trying to save to (say) Fred.icm and had no success with that either.

2) Could the ICM file be saved elsewhere and then
just copied into the folder?

I've got no access to or control over the software which determines
where it is trying to save(
C:\Windows\System32\Spool\drivers\color\...

3) Presumably you have a 64-bit version of the
software? 32-bit that's 64-bit-unaware might
try to save to System32 and fail. (Against all
common sense, System32 is the 64-bit folder
on Win64.)

I've been running Spyder 4 (where the problem started) on 64 bit
Windows for years with no problem.

4) If you think permissions are the issue you can
"take ownership" of the folder and then give
yourself permission. And/or start the program
with elevated permissions. (right click option)

I've done all that.

"net user administrator /active:yes" only makes
the real admin account visible at boot. You would
then need to log in with that account to be a real
admin.

Understood. Administrator under Windows 7 is not a fully empowered
Administrator unless you do as above.

I quickly got fed up with that convoluted nonsense
when I started to work with Win7 and ended up
writing a simple program to *really* free up any
file/folder:
http://www.jsware.net/jsware/nt6fix.php5#restfix

THat's interesting and useful, but I shouldn't have to resort to that.
I'll hold off for the time being.

It's free. You're welcome to it. If you're queasy about
3rd-party software look up CACLS and Takeown. Those
are command line options that can do the same thing
my software does -- just with more work. I *think*
the same can be done manually but the restrictions
mess is so convoluted I've never been able to quite
figure that out for certain.

Then there are the 'special' permissions, some of which are weird.

I wonder about permissions if the software used to
work. On the other hand, if you're enabling Windows
Update without carefully checking exactly what each
patch is doing then all bets are off.

The information provided by Microsoft is usually obscurely brief.

It seems very odd that the people writing the software
have no ideas, but that may be a case for a 3rd-party
factor. Those things can be very hard to track down
because they're unexpected by nature. Though I suppose
you could try killing any process related to Adobe, printer,
etc before you do the operation. That wouldn't hurt.

I'm just about at that stage. A problem is that running a calibration
to get a file to save takes several minutes so the cycle is slow.

Ron Hardin's idea of Process Explorer (sysinternals.com)
is good in general, though if you're trying to write a
file that doesn't exist it can hardly be locked by another
process.

I haven't tried yet and right now I have to go out and pick up my
chain saw. :-)
--

Regards,

Eric Stevens