Ready.
This is the goodies page for form@fix. This page is with the form@fix 0.1a version. This is the fix.exe. I also publish include-files here-and-there, and refer to them in the examples. They are subject to the legal-conditions of fix.exe - working as the team.
If you choose to use them, you understand that form@fix, AND OTHER FILES/CONTENT AT THIS SITE, IS/ARE PROVIDED AS IS, WITHOUT ANY GUARANTEES. IT IS THE USER'S RESPONSIBILITY TO MAKE SURE, AS MUCH AS HE/SHE/IT IS EXPECTED, TO ENSURE CORRECT OPERATION, ON THE SET OF PROBLEMS HE/SHE/IT ENCOUNTERS.
IN JURISDICTIONS, OR CONDITIONS, WHERE SUCH NOTICES LIKE THIS, WOULD STILL LEAVE THE SOFTWARE/AUTHOR LIABLE FOR ANY DAMAGES, OR IN ANY WAY, LET LITIGATION TO EXIST, PERMISSION FOR USE IS NOT GIVEN.
In other words, legally speaking, I am not taking any responsibility about what happens with form@fix, when you use it.
You may still contact me, and I would like to help. But generally, FIX is for my own usage, yet. Let me decide later, at some later releases, whether I would like to support some stronger claims of safety. Currently, for a byte-editing techie-tool, even this much of a "guarantee" may be too much. Instead, I should guarantee that, while tinkering with your own code, you would probably hang the system a few times.
In the following text box, there is the batch file to generate the fix.exe. You may copy it to the clipboard and save it on your harddisk (with the file name for a batch file. e.g: "2fix.bat"). Then, run it by double-clicking on it (or, you may also enter the name of the batch file at the DOS-command-prompt).
This batch file generates fix.exe by redirecting itself through the standard DOS program DEBUG which converts the text file into a binary (executable) file.
The debug.com must be accesible while the batch file is running. (Most usually, it is in the directory "c:\windows\command\" and probably no problems will occur, because that directory is already in the path, in most configurations).