This is just an idea, but shouldn't the new hw3 patch be called hw4patch now? o_O

Just as an aside, has anyone tried out TI Vibe? I'm running on Windows 2000, and I had to edit the batch file to get it succesfully converting mp3/wav files to TI readable form.

I was going to try, but I don't know enough about Windows batch files or UNIX shell scripts or Applescript to be able to port the batch file to use on Mac OS X, and I wasn't able to recompile SSRC for Mac OS X. I also don't know enough Python to know if you can run it separately. The only component that actually works is LAME, but I have my music in iTunes in AAC format anyway, so it's easier just to reencode in WAV format instead of going through MP3.

So no.

Only vibegen.py is TI-specific, and can be used independently. It needs a resampled WAV file as input (around 22200 Hz depending on the calculator).

So once I get it to vibegen.py, it's basically done and needs nothing else? I could do the resampling in, say, VLC (assuming it can do that), a priori?

So, if anyone's keeping track, I've used iTunes to re-encode one song ("Nil Si I Ngra" by Capercaillie) to wav format with 8-bit audio, 22.5 kHz sample rate, and mono sound. I should be able to use that.

How long is it supposed to think about it? It's been using >60% of my processor for nearly 20 minutes, and I'm only doing the aforementioned file, which is only four minutes long.

Strange, it shouldn't take more than 20 seconds.

Not really. The only thing I changed was a single instruction (which checked the hardware version to make sure you don't use it on a version it can't work on). HW3Patch was already misleading given that it also works on HW2, but HW2HW3HW4Patch just sucks as a name. :-)

what's worong whith a name that doesn't seem to bind it to a single hardware version?

Then people wouldn't know that it's the successor of HW2Patch.

How about HWPatch v2.0? HWPatch_v3.0? HWPatch_v4.0?

Or all of the above. The same binary could be released under several names.

that's an interesting point but it could lead to lots of confution

It depends on the documentation. The hw3 patch documentation could read:

"Yo this is the hw3 patch. It patches hw3 calculators. As an added bonus it can also patch hw2 or hw4 calculators, just in case your stupid enough to use the wrong hardware patch on the wrong hardware model."

Then the hw4 patch doc could read:

"Yo this is the hw4 patch. It patches hw4 calculators. As an added bonus it can also patch hw2 or hw3 calculators, just in case your stupid enough to use the wrong hardware patch on the wrong hardware model."

you or I might be able to see through this. But 99% of the plebians shouldn't be confused.

Using a program which works on a hardware version it works on is not "stupid", releasing the same program 3 times is. (3 times the packaging effort, no benefits whatsoever.)

Yes!! I just got a TI-89T for my b-day a couple days ago, and it ha d HW4 I'm so lucky! And my dad got it off amazon! I wouldn't expect somtin like that from amazon...

So you can verify it's just a faster processor?

Yeah, use Olivier's benching program linked elsewhere. I've seen 16MHz, can you corroborate that?

I'm not sure how I would check. Can you tell me how to? I would be glad to. I can verify that the new HW3Patch works on it though, no problems. My <about> screen looks just like the pic in the article.

Download the linked and run cpuspeed() . It shows up in the status bar.

I have always noticed that my ti-89 HW2 graphs faster than my ti-89t HW3, so I ran cpu speed on both of them. Sure enough the 89 was calculated at 14.16, and the 89t was at 12.56. Why is the HW2 faster?

Maybe USB overhead? My v200 (clocked at 13.78) graphs almost half as fast as my friend's Ti (clocked at 12.3).

That is, 3D graph.

It does everything faster, games, 3D graphing, 2D graphing, calculating pi, etc.

The new AMS graphing app has discontinuity detection (meaning it wont graph vertical lines at divide by 0 points) But this requires an xres setting of 1.0, whereas the AMS of the hw2 has it set to 2.0.

To change AMS 3.10 xres from 1.0 to 2.0

Go to the graph app (diamond + f3)
to the graph apps settings (f1 , then 9: Format)
turn off discontinuity detection
go to the window setupt (diamond + f2)
change xres to 2.0

Alright, I just did. I says 13.16 Mhz. Is that really much better? The article says 16 Mhz..

Intriguing.

Try running it twice. cpuspeed sometimes returns a lower value when the calculator has just been turned on.

well, I did, and now it says 13.28 Mhz. Big difference.