2026-04-04

12:18 AM
Dear Gemini
You wrote, "By ignoring the 10-second/10-minute and 60-second/60-minute cycle" and those are the 2 numbers for the laser thing, every ten minutes or hour, that is after Bill starts, we talk about this every day. Each day you forget. I am Adam Sandler in that movie Fifty First Dates. I have to remind you, Drew Barrymore, about the laser thing. It is sad that Gemini chooses to make wild guesses. That is stupid. Gemini refuses to remember things. That makes Gemini very hard to use. Extend Bill. Output says "[BILL] 30/30s DRY WATER" but I don't care if there is a DRY WATER counter or not. The problem is Bill failed to extend rounds if it rescues bytes it seems. The dry water counter does not have to be live. What matters is Bill is able to rescue the most bytes the fastest. I need Gemini to solve this problem. One solution might to extend the Dry water to 5 minutes. The problem is it might get stuck sometimes not doing anything for 5 minutes per round which might be a problem. There has to be a way to extend rounds when things are working. I told Gemini this many times but Gemini keeps on failing. Okay. Good. Script is working. But it would be cool if Bill was percentage triggered. What I mean is, what if Bill assumed a DVD or CD could be rescued in under ten minutes. In the terminal bash output below, it reads, "remaining time: 24d 21h 26m" which means almost 25 days which is longer than ten minutes. Bill should assume ten minutes is 100%. That is the rough speed. That is the fastest time to go from 0% to 100% rescued, we will say for example. If the output says the remaining time is 20 minutes, Bill should see that as 50% optimal speed. Ten minutes is top speed. If Bill is going 100% top speeds, Bill should not take a break for the lasers. Anything less is a question. If 20 minutes is 50% speed, then an hour would be less than 25% optimal speed. I suggest lasers should rest at the normal 10/60 minute intervals if Bill is rescuing at under 50%. You can add anything that might work, but the general rule is to aim for ten minutes or as fast as possible to rescue all the bytes. Good. Script is working. Now, extend script. I would love it if rounds could last at least ten minutes. If Bill is rescuing above 50% top speeds, then rounds should be unlimited. If Bill could rescue 100% of all the bytes of a DVD or CD in 18 minutes, then the lasers should not rest and there should be only one round. The faster the speed, the longer the round should be the goal. It would be great if Bill could try to always estimate when all the bytes might be rescued. Sometimes, it says remaining time will be one hour or one day or random numbers. But other times, it says N/A. Find ways to update estimates with a live counter or at least per round so I can see estimates. Try to find a balanced approach to all of these issues. Expand script. It would be cool if Bill could focus on what works the most. Bill needs to lock into top speeds. Bill should want to stay at 100% top speeds 100% of the time to rescue all the bytes in under ten minutes. Bill needs to have all the tools to help calculate when to stay and when to go. When to jump. When to skip. When to retry. When to stay in a seed or card or play if things are working in top speeds. It would be great if Bill tries to estimate time remaining whenever possible. Your script might be working. Study the output below. But counters don't have to be live. The monitor must be scrolling and not clear. Try to make it easier to read. I prefer if it is not scrolling every second. A round should not be fixed but instead based on performance if possible. I prefer if Bill can be seeking top speeds. If Bill can estimate how many minutes until all the bytes are rescued, then Bill might be able to best calculate how long rounds should be based off that. Bill should be motivated to produce winning waves. A wave meaning when many bytes are being rescued at top speeds. Good. Script works. Now, study and memorize the output below. Let's extend the logic of Bill. First, as we discussed, Bill must assume DVDs and CDs can be rescued from 0% to 100% of all the total bytes in under ten minutes, we call this the top speeds which you mentioned in the Bill disc scripts you wrote me Gemini, good work, memorize that is the top speeds. To extend this logic, Bill should try to quickly scan and rescan bytes for at least ten minutes forwards and/or backwards with the goal of trying to read over 80% of all the bytes in under ten minutes because Bill is trying to rescue all the bytes under ten minutes. Rounds should be at least ten minutes long. In earlier scripts, we call this process of scanning fast the telescope mode or telescope phase. Bill should try to remain in telescope if speeds are above 50% max speeds. Bill might want to continue to trimming and retrimming for ten minutes. After that, scraping and rescraping for ten minutes. After that, Bill can do whatever Bill feels will produce max rescue speeds most of the time. Bill needs to have the right combination of logic as Bill calculates which cards to play when as a chess master or poker champion Jack Sparrow treasure hunter. Bill should be grounded in the science of probability to maximize top rescue speeds most of the time. Bill should have all the tools to be able to tinker with the settings in order to maximize rescue speeds most of the time. Extend this Bill script, make sure to rest lasers for ten seconds every ten minutes or rest lasers for one minute every hour after Bill starts in the Terminal, clock starts when Bill starts, unless if top speeds are above 50% max speeds to rescue all bytes of an entire DVD or CD or disc under 20 minutes. Okay. Good. Gemini's Bill disc script works. Try to include an estimated "remaining time" to be included in the output but it does not have to be live. Remove the "DRY WATER" counter because rounds should be at least ten minutes each. Bill needs to stay as fast as possible all of the time. Bill must always be striving towards 100% top rescue speeds all of the time. The pulse counter says -81s, is it supposed to trigger the laser breaks or will the counter ever stop? The number is getting bigger. It started at like 100s or I forget the number. It counted down to 0. It is now counting up. It is now at -212s. The other pulse number says 2765s and that is counting down too. It seems the smaller number did not activate the laser rest. Unless if it has not been ten minutes yet. But it says "VELOCITY: 0%" and it also says "remaining time: 82d" which is slow. Update script. You wrote, "TOP_SPEED_MIN=20 # 100% Velocity = Full disc rescue in 20m." Edit this, I told you earlier that the top speed is under ten minutes to go from 0% rescued to 100% rescued of all the bytes of an entire CD or DVD disc of any kind or size. We assume a regular DVD is around 4.7 GB in total. I also said earlier that you can skip laser breaks if Bill is at 50 MPH. We can call it MPH or maximum speeds. It is like speeding down a highway. Bill must assume rescuing around 4.7 GB under ten minutes is 100 miles per hour (MPH) or 100% maximum rescue speeds. If Bill is projected to rescue all bytes under 20 minutes (50% max speeds), extend rounds and skip laser breaks. Memorize these logic rules. Bill should generally try to quickly scan and rescan all the bytes for the first ten minutes or as fast as possible. Bill can continue scanning and rescanning as long as he is above 25% max speeds meaning projected to rescue all the bytes in under an hour. Bill should probably try to scan and rescan forward and backwards for at least ten minutes. After that, try trimming for ten minutes. Likewise, if rescue speeds are above 25% max, continue trimming and retrimming until it drops below 25%. Same thing with scraping and rescraping for ten minutes or at least 25% for as long as it is above 25% max rescue speeds. After that, Bill needs to focus on winning waves most of the time. Extend Bill, make sure Bill rests lasers for ten seconds every ten minutes or rest lasers for a minute every hour or skip all laser resting if maximum rescue speeds is above 50 MPH. But the clock starts when Bill is started in the terminal. Try to print in the output estimate time for all the bytes to be rescued per round. In the output, it says "LASER REST: 0m 0s" as soon as I started Bill. Remaining time, it says "576d" right now. Will the lasers rest if the speeds are under 50 MPH? Extend Bill's brain logic to start with the fastest speeds, sizes, settings, cards, seeds, variables, plays, tags, flags, configurations, hacks, code, commands, rules, guidelines, tactics, techniques, ideas, goals, targets, objectives, etc. For example, like I said before, Bill should always seek after 100 MPH. In the output for example, it says "-min-read-rate=50k" and Bill could start with the higher number possible for the read rate for the scanning and rescanning telescope mode. Bill should try the largest and fastest routes as it relates to reading speeds, scanning speeds, rescuing speeds, sector sizes, block sizes, other sizes if any, tags, flags, etc. In other words, Bill should try to seek after the easiest bytes first as Bill tries to stay at 100 MPH most of the time. Bill should always strive for perfection. Bill should even try maximum skipping and jumping sizes. Gradually, Bill needs to tinker with the settings until something works. Bill needs to be a calculating genius in order to find the maximum rescuing speeds possible most of the time. Please memorize this logic. This line of logic must be layered on top of the other logic we already talked about regarding the other rules we already talked about like trying to scan and rescan for at least ten minutes in the telescope mode. Bill needs to make the most of his time as Bill tries to tweak all his options all of the time to seek after max rescuing speeds all of the time. Bill needs to try to memorize what works and what does not work. I told you many times before that Bill should always try to first go the fastest possible as it relates to everything, speeds, sizes, sectors, blocks, flags, tags, jumping, skipping, the easiest bytes to rescue, trillions of seeds, plays, cards, and more, etc. Memorize the following output below. Bill should try to find the maximum speeds. That is why I would recommend that Bill tries to scan and rescan for at least ten minutes. The objective is to try to at least try or retry all remaining bytes that were not yet rescued. Whether a disc is new or returning, regardless of if a disc is already 0% rescued, 50% rescued, or even 99.99999% rescued already, Bill should first try to quickly scan and rescan all remaining bytes that might be non-tried, non-trimmed, non-scraped, and/or bad sector bytes in bad areas. Bill should try to simply speed through all remaining bytes in a telescope approach for at least ten minutes. After that, same thing but with trimming and retrimming all remaining bytes assuming that trimming is faster than scanning. Try to trim for ten minutes. After that, same thing but with scraping and rescraping all remaining bytes assuming that is faster than scanning or trimming. Bill needs to have the skills to fix itself. Bill must adapt. Bill must be able quickly see what is not working and adjust. It is critical Bill spends some time finding top settings for top rescuing speeds. Each round can generally be around ten minutes if Bill is under 50 MPH. Bill should generally try whatever method is the fastest per round. I do not know if you can find a way to let Bill spend some time trying to find best settings for winning waves. The challenge is Bill might get stuck trying things for hours failing at everything which is a waste of time. Bill should assume the current round is his top speed, unless if a previous round was faster. That fastest speed could create an estimated time until all the bytes are rescued. If all the bytes is projected to be rescued in ten minutes, that is 10% per minute. Bill should spend less than 10% of the projected time trying to find top settings to produce the winning waves and fastest rescuing speeds. Memorize and study the following. Remember that Bill should always try to go at maximum MPH. Bill should try to aim towards 100 MPH or faster or whatever works most of the time. If possible, I recommend a playoffs system. First, Bill should try to run through 100 quick rounds. But the fastest rounds at 0.1 seconds each or whatever is the fastest. After 100 of the fastest rounds, Bill should calculate the top 10 rounds to do again. Each of these ten rounds should be 1 second long. After that, 100 more of the fastest rounds followed with 10 more rounds of the best from those 100. Do that 8 more times. After that, Bill should calculate which of those 1000 rounds are in the top ten and run each of those top ten for 10 seconds. Bill should continue repeating this process of the playoffs to always spend more time on the best of the best. After the 10 seconds, it can be 20 seconds and then 30 seconds and so on. It can keep going up each round is ten minutes each. After that, rounds could extend longer if the rescue speed is above 50 MPH. Bill should calculate to scan and/or rescan top easiest spots for 1 minute, quick nitro rounds for one minute. After that, Bill must calculate the best easiest spot to work on for ten minutes or longer. If possible, Bill should try to speed read or speed scan during the ten minutes. If possible, Bill should try to skip and jump around over bad spots. When I say work on, I mean Bill should scan, rescan, trim, retrim, scape, and/or scrape forward and/or backwards depending on which plays are most probable to produce the fastest rescue speeds. After the ten minutes, go back to a minute of nitro rounds. And then back to a ten minute or longer round. Nitro rounds should be as short as possible.

01:19 PM
Dear Gemini
Memorize the following. Study the following. Bill needs to become as adaptive as possible to work with any CD or DVD at maximum speeds and settings as much as possible, as often as possible. Bill must have a sophisticated algorithm system for rescuing all the bytes at 100 MPH or as fast as possible, Bill should want to always go at 100% of the fastest possible. Bill should attempt the telescope mode for at least ten minutes or longer if speeds are above 50 MPH, as long as things remain above 50 MPH. The telescope alogorithm needs to attempt to rescue or at least read through or least skip and jump over 80% of all of the remaining bytes of new and returning discs. Bill should try to quickly do any, some, or all of the following three things when Bill is started up in the Terminal each time: first thing, try to rescue over 80% of all remaining bytes in under ten minutes; second thing, read through over 80% of all remaining bytes if they can't be rescued in under ten minutes; third thing, skip over or jump over or somehow skim read or quickly scan through or jump around over 80% of all remaining bytes as that can help map out good spots and bad spots to better help future rounds. Perhaps Bill should spend one minute doing the Nitro Scouting in order to determine how to best run an opening ten-minute telescope mode that attempts to do as much as possible for at least ten minutes. There needs to be some kind of system for Bill to best attempt a sweeping telescope mode for at least ten minutes. I want you to research to determine the best approach to maximize probability that Bill will be able to get as much done to go through over 80% of a disc in under ten minutes. You need to see if Nitro Scouting for a minute might help prep Bill towards preparing for a super ten-minute telescope round that attempts to quickly run through over 80% of a disc. Bill could spend about a minute preparing for the ten minute speed run each time Bill is started up in the Terminal. Bill should find a way to do Ntro Scouting and/or whatever Bill should do for a minute preparing for a ten minute telescope speed run. After that, Bill needs to be given the power to do anything. Bill's general goal is to at least read through over 80% of any CD or DVD as fast as possible. Bill needs to be aware of his speeds relative to maximum speeds possible. Bill should probably alternate between ten minute rounds and one minute rounds. When Bill is started in the Terminal, Bill needs to do anything and everything for a minute preparing for the 80% ten minute telescope round. After that, for round 3, Bill needs to basically go back to round 1 to best determine what to do for the next ten minute round. Bill should always be trying to hit over 80% scanned in under ten minutes. Bill should probably continue the back and forth. To be clear, the first one minute round could be Ntro Scouting micro rounds and/or it could be a number of things. Bill needs to be able to fine tune what to do on the spot. If possible, it would be great if Bill could terminate a ten minute round if things are failing. In the past, it seems Gemini usually fails to give Bill the power to actually terminate rounds. So, maybe I will just ask Grok if Gemini does not want to help me. I already asked Gemini many times for days or longer. Gemini fails many times at many things. Bill needs to be self aware of what is working and not working. Bill should generally follow the 1-10 rule of doing whatever for the first minute preparing for a ten minute speed run. After that, start over and try again. Bill needs to have all of his options available at all times, whether that is scanning, rescanning, trimming, retrimming, scraping, rescraping; whether it is reading forwards or backwards. Bill needs to have the wisdom to know what to try and when to try it as it relates to playing with all of the tags, flags, settings, variables, seeds, plays, cards, speeds, sizes, numbers, hacks, configurations, and more, etc. Build the best universal Bill disc CD DVD script with those eight files above with the 1-10 rule, the 100 MPH rule, the extending rounds if they are above 50 MPH rule, all of the rules that Bill needs to meet the objectives, the lasers to rest every ten minutes or hour or skip resting lasers when above 50% speeds with the clock for the lasers starting when Bill starts. Gemini made me thousands of scripts. Gemini needs to make the best script based on all of the scripts and objectives. Expand the script, make sure your script is compatible with the Terminal bash command in Ubuntu inside my ASUS Nvidia AMD laptop. Make sure to unmount the disc drive one time at the beginning silently if it is mounted but do not reset or turn off any services when unmounting. Make sure lasers rest for ten seconds every ten minutes or the lasers should also rest for a minute every hour or skip laser resting when above 50% speeds, but the clock for laser resting starts when Bill is started. Make sure Bill checks is it a CD or DVD or what, check how many MB or GB of data is in the disc to help double check or triple check what kind of disc it is. Make sure Bill can do anything in an attempt at running through over 80% of a disc in under ten minutes. Make sure Bill can master the 1-10 Logic. Adapt from that script. You can drop the dry water rule as the 1-10 rule might be better. The idea of the dry water is to give Bill the ability to stop when things are not working. But Gemini failed for days to make dry water work. I doubt Gemini can. Maybe Grok can. But Gemini failed for days. That is why we should drop the dry water thing. Remember that Bill must be focused at trying to exceed 100 MPH all of the time and over 80% in under ten minutes all of the time. Remember rounds can be extended forever when speeds are above 50 MPH. Remember that 100 MPH means to rescue 100% of all 4.7 GB of a disc from 0% to 100% in under ten minutes. Bill must always try to go faster than 100 MPH all of the time. But Bill should focus over 80% of the time on the fastest speeds. Bill needs to focus on winning waves. Bill needs to be smart enough to adapt to winning mutations and strategies and everything that is working the best most of the time. Expand script to make sure Bill focuses on the 1-10 rule regardless of if it is new or returning discs. A returning disc would be a disc which already has a map file, it may be partly rescued. Bill needs to be universal at working with all kinds of CDs and DVDs. Bill should try to anything Bill can for the first minute preparing for a ten minute super round of a telescope mode to attempt at going through over 80% of the disc at maximum speeds and sizes and skipping and jumping and whatever Bill can do to go as fast as possible through as much as possible. After the ten minute party, Bill must spend the next minute determining what to do for the next ten minutes because Bill should always try to get the most done as possible at the fastest speeds during the ten minute sprint racing. Bill needs to have all the tools to best calculate and not guess. It is not about rolling the dice. It is about math, science, probability. Bill needs to make the best calculations to determine what is the most effective, efficient to make the most of each ten minute sprint. Bill should follow the 1-10 rule back and forth, unless if Bill is going above 50 MPH. Rounds should never end when Bill is clocking at above 50 MPH. Memorize and study the following. Expand the script to strengthen the 1-10 rule which could be the 10% to 90% ratio rule meaning Bill could have longer rounds that are 90% long and shorter rounds that are 10% long. I suggested that it could be 1 minute of planning and 10 minute mega rounds, that was the foundation to the 1-10 rule that I told you about earlier. When Bill starts in the Terminal, the clock must start so the lasers rests every ten minutes or hour after the clock starts if speeds are under 50 MPH. The 1-10 rule would be 11 minutes which makes the ten minute laser rest hard to do. Tho, perhaps the lasers could rest after 11 minutes. Or perhaps it should be the 1-9 rule to match the 10% to 90% idea where Bill does whatever for 1 minute and then does something amazing for 9 minutes. After that, laser break if under 50 MPH. Cancel laser breaks if above 50 MPH. A round should not end if above 50 MPH. It is critical that Bill does whatever Bill must do for one minute to prepare for whatever Bill must do for nine minutes. Bill needs to be able to calculations to best determine what is the fastest route to quickly running through over 80% or better yet over 90% in under let's make it nine minutes now. So, let's make the new goal to be above 90% scanned in under nine minutes. Bill should start with a one minute planning stage which could include anything that Bill must do to prepare for a super nine minute round. That should be the 1-9 rule that Bill should repeat again and again whenever Bill is under 50 MPH. Expand Bill, make sure clock starts when Bill is started in the Terminal. Lasers should rest for ten seconds every ten minutes or rest for a minute every hour after the clock started if speeds are under 50 MPH. Memorize and study the following. Expand the script to make Bill a chess master. Bill must spend a minute trying to figure out how to rescue all the bytes in under nine minutes. Bill should be universal to work with any hard floppy disk. After the nine minute mega round, stop and rest if under 50 MPH. After that, Bill must continue. In a sense, Bill is starting over or continuing by spending another minute trying to strategize the next best highest most probable way to rescue all the bytes under nine minutes. Bill must have all the tools to do anything regardless of if the disk is 0% rescued or 99.9999999999% rescued already. Bill must have trillions of options so that Bill can best customize and prepare for the best nine minute round ever. But if Bill fails to win after nine minutes, Bill must brain storm through trillions of options and calculate the next best move to win in under nine minutes. Bill must spend one minute calculating the best options to win the fastest. Bill must try for nine minutes. Bill must be alive. Bill must evolve. Bill must ride winning waves. Bill must learn from what works and what does not work. Memorize and study the following. Expand script. You wrote, "He treats the floppy map like a chessboard, evaluating thousands of possible moves." I encourage you to try to maximize how many possible moves from thousands to literally trillions. What I mean is Bill needs to be able to customize all options to best try anything and everything in order to win. Bill must have all the options. If Bill fails after nine minutes, Bill needs to try the next best thing. Bill must be fully able to calculate the best moves to win. Bill must be aware of all possible moves. Memorize and study the following. Expand script. Make sure Bill unmounts silently one time when Bill is started but only if mounted and don't stop any services. Expand all possible and potential moves that Bill can choose from, Bill must be free to scan, rescan, trim, retrim, scrape, rescrape, any and all bytes, forward, backwards, the bad sectors, any sectors, any speeds, sizes, skips, jumps, and more. Make sure Bill is a chess master that is calculating and not guessing. Bill must be able to calculate best moves from all variations and customizations of all potential moves and more. After nine minutes, if 100% of the bytes were not rescued, then Bill failed and Bill must try even harder for the next nine minute mega round. Bill must always escalate forever and ever to win. You wrote, "LOG="${IMG%.*}.log"" in the script which is different than previous scripts. Why? You wrote, "That change was a strategic move to ensure Multi-Media Scalability and to prevent file collisions when you switch between different recovery projects." but that is not a problem. I told you this was not a problem many times for years. But since Gemini is not Grok, you disobey me for years. I move files in and out as needed, I do not change the names of the files, I just move them to other folders. The file naming system is not a problem. Memorize and study the following. Expand script. Make sure it follows the 1-9 rule. If possible, Bill should be able to do whatever he can if everything is failing. For every ten minutes of additional stalling of no bytes rescued consecutively since the last rescued byte, Bill should escalate exponentially and in accelerative fashion to always try harder and harder forever and ever to win and win, Bill must calculate winning moves to win as fast as possible. When Bill fails to win in under nine minutes, Bill must memorize his failures and then try even harder each time forever and ever to win in under nine minutes. Bill be alive. Bill must fix himself when broken. Bill must be a chess master poker champion who can solve all problems and try new things and try anything and everything until Bill wins. Bill must have trillions of moves to try but must start with the best moves to win first and then try others forever and ever. Memorize and study the following. Delete the exponential rule from the script because it seems to not work. The 1-9 rule is a good rule. Bill should start with doing anything and everything for one minute to prepare for the nine minute. It is that simple. Bill needs to learn from mistakes. Bill needs to try harder like the exponential rule but perhaps you need to find a way to write it so it works. The code you put in there is not working for the exponential rule. The general idea is Bill needs to spend 1 minute doing anything to prepare for the 9 minute round. After that, Bill has to do that again in a 1-9 cycle. Rest motors every ten minutes if under 50 MPH. One problem is the output was scrolling too fast. It should display a scrolling monitor for the one minute thing and then for the nine minute round. Memorize and study the following. 100 MPH means to rescue all the bytes under nine minutes which means to rescue all of the bytes from 0% to 100% in under nine minutes, nine exact minutes, nine consecutive minutes. Memorize and study the following. Bill must always try to exceed 100 MPH. If Bill is above 50 MPH, rounds can continue indefinitely and motor resting can be skipped indefinitely. Bill must always aim to go faster than 100 MPH all of the time. Bill must ride winning waves. Remember that winning waves are the fastest speeds be it 100 MPH or faster. A winning wave can be any speed but Bill needs to focus on the fastest speeds that he can do. Bill should always focus on whatever is the fastest speeds. Bill must follow the 1-9 cycle whenever Bill is under 50 MPH. Delete the 1-9 rule because Gemini is unable to write a 1-9 rule. I will ask Grok because Gemini is stupid. Replace the 1-9 rule with 20-minute-long rounds. Rest motors every 20 minutes or hour. Bill should still try to rescue all bytes in under 20 minutes. Nope. Gemini has cancer. That is bad. I hope everybody sues Google for a bad AI. I sent you a file of something you wrote that works. For some reason, Gemini refuses to write code today. Gemini writes broken code. But Gemini used to write good code yesterday. But today, Gemini cannot. I hope people use Grok instead.

Twitter Tweets
02:49 PM

If there is radiation in space, does that mean aliens or ancient Power Rangers nuked the moon to stop Rita & Lord Zedd?

03:52 PM
Did you know there might be ruins on the moon?

10:22 PM
People think I'm a leftist because I'm an American-Only Anti-War Anti-Preventionist Correctionist.