2026-03-22

Welcome to my daily blog, my name is Oatmeal Joey Arnold, follow me on social media and on all the websites at Joeyarnoldvn or else. Wait, was that a threat? No way. I'm joking. But that's the thing about me, I'm a nerd stuck in the body of an athlete, born in 1985 in Oregon, been online since like 1995 (or longer) meaning I've been on the world wide web the past 30+ years uploading over 30K+ videos, we're talking thousands of hours of worth of content (I have millions of things online, literally), most of my content is terrible which is weird because I'm a perfectionist who would probably prefer only sharing my best stuff on the Internet. Click here for more information. Quick disclaimer, I sometimes like rant, I speak often from the top of my head opinions, feelings, random thoughts, I often don't even spell check, fact check, or look at what I've been posting on hundreds of websites and apps for decades now. But as I get older, I do try to be more careful as I try to summarize my life, my autobiography, to correct the record as I try to tell my side of the story to combat the Oatmeal Fake News that my lolcow trolls spam the Internet with as they fool people into believing the lies they tell about me. Not saying you should watch my videos. But if they can lie about me, they can lie about you. But I sometimes trolled my trolls to show the world how easy it is to fool trolls who fell for the lies I put out there. Most of what I try to do in my life probably fails big time you might say but I was at least able to scam my trolls a few times over the years. I sometimes utilize sarcasm, hyperbole, satire, comedy, absurdity, Devil's advocate, trolling, scamming, click baiting, out of context stuff, irony, etc. But I often wouldn't tell people when I was trolling or not trolling. If you studied me, you could eventually figure it out. But most of my trolls are too lazy to research beyond the tip of the iceberg which led to my trolls repeating lies they about me which would only take a second to debunk. I felt like I had more trolls at times than actual fans or friends. For more info, questions, feedback, join my Discord servers. I have more to say but I will continue writing some of this stuff other places as usual. Because I write many books worth of content all of my life. You can send your artificial intelligence or AI to give you outlines of my content and what not. But you have to always remind the AI that I've had hundreds to thousands of different accounts, channels, pages, groups, sock puppet alt accounts, personas, parodies, profiles, communities, entities, and so on and so forth, ask me about all of that if you dare. People are free to steal any of my like free content, you don't have to give me credit, do whatever you want. Timestamps generally in Pacific Standard Time (PST) or Pacific Daylight Time (PDT) unless otherwise noted. Welcome to my Oatmeal Daily which is generally posted & syndicated to different websites daily by me, Oatmeal Joey Arnold, feel free to mirror, edit, clip, reupload my content. For more information, see some of the links on this page or you can try to Google search or look me up using keywords like Oatmeal Joey Arnold @ joeyarnoldvn and other keywords. Try using different combinations of words in search engines for better results. Don't rename the script but fix the script. The script appears to be stuck in loops where it does not do very well. It appears the dvd.iso image file has not been modified in the last 3 hours even as your most recent script is running, the disc drive light is flashing, the drive is making normal drive noises, feels like the disc is spinning inside. It appears the script alternates between modes but is failing to make much or any progress. It appears the script ends up in loops where it goes over similar or identical spots of offsets. It might be that the back and forth between modes causes interruptions which results in the different modes starting over wherever they last were resulting in a stalemate. The output seems to claim an average of 0.1% rescued every like 5 minutes. Rounds appear to be an average of roughly 40-90 seconds long with an average of every other or every 2/3 rounds rescuing 0%. The DVD.velocity file has 0 bytes. The DVD.map file is constantly being written to as we speak. Dvd.memory file is 43 bytes in size. The DVD.winners file is 0 bytes. DVD.state file is 23 bytes. The DVD.iso file is at 3.3 GB and was not modified in 3 hours even as the Terminal says 0.1% is being rescued every roughly 5 minutes, it might be that what is being rescued was already rescued before which would result in the image file not being modified as there are no actual changes being made, that is my theory. I suggest the script tries to continue whatever mode the disc was previously in if it is a returning disc. If a disc is not on a path to be tried in 10 hours, the script should engage the brain or tier 0, there needs to be stop valves every minute, ten minutes, and hour. If 10% of a disc is not tried in an hour, activate the brain or the opposing athlete. Notice I said tried and not rescued. In other words, the focus is on speed runs like you wrote in earlier scripts, whether that is done via normal modes or AI modes or different tiers, the priority is to first attempt to try each byte on a disc. Please rewrite the script to ensure the number one priority of trying to try each byte in under ten hours or as fast as possible. Like in previous scripts, I want to run the script forever to rescue 100% of all the bytes but it is critical to first do all the non-tried bytes as fast as possible and to try all tricks to try each byte on a disc. Also, try to include multitasking if that is possible, scouting should happen while the script is running. In other words, scouting should happen in the background as each byte is being tried, the script should always attempt to build maps or systems for knowing which spots to target in the future. Study the following output, try to improve the script based on my main objectives and based on everything else I have every said to you or to anybody these past few weeks or longer. Don't rename the script, include 10 second laser resting every ten minutes and 1 minute laser rest every hour, it appears you removed that even tho it was in many scripts, the scout can continue to be integrated like before. Make sure the script utilizes all options, settings, variables, numbers, sizes, speeds, especially for the last mile meaning the last 99% of a disc. It seems you often omit things when you edit these scripts. It seems Gemini often fails to tell users when Gemini happens to omit things which could cause big problems as millions to billions of users globally may get really mad at Gemini in the future if Gemini chooses to continue to do this type of practice which may be considered by some to be deceptive and malicious. Don't rename the script. Fix the script. The DVD.log file is not being written to, it has not been modified by the script in over a day meaning your most recent script failed to write to the log. Normally, script write to the log and to the map. Your script doesn't seem to be working very well. The script should now be edited to focus on trying every byte in order. Use a sophisticated but thorough algorithm to try every byte in the fastest route. In other words, the script should not try random bytes. Instead, the script should use protocols for trying the easiest spots first. The script needs to know if the disc is a CD or a DVD or what. The script needs to try variables, tags, settings, numbers, speeds, sizes, that are most likely going to work. I am not sure if the scout is different than what the map is for. It seems the map is sort of like a scout. You could keep some or all of the things you had in previous scripts, but the script needs to first try every byte using systems to best the fastest routes to trying every byte. After every byte is tried, then you could utilize things from previous scripts that you wrote here, but the script needs to focus first on trying each byte as fast as possible. I did not say rescue, I said the script needs to try each byte at least. Remember to keep all the hacks for the last mile. The trying of all non-tried bytes could be like the first mile which should be focused. You can be as creative as you want with everything between the first mile and the last mile as you try to get the script to trim, scrape, and rescue every byte. But the first mile is all about trying each byte. Exhaust all options for attempting to try each byte starting with the fastest routes focused on the easiest spots first. Write the best script based on all of this and based on all of the previous scripts you have been writing for me for weeks or years. Don't rename the script, fix the script. Include dvd.iso, dvd.map, dvd.map.bak, and dvd.log. Do not omit the log file (--logfile) but the log file must be named dvd.log as that is what I have been naming the log files for years now. Three phases, the first mile, the last mile, and everything else in the middle. Don't eject. I told you that an hour ago. Gemini is bad for forgetting things in an active session. I will need to move to Grok as Grok does not forget things unlike Gemini. Please fix the script with everything in mind from all the scripts you wrote. Remember direct access to the disc is critical. Don't rename the script, update the script, yes try to estimate how many missing bytes count. Phase 2, the middle mile, should not be random but like phase 1 but focused on trimming and then scraping at least 99% of all the bytes. Use the best math to try to find the fastest path to trim and scrape each byte similar to phase 1. Like phase 1, phase 2 should not be random but should start with the easiest spots and then go to each byte at least once. Phase 2 should try all applicable hacks, tags, settings, sizes, speeds, variables, code, in the best order but not a random order but in an attempt to trim and scrape each byte. Include anything applicable from previous scripts. Don't rename the script. Make sure the script finds out what kind of disc is in the drive be it a CD or DVD or something else. Make sure the script has all the tricks to find the easiest spots to focus on the easiest spots in order. Remember the phases should not be random but should use math and science. The script should focus on the easiest spots first and only jump when things are not working. Only include applicable things from previous scripts if you think it helps. The problem is not the clusters. It is normal for DVDs to do 2048. Gemini is crazy not to know this. It is fine if the script adapts when it needs to adjust cluster size when it needs to but you need to realize that one of the issues is bad spots. The script should try to jump to every byte one time starting with the easiest spots to try each non-tried byte before it attempts to adjust cluster size and other settings. I went to bed at 02:40 AM. Woke up at 10:00 AM. Breakfast: 10:08 AM. Church sermon by Nate on personifying God's goodness, having integrity, conviction, to do the right thing, paying even when it's on the house after waiting so long at the drive-thru at Burger King was one of his examples. It was her birthday yesterday, I didn't know that. Islam history. Tech Kelly man said hi, he is new. Gave Leroy, his wife, and their neighbor a ride home, rolled back in time to pick up mom, got plants at Walmart filled up 4 gallons for $19 at Arco, sunny, back around 01:30 PM, DVD Work issues as Gemini gave me bad scripts or it may be multiple issues. Gemini is stuck in a logic loop where Gemini is making the same mistakes many times unable to fix itself. Gemini is becoming a very bad AI system because it has giant blind spots. It is still stuck even after ten minutes, it is doing nothing. It looks like Gemini has no idea what Gemini is doing. Study your last dvd_recovery.sh script file and compare it with the the dvd_recovery_previous.sh script from only a day ago, it was an earlier script you wrote which seem to have worked better. There might be many different reasons why there are problems now, it might not just be problems with just the script. One of the problems might be the log file. One of the problems might be the map file. Gemini changed the script many dozens of times for this same DVD I am rescuing these past few days, so it might be hard to know. Gemini has the power to know but Gemini seems to fail to study chat history which is probably why Gemini can't fix this problem even after trying dozens of times in a row. Lunch: 02:31 PM. Don't rename the script. Fix the script. Remember to keep relevant things including things I want, make sure to unmount at the beginning. Lasers should rest 10 seconds every ten minutes and for a minute every hour. I had Gemini write many different scripts for the same DVD, Gemini wrote dozens of scripts these past few days, Gemini used many different words to describe aspects of the scripts, words like phases, tiers, rounds, modes, etc. The back and forth of all these different scripts may have caused the map and log files to become inconsistent because the scripts changed dozens of times. I had scripts where there was like AI modes. Other scripts added a normal mode compete with the AI mode like as if they were athletes. Gemini wrote so many different scripts. Now, I have a different disc in the drive. I also have a returning log and map file. I want you to write a universal script that should work with any disc. Make sure the script finds out if the disc is a CD or a DVD or what. I already told you Gemini that the previous disc and/or script and/or map file and/or log file and/or the drive and/or maybe the cache and/or the kernels and/or a variety of issues may be problematic as we have already talked about for days in this conversation chat session thread above between me and Gemini message after message for days right here as it is active. So, sometimes, you can solve problems through a process of elimination. Therefore, I now have a different disc with a returning map and log file that I made with that disc via ddrescue. Write a universal script that should work for CDs and DVDs with everything we have talked about in mind. Make sure the script can work with any disc, CD, DVD, etc. Some discs are unfinalized with scratches. You are free to rewrite the script as much and as little as you want but rememeber the objective is to at least try every byte as fast as possible. You may want to let ddrescue have some freedom to do what it does best but you also want to sometimes nudge or push ddrescue when it gets stuck for too long. It is critical to find a balance between letting ddrescue do whatever it wants versus trying to order ddrescue around. I already told you many times how ddrescue has 3 steps, to try, trim, and scrape. It is critical to try to nudge ddrescue to do those 3 steps as fast as possible. It is difficult sometimes when discs have too many scratches or other issues. I would recommend the script starts with a fast mode where it attempts to do all 3 steps as fast as possible meaning to try, trim, and scrape each byte one time. It is generally a waste of time to retry bytes too many times. I recommend no retries for the fast mode. You could have a slow mode activate only after every byte on a disc is tried, trimmed, and scraped just only one time. Fast mode should try to do all 3 steps as fast as possible one attempt on each byte before moving to a slow mode. Remember not to eject the disc. The script should run forever until 100% is rescued. Your script might be working on this other disc. But it does seem the ipos and opos says 4482 MB for some of the rounds. But some rounds says 4485 MB. I am mostly or only seeing the script alternate between 4482 MB one round to 4485 MB in the next round to back to 4482 MB in the next round and so on in that loop. I do not know if it is going to the same exact spots each time or to different spots in the general areas of 4482 MB and 4485 MB on the disc. Round 1: the non-tried: 160694 kB. Round 24: non-tried: 160694 kB. Your script seems to try to nudge the hardware when it gets stuck, I am not sure if that is helping or hurting. Off to night church, 06:30 PM. I was on Twitter X while Brian sermon. Mom finally found her rectangle pan on the kitchen floor, I said I could have found it I was alone without her hovering. Dinner: 08:11 PM. Dishes. Mom says Tracker is Lone Ranger. Scanning. Food log: Breakfast: 2 tangerines, coffee, oatmeal, 10:08 AM. Lunch: potatoes on onions on beef beans soup was hot and amazing, 02:31 PM. Coffee. Dinner: yogurt tomato garlic salad in blue plastic bowl, 08:11 PM.