ioZS ioFTPD Zipscript - Page 3

Stardog · 03-24-2003, 09:26 AM

Yes, I can add that for next release..

StarDog

bounty · 03-24-2003, 10:54 AM

and add also color's cookie please

for ppl who want/like colors

have fun
bounty

caladan · 03-25-2003, 04:30 AM

hmm shouldn't it work if u use plain color codes?? \0034 for example. i'm sure ioZS writes announces straigt to ioFTPD.log and if dzsbot is reading them out and posting to the chan it will replace the plain colorcode with the color.

just a hint .. because it works project-zs and should be working in ioZS too

Stardog · 03-25-2003, 04:24 PM

Yes those codes whould work (if not \003, then \\003 will work), but I added the cookie for it.

It'll be in next release, which I will put out very soon, as I found a big bug in the locking function..I was creating the mutex everytime with the same name, so ioZS would not run multiple instances (BIG oops!)...

StarDog

Stardog · 04-01-2003, 06:33 PM

Now available on www.iozs.com/ioZS v1.00.rar, version 1.00. Here is the changelog:

04/01/03 v1.00
ioZS:
* Fixed locking routines. Big oops! The mutex name was the same for every release, therefore preventing files from being checked if ioZS was already running once.
* Added $color, and $underline cookies for output.
* Fixed a crash instance when zip file did not have a .diz file.
* Changed ioZS behavior when it encounters an invalid format in an .sfv file. Instead of erroring out, it will continue and try to read the next line.
* Added events to run after release is complete, and after a file has passed or failed a test. Added ONRELEASECOMPLETE=, ONFILEPASSED= and ONFILEFAILED= to the ini file.
* Removed the PROGRESSBAR settings from the ini.
* Rewrote Race logging function to be a little quicker.
* Rewrote all string handling functions to prevent buffer overflows.
* Removed all MFC code.
ioNewDay:
* Now creates the Today link folder if it doesn't already exist.
* Added option in ini, TIMEOFFSET. ioNewDay gets the date from localtime and ioFTPD scheduler is based on UTC time. Now you could schedule it to run in UTC time, and still get the correct date by setting your time offset.
* Rewrote all string handling functions to prevent buffer overflows.
* Removed all MFC code.
ioZSCleanup:
* Rewrote all string handling functions to prevent buffer overflows.
* Removed all MFC code.

Giant · 04-02-2003, 05:20 AM

Looks very nice. I like the function to call for example unrar when an upload is complete. Perhaps there will be a future option to define to unpack to another location (might be possible now but i havent looked into that). Anyway kickas work indeed with this update.

/Giant

malexx · 04-02-2003, 07:09 AM

how this color code work?which syntax i have to post?

Stardog · 04-02-2003, 10:07 AM

Giant: you should be anle to run a batch file and pretty much do whatever you want. If you need any other info passed from the script to your external event, let me know and I can add more cookies.

malexx: basically $color = "\003" so you do like $color1,0blackonwhite$color.

malexx · 04-02-2003, 11:13 AM

hm,yes,but how i do it if i want to have a red font or something like this?

WiZLeR · 04-02-2003, 01:45 PM

heya stardog

first your iosz is very nice but hmm i dont know why have removed

PROGRESS_BLNK=-
PROGRESS_FILL=#

i understand why ya remove the progress_lenght=
but the blank and fill sign would be nice to change i think

coz some ppl wanna use # or & or anything else

maybe you could add this feature again to the next version

thanxx and l8a

Stardog · 04-02-2003, 06:43 PM

malexx: Use normal IRC color codes... I think there is a list of them in the help file for mIRC..

WiZLer: mkay..I suppose I could add those options back in..(I just have to uncomment a couple lines)...but I'll leave the length fixed at 20 chars..

2bux · 04-02-2003, 07:11 PM

Quote:

Originally posted by StarDog
malexx: Use normal IRC color codes... I think there is a list of them in the help file for mIRC..

WiZLer: mkay..I suppose I could add those options back in..(I just have to uncomment a couple lines)...but I'll leave the length fixed at 20 chars..

sure the lenght fixed at 20 is no prob i just thought about the styling ......

|ZOK| · 04-03-2003, 01:13 AM

Just read the install instructions for the new ioZS v 1.01
and i noticed that the:

OnUploadError = ..\scripts\ioZS\ioZS.exe Upload

isn't mentioned like in the previous readme for 0.98.
Does this mean it's not needed anymore?
And if it isnt, how is iozs told to execute when a transfer fails?

----------------------------------------------

PS: I agree with WiZLeR, but I'd like to be able to choose number of chars also.
I've always used 10 and think 20 is a tad too much.
Especially since the rest of the tag can be quite long
for individual tag designs.

-----------------------------------------------

Oh and finally...what changed from 1.00 to 1.01
Changelog.txt doesn't say.

-----------------------------------------------
Otherwise, thx for a truly kickass ZS

Stardog · 04-03-2003, 09:14 AM

If you have the OnUploadError running ioZS, then you will not be able to resume a partial upload.

Check the webpage now, I updated the Changelog. I accidentally deleted the whole website last night before going home

Here...

04/02/03 v1.01
ioZS:
* Fixed a crash when deleting a zip file that was not listed in the .ioFTPD.race file.
* Wasn't updating VFS permissions correctly on incomplete parent tags and progress tags.
* Fixed MP3 releases not announcing.

WiZLeR · 04-03-2003, 01:29 PM

nice if ya think bout the readding of the 2 features ....