webserver template change, small changes

Starting with tomorrow's tarball, only one webserver template will be shipped with aMule - the wonderful litoral design by GeVauDan and Gulp.


This is a first step to improve amuleweb making it a very stable application, which ultimately should be able to support this awesome template concept by GeVauDan.
The name of the skin has been changed to "default" - amuleweb might have to adjust config file.


A couple of small fixes have been committed, too. The progress bar in amuleweb for files > 4GB has been fixed, Stu Redman has committed patches to disable warnings for MSVC builds and for automatic geoip.dat download using the RemoteGUI as well as a compilation fix for the RemoteGUI on MSW when IP2Country was disabled.

MarkAsKnown selection, GeoIP, Win documentation

There were a couple of changes the last days:

LittleAbacus wrote a patch to allow the selection of multiple files for the MarkAsKnown function.

Further work on GeoIP compatibility was done and Stu Redman extended the documentation for Windows builds.

GonoszTopi wrote an instanceless URL decoder, fixed GeoIP flag selection when actived, but not found and patched a sed script to be more portable.

Buffer overflow, notification based EC, MSVC and fixed links

Thanks to a bug report by menos_16, we were able to resolve a nasty buffer overflow error in cas - the command line tool is now fully working again.

lfroen started to rework EC (What is EC?) to use a command/notification system. This will yield in a more stable remote connection experience. Please excuse any EC usage problems during the switching period and report any problems in the forum - thank you!

Stu Redman worked on MSVC solutions for the free Express Edition and solutions for fileview and geoip.

GonoszTopi fixed the links in the amuleweb page shown when there's no template available, so that you should be able to easily get help in this case.

More bug fixes

gtoso and sturedman fixed a bug which affected skin support on localized system.

GonoszTopi worked on the GeoIP integration (IP2Country), making libgeoip optional and prefer static linking .
Edit: I've understood the summary wrong, here's his correction from the comment.

It only checks, if a static link request can be fulfilled and displays a warning if not, reverting to dynamic linkage.

Furthermore he fixed incorrect handling of zipped archives and added another ipfilter file name.

Skolnick's patch to support files bigger than 4 GB with alc and alcc was committed and GonoszTopi fixed the related progress bar display problem.

sturedman also fixed the debug build on MSVC.

Last, but not least, some very good news: gtoso joined our team as a Mac developer and already started on providing valuable help and Mac packages. Welcome!

aMule fileview, configure warnings and Mac GUI discussion

GonoszTopi worked a bit more on the fileview utility. Located in src/utils/fileview it provides an easy way to take a look at binary only files from aMule.

While there is not yet a configure option to compile fileview, it can be easily compiled after running the configure script by switching to the fileview directory and typing 'make'.

The utility itself can be used by executing the mulefileview executable and giving an aMule binary file as argument.

An example:
$ ./mulefileview ~/.aMule/Temp/001.part.met
Decoding file: /home/johkra/.aMule/Temp/001.part.met
Version : PARTFILE_VERSION (0xe0)
LastChanged : 1215680812 (Thu Jul 10 09:06:52 2008 UTC)
FileHash : 834604C8ED9FEB337454B4E75F77CE9F
Parts : 0
HashSet :
TagCount : 18
{ 0x01 FT_FILENAME, 2 TAGTYPE_STRING, "LinkCreator0.7.[contentdb.emule-project.net].zip" }
{ 0x02 FT_FILESIZE, 3 TAGTYPE_UINT32, 128718 (126 kB) }
{ 0x08 FT_TRANSFERRED, 3 TAGTYPE_UINT32, 0 (0 bytes) }
...

You can use this tool to view part.met files as demonstrated or to open the known.met file and view all finished downloads by aMule.


Furthermore he also added a new macro for the configure script, which will allow for a nice formatting of messages and more importantly display all warning messages at the end of the configure output, so no warning will be overlooked in the future.


Lastly I want to point to an discussion in the forum: Mac port - different approach