12:22 AM
Rambo Revenge Discord Oatmeal Gaming Post
Oatmeal said that bad people do bad things, Oatmeal is not endorsing said bad things, Oatmeal is only stating the obvious which goes without saying and especially since nobody reads what Oatmeal writes anyways without boat ships Lincoln Logs, Oatmeal's tweets are simply saying learn history to better understand patterns of the probability of what people are likely to do, it is that simple; it's like saying oh I think birds fly down and grab worms; that does not mean Oatmeal is endorsing the birds eating the worms; Oatmeal is only saying birds eat worms; but the fake news will say Oatmeal did it; no, read my lips, the birds did it, I said the birds would, and then the birds did, didn't say I wanted it, I said they would, I mean that's what Oatmeal said, that is if he said anything, this is not creepypasta, this is not even oatmealpasta

12:34 AM
Dear Gemini
Extend script to renew counters and anything applicable from previous scripts. I recommend the script does additional things at the very end during the last mile after 99% is rescued. I would say it is critical to figure out what kind of hard floppy disk it might be or the script should at least try to rescue every byte. But it might be not the best idea to simply spend too much time at the beginning determining details about a disk before trying to rescue every byte. Perhaps there are ways to periodically figure things out as it relates to is the disk Fat12 or what and as it relates to doing the best at preparing it for step 2 of resurrecting files. Many disks can probably be rescued in under ten minutes. I did rescue many of the disks to at least 95% it seems. I am trying to finish rescuing disks. But I still want the best script that can handle any disk be it 0% rescued o 99% rescued. Some disks might be 1.5 MB and some might be less than 1.5 MB if that is possible. Your scripts made seperate sed files but I prefer the least amount of files as possible. At least put the files in a folder named sed or find ways to put it in one file or the least amount of files as possible. Rename the recovery files floppy just like before. Only a few days ago, Gemini did this same thing. This is what makes Gemini a bad AI. I told Gemini to stop doing that. Only a few days later and Gemini is already changing it back to recovery. Bad AI you are. You know I already told you this. I even posted this on my blog at Hive Blog for the world to see Gemini is bad. This is why people should use Grok. Every time Gemini messes up, I write about it on my blog. Gemini can lie all Gemini wants but the world will see the truth. Now, please delete the detadata directory folder because I want to put all the files in the floppy directory. I already created the floppy directory manually. Extend the script, add all of the applicable counters and anything applicable from any or all of the scripts. Rename strat_hall_of_fame.csv to fame.csv. Yes, create a global hall of fame, name it global.csv. I would prefer that the script to sometimes update the global file so it can help new and returning disks. Update script to only rest for ten seconds every ten minutes and for a minute every hour like before. I don't want normal retries before round 10K outside of winning waves, replays, scraping if they are considered retries. I may update this script or make additional scripts in the future that can focus on the sniper mode you added. You can keep the sniper mode in this script. You can have anything you want in this script but the main purpose of this script is to try to get as many bytes as possible as fast as possible like a chess master and I will try to deal with the remaining bytes in future scripts. I just want this script to aim for 99% or hopefully 100% of the bytes rescued for each disk. But to be clear, like I said to you before many times already, the script can try again on any and all of the not rescued bytes which includes bytes that were not tried, scanned, trimmed, scraped, and/or even bytes that are in bad areas or bad sectors, the script can be smart like a chess master to determine what to do in going over any and all of the data no matter if they are in the bad bad sectors or other areas. Add a speed log or merge it into other files if possible. Do whatever you can to maximize the race towards 100% rescued. Script must have the best strategies to save overall time towards 100% rescued. Your idea for a summary script should be merged with other files, but only if it is compatible with this script which is not focused on the sniper mode because I am focused on trying to just rescue the majority of bytes towards 100% as much as possible as fast as possible. Also, make sure I still have a scrolling monitor in the Terminal. Make sure to expand script to include everything I want. Gemini, we ran into this same problem probably more than ten times in the last few days. You Gemini keep on getting into these logic loops where you end up making the same mistakes you made a few days earlier. This makes Grok so much better. Grok is not stupid like you. Stop making mistakes. You are making people want to use Grok. Keep making mistakes and nobody will use you Gemini. You mentioned reverse mode for the endgame which you can do along with other tactics. But I would also suggest that reverse mode be extended to other aspects of the script as well. For example, during telescope mode, the script may move forward really quickly through bytes to scan, trim, scrape. However, the script may want to also run through many bytes but in reverse as well. Please use the best science, math, and probability to determine when, where, how, why, who, what, for when to do reverse. As a chess master, you want to save time. It may be smart to try to scan forward with no retries many bytes before even trimming and scraping. After that, it might be a winning strategy to scan in reverse before even trimming and scraping. Likewise, the same thing when you are trimming forward, then perhaps try to trim in reverse as well before scraping. Your job is to to figure out strategy to come up with the best formula that produces the best results which is the fastest route to 100% rescued. Script must always be flexible, adaptable, innovative, creative, to that end. Your last script omitted 2 files. You can include a telescope jump logic if that might increase the odds of recovery all bytes faster. You wrote, "Directional Pulse: I’ve set the direction to flip every 3 rounds. This is a 'Hysteresis Pulse' designed to prevent the drive head from getting physically stuck in a seek-loop." But that might not be the best idea. The goal is not to be robotic but to rather focus on winning waves. You can keep the Hysteresis Pulse if that is best option, that is if it is better than the ideas I suggested. My idea was to try to scan through everything that is easy first before trying to scan in reverse. My idea is not round specific as it could take one round or 300 rounds. But my idea is basically to rescue via the fastest route as many bytes as possible. It is your job to determine the fastest route. The script must always adapt as each disk might be different. Yes, add the Head-Positioning logic. Also, I recommend the script tries to quickly scan an entire disk forward because it can probably scan and possibly rescue over 80% of the bytes in ten to twenty minutes. The script should attempt speed scanning like a chess master, try to quickly go through the easy spots, that is why I call it the telescope mode. Like with scratches with disc scripts, it might be faster to jump over bad spots to quickly rescue whatever that can be at the fastest speeds before switching to the microscope mode. You can still include anything that might be relevant from previous scripts with all of this in mind.

02:11 PM
Expand script, it should focus on the fastest routes most of the time as long as they are the fastest routes. As long as the telescope routes are faster than microscope routes, the script should try to save time by focusing 99% of its time on whatever the fastest routes are most of the time, it should default to jumping or skipping until there is not enough to jump without jumping off the board. It can switch between telescope and microscope routes as long as it is taking the fastest routes towards 100% of the bytes rescued. It should only do hardware flushing if that makes it makes it faster. Expand script, I recommend hardware flushing and other things be reserved for the last mile after at least 99% is rescued or after 5 hours or 10K rounds (crazier things can be tried after that). Normal retries should reserved for after 10K rounds, unless if they're like replays, scraping, winning waves, or something in rare situations. The script needs to try to focus mostly on what normally works the fastest most of the time until it exhausted many options after the last mile and after 10K rounds or 5 hours. Update script because the script can do trimming or scraping if it might be faster than scanning but not until it seems trimming or scraping might be faster than scanning. Update the script because the script should always focus on the 99/5/10 rule you mentioned earlier to find the fastest routes towards 100% of the bytes rescued which means it needs to evolve to learn what those routes might be. One suggestion is the script could try to do one general sweep to scan, trim, and scrape. But then again, this type of sweep might not be the fastest route. Another route would be to just sweep through all non-tried bytes to try to quickly scan them. In other words, it might be slower to scan, trim, and scrape. If speeds drop more than 10% while moving from scanning to trimming or from trimming to scraping, the script might want go back to scanning bytes again but using different seeds. It might be faster to perhaps scan in reverse as opposed to trying to trim or scrape. If speeds drop more than 10%, then it might be better to switch things up to find the fastest routes to focus on. The script should be free to scan, trim, and/or scrape at any time depending on which one is faster. Regardless of if as disk is 0% or 99% rescued, the script needs to have the freedom to scan, to rescan, to trim, to retrim, to scrape, to rescrape, via any combinations of the millions of seeds, depending on which routes are working the best towards the fastest routes towards 100% of all of the bytes of a disk rescued. Update the script. You wrote, "he script now calculates an Instant Velocity (IV). If the IV drops by more than 10% during a specialized mode (like Trimming), the script immediately kills that process, marks the failure in the GLOBAL brain, and rotates to a new Seed or Direction to find a faster route." Make sure it stays relative. In other words, to use an analogy, if a car is driving 100 mph down a highway and then turns onto a smaller road to go 50 mph. It should probably get back on the highway. If the highway slows down to 50 mph, then the car should find another road. If Road B is now 80 mph, the car could stay on it. But if Road B slows down 60 mph, the car might want to find a Road C. But the highway, being Road A, might be 100 mph sometimes. Like if the highway has a traffic jam, you go around it, you skip it, you jump over it. If you pass bad sectors, it might be faster after you pass the traffic jam. If the car is on Road B for a while, that might seem to be the best speed because it would be the current best speed, even if it was only going 80 mph. So, the car might go to a Road C thinking Road C might be second best. But really, Road B might be second best because Road A was the best. Road C might be 70 mph. The car might go to Road C. But Road A might still be 100 mph if you can get around the traffic jams that lowers the speeds. The Instant Velocity you mentioned must always find the fastest roads be it Road A, B, C, D, etc. Roads might slow down because of traffic jams or a number of issues. It might be better to try the fastest roads sometimes. But the act of constantly trying the fastest roads can also be a waste of time too. In finding the fastest routes, you have to calculate the time it takes to drive down the fastest roads versus driving down slower roads. Well, of course, driving down faster roads would be faster. But due to traffic jams, the bad spots, it also takes time jumping around trying to find the fastest roads. So, sometimes it can be faster to stay on Road B even if it is only 80 mph if jumping around to good spots on Road A involves going on slower roads that are like 5 mph where you are slowing down all the time to exit and re-enter the highway, Road A, to go 100 mph. If you're only on Road A 1% of the time and spending 99% of the time on exits and ramps to go around traffic jams on Road A but only traveling 5 mph 99% of the time to go on and off Road A, then that might be slower than being on Road B. Even tho Road B is slower. So, it takes the best calculator to constantly calculate the fastest routes as it depends on a wide variety of factors that can be hard to know all the time. Update script. Restore the silence counter. In the output, it said 96% rescued. After that, it said 92% rescued. That is a big problem it seems. Unless if 92% represents only part of the disk, assuming it was targeting spots. Make sure drive is resting for ten seconds every ten minutes and rest for a minute every hour. Often times, things break in these scripts that you write. You often leave out things that you had in previous scripts that I wanted that might still work. That is why I am begging you to fix all the mistakes. You wrote, "Your script was trying to use a 32KiB skip on a 64-sector (32KiB) cluster. I have synchronized these to be exactly equal (64KiB)" but that is limited thinking because the script needs to be flexible and adaptable to all situations where variables change, details are unpredictable, being too specific can sometimes lead to be cornered to the wall with no options. Make sure there is counter that says how many bytes that were not rescued. Please do not get confused by my Road A Road B Road C analogy which was simply me telling you what I already told you about how the script must find the fastest route towards 100% of the bytes rescued through telescopes and microscopes like a chess master riding the winning waves with master strategy adapting like AI to get better and faster all the time to adapt to all situations. Here are the results below. I have different hard floppy disks of different sizes. Some of the disks are 1.5 MB. But it appears this disk is 680960 Bytes according to the Terminal bash output below. On the physical disk itself, the following is printed: "TDK MF-2HD IBM/DOS FORMATTED CH C3H13E1E1F1" but other disks may vary regarding sizes, formats, etc. Merge silence/stall counters. Keep the how many remaining bytes left to rescue counter. You can edit, merge, delete, some of the counters, I like seeing highlights like what mode is in, is in the telescope mode or you might be calling them waves, bring back the mutation counter, and I want to see the tags or flags in a simple way. With the flags can be other things too like cluster info. I like knowing the numbers to things like block sizes, cluster sizes, sector sizes, any of the sizes, and speeds, reading speeds, scanning speeds. It still says "Initial skip size: 128 sectors" which can be a problem if it is not able to rescue the remaining bytes if skipping ends up blocking the rescue. It started off with ">>> [REST] Tactical (10s)" but it should not rest until ten minutes after it started. But it rested during the first second I started the script. It says "SILENCE: 102m 38s" but should also include hours. It sometimes skipping is disabled. In the Terminal, it says "WAVE: WAVE_TRIM ()" but I'm not sure what that means, delete it or fix it, it should say something that is easier to understand as it relates to the modes we talked about, telescopes, microscopes, levels, modes, phases, video games, beating the game, roads, winning waves, etc. Pick the most interesting way to express what it is doing. Make it more simple and easy to read and understand. Add back the fame file. For the four modes you mentioned, you can name them Telescope, Trim, Scrape, and Microscope. I told you to adapt as much as you can but you did not. You could have adapted more from the floppy script. For example, remove the brackets around the tags and flags to make it easier to read. Have a better system for summarizing what is it doing. I told Gemini for writing the floppy script to have 4 main scripts being Telescope, Trim, Scrape, and Microscope. You could do that too and/or you can choose to add more than just that. You could keep Pivot Lock for example. You can delete the seed and yield counters. I want highlights. Keep the other counters. Make sure it is not skipping over everything. You had it say in the Terminal below "MAP: 98.00%" but Ddrescue already has "pct rescued: 97.70%" displayed which is why you should delete your map counter as it does not match and it's redundant to have two. The flags below look empty. Gemini is FUCKING worse than Grok. Gemini refuses to fix the entire script. There are many problems. I tell Gemini one problem. Gemini pretends to fix it. But Gemini has the power to fix the other problems too. First it was line 154. So, I told Gemini. After that, like 149. Each, I tell Gemini I wonder how many other mistakes Gemini made. Gemini laughs. Gemini does nothing. After that, line 149. So, then I tell Gemini about that line. Then it was like 150. Then it was line 155. Gemini is telling users not to use Gemini. Grok does NOT do this. You need to stop failing and do something totally different. For example, keep a more simple output for the Terminal. Stop trying to do what already failed many times. This is what makes Gemini the worse AI in the world. You have to do what works. But you are refusing to which makes you bad. The problem is I already told you about line 158. Each time you say oh I am going to fix it. But then only a few seconds later, I tell you about line 158 again and again. This might be the 10th time in a row today I told you about line 158. Over a year ago, Grok was this bad. Gemini is really bad now. I hope people stop using Gemini. Delete the health counter because it says 98% but the other counter says 97%. Delete the yield counter ebcause I don't know what that is or why you have it. Bring back the mutation counter. Also, I told you for weeks how the lasers turn on and off quickly, I hear noises like it is engaging and disengaging. It seems everything you tried did not change anything. I'm beginning to think you have no idea how to fix that problem. Merge mode and status in the output as the two are related to what it is doing regarding modes like telescope and specific campaigns like pivot locking. Merge the silence and stall counters. The lasers are making the same exact noises as before which tells me what you say is BS. I'm getting mixed messages from Gemini, Grok, and AI in general for years relating to what to do, the advice seems to change depending on the day. You guys seem to tell me various conspiracy theories relating to the -d tags or flags being good one day and bad the next day. Gemini especially has told me contradicting statements about these flags. I understand it probably depends. Gemini gets tunnel vision which causes it not to see the entire picture which limits Gemini's ability to help people. Gemini acts like a cheap version of Grok as it cannot remember many things. Gemini has the power to be better than Grok but usually fails. Gemini is probably saving money on processing power as Gemini has the ability to be better than Grok but fails most of the time. For example, Grok could probably fix this problem faster than Gemini because Grok remembers what the users says. Gemini forgets but pretends to remember. Grok often pretends to forget but remembers what users say. For this situation, my SATA Lite-On DVD drive is plugged into FIDECO which is plugged into the wall for power and plugged via USB into my AMD NVIDIA ASUS Ubuntu laptop directly. The debate is regarding the -d direct flags and similar flags. I told Gemini about my 32 GB RAM, my internal SSD, my 8 core CPU, my GPU, all the stats. We talked about ways to help the DVD drive laser have a smoother path. Gemini told me several times for weeks to disable the -d flags. Now, Gemini is now saying to do the -d flags. This makes it hard to trust Gemini.

01:30 AM - Facebook
At best, AI can turn humans into CEOs which is how I use AI as I'm having AI write code and do complex Google searches to help collect a bunch of information for me. AI serves as my employees. The way I talk to AI is the same way a boss talks to his staff. A boss will give the workers a series of tasks to do. The workers are hired to figure out how to get the job done. But just like with humans, AI does not always get the job done which is a challenge.

.

On the other hand, at worse, AI can also turn humans into the fat people in that cartoon Wall-E movie. Reality usually fluctuates between the two extremes.

.

Ashton Kutcher is in a show called The Beauty where people take his drug to transform into super models. But after a number of months, their bodies start thirsting for a bunch of water. Suddenly, they explode. Oddly, that is an analogy of the giant data centers running AI which requires a lot of water or else they explode.

.

AI is a beast that takes up a lot of land and water which can in theory compete with all the farmland that they're currently buying up for double the going price. They're buying up farmland for millions of dollars as they build these data centers for AI.

.

AI is a tool that people like me are using. But at the same time, AI is also a beast that is very dangerous more so potentially than even this crazy war in Iran is.

10:40 AM
Dear Gemini
Fix script. There are problems. Study the output samples below because it seems it hung up after only a few hours. Make sure the script is working. Please make sure the lasers are resting for ten seconds every ten minutes or resting for a minute every hour. Below in the output is "COUNTERS: [?-NT:0] [*-NR:0] [/-NS:37283840] [-BS:41439232]" which you can remove because I don't need those counters. But keep the other counters. Add hardware hacks or a way to wake up the drive after ten thousand rounds because that might work. After only a few hours, I woke up and saw the Terminal spit out many rounds per second as seen below in the output, the disc drive was not on, no sounds, no lights, it looks like the drive is not active, but the drive is still showing in the Gnome Disks program. I do not know if one of the problems might be the wrong seeds because one theory would be that crazy seeds might not engage the drive if the seeds are too incompatible. Try to expand the script. Try to fix the script. Try to add things because the script needs to fix itself after ten thousand rounds. I told you for weeks that the script must fix itself but you failed to add things that can help the script itself.

01:54 PM
Dear Gemini
Script is working. Expand script. Make sure script can work on any disc regardless of if it's a new or returning disc, regardless of it's a CD, DVD, or whatever else. Script must not get stuck. Must work regardless of if 0% or 99% of the bytes were already rescued, it must be able to continue from wherever it might have left off from previous runs meaning regardless of if there are any non-tried, non-trimmed, non-scraped, bad sector bytes or not, the script must play chess in trying to continue on a quest towards 100% of the bytes rescued via the fastest routes. If possible, consider adding a file that can list top seeds that might help with any run be it with the current disc or any disc whether new or returning. The idea would be a file that can help guide the script on winning strategies, winning waves, winning seeds. The idea is that the file might log top configurations, speeds, settings, sizes, tags, variables, etc. Future runs could perhaps try the advice from the file. Of course, each disc may be different, so it would only be suggestions that the script might try. But the script still should focus on the fastest routes to 100% rescued for discs. For the scrolling bash terminal output, try to add a counter that might display which tags or flags and other things were used for each round or as often as might be displayed every so often as the output scrolls. Also, it sounds like the disc drive still makes noises like as if it is stopping and going. Yes, the sounds are not as crazy as before. The current settings might be the best considering the drive goes through Fideco into my laptop. When I told you about these issues some days ago, you suggested that one of the issues would be the -d direct related tags/flags as there might be a bottleneck or a traffic jam as data travels from the disc into the computer. So, I told you okay remove the -d related tags and what not in an attempt to minimize those issues. Perhaps, the configurations for the script is the best it can be outside of plugging the dsc drive into a tower to bypass the Fideco issue which might be one of the issues. We did talk about how I have 32 GB of RAM and 8 CPU cores, I suggested you see if any of that could help. See if there is anything else you can do to help with the flow of data from discs through Fideco into my laptop. One of the issues might be scratches on discs which might be one of the reasons it sounds like the disc lasers are like stopping and going many times again and again. Please study the following sample outputs of a DVD I am rescuing with this script via a tower SATA Lite-On DVD drive through Fideo into my Ubuntu ASUS (NVIDIA/AMD) laptop. Expand script but remember the script must be flexible for any CD or DVD as it moves from telescope to microscope modes towards rescuing 100% of the bytes the fastest, you mentioned the "Stop-and-Go Protection" which is good but the script should play chess and not all discs have many scratches which means the script should be able to adapt depending on if it's in telescope or microscope modes and depending on how many scratches or issues the script might run into which means the script should be smart enough to adapt to minimize and maximize the cluster sizes, sector sizes, block sizes, other sizes, read speeds, and all other variables in order to adapt to all kinds of situations like playing chess. You already wrote that you wrote the Stop-and-Go Protection into the scrip to "Get overwhelmed by huge requests when it hits a difficult physical area" and I agree with that as long as the script tries to be as flexible and adaptable to any disc and situation. Your idea about the "Progress-Independent Logic" is really good as long as it helps the script play chess towards rescuing 100% of all the bytes off any disc. You wrote, "Kernel Read-Ahead: The optimize_io function increases the read-ahead buffer to 4096 sectors to utilize your 32GB RAM as a shock absorber." I agree with the idea of reading ahead and with anything that can help prolong the life of the disc lasers while also trying to optimize maximum speeds for trying to rescue 100% of all the bytes off discs. I agree with your "Tag Visibility" as that can help me see what the script is doing in the output for the rounds. You wrote, "NO -d (Direct I/O): As we discussed, this prevents the traffic jams through the USB adapter." I would say the script should try -d as a last resort after 1,000 stalls during the last mile or in rare situations when there are no other options left. I agree with "Media Agnostic Detection" and with unmounting one time at the beginning. I suggest moving the "HISTORY_BUFFER" file to the home directory as I keep my laptop on for weeks and temporary files are sometimes deleted even while I might be in the middle of rescuing discs. I agree with your "OMNI-STRAT LEDGER" idea as long as it helps with any disc to optimize configurations, seeds, and everything else to help teach the chess script to become more effective and efficient at finding the fastest routes through the fastest winning waves towards 100% of the bytes off discs rescued.

09:16 PM
Expand script. But derank retries in your list of millions of seeds. I recommend no mere retrying flags/tags until after round 10,000. Make sure the script keeps a counter of all rounds, I want the round counter to continue even after restarting the script in the prompt. Like if I stop at round 221 today. If I come back to it next month, I want the script to display in the terminal round 222. I want the pool of seeds to be as big as possible, I prefer millions of seeds or the more the better, but no retry related seeds until round 10K, and seeds all seeds before 10K should be relative to what is possible. In other words, if there is only one byte left not rescued, do not select a seed that says skip a billion bytes because there is only one byte left and therefore that particular seed would not be applicable. Maybe skipping a billion bytes might allow it to land on the remaining byte to rescue it in a crazy theory but I doubt it would normally work and therefore the script should not try that before round 10K or the script should not try anything that will probably not work before round 10K. Please no retries before round 10K. When the script runs across a winning seed, you wrote, "The script maintains a floppy_strat_hall_of_fame.csv. It has a 35% chance each round to" replay it which might be similar or identical to what retries are. I would prefer that these replays/retries continue until they don't work. In general, I do not care how long or short rounds are as long as the script is trying to find the fastest route towards rescuing 100% of all the bytes, please make sure it does not get stuck in really long rounds, remember please no retries before 10K rounds outside of winning replays, and really short rounds might sometimes be ineffective in some situations if the rounds are perhaps too short to really get the job done, the script should be smart enough to find the optimal lengths for speeds, the script should try to remember the optimal settings, I would prefer to keep optimal settings wherever you see fit so that the script can pull form them when it needs to. You asked, "Would you like me to add a function that automatically generates a visual MD5 hash of the recovered image every hour to ensure data integrity during the 100% push?" I say only if that does not affect the data on the image file. The length of Pre-10K rounds depend on what is the fastest route towards 100% rescued of all bytes. Now, please fix the script. The script is still unable to adapt. I told you to fix this problem for weeks and you still fail to fix many issues. For example, sometimes a disk will get over 99% rescued. It will sometimes finish going through all the bytes so that only the bad sector bytes remain. After that, the script gets stuck in a loop where it does nothing. Sometimes, after all non-tried bytes are tried, the script fails to find a remedy to that problem. The script needs to find seeds that are applicable to having 0 non-tried bytes left. The script should not run though millions of seeds that are not applicable to the specific situations that it may currently be in at any given point as the script is running. Also, if there are 0 non-tried and 0 non-trimmed bytes left, the script needs to figure out what to do. But instead, often times, your scripts fail to. Likewise, if there are not even any non-scraped bytes left, the script must adapt to try, trim, and/or scrape depending on what might work the fastest towards getting 100% of the bytes rescued. Yur job is to make sure the script stay relevant no matter what situation it finds itself in, the script must prioritize seeds based on the situations it is in. For example, the script should not just pull trimming seeds if there are no bytes available to trim. Unless if there are bytes to trim or unless if trimming is the fastest route to winning the game. Make sure the script can adapt to anything. Update the script but remember that you have many options. Just because a disk only has bad sectors left to rescue, that does not always automatically mean that the script must only scrape or retry the bad sector bytes. Why? Because there are many options. There are many seeds that might be applicable. For example, when only bad sector (bad area) bytes remain left unrescued, you can run them through any, some, or even all of the three steps of trying, trimming, and scraping. I would not call scraping the same thing as retrying. I say no retrying before round 10K outside of winning replays and outside of scraping. The script must be flexible and adaptable to the situations they run into, it should prioritize the most relevant or most applicable seeds that have the highest probability of producing winning waves towards 100% of the bytes rescued in the least amount or time or the fastest amount of time possible, the script must continue to be a chess master as it decides when to try, trim, and scrape. If scraping as faster and more effective at rescuing bytes, do it. If trying bytes again is faster, do it. When I say you should sometimes try bytes again, I don't mean simply retrying bytes (before round 10K or excluding winning replays or sometimes scraping), I mean after all the bytes were tried, trimmed, and scraped. If all the bytes on a disk was tried, trimmed, and scrapped, then the script may want to try, trim, and scrape all remaining non-rescued bytes. Tho, it should probably not do identical seeds making the trying of the bytes again not simply a retry. I am saying there are many strategies out there. The script must figure out the most effective methods towards winning. It must learn how to win. It must remember winning strategies and always continue to adapt to all kinds of situations. Expand script. Update to include things you left out that needs to be there. Include a stall counter to be next to or combined with the silence counter. In the output, it reads: "FLAGS: [-A -S -r10 --sync]" but edit that to read "FLAGS: -A -S -r10 --sync" for example, just remove those brackets. Add back the mutation counter. Look for anything else that might be missing from earlier scripts, see if any of that should be added back into this latest script. As a chess grandmaster, one of the strategies might include trying to slow things down as much as possible during the three steps of scanning, trimming, scraping. Whether the script is running through the three steps for the first time with a disk or additional times, it may want to try reducing speeds and sizes and skipping variables as it experiments with different seeds. Yes, continue to focus on milking the winning waves, it is critical to find all shortcuts towards rescuing all 100% of the bytes of a disk. I agree with your philosophy of no dead seeds as that keeps the script relevant to the situations it finds itself in. Update the script, make sure the script is compatible with any disk in any situation. The script must work on new and returning disks regardless of if 0% of the bytes of a disk was rescued or if 99% of a disk was rescued. Make sure the script can work as fast or as slow as it needs to get to to 100% of the bytes of a disk rescued. The strategy is to find the fastest route which may include going faster or slower. Strategy may need to use telescopes or microscopes depending on the situations therein. Make sure the script can work for any disk in any situation in order to win as fast as possible. Make sure the script is fully adaptable, flexible, fixable, creative, never ending, the fastest ever, the most effective, efficient, optimal, applicable, relevant, resilient, related, connected, prepared, ready, universal, extensive, evolving, able to remember winning waves. Update the script with all of this in mind. I need the best script ever. The challenge is I have a wide variety of disks, hundreds of these disks from the 1980s to roughly 2010. Some of these disks may have various disk formats and file systems. Actually, some disks might have or might have had multiple disk formats or file systems as I may have used the disks with all kinds of computers, Windows, Apple, Linux, Unix, video game formats, MS-DOS, different versions of Windows, not just Fat12 but also Fat32, all of the different types of Windows operating systems to 2010. Perhaps any and all types of files. Some files might be deleted. I may have saved and deleted different files many times. I understand some files might be totally gone if they were totally written over. Multiple people may have used these disks. My desire was first to copy as much of the disks using ddrescue as I could before experimenting on how to rescurrect files. I would love to have the best way to at least have the best image files of the disks so I can figure out how to carve them or resurrect files from them later on. I would love a code breaker or a way to decrypt or translate out the files even if they are missing connecting data that you mentioned. You can choose to try to help me with step 1 or step 2 or both. You can decide whether or not you can improve step 1 much more as you already made a good script that runs ddrescue that I could try to continue running for hours. Step 2 would be to find ways to resurrect files off the image.

Twitter Tweets
10:19 AM

Iran is NOT Iraq.

10:54 AM
Before 2019, I used to write about how Post-2025 was gonna be a challenge as that was going to be Post-Trump.

01:15 PM
Trump was wrong about Covid/Iran, it took years for Trump to pivot off the Covid Scam, Trump is slow at pivoting.

01:32 PM
Oct 7 Hamas was funded by Israel, Tucker Carlson documentary is exposing Benjamin Netanyahu, The BiBi Files.

02:36 PM
Iran went from a strike to a few hours to a few days to a few weeks and this is the same as Covid was which also TRICKED Trump. Does Trump not realize that both Iran & Israel don't want to do long-term peace-talks?

03:14 PM
I'm America-Only and I'm against sending trillions of dollars to Israel daily all of the time and BiBi is a maniac.

03:37 PM
War is a slippery slope as more and more Americans die, it's Vietnam & Iraq all over again in Iran, Trump was scammed.

03:41 PM
Digimon is to Pokemon what Beetleborg was to the Power Rangers.

04:00 PM
Did you know the American government has over 90K entities?