Sun Sep 28 17:32:05 2008 - ioFTPD v6.4.3
Unhandled exception: Access Violation (0xC0000005)
Address: 0x0045D056 [attempting to read data from 0x00000014]
PID=2008, PATH=E:\ioFTPD\system\ioFTPD.exe
Thread ID: 416
System information:
Processor #0 Name: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
Processor #0 Identifier: x86 Family 6 Model 15 Stepping 6
Processor #1 Name: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
Processor #1 Identifier: x86 Family 6 Model 15 Stepping 6
OS: Windows 5.1 (build 2600)
Registry: Microsoft Windows XP
Decoded: XP - Service Pack 2
Page size: 4096
I know .. I run 6.4.3, but this is the latest working version with NxTools 1.2.1 and IoNinja 0.7.1. After this u get problems with NxTools commands, so I can't upgrade until NxTools will be updated!!
Any ideas why it crash so often ?? .. It's like someone is doing a 'KILL IoFTPD' from the GUI menu. The GUI stays up and it's just waiting for someone to 'START IoFTPD' to have it up again as nothing happened!
I've tryied ioftod .6.6.1 and after that, PRE command didn't work (crashed my IO).
I don't think newer versiond of IO will solve that problem either. I did try your little fix
but it's not working for me! Results in another crash:
--------------------------- ErrorInfo ----------------------------
expected number but got "-freespace 16609779712"
while executing
"expr {wide([twapi::get_volume_info $destDrive -freespace]) / 1024}"
(procedure "Release" line 109)
invoked from within
"Release [lrange $argList 1 end]"
(procedure "::nxTools::Pre::Main" line 25)
invoked from within
"::nxTools::Pre::Main [expr {[info exists args] ? $args : ""}]"
(file "..\s09-22-2008 14:19:27 "..\scripts\nxTools\nxPre.tcl" terminated abnormally
--------------------------- ErrorInfo ----------------------------
weisan: Is that error from an nxTools patched with o_dog's modifications? I see a call to the twapi module/package and so far as I can tell that isn't in the regular nxTools distribution and isn't distributed with ioFTPD by default either. It's something I might be using for my own script which is why I noticed it, so perhaps just adding the library might solve that problem or if it is an o_dog mod perhaps he can modify it to not check freespace for the moment.
[twapi::get_volume_info $destDrive -freespace] change that line to [lindex [twapi::get_volume_info $destDrive -freespace] end]
in nxpre.tcl
or update to the latest fix.