-- we're linking against ws2_32 Is this DLL available on all versions of Windows we want to run on?
As far I know <http://msdn.microsoft.com/library/en-us/winsock/winsock/windows_sockets_st
art_page_2.asp>
yes. But I am not sure whether it is installed in the base system or only an option if you want to have networking (like on Win3.1). Probably not too many people would run the tests on a standalone machine anyway, but who knows...
I actually just ran into this the other night. I installed TaxCut 2003 (which, by the way, mostly works with a few native DLL's) when it didn't like Wine's ws2_32. According to the references built into TaxCut this wasn't part of the original Win95 that shipped. It came out shortly after as an add-on and was likely first included in OSR2.
--------------- Brian Vincent Copper Mountain Telecom vincentb@coppercolorado.com
"Brian Vincent (C)" VincentB@coppercolorado.com writes:
-- we're linking against ws2_32 Is this DLL available on all versions of Windows we want to run on?
As far I know http://msdn.microsoft.com/library/en-us/winsock/winsock/windows_sockets_start_page_2.asp yes.
According to the references built into TaxCut this wasn't part of the original Win95 that shipped. It came out shortly after as an add-on and was likely first included in OSR2.
Damnit. How can we test it? It is possible to split out the Winsock calls into a separate executable, invoke it and check the return value. No rocket science, but I can imagine it work...
Feri.
On December 2, 2003 11:10 am, Brian Vincent (C) wrote:
It came out shortly after as an add-on and was likely first included in OSR2.
Not a big deal, we'd be hard pressed to find a Win95 pre OSR2 system these days anyway. We can live with it.
Dimitrie O. Paun wrote:
On December 2, 2003 11:10 am, Brian Vincent (C) wrote:
It came out shortly after as an add-on and was likely first included in OSR2.
Not a big deal, we'd be hard pressed to find a Win95 pre OSR2 system these days anyway. We can live with it.
Well, i have one at home :). If you guys want me to test something just shout but i will be able to test only on friday cause i won't hit home till then.
bye michael
Michael Stefaniuc wrote:
Dimitrie O. Paun wrote:
On December 2, 2003 11:10 am, Brian Vincent (C) wrote:
It came out shortly after as an add-on and was likely first included in OSR2.
Not a big deal, we'd be hard pressed to find a Win95 pre OSR2 system these days anyway. We can live with it.
Hi,
Should we just look win98 onwards? and put win95/3.1 in the past as it very well deserves to be?
I think we should concentrate on win2k, XP compliance myself........
Tom
On December 3, 2003 05:08 pm, Tom wrote:
Should we just look win98 onwards? and put win95/3.1 in the past as it very well deserves to be?
I think we can support win95 just fine for now. Win31 was never in our plans however...
On Wed, 3 Dec 2003, Dimitrie O. Paun wrote:
On December 2, 2003 11:10 am, Brian Vincent (C) wrote:
It came out shortly after as an add-on and was likely first included in OSR2.
Not a big deal, we'd be hard pressed to find a Win95 pre OSR2 system these days anyway. We can live with it.
I have one! It would be a good platform for tests too.
Why not simply link against/use the original 32bit winsock library, wsock32.dll? It does not support raw sockets and some other advanced functionalities but that should not be a problem. No?
Francois Gouget fgouget@free.fr writes:
On Wed, 3 Dec 2003, Dimitrie O. Paun wrote:
On December 2, 2003 11:10 am, Brian Vincent (C) wrote:
It came out shortly after as an add-on and was likely first included in OSR2.
Not a big deal, we'd be hard pressed to find a Win95 pre OSR2 system these days anyway. We can live with it.
I have one! It would be a good platform for tests too.
Why not simply link against/use the original 32bit winsock library, wsock32.dll? It does not support raw sockets and some other advanced functionalities but that should not be a problem. No?
Sure, we need very basic functionality only: socket, connect, send and recv for TCP streams. It's just I didn't find any documentation on it. Can you recommend something? Or just change the version to MAKEWORD(1,1), don't #include <winsock.h> and link against wsock32 instead of ws2_32? Is it supported on each Windows version? Lots of questions...
Thanks, Feri.
On Wed, 3 Dec 2003, Ferenc Wagner wrote: [...]
Sure, we need very basic functionality only: socket, connect, send and recv for TCP streams. It's just I didn't find any documentation on it. Can you recommend something? Or just change the version to MAKEWORD(1,1), don't #include <winsock.h> and link against wsock32 instead of ws2_32? Is it supported on each Windows version? Lots of questions...
I believe you should have nothing to change except linking with wsock32.dll insted of ws2_32.dll. But I believe you already sent a patch so it seems to just work<g>.
-
Brian Vincent (C) -
Dimitrie O. Paun -
Ferenc Wagner -
Francois Gouget -
Michael Stefaniuc -
Tom