Anyone interested in my ioFTPD build?

[Prodigy]

UltraFine, could you please trying my new compilation test?

Binaries :

https://mega.nz/#!NA8kyYwR!BUx2cv8mXUzT84BaoO6ktdlp-S3qrLwNlOA1SPqfHdg

Source code :

https://mega.nz/#!MBsikIDD!IsUWlFTvY_Ew4wXiOqFcIEfuSbmOAg2MdppdLkBXNIQ

I have a hunch that your ioFTPD installation still using old TCL lib folder, please make sure to delete old one and replacing it by mine.

[UltraFine]

Originally Posted by Prodigy

UltraFine, could you please trying my new compilation test?

Binaries :

https://mega.nz/#!NA8kyYwR!BUx2cv8mXUzT84BaoO6ktdlp-S3qrLwNlOA1SPqfHdg

Source code :

https://mega.nz/#!MBsikIDD!IsUWlFTvY_Ew4wXiOqFcIEfuSbmOAg2MdppdLkBXNIQ

I have a hunch that your ioFTPD installation still using old TCL lib folder, please make sure to delete old one and replacing it by mine.

Hey Prodigy,

fyi.

I test on two different machines with Win7 and Win10
In the past weeks I was testing ioftpd always on two completely different machines. One my Win7 laptop and the other a win10 desktop pc which has no relationship to the laptop whatsoever. I basically do the setup on the laptop, zip ioftpd and copy it to the desktop. So I always have two identical copies running. I experience the crashes on SCHEDULER events on both machines when I stick EXE scripts into the SCHEDULER. So I would exclude "windows misconfiguration" as a possible reason for that.

Sticking TCL scripts into SCHEDULER seems to work fine
This night I tried out the nxTools NEWDAY script, which is a TCL based solution. The SCHEDULER ran just fine created the NEWDAY directories. Thus I conclude from this that a TCL script in the SCHEDULER DOES NOT crash the ioftpd.

I am using the TCL lib folder from your compilation
I am pretty sure I am using the TCL lib folder from your compilation, because (if I remember correctly) your version would not even start if you have the tcl lib folder from YIL compilation. But I will recheck one more time for you.

Next Steps: Two tests to run?
If I understand you correctly I have to perform two tests now.
First Test: Just the test with the new compiled binary from 18th-Dezember without changing the DEP.
Second Test: Disable the DEP and test with the ioftpd.exe from 30th-November (heh, it would be way better to have some other differentiator than the compilation date)

Correct?

UltraFine

P.S.
Prodigy, one more thing: could you please name your files names in a way that they contain information that makes them easier to differentiate? I have now three different "ioftpd.rar" files in my download directory, and never know which one is the new one or the old one. One solution could be to name them "ioftpd_19122018_Prodigy_compilation.RAR"

[Prodigy]

Originally Posted by UltraFine

Hey Prodigy,

fyi.

I test on two different machines with Win7 and Win10
In the past weeks I was testing ioftpd always on two completely different machines. One my Win7 laptop and the other a win10 desktop pc which has no relationship to the laptop whatsoever. I basically do the setup on the laptop, zip ioftpd and copy it to the desktop. So I always have two identical copies running. I experience the crashes on SCHEDULER events on both machines when I stick EXE scripts into the SCHEDULER. So I would exclude "windows misconfiguration" as a possible reason for that.

Sticking TCL scripts into SCHEDULER seems to work fine
This night I tried out the nxTools NEWDAY script, which is a TCL based solution. The SCHEDULER ran just fine created the NEWDAY directories. Thus I conclude from this that a TCL script in the SCHEDULER DOES NOT crash the ioftpd.

I am using the TCL lib folder from your compilation
I am pretty sure I am using the TCL lib folder from your compilation, because (if I remember correctly) your version would not even start if you have the tcl lib folder from YIL compilation. But I will recheck one more time for you.

Next Steps: Two tests to run?
If I understand you correctly I have to perform two tests now.
First Test: Just the test with the new compiled binary from 18th-Dezember without changing the DEP.
Second Test: Disable the DEP and test with the ioftpd.exe from 30th-November (heh, it would be way better to have some other differentiator than the compilation date)

Correct?

UltraFine

Prodigy, one more thing: could you please give your files names that contain information that makes them easier to differentiate? I have now three different "ioftpd.rar" files in my download directory, and never know which one is the new one or the old one. One solution could be to name them "ioftpd_19122018_Prodigy_compilation.RAR"

Yes, that would be correct, will do about archives naming. FYI you need to always replace all of the *.dll, *.pdb from my archive into the system folder, the mandatory lib folder replacement is required as the one on my archive is newest & compatible with the libraries that is linked with the ioFTPD in term of TCL 5.9.x branch.

What is your preliminary test of my newest build?, not crashing anymore or bad news :-(?.

Btw you could send/P.M me your dumps now if it's still crashing.

My preliminary test was only done with ioNinja addon.

[UltraFine]

Originally Posted by Prodigy

Yes, that would be correct, will do about archives naming. FYI you need to always replace all of the *.dll, *.pdb from my archive into the system folder, the mandatory lib folder replacement is required as the one on my archive is newest & compatible with the libraries that is linked with the ioFTPD in term of TCL 5.9.x branch.

What is your preliminary test of my newest build?, not crashing anymore or bad news :-(?.

Btw you could send/P.M me your dumps now if it's still crashing.

My preliminary test was only done with ioNinja addon.

Current status is: ioftpd from 30 November is crashing on SCHEDULER events of EXE scripts like NEWDAY and SEARCHLOGCREATE of IOA. TCL scripts as SCHEDULER events seem to work fine.

Tonight I will be testing:

WIN10 machine: Will continue running the test of ioftpd from 30th November where I check if TCL scripts in SCHEDULER crash ioftpd. Last night the TCL script NEWDAY of nxTools did not crash iofptd. I keep ioftpd running for another day now, to see if it will stay stable this night too.

WIN7 machine: I will test ioftpd from 18th Dezember with EXE scripts in SCHEDULER (IOA). I replaced all non *.ini files in /system directory and I replaced the /lib directory.

We will see what will happen.