.

Good to know you're on the right path now, secret agent girl. You're certainly in good hands with sronsen (!), and I'm sure it'll all get worked out soon.

When I was searching past forum posts earlier using "ACR38" I had come across this post by billbolton viewtopic.php?f=1&t=46752&p=420391#p420391:

I have tried an ACR38U-SPC-R (ACS brand) and a ACR38U-NPC (Resmed brand) with the 1.1.6.4 drivers (for the ACR-38U-CCID) and can tell you that neither type of reader works with that driver.

I kinda thought that may be part of the problem, since you mentioned earlier that it had installed version 1.1.6.4, but my "glory days" with computers were back in the days of DOS (1980s!), so I knew I wouldn't be able to guide you any farther than my last post.

I hope that you find the software to be helpful. I've found it very interesting to see just when my apneas/hypopneas are occurring and whether they're associated with leaks.

Best wishes,

DreamOn

.

Try manually deleting the following file....

C:\Windows\System32\DRIVERS\a38usb.dll (at least that's where it is on my Windows 7 operating system, but it should be the same for Windows XP)

This should cause Windows to try and find a new driver for your ACR38U, and hopefully it will be the 1.1.6.1 version.

Cheers,

Bill

.

[quote="secret agent girl"]We've searched for and read every post concerning the ACR38 smart card reader. If the solution is there, we don't recognize it.


On my Vista I had to disable the wireless connections before the card reader was recognized by the ResScan program. Not sure if this has happened to anyone using XP.

elg5cats

.

secret agent girl wrote:We did delete that file and Windows does try to find a driver again.

If we let it try to find a driver, it always goes to the internet and finds 1.1.6.4. If we try to point it to the 1.1.6.1. driver, it fails with "Cannot install this hardware. The hardware was not installed because the wizard cannot find the necessary software."

What this tells me is that the reader you have will not work with the 1.1.6.1 drivers, or at least Windows thinks that because your particular reader version isn't listed as "compatible" in the driver's .inf file. You could try editing the .inf file (it's just text) and see if you can add your reader to the list, but of course, even if you succeed at getting Windows to install the driver this way, it still may not work... The .inf file is looking for a device with hardware ID "USB\VID_072F&PID_9000". If you go to Device Manager, get properties for the reader, select the Details tab, select Hardware ID on the pop-up, and you don't see this ID listed for your reader, you know that the driver you have is not made for your reader.

I'm as frugal as the next guy, maybe more frugal, but for reasons like this and having to use a home-made guide, I just spent the extra forty bucks and got the ResMed reader. If having access to your data is important to you, as I can only assume it is, my suggestion is to send this reader back from whence it came and order the ResMed reader.

.

Given your latest info, I'm 99.9% certain that you have the wrong reader.

The ID, USB\VID_072F&PID_90CC, is for the CCID version of the reader and it needs a different version of the driver, 1.1.6.4. ResScan however, doesn't want to see that driver, it wants to see the non-CCID version of the driver (and reader) to work. If you want to try the "modify your .inf file trick", just replace all instances of the ID in the 1.1.6.1 .inf file with USB\VID_072F&PID_90CC and it should install. The problem is that even though it will probably install, I'm fairly certain that it won't work as the hardware may not understand what the driver is saying...

Let me know what happens!

For letting WIndows attempt to find the appropriate drivers automatically, Secret Agent Boy should be exiled to the Villiage!

I suggest that you do the following:

- Unplug the card reader.

- Uninstall the drivers again.

- Go to the ACS website and download a fresh copy of ACR38U_PCSC_Driver-1.1.6.1.msi.

- Run that install script by right-clicking on the file name in Explorer and selecting "install".

- Please report back the results. Do not plug in the card reader yet.

Hope to hear from you later.

Steve

.

Now I tend to be overly obnoxious and cynical. It's in my DNA. And I apologize in advance if I offend anyone. But just wanted to mention, this is why I decided to overpay and order the card reader directly from ResMed, instead of buying a cheaper card reader that should work.

https://www.cpap.com/productpage/resmed ... -cpap.html

This card reader works right out of the box. No need to change any drivers or do anything sneaky. What am I missing?

I'm not sure it's the wrong reader, as it has the same part number as mine. It could be mislabeled. Could be a variant with the same label. However, I had a hell of a time getting the drivers installed on one of my PCs, so I think it's worth a little more effort to get it working.

The point isn't so much saving money, although that helps. It's the adventure and getting to know people you reach out for or offer help to when everything goes to hell! And when she can read her data, Secret Agent Gal will have a great sense of accomplishment.

Steve, can you check the hardware ID of your reader in Device Manager? If it's the same as hers (USB\VID_072F&PID_90CC), and you got yours to work, then we can continue to send her down that path. If they are different, it may be futile to make her jump through these hoops for nothing...

falvesjr,

You nailed it. The "correct" device ID is USB\VID_072F&PID_9000\6&CF4CC12&0&1, or at least that's what I have installed and working.

We've learned something here. The correct model number is no assurance of the correct device. I'm devastated.

Secret Agent Gal, if you cut the USB cable where it enters the reader, it will impact the target faster when released from the slingshot and produce a more satisfying result. Sorry the effort came to naught.

Steve