Wow, and the fact that I'm using flight sim on a pentium chip laptop, ought to tell you how deep my knowledge of computer programming goes. All this is fascinating to me, but I just get so lost when CTD's occur in what seems like such randomness from my untrained perspective.
Often if I can fix things by bypassing them or eliminating them, that's usually the path best chosen for me. I am able to see most of the "important" gauges on the F/18 panel... including the HUD. So whatever I'm missing by bypassing the original 'dsd_xml_sound' file... apparently isn't anything too important (or noticeable).
Of course... when in doubt, hit the "W" key, and I get to fly my F/18 with Cessna gauges along the bottom! LOL (How special is that?)
Actually, one last thing that's interesting to note in all this (that I failed to mention earlier), is that when I first posted this thread the problem was intermittent, and I'd often have to fly for 3 minutes or more before the CTD occurred. It wasn't until I started isolating the troubled files by taking JGF's advice and placing "//" 's in front of the gauge lines in the panel.cfg file one at a time and honing in on the problem, that I would get instant CTD's when I loaded the plane. Actually, forget loading the F-18. It had reached the point that if the naming conditions of the files I had described earlier were met, it would crash trying to load the simulator with ANY plane! So the fact that as I experimented w/ it the CTD seemed to evolve into something different, was a strange occurrence in and of itself.
MSFS 2004 v9.1 & FSX Deluxe Edition w/ Acceleration Pack; Windows 7 Ultimate 64-bit; AMD FX 8120 8-core processor clocked at 4.3Ghz; XFX R7870 2GB GDDR5; Corsair Vengeance 8GB 1600; Corsair 600CX PSU (600 Watt); Western Digital 500GB HDD; Biostar A880GZ AM3+, 125 Watt Max TDP MOBO; Antec Kuhler 620 water cooling