Hi,
this post belongs in the Mach4 General discussion board. No doubt Tweakie will shift it there when he recovers from
Easter Egg bingeing.
I suspect that what happens is that the edits and modifications you made to various macros meant that they were saved, internally at least,
as individualized files. When you delete Mach4 those files will remain...they are no longer on Mach's list of install files.
When a new install of Mach comes along it just gets written into the same directories and thus your edited macros survive the re-install.
If you need to 'wipe the slate clean' then you need to delete the entire Mach4 directory, and that should take those pesky files with them.
There may be a better method however. If you have macros and/or other small chunks of code scattered throughout an otherwise standard
Mach install....when those files compile they will fault. Mach compiles ALL Lua chunks, both standard install AND individualized chunks into one
master file for runtime. If that file fails to compile there will be compile errors reported, and in particular a location in the file where the fault
occurs. If you open ScreenScript.lua you will find the entirety of the all the combined chunks. Scan down untill you find the line or lines
which are in error. Note that you cannot edit this file directly....you need to go back and edit the macro (or other lua chunk) at its source.
While it might be OK to 'wipe the slate clean' and start again when you are first starting out with Mach4 it becomes very VERY tedious once
you start making you own customizations in Mach. Often the fault is one line, and maybe just a misspelling or miss-click you don't want to have to start
all over again for such a small fault.
Craig