Registered: Nov 1999
Location: Stony Brook, NY, USA
Posts: 35

Ok, so I know mostly what makes the Visor better than a Palm, but what about raw SPEED?? which is faster?

Registered: Oct 1999
Location: East Lansing, MI, USA
Posts: 126

The visor is about 50% faster then the palm V. I dont know if its faster then the palm Vx. The reason is because they optimised the hardware and software to run better.

Registered: Sep 1999
Location: Burlington, VT, USA
Posts: 127

Actually, it's because they eliminated the wait states... If you run CruiseControl on a Palm IIIx, you get approximately the same speed as a Visor (158% normal).

What the heck were those wait states doing in there in the first place, that's what I want to know...

Registered: Oct 1999
Location:
Posts: 95

Not only that, but I think OS 3.3 eliminates the wait states as well, just like 3.1h in the Visors.

MJH <><

Registered: Sep 1999
Location:
Posts: 61

My Palm V with 3.3 w/o CC is 100% Benchmark

With CC 148%
With CC and StreakHack - 161%
With CC/StreakHack and Afterburner 2.0 - 259%

Looks like the handspring guys did something like CC and Streakhack so Afterburner should still work with them.

Overclock at your own risk

jonpod

Registered: Sep 1999
Location:
Posts: 159

With CC/StreakHack and Afterburner 2.0 - 259%

Whoa! That's some markup. Would definitely like to see a similar benchmark run with the Visor and these apps installed.

Registered: Oct 1999
Location: Mililani, HI, USA
Posts: 256

None of you are getting wait states? I'm getting them most of the time when I access the info and delete dialogues. Am I the only one?

thanks,
Chris

Registered: Nov 1999
Location: Ann Arbor, Michigan USA
Posts: 790

There seems to be some confusion about the term "wait state". It is a computer architecture term refering to 1 or 2 CPU cycle pauses which are designed into a system to accomodate differences in speed between various chips.

It does not refer to delays seen by a user.

A system can be designed without wait states, but it takes more effort, and thereby more time and expense. Wait states can be removed after the fact (often with noticable results - cf Afterburner), but it is not usually supported by the manufacturer. This is because it is possible that system components will be out of sync and not work properly if wait states are removed. There's no way to know except to try it.

At least that's what I remember about it from my computer engineering degree.