so the thing about an OS like windows that makes this not work as well as it does on something like a WII game is that an OS is usually going to be a lot smarter and have a lot more checks in place because the stakes are a lot higher if something goes wrong. If your WII game is broken and writes some garbage data to the storage that fucks everything up, it's a WII so it's not that big a deal. If windows is broken and writes some garbage data that fucks everything up, then someone has potentially lost a lot of very important data they may have had on the computer. And when your OS is being used by almost everyone, government agencies included, avoiding a scenario where shit gets deleted because of your shoddy code is REALLY IMPORTANT. So even windows 95, for all the flaws that it has, will make it really hard to run in a corrupt state for this reason. Admittedly you might have better luck with windows 3.1 which is a bit more crude. Regardless though, this is still really interesting to watch!
im trying to work on an automated tool right now with a few friends but for this video and the one i did on windows xp on my other channel, i used the hxd editor the hxd editor lets you fill selections with random garbage data which is how i managed to mess with windows 95 and xp
@@ignacyk3203 i used a built-in tool that filled my selections with random bytes, effectively rendering all the data and sectors in that specific disk unreadable
intro is gold
thank you :)
so the thing about an OS like windows that makes this not work as well as it does on something like a WII game is that an OS is usually going to be a lot smarter and have a lot more checks in place because the stakes are a lot higher if something goes wrong.
If your WII game is broken and writes some garbage data to the storage that fucks everything up, it's a WII so it's not that big a deal.
If windows is broken and writes some garbage data that fucks everything up, then someone has potentially lost a lot of very important data they may have had on the computer. And when your OS is being used by almost everyone, government agencies included, avoiding a scenario where shit gets deleted because of your shoddy code is REALLY IMPORTANT.
So even windows 95, for all the flaws that it has, will make it really hard to run in a corrupt state for this reason. Admittedly you might have better luck with windows 3.1 which is a bit more crude.
Regardless though, this is still really interesting to watch!
you have a point, also thank you!!!!!!!
aw man now my os with my favorite startup is corrupted😢
Real Time Corruptor could also have some interesting effects, jtlyk...
oh yeah i forgot that rtc has a dosbox port...... >:) mueheheheheh.......
@@pooalgaming ... that too. I was thinking with the HDD image but that's somehow more sinister.
i have to ask; how did you do this? pure deleting regestries or an automated tool?
im trying to work on an automated tool right now with a few friends but for this video and the one i did on windows xp on my other channel, i used the hxd editor
the hxd editor lets you fill selections with random garbage data which is how i managed to mess with windows 95 and xp
@@pooalgaming would you happen to have any information how to do this? is it just using hxd editor on the virtual hard drive or?
@@ha_ades yeah thats basically it
@@pooalgaming How did you modify it, did you type garbage or used some kind of tool in the software
@@ignacyk3203 i used a built-in tool that filled my selections with random bytes, effectively rendering all the data and sectors in that specific disk unreadable
nice vid! +1 sub!
It didnt like it much
meh.. i dont like curse words change the video as not swearing