Przemyslaw,
Przemysław Czerpak wrote:
> On Mon, 08 Mar 2010, Maurilio Longo wrote:
>
> I believe that you are right but test on shared volumes is not an answer
> because it may depend on host system behavior which can be different then
> native OS2 one so it would be nice if you can verify it for
On Mon, 08 Mar 2010, Maurilio Longo wrote:
Hi,
> Przemysław Czerpak wrote:
> > The description suggests that files with attribute READONLY or ARCHIVE are
> > not shown if MAY bits are not set. It's not Clipper compatible behavior.
> > So it should be definitely fixed or the description is wrong.
Przemyslaw,
Przemysław Czerpak wrote:
> The description suggests that files with attribute READONLY or ARCHIVE are
> not shown if MAY bits are not set. It's not Clipper compatible behavior.
> So it should be definitely fixed or the description is wrong.
>
I think description is wrong, see
MUST_
On Tue, 02 Mar 2010, Maurilio Longo wrote:
Hi,
> > Also seems that flAttribute parameter has wrongly value.
> > Without ORing with FILE_ARCHIVED and FILE_READONLY files with above
> > attribute should be excluded.
> >
> bits 5..0 are MAY-have, that is, file name is returned either it has that
>
Ok,
I've found out :)
I have version 4.0 toolkit documentation, that is, OS/2 Warp4 level, the
lastest is 4.5, in 4.5 documentation you can read:
-8<---
Information levels designated L should be used in order to get complete size
information for files larger than 2GB. If information
BTW,
firefox 3.x for OS/2 has this code
if (isWSEB)
{
rc = DosFindFirst( filename,
&d->d_hdl,
FILE_DIRECTORY | FILE_HIDDEN,
&(d->d_entry.large),
sizeof(d->d_entry.large),
Przemysław Czerpak wrote:
> I cannot help you here. Information about DosFindFirst() in OS2 returned
> by google suggest that our implementation should not work correctly, i.e.:
>
>Level 1 File Information (ulInfoLevel == FIL_STANDARD)
>On output, pfindbuf contains the FILEFINDBUF3 data st
On Mon, 01 Mar 2010, Maurilio Longo wrote:
Hi,
> I'm facing an error on OS/2 which I'm beginning to suspect it is due to the
> fact that we're not allocating the correct type of memory when calling
> DosFindFirst().
I cannot help you here. Information about DosFindFirst() in OS2 returned
by goog
Przemyslaw,
I'm facing an error on OS/2 which I'm beginning to suspect it is due to the
fact that we're not allocating the correct type of memory when calling
DosFindFirst().
Now, can you tell me if _all_ memory allocations, made via hb_xgrab(), when
using dlmalloc.c go through dlmalloc.c line 13