Oct
9
Dial-a-fix intimidates know-it-alls
Filed Under Dial-a-fix | 12 Comments
http://forums.techguy.org/all-other-software/609118-solved-dial-fix.html
Basically Dial- a fix .. Does nothing .... Very few cases .. it solves the problem
...and this gem...:
All this can be easily achieved by a batch file
I've seen stuff like this floating around the web before. It doesn't really faze me as it just proves the poster's ignorance.
Dial-a-fix started as a set of batch files which were long and ugly like devil_himself's list of DLLs. Batch language differs slightly between Windows versions, and so do DLL registrations. Obviously, Windows 9x can't register all of the same DLLs that Windows XP can. IE7 also changed a lot of DLL registrations.
After a few months of using multiple batch files for each issue set (Cryptography, Windows Installer, etc) I got tired of having to fix them whenever a new conditional interrupted the workflow (such as a new version of a DLL that is no longer registerable, or to add dependency checks for missing files that I didn't realize could be missing when I first wrote the batch) so I converted the entire project into actual compiled code. This way, I could use real logic instead of a weak batch engine, and support more platforms.
The main problem that I have with that thread is that the junior member penguin47 has said that Dial-a-fix has solved the problem and simply wondered how it works. I wish he had asked me or Lunarsoft.net, but what can you do? Fortunately, the "senior member" devil_himself let him/her know that Dial-a-fix does nothing at all and has implied that it can accidentally fix your problem sometimes. I love that at the end devil_himself stated that this can all be easily accomplished with a batch file. Did you expect penguin47 to have found or written one?
penguin47 found my program, and it fixed the problem easily - for free. What's so wrong with that? Sure, you can easily write a junk batch file that does similar things to Dial-a-fix, but why would you shit on a program that makes it ten times easier and works on multiple versions of Windows, checking for stuff your batch file could never check for? My guess is that devil_himself is not an actual bench technician or has never used Dial-a-fix. I can't imagine any other reason to avoid something that is free and works this well just because you have some kind of batch file pride.
Yes, Dial-a-fix tells you all of the basic commands necessary to perform the same operations (somewhat) in its tooltips but you must remember that there is not enough advanced logic in a batch file to match what Dial-a-fix does now (checking for dependencies, etc).
