How can I use a calling card automatically while I am roaming?
How can I use a calling card when I am not roaming?
Can I use different calling cards for different phone numbers?

Cheers
Chris

Hi Folks!

I recently bought TealLaunch for one specific feature - pressing and holding
hard buttons
to launch alternate applications - and I'm thrilled with it. I'm regularly
switching between
six main applications on my Treo, and this addition makes the process very
fluid. Here's
what I love about the press and hold feature:

- it's intuitive (using hard buttons to launch applications is built-in, and
this is a natural
extension behaviorally)
- single button access (using the Treo's option-hard button feature requires
finding two
different buttons every time I switch applications; TealLaunch's press and hold
requires
finding only one button)
- adds functionality without interfering with built-in features (I can still use
built-in
features like pressing a button to change memo categories or calendar views, as
well as
the standard option-press feature to launch less frequently used applications)
- no wasted time (the built-in press and hold feature of the Treo's side button
has an
unnecessarily long delay, leaving me feeling like I'm waiting for the machine
every time I
use it; TealLaunch's press and hold delay is long enough to clearly distinguish
from
regular presses, yet short enough that I don't feel like I'm wasting time
waiting for a
response)
- visual & audible feedback (clear signals when a state has changed due to the
passage of
time)

I like this so much that I'm writing to ask for an extension to this feature.
There are two or
three more applications that I expect to begin using regularly, and I would love
to be able
to access them just as fluidly. But I've run out of hard buttons to assign this
press and
hold feature to.

I would love to see the Launch Application action extended such that when
triggered it
would bring up a popup menu (not a regular menu, and not a dialog) in the upper
left
corner of the screen listing one or more applications (however many the user
assigned to
this particular trigger) with the first one selected/ highlighted. If this
action were attached
to a press and hold trigger, the popup would automatically highlight the next
selection in
the list at half second intervals (delay subject to usability testing) for as
long as the button
is held down, cycling back to the top of the list whenever it passes the last
item. Whichever
application is highlighted when the user releases the button is the one that
gets launched.

This provides a very elegant way to get to even more applications in a flash. It
provides all
the key benefits listed above that make the existing press and hold feature so
valuable,
while extending its capability even further. Here are some key points:

- user should be able to assign a different list of applications to each trigger
(thus
expanding the total number of applications that can be quickly accessed)
- user should be able to control the order of applications on each list (most
frequently
used applications should be at the top of each list for the shortest delay)
- assigning a single application to an application list would essentially work
the same as
Launch Application currently works, except for the added appearance of the
single-item
popup showing what application is being launched

Functionality would be modified slightly for triggers that do not involve
holding button(s)
down. A simple approach could be to only ever launch the first application on
the list,
ignoring the rest of the list, and never showing the popup menu. A more
sophisticated
approach could involve bringing up the popup menu on the first press, with the
first
application highlighted, and leaving it up for a half second or so. If user
pressed the same
button again within that half second, the next application in the list would be
highlighted,
and another half second timeout would begin. Whichever application in the list
is
highlighted when the user allows the popup to timeout would be the application
that's
launched.

I don't know how complicated these things would be to develop, or what other
issues
might need to be addressed, but I'm excited about the prospect of extending this
magical
press and hold capability even further.

Thanks for a great product. And thanks for even considering this proposal.

Eric

Hi Folks!

Another suggestion, if I may...

I see that you've added the Home and Menu buttons to the Treo-specific list of
triggers in
TealLaunch, which I appreciate. Would you also consider adding Hold Menu, Hold
Home, and
Hold Voice triggers for this device? I would like the added launch capabilities
without taking
away any built-in features. (I realize the Treo already has Hold Voice built-in,
but the built-in
delay is noticeably longer than that of TealLaunch - to the point of being
annoying.)

Many Thanks,

Eric

Could you please give me more info about this TX NVFS system bug? I just ordered
a Palm TX
from Amazon to replace my pokey LifeDrive...

From the beta page:

> TealTools 1.23
> Beta 1.23 - May 5, 2006
> Fixed TealPad to save database to flash memory on Palm TX (works around
> TX NVFS system bug)

Thanks,

Joseph Maddison
Minneapolis, MN
jdmaddison@...

Hi,
Using either the keyboard or the index in TPhone468, the letter "a"
doesn'st function in any lookukp situation. I've tried soft reset to
no avail. Anyone else? I'm using a Palm TX
alan

--

---
Tried earlier betas(4.62) with the same problem. No problem using the
built in contacts db or other programs with keyboard
lookup(splashshopper etc.)

In tealtalk@yahoogroups.com, "Alan" <aashrink@...> wrote:
>
> Hi,
> Using either the keyboard or the index in TPhone468, the letter "a"
> doesn't function in any lookup situation. I've tried soft reset to
> no avail. Anyone else? I'm using a Palm TX
> alan
>
> --
>

Hi.

--- In tealtalk@yahoogroups.com, Joseph Maddison <jdmaddison@...>
wrote:
>
> Could you please give me more info about this TX NVFS system bug?
I just ordered a Palm TX
> from Amazon to replace my pokey LifeDrive...


There are three issues on the TX that appear to be due to
new "optimizations" PalmSource made to how the NVFS system works.
While not all strictly bugs, they tend to create as many or more
problems than they solve.

1) In previous versions of NVFS, if an application left a record
handle locked, the system would regard the record as "in use" and
would keep it in the DBCache.  Some programs, however, would forget
to unlock some data records, and this would cause the DBCache to
fill up with locked records until the machine was completely bogged
down and slow.

On the TX, the NVFS system doesn't regard keep "locked" records in
memory unless the database is also protected.  While this keeps
those "orphan" records mentioned above from filling up the cache, it
causes a worse problem.  It causes many hacks and background apps to
be flushed from memory when they are still hooked up to system
notifications, causing crashes when those notifications (for user
interaction, timers, hotsync, etc) are called.  We think this was a
dumb change, since PalmOS has a list of the registered notification
handlers and could just as easily cross reference the callback
addresses with blocks it wants to flush, and keep the crashes from
happening at all.

2) The NVFS system on the TX attempts to speed up caching by
limiting the instances in which changes are flushed back to flash
memory.  We've found that in a few instances that it was not copying
changes back to flash memory, resulting in "lost" information after
a soft reset.  In TealMaster and TealPad, we were able to "force"
data to be flushed to flash by copying an existing data record and
then deleting the original record, but ideally this should not be
necessary if the new NVFS system were better designed.

3) There appears to be a more serious related system bug where the
system Saved Preferences database seems to lose data records,
causing various program settings, options and registration states to
be lost after a soft reset.  We've seen this many times on our own
TX, but not on other devices.  It acts as if some preference changes
are never being copied back to flash memory, causing applications to
act after a reset as if they are being run for the first time.  With
no official fix or acknowledgement of this as a system bug, we've
resulted to using PreferenceDoctor (www.hobbyistsoftware.com) to
backup and automatically restore our preference database.

-tex

---
I tried the other betas(4.60,1,2 & 8) that I have and all have the
same issue. V 4.51 is fine- No problems.
I sent Tex my database and he is going to test that.
alan

In tealtalk@yahoogroups.com, "Alan" <aashrink@...> wrote:
>
> ---
> Tried earlier betas(4.62) with the same problem. No problem using the
> built in contacts db or other programs with keyboard
> lookup(splashshopper etc.)
>
> In tealtalk@yahoogroups.com, "Alan" <aashrink@> wrote:
> >
> > Hi,
> > Using either the keyboard or the index in TPhone468, the letter "a"
> > doesn't function in any lookup situation. I've tried soft reset to
> > no avail. Anyone else? I'm using a Palm TX
> > alan
> >
> > --
> >
>

--- In tealtalk@yahoogroups.com, "Eric" <epsextra@...> wrote:
>
Hi Eric,
The beauty of TL. I think, is that these wishes could be implemented
such that one can 'program' a similar behavior. If I understand the
request, much of it can be implemented if TL would allow a <scroll
page down> while TL is open. Your select-app-on-release could be done
by a allowing a <keyX release> action on apps buttons.

Personally I don't mind hitting a second key and I use TL's quick key
feature a lot. But I would support a request  for a <scroll page
down/up> action on apps buttons for those apps that I want to select
visually.

In that case I'd program:
   when TL  closed / open
Home         <open>                 <scroll down>
Home hold <app launcher>       <scroll up>
> Hi Folks!
>
...[text deleted]....> I would love to see the Launch Application
action extended such that when triggered it
> would bring up a popup menu (not a regular menu, and not a dialog)
in the upper left
> corner of the screen listing one or more applications (however many
the user assigned to
> this particular trigger) with the first one selected/ highlighted.
If this action were attached
> to a press and hold trigger, the popup would automatically highlight
the next selection in
> the list at half second intervals (delay subject to usability
testing) for as long as the button
> is held down, cycling back to the top of the list whenever it passes
the last item. Whichever
> application is highlighted when the user releases the button is the
one that gets launched...[text deleted]...
> Eric
>

Hi Dick,

Thanks for the thoughtful reply.

What I love about the existing press and hold feature is its simple, fluid
elegance - press,
pause, and release. This is literally the only TealLaunch feature I use, and
it's precisely
because it is so transparent to my workflow. I press a single button, hold it
there just long
enough to clearly distinguish from a momentary press, and then release - and up
comes
my alternate applicaton.

The extension I've proposed makes only a tiny tweak to this very natural
behavior - a
slightly longer pause. During that pause, a popup list of say 3-4 applications
remains
displayed, and the highlighted selection in the list cycles from one item to the
next in very
short intervals. Releasing the held button launches whatever application was
highlighted in
the list. The elegance of the existing press and hold feature is preserved,
while extending
its functionality significantly. And since each trigger could have its own list
of 3-4
applications (more could make the delay too long), the number of applications
that could
be launched this conveniently would increase dramatically.

As far as I can see, trying to accomplish this via the TealLaunch dialog
compromises this
approach in at least two ways. First and most important, the elegance of a
single step
solution (press, pause, release) is lost. One press and release is required to
open the
TealLaunch dialog, and at least one more press and release would be required to
select
and launch another application - even if they added the ability to automatically
cycle
through the application list there. Second, using the TealLaunch dialog limits
the user to a
single application list. Having several short application lists keeps the pauses
short, which
is also critical to keeping this fluid.

It may sound like I'm dealing in subtleties here, but it's those subtleties that
make me so
passionate about the existing press and hold feature. As I described in my
original post,
there are several very specific aspects to this existing feature that, together,
make it so
compelling. I just think this minor tweak could make its potential explode.

Eric

--- In tealtalk@yahoogroups.com, "dfikkert" <dick.fikkert@...> wrote:
> Hi Eric,
> The beauty of TL. I think, is that these wishes could be implemented
> such that one can 'program' a similar behavior. If I understand the
> request, much of it can be implemented if TL would allow a <scroll
> page down> while TL is open. Your select-app-on-release could be done
> by a allowing a <keyX release> action on apps buttons.
>
> Personally I don't mind hitting a second key and I use TL's quick key
> feature a lot. But I would support a request  for a <scroll page
> down/up> action on apps buttons for those apps that I want to select
> visually.
>
> In that case I'd program:
>   when TL  closed / open
> Home         <open>                 <scroll down>
> Home hold <app launcher>       <scroll up>
>

Ahhh!
The  issue I had with the later betas of TealPhone have been resolved
thanks to Tex. He worked with me with no complaints(other than some
unseen eye rolls, I'm sure:-)) for a few days till the problem was
fixed. Maybe that's why, between my wife and me, we have 13 registered
Teal programs.
Anyway, v4.69b works as the way it should.
Thanks, Tex.
alan

I have been using Teal Auto for years, but am slowly getting dis
heartened that such a great app doesn't yet ahve a desktop companion.

Often I want to be able to reconcile my budget on my PC and would like
to be able to get great looking graphs and stats (I have five years
worth of data on numerous vehicles) on my desktop.  Not only that, but
it would be great to have QIF support or similar so I can integrate
into my budgeting software.

Why don't Teal add the same functionality that Splash Data does with
their products?

First, the new beta fixes some photo and group issues -- try it!

Now my suggestions:

1. Under the Search options; a date and date range search for birthdays.
2. Under Printing; Ability to print other contact fields like main
contact phone with E-mail.
3. Related to #2; Export Search found set to Memo.

Thanks for a great product!

Steve

I'm a new Palm TX owner, and although I haven't experienced data loss
with the Tx or its predecessor (IIIC), I think that it would be wise
to purchase a backup program.  I've been looking at Tealpoint's backup
competitors, including a freeware application, and noted that
TealBackup is pricier than some of the more popular applications.  Is
it worth it?

> TealBackup is pricier than some of the more popular applications.  Is
> it worth it?

It has some interesting features, such as the ability to schedule automatic
backups and to
backup to an incrementally named directory, as well as data compression and
encryption, if
I remember accurately.

Unfortunately, I found it unusable with my LifeDrive, as it turned out, due to
the
inherent instability of the LD. I would get nasty behavior such as a reboot as
soon as I
turned *on* the LD. Four minutes later, it would finally come back from booting.
(What a
machine!) Though it technically was some other app conflicting, the problem went
away
when I disabled the automatic backup in TealBackup.

Even worse, I once managed to misconfigure TealBackup so it backed up main
memory *to*
main memory though it looked like they were two different places. It eventually
got to
the point with the automatic backup where memory was full, causing a fault where
rebooting causes an immediate reboot. Unless you are quite technically inclined,
it takes
a hard reset (losing all your data, including the LD's built-in hard drive's
data) to get
out of it.

I have just recently switched to a TX. The difference in speed is fantastic! No
longer
does it take 10+ seconds each time to switch to another app! Unbelievable!

However, I see that the file system displayed in TealMover on the TX (and
presumably in
TealBackup as well) still has the same funky characteristic-- the far-left
silicon chip
icon *and* the first sd chip icon next to it refer to the same memory space in
different
ways. Trust me, you don't want to backup one to the other!

For me, TealBackup was *not* worth it, but maybe on the TX (with my caveat), it
will be
usable now. TealMover, on the other hand, has been unbelievably useful. It
should be
built directly into PalmOS. Why doesn't every Palm have a built-in app that can
create
and remove directories, copy and move files, even between main memory and memory
cards?

You may find that simply using TealMover will work just as well, maybe better
for you
thann TealBackup.

Regards,

Joseph Maddison
Minneapolis, MN

licensed: TealMover / TealScript / TealLauncher / TealMaster / TealAuto /
TealAlias /
TealBackup (TealLauncher/TealMaster and TealAlias were mainly to work around the
dreadful
slowness of the LD, with limited success).

> You may find that simply using TealMover will work just as well, maybe
> better for you
> thann TealBackup.
>
> Regards,
>
> Joseph Maddison


Thanks for the info, Joseph!
Mary

I found two free applications that solve this problem...
One is Resco Locker...
the other is Off Flush... Again both of these are free.

RLock is great.

Just started testing of Off Flush, do not turn on flush when turn off
palm, unless you are willing to wait for it to do it thing...

Since I started using these my Palm LifeDrive is stable and all Teal
products that I own work great with these. TealLock, TealLaunch,
TealMaster and TealTools.

Thanks for updating TealTools... I use it more now...

J
--- In tealtalk@yahoogroups.com, tealtex <no_reply@...> wrote:
>
> Hi.
>
> --- In tealtalk@yahoogroups.com, Joseph Maddison <jdmaddison@>
> wrote:
> >
> > Could you please give me more info about this TX NVFS system bug?
> I just ordered a Palm TX
> > from Amazon to replace my pokey LifeDrive...
>
>
> There are three issues on the TX that appear to be due to
> new "optimizations" PalmSource made to how the NVFS system works.
> While not all strictly bugs, they tend to create as many or more
> problems than they solve.
>
> 1) In previous versions of NVFS, if an application left a record
> handle locked, the system would regard the record as "in use" and
> would keep it in the DBCache.  Some programs, however, would forget
> to unlock some data records, and this would cause the DBCache to
> fill up with locked records until the machine was completely bogged
> down and slow.
>
> On the TX, the NVFS system doesn't regard keep "locked" records in
> memory unless the database is also protected.  While this keeps
> those "orphan" records mentioned above from filling up the cache,
it
> causes a worse problem.  It causes many hacks and background apps
to
> be flushed from memory when they are still hooked up to system
> notifications, causing crashes when those notifications (for user
> interaction, timers, hotsync, etc) are called.  We think this was a
> dumb change, since PalmOS has a list of the registered notification
> handlers and could just as easily cross reference the callback
> addresses with blocks it wants to flush, and keep the crashes from
> happening at all.
>
> 2) The NVFS system on the TX attempts to speed up caching by
> limiting the instances in which changes are flushed back to flash
> memory.  We've found that in a few instances that it was not
copying
> changes back to flash memory, resulting in "lost" information after
> a soft reset.  In TealMaster and TealPad, we were able to "force"
> data to be flushed to flash by copying an existing data record and
> then deleting the original record, but ideally this should not be
> necessary if the new NVFS system were better designed.
>
> 3) There appears to be a more serious related system bug where the
> system Saved Preferences database seems to lose data records,
> causing various program settings, options and registration states
to
> be lost after a soft reset.  We've seen this many times on our own
> TX, but not on other devices.  It acts as if some preference
changes
> are never being copied back to flash memory, causing applications
to
> act after a reset as if they are being run for the first time.
With
> no official fix or acknowledgement of this as a system bug, we've
> resulted to using PreferenceDoctor (www.hobbyistsoftware.com) to
> backup and automatically restore our preference database.
>
> -tex
>

Thanks for the great info.  If I may help clarify when I think you
might want to use these apps:

The locking program you mention sounds like the same as the "locked
application" feature that we have in TealBackup.  A good idea to
stabilize those background apps that haven't properly locked
themselves down to run on NVFS devices like the TX or Lifedrive.
This prevents the crashes that occur after accessing/copying large
files or many smaller files because you have bad background apps
running that haven't properly done all the necessary steps to tell
NVFS that they shouldn't be moved during a DBCache shuffle/flush.

Still, I wish Palm or somebody else would write a simple app that
would detect "bad" applications.  It could just scan the PalmOS
notification list and just look for any apps that registered for
notifications via a callback pointer to an unlocked block of
memory.  This would require inside knowledge of PalmOS's inner
workings, but should be easy for an insider to write.

The "flush" application, I believe, is useful to prevent problems
from the opposite problem: apps that accidentally leave data locked
so that it stays in the cache, filling it up until the system slows
down and gets unstable.  It's interesting to note that my guess is
that the second (flush) app would instantly cause a crash if you
have "bad" apps that need to locked down with the first (locker) app.

Note that I haven't used either utility, but this is based on our
experience with instabilities on NVFS devices.

-tex


--- In tealtalk@yahoogroups.com, "jdebay" <jdebay@...> wrote:
>
> I found two free applications that solve this problem...
> One is Resco Locker...
> the other is Off Flush... Again both of these are free.
>
> RLock is great.
>
> Just started testing of Off Flush, do not turn on flush when turn
off
> palm, unless you are willing to wait for it to do it thing...
>
> Since I started using these my Palm LifeDrive is stable and all
Teal
> products that I own work great with these. TealLock, TealLaunch,
> TealMaster and TealTools.
>
> Thanks for updating TealTools... I use it more now...
>
> J
> --- In tealtalk@yahoogroups.com, tealtex <no_reply@> wrote:
> >
> > Hi.
> >
> > --- In tealtalk@yahoogroups.com, Joseph Maddison <jdmaddison@>
> > wrote:
> > >
> > > Could you please give me more info about this TX NVFS system
bug?
> > I just ordered a Palm TX
> > > from Amazon to replace my pokey LifeDrive...
> >
> >
> > There are three issues on the TX that appear to be due to
> > new "optimizations" PalmSource made to how the NVFS system
works.
> > While not all strictly bugs, they tend to create as many or more
> > problems than they solve.
> >
> > 1) In previous versions of NVFS, if an application left a record
> > handle locked, the system would regard the record as "in use"
and
> > would keep it in the DBCache.  Some programs, however, would
forget
> > to unlock some data records, and this would cause the DBCache to
> > fill up with locked records until the machine was completely
bogged
> > down and slow.
> >
> > On the TX, the NVFS system doesn't regard keep "locked" records
in
> > memory unless the database is also protected.  While this keeps
> > those "orphan" records mentioned above from filling up the
cache,
> it
> > causes a worse problem.  It causes many hacks and background
apps
> to
> > be flushed from memory when they are still hooked up to system
> > notifications, causing crashes when those notifications (for
user
> > interaction, timers, hotsync, etc) are called.  We think this
was a
> > dumb change, since PalmOS has a list of the registered
notification
> > handlers and could just as easily cross reference the callback
> > addresses with blocks it wants to flush, and keep the crashes
from
> > happening at all.
> >
> > 2) The NVFS system on the TX attempts to speed up caching by
> > limiting the instances in which changes are flushed back to
flash
> > memory.  We've found that in a few instances that it was not
> copying
> > changes back to flash memory, resulting in "lost" information
after
> > a soft reset.  In TealMaster and TealPad, we were able
to "force"
> > data to be flushed to flash by copying an existing data record
and
> > then deleting the original record, but ideally this should not
be
> > necessary if the new NVFS system were better designed.
> >
> > 3) There appears to be a more serious related system bug where
the
> > system Saved Preferences database seems to lose data records,
> > causing various program settings, options and registration
states
> to
> > be lost after a soft reset.  We've seen this many times on our
own
> > TX, but not on other devices.  It acts as if some preference
> changes
> > are never being copied back to flash memory, causing
applications
> to
> > act after a reset as if they are being run for the first time.
> With
> > no official fix or acknowledgement of this as a system bug,
we've
> > resulted to using PreferenceDoctor (www.hobbyistsoftware.com) to
> > backup and automatically restore our preference database.
> >
> > -tex
> >
>

Hello,

> Is it worth it?

Of course no developer is going to give you a negative answer to the
question above, but I think we can make a good case for the
affirmative.

The thing to keep in mind in purchasing any program for PalmOS is not
only the experience you get with the product from the start, but how
it will evolve as the platform and your needs change.

The PalmOS platform has changed much in the past ten years, and our
applications have undergone numerous updates to keep up with new
devices, new features, new system bugs, and neighboring applications.
As you use your device, you'll download new applications, maybe
upgrade the OS from time to time, and even eventually upgrade to a new
handheld in the future.  You'll want your software to stay working and
improve too.

I think if you were to ask other users here, you'd find that most
agree we've done much to incorporate user input and revamp our
products to keep up with the times (though no, we can't always grant
every user's request the instant they want it).  In fact, we've spent
the entire last year doing nothing but go through our entire product
line, updating them with a long list of mostly user-requested features
and improvements.  It's been a very slow, hard, and time-consuming
process, but we do it anyway.

Sadly, you will not get this kind of ongoing support with cheap or
free applications, because their developers (often students)
eventually find it's now worth their time to support.  Take Hackmaster
($5) or XMaster (freeware), for instance.  Both were created by
talented, well-intentioned individuals who wrote their programs as
their gift to the Palm community.  Development seemed to stop for both
long ago, however, even though Hackmaster has obvious bugs going way
back to 1997.  My guess, based on our experience with TealMaster, is
that they found the support emails they got were far more numerous
than they had predicted, and that it was too much work to keep doing
for free after the fun part (writing the app) was done.

With a backup program, keeping up-to-date is even more critical, due
to the importance of saveguarding your data.  Our current version
features new user-requested improvements like an application-lockdown
feature (to workaround bugs in other apps under NVFS systems),
optimized compression/encryption, multiple backup channels, access to
hidden/system volumes, and detailed logging capabilities.  One of our
major competitors, however, (whom I won't mention because they're
friends of ours) still--even after many years--incorrectly "restores"
locked applications, creating damaged 1k files instead that crash when
you try to run them.  Interestingly, it was constantly dealing with
tech support emails from our TealLock/TealScript users who had run
into this bug that prompted us to write our own backup solution in the
first place.

hope this helps,

-tex
--- In tealtalk@yahoogroups.com, "maryloe2000" <mloe@...> wrote:
>
> I'm a new Palm TX owner, and although I haven't experienced data loss
> with the Tx or its predecessor (IIIC), I think that it would be wise
> to purchase a backup program.  I've been looking at Tealpoint's
backup
> competitors, including a freeware application, and noted that
> TealBackup is pricier than some of the more popular applications.  Is
> it worth it?
>

"tealtex" == tealtex  <no_reply@yahoogroups.com> writes:


[...]

     tealtex> The locking program you mention sounds like the same as the "locked
     tealtex> application" feature that we have in TealBackup.  A good idea to
     tealtex> stabilize those background apps that haven't properly locked
     tealtex> themselves down to run on NVFS devices like the TX or Lifedrive.
     tealtex> This prevents the crashes that occur after accessing/copying large
     tealtex> files or many smaller files because you have bad background apps
     tealtex> running that haven't properly done all the necessary steps to tell
     tealtex> NVFS that they shouldn't be moved during a DBCache shuffle/flush.

As a user the problem I have is that I don't know how to identify the
apps that need this. Do you have a list well-know trouble apps ?
Maybe even users could contribute to this, if a method for finding
them exists.

     tealtex> Still, I wish Palm or somebody else would write a simple app that
     tealtex> would detect "bad" applications.  It could just scan the PalmOS
     tealtex> notification list and just look for any apps that registered for
     tealtex> notifications via a callback pointer to an unlocked block of
     tealtex> memory.  This would require inside knowledge of PalmOS's inner
     tealtex> workings, but should be easy for an insider to write.

Would this be the only way?


[...]


--
Nelson Ferreira

Tealtex is quite right in his reply.  I've found TealPoint's support
and evolution of the programs to be superior.

I feel I get my money's worth not only in the "now" but also in the
future.

As the saying goes, "Pay the freight."
Steve


--- In tealtalk@yahoogroups.com, "maryloe2000" <mloe@...> wrote:
>
> I'm a new Palm TX owner, and although I haven't experienced data loss
> with the Tx or its predecessor (IIIC), I think that it would be wise
> to purchase a backup program.  I've been looking at Tealpoint's backup
> competitors, including a freeware application, and noted that
> TealBackup is pricier than some of the more popular applications.  Is
> it worth it?
>

Hi,

RLocker can be found here:
http://www.resco.net/palm/locker/default.asp

Resco Locker is
a utility that keeps applications locked in memory on NVFS systems.
While Resco Locker can be formally used on non-NVFS systems, it
cannot do anything usefull here.

Why to use Resco Locker?
Main reason is the safety. NVFS brought changes to the Palm OS
programming and not all applications reflected them. (Those that were
last time updated prior to NVFS release, could not.) One of the most
frequent problems is that the Palm databases are no longer fixed.
That's exactly the problem that is targeted by Resco Locker. For more
detailed explanation of the NVFS specifics see please the discussion
on the Resco Backup product page.

As a side effect, applications locked in memory need less time to
load, which in turn may increase the performance of your handheld.

News
V1.01 - Locks the whole applications instead of just the first
records.

V1.02 - corrects occasional bad display of the "L" attribute

V1.03 - another correction of the DB attribute "L" (locked).

V1.04 - preference panels added to the application list.

V1.05 - 5way handling added

V1.10 - Prevented locking of ROM DBs (crash), moving cursor by typing
a char, support for DA's (Desk Accessories), sorting by the lock state

V1.20

Palm TX compatibility
Attribute "P" denotes protected databases.
"!" marks apps that might be acting on background. (They receive
typical notifications.)
You can save DbCache space by locking the code segments only.
(Concerns apps only.)
DA's display DA launcher icon.
Help.txt included into the .zip installer.

V1.21 - Bug fix: DB protecting limited to the Palm TX applications
only

Usage
  Lock
Select applications by tapping the respective rows and tap the Lock
button. The locking is performed immediately.

Unlock
To unlock repeat the same procedure and tap the Unlock button.


Supplementary possibilities
Action trigger offers selection commands (e.g. Select All) and Column
Setup dialog. (Additional columns are type, creator, date.)
To change the sort order tap suitable column label.


Meaning of attributes
! - Receives Notifications
L - Locked
O - Opened
B - Backup
P - Protected

General Options dialog:
Resco Locker can be disabled, in which case it unlocks all currently
locked applications. (However, these apps will be further on marked
as locked.)
Resco Locker can restore application locks on reset or clear all
locks - depending on the option the user selects.



Typical use

Options dialog: Enable RLocker and switch on 'Only lock code'
Action trigger > Select Defaults
Unselect apps that you know are safe
Press Lock button
Test
If satisfactory, switch on 'Restore locks after reset' in the Options
dialog
Otherwise read Help.txt (part of the .zip installer)

The risks
One could envisage specific programming constructs that under special
occasions would conflict with external locking as performed by Resco
Locker. These constructs are not very probable, but cannot be
excluded either.

Conclusions
Resco Locker was created with the hope to help the users. However,
Palm OS is an open system and bad interactions with the way RLocker
works cannot be excluded. We don't want any money for this tool, but
do not take any responsibility for eventual consequences. Use it with
care.

The above was from there site... J
--- In tealtalk@yahoogroups.com, Nelson Ferreira
<nelson.ferreira@...> wrote:
>
> "tealtex" == tealtex  <no_reply@yahoogroups.com> writes:
>
>
> [...]
>
>     tealtex> The locking program you mention sounds like the same
as the "locked
>     tealtex> application" feature that we have in TealBackup.  A
good idea to
>     tealtex> stabilize those background apps that haven't properly
locked
>     tealtex> themselves down to run on NVFS devices like the TX or
Lifedrive.
>     tealtex> This prevents the crashes that occur after
accessing/copying large
>     tealtex> files or many smaller files because you have bad
background apps
>     tealtex> running that haven't properly done all the necessary
steps to tell
>     tealtex> NVFS that they shouldn't be moved during a DBCache
shuffle/flush.
>
> As a user the problem I have is that I don't know how to identify
the
> apps that need this. Do you have a list well-know trouble apps ?
> Maybe even users could contribute to this, if a method for finding
> them exists.
>
>     tealtex> Still, I wish Palm or somebody else would write a
simple app that
>     tealtex> would detect "bad" applications.  It could just scan
the PalmOS
>     tealtex> notification list and just look for any apps that
registered for
>     tealtex> notifications via a callback pointer to an unlocked
block of
>     tealtex> memory.  This would require inside knowledge of
PalmOS's inner
>     tealtex> workings, but should be easy for an insider to write.
>
> Would this be the only way?
>
>
> [...]
>
>
> --
> Nelson Ferreira
>

I appreciate your effort but that does not bring me any closer to have
a list of apps which should be locked.

RLocker pages and forums do not have such list either.

"jdebay" == jdebay  <jdebay@...> writes:


[...]


     jdebay> Palm TX compatibility
     jdebay> Attribute "P" denotes protected databases.
     jdebay> "!" marks apps that might be acting on background. (They receive
     jdebay> typical notifications.)
     jdebay> You can save DbCache space by locking the code segments only.

This is the closest it comes to have some clue of what apps to
lock. Still it is a "might" not a verified list.


[...]


     jdebay> The above was from there site... J
     jdebay> --- In tealtalk@yahoogroups.com, Nelson Ferreira
     jdebay> <nelson.ferreira@...> wrote:
     >>
     >> "tealtex" == tealtex  <no_reply@yahoogroups.com> writes:
     >>
     >>
     >> [...]
     >>
     tealtex> The locking program you mention sounds like the same as the "locked
     tealtex> application" feature that we have in TealBackup.  A good idea to
     tealtex> stabilize those background apps that haven't properly locked
     tealtex> themselves down to run on NVFS devices like the TX or Lifedrive.
     tealtex> This prevents the crashes that occur after accessing/copying large
     tealtex> files or many smaller files because you have bad background apps
     tealtex> running that haven't properly done all the necessary steps to tell
     tealtex> NVFS that they shouldn't be moved during a DBCache shuffle/flush.
     >>
     >> As a user the problem I have is that I don't know how to identify the
     >> apps that need this. Do you have a list well-know trouble apps ?
     >> Maybe even users could contribute to this, if a method for finding
     >> them exists.
     >>
     tealtex> Still, I wish Palm or somebody else would write a simple app that
     tealtex> would detect "bad" applications.  It could just scan the PalmOS
     tealtex> notification list and just look for any apps that registered for
     tealtex> notifications via a callback pointer to an unlocked block of
     tealtex> memory.  This would require inside knowledge of PalmOS's inner
     tealtex> workings, but should be easy for an insider to write.
     >>
     >> Would this be the only way?
     >>
     >>
     >> [...]
     >>
     >>
     >> --
     >> Nelson Ferreira
     >>


[...]


--
Nelson Ferreira

I have found that any app that is a hack should be locked.  This provides me
less resets

textplus, graffiti anywhere, teallock, volkeys, powerrun
etc.
I also finf Uncache useful for keeping the DBCache less fragmented  or with a
larger contiguous chunk.

  brad@...

-----Original Message-----
From: Nelson Ferreira <nelson.ferreira@...>
Date: Saturday, May 20, 2006 9:44 am
Subject: Re: [tealtalk] Re: NVFS problems on TX

I appreciate your effort but that does not bring me any closer to have
a list of apps which should be locked.

RLocker pages and forums do not have such list either.

"jdebay" == jdebay  <jdebay@...> writes:


[...]


     jdebay> Palm TX compatibility
     jdebay> Attribute "P" denotes protected databases.
     jdebay> "!" marks apps that might be acting on background. (They receive
     jdebay> typical notifications.)
     jdebay> You can save DbCache space by locking the code segments only.

This is the closest it comes to have some clue of what apps to
lock. Still it is a "might" not a verified list.


[...]


     jdebay> The above was from there site... J
     jdebay> --- In tealtalk@yahoogroups.com, Nelson Ferreira
     jdebay> <nelson.ferreira@...> wrote:
     >>
     >> "tealtex" == tealtex  <no_reply@yahoogroups.com> writes:
     >>
     >>
     >> [...]
     >>
     tealtex> The locking program you mention sounds like the same as the "locked
     tealtex> application" feature that we have in TealBackup.  A good idea to
     tealtex> stabilize those background apps that haven't properly locked

There is a whole thread on locking apps at
http://discussion.treocentral.com/showthread.php?t=91243&highlight=rlock
--- In tealtalk@yahoogroups.com, Nelson Ferreira <nelson.ferreira@...>
wrote:
>
>
> I appreciate your effort but that does not bring me any closer to have
> a list of apps which should be locked.
>

--- In tealtalk@yahoogroups.com, Nelson Ferreira <nelson.ferreira@...>
wrote:
>
>
> I appreciate your effort but that does not bring me any closer to
have
> a list of apps which should be locked.
>
> RLocker pages and forums do not have such list either.

Unfortunately, this is our dilemma too.  Believe me, we don't like the
fact that we have to lose thousands of dollars in tech support costs
and lost sales because customers cannot track down the cause of
crashes and sometimes blame our apps or give up on third party
software altogether.

We wish we could give them a list of "bad" apps, but we don't know of
one, and whenever people try to build these sorts of compatibility
lists then end up being horribly unreliable because end customers
don't have the tools to definitively determine the cause, relying
instead on limited experimentation inconclusive results.
Palm/Palmsource should easily be able to create a tool like this, or
even automatically "lock" apps that register for notifications,
solving most of the crashes from every happening in the first place.

-tex

Hi all,

Yes Tex you are right. It has only been through trial and error, and
finding products that lock apps. I found that your products do a
better than average at this. I also found your support and updates
great.

I did notice when I upgraded to my latest palm, a new subdirectory
was created that are not os5 compliant per Palm. If they can figure
this out that can do as you suggest. Make an application that check
apps.

I have also noticed the Resco is doing the same as you (the makers of
RLocker). I have many third party applications. What I find is I must
lock Blazer in memory, once I did that a lot of my resets stopped.
And this is a Palm application. I run alot of DA's, including your
TealTools, with your TealMaster and TealLaunch. Plus DA Launcher and
some additional DA's. I lock those in memory too, if they do not. I
started work on looking at howto program DA's and working on that
project.

I would also recommend that people that do a lot of wifi
communications make sure that they lock in memory those apps.

Like Mini-Opera 2.0.

My thoughts on the topic.

J



--- In tealtalk@yahoogroups.com, tealtex <no_reply@...> wrote:
>
> --- In tealtalk@yahoogroups.com, Nelson Ferreira <nelson.ferreira@>
> wrote:
> >
> >
> > I appreciate your effort but that does not bring me any closer to
> have
> > a list of apps which should be locked.
> >
> > RLocker pages and forums do not have such list either.
>
> Unfortunately, this is our dilemma too.  Believe me, we don't like
the
> fact that we have to lose thousands of dollars in tech support
costs
> and lost sales because customers cannot track down the cause of
> crashes and sometimes blame our apps or give up on third party
> software altogether.
>
> We wish we could give them a list of "bad" apps, but we don't know
of
> one, and whenever people try to build these sorts of compatibility
> lists then end up being horribly unreliable because end customers
> don't have the tools to definitively determine the cause, relying
> instead on limited experimentation inconclusive results.
> Palm/Palmsource should easily be able to create a tool like this,
or
> even automatically "lock" apps that register for notifications,
> solving most of the crashes from every happening in the first place.
>
> -tex
>

during installation of any previous beta-versions 3 (=all) adressbook
entries starting with the @-character disappeared misteriously (e.g.
@name1, @name2, @name3)
i used the @-character to have theese entries at the top of my list;
they mainly were used for information stored within the attached note.
fortunately i could restore the information an recreated new entries
as followed
(Last): @name; (first): @name; company @name (@name = same for last,
first and company)

today i wanted to lookup for information but the attached note has
disappeared again, leaving just the core-information of adress-entry.
the problem must have occured somehow between using beta 3.69 and
updating to version beta 3.70.
fortunately i could restore the information again via old backups.

unfortunately i have no further details.
hardware: palm TX

cheers,
robert

The '@' characters isn't treated specially in TealPhone, but it may
be in one of your other programs or from something on the desktop
(outlook sync conduit?).  It's unlikely that TealPhone could remove
these entries entirely, as TealPhone normally accesses the database
read-only unless you specifically open up a record, and then it's
only one record at a time.  When a record goes "missing" in
tealPhone, it's typically a case that you just need to rescan the
database to rebuild the sort/index table, but the address database
itself is untouched and all the entries should still be visible in
the standard contacts app.

-tex

--- In tealtalk@yahoogroups.com, "hoppe_christoffel"
<hoppe_christoffel@...> wrote:
>
> during installation of any previous beta-versions 3 (=all)
adressbook
> entries starting with the @-character disappeared misteriously
(e.g.
> @name1, @name2, @name3)
> i used the @-character to have theese entries at the top of my
list;
> they mainly were used for information stored within the attached
note.
> fortunately i could restore the information an recreated new
entries
> as followed
> (Last): @name; (first): @name; company @name (@name = same for
last,
> first and company)
>
> today i wanted to lookup for information but the attached note has
> disappeared again, leaving just the core-information of adress-
entry.
> the problem must have occured somehow between using beta 3.69 and
> updating to version beta 3.70.
> fortunately i could restore the information again via old backups.
>
> unfortunately i have no further details.
> hardware: palm TX
>
> cheers,
> robert
>