Recent changes to bugs

Winsock fill-up Bug that makes MADDIS crash...

2003-01-24T00:25:54Z

We recently had a little bit of testing with MADDIS and
it turned out that after running it a little while it often
seems to crash with an "Automation Error" or
something similar.

Anyway, I was able to trace the root of the error in
terms of why it appears, but not the exact location in
the source that creates it.

The reason for the error is the following: Since MADDIS
supports several synchronous TCP-connections it
requires multiple instances of the MS Winsock-control.
This is achieved by using an array of winsocks.

To keep track of which of these winsocks are currently
unused there is another array:
"Public All_Sockets(1 To 32001) As Boolean"
in the module "damn_server_handler.bas"

when a winsock is in use, then the equivalent boolean
value in the array is set to true and if not then it's false.

Now the problem that occurs is that we somehow seem
to run out of winsocks which should not happen.

Usually when the close function is called on a winsock,
it should automatically clean all the connections and
set this array to false.

So the error is most likely ONE of the following:

1) I somewhere forgot to catch the closure of a tcp-
connection
2) The winsock object just "hangs up" in a busy state
even though there is no longer a TCP connection
3) I am unable to really unload or close the winsock
objects in some case.

This error should theoretically occur quicker if the
automatic subnet-scans are enabled.

I will appriciate help of some debuggers...or
comments/ideas, since I myself don't have a lot of time.

problem while installing

2002-08-23T21:12:39Z

on windows 2000 and windows xp there is a msg during the
installation saying windows installer cannot update
msdxm.ocx because of windows protection

it can be bypass but maddis seems to not work properly as
i cannot obtain any file and each time i close the program it
make an error

please help

Window Refresh

2002-04-04T04:39:22Z

Windows with updating information tends to flicker
with each refresh it does of its information. This
makes reading, scrolling, and otherwise -using- the
information very difficult indeed. You can see this if
you get a lot of nodes or downloads and try to scroll
around.

Self Connection Bites Again

2002-03-25T22:35:08Z

It got worse, not sure what happened..

Ok, If I go to the known nodes window, I know have
pages of my external IP, and now, 127.0.0.1, all after
one another, over and over and over again. This is
useless, this is eating CPU cycles. And, from what
I've seen, this is also propogating. The moment I
contact someone else, I'll tell them about ALL THESE
WONDERFUL NODES! Which means, they get pages and pages
of themself and me :P This has to be addressed quickly.

Excessive Hard Drive access

2002-03-24T23:03:35Z

Nothing seems to be going on, but my hard drive is
really cranking. What's up with that? No transfers
currently, so why the need to slow down everything by
mercillesly working the old HD? Someone clue me in? :)

Self Connection

2002-03-24T23:00:32Z

As soon as I connect to another node, I find it
grabbing MYSELF as a node, then proceeding to connect,
to myself. Now, I'm reasonably sure I'm not going to
find any rare or new files on my own hard drive that I
didn't already know about, let alone marked as shared,
so this seems like a waste of time and energy.

Routed d/ls conflict with passive-mode.

2002-03-12T20:58:44Z

Both routed downloads and passive-mode (for
firewalled users) are implemented now. The problem
is: they don't work together properly (yet).
I think it somehow has todo with the Download_Partial
function. Because if you simulate to download
something via passive mode and have routed-downloads
turned on, MADDIS will not start the download. In
some cases the other MADDIS node will start to
download from itself.

For current usability I disabled routed downloads for
now, so people who need passive mode can use MADDIS
until this issue is fixed.

It will be difficult to debug but generally it should
be able to be fixed.