I know we have a client with OCX's from 1997 that work on 2003 without SP1, you might try it on a system without SP1. Also, if you can identify the missing DLL's you may be able to copy them from an older system. Another thing to consider is locating an old installer, sometimes they include runtime files that are required in addition to the OCX files. Regards, Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd D8453 Scottsdale, AZ 85262 (602) 432-8649 www.thinclient.net steveg@xxxxxxxxxxxxxx _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Evan Mann Sent: Tuesday, July 19, 2005 12:25 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] OT: can't register some OCX's on 2003 Server I have some in house codec apps that use a variety of OCX's, some of them very old (one back from 99). All of them have worked on everything from 98 through XP SP2, but it appears many of these OCX's won't register on 2003 Server SP1. They get a standard LoadLibrary error, which from my research indicates that some DLL's that the OCX needs to register itself are not installed on the system, which seems valid. The likelihood of these custom apps being updated is small, and some of these OCX's are so old the companies don't exist. So I'm not sure how I go about getting these working, any thoughts?