Posts: 15
Threads: 3
Joined: Oct 2011
01-04-2013, 10:14 PM
(This post was last modified: 01-05-2013, 10:01 AM by RoyDJ.)
i used different gui or .bat file i got an error if more wordlist used to straith attack.
same wordlist number i used in .9 , but after timebomb i updated and new version and had this error.
i tested all wordlist single and are ok, i tested in grup and exist a limit, i think in argument length, that burn up this error.
can be done somethings?
Posts: 2,936
Threads: 12
Joined: May 2012
you talk about "same error" and "this error" but you never actually mention what the error is.
Posts: 649
Threads: 18
Joined: Nov 2010
My telepathic powers are down this week, can you post the errors?
Posts: 88
Threads: 16
Joined: Nov 2012
I will try to guess, I have something similiar in windows, When I use large list of wordlists, says me that there is not enough memory. that's what I understand. I can be wrong.
Posts: 15
Threads: 3
Joined: Oct 2011
01-05-2013, 10:00 AM
(This post was last modified: 01-05-2013, 10:07 AM by RoyDJ.)
it think topic title say all, anyway is a popup windows that say "oclhascat64.exe has stopped to work, find solution online or close program"
this happen when i load alot of wordlist, same wordlist i load on 0.9 so it's not a wordlist problem.
normal usage is : oclHashcat-plus64.exe -a 0 -m 1500 -p : --gpu-temp-abort=90 "encripted file path" "wordlist1 path" "wordlist2 path" and so on.
if i put alot of "wordlist path" i got error, but same wordlist number i uded in .9 so the new .12 have a argument lenght limit lower of .9
more clear this time?
Posts: 5,185
Threads: 230
Joined: Apr 2010
Its clear for me now. That issue is known. I was unable to fix it before release because of the time bomb pressure. Thanks for report.
Posts: 15
Threads: 3
Joined: Oct 2011
good, and problem not fire up if use as argument "WlPathFolder" but last updated gui not support this feature
i'll hope this bug will be solved soon or updated gui at least
Posts: 5,185
Threads: 230
Joined: Apr 2010
Just wanted to inform you that the bug is fixed in beta and will be fixed in next release version.