Sorted at last...!
I read the read-me file, (as you do, as soon as you have un-zipped the file), but this time I read it right to the very, very end, (which you rarely do)....

...!
And lo and behold, half way down the text file the following appears ...

...!
--------------------------------------------------------------------------------------------
Quote:
Up to and including Warrior4.zip, when specific Piper gauges were needed I used existing FS2002 files,
replacing bitmaps in them.
In this Arrow I made these myself, turning photographs of the real instruments into bitmaps,
and using EasyGauge to make functioning gauges out of them.
To use gauges made with EasyGauge, a file GaugeSound.dll must be either in the windows\system32 directory or in the
FS2002 main directory; it is in this zipfile.
Un-quote:
--------------------------------------------------------------------------------------------
....So having dropped the GaugeSound.dll file into the Main FS2002 Folder, fired up the prog and selected the Piper III Arrow, it works a treat...!
I had a funny feeling the problem was something to do with the 24, r_c_XX custom gauges!
This is typical of what happens whenever a diddly-doobry.dll file is missing, or not in it's correct place...
So todays lesson is, "READ EVERY WORD IN THE AUTHORS READ-ME FILE)...LOL...!
...don't you just love magical, mystical, .dll files...?
LOL...LOL...LOL...!
Cheers...
Paul.
(England).
Win 8.1 64-bit. DX11. Advent Tower. Intel i7-3770 3.9 GHz 8-core. 8 GB System RAM. AMD Radeon HD 7700 1GB RAM. DVD ROM. 2 Terra Byte SATA Hard Drive. Philips 17" LCD Monitor. Saitek Cyborg X Fly-5 Joystick. ...and a Briggs and Stratton Petrol Lawn Mower.