SCSI on Windows 10 64-bit: Adaptec AHA-2940 (29xx) Ultra, AIC-7870 (78xx), or 29320LPE Ultra 320

When I first started playing with 68k macintosh systems around 1999/2000 (a Macintosh Plus) I connected an external SCSI drive to my Windows 98 system and was able to use an early version of Basilisk II with SCSI pass-through to format the hard drive.  Now 18 years later, SCSI is an obsolete technology, and in general is not supported under the latest versions of Windows and the the Macintosh OS, although I believe Linux still has support.

Luckily a skilled person on the internet has made 64-bit compatible drivers to support some of Adaptec’s cards under Windows 10 (sorry I’ve found nothing for the latest version of the Macintosh OS).   I’ve personally tested the Windows 10 driver for Adaptec AHA-29xx cards with an AHA 2940U PCI card.

I’m not sure how much longer using SCSI controllers will be supported, so if you don’t already have working SCSI devices I’d suggest you invest in one of the more modern solutions such as SCSI2SD for setting up your classic Macintosh instead of using this option.   But, if you’re like me, and do have a bunch of old hardware, it’s good to know we can still use it on our modern systems to setup our aging systems for at least a couple of more years.

Step 1: Select your driver

Step 2: Configure Windows 10 to let you install unsigned drivers

Updated 2019/03/13: Shane’s suggested method is now blocked by windows Secure Boot Policy… you can turn off the Secure Boot Policy, but the methods I found are more complex than the original method to do this… so I’ve reverted back.

Update 2018/12/31: Shane Cook (see comments) provided an easier way to install unsigned drivers.  I’ve updated this post with his suggested changes.

Figure 1: Choose an option
  1. Physically install your SCSI card in to your computer if you haven’t already
  2. Download either the AHA-29xx or AIC-78xx driver for your card if you haven’t already
  3. Unzip the zip file,
    1. there should be a folder called: AdaptecAic78xx
    2. the folder contains 3 files: djsvs.inf, djsvs.PNF, djsvs.sys
  4. Hold down your shift key and select windows -> power -> restart
  5. On the screen titled: Choose and option, select Troubleshoot (Figure 1)
  6. On the screen titled: Troubleshoot, select Advanced options
  7. On the screen titled: Advanced Options, select Startup Settings (you may have to select more options)
  8. On the screen titled: Startup Settings, select Restart
  9. After your computer restarts, on the screen titles Startup Settings, select Disable Driver signature enforcement (option 7 for me)
  10. Wait for you computer to finish restarting, you should now be able to install the driver for your card.
  11. Run Command Prompt as Administrator (added 2018/12/31)
  12. In the Command Prompt Window run: bcdedit.exe /set nointegritychecks ON (added 2018/12/31)

Step 3: Installing the Driver

Figure 2: SCSI Controller
  1. Open Window’s control panel
  2. On the window titled: Control Panel, Adjust your computers settings, choose Hardware and Sound
  3. On the window titled: Hardware and Sound, under the grouping Devices and Printers, choose Device Manager
  4. On the windows titled: Device Manager, you should see an Under device manager you should see a grouping Other devices -> SCSI Controller, select SCSI Controller (Figure 2)
  5. Right click on SCSI Controller, and select Update Driver
  6. On the window titled: Update Drivers, select Browse my computer for driver software
  7. Select the folder containing the driver you downloaded (Figure 3)
  8. Windows should ask you if you want to install the unsigned driver (Figure 4), select install this driver software anyway.
  9. Windows should install the driver (Figure 5)
  10. The proper name for your card should be listed in the Device Manager (Figure 6)
  11. Run Command Prompt as Administrator (added 2018/12/31)
  12. In the Command Prompt Window run: bcdedit.exe /set nointegritychecks OFF (added 2018/12/31)
  13. Turn off your computer
  14. Connect a SCSI device to your computer and reboot.   I tested with a Iomega Jaz 2GB drive. (Figure 7)
Figure 3: Browse to files
Figure 4: Install this driver software anyway
Figure 5: Driver Installed
Figure 6: Driver Listed
Figure 7: Drive Attached

Steps 4: Using a connected storage device

I’m assuming that you mainly want to get a SCSI device connected to your modern system because you want to setup an old hard drive, or removable drive for use with a 68k Macintosh System, or some other SCSI system from that era.

As I mentioned in my intro paragraph, I originally connected an external hard drive and used Basilisk II’s SCSI pass-through feature to setup the drive.  I haven’t been able to get SCSI pass-through working under Windows 10, so instead I now I attach the SCSI device/drive to my PC and then create a disk image to work with, then write the edited disk image back to the device/drive.

Step 5: Let me know in the comments if this worked (or not)

I’m not the creator of these drivers, so I can only vouch for cards they have been tested on that work.   Please comment to let me know what card you’ve used these with and did they or did they not work.

Current reported as working:

  • AHA-2940AU (by Knutbert, in comments below)
  • AHA-2940U (by me)
  • AHA-2940UA (blascow, author of the driver, the original thread)
  • AHA-2940UW (spacek, in comments below)
  • AVA-2903B (mdlark1966, original thread)
  • AVA-2906 (harry, in the comments below)

37 thoughts on “SCSI on Windows 10 64-bit: Adaptec AHA-2940 (29xx) Ultra, AIC-7870 (78xx), or 29320LPE Ultra 320

  1. Hi Steve,

    When I download your Unsigned driver for Adaptec AHA-29xx cards there is only and entry inside for the 78xx scsi cards. Am I missing something ?


    • The creator of the driver modified the 78xx drivers, if you look in the .inf file you’ll see entries for the 29xx series of cards, e.g. the Adaptec AHA-2940AU PCI SCSI Controller, I’ve updated the blog entry with a note.

  2. Hello Steve,

    You can add the Adaptec AVA-2906 to the working cards list. I had 2940’s but no more, so I decide to try with the 2906. The setup included the PCI Adaptec 2906, a SCSI 50 pin ribbon cable and a 1.3GB SCSI MO internal drive. I followed your instructions and after rebooting the drive was online in Windows 10. Reading and writing was very good if not better than years ago. I loaded the 2940 drivers. I also can confirm SCSI still works on linux. We had a Workstation running Opensuse Tumbleweed that had two 300GB SCSI drives. That was less than 2 years ago. Next time I will try to mount one of the 300GB drives on Windows 10.

    Thanks for the great tutorial.

  3. Hi Steve

    I have an Adaptec 2940 PCI Card. I followed your instruction to the letter. Unfortunately, when I give the location of the djsvs.inf and the djsvs.sys files, Windows 10 (64 bit) tells me that it does not find any driver. Any idea what is wrong?

    • Hi Kurt, not sure. I’ll test this again later this weekend, hopefully nothing has been changed in Windows 10 that prevents the installation. is your Adaptec 2940 card listed under “Other Devices?” (step 3.4). Also when you downloaded the .zip file did it have all 3 files (I updated the blog entry to list them).

      • Hi Steve

        Thanks for prompt reply and for updating the blog. The Adaptec 2940 card is listed exactly like in your screenshot above, i.e. as “SCSI Controller” with the exclamation mark. All three downloaded and unzipped files are in my folder: djsvs.inf (18KB), djsvs.PNF (8KB) and djsvs.sys (87 KB).

        I assume that there is no aspi required under Windows 10? Please let me know if I can assist with any additional information.

        • Hi Steve

          One more thing: the system tells me that it could “not find any drivers for this device” although I pointed it to the folder with the drivers. It appears to me that the system refuses the “unsigned drivers” although I went through the procedure in your step 2.

          • Just tried with a clean install of Windows 10 build 1803 and was able to install the driver for my 2940AU card. It could be you have a version of the 2940 series that isn’t supported, or something else on you system is blocking the install. I’ve added some more screen shots to show the later steps so you can confirm how far you get.

  4. Hi, I report that Your solution is working. My configuration:
    IBM Thinkstation S20, Win 10 Pro 64bit (1703), Adaptec AHA-2940UW PCI SCSI adapter. Thank You.

  5. Hi Steve,

    thanks for putting together that information!

    I chose the file and installation of the driver for my old Adaptec AHA-2940AU on Win 10 pro / 64-Bit went smoothly just as described. Next I’ll hook up my Fujitsu MO-Drive…


  6. Hi Steve

    I’m back just to confirm that your solution is working. My AHA-2940U2W has another chip set, and I could not solve the problem. It uses the driver aic78u2.sys (instead of djsvs.sys). So I bought an AHA-2940/2940U from Ebay, i.e. I circumvented the Problem. With the new card, the patch is working.


    P.S. If somebody comes up with a solution for the AHA-2940U2W, I am still interested.

    • Can you provide more detail? E.g. what card did you try it with, did you have any other SCSI cards etc? Any additional information you can provide would be helpful so that others can avoid the issue.

  7. It worked as described with an Asrock H81 board PCI AHA-2940UW. After the driver was installed my DDS tape drive was listed as a cassette drive at the top of the device list. If updating the driver does not work try installing the driver manually by right clicking on the file “djsvs.inf” to install it.
    Thanks. I am backing up with tape and not accidently wiping out my files again !!!.

  8. I followed the instructions and it worked great to install my Adaptec scsi card (AHA-2940) but windows 10 can’t (or won’t recognize my HP Scanjet 4C). Any suggestions from anyone?

  9. The same case reported by Al. I followed the instructions and it worked great to install my Adaptec scsi card (AHA-2940) but windows 10 can’t (or won’t recognize my HP Scanjet 4C). I tried with VueScan x64 but it is not working very well because it identifies the scanner as HP Scanjet 6100, it seems that an update has to be done. Did Al give you feedback?

    • I wish I could help more, but I mainly wanted to get this working so I could connect old storage devices, most of those don’t need extra drivers. You best bet would be to contact VueScan to see if they could help.
      According to their website it’s supported.
      To clarify, I’ve never used VueScan, or tried to use a SCSI scanner in at-least a decade.
      If you do get this working feel free to post here so others can benefit from what you figure out.

  10. Hi this looks really interesting and looks like it might solve my problem of connecting a Nikon Coolscan III scanner to my computer running Windows 10, however I noticed the comment about storage, should it work for the scanner? Thank you

    • Hi Guy, the driver posted here should let your computer see your SCSI card. But you’d likely still need a driver from VueScan to actually use the scanner. At least that’s how it was in the old days. One driver to activate the card, and a second driver to activate the device attached to the card (if it’s anything other than a storage device)

  11. Installed the driver today. Quick and simple to do following your instructions. Works perfectly with my AHA 2940/2940U card and my Nikon Coolscan III scanner. Vuescan is essential for the scanner driver. For film and slide scanning you need the Professional Edition. Supported scanners can be checked at A free trial version can be downloaded to check whether it works with a particular scanner. If the web site says a scannner is supported but it isn’t working properly contact Ed Hamrick via Support/Contact us on the web site. He is very good at responding.

  12. I managed to buy a new ‘Adaptec 29320LPE PCI-E 1x U320 SCSI Card’ from Ebay.
    Windows 7 x64 drivers were available here:

    Despite being signed got the error “the publisher of an authenticode(tm) signed catalog was not established as trusted”. Why make this so dam complicated? After a bit more looking, I see you need to run command prompt as administrator and type

    bcdedit.exe /set nointegritychecks
    This disables ALL driver checks, so be careful with future drivers.

    Driver would then install. Adaptec SCSI Card 29320LPE – Ultra320 SCSI.
    Now I just need to find an external a SCSI lead that will fit my SCSI film scanner…..

    To enable driver checks, enable again with
    bcdedit.exe /set nointegritychecks off

    Hope this helps.

  13. Well, all this does is reinforce my 30+ years of disdain for Microsoft… /set doesn’t have a nointegritychecks command. I even tried cut-n-paste from Shane’s post above…
    Administrator: Command Prompt
    Microsoft Windows [Version 10.0.17134.590]
    (c) 2018 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>bcdedit.exe /set nointegritychecks
    The set command specified is not valid.
    Run “bcdedit /?” for command line assistance.
    The parameter is incorrect.


    Someone else mentioned having to boot from the installation disk to get this to work. I guess I’ll try that…

  14. So does this mean I’m done, with nowhere else to go? When I select “View – devices by connection”, I can see the drive, correct size and part number, etc. However it doesn’t show up even as an unformatted disk in the drive list in File Explorer. It’s like it is nowhere, yet I can see everything about it in the Device Manager…

    • Hi Keith, have you tried initializing the drive through Windows Disk Management application?
      Control Panel -> System and Security -> Administrative Tools -> Computer Management -> Storage -> Disk Management?
      I’ve used this method mainly for connecting and formatting removable media, and emulated drives (e.g. SCSI2SD).

      For bcdedit.exe /set nointegritychecks two things:
      I had a typo, it should have been bcdedit.exe /set nointegritychecks ON, I’ve updated my blog.
      Also Windows now blocks this as part of it’s default “secure boot policy”. I’ve found a few ways to turn that off, but it makes this method, way, way more complicated.
      So for now I’ve reverted back to the original method which still works.

  15. I have followed your instructions above to install an Adaptec SCSI controller AVA 2904 to interface an old Canoscan 2700F under Windows10. I used ‘Unsigned driver for Adaptec AHA-29xx cards ‘ from above and this worked effortlessly. Thank you very much.

  16. Driver and your instructions did the trick for an Adaptec 2930 and Syquest Syjet. Ahh…and now for easier file transfer between PC and Atari Falcon. Thanks so much!

  17. Thanks very much for this! I got my old Minolta Dimage Scan Elite F-2900 to scan again after these drivers worked for my AHA-2930U SCSI card. I use VueScan software and it recognised the scanner without a glitch.

  18. Hi,
    Thank you so much for this driver fix. Using it I’ve brought an ancient Adaptec AVA-2904E/canon PCI card back to life and it’s working fine with a canon FS7210 film scanner which was otherwise destined for the scrapheap. I’m running Windows 10 Pro version 1903 OS Build 18362.207

  19. I am hoping to get my Adaptec 2940UW card installed along with my SCSI Plextor 8/20 CD writer and Plextor 40 CDrom which I’ve used for years on Windows XP. I now am at version 1809 on Windows 10 Pro. My question, which hasn’t been addressed that I can see, is whether I need to intall an ASPI layer with Windows 10? I am running software on Windows 10 which I had running on Windows XP which is compatible with the Plextor drives. Thank you

    • Hi Delbert,
      Yes, I believe you need an ASPI layer, I did some hunting about a year ago when I tracked down these drivers, I didn’t have any luck.
      If you find something let me know.

      • I ran a check of my Windows 64 bit system using ASPICHK.exe and it reported I am running wnaspi32.dll version 4.60 which is located in my syswow64 folder of my windows directory. I assume this was installed when I installed Exact Audio Copy. I have been using EAC version V.095 prebeta which is a pretty old version, but have not experienced any problems ripping audio CDs to Windows 10. I think this is the only ASPI file required because ASPI32.sys is a 32 bit file, WOWpost.exe is required only for 16 bit programs and ASPI32.dll is also only necessary on a 32 bit system. I’m going to proceed with the tutorial you’ve provided, but have decided to use an Adaptec AVA-2906 card instead of the 2940UW. The AVA-2906 card has an internal 50 pin connector and doesn’t come with the bios as the 2940UW. Got my fingers crossed

  20. Well, today, I set out to install my Adaptec 2940 UW card or my Adaptec AVA 2903 card in my computer to get this thing going. I was stumped from the beginning. Neither card could be inserted into the PCI Express slots of my Gigabyte Z370P motherboard thereby thwarting my well planned intentions. There’s always a hurdle!! So, it appears lacking a PCI slot, I am out of luck on this adventure……..

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.