You can try to set any speed you like, but setting a speed higher than what your media supports may cause read errors if the drive's firmware doesn't govern it. Example: "-speed 12" will attempt to set the drive speed to 12x.
Then go one folder up to where you see the abgx360.dat file and put that abgx360.ini file you extracted in there right next to it.įrom now on our domain and site is located at with an special reverse proxy now working at for the outdated GUI itself, since it can not corrently handle today's era of always-secure connections. To find out where your StealthFiles folder is, open abgx360 GUI v1.0.6 and press Ctrl+F (and click yes to have it opened for you).
#Abgx360 fix archive#
As such to get the abgx360 app working again you will need to download this abgx360.ini file and extract it from the zip archive to the folder directly above your StealthFiles folder. However, our original first domain has been completely different site for a few years now. Our many thanks to our friends at Team-Xecuter for graciously providing the bandwidth from now on! I was never keen on the nohup thing I was just trying to find a way to make the damn thing work.Sorry for the downtime over the past couple of weeks, but the site has now been moved to a new server. I like the screen idea, not to mention it gives you a way to check in on the process if it acts screwy in the future. I say background it (for debugging purposes not actually writing the script that way) because that will give you the same effect that SAB is giving you when it gets to the CRC issue. Launch a another script from with the SAB post processing script and hope that somehow works.įigure out a clean way to use nohup (it really makes a mess of the output file), and use it for running abgx360 from the scriptĭo not perform CRC check with ABGX automatically from SAB - would have to manually run it though. Why are you running it in the BG? Doesn't SAB already do that when it runs post processing scripts? I've never needed to force it to run in the BG before? You could also try using screen to run it in the BG, although I'm not sure if that would work though.ĮDIT: Downloaded something with SAB - The issue revolves around the CRC check it looks like (thats the last I get back when I manually stopped the script after 20 minutes, when it shouldn't take longer than 10 Mins with high disk usage. Mad props to markus101 for helping with this.
#Abgx360 fix free#
Other than that feel free to take it and improve upon it. I will not offer any support for abgx360 here this is not the place for that.
#Abgx360 fix code#
Remember to change your region code in the config section otherwise leave everything alone unless you know what you're doing. # Search $1 (source path) for folders including _FAILED_, move contents of $1 to $FAILED_PATH if found and exit scriptįAILED_TEST=`find "$1" -type d \( -iname "*_FAILED_*" \) -print`Įcho "failed download detected, abgx360 aborted, removing bunk image"
#Abgx360 fix password#
TWITTER_PASSWORD="****" #Twitter Password TWITTER_NAME="BrandonG777" #Twitter Username OPTIONS="-corrupt -stripcolors -af3 -onlinefirst -fixangle359 -myregion 000000FF -splitvid" # Define abgx360 Parameters
# $1 (source path) is provided by sabnzbd+ upon execution