Okay, just installed Creator's Update

Jonathan N. Little wrote:

The problem is for this scanner there is no WAI only TWAIN, and
apparently with 1703 the WAI to TWAIN bridge is gone. BTW, 1604 wasn't
A1-skippy either because the TWAIN didn't work with my Corel Photo-PAINT
I had to do my scanning in Irfanview, but with 1703 does not show in
selecting TWAIN sources. Yet it does show in settings Printers &
scanners... and Manage button works. Just cannot access it from any
programs.

Someone had a problem here with TWAIN, where the
path to it was missing from the $PATH variable.
But that's dated November 2016, which corresponds to
one of your "it works" intervals.

https://www.tenforums.com/drivers-ha...in-source.html

I'm just surprised I'm not finding any modern reference
to changes made in Creator on this. You would think if
they were trashing something, there would be a warning
posted somewhere. And, written in Plain English, not something
we'd need to read between the lines to detect.

In their example, the driver is in

C:\Windows\Twain32\CNQ4803

and yours is probably similar to that.

Paul

Paul wrote:

https://www.tenforums.com/drivers-ha...in-source.html


I'm just surprised I'm not finding any modern reference
to changes made in Creator on this. You would think if
they were trashing something, there would be a warning
posted somewhere. And, written in Plain English, not something
we'd need to read between the lines to detect.

In their example, the driver is in

C:\Windows\Twain32\CNQ4803

and yours is probably similar to that.


C:\Windows\twain_32\CNQ4200

Well I got it working back in IrfanViewer. I had to reinstall
IrfanViewer for some reason. shrugs

My 32-bit version of Photo-PAINT still hangs, but that is on Corel.
Their tech support gave up on a fix...ain't proprietary software the
greatest? And people scoff at OpenSource...

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

Jonathan N. Little wrote:
Paul wrote:

https://www.tenforums.com/drivers-ha...in-source.html



I'm just surprised I'm not finding any modern reference
to changes made in Creator on this. You would think if
they were trashing something, there would be a warning
posted somewhere. And, written in Plain English, not something
we'd need to read between the lines to detect.

In their example, the driver is in

C:\Windows\Twain32\CNQ4803

and yours is probably similar to that.


C:\Windows\twain_32\CNQ4200

Well I got it working back in IrfanViewer. I had to reinstall
IrfanViewer for some reason. shrugs

My 32-bit version of Photo-PAINT still hangs, but that is on Corel.
Their tech support gave up on a fix...ain't proprietary software the
greatest? And people scoff at OpenSource...


I made the mistake of buying Corel once, and the answer
was always "fixed in the next release".

Paul

On 4/17/2017 4:07 PM, Leala wrote:
This works on Win10.

http://8gadgetpack.net/

My previous program worked with Win10 also, at least a previous version
of it.

Yousuf Khan

On 4/17/2017 3:02 PM, Yousuf Khan wrote:
Okay, just installed Creator's Update, and though it looks more or less
the same, one thing different is that the Desktop Gadgets are no longer
working. I had installed a program called "Windows Desktop Gadgets" on
the machine under Anniversary Update, which brought back all of my
Windows 7 desktop gadgets. But now that's not working at all. I still
see the option for Gadgets when I right-click the desktop, but selecting
it does nothing.

Yousuf Khan

Okay, found the solution: simply uninstall the program, and reinstall
it. It looks like everytime there is a major Windows 10 update, it
resets big swathes of the Registry to default. So reinstalling the
program changes some of those Registry settings back to the way they were.

Yousuf Khan

Yousuf Khan wrote:
On 4/17/2017 3:02 PM, Yousuf Khan wrote:
Okay, just installed Creator's Update, and though it looks more or less
the same, one thing different is that the Desktop Gadgets are no longer
working. I had installed a program called "Windows Desktop Gadgets" on
the machine under Anniversary Update, which brought back all of my
Windows 7 desktop gadgets. But now that's not working at all. I still
see the option for Gadgets when I right-click the desktop, but selecting
it does nothing.

Yousuf Khan

Okay, found the solution: simply uninstall the program, and reinstall
it. It looks like everytime there is a major Windows 10 update, it
resets big swathes of the Registry to default. So reinstalling the
program changes some of those Registry settings back to the way they were.

Yousuf Khan

I don't pretend to understand how the migration logic
works on Windows 10.

Remember, that the OS keeps a huge cache of .msi files
from when programs are installed. When you go to Programs
and Features, and Uninstall or Repair a program, those .msi
can be brought into play.

On one Windows Insider upgrade, my Logitech webcam software
popped up on first boot, as if I had just installed it. Suggesting
that maybe the .msi for it got executed at some point, and it
was re-installed. Later versions of Win10 Insider no longer
did that, so they figured that one out.

I don't know to what extent portions of the registry are
just copied, or, programs are installed fresh. For a lot of
programs, if you uninstall them and reinstall them, user
preferences are preserved. So even a program uninstaller, doesn't
remove everything. And they could be uninstalling and reinstalling
using .msi files, making it look like nothing had changed.

If the gadgets don't use a standard install mechanism, there
are two ways they could go missing. They could be blocked,
like an installed copy of CPU-Z could be (reason - hardware
access driver of some sort). Or the package doesn't lend itself
to migration. In your case, it could very well be the latter.

And you can still use CPU-Z, it just doesn't migrate.

Some things are more actively black-listed (mechanism, unknown).
You would not expect VPC2007 or Windows Virtual PC to run on
Windows 10 (even though in a perfect world, they should).
These are approximately 16MB downloads, if you want to test
them today and see what the current response is. The
hypervisor type used in the Windows 10 era, probably plays
a part in outlawing them. They would not be compatible
with Hyper-V. And even if you don't have Hyper-V hardware
(no SLAT/EPT), I would still expect VPC2007 to be blocked.
VirtualBox works, because the VirtualBox staff are chasing
after Microsoft, week after week, keeping their package
in a usable state. Many times, you go to start VirtualBox
on Windows 10, and it won't start. Installing an update version
of it, gets the latest changes and fixes that (issue resolution
has always been fast). The developer log for VirtualBox will
mention changes to kernel files or the like, which means
the VirtualBox developers keep having to change their stuff
so it can co-exist.

I'm sure somewhere, there's an explanation of how the
lengthy migration portion of an Upgrade works, but I've
not run into it yet.

Paul