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. I went to bed at 4 AM. Woke up at 8 AM due to a headache from my infected ears which I got from my nose I got from my cold, resurrected the wood stove fire for an hour while mom told me random news related stuff as she usually does off her phone. Back to bed until 01:10 PM. Added another log to the stove. Breakfast: 01:24 PM. Write your script even better. Make it go slower and slower per round at the very end after it exhausted everything else. It should be as fast as possible at the beginning as it does the trying mode via all options like forward, backward, and all combinations of skipping/jumping bytes too at first in larger and smaller numbers starting with the largest numbers possible. If it was possible to skip 1 TB or 1 GB or whatever the biggest numbers could be. You could try different block sizes if that might help at all. You could perhaps add something in the script to try different block sizes to see if that might work. It's critical to go as fast as possible via the trying mode which should not be round dependent meaning as many or as little rounds as it takes to quickly try all the bytes. Same thing for the trimming mode and then the scraping mode. The script should quickly try all the bytes and then quickly trim all the bytes and then quickly scrape all the bytes. I mean it should try to quickly go through all of that. After that, it could try to go through all the modes again but slower. Think of it like a video game, the script should play all the levels of bytes of the floppy disk at least once through the the three or more modes as fast as possible to try, trim, and scrape. But it will miss some. Perhaps it could go back and then try, trim, and scrape again but instead of the easy mode for the levels or rounds, it is medium or less easy. Gradually, it should get harder and harder. Eventually it should get to harder modes. Put in the script infinite levels or infinite modes where it continues to get harder and harder every time it tries to go through the remaining blocks and bytes that have not yet been rescued by ddrescue. Here is an example of what I am seeing below, it is still not gradually getting harder and harder or slower and slower per round. Yes, you can add a dmesg to check to make sure floppy is still connected like you said. As a last resort at the very end when the script exhausted all options, modes, levels, etc, the script should increase the levels indefinitely to get harder and harder or slower and slower. For example, try to get the script to copy smaller parts. Look at the blocks, clusters, systems, jumps, sectors, bytes, bits, skip sizes, jump sizes, all other variables, numbers, sizes, sections, and more, etc. In other words for example, if it is trying to read 10 bytes for a while, then next time it should try to read only 9 bytes or 5 bytes or clusters or sectors or other things. After that, 4 bytes. After that, 3 bytes. Those are only examples as I don't know the exact numbers but the idea is it should gradually try to get slower and slower. Your script does not seem to continue to get harder and harder. After your chaos mode should be just an escalation mode where any and all of the numbers get smaller and smaller so ddrescue can try to grind at smaller parts. Try to make it continue to get smaller and smaller indefinitely. Lunch: 02:41 PM. The grind levels seem to eventually stop working. You can see this particular floppy disk only has 512 bytes that was not yet rescued. Search the Internet for all the ways to try to get the remaining bytes. It seems ddrescue is not slowing down like it would when I was copying DVDs. You should try to remove the skipping mechanism for the hardest of levels at the very end, especially if there is only 512 bytes left on a disk. The light to the floppy drive was off at the end, there was no more floppy drive noises. I would prefer to perhaps let ddrescue grind in extended rounds at the very end if that is possible, especially if there is only 512 bytes left or the smallest numbers possible after the faster modes are exhausted. Try to make the grinding levels eventually extend each round to perhaps last a second longer than the previous round where it gradually gets slower and harder indefinitely and infinitely where it gradually gets harder and harder where the rounds might eventually and slowly extend to maybe even an hour per round or a thousand hours per round but only if it gradually and slowly gets there while trying all options as it slowly tries to extend each round so each round would eventually get like just one second longer than the previous round. Make the breaks/timeouts/rests between rounds zero seconds if the rounds are under five minutes. Make the script tries to quickly do 3 things: first, try all the bytes. Second, trim all the bytes. Third, scrape all the bytes. But it might not try, trim, or scrape every byte the first time. Therefore, it could try to do those 3 things again using different methods like backwards and other methods. You should try to exhaust the fast mode where it tries all combinations of trying to do those three things via all possible ways but at the fastest speeds and fastest quickest rounds possible. A harder mode would be to try to do those 3 things but a bit slower or harder to try to capture the remaining bytes. It should continue to scale up or get harder and slower. Also study the sample output as you can see the rests continues to get bigger per round but there should be no resting for under five minutes. Make sure everything else from previous scripts that should be there are still there. Shower, 04:30 PM. Fix the script, add a cap/limit to retries to 2 at the end of the infinite grounding phase meaning I want the rounds to get longer but not the retries. During this final phase or highest level, the script should continue making each round longer and longer per round for 200 rounds or two hours of rounds and if not a single new byte is rescued after that, then you should remove the timeout limit to let ddrescue extend rounds as long as it wants to go. Perhaps the script should try to check on the status after five hours to see if ddrescue and the drive are both still active and the script should attempt to do CPR to resurrect it if it appears to be idle. But if it is not idle or stuck or whatever, perhaps the script could let ddrescue continue trying. Night church. But when the guest speaker started speaking in tongues and the music started, mom wanted to go. We filled up around 5 gallons for 20 bucks for the car at Arco near Walmart around 08:30 PM. Resurrected the fire. Dinner: 08:40 PM. Please fix the script. Gemini failed big time. AI often fails with code. I have studied AI for years. AI has blind spots where it is too lazy where it just spits code out without researching. AI will make bad assumptions often which leads to big mistakes. Gemini should remember this or else millions of people will stop using Gemini. Check to see if ddrescue can copy from the floppy drive regardless if the floppy is mounted or not. Gemini failed. I asked Gemini many times to fix problems but Gemini failed many times. The script might be okay, one issue might be that this floppy disk only has 512 bytes not rescued stuck in the bad sector as it was tried, trimmed, scrapped, but not rescued. In the Terminal, some of the longer rounds were around two minutes long but some were shorter. I was hoping to try to extend the rounds. I do not know if it is possible to extend rounds if there is only 512 bytes remaining say for example. See if there are any ways to get ddrescue to try harder or longer to do the remaining 512 bytes. Update the floppy script to make sure it can work with any floppy disk of any stage whether for the first time at 0% or even 99% like my current disk at 512 bytes remaining, I want to be able to reuse the script for new and old disks alike. I sometimes like to go back to older disks I already tried copying. I want to try to continue copying with the script. Make sure this script can work in any situation for any floppy disk of various formats and sizes. Make sure the script is flexible and adaptable enough for anything, for surprises as some of the floppy disks are from like the 1990s or are pretty old of various formats and what not. For the last mile, see if you can slow down the reading speed to 1 byte or 1 bit per second or per minute or per hour meaning as slow as possible, see if you can skip the skipping/jumping, see if there are ways to extend rounds during the last mile to grind longer or differently or harder or additional options of tactics. See if I can turn the drive sideways to help copy or other options. Update the script to make sure the script does everything we have already talked about in this thread like going as fast as possible in tier 1 and to gradually level up per tier. See if you can have additional tiers to make sure it gradually levels up one step at a time to gradually try more challenging tactics that might extend each round but make sure it is not round dependent but tier or level or step dependent. Adapt the rescue_floppy sh script file into the dvd recovery file. One of the issues is the dvd script may have made some mistakes. For example, when I put a DVD video disc into my drive plugged into my powered hub into my Ubuntu ASUS laptop, the script ended up retrying bytes that were already tried. It should have been clear from the map or log file that all the bytes of the disc were tried. I was already on the trimming tier/step/level/whatever you want to call it. Make sure the disc script can work for new and old discs alike so I can reuse the script as I like to retry discs I already started trying to copy. Make sure the disc script can do all the things I want to to do including trying to quickly try, trim, and scrape as fast as possible in earlier stages and to then to spend more time trying, trimming, scraping at later steps/stages/tiers/levels/whatever you want to call it, but it should not be round dependent meaning it could take as little or as many rounds as possible. But make sure it gradually gets harder and harder. I want the script to run forever and ever for weeks or years. But I want to make sure it can go as fast as possible at first and the gradually slower and slower. You broke the code of the script. The name of the sh file is dvd_recovery.sh and the the name of the image file I create using this is named dvd.iso as seen in the script file. I manually move files in and out of the folder meaning do not come up with new names for the files. Just make sure I can reuse the script again and again. Also, I sometimes use this disc script to try to copy all kinds of discs, DVDs, CDs, music CDs, data CDs, unfinalized DVDs, home video DVDs, a wide variety. Food log: Breakfast: orange, oatmeal, 01:24 PM. Lunch: noodle vegetables soup, 02:41 PM. Dinner: homemade bread with butter, raspberry yogurt, 08:40 PM. Tea. 2026-03-14 - Saturday - 11:34 PM - Thao-102 - SAT Reading 26-28. I mentioned the snow, wood stove. She mentioned she likes the sunshine in the rain.

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. The longer a round, the longer a timeout should be generally. One of the problems is I see 200+ rounds where each one is generally around 2 minutes each. But then the timeouts gradually get longer. I want to quickly try every byte on a disc. But after 200+ rounds, that failed. I want to try each byte and then trim and then scrape. The script should do rounds as fast as possible. But rounds should not be dependent on any of the three steps ddrescue has of trying, trimming, and scraping. In other words, the script should try to finish the trying process regardless of how many rounds it might take as opposed to be commanded to only do the trying for a certain numbers of rounds. If you use say Algebra for example or anything, the trying process or trying step could be the A variable, trimming could be B, scraping could be C. Write the best script based on the script you already wrote me to make sure it tries to go through each rounds as fast as possible while it is trying each byte. The shorter a round, then the shorter the break/timeout. Regardless of how many rounds it takes, it should try as many things as possible to simply try every byte before going to the trimming step and then the scraping step. So, whether it takes say 1 round or 500 rounds to try each byte, it should try a variety of tactics to try each byte of a disc. The trying only rounds should probably be as fast as possible and the faster the round, then the faster the break/timeout between rounds. The longer the round, the longer the break. Try to come up with a number of tactics for trying to quickly go through the trying process regardless if it might be 1 round or a thousand rounds. Same thing for trimming and scraping too, they should also be as many rounds as possible. Try to trim as fast as possible no matter how many rounds it might take. Same thing with scraping, as many rounds as possible. Whether it is trying, trimming, scraping, etc, it should start with trying as fast as possible via all tactics and more. And then it should gradually get slower and slower or try harder and harder. And later on after it tries everything, after it is done trying, trimming, and scraping every byte, then it should try all combinations of random tactics and methods randomly and to perhaps stick to whatever works or to move on whenever it is not working, it start trying all tactics as fast as possible and then gradually get longer and longer and harder and harder and random tactics and more after it has tried all other options first. Study the following. Add a formula to the jumper tactic where it starts with jumping as far as possible. You mentioned jumping say 5MB ahead but you should consider a higher number than just 5MB if possible. In other words, the formula should be to start off jumping the farthest possible at first in earlier rounds if that might help in finding a good read. The formula should not be dependent on the rounds themselves but instead should try first to jump the maximum it can. After that, perhaps it should try jumping to random points. After that, it should gradually jump a little less each time until it is only jumping 5 MB or less even. It should go back and forth between jumping chronologically and jumping to random spots or points. Also, consider making the resting shorter if the rounds are under ten minutes each but then perhaps make the resting/timeouts a little bit longer after a number of rounds. Regardless of how long or short rounds are, rests could be a little longer after say every large amounts of rounds be it one long hour-long round or perhaps 60 one minute each rounds. Make sure to keep that cap you have where the resting cannot be too long. I say that resting should generally be shorter. You have the break proportioned to be a half of the round meaning if the round was one minute long, then the rest/break/timeout would be 30 seconds but I suggest the rest should perhaps be a tenth of the round meaning 10 seconds instead of 30 seconds of a one minute round. But then after a number of minutes or hours, then perhaps you should add extra time to the rests. Look for the science of what lasers can do. Try to reduce the resting period as much as you can without risking breaking the laser or something. I would suggest if a round is under 5 minutes, then the resting period should probably generally be as short as possible. And then under ten minutes, rests can be a little longer. Gradually, rests can get longer and longer based on if the rounds are longer but I suggest keeping a cap like you did to rests being not longer than ten minutes per rest or whatever is recommended. I would suggest rounds under five minutes each should probably have rests that are only five seconds if that is possible or as short as possible. Rounds longer than five minutes, consider rests that are a little longer. Rounds longer than ten minutes, a little longer. And so on and so forth. And then like I said, after a number of minutes or hours, perhaps a little bit longer of a rest for that one time each hour or each every few hours or as few often as possible meaning try to keep the rests to a minimum. For example, try to keep rests only five seconds long per round if possible or as short as possible based on the length of each round but then after a number of minutes or hours or days, have special rests that are extra long but remember not too long every x amount of time to help protect the laser. Write the best script ever based on the script you already wrote. Study this rescue_floppy .sh file script you wrote me for my Ubuntu ASUS laptop. I have a hard floppy drive connected through a powered USB hub to my laptop. Your script works but please add more tactics to the script. Borrow as much as you can from the dvd_recovery .sh script file as much as you can to adapt that with the floppy script. You wrote both scripts. Please try to adapt as much as you can from the dvd script into the floppy script. I want to increase the strategies and everything for the floppy script to start off as fast as possible and to gradually try tougher tactics. Try to adopt everything from the dvd script into the floppy script if that is possible. Also consider adding additional things. I am currently trying to copy a floppy disk. study internal SATA Panasonic DVD Super Multi, date code J1050, Rev 7.01, model number UJ8A0, manufactured April 2011, HW 1.0 FW 1.51. Class Lazer Product. I went to bed at 4:30 AM. Woke up at 12:10 PM. Breakfast: 12:29 PM. Snow. Wood stove. Lunch: 01:54 PM. Stove continues. Snowed until like 5 PM, like 2 PM. Dinner: 06:16 PM. Dishes. Food log: Breakfast: orange, 12:29 PM. Lunch: hot carrot rice soup was great, 01:54 PM. Dinner: raspberry yogurt which mom made yesterday in a blue mug, 06:16 PM. Rice, 07:18 PM. Meat, 09:00 PM. Rest of the nuts from that small Fred Meyers metal can. Tea. 2026-03-13 - Friday - 10:30 AM - JoJo-329 - he wrote an Climate Change. Agriculture: farming the ground. Saline. Barron. Kohlrabi: cabbage. Construction: building. Dawn. Curiosity. Write about dogs or fashion or qualities. 2026-03-13 - Friday - 11:30 AM - Thao-101 - SAT Reading 23-25. Soccer school matches recap.