01:00 AM
MPH Protocol
The independent speed MPH Protocol regulates Bill's speed in any zone, mode, run, pass, level round, world, or whatever. MPH must be designed so Bill can go any speed at any time. But at the same, there must be default routes where MPH goes from fastest to slowest. Gemini usually says the top speed should be 25 MPH which is 25 MB/s. My disc drive is labeled as 16 MB/s but 25 MPH might push Bill over bad spots during earlier rounds. Sometimes, Gemini says 100 MPH might also help. I don't know what to believe because Gemini is often wrong about everything. I don't know how much MPH affects Bill as it often seems Bill goes at whatever speed Bill wants to go. Also, sometimes my drive might be being throttled by cops and stuff. If possible, I would love for Bill to match the MPH to whatever speeds the drive went in the previous rounds. But then again, I don't know if that is a good idea. I think for most flags, including the MPH -a flag, the 80/20 rule apply, generally speaking. The 80/20 rule is twofold. First, stick with the highest settings possible during the first hour of rescuing a disc. Second, to focus on what works the best 80% of the time. A perfect disc can be copied in under 5 minutes, that's around 17.07 MB/s. Other discs, under an hour which is roughly 10x slower. Assume that almost 20 MB/s is the gold standard. My drive is capped at 16 MB/s tho. If copied in an hour, that might be roughly 1.4222 MB/s. 20 MPH is the best. Anything above 2 MPH is good. The MPH Protocol must push Bill to max speeds, especially for the first 80% or more. Eventually and/or as things continue to slow down for many minutes and/or many rounds, especially rounds under 2 MPH, the MPH Protocol might sometimes experiment or try different tactics. For example, the first tactic is the highest MPH possible. Another tactic might be lower MPH. Another might be an average which might be around 10 MPH. Another might be to match whatever speed the drive is going in an attempt to finish the current pass through all bytes. It may or may not be best to raise and lower MPH. Sometimes it feels like MPH might have little power as you get closer and closer to 100% rescued. Therefore, it might be best to keep MPH at max until 99% rescued or until it seems max MPH is doing more harm than good which still might be very hard to determine if MPH is being too counterproductive or not. Build me a template with enough MPH speed options from max speeds to the lowest speeds which even include -a 0 as the lowest speed that I know about right now.

Cluster Protocol
The independent Cluster Protocol must push Bill to focus on the largest cluster sizes possible at first and/or whenever it might help. I recommend including a 128K, 64K, 32K, 16K, 8K, 4K, 2K, 1K, 512, 256, 128, 64, etc, down to -c 1. Must be independent. Must try to do the largest ones at first and whenever it is needed. Bill must know what is needed. Sometimes, higher sizes might not work. There must be a way to quickly see if a crazy high size might do something for a short time. But then eventually Bill needs to lower the volume as too high might be a waste of time sometimes. Especially during the first 80% rescued and/or for the easiest bytes, Bill is encouraged to try for max speeds, max clusters, etc. Perhaps the Housekeeping Protocol might help with keeping things clean. A lot of things can go wrong at any second. Bill might even think a crazy high cluster size is working but it might be just ghost data from cache, RAM, CPU, GPU, etc. So, Bill must be smart with finding the Goldilocks Settings for Clusters, MPH, Mario, etc. Especially for the first 80% or for the easiest bytes at least.

11:46 AM
Default Tiers
Bill must loop levels. Each level must have infinite levels. Bill must attempt multiple tactics to complete each pass. But a pass is a run or probe through all remaining non-rescued bytes. After a pass, it should say 0 untried bytes during the Scan Modes. Bill must try very hard to complete full passes via Mario, MPH, and different tactics when possible. Bill must hop over scratches. Bill must try to run all over the disc during passes. Eventually after trying everything for a long time, the Stall Protocol might push Bill to other levels, etc. Bill must loop in worlds too. The hierarchical tiers goes rounds, levels, worlds, modes inside the Scan Loop or some of the tiers can be added or deleted or altered depending on what is needed. But Bill should not switch to Trim until trying many different levels, worlds, rounds, Scan Modes, etc. Bill should first try everything to finish each pass. Each level represents a pass. But each level should be unique. Bill must try different things. Bill must by default loop forever until it is time to switch.

Timeouts to Risk Ratio
The default must be the higher the risk, then the smaller the timeout. Speed might minimize risk normally. The larger the cluster size, the higher the probability of risk which means timeouts should probability be minimized at first until it is proven that it is working. But generally speaking, timeouts are supposed to help protect Bill from risks. Some things might increase the odds of risk. Like running into scratches and bad spots. Increasing jump sizes might decrease the probability of risk for example. Timeouts can help extend rounds which is sometimes good if it is working but dangerous when it is not working as well.

Direct Protocol
The independent Direct Protocol must sometimes use the -d --idirect related flags to help Bill when Bill really needs it the most. The Stall Protocol, for example, could trigger the Direct Protocol. I was able to rescue almost 80% of a disc in about an hour without -d which means -d is not always needed. Bill must try -d out. Bill can turn -d on and off at any time when other tactics are not working. If -d improves performance (The Goldilocks Rescue Protocol), then -d could continue to be used when it is needed the most. Not just the -d flag but also -R and -O and maybe even Error related flags and maybe even -J. Tho -J might be less likely to work. But Bill can try different flags to see if they improve performances when Bill is struggling. Especially when below 2 MB/s before 80% rescued. After 80% rescued, it might be more normal for speeds to drop under 1 MB/s and that might not be the worse thing. But Bill can still decide to try things out when needed and to use whatever works the best. The Direct Protocol must be independent of other tiers. Bill can use the Direct Protocol whenever Bill needs it the most.

08:06 PM
Dear Gemini
Gemini wrote, "To fix this so Bill actually listens..." But I didn't say Bill doesn't listen. I said Gemini doesn't listen. I said Timeout should begin small and gradually get bigger. Gemini translated the word "GRADUAL" to mean two things. First, a one second timeout. Second, a one hour timeout. That is NOT gradual. But that is what Gemini did. That is proof of how bad Gemini is. This is being posted on my blog.

List of some of the problems:

1. Bill failed to decrease Clusters Size (-c 131072) after that first round. If Clusters are too high, turn it down to -c 64K the next round. After that, 32K. And then 16K. Find the Goldilocks Settings. Gemini used to say 2K was the ceiling for cluster. Then Gemini said 4K. And then 16K. Therefore, 131K is probably not going to work. Anything above 16K should only be tried one time per session. 8K might work a little sometimes. Usually, Bill does better when clusters are below 2K.
2. Bill might be stuck on a scratch.
3. Bill decreased jump sizes but it is better to increase to hop over bad areas. You decrease after rescuing a lot of bytes. When you struggle, then you increase jump sizes.
4. Bill failed to activate -d and/or any flag that might help.
5. Bill did not really return to normal rounds. It looks like Bill was stuck in Oatmeal Rounds and was unable to escape it.

11:40 PM
Gemini is bad at writing code.
Here are some of the many problems:

1. It went from -c 131072 clusters size by 50% per round (which is good) but then looped back to 131K for no reason. If 131K produced 50 MB/s, that would be a great reason.
2. It always seems to say "TARGET: 0x110008000" or at least lately which might be a scratch, a loop, if it is not able to complete a pass.
3. It says -a 100K and it also sometimes says -a 75K.
4. It says -d every single time which means it is not even trying. It should turn -d on and off to see what works. It did not work with -d. Bill should have turned it off realizing it did not work with -d. If Bill was still stalling, then Bill could have turned it back on. Same thing with any flag, really.
5. You are missing the cpass flags which I want for many levels or at least until all the easier bytes are gone. I prefer cpass until 99%.
6. Jump sizes should increase if stalled.
7. Why not try Error flags sometimes?
8. Why not try many different flags when stalling?

12:48 AM
Dear Gemini
I thought that 8192 clusters would make the round fail so that Bill can move on to smaller clusters. It is amazing how the high cluster size is not crashing the round. It make me wonder what would happen if it was 16K clusters. A few hours ago, Gemini said 2K was the max. And then it said 4k. And then Gemini said 8K. Will Gemini someday say 16K? Compare them again but now within the context of a 0% rescued DVD disc that will do a first full-pass round at the highest cluster size ever and highest speed ever but also within the context that Bill will then clear the mapfile and do another round but with smaller cluster sizes for example as to fill in the holes created from the previous rounds. The goal of higher speeds and clusters would be a faster round. But it is a question of what might save total time. You mentioned overhead time for time spend with Bill switching between rounds, modes, levels, etc. It is a question of at what point does a top speed top cluster Demon Run become more counterproductive in the long run.

Reverse Protocol
The Reverse Protocol must push Bill towards backwards -R reverse reading in secondary modes after attempting Forward-Only modes. Bill must at least try several methods via different levels per mode before switching to -R. Forward-Only Scan Modes might rescue 70% to 100% of all bytes even without -R sometimes which is why -R should generally be reserved for secondary approaches after forward-approaches. Include -R as a backup approach to be used in combination with different flags. By default, -R is already included in Trim. But -R could perhaps be included in Scrape, Crawl, etc. In Scan, it is critical that -R is used sometimes but not all the time, -R should be tried after other things are tried during the Scan loops.

Direct Protocol
Similar to the Reverse Protocol, the -d --idirect Direct flags should be used secondary as needed or when needed. Many discs can be rescued to 80% to 100% even without -d in many cases. Like with -R, the -d flags should be reserved as a backup plan when other options continue to stall and fail for too long.

Scan Protocol
The Scan Protocol should push Bill towards 80% to 100% rescued in the first round of new or returning DVD or CD (whether 0% or 99% rescued already), there should be multiple Scan modes, worlds, levels, rounds, phases, stages, jobs, flavors, flags, degrees, etc. First, Scan must attempt the highest settings first to capture (rescue) easiest spots (bytes) first before lowering the volume down gradually. Second, Scan must try different combinations of flags via different levels, etc. Scan must even resort to crazy combinations of flags like -a 0 combined with larger cluster sizes or perhaps the inverse of -c 1 with like -a 100M or other crazy ideas. Scan must loop through modes, levels, etc. Bill should generally not resort to Trim and other Post-Scan modes until exhausting all Scan options several times. Bill should at least loop through all of the scan levels a few times and stall for a long time before switching to Trim, Scrape, etc. Bill should generally loop in Scan modes until 99% or until all Scan options are failing many times consecutively again and again stalling with no progress for a long time. Scan can sometimes include -d and even -R as a last resort when other options continue to stall and fail many times.

Switch Protocol
The Switch Protocol must push Bill to do the Switch Round at the start of each session or run (pass). Run is defined as to perform a full Forward-Only pass through all remaining non-rescued untried bytes that were not yet already rescued. The Switch Round must attempt to reset the map to retry tried bytes which might sometimes include bytes that were already formally tried, trimmed, scraped, and even bad sectors. Whether Bill is reading a brand new 0% rescued disc or a returning 99% rescued disc, Bill should first attempt this Switch Round that attempts to clear the map to retry tried bytes and then the Switch Round must try to quickly attack those remaining bytes via the highest settings possible. After that quick Switch Round, then Bill can decide what to do. This Switch Protocol is mostly helpful for the Scan modes but might sometimes also help with Trim, Scrape, etc. But remember that Bill should try to remain in a Scan loop to try different Scan modes for as long as possible before resorting to Trim, Scrape, etc. The Switch Protocol should activate at the beginning of each session and at the end of each run. Remember that a run is when all non-rescued bytes were passed through. A run is a full pass through all remaining bytes. Bill can try different methods to pass through remaining bytes. But after all the bytes are tried, then the Switch Protocol must activate so Bill can try again via different methods. Bill must be thorough at trying all bytes. After trying all bytes, restart or reset via this Switch Protocol. This Switch must activate the Switch Round that attempts to re-mark tried bytes to be untried and Switch must attempt a quick scan or run through untried bytes via one fast round. After that, Bill must continue via different methods. Jordan can help when needed.

Switch Round
The Switch Round must try to rescue all remaining bytes in record times via the fastest speeds, biggest cluster sizes, etc. The Switch Round should extend if it is the fastest option. The Five-Minute Blitz idea you mentioned is dangerous if Bill is rescuing 20 MB/s say for example. As long as the Switch Round is the fastest option to rescuing all the bytes, Switch could continue. If Bill is not going super slow or stalling for a long time, the Switch Round could perhaps continue. Bill can loop through Scan modes, levels. The Switch Round can be the first round that Bill runs per disc. But the Switch Round can also be run at the beginning of each session or run. Timeout flags and other flags might be able to help Bill to end the Switch Round. Switch must try to rescue all bytes in under five consecutive minutes total. A Switch Round could perhaps be extended if it can actually rescue all bytes in under five hours. It is critical Bill does not end the Switch Round too early or too late. If a lot of progress is being made, Switch can run a little longer. But eventually, Bill should probably end Switch and rotate through different modes, levels, flags, speeds, clusters, settings, options, tactics, stages, rounds, methods, etc. Switch Round should probably use the fastest speeds and biggest clusters to mirror what I did a few days ago with capturing almost 80% in like an hour. The idea for Switch has two parts. First, to re-mark bytes to untried. Second, to quickly probe the untried. I'm a little bit hesitant to suggest divorcing these two parts of Switch to run them separately, that is why I generally prefer the two parts of Switch stay married together if possible. The second part of Switch attempts to quickly rescue the untried again. But if Switch ends, Bill must continue rescuing the untried via other Scan methods if possible until the Untried drops to 0. After that, Bill probably should activate Switch to restart the process all over again, assuming that is the best option.

Last Resort Policy
The purpose of flags like -e would be to help run through the untried assuming Bill is unable to simply probe the untried after five hours. Correct me if I'm wrong but there might be many ways to push Bill to probe the untried via different methods per run. It seems that flags like -O and other flags might be better as a last resort. It seems Bill has many options to rescue 80% to 100% before resorting to tougher tactics normally. That is why I recommend tougher flags be reserved after other options stall for ten full runs. There are many flags out there which might sometimes include maybe -d and -R and many other flags, some flags might be needed sometimes, some flags should be reserved for after other methods results in prolong stalling or when it seems Bill is only rescuing like 1 byte per hour or a very slow speed, assuming Bill tries all other options, assuming options are not boosting speeds enough, then resort to tougher options. Remember the Refresh and Housekeeping protocols we talked about for weeks.

Scan Loops
By default, Bill should loop through the Scan Loops before switching to Trim, Scrape, Crawl, Merge, Fill, etc. Within the first Scan Loop are the Scan Modes. Inside each Scan Mode are worlds. Each world houses level. Inside each level can be infinite rounds. In a sense, Bill could loop within rounds, levels, worlds, but also modes. Once Bill runs through all of the Scan Modes one time, then that completes the first Scan Loop. If Bill retries the Scan Loop, Bill should begin again afresh at Mode 0: World 0: Level 0: Round 0 but perhaps with the -d --idirect and possibly other flags too like -R, -O, etc. I prefer -d for Scan Loop 2 by default. Perhaps, Bill will feel the urge to activate -d before Scan Loop 2. Each Scan Loop can be different. Bill can activate -d before Scan Loop 2 but -d and other flags should generally be reserved until Scan Loop 2 or Scan Loop 3, etc. Bill needs to be smart enough to activate any flag when needed. But by default, Bill should first be hesitant to avoid bringing some flags out too early or too often or too much. Jordan is supposed to check the Map, Dmesg, etc, between each round, in order to help Bill decide when to bust out tougher flags and settings. Trim can also have a loop if need be. But the focus is on the Scan Loop because many discs might hit 99% rescued while in the Scan Loop. Trim, Scrape, etc, might only come out after 99% for many discs.

Switch Round
The run_switch_round should activate per session and run. To be clear, Switch Rounds must not be triggered each Scan Loop. Please don't conflate between these things. Bill must probe through an entire run (pass) per round potentially. But flags/settings/Bill might stop rounds. Bill must continue trying to run through all bytes. When Bill runs out of bytes to probe, then Bill must active the Switch Round to re-mark all remaining non-rescued bytes. Bill can also re-mark at the start of each session too.

Output
Give me block codes to fix the following problems. First, lasers must rest for ten minutes after Bill is running for one hour. But Lasers-Clock start when an active current live Bill-Session is started in the Terminal but then the Lasers-Clock must end when Bill is terminated in the Terminal too. Second, it said, "3751919616 bytes (80.25%)" rescued. But it previously said "3G (3873245184 bytes) (82.85%)" rescued. Third, output also said, "/home/a/dvd_recovery.sh: line 36: run_switch_round: command not found." Study files and output. Bill should activate Loop 0: Mode 0: World 0: Level 0: Round 0 when a Bill-Session is initiated in the Terminal, and/or that first round may or may not be the same thing as the Switch Round. The current version of Bill made the Switch Round a separate entity it would seem which is okay as long as it rescued 100% of all the bytes of all discs, what matters are the end-results. I prefer if the very first round 0 and/or the Switch Mode be the very fastest with the highest settings which may contain the highest clusters and the highest speeds might be 25M and/or I've debated with Gemini for months about what the highest speeds might be. But last few days, Gemini was saying 25M might be the best option. By default, Bill slides from higher to lower settings. Bill can pick which levels to play. One idea for different levels might be different jump/skip/hop/leapfrog/teleporting sizes. By default, Bill should play level 0 at the beginning of a session after the Switch Round and/or the Switch Round is level 0. Loop 1 (the second loop of the Scan Loop) may want to consider the error flags and many other flags if they have not been used in the first loop.

Jump Protocol
Big to Small. Generally, Bill prefers fast to slow. Bigger jumping might minimize slow. Gradually, Bill can jump smaller and smaller. But at first, Bill is trying not to slow down. Jump means hop, leapfrog, teleport, skip, jump forward.

Gambit Protocol
Big to Small. Bill wants to maximize his gambit each session and run. When a session starts, Bill wants to play at the highest level so to speak, the fast speeds, the biggest clusters, the biggest baddest settings. Bill is playing chess and poker. In general, Bill wants to play the strongest move that might win Bill the game. A run is a full pass through all non-rescued bytes. Over time, Bill lowers the volume to the settings, the flags, and even the Jump Protocol. Bill transitions from the Telescope to the Microscope. But Bill by default wants to put troops on all the continents like it's the Risk board game. The opening gambit per session and run attempts to win all the remaining bytes in seconds. But perhaps timeout flags and/or different settings and protocols might bail Bill if the Gambit isn't rescuing all the bytes. In theory, the Gambit (also called the Switch Round) could last seconds or even hours. If it's the best move, Bill should stay. If not, Bill should go. That goes for any round or anything Bill is doing at any time. If what Bill is doing is the best thing, Bill should do that forever. If not, Bill should stop and do something else. If Bill needs to stop every five seconds, that might be good. If Bill is making amazing progress doing something, then maybe Bill should do that for hours and hours. As long as Bill tries to do the best things from big to small that has the highest probability of winning and rescuing all the bytes. Bill must activate the Housekeeping Protocol sometimes.

12:35 AM
Tracy Morgan sure aint no Adam Sandler. Tracy is interesting but not like a super star it would seem. I find him to be like an over the top stereotype character.