Is there any possible .bat or .ps1 method to automate progression to the next bit after hitting buffer overflow (which as a gross rookie, I assume to mean what I was testing wasn't in that range and time to move on; please correct me if that's dumb) or past x% progression? Perhaps start /w "vs-kangaroo.exe -switches go here" and put each progressing start /w in a batch file?
Would it be feasible to add this as a switch (like perhaps -c 120 would continue onward to/thru the 120 bit range) in a forthcoming revision? Obviously it would have to cycle thru the initial steps that occur at the beginning (figuring jump size, etc), but a set/forget/check on occasion for an output file would be quite a handy thing.
Thanks for your continued work!
Is there any possible .bat or .ps1 method to automate progression to the next bit after hitting buffer overflow (which as a gross rookie, I assume to mean what I was testing wasn't in that range and time to move on; please correct me if that's dumb) or past x% progression? Perhaps start /w "vs-kangaroo.exe -switches go here" and put each progressing start /w in a batch file?
Would it be feasible to add this as a switch (like perhaps -c 120 would continue onward to/thru the 120 bit range) in a forthcoming revision? Obviously it would have to cycle thru the initial steps that occur at the beginning (figuring jump size, etc), but a set/forget/check on occasion for an output file would be quite a handy thing.
Thanks for your continued work!