dallaz
June 24th, 2002, 04:37 AM
Hi there!
In Win32, there are support for Winsock 2. WinCE3.0 supports only winsock1.1. I understand that on systems that doesn't support Winsock 2, the common way to handle the problem is to replace the winsock.dll (i.e. rename the dll)
Now I wonder... If I do the same thing in WinCE 3.0 - I replace the winsock.dll and add some functionality - Is this ok to do? Do I have to get an approvement from Microsoft?
This is not in the OEM-layer, so the rules for this doesn't apply here? And I haven't changed any of the original code (it's hidden ofcourse..) But the functionality has changed though...
Another problem that turns up here is HOW do I replace the winsock.dll. It's possible if you make the platform by yourself (using platform builder), but is it possible to make a standard installation that does the replacement?
Any ideas and thoughts around this?
/Johan
In Win32, there are support for Winsock 2. WinCE3.0 supports only winsock1.1. I understand that on systems that doesn't support Winsock 2, the common way to handle the problem is to replace the winsock.dll (i.e. rename the dll)
Now I wonder... If I do the same thing in WinCE 3.0 - I replace the winsock.dll and add some functionality - Is this ok to do? Do I have to get an approvement from Microsoft?
This is not in the OEM-layer, so the rules for this doesn't apply here? And I haven't changed any of the original code (it's hidden ofcourse..) But the functionality has changed though...
Another problem that turns up here is HOW do I replace the winsock.dll. It's possible if you make the platform by yourself (using platform builder), but is it possible to make a standard installation that does the replacement?
Any ideas and thoughts around this?
/Johan