Eurocopter AS332 for FSX:SE: missing CALLOUT.CAB and CALLOUT.dll CALLOUT_SOUND.dll

Ulrich,

What you’re seeing (a 0‑byte “Callout” file plus a CALLOUT_SOUND.dll) usually means the package you downloaded is either incomplete/corrupt, or it was re-packed at some point and the original “callout” gauge/cab never made it into that archive.

A couple of points to clear up the confusion:

1) CALLOUT_SOUND.dll is not the same thing as CALLOUT.dll
Even if it’s “doing callouts,” FSX won’t treat it as a drop-in replacement for a different DLL name. If the panel.cfg is calling CALLOUT.dll or a CALLOUT.CAB gauge, renaming files generally won’t fix it (and can actually break loading if exports/entry points don’t match).

2) A 0‑byte file is never right
A zero-length “Callout” file can’t contain a gauge or module. That alone strongly suggests the download didn’t come through correctly, or the archive was built wrong.

Practical things to check (quick triage)

1. Open the helicopter’s panel.cfg and search for the word callout (or CALLOUT).
   That will tell us exactly what FSX is expecting to load (a .CAB gauge, a .GAU, or a .DLL entry).

2. Check these common locations depending on what the panel.cfg references:
   • If it references CALLOUT.CAB, look in FSX\Gauges\.
   • If it references a DLL module, look in FSX\Modules\ (some older installers used that).
3. If you already installed and you’re getting a startup error, note the exact wording FSX gives you (it matters whether it’s “missing,” “failed to load,” or “not a valid Win32 application,” etc.).

What I suspect is happening
If the “current description” you mention is still talking about installing CALLOUT.CAB and CALLOUT.dll, but the actual download only contains CALLOUT_SOUND.dll and a 0-byte placeholder, then you likely have a newer (or incorrectly re-uploaded) archive that simply doesn’t include the required callout gauge anymore. In that case, Windows search won’t find CALLOUT.CAB because it genuinely isn’t on your system.

A few targeted questions so we can pin it down

• Are you getting an FSX:SE error message on startup/load? If yes, what does it say exactly?
• Can you paste the line(s) from the aircraft’s panel.cfg that reference CALLOUT/callout? (Just those lines.)
• Where did you place CALLOUT_SOUND.dll (Gauges folder, Modules folder, somewhere else), or have you not installed it yet?
• Is this the original AS332 package you downloaded “a few years ago,” or a freshly downloaded copy from the library today?

Once I can see what the panel is actually calling, I can tell you whether you’re missing a CAB gauge, a module DLL, or whether the package needs to be re-downloaded/repacked because it’s incomplete.