11:12 AM
Dear Gemini
The point of the five tiers was to keep Bill on a track. For months, I tried expanding the tiers and to try to keep Bill looping in Scan Modes and the tiers inside Scan before graduating to Post-Scan Modes. But then I started focusing on a Pass System. But to be clear, a Pass System is a simple version of the Tiers System. Since this script has been edited hundreds to thousands of times for months, this particular Bill file may have many holes within the three branches of the Bill government with the many things I begged you to add.

12:44 PM
Bill must loop within the Scan Mode. Bill should generally never try the other 4 modes until 99% rescued or depending on the Five-Factors I mentioned many times for years via my many long books I sent you thousands of times each day for years which you always ignore and forget. Many books of details you ignore each time. Bill must loop through the five modes. Bill must be able to exit modes at any time if needed. But generally, Bill should not do much until 99% rescued. But when Bill hits 0 untried, then Bill must do something. When Bill is stalling, Bill must do something. When Bill struggling and slowing down too much, Bill must do something. I wrote many books to you for years detailing how Bill must decide what to do each session, mode, round, level, pass, etc. Even if Bill was stuck in Crawl Mode, Bill is supposed to react per round. Bill is supposed to see that Bill is stuck in Crawl Mode or any mode. That is the point of the Escalation Protocol that I have been telling you about for years. I keep on writing books to you Gemini and you always ignore over 99% of what I write to you for years making you a million times worse than Grok and all the other AI engines in the world as you refuse to remember anything I say each day. -M -A should only happen during Super Escalation after several passes down the road or in rare situations when there are no other options.... as Bill gets closer to 100% and/or the five factors we talked about in general, then Bill should generally not only react per pass but eventually exponentially per round...... but it should generally be gradual where Bill becomes more and more reactive slowly over time..... generally, Bill can simply accelerate Mario to jump through a pass and then evaluate what kind of mode or pass or level to do at the end of a pass...... but if Bill already did many passes and tried many things already many times, then Bill then might want to escalate more often and eventually every single round after Bill begins to always remain too slow and struggling and stalling too often or all the time down the road after all options were tried and after many passes were already tried and many modes and flags were already tried with the settings turned up and down looking for Goldilocks.

Time Speed Stalls Passing Protocol
Bill must try to finish each pass. When Bill is under 100 KB/s, Bill must escalate Mario to jump ahead to the end of the pass faster. After one hour in a pass, BIll must begin escalating Mario. After ten consecutive stalls, Bill must escalate Mario. Perhaps there are other protocols that might help too that Bill can use. But Bill should start with Mario to complete a pass if slow or stalling too long or too much. We already talked about the Five Factors for the Escalation Protocol which is at the heart of this new rule. Technically, this new rule is an updated aspect of the Five Factors within the Escalation Protocol. Bill should rush through entire passes. Bill should generally try different things per pass and especially if Bill is under 100 KB/s. Based on the output below, it looks like Bill is not trying many different flags per round. Please see if Bill can choose flags per round or Bill might be broken. If Bill is making the best decisions per round as seen in the output below, then that is good. But there are so many flags like -R -O -d and many more. Also, it seems Mario is not changing per round. If Bill does not want to change Mario per round, I guess that is good if Bill is making good choices. Tetris looks the same per round. I see the Timeout changing per round. I do not care if each round is the same or not the same but I do care about Bill's ability to always make the best decisions per round to use the best flags and settings per round. Please study the output and the Bill script file code to see if Bill can totally make the best decisions all of the time. Also, the lasers turn on and off based on the noises I hear, the lasers turn on and off every like five seconds which seems to say the laser run into DVD scratches or whatever it might be and then stops.

Five-Things Protocol
To determine which flags to try per the Five-Things being each session, pass, level, situation, and round, in the spirit of the Five Factors within the Escalation Protocol and many other protocols, Bill should look at everything, look at those things, look at the Five Factors, like how many rounds, passes, stalls, percentages, retries, map files, Dmesg info, and whatever else, in determining when to escalate, when to increase and decrease settings, when to turn on and off any and all flags based on everything. Probably after 80% or based on complex nuance math, Bill should reacting with any and all variations of flags possibly everything round as opposed to only modifying Mario before like 80% or subtle acceleration exponentially as Bill gradually gets closer and closer to 100% rescued. Mario for example does not have to have infinite variations of jumping -K sizes if that messes with the math which might break Bill, Mario can at least have a few jump options from -K 100Gi to -K 0. Mario should gradually jump smaller and smaller per pass. Mario should expect 1000 passes (not rounds) meaning Mario should not race to -K 0 too quickly. Mario can increase jumping per stall. Mario may want to decrease jump sizes faster in some cases but default should be slowly and gradually. Sonic should follow that same logic. Tetris probably could be similar. Timeout probably the inverse or relative to the difficulties Bill might run into.

Mario's first jump should be -K 4Gi, gradually go down to -K 0 over the course of 1000 passes. But when stalled or in specific situations according to the Escalation Protocol depending on the Five-Factors, Dmesg, the Map File, and everything, Mario should sometimes escalate back up step by step to larger jump sizes. For example, If Mario stalls at -K 1Gi, then perhaps Mario should jump at -K 2Gi in the next round. But that is more so relevant after like 80% rescued or depending on all the things. Bill should gradually react faster and bigger as time goes on. Sonic, the same. Tetris, probably the same. Timeout, probably the same in reverse perhaps.

Overtime Protocol
Mario can jump up to say -K 100Gi in crazy situations when escalating. But Mario starts at -K 4Gi and then -K 2Gi and so on. Going up above the starting point of -K 4Gi to -K 100Ki is called Overtime Escalation (or overflow) as it is related to the Escalation Protocol. Other flags can have Overtime too. Sonic could go from -a 25M to -a 0 with a -a 100M overtime. Tetris -c 2048 to -c 1 with a -c 131K overtime. Timeout from -T 120s to -T 1s with a -T 1200s overtime. Perhaps other flags can have similar systems if applicable. Each flag can follow the 1000 passes template by default. In special situations, flags can go off these outlined routes if Bill needs to do something crazy sometimes. But most of the choices Bill makes should be mostly influenced to a large degree by the Escalation Protocol.

Blake-85 Protocol
The Blake-85 Protocol is a general rule related to everything Bill-related. Many things can be pass-influenced until 85% rescued. By default, Bill should decrease settings per pass minus stalling. Generally, many discs may not stall a lot before 85%. After 85, Blake pressure Bill to escalate up to every single round. I even recommend a gradual transition to Roundly-Reactions.

Ned Protocol
The Ned Protocol is part of the Stall Protocol that we talked about for months. The Ned Protocol pushes Bill not to react every round until 85% rescued. Bill can react normally per pass. In some cases based on the Escalation Protocol, Bill might increase Mario and Sonic to rush through passes when needed. But generally, Bill should limit changes per round before 85% rescued. From 85% to 95%, Ned pushes Bill to react starting at every 20 rounds for a pass and then every 15 rounds for the next pass, 10 rounds for the next, 5 rounds for the next, and then every single stall for all passes after that. For the first 85%, Ned should react after 50 consecutive stalled runs.

After 85% rescued, Bill might consider the following flags sometimes for example:
-P --data-preview, -d --idirect, --max-read-rate, --max-slow-reads, -e --max-errors, -r -retry-passes, -R --reverse, -O --reopen-on-error, -X --max-read-errors=, -A --try-again, -M --retrim

For the first 85%, Bill may want to consider including the following flags for example:
-n --no-scrape, -N --no-trim ,-r0, --cpass=1, -u

11:59 PM
I told Gemini to write JORDAN="$ERROR $MARIO $MODE $PASS $SONIC $TETRIS $TURTLE" and it took Gemini like ten tries. That makes Gemini a very bad AI. If there is conflict, you should tell me. Like if $MODE was actually code that existed in other places in Bill for example or if it was a secret code that would cause certain results, it is your job to tell me. If there were no conflicts, then there is no reason for you to no write $MODE. Right now, my DVD is at 86%. Bill ran -K 4190109Ki -n -N -u --cpass=1 -P -a 1 -c 2048 -T 120s but I think the first round or pass should be faster. Bill should probably try different things per pass or round after 85% and especially after 95% rescued. I think Bill should try max Sonic and Mario while suffling through the other Jordan Flags. Bill could shuffle through Tetris. Bill could keep Sonic while slowly decreasing Mario per pass. There are so many flags Bill could try. Eventually, Bill might need to try Trim, Scrape, -R, -O, and so many flags. I am not sure what Bill might do right now if I let Bill run. Generally, the Timeouts should be less than 20 seconds. Recently, Bill would run -T 120s and it seems Bill escalates too fast for Timeouts. Bill probably needs a more sophisticated logic for deciding when to extend Timeouts. Bill is too bipolar sometimes with Timeouts running -T 120s or -T 1s as both are sometimes counterproductive. Extending Timeouts might generally be ineffective on bad sectors or when error rate is high while the read rate is zero. It might be that there are many bad spots on this current disc which probably means Bill needs to avoid extending Timeouts above 20 seconds most of the time. Maybe in good spots, extend to 40 seconds. But 120 or even 1200 seconds might generally be a waste of time outside of very unique situations.

Twitter Tweets
04:06 PM

Grandpa Oatmeal born in the Netherlands, does that mean we can clone Peter Rasp now?

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.