missing export NTDLL.DLL:NT close

[Kalitechnis2]

Hi, folks,

I've just installed a Canon scanner with it's Arcsoft Photobase software, which on loading gives the error message:
"MSACM32.DLL is linked to missing export NTDLL.DLL:NT close.
I am running Windows 98se.

Please can anyone help me with this.
I have tracked down and downloaded NTDLL.DLL, but am loath to put it into windows/system, without some expert advice -is it the correct file? And how do I do it? There is already a version of NTDLL.DLL in my widows/system folder, by the way.
What about the :NT close?

Many thanks for any help,

Kali

[Paul Komski]

There would appear to be a version conflict going on between the MSACM32.DLL and the NTDLL.DLL system files both of which should reside in the Windows/System folder. Don't even know where you got the downloaded file from. The installation probably installed or needs a different version than the one that is there.

You can try renaming them to .old and just paste in the downloaded versions and see what happens; you can then always rename them back to .dll if you need to.

You might also want to try and get back to the original versions by using the system file checker and extracting the files one at a time. See http://support.microsoft.com/default...;en-us;Q129605

[Kalitechnis2]

Thanks Paul,
and sorry for the delay in getting back to this...parental responsibilities take precedence!

I have replaced the NTDLL.DLL using SFC, with no change.

Could it be caused by a deleted registry setting, do you think?

Thanks for your help,

K

[Paul Komski]

It's as likely to be the MSACM32.DLL file. The .dll files are not "stand alone" and call on one another. The MSACM files are Microsoft Audio Compression Manager files. There are three of them: Msacm.dll and Msacm32.dll files from the Win98_33.cab file, and the Msacm.drv file from the Win98_40.cab file.

First check these three files in your system folder to see that they are all the same version and at least version 4.0. A search for msacm*.* should list these three files. Right-clicking on them will let you see the versions. If they are all the same and at least version 4.0 then you can probably leave them alone but could replace them with the originals from the cab files, in case any happen to be corrupted.

If this fails to solve the problem, we can go back to the NTDLL.DLL bit and consider how to maybe uninstall/reinstall your scanner and its software or other things.

PS Forgot to mention to do this after a clean boot. Use MSCONFIG and uncheck all the items in the selective startup. When you have finished turn them all on again.

[Kalitechnis2]

Paul,

Once again thanks for your help..will try out your suggestions when I get a chance.

K.

[Kalitechnis2]

Paul,

It's done-the culprit was the msacm32.dll, not the NTDLL.DLL which I did replace & which I thought everything hinged on. I shall be using the SFC more often now, methinks.

By the way, DXdiag also had a problem on loading, which I felt was caused by the same issue, and that is loading fine now as well..glory be!

And I was planning on a reformat sometime in the near future to sort it out! I'm glad that's no longer necessary.

Many thanks once again..if you're still looking at this post.

K.

[Paul Komski]

Good news. It is perhaps more understandable that dxdiag had gone wonky (since it was a problem with Microsoft Audio Compression Manager files) than your scanner/graphics per se; but then all these things get linked up somehow. That's both the beauty and the beast of computers!