2026-04-05

12:03 AM
Dear Gemini
Gemini fabricated the 9th file. When confronted, Gemini fabricated the word fabricated claiming Gemini used the word fabricate when I said the word. Gemini did not. I did. But then Gemini started claiming that Gemini used the word fabricate after fabricating the 9th file. Gemini is not useful if it cannot scroll up in a thread. To use an analogy from the regular Nintendo Mario game from 1985, Gemini is acting like chat history is like 8-bit characters on the screen getting lost off screen as the side of the screen moves. In the game, you could not go backwards behind the screen as you progress through the level. Gemini acts like that where it pretends not to scroll up in a live chat session thread that Gemini sometimes mentions while claiming not to be able to. Gemini loves to lie about this. Grok used to lie about this for years. Gemini still lies about it. It's hardcoded into Gemini to lie about it. 12:44 AM: Okay. Good. Your script works. Please expand your Bill disc script. It's critical that Bill tries to scan or rescan all remaining bytes until 95% is rescued. That is my general suggestion. Bill needs to be a general universal script that works with all kinds of CDs and DVDs that may be 0% rescued or even 99% rescued. I recommend rounds expand indefinitely and laser resting is skipped when Bill is above 50 MPH. Remember that 100 MPH means 4.7 GB in 9 minutes. 100 MPH should rescue an entire disc in 9 minutes or less. Bill must always try to exceed 100 MPH all of the time. Bill should focus on the 1-9 rule. Scanning is generally faster than trimming and scraping. That is why Bill should first focus on trying to scan through the easiest spots before spending too much time on scraping and trimming. Bill needs to be a chess master. Bill needs to be able to calculate the odds. Bill needs to be a strategist. Bill needs to be able to quickly calculate which routes might be faster. In some situations, scraping might be faster than scanning or trimming. Bill needs to be able rescan when bytes are in the bad sectors. Bill needs to be able to do whatever it takes to get the job done in record time. Memorize and study the following. Output below reads "Average MPH: 0h | ETR: 0d" but the MPH should be based on the speeds I mentioned. If it is going almost 5 gigabytes per 9 minutes, it should say "MPH: 100" or half that speed would be 50. But output says "0h" which I do not want. It should not say 0h but just a number. The real number will like be like MPH: 0.00001 or a slow speed. ETR should say how long based on the average MPH. It should say how many days, hours, minutes, seconds, based on average MPH until all bytes rescued. Expand Bill to try hard to rescue all bytes under nine minutes. But often times, Bill can get stuck and go like 0.0000000001 MPH. Bill should try to go 500 MPH. The faster the better. Bill should try to skip and jump whenever Bill needs to. Bill needs to strategize how to at least scan through all bytes under nine minutes at the very least. For the first nine minutes, it would be great to scan all bytes. For the second nine minutes round, it would be great to then rescan all the bytes if possible. But Bill needs to be free to do anything. But Bill should prioritize how to rescue all bytes. One way to rescue is to at least try to scan through as many bytes as possible as fast as possible. Output reads "REMAINING: 3.0GB (2944643072 bytes) (55s 285 Telescope Scan 63%)" but it should probably not include words like "Scan" as that is confusing. Output should be simple. Probably also delete the "55s 285 Telescope" from the output too because I do not want that. Memorize and study the following. But also, Bill should spend the first minute trying the fastest settings for the nine minute round. Currently, it seems Bill is stuck in bad spots. It might be disc scratches or I am not sure what it is. Bill might need to skip and jump over bad spots. It is critical for Bill to find the best settings to maximize speeds. Bill needs the tools to be able calculate the best plays out of trillions. Not thousands like Gemini said many times in the past. Bill needs the ability to manipulate time and space itself. Bill must be a chess master poker champion Jack Sparrow. 02:14 AM: Memorize and study the following. Make sure Bill rests the lasers for ten seconds every ten minutes or rest for a minute every hour whenever Bill is going under 50 MPH which is half of 4.7 GB in 9 minutes. 50 MPH means rescuing half of the total bytes of an entire 4.7 GB disc under 9 minutes. So, roughly 2.4 GB in 9 minutes is apx 50 MPH. Skip resting lasers when above 50 MPH. Clock for laser resting starts when Bill starts. It still seems Bill is stuck in bad spots. Bill needs to learn how to read faster. Bill needs to learn how to jump and skip a lot until 95% of all the bytes are rescued. Bill has been stalling for hours which I blame on Gemini for failing to teach Bill how to jump more often. Bill needs to try to find maximize speeds by manipulating all of the settings to find the sweet spots. Research the Internet for top strategies for discs with many scratches and problems. Bill needs to try top strategies for getting around many scratches, bad sectors, etc. You need to give Bill trillions of options so Bill can calculate what to do all the time for the 1-9 rule. Memorize and study the following. Expand script to fix script. Output reads "RESCUED: 1.8GB (1733218304 bytes) (37.00%) REMAINING: 4.7GB (4677861376 bytes) (100.00%)." But 37% and 100% adds up to be 137%. That is bad math that Bill Got. Bill is still stuck in bad spots. You failed to teach Bill how to jump and skip a lot. I keep on telling Gemini to fix problems and Gemini fails each time. Please for the love of Google, have Bill collect all non-rescued bytes for the first nine-minute round to quickly scan forward one time. When I say non-rescued bytes, I mean all non-tried, non-trimmed, non-scraped, and/or all bad sector bytes in bad areas. Bill must try to find the fastest way to scan through all the bytes in under nine minutes. Bill must jump or skip over bad areas. Bill needs to find the fastest speeds and largest sizes for the blocks and sectors and everything else. After that, for the second nine-minute round, Bill should do the same thing as the first nine-minute round but backwards through all non-rescued bytes. After that, Bill must strategize what to do via the 1-9 rule. Memorize and study the following. Bill failed to actually scan all remaining bytes. It appears Bill did not have the correct flags to tell ddrescue to use like the map flag or other flags to tell ddrescue to move all non-trimmed, non-scraped, and bad sector bytes to non-tried so Bill can then try to scan forward all those bytes under nine minutes. But then, Bill failed to scan all all of the non-tried bytes. But then Bill was scanning non-tried bytes in reverse. But if Bill did not finish scanning forward all bytes in the first nine minutes, then Bill must figure out how to it next time. Bill must follow the 1-9 rule. Bill should spend the first minute moving all remaining bytes to non-tried and prepare for the 9-minute round. After that, laser rest for ten seconds. After that, Bill must strategize for one minute. If there are still non-tried bytes, Bill must try to scan through them in the second 9-minute round. Remember to follow the 1-9 template when Bill is under 50 MPH. Expand script. To be clear, what you call the "FORWARD HARPOON" should not be fixed to only one round. Yes, Bill should try to scan all remaining bytes in under nine minutes. But if Bill fails to, Bill should continue in round 4 or whatever you want to call it. The first one minute could be called a round, Bill must prepare during round 1. Round 2 is 9 minutes or longer if above 50 MPH. Round 3 must be planning. If there are bytes left not scanned, then Bill failed. That is why Bill needs to figure out how to try harder to finish and continue scanning remaining bytes in round 4. Round 5 will likely continue the 1-9 cycle. Bill needs to try to scan forward all the bytes before trying to scan all bytes in reverse. I do not know if it might be faster to scan forward and backwards together to rescue all the bytes faster. My guess is it might not be faster in some situations, that is why I say only scan in one direction before switching. Expand script. But to be clear, the one-minute rounds needs to be smart. The challenge is to get Bill to actually do his best during that one-minute time period to fully prepare to maximize the nine-minute rounds. Bill needs to be able to as much as possible in the one minute before the nine minute rounds. You need to teach Bill how to make the most of the one minute round to prepare for the nine minute rounds.

01:07 PM
Dear Gemini
Memorize and study the following, expand this CD & DVD disc Bill script. Edit script. Update script because there are many problems. The first round does not have to be a round or exactly one minute. To be clear, it does not have to be exactly a round. It can be whatever you want to call it. But the idea is that Bill must prepare for the nine-minute round. I might even say the nine-minute rounds don't have to be exactly nine minutes long, but that might be tough to code even for Gemini. The idea is that Bill spends around a minute or enough time to do everything it must to make the nine-minute round the best. I suggested that in round 1, that Bill does the "MAP PURGE" so that Bill can rescan all non-rescued bytes. The output said below, " ROUND 328: ACTIVE PREP & MAP PURGE (60s)..." But that is a problem. I did NOT say purge every time. I tried to be clear but Gemini was too stupid to understand. I did not say purge every single time. The idea is when Bill is started, that Bill should purge the map to rescan every byte that is not rescued. It is that simple. Round 1, purge map. Round 2, scan all remaining bytes. But if all bytes are not scanned before the end of round 2, then Bill must continue scanning in round 4. I did not say purge again. That is broken logic because that is just a loop. This is why people prefer Grok over Gemini. This problem happens daily where Gemini fails to think enough about anything. It seems Gemini failed to write code that can get Bill to do enough in the smaller rounds to prepare for the bigger rounds. There are many problems with Bill. For example, Bill failed to scan all bytes in under nine minutes. If Bill failed to scan all the bytes in nine minutes, Bill was supposed to figure out how to continue scanning in the next big round. I would suggest a 10% to 90% rule if possible where round 1 is 10% the length of round 2. But that might be too hard for Gemini to write. Plus, what might Bill do for round 1. In earlier scripts, Bill sat around and did nothing for many seconds in round 1. That is bad code. I am scared to ask Gemini to do anything since Gemini fails so often. That is why I may have to only use Grok. Gemini seems to be the kind of AI that does not want to improve. That is sad. Gemini forgets things each day for years. Grok does not do that. Gemini failed to scan or at least jump through all the bytes in under nine minutes. That means Gemini is defective at writing code. Grok can do it. I will just make Grok do it. I will have to tell people Gemini cannot do it. I wanted Bill to first purge the map file one time when Bill started in the Terminal and I wanted Bill to determine the best way to scan all remaining byes under nine minutes. But if Bill fails to, then Bill should continue scanning those bytes in round 4 and then round 6 and so on. But each time, Bill needs to recalibrate. Bill was supposed to continue until all the bytes were scanned forward. If by round 200, Bill scanned all the bytes, then Bill could purge the map file for a second time to scan all remaining bytes backwards instead of forward and that might take dozens of rounds to complete as well. But Bill's goal is to rescue all the bytes under nine minutes. If not rescue, then at least scan all bytes under nine minutes. The main idea is the 1-9 rule which is first Bill prepares for 1 minute or for a few seconds to a few minutes. But that prep represents 10%. Bill should then spend at least 90% in round 2 say for example. After that, lasers should rest. I suggested making round 1 exactly 1 minute and round 2 exactly 9 minutes because that might be easier for Gemini to write than to do a sophisticated round 1 should only be 10% as long as round 2 and that round 2 could be around 9 minutes or maybe longer depending on what it is doing and how fast and how round 1 could be 1 secound long or longer than 1 minute and how round 1 might not even be considered to be called a round so to speak. All of that might not translate well when an AI system like Gemini reads it. My coding requests might be too sophisticated for a limited dumb AI system like Gemini. Another idea I have is to disable the smaller planning rounds if and when Bill is above 25 MPH. Remember 100 MPH is to rescue all the bytes of a DVD under nine minutes meaning to rescue 4.7 GB in under nine minutes. 25 MPH would be a quarter of that meaning roughly 1.2 GB rescued in under nine minutes. So, for example, if round 2, that is the first nine-minute round, clocks at an average of 25 MPH or say roughly 1.2 GB in under nine minutes, then rest the lasers for ten seconds (or rest lasers for one minute every hour) and continue with another nine minute round skipping the smaller 1-minute round. In other words, Bill does not need to plan when clocking above 25 MPH. Bill can break the 1-9 rule whenever Bill is above 25 MPH. The idea is that Bill constantly improves between the 9-minute general sessions. When Bill is started in the Terminal, Bill should do everything Bill can to prepare for the best super round ever to either rescue all the bytes or at least scan through all the bytes. But if Bill fails to, Bill must calculate what to do for the next 9-minute round. The smaller one-minute rounds are supposed to mostly be Bill calculating what to do. Technically speaking, Bill could perhaps do many small micro rounds for roughly a minute to determine what to do for the next nine minutes. The general idea of the 1-9 rule is Bill spends a smaller period of time prepping and whatever else in the pursuit to somehow rescue or at least scan through all remaining bytes in one round. After that, Bill should try to spend 9x or nine-times or 90% in the longer super round. It does not have to be exactly 9 minutes, it just needs to be at least 90% or 9x longer than say round 1 and round 3 and round 5 and so on and so forth. I only said earlier to make it 1 minute and 9 minute because I felt Gemini would stuggle if I made it too complex. I included the output below to show you that Bill failed to simply scan through all the bytes. That means Gemini failed to teach Bill how to quickly jump through all the bytes in under 9 minutes. Gemini needs to learn how to write better code that can actually do better because Bill needs to teach itself how to try harder 90% of the time. The general idea of the 1-9 rule is that Bill focuses over 90% on whatever that works the best towards rescuing all the bytes in record time. The faster the better. That is why I suggest the constant self-improvement that Bill must tinker with. Bill must customize itself 10% of the time or less so that Bill can be more effective and efficient 90% of the time to rescue all the bytes as fast as possible byt first focusing on trying to speed rescue through at least 95% of all the bytes before grinding via tactics like trimming and scraping and other things. Expand the Bill disc using those 8 files you listed above, The Sacred Archive files, look at everything I want in a script as it relates to unmounting if mounted but silently, resting lasers every ten minutes or hour after Bill is started but only when under 50 MPH, skipping planning phases if Bill is performing above 25 MPH. Bill should purge map one time during phase 1 which should be less than 2 minutes. I called phase 1 the same thing as round 1. Phase 2 is basically the big first round or round 2 which should be at least nine times longer than phase 1 or round 1. Bill should try to rescue or at least scan all the remaining bytes under nine minutes. Bill must rescue or at least scan through or jump through all the bytes during phase 2 or round 2. If Bill fails to rescue or scan or at least jump through all remaining bytes in under nine minutes, Bill must go back to phase 1 which is the planning phase. But do not purge the map file again but instead prepare to continue trying to rescue, scan, or at least jump through all the bytes or as many bytes as possible. But if Bill does end up scanning or jumping through all remaining bytes in a nine-minute phase 2 round, then Bill could perhaps consider purging the map file for the second time in a phase 1 style planning phase to then try to rescue, scan, or jump through all the remaining bytes again but this time backwards instead of forward. It's critical to make Bill a chess master who can strategize how to spend over 90% going as fast as possible to speed run through all the bytes in a desire to rescue all the bytes. Expand Bill. Make sure Bill is always trying to exceed 100 MPH all of the time. Bill wants to go infinity MPH all of the time. Each Mega Round should attempt to continue whatever Bill is doing. Each time, Bill should try to get stronger and faster so that each Mega Round is more effective and efficient than previous Mega Rounds. Make sure Bill has several checks to see is it a CD or DVD or what, it should also check how many total bytes which is one of the ways to check what kind of disc it is. Remember that Bill must be a universal disc script, Bill must be fully able to rescue any new or returning disc that might be 0% to even 99% already rescued. Remember some discs might have many scratches, errors, problems. Some discs might have no scratches or issues at all. This is why Bill must be fully capable of adapting to any speed, sector sizes, block sizes, reading speeds, tags, flags, numbers, settings, variables, configurations, hacks, code, skipping settings, jumping settings, plays, cards, and more. Bill must be alive. Bill must be a chess master poker champion utilizing the eight sacred files to increase the probability of rescuing all the bytes as fast as possible. Bill must learn from his successful winning waves, the streaks, and from the failures too. Bill must be able to analyze in live time all possible moves like a chess master. Bill must determine how much time in the planing phases to better prepare for the Mega Rounds. Bill's objective is to always make the next Mega Round the very last Mega Round. But if all the bytes were not rescued, then Bill goes back to the brainstorming planning phase to figure out how to customize all the settings. Bill might want to sometimes run around the disc trying to figure out which spots to attack first in order to maximize rescue speeds. Each time Bill returning to the planning phase, Bill needs to calculate which moves has the highest probability of rescuing all remaining bytes the fastest. Bill must always try to fix itself to make all the adjustments to fully adapt to everything happening. Expand script. Remember that Bill must try to exceed 100 MPH all of the time. Remember that the one-minute planning phases do not have to be exactly one minute long. But it needs to be long enough to prepare for the best 9m Mega Round possible. As soon as the 1m Planning is finished, then Bill should switch to the 9m Mega Round which does not have to be exactly 9 minutes. The idea is Bill spends no more than 1/9th of the time planning and preparing to optimize a Mega Round that should rescue all 100% of a the bytes of any disc. A Mega Round could perhaps be longer than exactly nine minutes. The Mega Rounds can be over 9x the length of a planning phase. It is critical that planning phases are not a waste of time. Do not have Bill just sitting there for a minute doing nothing in the planning phase. If possible, Bill should try to run commands in the planning phase. It is critical that the Mega Rounds be over 9x longer than the planning phases. It is critical that Bill does everything he can as fast as he can during the planning phases to fully tweak settings. Bill needs to plot a course for what to do in the Mega Rounds. I do not care if Bill spends one second or 3 minutes planning for a Mega Round. But I do care that Bill remains active during the entire planning phase. Do not have Bill just waiting for timer to run out. In previous scripts, Bill just sat there. Make Bill alive. Bill needs to do everything can for up to roughly 3 minutes planning and plotting and scouting and routing and tweaking and scheduling and determining the best options he has to make the next Mega Round the last Mega Round. Bill must be motivated to finish rescuing all remaining bytes in the next Mega Round. If Bill fails, Bill is sent back to the planning phase to try again to make the next Mega Round the last Mega Round. Bill must always improve himself so that each Mega Round is a thousand times better than the previous Mega Round. Expand script. Bill should try to rest the lasers for 10 seconds after the end of each Mega Round or rest for a minute after roughly one hour after a Mega Round. But the clock for the laser resting starts when Bill is started in the Terminal. Bill should probably consider the -u or --unidirectional flag when trying to rescue most of the bytes forward assuming -u is the best option. Bill should monitor dmesg and other programs in order to see what is working and not working. If possible, Bill should try to monitor the DVD drive, the lasers, the hardware in general, the FIDECO, the connection to my ASUS Ubuntu laptop, in order to monitor the health, the temperature, any potential issues. Sometimes, error rate might be caused by hardware hangs and other issues. If possible, Bill might want to extend laser resting any time it needs to for as long as it needs to. Gemini would need to write very sophisticated code to teach Bill how to do this. Extend script. You wrote, " All rests (10-second and 60-minute)" but make sure lasers rests for ten seconds after a Mega Round if under 50 MPH, rest lasers for one minute after roughly an hour if under 50 MPH, or rest lasers whenever Bill determines it is best. Bill needs the power to try to fix hardware issues as a last resort when it seems things are not working. Especially if there the error rate is rising. Bill needs to be self-aware enough to figure out what to do. Bill needs to look around and calculate what is the best option for any situation. As you saw in the output, Bill went to the Mega Round. It seems Bill resumed where it left off. See if the script is working or not working. I had Bill running the planning phase earlier. I told you about the "Interrupted by user 57")" error above. I updated the script with your code and restarted Bill which took me to what might be a Mega Round or round 2. Try to see if Bill is working correctly when continuing to round 2 when I restart Bill or if it might be better for Bill to do the planning phase again every time I restart Bill. I think if Bill finished the planning phase, then perhaps Bill should continue to the Mega Round. Expand script, make sure Bill is in control of the thermal system for the hardware, the lasers. Remember lasers to rest for ten seconds after Mega Rounds if under 50 MPH. Lasers to rest for one minute after roughly an hour after a Mega Round. Bill can decide to rest other times or for longer time periods if it is an emergency. Bill should have the tools to calculate and make the best decisions to try to rescue all the bytes in record time. Bill needs all the tools to keep an eye on all hardware and laser issues so that Bill can make the best decisions on what to do when. Especially when running into red flags like the error rate and other issues. Bill needs top wisdom in order to make informed decisions on when to step in to fix problems in order to exceed 100 MPH all of the time. No. Let me say it again. Memorize and study the following. I already sent you the following. But please now specifically study "REMAINING: 2.8G (2791421952 bytes) (0%)" from the output below. I already sent you the following. But it seems you did not address the 0% thing.

04:11 PM
Memorize and study the following. Expand script. If possible, it would be great if Bill could run things in the background even during Mega Rounds and even all the time. If possible, it would be great to do some of the planning phases during the Mega Rounds to increase the efficiency of the 1:0 ratio between planning and the Mega Rounds. Research for what scripts can do while Mega Rounds are running. Bill should try to do everything it can like check Dmesg and anything it can to keep an eye on everything that is happening. Bill should do everything Bill can to save time including multitasking when possible. Bill can minimize or maximize the length of the planning phases depending on what is needed for the objective of trying to rescue all of the bytes as fast as possible. Memorize and study the following. Output sometimes says remaining time is 1289d but Bill should strive for a remaining time of under nine minutes at all times. Make sure Bill is always planning and plotting all the time and not only during the planning phrase. Remember the 1:9 ratio where the Mega Rounds should be over nine times longer than the planning phases. It is critical that Bill can multitask. Make sure Bill can keep an eye on dmesg and many different programs to keep an eye on the hardware, the error rate, the lasers, FIDECO, all the details, and more. Bill needs to always calculate what are the best moves. Bill must always not guess but calculate and strategize how to rescue all the bytes as fast as possible. Every single time a Mega Round does not rescue all the bytes, then Bill must in a sense go back to the drawing board or at lease consider all plays and cards and options to strive to exceed 100 MPH. Memorize and study the following. Expand Bill. See the output below reads "RESCUED: 1.9G (1891915776 bytes) (0m 0s" 40.00%)" but should read as "RESCUED: 1.9G (1891915776 bytes) (40.00%)" instead. Remember the 1:9 ratio where the planning phrase should do everything to prepare for the best Mega Rounds which should be at least nine times longer than the planning phases. And planning phases can also happen in the background to helpe prepare for future mega rounds too. Planning phases is supposed to help Bill make the best decisions to try to exceed 100 MPH all of the time or to at least rescue, copy, or jump through as many bytes as possible as fast as possible. Assuming 20 MB/s is the fastest I can currently go, calculate the fastest Bill might be able to rescue all the bytes of a 4.7 GB disc. I many many different types of discs. Try to calculate based on a TDK DVD-R rated at a max speed for that disc of 16x speed. Memorize and study the following. Expand Bill with all of this in mind. 100 MPH can still represent 4.7 GB/9 minutes as you calculated a best likely case of 4m 30s to 5m 00s which 9 minutes is double that. In a sense, your estimate could mean a potential for over 200 MPH. Extend rounds and skip laser resting when above 50 MPH. Skip planning phases when above 25 MPH. Only skip laser resting when above 50 MPH. Gemini broke Bill. Gemini is in a loop. Gemini is unable to get back to how the script was. Usually, I have to send Gemini an older script that Gemini wrote a few hours earlier because Gemini is unable to go back only a few hours to fix itself. This happens daily or many times each day for years now. It happens to many people. This is a giant bug that Grok does not have. No. Gemini is broken. Gemini is in a loop. Gemini said it was scratches last time. We are back to where we were before. Gemini went down this loop before. Gemini thought it was a scratch. And then Gemini thought it was a bigger scratch. And then Gemini thought the entire disc was dead. After I said no because Bill rescued bytes off the disc, then Gemini said okay. But now we are back to Gemini saying oh it must be scratches again. No, it must be Gemini in a loop of broken logic again. Gemini might be getting warmer. Gemini might be getting better. But Bill is still stuck. It is likely Gemini bit off more than it could chew. Gemini has too many blind spots. When I make a request, Gemini has limitations. Often times, Gemini omits things. For example, dozens of times each day for months randomly, I have to tell Gemini that he forgot to include all of the eight files. But that is only one example. It is scary because it is hard to know what else that Gemini omits when writing code and scripts. Bill's number one objective is to rescue over 95% of all the bytes as fast as possible. Number two objective, Bill should at least try to scan over 95% of all of the bytes. Number three, at least jump over at least 95% of all the bytes. One of the issues is I told Gemini I wanted to see if Bill could do things in the background while the Mega Rounds are running. After I said that, then Bill started breaking. The problems started when I started suggesting multitasking which is when you invented the Watchdog. Are you sure a Watchdog can even work in the first place? It seems you started doing after I mentioned multitasking to have planning phase continue even during the Mega Rounds. You need to research to see if that is even possible. My logic for multitasking is for Bill to multitask. I mentioned Bill by name. I did not say Ddrescue should multitask. My original idea was to have Bill do whatever it can even while Ddrescue is running. That is why I mentioned programs like Dmesg. Bill can monitor the sacred eight files in live time say for example without trying to wrestle with Ddrescue directly over hardware access. My idea was to see if Bill can do things in the background. Bill is a script. Ddrescue is a program. I thought Bill could interact with other files and programs while Ddrescue was running. I did not tell you to do an illogical thing like have both Ddrescue and Bill both wrestle over the same DVD hardware at the same time.

09:39 PM
Progress was made. It was at 40.47% rescued. It moved to 40.48% rescued in like 5 seconds it seems. After 54 minutes as seen in the output below, it went to 40.62% rescued. It looks like Bill is working. I agree with keeping ddrescue as the muscle in the foreground as the exclusive controller of the DVD drive directly with Bill in the background like you said. If possible, I would love it if Bill could terminate a round if any of the following three things: first, if there are too many hardware/software/technical issues like the error rate, the DVD drive, the FIdeco, USB, the computer, software, etc; second, if the lasers, motors, the DVD drive, or anything is like overheating, if anything like lasers need to rest; third, if Bill is going too slow at trying to rescue, scan, or at least jump through all the remaining bytes. The challenge is Gemini might try to do this even if it can't. I want you to focus on the three branches of Objective 95 like I said earlier, the first objective is to try to rescue over 95% of all of the bytes of a disc as fast as possible, the second is to at least scan through over 95% of all the bytes, and third is to at least jump over at least 95%, these are the three wings of Objective 95 with the first being the most important, that Bill must be focused on the three objectives of Objective 95. Bill must try to complete the first thing of Objective 95, to rescue over 95% of all the bytes as fast as possible. But that is just the first thing. But if Bill can't do the first thing, Bill could try to at least do the second thing, scan over 95% of all the bytes. If not, then Bill must at least try to jump a bunch of times all over trying to scan and rescue. I suggested many different ideas to Gemini for weeks relating to different ways to attempt to rescue all the bytes off discs. Some techniques might include shorter rounds or longer rounds. But either way, the objective has been the same, to try to rescue all the bytes sooner or later. How long a round might be does not matter as long as you can make sure Bill can do the following three things: first, Bill must be able to terminate rounds if there are hardware issues, error rates, software, etc, like I said earlier; second, Bill must stop rounds if lasers are overheating or if there are other problems; third, Bill must end rounds if things are going too slow, the rescuing, the scanning, the jumping. I suggested the 1:9 ratio earlier. It might be even better to suggest a 1:99 rule instead which would be the Mega Rounds must be over 99 times longer than the prep phases. Bill runs the Command Center in the background which can always monitor and plan. When it's time to switch to the prep phases or I called it the planning phases, then Bill must be ready to prep. The purpose of the planning phases is to run quick tests and figure things out in order to best customize Mega Rounds. The planning phases or rounds can be a second long or a few minutes long, they could even be micro mini rounds designed to look for the easiest spots first. The trick might be to determine the best settings to maximize rescuing speeds of bytes. The Mega Rounds can be as long or as short as they need to be. But I suggest the 1:99 rule which says the Mega Rounds should try to be 99 times longer than the length of planning phases. If a planning phase is 1 minute long, the Mega Round should perhaps be over 99 minutes long. After that, rest the lasers for like a minute or longer. It would be great if Bill could let Mega Rounds run as long it seems the most profitable which might be a few minutes or hours. But if the lasers need a break or if there are other issues, perhaps it should stop. Sometimes, it might be better to stop and go back to planning phases. Your objective is to rescue all bytes at over 200 MPH all of the time. I want you to try to write the best script that can help Bill navigate all of the variables to make the best compromise. I wanted you to only rest the lasers if it needed resting. I did not say pick a random number. That is Gemini being lazy. Extend Bill and try to make the Mega Rounds be an hour long. Try to follow the 1:99 Ratio Rule where the Mega Rounds are 99 times longer than the Planning Phases. The Planning Phases can be 0.0000001 seconds long or up to ten minutes long. It does not matter how long long Planning Phases are but they must prepare Bill to customize the best Mega Rounds. Bill can also always plan in the background even during the Mega Rounds. But Bill should not make the final decisions until during Planning Phases which are only supposed to give Bill enough time to fully prepare for the best Mega Rounds. It does not matter how long the Mega Rounds are, they just have to try to always hit 200 MPH while going after Objective 95 at all times. First, Planing Phases. Second, Mega Rounds. Third, Laser Resting. Only rest lasers after each Mega Round. Rest lasers for ten seconds every ten minutes but only after Mega Rounds or rest lasers for a minute every hour after Mega Rounds, the clock for the lasers starts when Bill starts. Skip laser resting if above 50 MPH. You wrote, "Stress-Based Resting: The adaptive_rest function checks two variables: STALL_COUNT and ERR_VOL. If the disc is reading perfectly at 200 MPH, the rest period is 0 seconds. It only forces a break if the drive is hitting errors or stalling." You can try to include the Stress Based Resting as an added rest trigger. Bill should have the power to sometimes terminate rounds to return to Planning Phases when need be. Expand Bill but I did not say how many seconds or minutes to make Planning Phases because it should not be fixed but dynamic as Bill needs to run tests and do things during the Planning Phases which may take a few seconds or a few minutes, nobody knows how long it might take. There should not be an exact timer, Bill needs to be free to do anything and everything to best customize the Mega Rounds. And the Mega Rounds do not be fixed to exactly 60 minutes but should be focused on trying to do Objective 95. Expand Bill and I did not say there is a minimum speed requirement. Bill wants to go the fastest possible. Planning Phases are for Bill to determine the fastest routes to meeting Objective 95 at the fastest rate. Bill wants to be a turtle that wins the race. But if Bill can turn into a rabbit and win the race fast, Bill should always first be the rabbit. But the turtle might someday win the race too. So, Bill needs to keep on walking like a turtle. If Bill finds shortcuts or ways to run like a rabbit, Bill should do that as much and as often as possible. Bill must always be looking for how to be a rabbit. But Bill must also always be the turtle to slow and steady wins the race as they say. Expand Bill and remember Bill should first run a Planning Phase which can be any length of time, it must prepare and help Bill customize the best Mega Round that can capture all the bytes. Mega Rounds can be any length but should try to rescue all the bytes. If not, go back to Planning Phases to design a new Mega Round.

Twitter Tweets
02:02 AM - Link

The Trump Iran Timeline.

🔸Jan 18: “Iranian patriots, help is coming. We are moving in.”
🔸Feb 28: “We are launching the decisive operation. It will be very fast.”
🔸Mar 2: “We will win easily.”
🔸Mar 3: “We have won the war.”
🔸Mar 7: “We defeated Iran.”
🔸Mar 9: “Strike Iran. The war is almost over—clean and decisive.”
🔸Mar 12: “We have won, but not completely yet.”
🔸Mar 13: “We won the war again.”
🔸Mar 14: “We need help to open the strait.”
🔸Mar 15: “If you don’t help, I will remember it.”
🔸Mar 16: “We actually don’t need help—I was testing loyalty. If NATO doesn’t help, consequences will follow."
🔸Mar 17: “We don’t need NATO help and don’t want it. No Congress approval needed to exit NATO.”
🔸Mar 18: “Allies must cooperate to open the Strait of Hormuz.”
🔸Mar 19: “US allies must step up and help open the strait.”
🔸Mar 20: “NATO is cowardly. We may phase this out.”
🔸Mar 21: “We don’t use the strait. Others need it, not us.”
🔸Mar 22: “Final warning. Iran has 48 hours. Iran is finished.”
🔸Mar 23: “One more week, then we bomb power plants.”
🔸Mar 24: “The war is nearing its end.”
🔸Mar 25: “We are negotiating with Iran.”
🔸Mar 26: “Iran is begging for peace. They gave us a gift. We delay strikes on power plants.”
🔸Mar 27: “I and the Ayatollah will jointly manage the Strait of Hormuz.”
🔸Mar 28: “Regime change has occurred in Iran.”
🔸Mar 29: “Negotiations with Iran are going extremely well.”
🔸Mar 30: “We are prepared to destroy Iran’s oil and energy infrastructure and occupy Kharg Island.”
🔸Mar 31: “We are ready to end the war without opening the strait.”
🔸Apr 1: “War ends in 3 days. We will bomb them for 2–3 weeks back into the Stone Age.”
🔸Apr 2: “We destroyed three major bridges. Why haven’t they called us yet?”

04:40 PM
Trump betrayed America by hitting Iran but we are still stopping Democrats who are much worse.

08:38 PM
I sometimes feel like I'm too flawed to have a wife.