I have a serious problem about a week.

The class XbpFileDialog in debug mode does not work anymore and gives me 
the error listed on the attachment.

I repeated the test on 3 different PCs with the same result with all 
Xbase 1.9.331 and Windows XP sp3

With Windows 7 works regularly with Xbase 1.9.331 with 1.9.335 but gives 
me an error Library not registered!?

Does anyone have an idea about ...

Carlo Giudice

( sorry for bad english )

hi,

>I have a serious problem about a week.

what did you do 1 Week ago ?

> With Windows 7 works regularly with Xbase 1.9.331 with 1.9.335 but gives
> me an error Library not registered!?

you have both Version .331 and v355 installed? how do you "switch" between?

you have VX installed ... how many Version ?
... and "where" do you install it?

what does
"HKEY_CURRENT_USER\Software\Alaska Software\Visual Xbase++\2.0\Directories"
say ?

you can not run v331 EXE Sample within VX when VX is installed in v355
Directory. Use v355 EXE Sample Directory and/or recompile it

have a look for your Environment for PATH, LIB etc

use XPPLOAD.EXE and look for Version and Path

perhaps Anti-Virus ?

greetings by OHR
Jimmy

Thanks for your interest

> what did you do 1 Week ago ?
are 10 years of use XBase + + and if I knew I would have solved the problem 
..... 

> you have both Version .331 and v355 installed? how do you "switch" 
> between?
Use the command subst X: D:\ALASKAnn, but now I'm focusing to resolve the 
problem on Windows XP, because that is what I use at work.

To test the problem I used XPPDBG.EXE and enclose the result of tests with 
both 1.9.331 that 1.9.335, recompiling the program each time.

I have excluded VX to reduce complications
I disabled the antivirus and Windows Firewall.
The same tests I made on another PC (just reformatted) always with the same 
results.

I noticed that the log file there are variables with strange characters
oError:args         :
          -> VALTYPE: C VALUE: _DLL  6vY06v A
          -> VALTYPE: C VALUE: X    
                 
    ?  
?T? ^

... (you must use hex editor to see them)

Working without debugging is very difficult.

Carlo Giudice

( My English is translated from Italian by Google)

hi,

looking at your XppLoad Logfile i saw

VX20.EXE, 2006-04-27 11:15:36,    58368, 1.90.331,X:\XPPW32\BIN\,V
VX20.EXE, 2006-04-27 11:15:36,    58368, 1.90.331,X:\XPPW32\BIN\,V
VXBRIDGE10.DLL, 2006-04-27 11:15:58,   120320, 0.00.  0,X:\XPPW32\BIN\
VXBRIDGE10.DLL, 2006-04-27 11:15:58,   120320, 0.00.  0,X:\XPPW32\BIN\
VXCLASS10.DLL, 2006-05-04 17:07:44,  1063424, 0.00.  0,X:\XPPW32\BIN\
VXCLASS10.DLL, 2006-05-04 17:07:44,  1063424, 0.00.  0,X:\XPPW32\BIN\
VXDBD10.DLL, 2006-04-27 11:16:12,   381952, 0.00.  0,X:\XPPW32\BIN\
VXDBD10.DLL, 2006-04-27 11:16:12,   381952, 0.00.  0,X:\XPPW32\BIN\
VXDBGCMD10.DLL, 2006-04-27 11:16:32,    14848, 0.00.  0,X:\XPPW32\BIN\
VXDBGCMD10.DLL, 2006-04-27 11:16:32,    14848, 0.00.  0,X:\XPPW32\BIN\
VXDOT10.DLL, 2006-04-27 11:16:36,    36352, 0.00.  0,X:\XPPW32\BIN\
VXDOT10.DLL, 2006-04-27 11:16:36,    36352, 0.00.  0,X:\XPPW32\BIN\
VXIDE20.EXE, 2006-04-27 11:15:48,  3911680, 0.00.  0,X:\XPPW32\BIN\
VXIDE20.EXE, 2006-04-27 11:15:48,  3911680, 0.00.  0,X:\XPPW32\BIN\
VXIDECMD10.DLL, 2006-04-27 11:16:42,    10752, 0.00.  0,X:\XPPW32\BIN\
VXIDECMD10.DLL, 2006-04-27 11:16:42,    10752, 0.00.  0,X:\XPPW32\BIN\
VXIHL10.DLL, 2006-04-27 11:16:24,   203776, 0.00.  0,X:\XPPW32\BIN\
VXIHL10.DLL, 2006-04-27 11:16:24,   203776, 0.00.  0,X:\XPPW32\BIN\

all are 2x ...

>Use the command subst X: D:\ALASKAnn

you forgot Registry Key so Debugger will not work correct.
i do "switch" Environment and Registry Keys each Time between v331 / v355

greetings by OHR
Jimmy

I found the problem!

AVIRA 10, stop debugging and sending error in the function.

It is not enough to disable it but you need to uninstall it!

Now I'll try news for this compatibility problem to continue using AVIRA.

Carlo

"AUGE_OHR" <AUGE_OHR*AT*WEB.DE> ha scritto nel messaggio 
news:28eebd49$4603aaec$11a79@news.alaska-software.com...
> hi,
>
> looking at your XppLoad Logfile i saw
>
> VX20.EXE, 2006-04-27 11:15:36,    58368, 1.90.331,X:\XPPW32\BIN\,V
> VX20.EXE, 2006-04-27 11:15:36,    58368, 1.90.331,X:\XPPW32\BIN\,V
> VXBRIDGE10.DLL, 2006-04-27 11:15:58,   120320, 0.00.  0,X:\XPPW32\BIN\
> VXBRIDGE10.DLL, 2006-04-27 11:15:58,   120320, 0.00.  0,X:\XPPW32\BIN\
> VXCLASS10.DLL, 2006-05-04 17:07:44,  1063424, 0.00.  0,X:\XPPW32\BIN\
> VXCLASS10.DLL, 2006-05-04 17:07:44,  1063424, 0.00.  0,X:\XPPW32\BIN\
> VXDBD10.DLL, 2006-04-27 11:16:12,   381952, 0.00.  0,X:\XPPW32\BIN\
> VXDBD10.DLL, 2006-04-27 11:16:12,   381952, 0.00.  0,X:\XPPW32\BIN\
> VXDBGCMD10.DLL, 2006-04-27 11:16:32,    14848, 0.00.  0,X:\XPPW32\BIN\
> VXDBGCMD10.DLL, 2006-04-27 11:16:32,    14848, 0.00.  0,X:\XPPW32\BIN\
> VXDOT10.DLL, 2006-04-27 11:16:36,    36352, 0.00.  0,X:\XPPW32\BIN\
> VXDOT10.DLL, 2006-04-27 11:16:36,    36352, 0.00.  0,X:\XPPW32\BIN\
> VXIDE20.EXE, 2006-04-27 11:15:48,  3911680, 0.00.  0,X:\XPPW32\BIN\
> VXIDE20.EXE, 2006-04-27 11:15:48,  3911680, 0.00.  0,X:\XPPW32\BIN\
> VXIDECMD10.DLL, 2006-04-27 11:16:42,    10752, 0.00.  0,X:\XPPW32\BIN\
> VXIDECMD10.DLL, 2006-04-27 11:16:42,    10752, 0.00.  0,X:\XPPW32\BIN\
> VXIHL10.DLL, 2006-04-27 11:16:24,   203776, 0.00.  0,X:\XPPW32\BIN\
> VXIHL10.DLL, 2006-04-27 11:16:24,   203776, 0.00.  0,X:\XPPW32\BIN\
>
> all are 2x ...
>
>>Use the command subst X: D:\ALASKAnn
>
> you forgot Registry Key so Debugger will not work correct.
> i do "switch" Environment and Registry Keys each Time between v331 / v355
>
> greetings by OHR
> Jimmy
>

This is the solution:
You must enable AVIRA10 "low level detection heuristic analysis"