Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Painfully slow access to CF card #63

Open
fadden opened this issue Aug 4, 2023 · 0 comments
Open

Painfully slow access to CF card #63

fadden opened this issue Aug 4, 2023 · 0 comments
Labels

Comments

@fadden
Copy link
Owner

fadden commented Aug 4, 2023

On a Win10 system, it took about a minute to register the contents of a 256MB CF card. CiderPress II was able to open the same card instantly.

The problem is the unnecessary use of ScanCapacity(), which was added for old versions of Windows (<= Win2K) that didn't support the DISK_GEOMETRY_EX call. It wasn't possible to determine the size of the physical media, so the scan function essentially does a binary search to find the last readable block.

The card / reader combo I'm using (an old Lexar card with a USB 3 "PixelFlash" card reader) stalls for a couple of seconds on every bad read. Once the card's size is detected, it works just fine, but the initial scan time is absurd.

Curiously, it does try to use the geometry call (_EX version first, older version if that fails) when gathering the list of available devices, but it falls back on the block probe when actually opening the device.

@fadden fadden added the bug label Aug 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant