Re: The fread() that could.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Sigurd Stenersen (sigurds_at_utvikling.com)
Date: 10/08/04

Next message: L. Spiro: "Re: The fread() that could."
Previous message: L. Spiro: "The fread() that could."
In reply to: L. Spiro: "The fread() that could."
Next in thread: L. Spiro: "Re: The fread() that could."
Reply: L. Spiro: "Re: The fread() that could."
Messages sorted by: [ date ] [ thread ]

Date: Fri, 8 Oct 2004 17:40:41 +0200

L. Spiro wrote:
> fopen() works in both threads. Then in one thread or the other,
> fread() simply fails.
>
> In both cases the file is fopen()'ed with "rb" flags.

I never use the stream i/o stuff myself, but I think you'll find _fsopen()
more useful than fopen() for what you're trying to do.

-- 
Sigurd
http://utvikling.com

Next message: L. Spiro: "Re: The fread() that could."
Previous message: L. Spiro: "The fread() that could."
In reply to: L. Spiro: "The fread() that could."
Next in thread: L. Spiro: "Re: The fread() that could."
Reply: L. Spiro: "Re: The fread() that could."
Messages sorted by: [ date ] [ thread ]

Relevant Pages

Re: FREAD fails on files >4GB
... Problem with the freadcall on MS Visual Studio 2005 running under ... The parameters to fread size and count are both size_t ie 64 bits. ... Even so the call fails when the size arg is greater than 4GB (ie ...
(comp.lang.c)
Re: FREAD fails on files >4GB
... Problem with the fread() call on MS Visual Studio 2005 running under Win 64. ... so the call fails when the size arg is greater than 4GB (ie exceeds 32 ...
(comp.lang.c)