Um..."said while ducking the cross fire" I just got back from out of town and very quickly skimmed over the heated conversation. I will read further this evening and reply but I just didn't want you all to think I abandoned the thread.
Thanks for coming back and sorry for the Um...tangent. We can on occasion get a bit passionate about things.
I believe the bottom line is - We've had 4 members perform fresh installs of AHP 3.204 and 3.206 on multiple OS's (mine was 3.204 on XP). All of these have generated the AHPEEprom_W.txt file.
I'm not sure how you're AHp install could have downloaded to the CM15a without this file. At the moment, it sounds like things are functioning for you (and you probably don't want to fix something that isn't broken). Give us an update if things change.
Thanks,
Boiler
{OK, MichaelC beat me to the puch - here's my $0.02 anyway}
There is a registry setting that can be set to enable a "Read EEPROM" item on the Help menu in AHP, but I can't remember what it is, or where it goes right now. I'll think about it. If anyone has the really old installer for the old "debug" CM15A units we sent it, you can use that -- all it does is set the registry flag for enabling/disabling the menu items.
That's interesting - I have a AHPeeprom_R.txt in the same directory. In fact it's dated 11/6/07 where my _w.txt file is dated 11/2/07. I never paid much attention to this file since it does not update regularly.
I did notice that when I brought up AHP today it issued a P16 code. This is a fairly new PC but the .AHX file traces back to '04. Not sure how this could be related to a registry item, but a switch in the .AHX is possible.