Page 2 of 4 FirstFirst 1234 LastLast
Results 21 to 40 of 62
  1. #21  
    I have just stopped using BackupBuddy... The file is still on my Treo.
  2. #22  
    After having my Treo replaced on Friday due to the Lockwhateveritwas thing...I upgradeded and got everything working just fine. I also have this annoying error now after a hot sync. One way I've found to deal with it is to leave the room during a hot sync following the old "watched pot never boils" rule. When I return, it's over with and the error log has already closed itself.

    Better question is...why an I using BackupBuddy on my Treo? It was great when I had a Clié and did a full backup to the memory stick at 2 a.m. automatically...but what is the advantage now <sarcasm mode on> other than this great little message Hotsync leaves me after every backup?
  3. #23  
    Originally posted by Alli
    ...why an I using BackupBuddy on my Treo? It was great when I had a Clié and did a full backup to the memory stick at 2 a.m. automatically...but what is the advantage now <sarcasm mode on> other than this great little message Hotsync leaves me after every backup?
    Because the standard Hotsync doesn't backup all applications/data resident in the Treo's memory. Backup Buddy does this (more or less).
  4. #24  
    Treobuddy's solution, replacing the HSTraceBackup3 with a dummy file then instructing backupbuddy not to back it up, works for me. No errors are produced.

    I don't know what will happen during a restore, but since the file doesn't seem to be necessary, it probably won't matter.

    What I like about backupbuddy is that it makes me nearly fearless about an intentional hard reset. A fair number of settings are lost when you perform a hard reset without backup buddy, and I wound up spending time recreating them.
  5. #25  
    Originally posted by Preston
    What I like about backupbuddy is that it makes me nearly fearless about an intentional hard reset.
    I second that. However, I would really like to know how many "HS-has-totally-fogotten-about-that-useless-file" files there are floating around in there.
  6. #26  
    I received this from Blue Nomad, maker of BackupBuddy, who received it from Handspring:
    ----------------------------------------
    This is a file associated with the GPRS update. It shouldn't be a problem with the majority of Treo GPRS users. Some users have reported problems with backup of this file using BackupBuddy.

    The HSTrace3 file is generated by a test program which is not available to the general public and was supplied to testers of the GPRS software.

    The test file is called (GSMLibTestApp.prc)

    To fix the issue, please do the following:

    1) Delete the GSMLibTest app from the Treo.

    2) Hotsync Treo

    3) Go into the backup folder on Desktop HD and remove the HSTraceDatabase3 file if it is found there.

    4) Hard reset the Treo

    5) Hotsync to allow BackupBuddy to restore the data on the Treo


    From this point in time the app and this file should be fully removed from the Treo and you should not get this error again while using BackupBuddy.

    Let me know if this looks like it makes sense to you.. if it is wrong, maybe that workaround would be a good idea.

    --------------------------

    Unfortunately, there appears to be no such file as GSMLibTestApp.prc, unless it is somehow hidden even from Filez.

    The creator of HSTraceDatabase3 is HsT2, and there are no other files, even in ROM, that have the same creator.
  7. #27  
    Handspring contacted me, and said:

    Thank you for contacting Handspring Technical Support. We understand that you are experiencing difficulties with the HSTraceDatabase3 file. We will provide you with a series of steps to resolve your issue. Please follow these steps:

    (A) Please hard reset the treo again.

    (B) Go into your users backup folder which is usually located in C:\Program Files\Handspring\<your username>\backup\

    (C) Locate and remove the HSTraceDatabase3 file.

    If you ever have any other questions or issues, please do not hesitate to email us again, quoting the case number...

    This of course didn't work. I already knew it wouldn't work, because I had tried a hard reset, as I had told HS in the email to which they responded with these instructions. I tried it again anyway, just in case, but of course HSTraceDatabase3 is still present.

    Interesting that HS told Blue Nomad something different, and that neither were right.
  8. #28  
    Got the following message from Handspring via Blue NomadL

    "The file is not created by publicly released versions of the GPRS upgrade, of which there has been three flavors (1.0., 1.1 and 1.1.1). All three do not contain the application that creates this file.

    The ONLY way they would have this file is if they somehow got a hold of a pre-release version of the GPRS ROM, which does contain this app.

    They could delete the file from the backup folder, hard reset the Treo, then hotsync to restore. But, if the Treo has the GSMLibTestApp.prc on it, and they run it just once, this data file will be recreated and the hotsync issue will happen again.

    If the user in question is in the North American area, ask them what cellular carrier they use.

    If they have Rogers AT&T (in Canada) or T-Mobile/VoiceStream in the US, then they can go to the Handspring website, download the GPRS 1.1.1 updater and this will fix their problem. If they answer anything else other than Rogers AT&T or T-Mobile/VoiceStream, then they have hacked the Updater using information on TreoCentral. If this is the case, then Handspring has no obligation to help them with this (or any other issue) as the GPRS updater has not been approved for their carrier.

    If the user is outside North America, send them to the handspring website to get the GPRS 1.1.1 updater. As of right now only Cingular users I n North America are locked out of the installation. And installing GPRS 1.1.1 for these users should solve their issue as well."

    Dave Cagle
    Worldwide Technical Support Specialist
    Handspring"

    Unfortunately I was using the legal GPRS patch posted by Handspring for T-Mobile customers like me. I was, however, one of the very first to download the official patch (I was checking for it hourly). I wonder if Handspring had the wrong patch posted at first? Like everyone else here, I do not have the GSMLibTestApp.prc on my machine (at least I can't find it with Filez).

    But I wouldn't blame Blue Nomad - I think the problem is that Handspring wants to blame customers instead of fixing the issue.
  9. #29  
    Tried TreoBuddy's solution and it worked like a charm. Thanks!
  10. #30  
    I also downloaded the GPRS updater from HS for T-Mobile and am a T-Mobile customer, so they are clearly wrong. Moreover, I just downloaded and installed my GPRS December 1, so it had been posted for a while!

    Annoying to have waited for the official upgrade, have a problem and be accused of not following their own plan.

    I went to HS's site to download the 1.1.1 updater, on the principle that perhaps they have fixed this bug, but it is now gone and the link takes you to T-Mobile, which immediately transfers me to My T-Mobile. I am unable to find the updater on T-Mobile's site.
    Last edited by Preston; 12/04/2002 at 11:22 PM.
  11. #31  
    I also waited for the "legal" 1.1.1 version - and have the HSTrace file problem.

    I tried TreoBuddy's workaround, but it doesn't seem to work for me. I copied the 'hacked' file to my backup directory, and was able to check the box in the exclude from backup list, but when I hotsync, the warnings still appear.

    Did I miss something? Do you have to install the 'hacked' file, or just copy it to the backup directory?

    Michael
  12. #32  
    I just copied the file to my backup directory, then checked the box "don't back up" for that file, and the problem went away. Note that the file tries to download as a txt file (at least on my system) and you have to save as "All Files" so that the filename is HSTraceBackup3.prc, not HSTraceBackup3.prc.txt. If it is the latter (and if you aren't listing extensions of known file types, you may not see .txt, in which case go to folder options, and check the box 'show extensions of known file types), you can just rename it, then check the box again.
  13. #33  
    Thanks for the tips. I did ensure that the .txt was removed, but the file I have is a .pdb not a .prc.

    I renamed the file to .prc, but it still would not work...BackupBuddy thinks the file has been deleted, and moves it to the archive folder, in addition to generating the warnings.

    Michael
  14. #34  
    Sorry, I meant pdb, nor prc. I don't know why your backupbuddy is moving the file to archive when mine doesn't. I also have "Archive files deleted on handheld" checked, but this one can't be deleted on handheld, so doesn't get archived.
  15. #35  
    Originally posted by mfacelle
    I tried TreoBuddy's workaround, but it doesn't seem to work for me. I copied the 'hacked' file to my backup directory, and was able to check the box in the exclude from backup list, but when I hotsync, the warnings still appear.

    Did I miss something? Do you have to install the 'hacked' file, or just copy it to the backup directory?

    Michael
    Are you sure you installed it in the right backup directory?
  16. #36  
    If it is showing up in the "exclude" list from backup buddy, it must be in the correct directory, yes? The problem seems to be that Backup buddy is archiving the file, rather than excluding it.
  17. #37  
    Originally posted by Preston
    If it is showing up in the "exclude" list from backup buddy, it must be in the correct directory, yes? The problem seems to be that Backup buddy is archiving the file, rather than excluding it.
    Yes...this is exactly what is happening.

    Michael
  18. #38  
    Here is what I received from Handspring Support:

    > I understand that you still cannot remove a third party
    > software application from your Treo 270. At this point, I
    > would recommend you contact our Wireless Technical Support
    > Line directly.
    >
    > Our agent will be required to collect standard billing
    > information, as there is a $19.95 charge for all technical
    > support issues for owners of Handspring products over 90 days
    > old. We will continue to troubleshoot your issue, which may
    > result in a replacement. If your unit is over 90 ninety days
    > since the original purchase date, should the mandatory
    > troubleshooting steps be unsuccessful, our agent may waive
    > the $19.95 technical support charge if we issue you a
    > replacement.

    My response was to question whether T-Mobile approved GRPS updater v1.1.1 was a "third party app" because that is what installed the HSTraceBackup3. Moreover, I downloaded the GRPS updater from HS's own site, not from T-Mobile's site.
  19. #39  
    This is not new to GPRS 1.1.1

    I have this problem since v1.1 (Asian version) !!!

    How could it be a T-Mobile issue....???
  20. #40  
    Yes, I know it isn't a T-Mobile issue, but Handspring is currently ducking responsibility for it, claiming that people experiencing this problem upgraded before the upgrade was official. I did not, and several other posters apparently did not. That is why I described HS as taking a turn for the worse.
Page 2 of 4 FirstFirst 1234 LastLast

Posting Permissions