SP>I'm having a problem with the TSR capabilities of PowerBASIC.
        I've had a few myself.  Not the least of which is that I am
        ticked that POPUP INTERRUPT &H17 doesn't work....
SP>My TSR works fine when popped-up from the DOS prompt, but it
SP>really screws things up when I try popping it up over another
SP>program.  Then when I try to run it a second time, it uninstalls
SP>itself.
        This sounds like you need to put the POPUP SLEEP into a DO LOOP
        like this:
        DO
                POPUP SLEEP
                ' Tsr code goes here
        LOOP    ' Loop back and goto sleep
        This will make your TSR run forever, popping up and down when
        the POPUP event occurs.
SP>The example TSR (ASCTSR.BAS) works fine, and I used the same code to
SP>at the beginning of my program, so I'm not sure what the problem
SP>could be.  My program does, however, use a sequential-access file
SP>to load some data.  Could that be the problem?  And if so, is there
SP>some way I can get around it?
        Did you make certain to close the file and FLUSH before popping
        down?  Leaving a DOS file open or not flushing before popping
        down has created troubles for me in the past.
SP>I tried writing to PowerBASIC (dnavarro@powerbasic.com) but never
SP>got a reply...
        That could be for one of three reasons:
        1.  Dave and the PB staff are busy getting PB/DLL up to par for
        its impending release,
        2.  TSR's are tricky, even when written under PowerBASIC, and
        you may not have described enough of the details for the PB
        techies to discern the problem.
        3.  They don't know what the problem is (see 2 above) and don't
        want to make suggestions that aren't likely to help you.
        In the past, when I've contacted the PB support staff, they have
        responded quickly to my messages, faxes, etc., **IF** I am very
        clear about what has caused the problem.  If I just say, "my
        program broke under version 3.2" I am likely (and I did!) to get
        a reply like, "99.9% of bug reports are really user error".
        That reply miffed me, so I set out to write code that duplicated
        my problem in a minimum number of lines.  I then voice phoned
        Dave Navarro, and told him I would send the source that produced
        the error by fax.  Ten minutes later, he called back and
        informed me that what I had described was a known 3.2 bug, and
        that the tech staff had discovered it a week earlier.
        When it comes to tech supporting a language in which one could
        write a missile launcher or a coffee maker driver -- well, you
        must imagine how cryptic messages like "I have a TSR problem"
        come across to tired eyes.
        Try to isolate your problem to a specific section of code, and
        if you cannot figure it out past that, cut out that piece of
        code, write a preamble, if you can, post it here, and then we
        will be better prepared to help.
        In the meantime, keep the faith.  PowerBASIC is best!  I've
        spent hundreds of hours digging into the internals of PB, and
        I'm still coming across little undocumented features....
Jamshid
--- Maximus/2 2.01wb
---------------