Thanks Matt,
I have read this info, actually it is the reason I started looking for more
info. I can tell from the API how to set traps addresses however TrapWeaver
makes it sound very error prone. I wanted to know how the PalmOS does
things so I can better assure that my trap will not have problems. I notice
certain behaviors in the Palm OS traps that lead me to believe it is
possible to Trap address with out all the conflicts if it is done correctly.
For example the problem with traps getting added and deleted seems to be
addressed by PalmOS traps by issuing a soft reset when installing and
requiring a reset (with page-up to prevent the trap installation) before
deleting. This seems to make a lot of sense. But since HackMaster and
other programs remove set traps it is possible for conflicts. If we all
followed the rules that when a trap is set we force a reset then each trap
would install one at a time and it should work. That' my first impression
anyway. Of course trapping is error prone and conflicts can still occur if
apps trap the same address.
My main questions that I was hoping Palm might have documented are these
1) When I install a trap should I force a reset (I think Yes)
2) How do I require my trap be uninstalled before it is deleted (Like Palm
OS Patches)
3) How do I lock the memory address of the function that I will be setting
the trap to. It will be a very small part of my overall application.
Ron
-----Original Message-----
From: Matthew D Moss [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 07, 1999 5:15 PM
To: [EMAIL PROTECTED]
Subject: Re: Help Trapping the OS
> I want to write a trap of some OS calls without using HackMaster can
anyone
> point me to a source of information in the correct way to use
SysTrapAddress
> ? The doc's don't really cover it and the knowledge has very limited
info.
> Are there any good examples available ?
Yes, download TrapWeaver which discusses this sort of thing.
---- --- -- -
Matthew D Moss
[EMAIL PROTECTED]
