Maurilio:
>Error 8, that is ERROR_NOT_ENOUGH_MEMORY.
>With my last change, which uses a block obtained with a DosAlloc() with
>OBJ_TILE, that is a block aligned to a 64Kb segment, in low memory and
>with 16bit selectors set, it always works. This is on a SMP kernel
>searching for a file on a samba share, so going throug IBM LanManager
>(aka CIFS client) which is an old piece of code which might have some
>old 16bit/protect mode code inside.
>BTW, if we could be sure that some memory never goes to a DosXXX()
>call, we could add a OBJ_ANY to the call, making OS/2 use memory above
>the 512Mb limit that OBJ_TILE has; anyway, this is so a little
>improvement in every day code, I don't think it's worth the time I've
>spent writing about it here
>firefox 3.x for OS/2 has this code
>if (isWSEB)
>[...]
>So it seems newer kernels can/have to(?) use the FIL_STANDARDL flag
>but, maybe, they work with the old one as well (my kernel is the last
>one).
>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:
>----------------
>Information levels designated L should be used in order to get complete
> size information for files larger than 2GB. If information levels
>designated L are not used, a size of one byte will be returned for
>files which are >2GB in size.
>----------------
>Given that in harbour there is no (at the moment at least) 64bit file
>support for OS/2 I'd leave the current call.
>2010-03-02 16:15 UTC+0100 Maurilio Longo (maurilio.longo at libero.it)
> * src/common/hbffind.c
> * hb_fsFindNextLow() to work reliably in my environment needs
> OBJ_TILE memory. I've found no documentation about this
> issue, maybe it's caused by old LAN Manager code when searching
> for files on network shares.
0) I do not know/understand what mean information above
1) so, I do not know how your changes/considerations impact rest of OS/2
users ( you are now aware we are many :-) )
2) Based on that, I make some comments:
2.a) Is convenient to follow firefox path ? I think yes
So you can manage old and new kernels
2.b) Is convenient to manage files larger than 2 Gb ? I think yes
2.c) Can you prepare to manage "64bit file support" ? I think yes
So you will be ready for future :-)
2.d) I know you are aware of every movement which happen in OS/2 world,
and maybe you tested already, ... but maybe no
Days ago I removed "NETBIOS over TCP/IP" and installed .wpi files for
Samba 3.0.37, from NetLabs
( Samba Server version 3.0.37 for eComStation (OS/2) 1.0.3 )
- Migrated shares
- Everything is working fine to/from OS/2 and WinXPPSP2, Linux Mandriva
- Problems with shares/visibility between OS/2 and rest are gone
So as in this way we do not have: "... going throug IBM LanManager (aka
CIFS client) ..." I do not know if Harbour need some adjustment related
to samba and/or 2Gb and/or 64bit files and/or your recent change
David Macias
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
