Off topic, and, importantly, WRONG! Give the Ubuntu information a miss, Jared, the thread has Windows in the title....jharvey wrote:So I recall I could not uninstall the official 32 bit debs. I seem to recall it appeared they were configured via apt-get, and that typical tools like simplicity couldn't remove them, as those debs didn't follow typical Ubuntu practices. The 64 bit didn't work because those debs definitely didn't follow Ubuntu practices.
So, the Fred proclaimed "official" location has known issues that go unresolved, by official mechanism, as Fred doesn't have time to find some unimportant problem with the debs that do work. However he has time to remove posts about the packages that do work. Makes perfect sense to me....
32 bit on 64 can and does work, with warnings, while installing. The debs that follow Debian standards, which Ubuntu adheres to, because it is a DOWNSTREAM of Debian, work perfectly on multiple variations of 32 bit Debian AND Ubuntu. In contrast, the unofficial packages will NOT install on Lenny, which is currently a required target system. But, the key point, those unofficial debs have CONFLICTING version numbers, which is both against Debian policy, Ubuntu pollicy, my policy and general development basic practices. It is TOTALLY wrong and unacceptable, to publicise the existence of debs with DIFFERENT contents and the SAME version numbers. If you want to spend time trying to figure out WHICH 2.4.6 version of package XYZ you have, you know which forum to visit! This is a quality control thing, and a professionalism thing, and I won't bend on it, period. To quote Austin Powers, this is my bag, baby.
No more Ubuntu stuff in this thread, OK? Thanks.
WRONG! Your setup was the ONLY one that didn't work. It has been working on XP, Vista, 7, and probably 2k for 6+months, and XP and 7 for many more months before that, without fail. I worked through that with you one night, not too long ago, and verified it on several windows machines that weren't yours, that night. I can dig up quotes from you about your machine, if required. Just the other night I setup Abe's machine with both working OLV and working toolchain (thanks Dave, top work with that installer!) with built firmware, I did it in the passenger seat of his MX5 at 80mph on the freeway via a tethered android and did both, with the top down, the wind in my long and annoying hair, inside 30 mins on a virgin win 7 machine. There is no problem with the windows installer, period.Also if you can get it to compile on a windows machine, please let us know. We have not had people verify that the windows compile environment actually works.
Nope, see above, your machine is corrupt and weird, you confessed this to me at the time.I tried a month or so ago and failed. Supposedly I failed because the instructions on tools.diyefi.org were wrong or something like that.
That depends on your system, not the tools, which are simple and infallible. Don't make me dig up quotes :-pThe packages installed just fine, but I couldn't use them to create an S19 firmware file. Shrug, perhaps that fixed now.
No more posts on building firmware, in this thread, either, OK? Thanks.
Let's keep it on-topic about the man's win tuning package and anything related to that.
Jared, I'll give you a call this afternoon, sorry for the delay.
Fred.