due to new and updated os-systems the project won't be supported any more in the future

integrated plug-in engine (examples included) for remote administration and completly custom administration possible

new release is out now with tag out of the cvs repository. bugs fixed: ftp-gateway bug! web-server bug with files of 0 kb. winsock-pool upgrade

give me 1 week - perhaps somebody can test the apps (downloadable via anonymous cvs or webcvs)

version 6 will now support keep-alive connections 'improved performance'!
+ $DOCROOT can be set individually
+ Virtual Paths
+ RAS-Connections can be sorted

i've added some functionality to set the wakeup time in the bios to save power for your proxy server. it' experimental and will be an extra add-on, because not every bios supports the same registers... try my best in the next release

i'm very disapp. to report, that i'll not publish the openssl version of the cina proxy, because it's breaking the gpl license in the point that the openssl library is not an operating system essential on windows like on debian. so you'll have to make your own https and ssl implementation. sorry for that. i think there are several other linked libraries in the cina proxy project, but they all came from M$ and so they are real os-libraries - that don't need to recompile

now analyzing apachebench application for gzip support in web-server...

some errors with connecting more instances via crypt layered sockets... fised some time

Now i'm adding OpenSSL functionality for Secure HTTPS Server, FTP and the Remote Admin Port. I need some time, but i'm sure i'll get it. not so many projects vb and openssl out there - new challenge! do you want to help??

Functionality added: Now the Admin Tool supports ordering the Ras-Connections - so you can manipulate which connection will be reached first.

in the next release there will be support for ISP Proxies. see cvs tarball (latest version)

fixed memory leack problem on nt, fixed winsock pool implementation, fixed multiple server platforms, fixed virtual mappings (webserver), improved logging features available by registry setting, gzip output-handler added for web-server

i've hidden the installer packages, because of an unknown error that is caused of a replace of the ws2_32.dll file in system32 folder - i'll fix it in next release...

new functions are: improved performance, tested under win98/95, telnet problem solved and many more... so check this out... it's coming in the next week ... before you can access it by cvs

so feel free to modify the source and commit changes and better ways or perhaps you want to add yet another better remote admin tool... preneco

now win9x/me/xp/2k compatible - i hope. the tlbs are deleted now but i cannot think that the proxy will now run under nt3/4.x please report it!

the api-function GlobalMemoryStatus compiled under W2k makes problems under XP (this is in the cXPLib.dll) I am working...

ntsvc.ocx and compile instructions added to source distribution. check it out

sorry - the installer package was corrupted. the cxplib.dll was not up to date and so the proxy hangs under win xp. new release tommorrow planned.

new stablev03, less bugs, more config, more stable, more tested, more docs, more features (ip-blocking, user-behavior proxy adblock per user configurable,stable httpproxy, smartremote added, ras.manager improved performance, virtual path mapping added ->web-server)

i've got really hurting feedback- so i'
m not so lucky. but thats ok. see new additions to the homepage. i'm a student and i have not so much time to support any questions pronto ...

xml-features for init and settings like tomcat and not the shitty binary form that takes a special app to manipulate... also added a smart lan remote client for changing and setting adblocker and cache per user, admin user and default user scheme added, new msi-file planned for remote and server package, installer skripts planned to distribute

i 've just created a msi installer package -> so that you can use the binaries.

it is neccessary to register this dll properly in the windows registry. i think i'll add a init routine or a small registry-utility or a smart *.reg file to make it easier for you. first of all i'm packing a win installer app.