/write STILL Broken! - 17/10/03 02:46 PM
See this thread for the old 6.1 bug thread.
/write is Still broken in v6.12 even though Khaled knew about this problem. Why wasn't it fixed?
Let that run for like 10-12 mins or so... You will see that after like 32,767 /write's you will get an error:
"* /write: unable to open file (line 387, script7.ini)"
After this you can never /write properly again without restarting mirc. (/write alone works, but you can't use /write with any switches.)
I think that 32,767 writes may include logging etc.. also because after the 32,767 writes is reached, you couldn't save scripts in remote editor, when you did, it wrote to the script twice, appending the script to the bottem of the script (see bottom of last thread...... last time at least this was so, i didn't check the remote editor bit this time).
Since the bug is still in v6.12, i'll assume it is in 6.11 too, it is in 6.1, and isn't in 6.03... which now is unusable thanks to the exploit :\ (it'd be nice if the older v6 versions were patched too, for those who prefer the older ones!)
Any plans of fixing this?
/write is Still broken in v6.12 even though Khaled knew about this problem. Why wasn't it fixed?
Code:
alias test { var %x = 1 while (%x != $null) { write -l1 test.txt bugtest %x inc %x } }
Let that run for like 10-12 mins or so... You will see that after like 32,767 /write's you will get an error:
"* /write: unable to open file (line 387, script7.ini)"
After this you can never /write properly again without restarting mirc. (/write alone works, but you can't use /write with any switches.)
I think that 32,767 writes may include logging etc.. also because after the 32,767 writes is reached, you couldn't save scripts in remote editor, when you did, it wrote to the script twice, appending the script to the bottem of the script (see bottom of last thread...... last time at least this was so, i didn't check the remote editor bit this time).
Since the bug is still in v6.12, i'll assume it is in 6.11 too, it is in 6.1, and isn't in 6.03... which now is unusable thanks to the exploit :\ (it'd be nice if the older v6 versions were patched too, for those who prefer the older ones!)
Any plans of fixing this?