Nice, I can't wait to see if this will eventually fully support Windows 7 x64

It already does. You just need:
* a 64-bit libusb0.sys. They can be found in some places. (But it would be useful to provide one with Romain's patch fixing it for the Nspire (and some other devices according to people on the fedora-mingw mailing list).)
* a way to bypass the signature enforcement. There are several.

By full support I meant so the user doesn't have to go through that hassle. With TI-Connect, all you do is download an additional 64 bit patch then you're done.

That would require paying M$ for signing the libusb driver. It might also require fulfilling some additional requirements set by M$ which might not be met by libusb, e.g. they might require that the driver must be specific to some hardware and not leave this to userspace as libusb does.

In short: this will probably NEVER happen. You will ALWAYS have to work around the signature crap on 64-bit Window$ (Vi$ta and newer). Blame M$ for this situation, we can't do anything about it.

Not true, I have plans to fix this in the future using an alternative to libusb that is also GPL compatible and other Linux projects have used to solve this issue, if you want more info just ask me and I can provide links but I don't feel like going through my bookmarks atm to find them.

When will an rpm of this be released through calcforge?

Never. The CalcForge software will be packaged instead when released, with Obsoletes for upgrade path.

See what Romain wrote in page #1: Kevin's moves are often about imposing his views to developers and users ;)

In the topic linked to below my name, Kevin nicely summarized this as
"je suis le mainteneur, je fais ce que je veux" (I am the maintainer, I do what I want)
when replying to me writing
"Vu qu'il y a un certain nombre de personnes qui voient l'intérêt de cette option, je ne crois pas que tu aies vraiment le choix de ne pas la garder ;)" (Given that a number of persons see this option as interesting, I don't think that you really have the choice not to keep it ;) ).

When someone (here, Kevin) has so much trouble interacting with so many people over so many years (10 years now !), it isn't the sole fault of the others... especially if most of these others don't have such problems interacting between themselves.
One of the most acute proofs of that is the much more civil tone of yAronet during the long period Kevin was banned: the straw that broke the yAronet owner's back wrt. Kevin was Kevin rejoicing about a database problem and wishing that yAronet would not come back online... Surely that was humorous and the yAronet owner has no humor, right ?

Why would a CalcForge repository ship software which competes with CalcForge software? It just doesn't make sense.

We COULD ship this particular release as an interim solution, but IMHO the necessary QA is better spent on our upcoming releases.

The real problem here is CalcForge competing with upstream in the first place... as a result of your unwillingness to take other persons' opinions into account, and other bits of unreasonable uncooperativeness in an open-source, cooperative project.

> We COULD ship this particular release as an interim solution
Challenge upheld.

You conveniently omitted the part of the sentence where I explained why I don't plan to do this.

Will TIemu development also continue? I've been using it for a while, and it's pretty reliable.

Emu-TIGCC development definitely does continue.

The TiEmu tree at tilp.info is still there and Lionel has committed a few fixes to that (which also went into the Emu-TIGCC tree), but it looks like his priorities are focused on TiLP.

I want the ti-emu (ti-89/v200) in a pocket-pc or iPAD because Texas refuses to put all the commands in the ti-89

http://lpg.ticalc.org/
prj_tiemu/images/tiemu-ipaq-1.jpg

Texas refuses to put all the commands of the ti-89 in the TI-nspire CAS

port of the calculator HP48GX HP49G+ to iPHONE, iPOD and iPAD

www.mksg.de/m48plus/m48plus.html