Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.
dll not getting registered on win 95/98
Active-x dll is not getting registered on win 98/95 machine. But works fine on win 2K machine. The error code i get is 0x800700CE on win 98 and 0X80070078 on win 95 machine. The error message is "Filename or extension is too long", where as my dll name and ext is well within range (8.3). What could be the error?
Who is Participating?
The Win95 error code 80070078 actually means "Function Not
Implemented.", which usually points to the use of UNICODE in your control - is this possible? If so, try 'ReleaseMinDependency' or 'ReleaseMinSize'
Implemented.", which usually points to the use of UNICODE in your control - is this possible? If so, try 'ReleaseMinDependency' or 'ReleaseMinSize'
>> I also need to use UNICODE
UNICODE is an "implementational choice", not a necessity. Most ActiveX do not need to be built in UNICODE (only they would get a performance kick under NT4/W2K+)
Unless you do *heavy* UNICODE processing in your DLL, you can relatively safely compile to ReleaseMinDependency" (without UNICODE)
The "UNICODE" setting only tells whether to link to the UNICODE or ANSI versions of Win32 API functions. NT4 & W2K use Unicode internally in (almost) all API's that use strings; additionally they implement the ANSI versions (which convert the strings to/from unicode, and call the unicode version of the function).
Win95/98 implement only a very small subset of the API in UNICODE; enough to handle it but no more.
Peter
UNICODE is an "implementational choice", not a necessity. Most ActiveX do not need to be built in UNICODE (only they would get a performance kick under NT4/W2K+)
Unless you do *heavy* UNICODE processing in your DLL, you can relatively safely compile to ReleaseMinDependency" (without UNICODE)
The "UNICODE" setting only tells whether to link to the UNICODE or ANSI versions of Win32 API functions. NT4 & W2K use Unicode internally in (almost) all API's that use strings; additionally they implement the ANSI versions (which convert the strings to/from unicode, and call the unicode version of the function).
Win95/98 implement only a very small subset of the API in UNICODE; enough to handle it but no more.
Peter
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month3 days, 21 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
Then you'll have to forget about using that control on Win9x - it simply only supports UNICODE in a - err - 'limited' way. See http://support.microsoft.com/support/kb/articles/Q210/3/41.ASP ('INFO: Unicode Support in Windows 95 and Windows 98')