08:19 PM
Dear Gemini
Levels could be built around major themes. I like the modes and worlds I designed. To built on top of that design, the question would be what what are all the themes out there. One theme might be the --min-read-rate flag. Talk to me about different strategies for the read rate because I would do a minimum of 100m for perfect mode and 30m for scan mode. I don't think 100m is literally possible but Gemini suggested it. Perhaps 100m would just push the drive to go as fast as possible. The limits for my discs and drive right now might be under 25m or at least most of my discs. Therefore, 30m might be identical to what 100m tries to do. In the past, I would have Gemini write several speeds where Bill would start with the fastest speeds like 30m for a minimum read rate and gradually go to lower speeds like 20m, 10m, 1m, and so on. That is one tactic. Another tactic might be the reverse of that. First off, perhaps not using --min-read-rate flag might do better in some cases than 30m or 100m. Beyond that, perhaps a lower rate might help if it saves overall time in trying to rescue many bytes. I don't know the math, the averages, the probability, etc. Talk me through different tactics as it relates to different --min-read-rate flags speeds, settings, the debate on when to use the flags versus NOT using the flags, whether to start at lower speeds or higher speeds, talk about the pros and cons between different approaches relating to these types of flags and themes.

09:06 PM
Dear Gemini
Write instructions for Gemini for writing Bill to develop the Speed Switch which will also be called the Max Per Hit (MPH) as a parody of Miles Per Hour. Instead of pinning and fixing the --min-read-rate flags to specific modes, worlds, levels, or even rounds, keep the MPH gauge pinned to the Speed Switch. The challenge is writing triggers, the if this then that part of the code, I would love if the MPH could change even during rounds but I would settle for having the MPH fluctuate per round at the very least. The challenge like I said is in determining which variables might trigger the MPH to go up and down. I want the MPH to free to fluctuate between any round, level, world, or even mode. There are probably millions of ways to write code for a system as complex as this gauge. In my head, I can think of many different ways to writing MPH. There are many challenges as many things can go wrong with a MPH system like this one. Before I decide to give you all of my many ideas relating to MPH, I want to give you Gemini an opportunity to write as much as can as it relates to this. The following speeds:

30 MPH: --min-read-rate=30m
20 MPH
15 MPH
10 MPH
9 MPH
8 MPH
7 MPH
6 MPH
5 MPH
4 MPH
3 MPH
2 MPH
1 MPH
900K MPH
800K
700K
600K
500K
400K
300K
200K
100K
90K (with --timeout=5s perhaps)
80K
70K
60K
50K
40K
30K
20K
10K
5 K
1 K
500B
100B
1B
No flag null

Those are suggested speeds. And/or think about what if sometimes the MPH could be determined based minimum, maximum, and/or average speeds. So say for example if Bill is reading at 226.34567 kilobytes per second, what if the MPH Speed Switch locked onto that rate as to try to force that speed to continue for a period of time as to try to skip over slower spots.

In writing a MPH system, it can be challenges, many moving parts, many risks. One of the questions might be relating to which routes might save more time. To use an analogy, the turtle won the race because the turtle was consistent. The turtle was slow but was focused. The rabbit might be faster but might end up on roads that are thousands of times longer. What is tough is you may not know which routes the turtles and rabbits might take resulting in a hard time knowing how to do the math in guessing probabilities between different approaches. The rabbit might not only be on a longer road but might also stop and go more. Each time the rabbit stops, the rabbit might be wasting time. Perhaps a good MPH system needs a default route that takes in account all of these factors to come up with a balanced compromise that is founded on the highest probability of working, that is efficiency, effectiveness. The default MPH might be to start on off mode. However, I don't totally know as most of my discs probably have many scratches on them which sort of makes me want to focus on flying by as many scratches at the beginning as I can. But I know some might have only a few scratches. So, trying to create a universal Bill might be very challenging to do.

10:29 PM
If a 4.7 GB DVD has 400 MB of bad sectors in 4,000 spots all over the drive. Talk about everything that might help and hurt me in this type of situation, talk the pros and cons, all of the flags, speeds, settings, the cops, the variables, etc.

Shine bright while you're shooting for the stars because you might get stuck up there. Might as well make it count.

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?