Good morning, I've been fixing a few more bugs. I'm still working on
the reload configuration, which attempts to read immediately without waiting for amiga to finish writing the buffers to disk. However,
without using that option, it's quite stable, it's been working
without problems for two days.
If anyone tests it and reports any bugs, I'll be available here while
I work on fixing the reload configuration error.
I have uploaded the binaries and libraries for ixemul to github.
https://github.com/skbn/binkd/releases
REPLY: 39:190/101.1 69dde6a2
MSGID: 39:190/101.1 69de49bc
CHRS: UTF-8 2
TZUTC: 0100
TID: CrashMail II/Linux 1.5.1
Hello Tanausu!
14 Apr 26 07:50, I wrote to all:
Good morning, I've been fixing a few more bugs. I'm still working
on the reload configuration, which attempts to read immediately without waiting for amiga to finish writing the buffers to disk. However, without using that option, it's quite stable, it's been working without problems for two days.
If anyone tests it and reports any bugs, I'll be available here
while I work on fixing the reload configuration error.
I have uploaded the binaries and libraries for ixemul to github.
https://github.com/skbn/binkd/releases
For now, I've found a workaround for the reload configuration problem by adding a short timer to wait for Amiga to fully write the file.
The options I've tried are the usual ones:
-s -c -C -p -P
Now, before continuing, I'm going to clean things up. I've included too much Amiga code without #define, and I need it to compile on other systems. I've also fixed some bugs in the *nux version.
... It now compiles for any *nix environment. And I fixed some bugs,
... It now compiles for any *nix environment. And I fixed some
bugs,
Interesting! Are those bugfixes documented and/or in a git repo?
mostly memory leaks, bind problems, and issues with select and accept sockets due to thread blocking or forks. The rest of the system is
working fine, but that darn reload on the amiga with ixemul... it's a
real headache.
The idea is to get it stable, and then do the Amiga part without using ixemul.
Stephen Walsh wrote to Tanausu M. <=-
Hello Tanausu!
14 Apr 26 23:18, you wrote to Wilfred van Velzen:
mostly memory leaks, bind problems, and issues with select and accept sockets due to thread blocking or forks. The rest of the system is
working fine, but that darn reload on the amiga with ixemul... it's a
real headache.
There's the problem right there, ixemul! Plus the memory leaks, it's a wonder the thing worked at all.
The idea is to get it stable, and then do the Amiga part without using ixemul.
Good luck with that...
... It now compiles for any *nix environment. And I fixed some
bugs,
Interesting! Are those bugfixes documented and/or in a git repo?
Yes, I need to organize it a bit. I was racing against the clock
because of my classes. While trying to fix the reload config issue,
the other problems kept popping up. I've been fixing the others,
mostly memory leaks, bind problems, and issues with select and accept sockets due to thread blocking or forks.
Wilfred van Velzen wrote to Tanausu M. <=-
Hi Tanausu,
On 2026-04-14 23:18:35, you wrote to me:
... It now compiles for any *nix environment. And I fixed some
bugs,
Interesting! Are those bugfixes documented and/or in a git repo?
Yes, I need to organize it a bit. I was racing against the clock
because of my classes. While trying to fix the reload config issue,
the other problems kept popping up. I've been fixing the others,
mostly memory leaks, bind problems, and issues with select and accept sockets due to thread blocking or forks.
Yet the *nix version of binkd seems to work fine currently, without
these fixes...? ;-)
program,... It now compiles for any *nix environment. And I fixed some
bugs,
Interesting! Are those bugfixes documented and/or in a git repo?
Yes, I need to organize it a bit. I was racing against the clock
because of my classes. While trying to fix the reload config issue,
the other problems kept popping up. I've been fixing the others,
mostly memory leaks, bind problems, and issues with select and accept
sockets due to thread blocking or forks.
Yet the *nix version of binkd seems to work fine currently, without
these fixes...? ;-)
Yes, when solving the problem on amiga, for example, upon closing the
some memory remained unreleased, or child processes released resourcesfrom
the parent. or when resetting the server and client after something has arrived or been sent.the
This also occurs on *nix systems if a forked process is used instead of a pthread, among other things. With ixemul, these errors forced a restart of
amiga.those
In my case, I would choose pgul, which is very well tested, except for
minor issues.
Wilfred van Velzen wrote to Tanausu M. <=-progr
Hi Tanausu,
On 2026-04-15 08:45:03, you wrote to me:
... It now compiles for any *nix environment. And I fixed some
bugs,
Interesting! Are those bugfixes documented and/or in a git repo?
Yes, I need to organize it a bit. I was racing against the clock
because of my classes. While trying to fix the reload config issue,
the other problems kept popping up. I've been fixing the others,
mostly memory leaks, bind problems, and issues with select and accept
sockets due to thread blocking or forks.
Yet the *nix version of binkd seems to work fine currently, without
these fixes...? ;-)
Yes, when solving the problem on amiga, for example, upon closing the
am,from
some memory remained unreleased, or child processes released resources
the parent. or when resetting the server and client after something has arrived or been sent.thos
This also occurs on *nix systems if a forked process is used instead of a pthread, among other things. With ixemul, these errors forced a restart of
the
amiga.
In my case, I would choose pgul, which is very well tested, except for
e
minor issues.
So I suppose you will do a pull request to the main git repo, when you are done, so these improvements will be incorporated, and everbody
using binkd will benefit!? ;-)
So I suppose you will do a pull request to the main git repo, when
you are done, so these improvements will be incorporated, and
everbody using binkd will benefit!? ;-)
Hmm, well, I don't know lol. The source code is on GitHub; I use it for cross-system testing. It's available to everyone. Personally, I'm only interested in it for the Amiga, although I currently use it for testing on Linux and FreeBSD.
wilco.ydns.eu:24558
But mixing patches with pgul's code... well, I'm still not sure.
Wilfred van Velzen wrote to Tanausu M. <=-
Hi Tanausu,
On 2026-04-15 09:00:33, you wrote to me:
So I suppose you will do a pull request to the main git repo, when
you are done, so these improvements will be incorporated, and
everbody using binkd will benefit!? ;-)
Hmm, well, I don't know lol. The source code is on GitHub; I use it for cross-system testing. It's available to everyone. Personally, I'm only interested in it for the Amiga, although I currently use it for testing on Linux and FreeBSD.
wilco.ydns.eu:24558
But mixing patches with pgul's code... well, I'm still not sure.
We want your bugfixes for the *nix version in pgul's code, don't we?
And pgul probably wants them as a pull request. So maybe you should create a new fork of the pgul repository, apply your patches there and create a pull request?
variablesSo I suppose you will do a pull request to the main git repo, when
you are done, so these improvements will be incorporated, and
everbody using binkd will benefit!? ;-)
Hmm, well, I don't know lol. The source code is on GitHub; I use it for
cross-system testing. It's available to everyone. Personally, I'm only
interested in it for the Amiga, although I currently use it for testing
on Linux and FreeBSD.
wilco.ydns.eu:24558
But mixing patches with pgul's code... well, I'm still not sure.
We want your bugfixes for the *nix version in pgul's code, don't we?
And pgul probably wants them as a pull request. So maybe you should
create a new fork of the pgul repository, apply your patches there and
create a pull request?
It's a fork of pgul's, but I still need to clean up my code. I have
scattered around in brackets in the middle of the code, things from theamiga
tests. I also need to remove the reload part from anything that isn'tamiga.
The inbound timings were causing problems with ixemul.
I'd have to test everything thoroughly, which will take some time.
The idea is to apply the patches to yours.
Wilfred van Velzen wrote to Tanausu M. <=-variabl
Hi Tanausu,
On 2026-04-15 09:57:32, you wrote to me:
So I suppose you will do a pull request to the main git repo, when
you are done, so these improvements will be incorporated, and
everbody using binkd will benefit!? ;-)
Hmm, well, I don't know lol. The source code is on GitHub; I use it for
cross-system testing. It's available to everyone. Personally, I'm only
interested in it for the Amiga, although I currently use it for testing
on Linux and FreeBSD.
wilco.ydns.eu:24558
But mixing patches with pgul's code... well, I'm still not sure.
We want your bugfixes for the *nix version in pgul's code, don't we?
And pgul probably wants them as a pull request. So maybe you should
create a new fork of the pgul repository, apply your patches there and
create a pull request?
It's a fork of pgul's, but I still need to clean up my code. I have
esami
scattered around in brackets in the middle of the code, things from the
gaamiga
tests. I also need to remove the reload part from anything that isn't
.
The inbound timings were causing problems with ixemul.
I'd have to test everything thoroughly, which will take some time.
The idea is to apply the patches to yours.
It's not "mine". ;-)
But no problem, I already said "when you are done"... ;-)
The inbound timings were causing problems with ixemul.
I'd have to test everything thoroughly, which will take some time.
The idea is to apply the patches to yours.
It's not "mine". ;-)
But no problem, I already said "when you are done"... ;-)
I'm still struggling to learn english, although I sometimes use a translator :p
I'm still working on it, but I'm finishing the changes.txt file, which is... quite long.debug
ADE uses ixemul 63.1, for which I don't have the source code, so I can't
it step by step. If I use another program that depends on ixemul, thememory
gets corrupted. I don't know if versions 48 or 48.1 have source code.
As for the program, without reloading the configuration, it hasn't
given me any problems in the many days I've been using it nonstop.
I'm fed up with checkcfg xd
Wilfred van Velzen wrote to Tanausu M. <=-de
Hi Tanausu,
On 2026-04-15 11:46:59, you wrote to me:
The inbound timings were causing problems with ixemul.
I'd have to test everything thoroughly, which will take some time.
The idea is to apply the patches to yours.
It's not "mine". ;-)
But no problem, I already said "when you are done"... ;-)
I'm still struggling to learn english, although I sometimes use a translator :p
I can understand what you are saying. So you're doing fine. ;-)
I'm still working on it, but I'm finishing the changes.txt file, which is... quite long.
ADE uses ixemul 63.1, for which I don't have the source code, so I can't
bugmemor
it step by step. If I use another program that depends on ixemul, the
y
gets corrupted. I don't know if versions 48 or 48.1 have source code.
I don't know anything about ixemul...
As for the program, without reloading the configuration, it hasn't
given me any problems in the many days I've been using it nonstop.
I'm fed up with checkcfg xd
;-)
I just uploaded the latest version I consider stable, although I still need to fix some *nix issues, as well as some warnings and dangerous alerts that clang displays on bsd.
With ixemul 63.1, there must be some bug when using malloc and free in non-thread-safe mode.
I'll check Aminet to see the code for version 48.
If you want to try the linux version, I encourage you to do so :d
But do it in a virtual machine, you don't want your pc to explode xD
I'm going to continue filling out the changes document... I had it separated into several files. I need to organize it properly.
ADE uses ixemul 63.1, for which I don't have the source code, so I
can't debug it step by step. If I use another program that depends on ixemul, the memory gets corrupted. I don't know if versions 48 or 48.1 have source code.
Hi Tanausu,
On 2026-04-15 12:29:23, you wrote to me:
I just uploaded the latest version I consider stable, although I
still need to fix some *nix issues, as well as some warnings and
dangerous
alerts that clang displays on bsd.
With ixemul 63.1, there must be some bug when using malloc and
free in
non-thread-safe mode.
I'll check Aminet to see the code for version 48.
Isn't the 63.1 source code here: https://sourceforge.net/p/amiga/code/HEAD/tree/ixemul/
?
If you want to try the linux version, I encourage you to do so :d
But do it in a virtual machine, you don't want your pc to explode
xD
I'll wait until you are finished! ;-)
I'm going to continue filling out the changes document... I had
it
separated into several files. I need to organize it properly.
Sounds like a good idea! ;-)
ADE uses ixemul 63.1, for which I don't have the source code, so
I can't debug it step by step. If I use another program that
depends on ixemul, the memory gets corrupted. I don't know if
versions 48 or 48.1
have source code.
https://aminet.net/package/util/libs/ixemul48.2-060
Looks to contain the 'c' source...
years...I just uploaded the latest version I consider stable, although I
still need to fix some *nix issues, as well as some warnings and
dangerous alerts that clang displays on bsd.
With ixemul 63.1, there must be some bug when using malloc and
free in
non-thread-safe mode.
I'll check Aminet to see the code for version 48.
Isn't the 63.1 source code here:
https://sourceforge.net/p/amiga/code/HEAD/tree/ixemul/
Thanks, I'll take a look. Compiling it with Bebbo will be torture; 25
that's a long time. But at least I'll be able to analyze it calmly and seeif
I can avoid it somehow.
I just uploaded the latest version I consider stable, although
I still need to fix some *nix issues, as well as some warnings
and
dangerous alerts that clang displays on bsd.
With ixemul 63.1, there must be some bug when using malloc and
free in
non-thread-safe mode.
I'll check Aminet to see the code for version 48.
Isn't the 63.1 source code here:
https://sourceforge.net/p/amiga/code/HEAD/tree/ixemul/
Thanks, I'll take a look. Compiling it with Bebbo will be
torture; 25 years... that's a long time. But at least I'll be
able to analyze it calmly and see if I can avoid it somehow.
This version seems to be from 2009/2010 ish...
Wilfred van Velzen wrote to Tanausu M. <=-years
Hi Tanausu,
On 2026-04-15 14:00:05, you wrote to me:
I just uploaded the latest version I consider stable, although I
still need to fix some *nix issues, as well as some warnings and
dangerous alerts that clang displays on bsd.
With ixemul 63.1, there must be some bug when using malloc and
free in
non-thread-safe mode.
I'll check Aminet to see the code for version 48.
Isn't the 63.1 source code here:
https://sourceforge.net/p/amiga/code/HEAD/tree/ixemul/
Thanks, I'll take a look. Compiling it with Bebbo will be torture; 25
...
that's a long time. But at least I'll be able to analyze it calmly and see
if
I can avoid it somehow.
This version seems to be from 2009/2010 ish...
https://github.com/skbn/binkd/blob/master/CHANGES.txt
A quick changelog.
Wilfred van Velzen wrote to Tanausu M. <=-
Hi Tanausu,
On 2026-04-15 23:31:07, you wrote to me:
https://github.com/skbn/binkd/blob/master/CHANGES.txt
A quick changelog.
That's a lot of changes! ;-)
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,113 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 492304:43:12 |
| Calls: | 14,235 |
| Files: | 186,310 |
| D/L today: |
101 files (23,607K bytes) |
| Messages: | 2,513,964 |