Just open MAP file located in that folder as an ASCII text. You can verify original RT resources usage and easily find parts of original RTMUI localization engine in “Help” folder. Those things physically cannot be inside in-house project. #Evga precision x osd text size driverRTCore driver loader messages, RivaTuner Task Scheduler Helper loader messages (“Failed to load RTTSH.dll”) and many more. RivaTuner’s USF skin compiler/decompiler messages (“Failed to decompile %s skin”, “%s skin has been successfully decompiled” etc.), messages related to specific RivaTuner core components, e.g. There are traces very specific to RT core, e.g. For example in 5.0.0.16 (standalone version) it is located in close to 1E2xxx offset. This way you’ll easily locate the string table, which belongs to original RivaTuner core with no doubts. After opening it simply do a simple search for “RivaTuner” text (once again, in UNICODE). I use FAR) and view it as UNICODE (all string tables use UNICODE encoding). You can easily view this application in any binary file viewer (e.g. All string tables are located inside PrecisionX.exe. I do hope it is just a question of skills.Īnyway, you can easily replicate the claims using the following simple steps: I don’t know why the binary analysis is applied to DLLs when I more than explicitly said that those things were traced inside EXE. I don't know how can a programmer misunderstand "string table" term and call it "Visual Studio 2008 IDE output of compilation". Click to expand.I don’t know how it is possible for programmer with at least a bit of reverse engineering experience to be unable to replicate the claims.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |