NVDA 2009.1 Portable (not completely portable) Development Test 1

I'm sure 99% of the people on here are going to wonder what the heck is going on with my "declaration of non-portability"; here's the two IRC logs from yesterday that explain it all.

Log of #nvda
Log of #portableapps

I was talking with the NVDA devs in #nvda; they proposed a solution for a pretty big problem, and I went into #portableapps to talk it over with Chris Morgan. Turns out the proposed solution was almost as bad as the problem, and an hour of frustration followed. The #nvda log is the main conversation; Chris and I used #portableapps as a private "aside" channel, almost like PM.

The problem is that NVDA injects two DLL's into various processes; the DLL's frequently can't be unhooked, especially from Firefox: when I used SpyDLLRemover to break the DLL hook, Firefox crashed.
After a long, long conversation, we all finally reached a mutual understanding: there's no way on this Earth NVDA can unload the DLL's.
The proposed solution, copying NVDA to %TEMP% and running from there, doesn't solve the DLL unhooking problem; it only makes it easier to work with/around. A reboot is still required to break the hook and delete the troublesome DLL files, so NVDA is not PAF-compliant and, unfortunately, never can or will be.

John, I accept that this can never be an official release because of the %TEMP% problem. However, would it be OK if, after some testing (everything should be just fine, since the launcher just copies NVDA to %TEMP% and gives it one command-line parameter), I created a custom splash for NVDA? It wouldn't be official, true, and the splash would say so, but at least it's better than perpetually having an "Alpha or beta quality" splash.

Also, if somebody could look over the launcher code, I'd be grateful. I had to do yet another ugly hack to work around the DLL hook havoc (it's all documented in the code), but I can't get the time plugin working. I had to !include the time.nsh file instead, which is really ugly.