Custom Query (121 matches)

As far as I have seen and tried out - if you want to use system beeps instead of real sounds you can only use "!beep" for one single beep for an event. It would be very nice to be able to specify more than just one beep and differences in frequency and duration between different beeps - like it was possible in pwICQ, where you could specify a beep event like %frequency1,duration1,frequency2,duration2,.... (I always used %800,100,800,100,800,100,500,150 for example.) Any chance this could be added to the !beep parameter?

Hi dmik!

I still have problems with Psi leaking timers or at least using too many. You fixed the problems I had with quite a few applications when I first reported it. But I'm still having problems with one: FamilyTree? 1.2e (Buildt with VAC++ 3 - if that is helpful to know). Depending on how long Psi is running and on how many contacts are active or how many chats have been taken place FamilyTree? crashes or does not even start. Sometimes it crashes with "Feedback" : WINSTARTTIMER: UNK 20F9 E or just with a POPUPLOG Entry like this one:

01-14-2007 20:51:30 SYS3170 PID 00ac TID 0001 Slot 00e5 G:\FAMILYTREE\FTREE.EXE c0010001 1ffdc541 EAX=00000000 EBX=00623aac ECX=00222e70 EDX=001c358c ESI=00000000 EDI=00296a60 DS=0053 DSACC=f0f3 DSLIM=ffffffff ES=0053 ESACC=f0f3 ESLIM=ffffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC= GSLIM= CS:EIP=005b:001716f8 CSACC=f0df CSLIM=ffffffff SS:ESP=0053:002969ac SSACC=f0f3 SSLIM=ffffffff EBP=00296a1c FLG=00012202

DOSCALL1.DLL 0003:0000c541

(Don't know if that is of any help)

Not knowing what you did to improve the situation - may I ask if there is any more room for improvement? Any chance to check if Psi can be trained not to eat up that many timers?

Best regards Axel

files with umlaut can't be opened.
it's possible a djvulibre problem