This multi-part blog series is discussing an undocumented feature of Windows: instrumentation callbacks (ICs).
In part 4 we cover ICs from a more theoretical standpoint. Mainly restrictions on unsetting them, how set ICs can be detected and how new ones can be prevented from being set.
This multi-part blog series is discussing an undocumented feature of Windows: instrumentation callbacks (ICs).
In part 4 we cover ICs from a more theoretical standpoint. Mainly restrictions on unsetting them, how set ICs can be detected and how new ones can be prevented from being set.
Does anybody have some experience with 'hacking' Stratasys (F900) printers?
I'm specifically looking for the ability to use 3rd party filaments without the OpenAM software. (Sends stuff to their server and costs too much)
So one probably needs to customize the profiles in the Insight slicer software and maybe even something in the printer software itself?
:BoostOK:
I've managed to print "Hello, world!" on my 4610-TG3 from some Rust code running on an ESP32-C6. I've also dumped the opening screens from Zork to get a feel for where the project's going.
Hi everyone. I don't understand the following #ESP32#Xtensa assembly code and looking for explanations. I am not sure the Ghidra decompiler is doing the right thing here. Having trouble understanding the loop mnemonic here (loop a5, LAB_400f7cd4). a5 holds the loop count for the zero overhead loop. But what does the label hold? The end, i.e. where to continue after all iterations? Where does the loop begin and where is the end of an iteration? I am confused by the docs. #reverseEngineering
#RealityCheck dives into the case of an officer of public works in the former #SovietUnion named Valerij Černohajev, who wrote, in very specific terms, a manuscript describing a #UFO.
his daughter & her husband have translated the document & ask any expert to peer review it so it can be scientifically collaborated & verified.
here's the link:
"decomp2dbg aims to shorten the gap of context switching between decompiler and debugger by introducing a generic API for decompiler-to-debugger symbol syncing."
Oh my, it is #nakeddiefriday already. Time flies when you're busy, I guess!
This is one of them older decaps, apparently a L6284 by ST. I am not sure about the exact function of this one, but it does look like a driver of some sort. Literally half the die (on the right) is taken by the output driver circuitry. The rest is populated by a variety of analog and digital IP, a lot of it quite interesting in structure. The digital control unit sits right in the centre, a blob of dense standard cell circuitry. I suggest taking some time to explore the die!