2019.10.10 14:21 "Re: [Tiff] TIFF_IO_MAX too large for Windows XP", by David C. Partridge
I have since reproduced it using a "real" network share accessed from the VM. I don't have a real hardware XP to test with.
From: Tiff [mailto:email@example.com] On Behalf Of Olivier Paquet
Le jeu. 10 oct. 2019 à 08:14, Edward Lam <firstname.lastname@example.org> a écrit:
On 10/10/2019 8:10 AM, David C. Partridge wrote:
> I like to propose that this be adopted into the official codebase :)
Do we really want to be calling GetVersion() on every single I/O call on Windows?
No. It's horrible. At the very least don't call it for blocks which are already small enough, which will be nearly all blocks for a well formed file.
Or perhaps handle read() failure by a second attempt with smaller blocks, on windows only.
David, have you reproduced this with an actual network server? Or only with the vmware host drive? It could very well be a vmware problem too, although I suspect it might not fail so nicely in that case (with error code and everything).