Jethro said:
Good Good Grief Grief man man!! :<)
I DID a FULL C drive scan in Windows Explorer for UMAXUSD2.INF and it
did not show up under Windows or anywhere else other than where I
said. So, obviously, this must be my problem. Since my install,
using vssetup.exe, did not place that inf file there - then I have to
discover why it did NOT.
<<snip>>
I found a post containing a response from UMAX. I figured I'd
copy it to USENET, so it could be archived for future generations.
******
WELL, WEEKS later, I get a response from Umax.
Here is how the scanner is supposed to work with WinXP.
Quote:
Windows XP and FireWire Installation
If you do not have the VistaScan CD then you can download the software
from the website at
http://www.umax.com/download/. Be sure and save
the files in My Documents.
RESTART IN SAFE MODE AND YOU HAVE TO BE LOGGED IN AS ADMINISTRATOR
Uninstalling VistaScan
1. Left click on Start.
2. Go up to All Programs.
3. Select VistaScan.
4. Left click on Uninstaller.
After uninstalling click on Exit
Removing Scanner From Device Manager
1. Right click on My Computer
2. Left click on Properties
3. Select Hardware
4. Left click on Device Manager.
5. Click on the plus next to Imaging Devices.
6. Right click on 1394 Scanner.
7. Left click on Uninstall.
8. Left click OK to confirm uninstall.
9. Close Device Manager.
10. Unplug the scanner from the back of the computer.
Removing Leftover Files
1. Left click on Start.
2. Select All Programs.
3. Select Accessories.
4. Left click on Windows Explorer.
5. Click on the plus sign next to My Computer.
6. Click on the plus sign next to Local disk (C .
7. Right click on VSTASCAN and then left click on Delete.
8. Click on the plus sign next to Windows.
9. Right click on TWAIN_32 and choose Delete.*
10. Right click on TWAIN32 and choose Delete.*
11. Close Windows Explorer.
*By deleting the TWAIN folders, you will need to reinstall any other
TWAIN devices, such as digital cameras, web cams, and other scanning
devices. You will need the installation CDs for any other TWAIN
compliant devices present on your PC.
Installing the VistaScan Twain Drivers
Disable any Anti Virus software
1. Insert ³VistaScan² CD in your CDROM . If you do not have
the VistaScan CD and have downloaded VistaScan 3.76 from
the website then read the following, otherwise skip to
step 2
a. Open the My Document folder.
b. Double-click on the VS376F.EXE icon. [presumably unzipping]
c. Open the folder Disk1 and find the file called VSSETUP.
d. Double click on VSSETUP to start the install.
2. On the first screen, click on Next.
3. Click Next on the following screen.
4. Click Yes on the License Agreement.
5. On the Installation Type, select Typical and click on Next.
6. On the Settings Confirm screen, click on Install.
7. If you see an Copy File Error message choose IGNORE, as this
is not a system file and can be skipped.
8. Once the installation of VistaScan 3.76 is finished, click Exit.
Testing the scanner
1. Left click on Start.
2. Go up to All Programs.
3. Select VistaScan.
4. Select VistaScan again.
If VistaScan comes up then your scanner is working, otherwise if the
Umax test program comes up please call Umax Technical Support at
214-739-1915
For tips on how to use VistaScan go to
http://www.scantips.com/umaxvs.html
******
So, the question is, do you have an Imaging_Device in Device Manager ?
Is it labelled 1394_Scanner ?
Here is another chunk of info:
http://www.microsoft.com/whdc/system/bus/1394/1394tech.mspx
******
Scanners and Printers and IEEE 1394
Device support in Windows is based on the SBP-2 specification, which
defines a protocol for transporting commands, data, and status between
devices connected by the IEEE 1394 serial bus. For example, an IEEE
1394 scanner that uses SBP-2 to transport SCSI commands does not
require additional drivers for Windows XP, Windows 2000, Windows Me,
or Windows 98 Second Edition. The scanner uses the same drivers and
INF entries as a SCSI scanner, with two exceptions: The Plug and Play
ID in the INF is different, and Scsimap.sys is not needed.
For an IEEE 1394/SBP-2 device, the PnPID is a combination of the
vendor name, device name, and command set ID. The easiest way to
determine the PnPID is to plug the device into an IEEE 1394-capable
system and then look in the registry under the following key:
HKEY_LOCAL_MACHINE\Enum\1394
The Plug and Play ID appears as the subkey name for the scanner under
the Enum\1394 key. Use that value in the INF file instead of the SCSI
Plug and Play ID. As an example, an entry in the INF might appear
as follows:
%StringName% = InstallSection,SBP2\Vendor&Model&CmdSetId104d8
In this example, the Plug and Play ID from the registry should be
used to replace Vendor&Model&CmdSetId104d8 .
For an IEEE 1394 SBP-2 scanner, only Scsiscan.sys must be loaded.
Scsimap.sys is not needed, and it should be removed from the [AddReg]
and [CopyFiles] sections in the INF for Windows 98 Second Edition and
Windows Me. This file has never been required for Windows 2000 or
Windows XP.
The version of Scsiscan.sys provided with Windows 98 Second Edition
does not send down the open and close IRPs correctly, which causes a
problem with IEEE 1394-connected scanners. To work around the problem
in your development processes, use the version of Scsiscan.sys that
ships with Windows 2000 or Windows XP.
If you need to provide the updated version of Scsiscan.sys to
customers, this can be done under the license provision of the Windows
DDK. If you choose to redistribute the Scsiscan.sys file, the file must
be copied only as part of a [CopyFiles] INF section so that proper
version checking occurs.
******
So, that description gives a couple more things to check.
Using regedit, does HKEY_LOCAL_MACHINE\Enum\1394 contain:
SBP2\UMAX&Astra_6450______&CmdSetId104d8
If it did, then that means SBP2 was able to query the plotter
and get the text string "Astra_6450" from it. If it returns
some other value, then that would be valuable info, in terms
of whatever hacking is needed for the Vistascan package.
If so, you'll notice that the INF file we've been discussing,
contains entries for 6400 and 6500. Hacking the INF, by adding
a similar line for 6450, might get you connected. And this
is hacking, so it will be a trial and error process. My hope
would be, that the Umax firewire scanners share enough
characteristics, that you'll get some response from it.
HTH,
Paul
)