Error when installing software

[Robert Johnson]

Today, when trying to re-install some software which I
had recently uninstalled, I couldn't get to "first
base." The only response I get is the following error
message:

"The Win16 Subsystem was unable to enter Protected Mode,
DOSX.EXE must be in your autoexec.nt and present in your
PATH."

I have checked the contents of AUTOEXEC.NT, and there is
a Load High command for autoexec:

lh %SystemRoot%\System32\dosx

So the first part of the error message would seem to be
not the problem. What I don't know is where to look for
(or correct) the PATH problem. Any help would be greatly
appreciated, for I fear that this will not be the last
time I run into this error message if it goes uncorrected.

TIA

Sam

 

[Michael Solomon \(MS-MVP Windows Shell/User\)]

Were you ever able to install this software in XP or was it installed on a
previous setup which you upgraded to XP? I'm assuming this is DOS software?

 

[Robert Johnson]

Actually, the program is a windows program which was
previously installed under WinXP. The problem is that
the installer for the software is started by a 16-bit
app, which is why I can't get to first base. Since I
posted the original message, I have restored (from the XP
installation disk) both the DOSX.EXE and HIMEM.SYS
files. (MS says corruption of one or both of these may
cause this problem) and have checked the AUTOEXEC.NT and
CONFIG.NT files agains the versions on the XP
installation disk. They match. After doing all that, I
rebooted. The problem persists. Hope you can help.

 

[Michael Solomon \(MS-MVP Windows Shell/User\)]

The reason I asked the question is because 16-bit subsystem is generally
associated with DOS apps but many older Windows apps, pre-Windows 95 apps,
fall into that category.

Again, I'm not clear, when you say it was previously installed under XP, are
you saying you installed it under XP and had no problems with the
installation or that it was already installed when you upgraded to XP?
Under the assumption you did previously install it under XP, my guess is
that some updates or other such changes have changed the environment enough
to push this application over the edge. It was likely always borderline and
how ever the environment has changed since you first installed it was
probably enough to start causing problems.

Aside from the program compatibility wizard, there's not much else I can
offer. Start\All Programs\Accessories\Program Compatibility Wizard. Beyond
that, I'm sorry, I don't have an answer for you, perhaps someone with
experience with this type of application and issue will know how to resolve
it.

 

[Robert Johnson]

Michael,
First, I should have stated clearly that XP was a clean
install on a new machine. The application, which is
Visioneer's scanning software, is XP-compatible and was
purchased new with the scanner after I found my old
scanner would not work under XP. My guess is that the
software uses the 16-bit install program to make it
backwards-compatible with older versions of Windows. I
have seen this same error message not too long ago (can't
remember what I was trying to install.) It's
frustrating, since this very same error is catalogued by
Microsoft with directions on how to correct it. Only
problem is, the directions do not correct it. The
original installation (under the clean install of XP)
went off without a hitch. If I had hair, I would be
tearing it out!!

 

[Robert Johnson]

Michael,
Guess I've managed to postpone the impact by finding a
workaround for this particular instance: went to the
Visioneer web site, downloaded their current version of
the driver software, then installed THAT copy! This
package doesn't use the 16-bit installer, so it worked
perfectly! I now have all the same old capability I had
before. Thanks for trying to help; I have no doubt that
I will run into this problem in the future with some
other software package -- or maybe not, as long as I only
use brand-new software. Again, thanks for your help.

Sam

 

[Michael Solomon \(MS-MVP Windows Shell/User\)]

Okay, things are more clear. Have you checked the Visioneer site for
updated software. Scanner software bundles can be a real pain. If they
don't have upgraded software, see if they have updated drivers and instead
of installing all the software, try just installing the drivers and using
XP's scanner and camera wizard.

I can't say I've run into this with scanners released for XP but I have seen
it with 9x scanners. Unfortunately, while the manufacturer's will often
update the drivers that will make the scanner compatible with a different
OS, they don't always have control over the software.

I agree with your premise and given the scanner was XP compatible the
software should work so I go back to the possibility the environment has
changed enough to push the software over the edge.

On other possibility that occurs to me is there might be a conflict with
something else installed on your system, hardware or software. That,
however, would take some digging. If you can think of anything you might
have installed that wasn't on the system when you first installed the
scanner, you might try removing it and see if that resolves it. If not,
then it's a trial and error situation meaning you'd have to start removing
items one by one and testing to see if you could install the software after
each removal; hence, my first suggestion is to check the Visioneer website
for later versions of that bundle, assuming they've released any. You might
also contact Visioneer tech support as they may have some insight or a work
around. If they have a knowledge base and/or some other tech papers at
their site, you might check those as well.

 

[Michael Solomon \(MS-MVP Windows Shell/User\)]

LOL, I must be psychic, I just posted that suggestion to you!

Glad you got it worked out!