Originally posted by terminalvelocd
For all those who don't have the time or the knowhow to modify the Speedhack program
LOL! Maybe you don't find this to be as funny as I do, but I think it's hilarious because just a little while ago, the concern was about people who didn't have the "time or the knowhow" to use a hex editor and to go around hunting for speed codes. And now it's "time or the knowhow" to modify the Speedhack configuration.
1) I do not have any objections.
2) I realize that my tool isn't very easy to use. In fact, ever since that beta version of someone else's graphical hacker came out, I've had a few people ask me if I would do a graphical version of my tool because they like the ease of the graphical version but don't like the fact that it can't do everything that my tool can. So after a bit of prodding, I'm now considering doing a graphical front-end--an optional add-on tool that would interact with the spdhack and getcodes tools. You would specify the firmwares that you want to hack in a pretty interface, and the frontend will generate a new config file and run spdhack with those generated config options for you. But even if this frontend were to be implemented, it would still take people time to go through and select all the codes to patch, etc., so having them all patched, I think, is a good thing for people who don't want to spend much time on it.
3) So I'm supportive of this idea, but I do want to bring a few things up that you might want to consider...
a) You may want to tell people that they still need to run LDW851FP on your new F/W in order for it to work on the 451S... you didn't say that on your page, and it might confuse people
b) I'm wondering if it might be better for people if, instead of having them download an entire firmware, just have them download a "config.pl" configuration file? It'd certainly be a lot quicker than a 700+ KB file. (but then again, considering the spdhack is 300+ KB, it might not save that much) And all that they'll have to do is overwrite the default config.pl with yours and run spdhack (okay, figuring out how to edit the config might be tricky, but I'm hoping that actually running the tool isn't, especially with pinto2's guide).
c) Actually, if you like that idea, then what we could do is create a little repository of custom "config.pl" files that people could submit, and the config.pl that you used for this could be one of the ones in the repository.
Thoughts, ideas, suggestions regarding the above would be welcome.