Making Adaptec AHA-2940 (AIC-7800) 32 bit Driver Work in Windows 7 or Server 2008 x64 (.inf download included)

While incredibly dry and enough techno babble to make your eyes glaze over, babywideeyesthis Post has enough info to help you overcome the “Not supported on x64” issue many manufacturers claim about their products, (this method can also work on other devices such as printers) and literally only takes about 2 minutes of your time. What it really comes down to is, it’s just text. You don’t need to understand anything more than that, a driver file is a text file that lists the info for your device, you don’t need to feel overwhelmed, you don’t need to understand why, how or what the coding is, just add your device text and make it match the format of the original driver text)

 So today I decided, OK, time to get the tape software installed on the newly rebuilt server 2008.

The tape drive wasn’t showing up in Nova Backup.

Device manager was not showing a tape drive, but under “unknown” showed a yellow “!” Next to “SCSI Controller”.


Ahhh, the Adaptec 2940UW scsi controller needs a driver installed.


Guess what. Adaptec End of Lifed the 2940’s Before Vista Came out, and they never made an x64 driver.  

I thought, people have had to run into this before me. Sure enough, many online are clamoring about it for many different controller models.

One guy posted, OH, if you find the XP driver file “pnpscsi.inf” in the c:\windows\inf folder, and open it in notepad, you can just add the hardware ID’s to the file, save it, then it will be seen by x64.

Except I read further that Win 7 and 2008 didn’t even have the .inf driver file. Vista did, but they took it out of 7 and 2008.



Finally I found a post where a guy said, another poster has posted a downloadable .inf file. I got it, it didn’t work.

I tried adding the hardware ID’s the one guy said. It didn’t work, then I realized, well, if my hardware ID’s are different, then that wouldn’t work, so I looked up the ID’s server 2008 was seeing

To do this go to device manager, right click and choose properties on the “Unknown – SCSI Controller” then click on “Details”, then change the drop down to show “Hardware ID’s” Then right click and copy each, then paste each one into notepad and save the file for easy one glance later reference.

I then opened this file in my main computer and copied and pasted the ID’s into the inf file, and added the needed language that matched what the file had before for the original ID’s and changed the description so I would recognize it when the system did see it.

Instead of “Adaptec 78xx SCSI controller” (which is what the previous lingo was for all models) I changed the description to “Adaptec AHA-2940UW”

So I copied the follwing four lines from the Hardware ID list and pasted only the needed portion, (IN BOLD) into the .inf file and altered the lingo to match what I saw already there:



I Altered the .inf file from this:


%PCI\VEN_9004&DEV_7078&SUBSYS_70781414.DeviceDesc% = aic78xx_Inst, PCI\VEN_9004&DEV_7078&SUBSYS_70781414


%PCI\VEN_9004&DEV_7078&SUBSYS_70781414.DeviceDesc% = aic78xx_Inst, PCI\VEN_9004&DEV_7078&SUBSYS_70781414





PCI\VEN_9004&DEV_7078&SUBSYS_70781414.DeviceDesc = “Adaptec AIC-7870 PCI SCSI Controller (Emulated)”


To THIS (in bold black is the text taken from the hardware ID’s, and in red is the lingo already in the inf for other models I had to put together with the ID’s to make it work, and in green is what I changed the description to so I would recognize it, it originally appeared for all models as the Desc directly above it):


%PCI\VEN_9004&DEV_7078&SUBSYS_70781414.DeviceDesc% = aic78xx_Inst, PCI\VEN_9004&DEV_7078&SUBSYS_70781414

%PCI\VEN_9004&DEV_8178.DeviceDesc% = aic78xx_Inst, PCI\VEN_9004&DEV_8178


%PCI\VEN_9004&DEV_7078&SUBSYS_70781414.DeviceDesc% = aic78xx_Inst, PCI\VEN_9004&DEV_7078&SUBSYS_70781414

%PCI\VEN_9004&DEV_8178.DeviceDesc% = aic78xx_Inst, PCI\VEN_9004&DEV_8178





PCI\VEN_9004&DEV_7078&SUBSYS_70781414.DeviceDesc = “Adaptec AIC-7870 PCI SCSI Controller (Emulated)”

PCI\VEN_9004&DEV_8178.DeviceDesc = “Adaptec AHA-2940UW PCI SCSI Controller”


 Once I knew what to do, it literally took me about 2 minutes to edit the file and get the driver installed and working.

x64 recognizes 2940UW and tape driveIt’s amazing isn’t it? Less than 2 minutes, but these companies won’t even do that. But I suppose in the spirit of good capitalism A 2 minute driver file update won’t make them millions more when they could release a new card that does the same thing, and sell it as new technology, just because they say the old one isn’t supported on a new OS.

Anyway, I got it working, instantly the tape drive was added to device manager, once the Adaptec driver installed successfully. 

Here’s a download link to my .inf file, and the matching driver files that go with it:

Click here For Adaptec AHA-2940UW (& Models listed below) x64 Driver Download

The following Device/Hardware ID’s are also included in this .inf file and should work under x64 when using this install .inf package:

PCI\VEN_9004&DEV_5078 (Adaptec AIC-7850 PCI SCSI Controllers)
PCI\VEN_9004&DEV_5075 (Adaptec AIC-7550 PCI SCSI Controllers)
PCI\VEN_9005&DEV_0011 (Adaptec AIC-7870 PCI SCSI Controllers)
PCI\VEN_9004&DEV_8178 (Adaptec AIC-788x PCI SCSI Controllers)


XP 64bit need drivers for HP PSC 1350 all in one

Here’s a solution I posted on Fixya a couple of years ago. (Number 2 in Blue below)

XP 64bit need drivers for HP PSC 1350 all in one

Problem with the HP PSC 1350 All-In-One Thermal Printer

By curtis_norma on Mar 06, 2009

I am using Windows XP 64bit and the disk that came with the printer does not support 64bit operating systems.I am using a HP PSC 1350 all in one printer / scanner / copier / and I don,t know how or where to get the drivers to download so I can print from my computer.I have a USB hook up and I,m still stuck on what to do. Please Help, Thanks


o curtis_norma

o 2 years ago

RE: Best Solution (2 of 2) thank you so much You were right it was just a diagnostic driver and i was still having issues until now. Thanks Again! Curtis

RE: Best Solution (1 of 2) Sorry. This link does not contain x64 drivers for the HP product… merely some update.

Best Solution (1 of 2)

posted 2 years ago


· Rank: Wiz

· Rating: 84%, 43 Votes

you can download the drivers from hp.use this link.ã‚â»


Solution 2

posted 2 years ago

Dirhyllykt Doc

· Rank: Apprentice

· Rating: 100%, 4 Votes

I cannot speak for the author or 3rd partys who may have been involved in the alteration or creation of this beta driver. It says that it’s an HP Beta driver for x64, and it seems to be working fine for me on XP x64. My system did not find any virus’s or spyware, and it is downloadable from cnet downloads which is usually a pretty reliable source for spyware free and virus free downloads. After much aggravation and a re-visit to past cussing sessions with clenched fists at the infinite money grubbing moronic attitude of the big companies (like HP and Epson) who want you to buy a new device so they don’t write the drivers you need for your existing and perfectly usable device, I came across this beta driver and gave it a chance. So far it seems to allow my PSC 1350 all in one to print flawlessly on XP x64! WHOO HOO!

HP can @#$%$#@! (this being the 5th or 6th go around with no drivers for an HP device that works fine on XP32, Vista 32 & 64, but not XP x64 (XP x64 being the most stable operating system MS has developed to date, I find it hard to understand why it’s become the re headed step child). I’ll never purchase another HP printer. (I fought this one desperately since it’s a brand new printer that was given to me as a gift.)

anyway, enough spouting off, here’s the link to the driver! ENJOY!

Was this helpful?

4 people thought this was helpful


Dirhyllykt Doc

· 2 years ago

In regards to the solution above mine:

That is a link to the only software available from HP for the PSC1350 on XP x64 which is a diagnostic utility and NOT the needed driver. The diagnostic utility is pretty much useless without the actual printer driver, and it only works on about 50% of the machines I’ve installed it on running x64 anyway.

(Typo correction – “re headed” above should have been “Red Headed”)


Dirhyllykt Doc

· 2 years ago

Here’s the same link from ZDnet which requires you to register and login, but it gives a good description of all the printer models supported:


Dirhyllykt Doc

· 9 months ago

I previously wrote about the solution for this using the x64 beta driver for XP. (Solution 2) I’ve since upgraded to Vista, and later to Windows 7 with a brand new Core i5 machine. I ran into difficulty because this driver will not install at all on windows 7, it gives 2 error messages, first saying you cannot install using the “Run as” command, and second saying the OS was not compatible. it was then I had a wonderful revelation:

1) go to then download and install the x64 version of 7zip. once installed, right click on the printer driver .exe file and choose 7 zip>> then extract to x64Drv5.64.0.17>>
this will extract all the files in the driver file into a folder.

2) add a printer. choose local printer, USB virtual connection. when it asks for a driver choose “have disk” then point it to the extracted folder.

The driver will install and work perfectly!

NOTE: if your downloaded file is named
x64Drv5.64.0.17, you may need to rename it and add the .exe to the end so it appears as “x64Drv5.64.0.17.exe”

Shake ’em away!

More Windows 7 Tips:

Some of these are repeats, but I just got such a kick out of the first one I’ll list it here:

1. Shake ’em away

Ever had 10 Notepad, two Powerpoint and 50 Outlook windows open?

Want to minimize all of them except the most important one?

In Windows 7, you can grab the top of the window and shake it about to scare away all of the other open windows. Simple.

Try it, open a bunch of windows, then grab the top of one and shake back and forth.

One more tip – creating system images Like GHOST

Windows 7 has a “Ghost” like feature built in. Start – All programs – Maintenance – backup & Restore, then at left, create a system image.

This is a great feature and allows you to restore the system exactly as it was like a ghost image would. (so it might be a good idea to also create a system recovery disk to boot to

In case you ever need to restore the image from boot up)

Another little tip – if you wish to keep multiple images on hand, all you have to do is copy the image folder to another folder and/or rename it (I add the date to the end of the folder.)

The folder will exist on the target drive you chose to backup your image to. The folder is called “WindowsImageBackup”


Awesome Win 7 Secrets & Activation

From the email archive 11/17/2009

Check out this page from maximum pc. The keyboard shortcuts alone at the articles beginning are worth the read – like:

Hold Ctrl + shift then click – to launch an app from the task bar or start menu (with admin rights)

and BTW, Win 7 does have to be activated, to check – right click “computer” then click on properties. Scroll to bottom, what does it say about activation?

If it says “WINDOWS IS ACTIVATED” then you’re good to go

If it says “windows will activate automatically in xx days” – then you should probably do it yourself because auto activation is known to fail, especially on volume license versions

Mine wouldn’t activate on its own, it kept trying and erroring. So I decided to do it by hand, and again encountered errors. The error message would just say it failed, but would

Have an underlined link that said “Details” when I clicked on that I found the following message:

Code 0x8007232B – DNS name does not exist

Adding DNS Server IP’s does not solve the problem. This is actually a throw back to Windows server 2003 and early Vista activation issues and interestingly the fix is

Kind of stupid. There’s a link that says “Enter new product key” next to the activation status area. You click that, but put your same key in and it activates successfully.

(this is probably because it never asked you for a key during install, and so is trying to activate with a blank key)

If you don’t activate and windows keeps failing automatic activation, you will eventually get locked out of the system.

In the past, Vista did this because you had to activate using the admin account, and not an admin equivalent. By default the account you set up when you install is given admin equivalent

And the real admin account is disabled. Whether this is part of the issue or the solution or not, I recommend that while logged in under your default account, that you:

1) Right click the computer icon and choose manage

2) Go to local users and groups, then users below that

3) Right click on the administrator account and choose properties

4) Untick the account disabled check box

5) Save by clicking ok

6) Now right click on the administrator account and choose reset password (answer yes or continue since the account has never been in use and is not logged in)

7) Type in a strong password for the account

This is your back door. If your admin equivalent account hoses for any reason, and this admin account is disabled you might just be done. At least with admin enabled and password protected you can get in to fix stuff.


Windows 7 Open Command Prompt Here Tip

Just found out this cool tip.

With windows XP, when you had the power toys installed, you could right click on a folder in windows explorer, and have the choice “Open Command Prompt Here”

This functionality is already built into windows 7, you just hold down the left shift key, then right click on the folder and there it is “Open Command Prompt Here”