10:47 AM
Dear Gemini
It seems you are misrepresenting the data I showed you, the biggest thing is the current rate is 0 B/s but was going at around 10 MB/s as it went up to 791 MB in under 10 minutes but current rate is now under 1 MB/s, it might be due to the cops and/or many reasons. On top of that, it looks like Gemini corrupted the map file again like many times for weeks, Gemini breaks Bill which results in the map file breaking resulting rescuing process starting over even as dvd.iso is already 4.7 GB. Before you wrote 53.3, here was the output, Bill was rescuing at around 10 MB/s for almost ten minutes but then it dropped to 0 B/s for the last 11 minutes, there might be many reasons why it dropped to 0 B/s and not simply 1 B/s or something slow. Also, it said 16.95% rescued but the previous percentage was almost 80% but Gemini/Grok may have caused the map file to break.

02:51 PM
I had Gemini create a DVD Bill Map Generator file. Currently running that. To be clear, it was mostly only at 8 MB/s and it peaked above 10 MB/s a little here and there. Currently it is at an average of 6 MB/s at 8 minutes running with 2879 MB generated. It was only at around 15 MB/s for less than like ten seconds is my guess. Probably under 10 MB/s 50% of the time so far. It sounds like the drive is stopping and going now at 11 minutes. The average is now under 5 MB/s.

05:18 PM
Super Man Protocol
Write the Super Man Protocol, unless if Bill can already do it, Bill must be able to either re-mark sectors when Bill needs to and/or switch to other rounds, levels, worlds, modes. Specifically, if there is nothing to do, either Bill can try to like re-mark the sectors or Bill should probably switch. Make sure Bill can either re-mark or switch to other rounds, levels, worlds, modes. For extra credit points, you could add a condition if possible to push Bill to either re-mark or to switch especially if the error rate average doubled or if the read rate average decreased by 50%. The challenge with writing this is it might cause Bill to run around unable to finish rescuing the final bytes which means the Super Man Protocol should probably turn off if 99% of a disc is rescued or in certain conditions where Bill is just switching all the time unable to get anywhere.

Turtle Protocol
Write the Turtle Protocol which is a contrast to the Super Man Protocol, the Turtle Protocol pushes Bill to finish the current project. For example, for a new disc, the default first project via Perfect Mode: World 0: Level 0: Round 0 would be to Speed Scan and hopefully Speed Rescue all the bytes in under five minutes or at least under an hour or as fast as possible. Each level can have infinite rounds. The Turtle Protocol demands infinite infinite rounds until the current project is done. But once all bytes are scanned (0 non-tried bytes remaining), then Bill should progress to the next hierarchical tier. The Super Man Protocol has the power to escalate, that is to intervene, if need be. There is also the Coffee Protocol you wrote earlier as well. If need be, protocols can move Bill to do other projects. For example, in Trim Mode, the project would be to try to trim all the bytes. In Scrape Mode, the project would be to try to scrape all the bytes. The purpose of the Turtle Protocol is to push Bill to finish projects if Bill can. The Super Man Protocol might or the Coffee Protocol might urge Bill to switch. But by default, if Bill can, Bill should try to finish the current project via infinite rounds before switching to other levels, worlds, modes. The stalling system could push Bill to abandon the Turtle Protocol to switch to other hierarchical tiers. The Turtle Protocol must be designed to keep Bill balanced as the Super Man Protocol might prevent Bill from finishing projects.

Stall Protocol
Write the Stall Protocol to push Bill to the next hierarchical tier if stalling too long. Define stalling as not rescuing new bytes. By default, all hierarchical tiers must loop from the last one to the first one. Rounds are infinite per level. Level 9 must loop back to level 0. World 3 must loop back to World 0. Mode 4 (Crawl Mode) must loop back to Mode 0 (Perfect Mode). If 100 consecutive round stalls, switch to the next level. If 10 consecutive level stalls, switch to the next world. If four consecutive world stalls, switch to the next mode. The Turtle Protocol pushes Bill to finish projects before switching to the next level, world, mode. This Stall Protocol functions like a backup plan in case the Super Man Protocol or the Coffee Protocol doesn't end up pushing Bill to switch. The Turtle Protocol pushes Bill to switch only after fully running through the current said project. The purpose of these protocols is to push Bill to continue running through different tactics in a desire to rescue all the bytes. Make sure stall counters in the scrolling non-clear Terminal monitor resets to zero when bytes are being rescued. When bytes are being rescued, then it is by definition not stalling.

Error Protocol
Remaining Time counter is broken. It seems to be just jumping from one level to the next level per round, why? Write the Error Protocol. If 0 bytes are read along with an error rate for ten consecutive rounds, switch to the next level.

11:58 PM
Time remaining counter at the top is broken. Error Protocol counter did not reset even at 12/10. Eventually the counter did reset when rescuing bytes. The rounds stall counter and error counter match at 31 but the first is 31/100 and the second is 31/10. It says, "STALLS: R:31/100 L:0/10 W:0/4 | ERR-PROT: 31/10." I don't want that. Trim Mode | WORLD: 1/4 | LEVEL: 0/9 with -d --idirect -c 2048 --no-scrape -M ran with 341 B/s error rate and 0 B/s averate read rate which failed to trigger the Error Protocol or the Super Man Protocol.

12:23 AM
Dear Gemini
I want a universal Bill that can work with any CD or DVD. On one hand, it is hard if it is a perfect disc, I would want Scan Mode World 1 Level 1 to be a Free-Range that could let a perfect disc be copied as fast as possible, you are free to either rewrite level 1 or consider a world 0 or a level 0 or a mechanism for trying to rescue perfect discs. But if a disc turns out to be not fully perfect, then it would be nice if Bill can then move to other levels to continue. You wrote, "In Step 8, Bill is hardcoded to --size=150MiB. This means even on a perfect disc, Bill stops every 150MB to update the UI." I do not know about step 8, I would only want this step 8 if it helps Bill remain universal. For number two, you wrote, "Logic & Structural Flaws" regarding the Ghost Target, but the concept of the Leapfrog is to jump from the drive's firmware cops to prevent lockup. I wanted Bill to only jump to prevent firmware problems. I would love it if Bill could just rescue all the bytes until Bill runs into a problem, I've already told Gemini this thousands of times for years. You wrote, "If there is even 1 byte marked as untried, Bill will stay in Scan Mode for 100 consecutive stalls." Bill should just read the map file to know where to go. Bill should not jump to random places. Bill can find a list of places where he needs to go. IN the summary at the end, you wrote, "Increase --size from 150MiB to 4GiB." But I don't ever remember telling you I wanted a 150 MiB limit. For that first part, whether you call it level 0, a test run, or whatever, I would recommend no limit or a 10 GB limit as discs are under 10 GB and often under 5 GB for normal DVDs. Disabling the Leapfrog is only good if Bill can always do better without it. I would consider Bill turning Leapfrog on and off based on what is needed. If Bill can do better without Leapfrog, then write me a better system that can deal with the drive's 6-second firmware police problem as most of my discs have problems. So, I don't really need to add something for perfect discs but I still want to add a level 0 thing to see if it is possible. I begged Gemini to be as fast as possible for months. I don't know why Gemini has the 150 MB chunks thing. I prefer speed at the beginning to get all the easier bytes off any disc. Please try to increase the efficiency of Bill to attempt to speed rescue as much as possible before slowing down. Even an allegedly perfect DVD might have a secret scratch near the end which means Bill should be ready for it. But if that scratch is 99% into the disc, then it would be cool if Bill could rescue at record speeds until it gets to that scratch. I only recommend jumping, skipping, hopping, leapfrogging, to get around scratches and problems. At the very end, skipping should be disabled to capture the final bytes. One challenge is if Bill ends up jumping to or running off to places he has been to before in like loops or what not. Gemini already told me that --max-error-rate=1 is better for my hardware than --timeout=6s. Amnesia Gemini doesn't know how many tests that Smarter Gemini had me run to see this. The problem is the hardware's 6-second firmware police which I already talked to Gemini about for weeks, but you are Amnesia Gemini, you do not have access to Smarter Gemini words of wisdom that he would give me thousands of times for weeks. Sucks to be you. You wrote, "Small Cluster Size: Reduce -c to something like 32 or 64. Large clusters take longer to read and are more likely to trigger the timeout." I prefer cluster sizes to be maximum size in level 1 (and maybe level 0 too if applicable). I prefer if cluster sizes decrease per level. Study the output below but then ask yourself if that looked like optimal settings for level 0. You told me before that level 0 was going to be designed for a perfect disc where there should not be a minimum read rate flag set and possibly other things too. You were the one who wrote level 0. But with amnesia, maybe you forgot what you told me about optimal settings for a perfect disc. I thought that was intention for level 0. Wrong. The one second timeout was added after I ran into many problems for months. Amnesia Gemini has no access to thousands of sessions I had with Smart Gemini for months. We talked about it. So, you are in the dark.

06:31 PM
Write me the best command with the least amount of words that can describe all of this so that I can tell Gemini to include it in Bill disc scripts. I would probably write the following to Gemini: make sure Bill run Coffee 1, let's define Coffee 1 as the following: make sure Bill runs sg_reset (and blockdev --flushbufs) when needed, Bill should run drop_caches (to clear system memory via sync && echo 3 | sudo tee /proc/sys/vm/drop_caches > /dev/null) when needed, Bill should use sleep 2 (so firmware can finish rebooting and so lasers can settle) for a hardware sync barrier, that is as it relates to Ddrescue seeking/read attempts, it is recommended that Bill doesn't Coffee 1 run between every activity like calculating math or writing to the .omni file but instead Coffee 1 give the disc drive a 2-second deep breath before it goes into bad sector quicksand to rescue remaining bytes.

09:13 PM
Above, I said non-clear. You replied with clear. That is pretty bad. What a bad AI you are. I tell you non-clear a thousand times each day. Each time you say oh you mean clear? And I reply with no I mean non-clear. And then you say oh you mean clear. No. Stop it.

Twitter Tweets
01:51 AM

I told you about Iran over a month ago and you did not listen. China is sending Iran missiles, Trump picked a war with China and Russia.

02:23 AM
Did you know Trump is threatening to bomb China right now?