Dude this was one of the most entertaining videos that I have watched in ages. Most of the jargon that you were referring to went over my plumber head but the humor was awesome.
So I think that Discord sells our data to Google as well because about a week ago I did the Resistor Mod to Undervolt the CPU and reduce temps and I had to remove the plastic bracket. What you're supposed to do is take the pegs inside the nubs out first not pull the whole nub out in one go. Those pegs keeps the bottom of the nubs from squeezing and becoming loose. Matt here instead decided to pull them straight out, you're not supposed to do that, just take flush cutters and gently grab the peg and pull it out. Don't squeeze too hard or you'll end up cutting the head off. Also don't use pliers as they'll grind the head off and ruin them. What I by discord selling our data is that I didn't look up this video of Matt even though I had seen it before because I was almost out of my daily internet quota that day so I was asking peeps in the XBox Homebrew discord server and someone by the name of Nathan told me to squeeze the bottom of the nub WITHOUT first taking out the peg inside of it. And I told him that's not how it's going to work because of course it won't, you have to pull out the peg inside of the nub then squeeze the bottom of the nub slightly to take them out.
This is actually an incredible achievement and it's fantastic that you have helped keep older systems useable for the future. I think these type of projects mean so much to people with old systems. I recently restored an old 80s xt system and could not have done it without the usb floppy emulators and flash floppy. I have a couple of 90s boxes that I've been fixing up and this project will likely be beneficial to those too.
With a modern screen replacement, you can more than quadruple the battery life of the Nomad. The screen they used had CCFL backlights, which are extremely power intensive especially compared to modern LED-backlit LCD's. That, and not the Genesis itself, was the reason for the Nomad's poor battery life (same goes for the Game Gear).
I mean...with a big enough battery (or more accurately, a lot of little batteries in both series and parallel) you can power anything. I can drive for almost 300 miles on a battery. It just has to be a big battery. (400v in this case).
this video actually motivated me to start tinkering in binary files, for example now im learning about the GBX file used by trackmania and other mania games. it seems pretty cool to me going into the hex editor and actually finding some data which makes sense
Don't edit msi's directly, create a transform file with the same name and the OS will pick it up automatically, or use the msiexec switch for the transform file....smh Also don't delete the if statement, just set it to TRUE
When I first started working on a Department of Energy project in Las Vegas in December 2000, all the computers were still running Windows 95 OSR2 on our network. And every system, contrary to what you might have expected, was rock solid. Never had a BSOD on my system. The reason was that every application installed on any PC was required to be exhaustively tested against all combinations of other software that your group might have on a PC. If anything caused a problem, it was not allowed to be installed on a regular users PC. We did migrate to Windows XP Professional sometime in late 2002. It was a big improvement in terms of network connectivity and security, in spite of all the internal bugs that were present in XP. According to Dave Cutler of Microsoft in his inteview on Dave's Garage channel, his team found thousands of bugs in XP and was not able to fix all of them. Some could only be partially mitigated.
Why so many registry entries? It's the CLSIDs. .NET was originally designed as a successor to COM, as a much easier and more convenient way of writing interoperable code and applications. All of this infrastructure is pretty much there as a compatibility layer to interface "old" COM with "new" COM. Usually COM applications only registered a couple of classes, but .NET was designed with a very public, open interface. You could pretty much run any .NET method from VB6 if you so desired. This was very useful for porting old applications to .NET in parts. And indeed, it _worked_ - there were tons of applications that actually transitioned this way, linking the parts from completely different codebases through COM. Funnily enough, this is what the registry was originally designed for - COM class registrations, and the closely related file associations. It was never meant for some random application to put its configuration or such there. .NET is using the registry right :D As for WinDbg... it was never very user friendly, but it's also very powerful. It takes quite a bit to get over the frustration to the good bits. It was closely related to kernel debugging, so it assumed you are already deep into working on the Windows innards :D And it has an extension for debugging .NET applications - SOS. No idea if you could actually load it in your version of WinDbg, though :D NDPHLPR.VXD? We're in the old 16-bit world, you have to do with 8.3 filenames :P NDP is related to .NET, HLPR is just "helper". Yeah, as useful a name as always :D SSE and its SIMD friends are awesome; it's all about squeezing out everything out of the CPU through having a whole load of complex instructions able to do fairly complex operations on vectorised data. Once you get into the pattern, the instruction mnemonics are decently easy to get around. The trickiest thing is being able to usefully handle all the various possible SIMD operations available on the particular CPU you're running on.
for people who got the error called instat a: to b: i cant remeber but to fix in rufus put ms dot not freedot but I M not sure it will work for ya but for.me itnworks it worked on my crappy dell inspiron3252
