johnl@ima.UUCP (09/22/85)
I am having a strange problem trying to make a program coexist with
SideKick and wonder if anybody has any suggestions.
What I have is a big program which, when it's time to draw a graph, loads
a graph driver program and then sends the picture to the printer using the
standard BIOS printer calls. (Going through DOS makes it about twice as
slow, which is one of the reasons why we don't.)
Normally, this works fine, but when SideKick is present, somehow a return
address or something gets bashed and it hangs. If I try to bring up
SideKick while it's printing, it crashes and burns right away. I tried to
make the stack bigger -- that didn't seem to help.
I know that SideKick does all sorts of morally reprehensible things and that
this is probably Borland's fault, but users are not going to be impressed by
that answer. Anybody have any experience in hardening code against SideKick's
depredations?
John Levine, Javelin Software, Cambridge MA 617-494-1400
{ decvax!cca | think | ihnp4 | cbosgd }!ima!johnl, Levine@YALE.ARPA
The opinions above are solely those of a 12 year old hacker who has broken
into my account, and not those of my employer or any other organization.