Re: [Harbour] Re: OT: with VirtualBox 2.0.6 Harbour Win apps can access shared folders files in Linux hosts

2008-11-25 Thread Lorenzo Fiorini
On Wed, Nov 26, 2008 at 5:27 AM, David Arturo Macias Corona <[EMAIL PROTECTED]> wrote: > In changelog of VBox 2.0.6 I do not see any change/fix related to the > problem with shared folders I couldn't find exactly where the problem was but I'm sure that only replacing 2.0.4 with 2.0.6 has fixed it

[Harbour] Re: OT: with VirtualBox 2.0.6 Harbour Win apps can access shared folders files in Linux hosts

2008-11-25 Thread David Arturo Macias Corona
>Since I've mentioned about this problem few weeks ago I'd like to >report that now with 2.0.6 it has been fixed. >Many thanks Sun. Lorenzo: In changelog of VBox 2.0.6 I do not see any change/fix related to the problem with shared folders In the case reported by me some weeks ago (included b

Re: [Harbour] hbapi.h and DWORD values

2008-11-25 Thread Randy Portnoff
It's working now with the DWORD cast - Thanks! At 11:00 AM 11/25/2008, you wrote: Hi, yes, of cause, you should have a DWORD variable DWORD lEAX = 0; hb_retnint( lEAX ); or cast it to DWORD, LONG lEAX = 0; hb_retnint( (DWORD) lEAX ); if you want to return DWORD value. Missing casting

Re: [Harbour] hbapi.h and DWORD values

2008-11-25 Thread Mindaugas Kavaliauskas
Hi, yes, of cause, you should have a DWORD variable DWORD lEAX = 0; hb_retnint( lEAX ); or cast it to DWORD, LONG lEAX = 0; hb_retnint( (DWORD) lEAX ); if you want to return DWORD value. Missing casting LONG lEAX = 0; hb_retnint( lEAX ); or casting it to LONG LONG lEAX = 0; hb_r

Re: [Harbour] hbapi.h and DWORD values

2008-11-25 Thread Randy Portnoff
Hi Mindaugas, Yes, that works - I was casting incorrectly at the C level. However, I have to cast as DWORD (not LONG) to get it to work. Here is what I am doing: LONG lEAX = 0; ... _asm{mov lEAX, eax} ... hb_retnint( (DWORD) lEAX ); As you can see, lEAX is set from the call stack via an _asm

Re: [Harbour] MT and hb_gtInfo() - Appln Locks

2008-11-25 Thread Przemyslaw Czerpak
On Fri, 21 Nov 2008, Pritpal Bedi wrote: Hi Pritpal, > > There is also yet another solution. You can create non HVM thread > > which will be used to create all windows and process their message > > queues. It will not make any other jobs so it will be always available > > and other threads which

[Harbour] 2008-11-25 02:14 UTC-0800 Pritpal Bedi ([EMAIL PROTECTED])

2008-11-25 Thread Pritpal Bedi
2008-11-25 02:14 UTC-0800 Pritpal Bedi ([EMAIL PROTECTED]) * harbour/contrib/gtwvg/hbgtwvg.ch * harbour/contrib/gtwvg/wvtwin.ch * harbour/contrib/gtwvg/wvggui.c * harbour/contrib/gtwvg/wvgwin.c * harbour/contrib/gtwvg/wvgax.prg * harbour/contrib/gtwvg/wvgphdlr.prg * harbour/contrib/g