10:09 AM
Dear Gemini
Give me block codes for this Bill script. Bill must revert back to working modes when stalled. In the output, Bill ran for hours unable to revert. Bill must focus on Scan Modes. In order to do Trim and Scrape for example, Bill must begin a full pass in the Scan Mode. Bill might want to modify or delete cpass related flags. Bill must turn on and off flags like -n -N for example. There are several options for Cpass flags. Only use flags that work on Gnome Ddrescue 1.27. --trim is not recognized in my version for example. Bill must decide which mode to do. But Bill must use complex math to determine which mode to do. Bill must start with independent Mario flags. Max Mario flags. Per pass, Mario decreases. But per stall, Mario increases.

Flags Protocol
Flags must react per round and pass and mode. Some flags (like Mario, Sonic, Tetris, Timeout, etc) should start big and decrease per pass. But per stall round, at least some (or maybe all) flags should increase. The general rule is to decrease flag volume per pass and to decrease flag volume per stall; but some exception might apply depending on a number of factors. Flags like -d and -O and maybe a few others should generally be off for the first few passes and first few stalls or wait until after 90% rescued or as Bill is below -a 200 KB/s for a long time. Many flags might want to follow similar or identical templates. This Bill script has three branches of governance like America, Bill has the tiers, protocols, and this pass system personified through this Flags System. I mentioned 3 things. First, the tiers which can serve as a default template route of rounds, levels, worlds, phases, modes (five-tier system) representing a way to shuffle through different combinations and volumes of flags. Second, the various protocols personifies decentralized independent systems that can override tiers. Third, as mentioned in this Flags Protocol, Bill should be Pass-Oriented at least to a degree. I am trying to expand Bill with these protocols to make Bill smarter.

Flags Map
The following is a general outline from high to low. For example, the first is the Sonic MPH Speed Flag set at a Super Max limit of -a 50000M which is more hypothetical or there for getting out of a jam to reset the system. The next highest is -a 25M designed to push Bill to attempt a quick pass over all the bytes and scratches. The next highest is -a 10M. The base is -a 1M. The other flags follow a similar template from high to low. In general these flags should start off as high as possible during the first pass. But perhaps the Timeout flag should be set relative to the Tetris Cluster. The higher Tetris is, the lower Timeout should be. In general, flags should start high but could decrease per pass but then also increase per stall. In general, Bill could be more relaxed during the first 80% rescued if -a 5M is flowing for ten consecutive minutes. I've included a Toolbox of flags below of example of flags that could be turned on and off as needed. The flags are independent of tiers, protocols, passes, but these flags can also work in concert with each other to coordinate the best strategy to rescue all the bytes. Bill must decide what to do per pass and sometimes per round even. After a pass, Bill can do another general Scan pass or try Post-Scan Modes like Trim, Scrape, Chaos, Crawl. To enter Trim for example, just enter a new full scan pass but without the -N --no-trim flag or without the -n --no-scrape flag for Scrape. The Flags Map Template as follows:

Sonic: -a 10M to -a 0; base: -a 1M; High: -a 25M; Super Max: -a 50000M
Mario: -K 100Gi to -K 0; base: -K 2Gi; Super Max: -K 100Gi
Tetris: -c 131072 to -c 1; base: -c 2048; Super Max: -c 10000000
Timeout: -T 120s to -T 1s; base: -T 30s; Super Max: -T 1200s
Toolbox: -d -O -n -N -r0 --cpass=1 --no-trim --no-scrape -b 2048

Mario Protocol
Mario's initial strategy: -K flags for the first rescued 80% of a disc (or first few passes or minutes to hours or after stalling a long time) before trying skip-size flags like --skip-size=1M,50M because skip size probing might slow Bill down. Perhaps Bill could adapt gradually. Mario could eventually use both -K and --skip-size at the same time.

Pass Protocol
On top of the Flags Protocols and other protocols is this Pass Protocol. The goal is to try to by default attempt the first pass with high settings. If Bill struggles to complete a pass, Bill should jump more and more to rush to the end of the map sooner as a way to give up when Bill is failing to rescue enough while losing too much speed. Remember the 3 branches of the Bill government. Section 5 should at least hold a general outline of the 5 tier system of rounds, levels, worlds, phases, modes. Section 4 can include the focus on a pass system might perhaps override tiers mentioned in section 5. Bill should generally be focused on Scan Mode as opposed to the other 4 modes of Trim, Scrape, Chaos, Crawl. Section 5 could offer default tier routes. Also, the many protocols may even attempt to influence Bill those default tier routes. But perhaps the main captain of the ship is Jack. I created a Jack Protocol, we could merge that with the Pass Protocol as they are almost the same thing. The Pass System focuses on the best passes that might rescue all the bytes. These passes may not always align with tiers or protocols. Section 4 might mention the Pass System. Section 5 might mention all 5 modes. Eventually, later passes should attempt to pass through Trim, Scrape, Chaos, Crawl.

Pass v Tiers Dynamics
Bill must start with Pass-01. A pass is a read (probe) run through all remaining non-rescued bytes. The first pass must attempt maximum settings. When Bill struggles, Mario must jump farther per stall. But per pass, settings must decrease. Not all settings have to change per pass. If Mario jumps -K 4Gi in Pass-01, then jump -K 2Gi in Pass-02. Flags should be dynamic. Only change settings when stalled. Stalled means not producing at least 1 MB/s. Bill doesn't have to change settings if rescuing at least 1 MB/s. When stalled, perhaps increase some of all of the settings. After each pass, decrease settings. Protocols should be independent of other systems. Protocols include Mario, Sonic, Tetris, Timeout, Direct, -O, and more. I've included a sample template starting point for Pass-01 below as to where to begin. A Pass is a simple version of the Tier-System that has the five tiers of rounds, levels, worlds, phases, modes. I'm still in the middle of designing the 3 branches of Bill, there might be overlap. There might be things missing. Bill needs to turn flags on and off as needed, that includes even -d --idirect, -r0 --cpass=1, -R, and -O for example. By default, the higher the Tetris Clusters, the lower the Timeout. I suggest -a 1M Sonic for the speed for the 131K Tetris Clusters but increased Sonic speeds if lowered Tetris for example. Like with the tiers, there could be in theory infinite Passes:

Pass-01
-b 2048 -a 1M -c 131072 -T 1s -K 4Gi --skip-size=500Mi,2Gi -r0 --cpass=1 -n -N --no-trim --no-scrape

3-Branch Bill Government

1. Jack: Executive: Pass-System
2. Bob: Judicial: Tier-System
3. Rick: Legislative: Protocol-System

Bill must not be fixed. Bill must not be static. Bill must be dynamic with the passes, tiers, protocols, flags, settings, variables, options, numbers, sizes, tactics. For example, Bill must use complex math within the 3 branches of the Bill government. For example, if Bill is using -a 10M, one math formula would be 10M/2=5M. Half of 10M is 5M, and that formula could tell Bill how much to decrease by. I'm not saying Bill has to move only in a fixed amount per pass, tier, round, protocol. I'm saying it depends per protocol, tier, pass, variable, situation. In theory, the second pass could be identical to the first pass if the speeds are the same. For the first pass, Bill can attempt the highest settings. For the second pass, Bill could keep the settings the same for one round. After that, Bill should alter settings if stalling or struggling. In general, Bill can decrease settings per pass. But it shouldn't be automatic. Bill should try to keep the settings fixed during a run/pass through all remaining bytes. After that run, Bill attempts to pass through the remaining bytes again via the same settings. But if Bill drops from 10M to 5M on average in pass 2 say for example, Bill should alter settings to react to that. In general, if stalling or struggling, perhaps Bill should increase settings and/or edit settings to counter. After 85%, Bill should react every round to actively edit passes even during passes. As Bill gets closer and closer to 100% rescued (like 85% for my current DVD), then the faster and more often Bill should react via Jack, Bob, Rick, Mario, Sonic, Tetris, Timeout, Direct, -O, -R, etc.

The Law of Halving: If a protocol requires a reduction, Rick uses New = Current / 2.
The Inverse Ratio: Rick mandates that as Tetris (Cluster) drops, Timeout must rise.
The Mario Mandate: Rick dictates that if Sonic (Speed) is high, Mario (Jump) must also be high to avoid grinding.

The "Status Quo" Ruling: If $MPH \ge 1MB/s$, Bob rules that the current settings are constitutional and prohibits changes.The "Struggle" Ruling: If $MPH < 1MB/s$, Bob declares a State of Emergency (Stall). He authorizes Jack to change flags mid-pass.The "Red Zone" Declaration: Once $PROGRESS \ge 85%$, Bob suspends the "fixed pass" rule and orders constant, round-by-round flag re-negotiation.

1. Jordan is probably better than Jack in some ways.
2. Ghosts: bring them back, you were the one who deleted them.
3. Bill must reset the map each time until 80% rescued. After that, Bill could skip trying bad sectors for the next 20 passes after 80% rescued.
4. Direct: yes, fix this to do that.
5. Each section should be separate sections and not combined. But sections can be written to work with other sections. Logic should work together across all sections. But each section should be unique when possible.

Escalation Protocol
Jack must escalate according to the following Five-Factors: passes, progress, time, rounds, retries. Escalate means to edit settings, flags, speeds, numbers, options, variables, tactics, modes, decisions, choices, codes, hacks, etc. For example, Tetris can escalate from -c 128 to -c 1. Mario can escalate down to smaller jumps from -K 100Gi to -K 0. Sonic can escalate from -a 100M to -a 0. Timeouts might escalate up or down. Escalation can change the volume up or down. To escalate is to change the settings in any variety of combinations to add, remove, and edit any and all of the flags and everything that might be available which may include all of the many protocols, routes, tiers, systems, etc. 1. Passes: Jack must escalate based on how many total passes. A pass is a run, a read, a probe, through all remaining non-rescued bytes on a disc. Bill should run the first pass using the highest settings possible. As long as Bill is rescuing at least 1 MB/s, Bill could continue running each pass the same. But during the second pass, as soon as rescuing speeds drop below 1 MB/s, that is as Bill struggles or stalls, that is when Bill should escalate via this Escalation Protocol. If Bill is struggling in pass 2, Bill must adjust accordingly. 2. Progress: Bill must escalate based on progress. If under 80% rescued (low progress), Bill must escalate if under 1 MB/s. Bill should generally only escalate per pass if under 80% rescued, as long as Bill is generally above 1 MB/s. If Bill is over 80% rescued, Bill can escalate if under 1 MB/s and per round instead of per pass. In former Bill scripts, a level represented a pass. So, the pass system is simply a more simple version of the five-tiers of rounds, levels, worlds, phases, modes. Bill can still have tiers but Bill can also be pass focused too as to defy the default routes of tiers. But I do like tiers too. The concept of a more simple pass system was to turn the tier system into a more dynamic system that was not too rigid. But tiers is a good template or backup plan for when the pass system is not working. If under 80% rescued, Bill should generally only focused on tactics like increasing Mario Jumping to simply finish the pass faster to get to pass 2 faster while avoiding speed drops, struggling, stalling. 3. Time: Bill can increase escalation each hour in general on top of the other factors. 4. Rounds: Bill can escalate per round but this is mostly relevant if Bill is already above 80% rescued or if struggling through thousands of rounds at only 5% rescued for example. 5. Retries: Bill can escalate per retry. To be clear, a pass is like a retry when Bill reads same bytes again during an additional round. Sometimes, a pass might scan/run/probe/read through new bytes during extra passes. This Retry Factor should mostly be relevant after 80% is already rescued. As Bill gets closer to 100% rescued and/or any of the five factors mentioned above in general depending on situations, Bill must escalate based on said factors, Bill should generally be as patient as possible when possible as long as Bill is rescuing above -a 1M but Bill always prefers maximum speeds and Bill must increase and accelerate escalation potentially even at an exponential rate using complex math and everything else as Bill gets closer and closer to 100% rescue and/or the other factors too. Make sure Bill can do what must be done according to the factors. Bill should remain at top speeds for multiple passes for as long as bytes are being rescued at a minimum of 50% of the max speeds of the previous pass. The only change per pass should be Mario. Make sure Mario jumps a little less per pass. But if speeds drops to below 50% of the top speeds of the last full pass, then Bill should escalate. Make sure Bill can alter the settings up and down as needed from high to low. But Bill is focused on speeds. Bill must be patient. Bill begins to escalate more based on the Five-Factors we mentioned earlier. Bill starts at max settings, top speeds. Bill can gradually decrease settings as Bill struggles to rescue bytes gradually per pass or round. As long as bytes are being rescued, Bill should not do anything except run the passes until the well starts to dry out. If Bill is about to re-mark bytes, like after a pass through all remaining bytes, Bill could attempt to Trim first. The logic follows that if Bill can Trim at 50% the speed of the previous pass, Bill can continue to Trim. Each round, Bill can check speeds. As long as Trim is at least 50%, then continue. If not, return to another Scan-Only Pass. In general, Bill should not attempt to Trim until 80% rescued, after five hours of running, or if the last pass was stuck below 100 KB/s. Basically, this can be merged perhaps maybe to the Five-Factors I mentioned for the Escalation Protocol, these are basic suggestions, templates, outlines, as it relates to how Bill can decide when to try Post-Scan Modes (I mean Post Scan-Only Passes) like Trim, Scrape, Chaos, Crawl. The general idea is Trim is generally slower than Scan. That is why Bill shouldn't be in a rush, a hurry, to attempt to waste time Trimming until the Five-Factors demand it down the road after many things in Scan are tried many times via Escalation.

Sonic: -a 10M to -a 0; base: -a 1M; High: -a 25M; Super Max: -a 50000M
Mario: -K 100Gi to -K 0; base: -K 2Gi; Super Max: -K 100Gi
Tetris: -c 131072 to -c 1; base: -c 2048; Super Max: -c 10000000
Timeout: -T 120s to -T 1s; base: -T 30s; Super Max: -T 1200s
Toolbox: -d -O -n -N -r0 --cpass=1 --no-trim --no-scrape -b 2048

11:45 PM
Dear Gemini
Did my Ubuntu updates. Restarted my laptop. I fixed my mouse and TV problems. Now, study Bill and list each section that may have caused these issues with my mouse and TV. Probably the USB related codes probably turned off my mouse. My mouse is back now. But the TV is connected by HDMI, I am not sure what triggered the TV. One of the issues was my RAM went up to around 29 GB and around 10 GB swap because I had many web browser windows and tabs opened and other things. I only have around 30 GB RAM. The RAM may have spiked close to the limit. The CPU and GPU may have spiked. Right now, my RAM is down to 4 GB.

Twitter Tweets
01:25 PM

Trump did good at times but remember that evil is always trying to hijack good every single step of the way.

12:30 PM
Bipolar Protocol
The Bipolar Protocol pushes Bill to try extreme opposites when stalling towards 100% rescued. Escalation Ladder. Try different things. Push the other protocols to try harder and harder per stall. The closer Bill gets to 100%, the more Bipolar Bill becomes. Experiment. Focus on what works. Hop around between any and all of the rounds, levels, worlds, phases, modes, Scan, Trim, Scrape, Crawl, flags, protocols, settings, tactics, -R reverse, and more. If something works, try it again. Especially after 85$ rescued because that is closer to 100% rescued. Escalate Bill sometimes through anything and everything. Try different combinations as Bill stalls more and more. Become more and more Bipolar as Bill stalls more and more. For example, Bill could try -a 100M and then -a 0 because those are two opposite settings. Bill can go back and forth between different various high and low settings. Bill might want to sometimes leave the Scan Mode and try Trim and other things to see if that might help. It is normally better to try to only Scan until 99% rescued. However, sometimes, it might be good to try to Trim every once in a while and especially after like 85% rescued or after stalling trying everything else. Bill needs to try harder and harder trying different things within Scan Mode and also sometimes within other modes too like Trim, Scrape, Crawl, Chaos, etc. After 85% rescued, if after ten consecutive stalls, if Bill can rescue more bytes at a faster speed via any mode outside of Scan, like maybe Trim, then Bill should try that for a pass or for as long as it seems Bill can do better in Post-Scan Modes. Make sure Bill can try more variety for his tool box of flag settings from 0 to even above 100% of what is possible regarding all the flags and combination of settings in Scan or any mode as Bill continues to stall consecutively as Bill gets closer towards 100% rescued or as Bill continues to remain under 2M speed. Bill should not escalate even at 99% rescued if Bill remains at above 2M speed. Escalate especially after 85% and especially if averaging below 2M speed in the last ten minutes or ten consecutive stalls.

02:12 PM
The Oatmeal Protocol was one of many protocols. I wrote many dozens protocols for years. Some protocols may or may not overlap with other protocols. Some protocols may or may not combine or be discontinued. I talked to Gemini about thousands of these Bill scripts for years. Gemini cannot remember all the thousands of conversations. Gemini has amnesia. That makes Gemini unable to help me. I do not know if Oatmeal can still work or not work or how Oatmeal might work best with Bill with all the many protocols.

05:20 PM
Before, I made levels named Sonic. But I discontinued the Sonic levels. Technically, Sonic levels can stay but protocols can override them if need be. There are 5 tiers in Bill: rounds, levels, worlds, phases, modes. Sonic was created to be the first three or more levels of world 0. Technically, all the levels could be named Sonic or none of them need the name. The idea was Sonic levels were supposed to focus on trying to rescue the bytes 100% in record times. For example, perhaps the first level could rescue 80% and level 2 the remaining 20%. But sometimes, it is not that easy to do that. I like my five tier system. But I also like protocols having the power to override tier defaults. I also renamed the MPH Protocol the Sonic Protocol. It might be confusing that I had both levels and a protocol both named Sonic. They're both similar and different at the same time. To be clear, the Sonic Protocol is the -a flag speed protocol that attempts to push Bill to max speeds like -a 100M for skim reading over scratches or -a 0 for slowing down. Sonic was designed to attempt to override any tier at any time for any reason according to what Bill needs at any time. It is critical that Sonic can use any -a flag from -a 0 to -a 100M in an attempt to regulate speed for any and all rounds of any and all tiers as needed. Sonic must be able to react between each round. It is critical that Sonic is aware of what works and does not work. Sometimes the -a flags might work a lot or not at all depending on many factors.

5m 5h 5G 500k 5M Jack Five Protocol
5m 5h 5G 500k Jack Protocol is the heartbeat of Bill. We will nickname this protocol as the Jack Five Protocol or Jack for short. Jack pushes Bill. Jack is the clock. Jack is the calendar. Jack is the heartbeat. Jack is the map. In Jack's name are five numbers representing two high numbers and three low numbers. The first set of numbers are 5m and 5h. Jack tries to copy each 5 GB disc in under 5 minutes (5m). But Jack knows it might extend to 5 hours (5h) and beyond to even 5000h. Jack pushes for 5 GB/s or at least 20 MB/s. But Jack also knows Bill may be lucky to get above 500 KB/s (500k). Rescuing 5 GB in 5 hours would be 277.78 KB/s. But let's just say 500 KB/s because faster is always better. Jack wants Bill to always go above 5 MB/s (5M). As long as Bill is rescuing at 5 MB/s or higher each second, that is perfect. The disc drive is rated at 16 MB/s max. The current disc has been in at around 85% for hours. So it is a question of what might be best for this particular disc. Scan can work for many discs. But eventually, it might be hard. I think for this current disc and any disc, it is critical that Bill tries several passes before getting stuck on Trim and anything that might be Post-Scan Modes. For example, the purposes of the protocols and the four phases was to try several tactics through entire passes using different methods from faster methods to gradually slower methods per pass.

Jack Protocol
To expand upon the 5m 5h 5G 500k 5M Jack Five Protocol which may be similar to other protocols I've written these past four months or so, like the Jordan Protocol, the Coach Phil Jackson Protocol, possibly the Oatmeal Protocol, a bit of the Goldilocks Protocol, and more. Another number that can be added the Jack Protocol can be 85 and especially as it relates to when a disc is at least 85% rescued. A key attribute to Jack must be escalation, especially if after 85% rescued. I've talked about the value of protocols overriding default tier rounds when need be. There are many tier overriding protocols like Sonic, Mario, Tetris (clusters -c), Timeout, Direct, and more. These protocols are searching for Goldilocks. But to expand upon all of this, it is critical that Jack becomes gradually more reactive as Jack gets closer to 100% rescued and especially after like 80% or 85% rescued. The Stall Protocol must become less patient and especially after 85% if below -a 5M in speed. After 85% rescued, Jack should push Bill to rotate through all combinations of tactics per stall. Jack must rotate through tiers and protocols searching for Goldilocks and especially after like 85% rescued or gradually more and more as Bill gets closer and closer to 100% rescued. After trying everything via several passes, Bill must give up on Scan and move on to Trim, Scrape, Chaos, Crawl. Jack pressures Bill to try everything within the Scan Mode at a faster pace after 85% rescued. Jack must become more Bipolar via the Bipolar Protocol to really try everything and especially after 95% rescued. Try -d and then turn off -d and back on and then off. Jack should turn things on and off. Jack should turn the volume up and down for all the flags and settings. Turn -R on and off. Turn -O on and off. Try all the flags and numbers and especially after 85% if speeds are under -a 5M.

Error
If a L-EC Medium Error ends a round, can Bill then run dmesg -w and/or commands and/or do things to see is it L-EC Medium Errors and/or what is, like what is happening, can Bill then use the info to respond accordingly?

Pass Protocol
I want you to talk about different ways to do it. We talked about protocols and tiers. But right now, we are focusing on passes. Within tiers is Phases and each phase might be like a pass. So, there might be differences and similarities between passes and phases. There might also be similarities and differences between protocols and passes. I talked about passes many times when making Bill for months. So many different protocols. And some protocols may relate to passes. But talk specifically about passes. There are many questions, desires, concerns. One question would be about how often to do full passes or how full and how often. I prefer the first ten passes be the fastest ever. But eventually at least, it might be better to do not just a fast pass but a pass that might include Trim and Scrape. Perhaps even return for another pass even after Trim and Scrape. The tier system and even the protocols were attempting to be pass focus already. I prefer a gradual system that started with the fastest pass that might rescue all the bytes in under 5 minutes if it is a perfect DVD or CD. First pass at 5 minutes at best. Pass 2 at ten minutes at best. 3 pass, 20 minutes. 4th pass at an hour. 5th pass at 2 hours. 6th pass, 3 hours. 7th pass, 4 hours. 8th pass, 5 hours. Like each pass can get a little slower and longer. That could be the general idea.

The Pass vs. Protocol vs. Tier Relationship
Protocols (The "Brain"): This is the high-level logic (like your "Oatmeal Protocol"). It decides when the hardware is too hot and triggers a cooling cycle or a reset.
Tiers (The "Gearbox"): These are the specific ddrescue flag combinations (Sonic, Run, Crawl). They dictate how the laser behaves at any given moment.
Passes (The "Map"): This is the physical progress. One pass equals one attempt to visit every "?" (untried) sector on the map

Pass Protocol
Give me block codes. First pass should attempt max speeds, jumping, settings, flags, options, like a Mario Speed-Run through all the levels. Bill must try to speed race from the start of the map to the end without slowing down. Bill must be adaptable enough to find ways to speed up with Sonic and jump farther with Mario when needed. Bill must use Tetris to gobble up as many -c 1 to 131K clusters like a Pac-Man as is possible. Bill must use a Goldilocks balance for Timeouts and any and all flags really. But after that first 5-minute (or longer) speed run (via at least one round or multiple rounds), each additional pass must be extremely reactive before and during each and every pass. In order to determine when to Trim say for example, Bill must check the map, Dmesg, and whatever else Bill can. There must be math formulas for determining when it is statistically better to Trim, Scrape, etc. Tho, some of it might be debatable. But the theory is if there only a small number of bytes left, and if Trim was faster at rescuing them then Scan was, then Trim would then therefore be the better choice in that hypothetical situation. Bill must try to get the easiest bytes in the first byte. Second pass, try to get little bit more. Perhaps the second pass could be identical to the first pass. If the first pass rescues 1 GB, then the second pass better rescue at least 500 MB or something. Otherwise, that second pass was a waste of time. Perhaps the first pass should be retired. But then again, I don't know if repeating the first pass a second time would do a lot. I don't know what the statistics say about that. But whatever Bill ends up doing, Bill can do if it works. If not, then Bill should move on and try something else. Give me block codes. All flags, speeds, numbers, settings, variables, options, must be dynamic, not just -O, -d, -R, etc. For the most part, Bill should be speed oriented in that Bill attempts the fastest first pass. Bill reacts as needed with dynamic flags. As long as Bill is running at -a 5M or higher, Bill probably shouldn't do much. But Bill needs to be ready to try things when things are not working. But Bill should at the same time understand he needs to complete the first full pass without making too many decisions and reactions, assuming Bill can complete a first pass in under 5 minutes or under an hour, I mean as fast as possible. With each pass, Bill should become more and more reactive. Eventually, if Bill already did like a thousand full passes, Bill should be really reactive per round at that point. But early on, Bill not need to always respond and react per round during like a first pass. But using math formulas, Bill can determine if he needs to change the flags and settings for the next flag assuming things are not working. Study the data. Make sure flags are totally dynamic so Bill can decide what to do and when to do it and especially as Bill gets closer and closer to 100% gradually, make sure complex math is always used to make nuance subtle choices step by step with an emphasis on riding winning waves during the first 85% if it is an easy perfect clean DVD or CD that is easy to copy and/or it may slow down and that is when Bill needs to get smart quick as things start to slow down below -a 5M. One of the flags is --cpass=1 which could be dynamic as needed to be --cpass=1,2 or --cpass=3 and whatever the options are, maybe delete --cpass=1 whenever Bill should not use it. Remember to use -R but only when needed. Use -r only when it might really work. Make sure Bill can really turn on and off and up and down all flags as needed based on whatever Bill needs the most at any given time.