Hi Vali,

You have helped me by asking this question!

I am developing under Windows 2000 but a new client is running Xp on his system and I was to install this next week. Windows 95/98/2000 all used the Kodak imaging controls but XP does not come with them! I went out today and purchased an XP upgrade and installed it dual-boot on my computer. When I ran the program, it would not work. (as you already know!) After a bunch of trial and error, here is what I came up with. I should note that I am not sure if this is by the book, license wise, so you may want to check before you distribute to clients.

I copied all of the imaging OCX's into my program directory and I then got the error that you received. There were 6 dll's that were of the format ????400.dll in my winnt\system32 directory on my development machine. I then copied those to my program directory. Everything seems to be working fine. I am going to be doing some more testing tonight and will let you know if there are any problems with it.

As an alternative, if you look at the link that Igor provided, that company offers a "PRO" version of the windows imaging controls that you can purchase and it provides additional functions such as OCR. They must have taken over for Eastman because the link to eastmansoftware.com from the documentations gets redirected there.

I hope this is of some help.

Bill


>Thank you for your message, but the MSDN link you inserted is not helping me.
>
>I already have an application using Windows Imaging the way it was described in your MSDN link, but it works only for Win98 and NT(maybe for Win2000).
>
>My problem is how to make it work in XP. After installing my application(the installation is also installing the ActiveX controlls) I was not able to run it because it was referencing some DLL missing in XP("IO*400.dll" - came with Imaging software on Win98 and NT - built by Kodak).
>
>So the question is what to do to make it work in XP? Are we having different ActiveX controls in XP? If so, what's the name of it?
>
>Thanks