On Apr 24 16:01, Brian Inglis wrote:
> On 2020-04-24 08:42, Corinna Vinschen wrote:
> > This problem is due to a restriction in Windows introduced with Windows
> > Vista. In theory it gets explained at length in "Changes to the file
> > system and to the storage stack to restrict direct disk acces
On 2020-04-24 08:42, Corinna Vinschen wrote:
> This problem is due to a restriction in Windows introduced with Windows
> Vista. In theory it gets explained at length in "Changes to the file
> system and to the storage stack to restrict direct disk access and
> direct volume access in Windows Vista
Hi John,
On Apr 23 12:36, netbsdrat--- via Cygwin wrote:
>
> write() on 64 bit platform sometimes returns 32bit -1 as error indicator:
>
> Using 64 bit cygwin on 64 bit platform. Doing direct read() / write of
> disks,
> this example is using the /dev/floppy device.
>
write() on 64 bit platform sometimes returns 32bit -1 as error indicator:
Using 64 bit cygwin on 64 bit platform. Doing direct read() / write of
disks,
this example is using the /dev/floppy device.
Opening for writing floppy device using open() succeeds.
2 cases:
CaseA) write() a 512
4 matches
Mail list logo
