Error 403 while trying to download a driver

[MGlolenstine]

Issue

When trying to run the enumerate example on Windows or Linux, it fails with the 403 error while trying to fetch drivers.

Enumerating Pico devices...
[
    Err(
        DriverLoadError {
            driver: PS2000,
            error: "LoadLibraryExW failed",
        },
    ),
]
Downloading drivers that failed to load [PS2000]
Error: HttpResponseError(StatusCode(403))

Investigation

I checked how the drivers get downloaded and I've traced the URLs, and it'd seem that the pico-scope people have disabled their bucket for drivers, so the drivers aren't accessible at the same URL anymore.

The following URL returns 403:
https://pico-drivers.s3.eu-west-2.amazonaws.com/windows/x86-64/PS2000

<Error>
<Code>AllAccessDisabled</Code>
<Message>All access to this object has been disabled</Message>
<RequestId>2B7SVVZA1DKJ2NX6</RequestId>
<HostId>
M5pxl2KGYILGVaoqvMxNBsLcJOg9pmWxznRa8PiCRUaJdNqaQHXfhPM3KVLdOq3BhZI6nuwVj90=
</HostId>
</Error>

Call to arms

I'd like to get some help with figuring out if they've fully removed the driver files or just changed the URL.
If they have changed the URL, I'd like to know what they changed it to, if not, I'd like to figure out how to get drivers a different way.

The drivers, not sure if they're the ones we're looking for, but they're accessible in the PicoScope 7 installation (under C:\Program Files\Pico Technology\PicoScope 7 T&M Stable on Windows), named ps2000.dll up to ps6000a.dll.

Temporary workaround

To get the drivers loaded in the example, I had copied the files to C:\Users\User\AppData\Local\Pico Technology\Drivers\x86_64, which included ps2000.dll.temp, which was a temporary file created before the error occurred.

The workaround works, but only for enumeration, for everything else, the hash fails and I'm not sure where to get the files that have the matching hashes.

Kind regards

[timfish]

I'm sorry, this was completely my fault. I had cleared out my AWS account and couldn't find any services left and then closed my account a week or two ago. This issue is a harsh reminder that I was hosting these drivers in S3!

Pico don't supply their driver in a bucket like this. To get Windows and macOS drivers you need to download all the drivers for the correct architecture and they're installed via "PicoSDK" installer packages available on their website. For Linux you need to install drivers via their repositories. Until last year, the only way to get macOS drivers was to download PicoScope/PicoLog for macOS and pull the drivers from inside the app.

Since most people only have a single device, I hosted all the drivers for all architectures in an S3 bucket so they could be downloaded automatically and quickly. This meant most people could access their Pico device by downloading a single ~2MB driver.

I will reinstate these drivers and host them in a public repository so this is all more transparent. However, I won't be able to do this until early April with I'll be back home with access to my Windows machine.

Until then, the workaround is to install the correct driver package from Pico's website and then use LibraryResolution::Default which loads Pico drivers for the OS's default search paths.

[MGlolenstine]

Oh, thank you very much, I have figured the bucket was theirs, as the URL looked official 😉

We've noticed the issue in our software, which stopped working yesterday and is now unable to be started due to the 403 error.

We lost the source code for the project somewhere and we're unable to recompile the program (in Rust), so we're looking for a plug-and-play solution.

I've downloaded the drivers and extracted the dlls out of the pico scope installation and I've placed them into the %AppDataLocal%, and while this does work for enumeration, it does seem to want to replace the drivers for anything more. I haven't managed to figure out why that is (yet), but I'm guessing it could have something to do with the hash verification, as the new PicoScope 6 and 7 drivers seem to have a different hash.

Do you have an idea as to which drivers you used to host?

[timfish]

Sorry no I don't recall which drivers were there. Once I'm back with my Windows machine 1st of April I could zip up the drivers from my app data directory for you.

[Christopher-06]

Is there any progress on this?