Why doesn't SCSI Pro work?(ASPI error, wrong drivers, general flaky problems)
SCSI Pro works at a low level. This means that if SCSIpro does not work the problem is usually an incompatible low level component problem. A component problem is either an incompatible scsi driver or aspi file. Old drivers can cause "flaky" problems. Wrong ASPI files give errors such as "no aspi managers found" and "aspi for windows not initialized". ASPI is often the problem because "there are more versions of ASPI drivers available than you can count".
We had one customer who had two different Winaspi32.dll on the same system. One was correct when he checked the version and one was a very old aspi that did not work with scsi pro. When he checked, he checked the good one and was convinced that it was not the problem, but the system was using the other "bad" one and giving him very flaky results.
If you have Windows 2000 or Windows NT.
1. First lets download the latest drivers for your Adaptec card. You can find those here
Load the latest scsi drivers, make sure you have a SCSI disk or tape attached with proper cabling and termination and then reboot. Then rerun SCSIPRO.
2.. If this did not solve your problem please check your file versions with the program called "aspichk" written by Adaptec against the following table of tested ASPI file component versions.
Download ASPICHK.exe . This utility was written by Adaptec but is no longer available on their web site. This test runs even if you do not have an Adaptec controller.
Compare the results of ASPICHK.EXE with Mirus supplied tested ASPI files.
Pictured below is the results of ASPICHK on a working version of SCSIPro on Windows 2000. The components must all be the same version number. Other versions of the ASPI components will work, however the versions that we supply have been tested.
Windows 2000 and Windows NT
 |
Windows 2000 and Windows NT
| File Location | File Name | Tested Version # | |
| 16 bit SCSI Pro | c:\winnt\system32\wnaspi32.dll | wnaspi32.dll | 4.60(1021) Adaptec |
| c:\winnt\system\winaspi.dll | winaspi.dll | 4.60(1021) Adaptec | |
| c:\winnt\system32\drivers\aspi32.sys | aspi32.sys | 4.60(1021) Adaptec | |
| c:\winnt\system\wowpost.exe | wowpost.exe | 4.60(1021) Adaptec | |
| 32 bit SCSI/FibrePro | Same as for SCSI Pro 16 | ||
If ASPI is not installed correctly go to the proper directories listed above and rename all four ASPI files. Then copy the proper aspi files supplied from your scsipro directory "C:\scsipro32\ASPI\WINNT" . You can also reinstall SCSIPro and when it finds the four aspi files missing it will load the ones that we supply into the proper locations. Then re-boot.
Window 98
Below is the results of ASPICHK for a working version of Windows 98. The ASPICHK program reports Windows 95 but the screen shot captured below was running Windows 98. In this example the ASPIENUM.VXD did not show up because we are not running an Adaptec controller.
 |
Window 98
| File Location | File Name | Tested Version # | |
| 16 bit SCSI Pro | c:\windows\system\wnaspi32.dll | wnaspi32.dll | 1,0,0,0 Adaptec |
| c:\windows\system\winaspi.dll | winaspi.dll | 1.0 Adaptec | |
| c:\windows\system\iosubsys\apix.vxd | apix.vxd | 4.0 Microsoft | |
| 32 bit SCSI/FibrePro | Same as for SCSI Pro 16 | ||
Windows 95
Why does SCSI Pro not start, blue screens on execution or get the endless hourglass?
The properties on your "scsipro.ini" file have been changed from "archive" to "read only". This can happen automatically when the "scsipro.ini" file is copied with a CD burner. It can happen automatically when this file is emailed with some but not all email packages. This file cannot be a "read only" or it will hang the system. SCSI Pro works at a low enough level that this problem will hang the system.
The screen below is CORRECT.
 |
I purchased SCSI/Fibre Pro, why does it still say demo?
The demo version and the purchased version are the same file. The only difference is the "ini" files. The most common problem is that the incorrect "ini" file is being used. The solution is to remove demo "scsipro.ini" file and then replace it with the registered/purchased "scsipro.ini" file.
Why does Adaptec's "Easy SCSI", SCSI Toolbox and other diagnostic software conflict with SCSI Pro?
"Easy SCSI" when installed loads either a ASPI component or a SCSI driver that is incompatible with SCSI Pro. To fix this refer to the solutions offered in "Why do I get WIN ASPI errors?.
Here is a a sample response to a service call from a customer who was trying to run scsi tool box and SCSIPro on the same machine. You cannot do it. This customer went so far as to reinstall windows 2000 and this did not get rid of the incompatible aspi files.
Note aspi issues: SCSIPro works with about half of the 2000 different aspi files on the market. If you have loaded a different diagnostic typically you have to remove their aspi files before you install our product. We ship aspi with our product but we will only load our aspi if you do not already have aspi installed.
Here is our level 2 responses to our last aspi issue where the customer had loaded different diagnostic programs on the same machine.
“Unless they absolutely wiped out the windows system directories with the W2K reload they wouldn't have deleted SCSI Tools pervasive ASPI driver. They should do a disk wide search for all copies of "wnaspi32.dll" and delete (if they can) all copies that are not in the installation directory for SCSI Pro 32 or c:\winnt\system32. The date code on the wnaspi32.dll in c:\winnt\system32 should read "modified Friday, September 10, 1999, 4:06:00 PM". If it doesn't then it is the wrong wnaspi32.dll file”
Why is my Win 3.1 code frozen but not my Win95/98/NT?
The 32 bit version of SCSI/Fibre Pro was released in May of 2000. This version will work for Win 95/98/NT. Win 3.1 requires the 16 bit version of SCSI/Pro which was frozen when the 32 bit version was released.
The installation needs a password
Registration File is "scsipro.ini"
***** Installation Summary*****
1. Create a directory C:\Program Files\SCSIPro32
2. Unzip "scsipro.zip" from your electronic download or CD into a temporary file.
3. Move "scsipro.ini" to C:\Program Files\SCSIPro32
4. Install the application with "scsipro.exe" using all of the defaults
5. Run the application "SCSIPro32.exe
***** Installation Details*****
Your CD will have one file called "scsipro.zip". If you bought electronically, you will be
directed via an email to a link to download a file called "scsipro.zip"
The zip file is not password protected.
"scsipro.zip" will unzip into three files
ReadMe.txt
scsipro.exe Run this to install scsipro. This install script is password protected.
Your password is given at the top of this page.
scsipro.ini This is the registration file. The registration file "scsipro.ini"
tells the program that you have a licensed copy that will not expire,
and wether you purchased SCSI/Fibre Pro 32 or SCSI/Fibre Pro 32 Lite.
Without a purchased registration file SCSI/Fibre Pro 32 will have very limited
functionality.
If this is an internet purchase, please save the registration file
"scsipro.ini" on a diskette. You will need the registration file
in order to do an upgrade.
Note: We have sent the program and registration file to you in a zipped format
NOT to save space on the CD. CD write programs automatically change the
file property of the "scsipro.ini" file to "read only". "scsipro.ini"
must have a file property of "archive" in order to run. Zipping the files
avoids this issue.
Run scsipro.exe to install
Application is installed into a directory called C:\Program Files\SCSIPro32
Go to "Start, Programs, SCSIPro32, Launch SCSIPro version 5.x.x" to run application
Create shortcut and copy to desktop if desired
Note: The most common installation problem is an error message:
"Thanks for choosing to test a limited version of Mirus Technologies
SCSIPro"
This means that the registration file did not get move properly
Make sure that the "scsipro.ini" file in the directory
C:\Program Files\SCSIPro32 is the one registered to you.
Having the registration file outside of the program is a bother
when you first install, but makes upgrading to new releases
much easier.
***** SCSI Pro - How to Notes, FAQ and Manual *****
A SCSI Pro User Manual is not included on the CD.
Follow this link for all manuals, on line screen shots, notes and FAQ
www.scsipro.net/support.htm : For FAQ, download manual
www.scsipro.net/ScsiProFeatures.htm : For screen shots and how to notes
***** Contact Information *****
Sales & Support:
Phone:970-231-3782
Fax: 301-460-0106
Email: Sales and Support: brent3306@comcast.net
If you have purchased SCSI/Fibre Pro Professional Plus, you can scan the fibre bus with this sequence:
"Options"
"Controller Command"
Set "Device Map" to on
Once the Fibre bus is scanned select the peripheral you are testing and all tests run exactly as they do when testing SCSI.
If you have purchased SCSI Pro Professional, you can download firmware with this sequence:
"Setup"
"Download"
Select device and CTRL ID from selection
You will be asked for the location of the firmware file and point to that directory
With DOS and Win 3.1 downloading is done in a single pass.
With Win 95/98 downloading firmware requires a "segmented" download. This is because Win 95/98 specifies that the download segment size must be less than 64 KB. Therefore, a download under Win95/98 takes several passes that are performed by our "segmented download" features. To do a segmented download you have to get the download specifications off the vendors website. For example, in the Seagate on-line manuals the proper parameters are defined in the "write buffer" command. Not all drives support segmented downloads. For example, only Seagate drives manufactured in the last 5 years support segmented downloads. You must get the firmware file itself from a Seagate Tech or from where you purchased the drive.
Example (write buffer information from Seagates on line manual):
Seagate ST39102LW
write buffer (modes,0,2, supported) Firmware Download Option (modes 5,7,supported)
In SCSI pro download screen enter
"write buffer ID" 0,
"write mode" is 5 or 7 depending on whether you send the segments with an offset on or off
NT/W2K needs a
patch to the registry in order to do single-pass downloads up to 1 Mbyte. NTtune,
a Mirus utility, makes that patch. All the operator does is specify the adapter
driver to be modified and the size of the largest single-pass download that they
want and away they go! Segmented downloads are a default requirement under
NT/W2K if you don't use NTtune.
Is their a re-sellers discount for SCSI/Fibre Pro?
No. SCSI Pro is sold exclusively by Mirus Technologies, Inc. Mirus Technologies does offer finders fees and commission for re-sellers.
Why do I get a "General Protection Fault"?
Win NT and Win 2000 have to have a SCSI device attached when running SCSI Pro or else you will get a windows error"General Protection Fault". This is not the case with Win3.1/95/98. To get around this you need to append your SCSIPRO.INI file with the file ADDON.INI that you will find in the same directory with the rest of your SCSI Pro components. Open the ADDON.INI file and copy the contents and then paste this to the end of your SCSIPRO.INI file. This should eliminate the "General Protection Fault" but may not solve your real problem which is that the SCSI device is not showing up on the bus. If the SCSI device does not show up on the bus you need to check cabling, cable length, possible SCSI ID conflict and that there is a terminator at the end of the bus. For PCMCIA/PC bus cards you need to make sure that termination power is supplied to the bus.
A second way to get a "General Protection Fault" is by copying SCSI Pro to a CD. When a file called SCSIPRO.INI is copied to a CD, SCSIPRO.INI property attributes are changed automatically by the OS from "archive" to "read-only". SCSI Pro requires this file to be a read/write(archive) and not a read only file. To avoid this problem the SCSIPRO.INI file is zipped when the program is shipped on a CD. We agree that this should not cause a "General Protection Fault" and our developers are looking at ways to fix it.
It is possible to see up to two extra controllers (other than your SCSI and Fibre). These are your primary and secondary IDE controllers. Zip drives and CD readers and writers are really SCSI devices running on a USB or parallel-port adapter and can be tested with SCSI/Fibre Pro. Other IDE devices show up as "?'. You can turn off the IDE scan by clicking on the corresponding CTL button, saving the configuration under FILES/SAVE CONFIG, then exit SCSI Pro and re-run it.
How do I lower the capacity of my disk drive by lowering the number of blocks?
To lower the number of blocks go to "commands, setup, mode select,
operating parameters, number of blocks". In the operating parameters
number of blocks is one of the variables. Lower the number of blocks in all three fields ( current,
default and saved). Change
these fields, save the parameters and reformat.
How do I change my SCSI 2 drive to a SCSI 1?
"Commands, setup, change definition"
How do I lower the capacity of my disk drive?
There are problems with changing drives to 9GB since you run out of bits to describe values that high, so Seagate will say that a drive over 9GB
starts at 0, ( 0 being 9 GB) and then adds the blocks over 0 to get to 18GB.Rather than play around with that, try this:
I am assuming that you have a working 9 GB drive. Take the 9 GB drive and add the 18 GB drive to the same SCSI bus. Then Go to SCSI Pro
Select Utiltiies:
Select Media Exchange . This utility will do a bit by bit copy of your 9GB drive to the 18 GB Drive. The 18 GB drive will then have a 9GB boot sector, and will look like a 9GB drive.
You can do multiples of these!
Having trouble with the Media Exchange Utility?
A lot of our customers cannot use the newer drives. What they do is take a old drive and do an image copy with our "Media Exchange" feature. Media Exchange does a bit by bit copy which turns makes the new drive exactly like the old drive. I am not sure if this will solve your problem but it has worked for other people who are doing digital audio.
Go to SCSI Pro
SCSI ID's of the source drive must be lower than that of the destination drives.
Select Options, protect keys and unprotect the destination disk drive (uncheck)
Select Utilities
Select Media Exchange This utility will do a bit by bit copy of your older drive to the newer drive.
The new drive will then look exactly like the older drive!
How do I report a problem with SCSIPro?
In order to make it easier for our development team to understand your problem we request that you run the simulator option in order to capture the problem and then zip up and email to us 5 files.
Here is how this is done:
1) Start SCSIPro 32. Save the config file (File, Save Config). This step adds a configuration section to the "scsipro.ini" file which includes the simulator option. Before the simulator option can be set you need to save the config file once.
2) Within the SCSIPRO.INI file change the line containing the "Simulation" parameter from "Simulation = 0" to Simulation = 1". You can use an ordinary text editor (e.g., notepad) to complete this change.
3) Start SCSI Pro and immediately repeat the original actions that resulted in the observed error or problem.
4) As soon as the error/problem occurs close SCSI Pro (if it hasn't been closed for you by the system).
Change the SCSIPRO.INI file back to "Simulation = 0". This is
important. Should you leave the simulation recording on you can quite easily fill up the available space on your system disk!
5) Zip up the following 5 files:
[a] All the record*.txt files in your SCSI Pro installation subdirectory. There should be
three (RecordAdapters.txt, RecordCommand.txt, RecordDevList.txt)
[b] The daily log file (spmmddyy.log).
[c] Your SCSIPRO.INI file.
Email these five files with a description of you problem to bduckworth@mirustech.com.