VisorCentral.com - Handspring Updater V1.0.0 Posted!

Pages (2): « 1 [2]
Show 20 posts from this thread on one page

VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- Visor & Deluxe (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=1)
-- Handspring Updater V1.0.0 Posted! (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=1464)

Posted by lance barnes on 07-22-2000 01:50 PM:

The sentence about usage patterns means
that if you use your visor often, then--
since 'power on' battery burn is much
greater than 'power off' burn (before and
after patch)--you won't notice a change in
performance.

However, if you use your visor seldom,
then it's off most of the time and the
'power on' burn isn't a significant factor
in battery life. Under these circumstances,
battery life becomes directly dependent on
the 'power off' burn, and so may decrease
by a significant percentage. How much
depends on how much more current is needed
by refresh under the patch.

Posted by Toby on 07-22-2000 03:12 PM:

quote:
Originally posted by lance barnes:
However, if you use your visor seldom,
then it's off most of the time and the
'power on' burn isn't a significant factor
in battery life. Under these circumstances,
battery life becomes directly dependent on
the 'power off' burn, and so may decrease
by a significant percentage. How much
depends on how much more current is needed
by refresh under the patch.

See my previous post with the link to Deja.com for the numbers.

------------------
"The mind is like a parachute. It doesn't work unless it's open." - Frank Zappa

Posted by ATHun on 07-22-2000 04:35 PM:

quote:
Originally posted by Toby:
See my previous post with the link to Deja.com for the numbers.

I checked it. If that guy's estimations are correct, battery life is going to be impacted significantly and I'm going to be looking for a replacement.

In that same thread someone else mentioned that there is another option for refreshing the memory which would seem to have much less impact. I'm not knowledgeable enough with these chips to know whose guess is best.

I wish Handspring, Palm, et al, would be a little more forthright about this. Because they are so tight-lipped about specifics, it makes a person wonder if the battery impact is quite significant.

------------------
A.T. Hun
The Haus http://www.thehaus.net

[This message has been edited by ATHun (edited 07-22-2000).]

Posted by KennethAaron425 on 07-23-2000 05:07 AM:

My visor was affected by the 8mb DRAM problem. I downloaded and installed the patch last night. Unfortunately, my visor began to experience several Palm reset loops last night and today that required hard resets to correct. Any one else with that problem?
I called the Handspring tech support, and they were very helpful. I'm very impressed with their service. They offer to replace my Visor. They are sending me the replacement, and I should get it in 3 to 4 days. All I have to do is to put my old visor in the replacement box and sent it back to them. I am VERY impress.

------------------
KAY

Posted by Babylon5 on 07-24-2000 03:13 PM:

I messed up here. Okay let me start by saying that I got my Visor last November so should not have had a problem to begin with. I used the original test anyway just to see and it was negative.

When the Handdspring patch came out I wanted to apply it mostly for the scroll fix. So I read the docs and it said to remove all hacks and reset before applying the patch. I did remove all the hacks but forgot to do a soft reset and hit the update button, it wasn�t sure about my Visor so asked me to enter my serial number so I entered it and it patched it WITH the memory fix. Damn it� So I reset it and reapplied the patch, as it did not need the memory fix, but did not overwrite the first fix so my info still says I have the memory fix update when I don�t think I need it.

Now aside from the �backing everything up and removing that one file and then redoing a full restore option�, is there a way to get this removed or the other patch in there?

I was thinking of just deleting that file itself and doing a reset. Using a program like Z�catalog, that lists all files on the Visor and allows one to simply remove files bypassing and not using the built in delete function. Will this crash the Visor? Other opinions?

Posted by guido79 on 07-24-2000 05:01 PM:

quote:
Originally posted by Babylon5:
I messed up here...
I was thinking of just deleting that file itself and doing a reset. Using a program like Z�catalog, that lists all files on the Visor and allows one to simply remove files bypassing and not using the built in delete function. Will this crash the Visor? Other opinions?

If want to avoid having to do the hard reset described in the documentation for Handspring Updater V1.0.0., you may want to do a "warm reset". A warm reset bypasses any system extensions (such as HackMaster hacks, OS patches, etc) that are loaded on your handheld. Performing a warm reset will often bypass the "boot loop" error, allow you to remove any third party application that has recently been installed that might be causing the problem.
To perform a warm reset:
1) Press and hold the Page Up button on your handheld.
2) Using the reset tip tool (or a similar object without a sharp tip), gently press the reset button inside the hole on the back banel of your handheld.
3) When the Palm Computing Platform logo appears on the screen, release the Page Up button.
4) From the Applications Launcher window, choose the "Delete..." menu item from the App menu.
5) Select "HsExt 1.0.3M" or "HsExt 1.0.3" file (whichever one you have)
6) Tap the Delete button
7) You will be asked to "Delete the HsExt 1.0.3M application and all data?".
8) Tap the Yes button.
9) You should have just deleted the update. If you see a message that says "Unable to delete HsExt 1.0.3M", you didn't warm reset correctly. Try warm resetting your Visor again.

Hope this helps everyone who accidentally installed the 1.0.3M update with Hacks installed.

Posted by MarkEagle on 07-24-2000 05:03 PM:

quote:
Originally posted by Babylon5:
Now aside from the �backing everything up and removing that one file and then redoing a full restore option�, is there a way to get this removed or the other patch in there?

If you do a WARM rest (hold the UP button while resetting), you should be able to delete the HsExt 1.0.3 file normally. Then do another WARM rest, reinstall the patch file and re-run it. This should apply the other fixes without the one for the memory bug. I had to do this myself, not because I got them memory patch when I didn't need it, but because at first the patch really screwed up AvantGo (or so I thought).

------------------
MarkEagle - Ice is nice!

Posted by Babylon5 on 07-24-2000 07:59 PM:

quote:
Originally posted by guido79:
If want to avoid having to do the hard reset described in the documentation for Handspring Updater V1.0.0., you may want to do a "warm reset". A warm reset bypasses any system extensions (such as HackMaster hacks, OS patches, etc) that are loaded on your handheld. Performing a warm reset will often bypass the "boot loop" error, allow you to remove any third party application that has recently been installed that might be causing the problem.

Hope this helps everyone who accidentally installed the 1.0.3M update with Hacks installed.

Thanks Guido 79 and MarkEagle! This seemed to work just GREAT!!!! I warm reset it, deleted the file then reapplied the OS patch. I am now reading the version I should be. I originally thought of doing this but wanted to get some solid opinions before I went around deleting any OS patch files. If it was anything else I would have just done this but an OS patch scares me a bit as you never know what else it could change or do etc�I trust you guys.

Posted by dtplink on 07-25-2000 12:52 AM:

So far I have upgraded two VDX and both required calls to Handspring. The first one went into a Palm Computing Platform start-up screen loop and the second went to Fatal Error at the reset prompt.

In both cases I was advised to do the same thing. A hard reset and erase followed by a reinstallation of the HS Updater. In both cased the update took and all seems to be working well.

If I were a betting man I would guess that in both cases there were visible or invisible files that caused the conflict and that the environment had to be purged of all but the starting set of files before the OS could be cleanly installed. I suppose the installation instructions could have been:
"Hotsync and Backup your Visor. Do a hard reset and erase all data. Download the HS Updater. Run it. Reset. Check version info for Palm OS 3.1H3M."

All times are GMT. The time now is 01:48 AM.

Pages (2): « 1 [2]
Show 20 posts from this thread on one page