bravi
asked on
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?
ASKER
I have tried releasemindependency, but still get this error msg
Are you using UNICODE?
ASKER
I also need to use UNICODE, i had built unicode releasemindependency while building
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I also need to use UNICODE, i had built unicode releasemindependency while building
ASKER
I also need to use UNICODE, i had built unicode releasemindependency while building
>> 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
ASKER
Thanks, I will not support unicode in my active-x dll
Implemented.", which usually points to the use of UNICODE in your control - is this possible? If so, try 'ReleaseMinDependency' or 'ReleaseMinSize'