VBscript Fights Cuda

[Maik]

it gives me type mistmash at ar 0.3 ... (WS2008 eng)

[/size]

Could you PM me / attach the log please?

Maik,

Have you thought of using boinccmd to automate the VLAR removal problem? (Arises from your remark at SETI).

[/size]

That is surely possible, but I wanted to give one assistance with my Script only, not to intervene in the characteristic functions of the BM.

[Raistmer]

Maik,

Have you thought of using boinccmd to automate the VLAR removal problem? (Arises from your remark at SETI).

[/size]

That is surely possible, but I wanted to give one assistance with my Script only, not to intervene in the characteristic functions of the BM.

I second in that If VLARs will be just deleted as files think it would be enough to prevent their devastating effect on current CUDA MB. No intervention with BM is needed, just interaction with filesystem.

ADDON: look here, peoples wanna such ability
http://setiathome.berkeley.edu/forum_thread.php?id=51334&nowrap=true#852707

[Maik]

it gives me type mistmash at ar 0.3 ... (WS2008 eng)

Could you PM me / attach the log please?

[/size]

Thanks to Devaster! I made a small however not insignificant error.
Working on update ^^

Update done ... still waiting for an replay from my 'beta-tester'

[Maik]

Update done ... still waiting for an replay from my 'beta-tester' [/size]

done ...
Thanks again Devaster!

v043


edit: removed file->new version

[Crunch3r]

I just hope that this script won't be misused to cherry pick WUs ... 

[Maik]

I just hope that this script won't be misused to cherry pick WUs ... 

hmm...the script-code is open. you can have a look on it and you will see what it do.
short-version:
 - process watching of defined *.exe (from win task manager)
 - terminate this process if it 60sec idle/stuck. a 4-time-counter will show that.
 - all actions in seti / boinc - directory are read-only
 |- the script is using the OpenTextFile - method with argument 1 (read)
 |- you can check that at http://msdn.microsoft.com/en-us/library/314cz14s(VS.85).aspx
 - the script will create *.txt-files
 |- this will be opened with argument 8 (write at and of file), to check that use same url like above
 - if defined the script will copy crashed wu's to a defined directory to do stand alone tests with taht file.
 |- it will create a copy of stderr from client_state in same directory
 |- if not needed start the script without -sam

[Crunch3r]

I just hope that this script won't be misused to cherry pick WUs ... 

hmm...the script-code is open. you can have a look on it and you will see what it do.

I know, but that not what i had in mind ... since this can work with the regular app as well... get my drift ?

[Maik]

anyone getting anglerange warnings since last update? 

replace cuda_log_043.vbs with attached file


edit: removed file->new version

[popandbob]

The latest update started running fine (once I got all the settings right  )
but after a few min of running it just stopped... no errors no nothing...
Log is attached...

[attachment deleted by admin]

[Maik]

Maybe your mb-seti run out of work ? or closed BM ?

Edit: I've notice you are not setting the temp - folder for crashed wu's. Please edit the *.cmd file and delete the -sam
Just wondering why i write readme-files ...

edit: removed file->new version

[popandbob]

Maybe your mb-seti run out of work ? or closed BM ?

Edit: I've notice you are not setting the temp - folder for crashed wu's. Please edit the *.cmd file and delete the -sam
Just wondering why i write readme-files ...

Still have work and BM still running...

Sorry I didn't read through the changes... I'm not used to reading through change logs for instructions on what stuff does... (Its not a problem on your side... just me... no need to change it)

[Maik]

Still have work and BM still running...

Did you restart script, is it running now ?

[popandbob]

Yes I restarted it and it is running now...

[Archangel999]

i hate when i update to new version and had a BUGG

C:\Documents and Settings\Administrator.TEST\Desktop\cuda_log_0431\cuda_log_043.
vbs(471, 3) Microsoft VBScript runtime error: Invalid procedure call or argument
: 'Left'

[Maik]

What is the setting for your path to seti directory ?
post the *.ini row pls ...