If get_io_timeouts sets the interval timeout to 0, it means that the
read should return immediately even if there is no data. If
get_io_timeouts sets the interval timeout to -1, it means that the read
operation should wait indefinitely for the next byte. In either case,
the interval timer is not used, so there's no need to worry about
forgetting to start it, and the delay in returning data was causing a
problem in Ti99Hdx.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=42882
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/8454
Before the commit in question, both of these paths would be parsed as valid (with e.g. FindFirstFile):
```
Z:\tmp\\*
/tmp//*
```
After the commit, only the DOS path is accepted, while the Unix path returns ERROR_INVALID_NAME.
Fixes: ffa88c3993c3da97c7403209ef2068b2e3fac66f
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/8464