backup/ipxwrapper
1
0
Fork 0
mirror of https://github.com/solemnwarning/ipxwrapper synced 2024-12-30 16:45:37 +01:00
Code Issues Projects Releases Activity

Rewrote README

Browse Source
This commit is contained in:
Daniel Collins 2009-01-29 20:29:02 +00:00
parent 75c0f30518
commit 4628d507bb
1 changed files with 15 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
readme.txt
View File

@ -2,23 +2,24 @@
-- LICENSE -- -- LICENSE --
Copyright (C) 2008 Daniel Collins <solemnwarning@solemnwarning.net> Copyright (C) 2008-2009 Daniel Collins <solemnwarning@solemnwarning.net>
Read license.txt for the licensing terms. Read license.txt for licensing terms.
-- INTRODUCTION -- -- INTRODUCTION --
ipxwrapper is a winsock wrapper which intercepts IPX socket calls and tunnels IPXwrapper is a winsock wrapper which transparently tunnels IPX packets over IP
them over UDP, this allows you to run legacy software which uses IPX on systems using UDP port 54792. To use it, simply copy ipxwrapper.dll, wsock32.dll and
that don't have the IPX protocol installed, it also allows you to tunnel the mswsock.dll to the directory containing your legacy program.
connection over IP tunneling software such as Hamachi.
ipxwrapper currently supports most of winsock 1.x, more of the winsock library
will be implemented over time.
-- INSTALLATION --
To install ipxwrapper, copy the DLL files to the directory containing the legacy
program exe, you need to do this for every program you want to tunnel.
DO NOT REPLACE THE WINSOCK DLLS THAT ARE IN YOUR WINDOWS/SYSTEM32 DIRECTORY AS DO NOT REPLACE THE WINSOCK DLLS THAT ARE IN YOUR WINDOWS/SYSTEM32 DIRECTORY AS
THIS WILL BREAK ALL NETWORKING SOFTWARE ON YOUR SYSTEM! THIS WILL BREAK ALL NETWORKING SOFTWARE ON YOUR SYSTEM!
Software using IPXWrapper can't contact machines that are using the real IPX
protocol, all systems must use IPXWrapper or the IPX protocol.
-- COMPATIBILITY --
Most of winsock 1.x is implemented, but some software still may not work because
it uses unimpletmented functionaliy. I plan to complete winsock 1.x support
eventually, winsock2 is unlikely, as the API is far bigger and any winsock2
program should be using IP anyway.