It worked on both the NT and 98se machines for me.

-Lane


> Five of you are now reporting this error, and of the four of you who have
> mentioned your operating system, you are running NT4.0. That's reasonable
> given the current hypothesis.
>
> We now believe the likely cause to be an outdated ocx and I would like to
> run
> a test if you don't mind. Error 372 is very commonly mentioned on the web
> and
> is associated with an outdated version of COMDLG32.OCX. One of these is:
>
>    http://fapcm.virtualave.net/faq.htm
>
> but it's on a hundred other pages, too. Actually, 16,000 pages :-).
>
> If your PC did not have a copy of COMDLG32.OCX previously on it, or has a
> copy as new as the one that we provide (June 24, 1998), then everything
> appears to run well. But if you have a substantially older version, one put
> there by some other software, you get the error 372. From what I read on the
>
> web, something about the older version(s) is incompatible with the new
> parameter requests.
>
> Because OCX'es are registered, Windows seeks out an OCX on the basis of its
> chronological entry into the registry (a mini-database) -- and my best guess
>
> is that your systems are referencing an older, incompatible version and
> ignoring the copy we include in the AICS folder.
>
> There are two ways to correct the problem. The first is to delete the
> COMDLG32.OCX from your Windows(Winnt)/System folder (and possibly reboot
> your
> machine to reset the registry). This method unfortunately will screw up any
> other applications that expect to see this OCX in the systems folder.
>
> The second -- and perfectly safe way -- is to change the extension on the
> Winnt/System/comdlg32.ocx file from OCX to BAK (making it comdlg32.bak,
> indicating a backup copy). After you've done this, perform a CNTL+X (cut) on
>
> the same ocx in the AICS folder and paste it into the /system folder.
>
> Doing this will update your copy of the ocx to the newest version without
> affecting any other application or the registry.
>
> At the moment, all of this is a hypothesis. We've never seen the problem
> here
> nor do we have any way to simulate it. You are the guinea pigs.
>
> Let me know how it works, if you try this. It should be perfectly safe. And
> if you don't mind, REPLY ALL so that everyone in this group can see one
> another's answers.
>
> Thanks much,
>
> Wirt
>
>