



*** Instructions to get the Microtek SMII scanner to run under Win-OS/2 ***

If you have a Microtek ScanMaker II and you're running OS/2, chances are you've either  a)  used
a SCSI interface dedicated to your scanner,  b)  rebooted to MS-DOS to do your scans,  c)  become
very frustrated,  or  d)  All of the above.

If you're like me, you purchased several months ago and have impatiently awaited a twain solution. 
Microtek says they don't support OS/2.  IBM says they will perhaps write twain drivers soon -
they've apparently learned the Microsoft "virtual software95" trick.  Right now today IBM might
support some of your other devices but it's a better chance they don't support the components you
need to know the most about.  Your SCSI adapter manufacturer tells you a few CONFIG.SYS
switches (if you're lucky) and then if it doesn't work, they tell you to buy an HP scanner.  Solution
Technology says they will make a twain driver for the Microtek, but don't know when.  Perhaps you
should buy a Logitech or HP scanner.  You can purchase Impos/2, but then you don't have twain
support and up until about six months ago it wouldn't work with Microtek anyway.

Then last months issue of OS/2.  You've seen these kinds of documents before - little snippets of
help that just might work.  They didn't.  But this time - maybe - will they shed some light?

No.  They just tell you to buy something besides a Microtek.  Where were our brains when we
bought the Microtek?  But alas, I see every other scanner is very troublesome.  Flip a few
CONFIG.SYS switches and some of the stuff works some of the time on Tuesday evenings provided
your CompuServe account is current.  The article might as well said nothing works right.  Just forget
it and buy something else.  You got a ton of money, go out and get new stuff.

OK.  So now here are some concrete answers.


First - Download Microtek ScanWizard 2.3 from CompuServe.

Microtek recently made ScanWizard 2.3 available for Win16 and Win32.  Their 16 bit version is
capable of running under Windows95.   Hmm.

ScanWizard 2.0 is usually bundled with Microtek scanners and will not run properly under
Windows95, but this new version will.  It has to survive preemptive multitasking techniques and
doesn't take liberties with its modes of accessing devices.  One guy at a time, please.

So download ScanWizard 2.3, disks 1, 2 and 3 from CompuServe.  You don't need disk 4 because
its only used on Win32 systems.  Install ScanWizard 2.3 from Win-OS/2.


Second - Change CONFIG.SYS:

a)  Turn off DASD and SCSI manager support for the scanner on your SCSI adapter device driver. 
Examples (if your scanner is SCSI ID # 6):
     Adaptec 1542 Controller
  BASEDEV=AHA154x.ADD /V /A:0 /!DM:6 /!SM:6
     AMI Series 70 Caching Controller
  BASEDEV=AMI0OS2.ADD /V /!DM:6 /!SM:6

b)  Make sure you have MS-DOS ASPI support.  Example uses drive "X:", change to your OS/2
drive.

  DEVICE=X:\OS2\MDOS\VASPI.SYS

This line should be in CONFIG.SYS somewhere.  All *.sys files are loaded AFTER *.add drivers,
so it doesn't need to be listed after the OS2ASPI.DMD statement.  But if you're adding the line,
might as well make it be the line immediately after OS2ASPI.DMD.  While you're there, make sure
that you have OS2ASPI.DMD.  If not, put it in somewhere after the SCSI controller device driver
and OS2DASD.DMD.

  BASEDEV=OS2ASPI.DMD

c)  Search your CONFIG.SYS for a line that reads IOPL=YES or IOPL=NO.  Make sure it says
IOPL=YES and if there isn't such a line, then add it.  It should be somewhere around the BUFFERS,
DISKCACHE, TIMESLICE and THREADS statements.  If you add the IOPL line, a safe place to
put it is right after the BUFFERS statement.

d)  You may want to increase the size of your swap file because scanned images are very large.  A
max size of 64Mb wouldn't be at all unreasonable.  The following example puts a 64Mb
(swapper.dat) swap file in the \XYZZY directory on the D: drive and tells OS/2 to warn you if the
D: drive ever gets within 8Mb from being full.

  SWAPPATH=D:\XYZZY 8000 64000

e)  When you installed ScanWizard 2.3, it made an entry for Windows HIMEM.SYS as the first line
of your CONFIG.SYS file.  Remove this line.


Third - Change AUTOEXEC.BAT

ScanWizard 2.3 installed a reference to ASPIIF.EXE as the last line in your AUTOEXEC.BAT file. 
This line should be retained, but you may want redirect messages from it to a null file.  This will
keep you from seeing "ASPIIF installed OK!" every time you start a MS-DOS session.

  C:\WINDOWS\TWAIN\SCANWIZ\ASPIIF.EXE > NUL


Fourth - Configure your SCSI adapter for proper communications with the scanner

The Microtek ScanMaker II scanner must run asynchronous mode at 5Mb/sec.  Sometimes it can
be run faster, but it must be run asynchronously.  Make absolutely certain that your SCSI card has
the scanner channel set for 5Mb and asynchronous negotiation.

Using the AMI Series 70 caching controller, MS-DOS ASPI drivers work OK at the higher speed
when used with ScanWizard 2.0, but the improved performance of the AMI0OS2.DMD,
OS2ASPI.DMD and VASPI.SYS drivers won't let you get away with the higher speed.  ScanWizard
2.0 under Win-OS/2 will simply "outrun" the scanner.

ScanMaker 2.3 performance has improved enough that the scanner can't communicate at the higher
rates under MS-DOS or OS/2 drivers if the interface isn't set for 5Mb async.

On the Adaptec 1542 or the AMI Series 70 EISA caching controller, you can set the speed and
communication mode for each channel individually.  On cards that allow individual channels to be
set, it is usually accomplished with a configuration utility (i.e. ECU.exe).  Some cards can only have
one speed for all channels and if this is the case the board must be set for 5Mb async to get the
scanner to work.


Fifth - Verify the scanner firmware is Rev. 5.11 or higher

If your SCSI adapter device driver is set in verbose mode (/V switch), it will display the scanner
firmware revision when it loads.  This will also verify that you have established communication with
the scanner.  If you have CONFIG.SYS set as previously shown and the scanner had power before
the system had power and the scanner channel is set at the proper speed and your terminators are
right and you've read the book, lit the candles and rung the bell - all in the proper sequence - then
you will connect to the scanner at boot time and your device driver will report all the connected
devices, their sizes (if media) and their revision level.

If your scanner isn't Rev.5.11 or higher, contact Microtek and have them send you a ROM. 
Shouldn't cost much and besides we've already established that you have a zillion dollars during our
discussion about frustration with scanners.


Sixth - Shutdown the system.  Power up the scanner and then the system.

You've probably brought it up and down a few times.  You probably also thought I was just being
funny when I said to bring up the scanner before the system in that stuff about reading the book,
lighting the candle and ringing the bell.

Nope.  You've got to POWER UP THE SCANNER BEFORE YOU POWER UP THE CPU.

I know it's counterintuitive to bring up a peripheral device before you bring up the processor -
something like turning on the arms and legs before attaching the brain - but in this case if the SCSI
card doesn't sense the scanner ID at boot-up, it won't provide info to the higher level drivers that
anything is there.  Don't worry, the processor won't send any strange data during power-up that sends
heads out over a platter while it's spinning too slow to load and give you this terrible screeching
sound like twenty  school children scratching their fingernails on a chalkboard...

After you've started OS/2 and connected to the scanner, you can turn it off.  As long as you have
connected during system load, you can shut off the scanner and not lose your ASPI "connection". 
If you forget and attempt a connection while it's off, just turn it back on and let it come ready.  Exit
the twain application and restart it.  You will be able to reconnect.


Seventh - Set up the Microtek "Quickpanel" Launchpad

The Microtek Quickpanel is a launchpad application that you will probably want to put on your
OS/2 desktop.  It allows you to easily use your scanner to make printed copies, disk file copies, fax
the scanned image or launch a graphics application.  When you press a button on the Quickpanel,
your chosen event is started and the scanner automatically makes a scan and passes it to the
application, printer or FAX.

To set up the Quickpanel, make a program object for it on the OS/2 desktop by choosing "create
another" in the properties section (right mouse click) of an existing program.  Set this new program
to C:\MICROTEK\QP\QP.exe and have it use Win-OS/2 enhanced mode with at least 32Mb DPMI
available.

 Alternately, you can enter Windows and launch Quickpanel from the Program Manager.  If you
choose this method, make certain that your Windows session has been set for enhanced mode and
has at least 32Mb DPMI available.

Launch the Quickpanel and after it has loaded, click on the "button" in the upper left corner of the
Quickpanel launchpad.  Select "Command Wizard"

a)  Set up the printer you want to use for printed copies.  Select the COPY icon and choose your
printer in the "output device" field.

b)  Set the scan mode using the icon that looks like a boat paddle near the "Scanning Setting" field. 
Choose the desired scan size, resolution and quality.  This is the twain mode and there are not
individual settings for every application - it's a "one size fits all" deal.  In fact, if you run a paint
program or something outside of the Quickpanel and change the twain setting, this change will be
used on all subsequent scan operations.  Whatever twain is set for, that's what your scanfile is.  Of
course, it can always be changed.

A good generic scan mode is 300dpi, 8.5 x 11.0 inches, and "Line Art" (which is two color B/W). 
This is a good mode for making black and white copies and FAX's and it's quick.  Don't set it for
"millions of colors" (24bit 16.7M colors) unless you're a patient person.

c)  To use the FAX, you will need to make changes to your Windows WIN.INI file.  I should have
told you this way back when you were editing CONFIG.SYS, shouldn't I?  Well, just think of how
frustrated you've been with everything you've done before today.  And look at how far we've gotten
this time.  And considering the price of admission, you can probably forgive the small
inconvenience of editing your WIN.INI file at this point.

Make changes to the following sections by adding or changing the lines listed in the example below. 
You will be adding a FAX entry in your [ports] section and listing the FAX driver in the
[PrinterPorts] and [devices] sections.

If you are using SofNet FaxWorks (bundled with OS/2 Warp), then you are probably using the
FaxWorkD virtual printer device driver. Your new FAX settings in the [PrinterPorts] and [devices]
sections should have similar entries as those installed by the SofNet FaxWorkD device driver.

     [ports]
     FAX:=

     [PrinterPorts]
     FAX=proprn24,LPTx.OS2,15,45

     [devices]
     FAX=proprn24,LPTx.OS2

In the [PrinterPorts] and [devices] sections, add "FAX=" entries the same as your FaxWorkD device
driver.  They are probably set for "IBM Proprinter XL24e" and LPT2.OS2 or LPT3.OS2.  You can
retain both the Proprinter and the FAX entries and have them set for the same LPT device.

You may find that FaxWorks installed these or similar entries for you.  Newer versions of FaxWorks
Pro or the FaxWorks bundled with OS/2 may make the changes to WIN.INI.  I'm running FaxWorks
1.39 purchased in 1993 or '94 and it's happy not even knowing that Windows ever existed.

Once you have made these changes to WIN.INI, you can set up the FAX application in your
Quickpanel launchpad.  You will need to exit Windows and restart for Windows to "see" the
WIN.INI settings - either by running a new instance of Windows or by rebooting OS/2.  The
Windows "FastLoad" session will not incorporate the WIN.INI changes until you reboot OS/2.

If all went well, the FAX section of the "Command Wizard" in the Quickpanel should now read
"FAX on LPTx.OS2".  If it doesn't, it should so there.

d)  Setting up a disk file for file copies simply requires you to choose a filename to store the scanned
image.

e)  The clipboard option should be set to "Device Dependant Bitmap" (as opposed to Independent). 
You might want to make the clipboard public in your Win-OS/2 settings in the OS/2 System folder. 
This will allow any OS/2 or Win-OS/2 session to have access to your clipboard image from the
scanner.

f)  Set up applications by choosing the application program EXE and the data file to store the
scanned image.

Use UPDATE to save your settings for each individual Quickpanel icon.  That's another thing I
should have told you before.  Oops.  But I think it asked if you wanted to save changes, didn't it? 
See, I meant to do that.  Anyway, DUPLICATE will let you create new icon buttons to assign
applications to.  You can set the icon graphic to any valid ICO file and set the application program
to any valid EXE file.  Doesn't make much sense to set things that aren't twain applications though. 
This will allow you to launch any of your twain compliant paint and OCR programs using the
Quickpanel launchpad.

This concludes our test of the emergency broadcasting system.  If this had been an actual
emergency, you would have been instructed exactly where, in your area, you should go.



Configuration instructions and valuable information provided by:

Wayne Parham
Parham Data Products
P. O. Box 702006
Tulsa, OK 74170
(918) 663-2131 voice
(918) 663-3044 fax
74224.2176@compuserve.com
http://ourworld.compuserve.com/homepages/ParhamDataProducts/homepage.htm

Visit our Web page to download FREE programs!



Smart mouthed comments and misinformation provided by:

Someone else