"P" <thomaspz@_takeout_bigpond.com> wrote:
> You seem to be getting close to solving my problem. I have Acrobat Pro
> 9.3.4 (with this week's latest security update).
> I have a Dell Optiplex 980 with an Intel i7 processor.
> The scanner is a Microtex x12. Now I know that is a few years old but I
> have the latest driver and it worked well before with Win XP and Acrobat
> 8. I have contacted Microtex support and they suggest the problem could be
> with Acrobat. I now suspect it is with Windows 7. The trouble occurs when
> I try to access the scanner via Acrobat by using the "Create PDF > from
> scanner > Select device ... " Then the DEP closes Acrobat.
I would be highly suspicious of the TWAIN drivers in that case. They are
the responsibility of the scanner vendor, not Adobe. I've used Acrobat with
an HP scanner with DEP enabled in the OS and had no problems, although in my
case it's XP and not Win7.
> Can you tell me how to change the DEP settings - you mention four states
> but I cannot find that. I get to the DEP tab in Advanced System Settings
> and there are only 2 options. It will not allow me to add acrobat.exe to
> the list. There is nothing else on the list.
There should be no need to add Acrobat to the exclusion list; my shop has
been running with DEP set to OptOut for some time and the current versions
of both Reader and Acrobat have run without problems on either XP or Win7.
(I can't say if it's been tested against TWAIN drivers on a Win7 platform,
but the shop has significant use of Acrobat and I'll be surprised if someone
with a Win7 system hasn't at least tried scanning. I own the Win7 system in
our shop and would probably have had heard of any problems from our ~8000
engineers if someone had run into problems.
OTOH, Google shows some reports about problems on Vista when using Acrobat
with DEP enabled, but the ones I looked at don't provide much detail or
followup.
Is there an event log entry for the failure?
Is it possible that somehow your system has been changed to set DEP to
"AlwaysOn"? As I mentioned upthread many, many programs (including some
only-slightly-not-recent versions of InstallShield) die if DEP is AlwaysOn.
Open an elevated command prompt, then in the command window type the command
BCDEDIT
with no parameters (case-insensitive; shown here in CAPS for clarity).
Here's typical output from a 64-bit Windows 7 system:
=====
Windows Boot Manager
--------------------
[deleted; not relevant here]
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {e5efa91a-6f68-11df-8a6d-000c29969504}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {e5efa918-6f68-11df-8a6d-000c29969504}
nx OptOut
=====
Note the last line: it shows that the system is running in OptOut mode. If
it's set to AlwaysOn, change it with the command:
BCDEDIT /SET NX OPTOUT
Expected output:
=====
C
>bcdedit /set nx optout
The operation completed successfully.
C
>
=====
Reboot to complete the change.
Other valid values for the last token are AlwaysOff, AlwaysOn, and OptIn.
Warning: if you're using dual boot you'll need to be much more familiar with
BCDEDIT's convoluted syntax but the example above should be appropriate for
a standard installation. In all cases (XP/Vista/7) you can see the
currently-active DEP setting in the Registry (rebuilt at each boot):
HKLM\SYSTEM\CurrentControlSet\Control[SystemStartOptions]
On my 64-bit Win7 Enterprise box that's a REG_SZ string:
NOEXECUTE=OPTOUT
Joe Morris
