Yea, I really doubted it would help. Basically, it would mean that AHP had to read a file off the harddisk drive, every time it tired to process a macro. I don't think that is true. At least from my experience, AHP doesn't need to read files all that often once started.
True AHP doesn't need to read a file everytime but it does need a clean file to upload to the CM15A
Also, except for possibly boot-up, defragging a drive doesn't have the significant effect it use to have, many years ago. Today's drives have built-in cache, and that basically eliminates any seek delays in accessing frequently used files (which would be a file that AHP needed to access with each macro).
To suggest that a defragging a hard drive isn't as significant as years prior is flawed!Todays drives although they have cache to speed them up there size is much more thus making defragmentation worse! Speed isn't the only reason to do a defrag I've seen many PCs fail because this simple procedure isn't performed. If left to long the only way to repair is to format. Probably why if you take in your PC to be repaired thats the first thing the repair shop wants to do!
donutlouSince now you have a well performing PC(you've done the scandisk and defrag in that order) it is time to look at the possibility that your AHX file is flawed (corrupt)!
Try recreating a new AHX file but keep it simple as we only want it for testing right now!
Add a few modules and a couple of macros, clear the interface and purge delayed macros, upload the new AHX file and test them for speed!
If speed is the same it isn't the AHX file, post your sample macro!
If the speed is much better then you'll need to look more closely at your macros in your original AHX file.(you may even need to rebuild your whole AHX file)
I've seen corrupt AHX files do some strange things so slow macro performance wouldn't surprise me!Once you have your macros working well back up your AHX file many things can corrupt it and a back up will save many hours of rebuilding it!