|
|
|
[下载]JEB Decompiler PRO 3.19.1 (May 7, 2020) by PNF Software
JEB Decompiler 3.19.1 Professional Edition by jimmy |
|
|
|
[分享]VisualGDB和VisualKernel的破解
Visual Studio 2013 - Visual Studio 2015 - Windows 10 - VisualGDB version: 5.5.5.3595 ------------------ System.OperationCanceledException ------------------ System.OperationCanceledException: The operation was canceled. at jd1.k() at f03..ctor(DTE c, VisualGDBPackageCommon b, of a) at ri1.p(Boolean a) at VisualGDB.VSPackage.VisualGDBPackageCommon.<RunSynchronousInitializationFromMainThread>b__35_1() at bh1.x(Object b, EventArgs a) trace=[jd1.k:296, f03..ctor:37, ri1.p:441, VisualGDB.VSPackage.VisualGDBPackageCommon.<RunSynchronousInitializationFromMainThread>b__35_1:0, bh1.x:0] |
|
[分享]VisualGDB和VisualKernel的破解
Arduino Settings + Manage Team Settings (VisualGDB-5.5.5.3595 Preview 5 Beta) |
|
[原创]Internet Download Manager 改离线激活
Ali.Dbg Crack == Change Log v17.7 == * Fixed Reg Nag On UpdateMenu
最后于 2020-4-30 22:45
被Alfik编辑
,原因:
|
|
[原创]Internet Download Manager 改离线激活
IDM_6.3x_Crack_v17.6_Ali.Dbg.rar Internet_Download_Manager_Keygen_addhaloka.exe +IDM_Patch_by_The_Hidden
最后于 2020-4-28 21:10
被Alfik编辑
,原因:
|
|
[推荐]VB Decompiler V11.1
VB Decompiler v11.4 has been released (April 5, 2020) What's new in this version: - Support addresses to global variables and objects in fld, fadd, fsub, fmul, fdiv, faddr, fsubr, fmulr, fdivr, faddrp, fsubrp, fmulrp, fdivrp fpu instructions (Native Code) - Getting value from register in fstp fpu instruction (Native Code) - Support pointer to register in fild fpu instruction (Native Code) - Support for fst FPU command (used only for unmanaged .NET code, VB6 use only fstp) - New FPU preprocessor for add, sub, mul and div commands with and without "p" and "r" suffixes (Native Code) - Filtering _adj_fdiv_r and _adj_fdiv_m64 with stack processing (Native Code) - Now you can disable analytic features and parsing prototypes on the fly, without changing options. Just hold "Shift" on the keyboard and start decompilation by pressing "Decompile" button or from recent files list (Analytic features) - Tracing is now works on both: Fast decompilation and Full decompilation modes (Tracing features) - Checkboxes on the main window now can be changed only on "Fast decompilation" mode, because this settings can be used only in fast decompilation mode - Japanese, French and German translations is updated - Search strings in a whole project of the .NET application via "Ctrl" + "F" (.NET) - Processing imports for x64 .NET managed applications - "Find next" button at String references list - Searching new file access APIs (Analytic features) - Searching new volume access APIs (Analytic features) - Searching new internet access APIs (Analytic features) - BugFix: Decompile msvbvmXX.dll functions __vbaR8IntI2, __vbaR8IntI4, rtcDateAdd (Native Code) - Plugin SDK function "VBD_SetActiveTextLine" now works for Decompiler and Disassembler tabs - FRX Viewer updated - BugFix: Processing boolean assignment to property via __vbaLateIdSt, __vbaVarLateMemSt, __vbaLateMemSt in some cases (Native Code) - BugFix: Procedure analyzer and optimizer can incorreclty replace the array variable with array index - BugFix: Processing "MemberRef" and "CustomAttribute" tables (.NET) - BugFix: Search strings in a whole project via "Ctrl" + "F" - BugFix: Issue with resizing panels at main window - BugFix: Processing "imul" assembler command (Native Code) - BugFix: Plugin SDK function "VBD_SetStatusBarText" - BugFix: Fix incorrect Virtual Tables - BugFix: Parsing type of "class" and "valuetype" variables (.NET) - BugFix: Jump history open incorrect tab after jumping from form to code or vice versa VB Decompiler v11.3 has been released (October 6, 2019) What's new in this version: - Support String References for "Fast decompilation" option if "Analyze Prototypes" option is enabled (for VB5/6 files only) - Support local ANSI charsets (include Japanese, Chinese, Korean) in String References, TStringList properties of controls (ListBox, ComboBox, etc) and long string from FRX files in Caption of Label and CommandButton - Database for Forms/Controls recovering is completely refactored - Recover most main properties of DataReports (dsr designer): ClientLeft, ClientTop, ClientWidth, ClientHeight, Caption, StartUpPosition and save properties of all controls to the OleObjectBlob (OLE container with other properties). You can open decompiled UI part of the DataReport in VB6 IDE. - Recover main properties of DataEnvironment files (without internal structure decompilation) - Declare OCX DLLs in Project - Support for some arrays in global variables (Native Code) - BugFix: Show functions with Chinese unicode names - BugFix: Jump to function by clicking address is file has no forms - BugFix: Error while opening VDD database files - BugFix: Freeze saving project with decompiled files with multibyte names (Japanese, Chinese, etc) if name after conversion from Unicode to ANSI contains slashes. VB Decompiler saves files with ANSI names because VB6 IDE is not support files with unicode names. Please note: you can open files with multibyte names using VB6 IDE only on Windows with same ANSI locale) - BugFix: Recent files list is not work on Windows XP with unicode locale - BugFix: Decompile msvbvmXX.dll functions: __vbaI2Cy, __vbaI4Cy - BugFix: Processing version info fields with more than 256 chars - BugFix: Filtering some integer variables as a compiler side variables VB Decompiler v11.2 has been released (June 18, 2019) What's new in this version: - New analytic features for forensics and malware analysts. VB Decompiler can generate a report that contains detailed information about the activity of a decompiled program on a user's computer. Needs additional license. - Support heuristic prototypes for functions and procedures (P-Code) - New German documentation - Slovak translation is updated - Greek translation is updated - Support ReDim for zero length arrays (Native Code) - BugFix: Show pointer to main form as value at argument of procedure (Native Code) - BugFix: Access Violation on parsing incorrect API references (P-Code) - BugFix: Auto-created prototypes replaces named prototypes VB Decompiler v11.1 has been released (March 3, 2019) What's new in this version: - Show events list directly by clicking on any object on the form. After double click on any event - VB Decompiler show decompiled code. After jumping back - VB Decompiler open form on last viewed control (UI Viewer) - Add new types of objects (2 types of Modules and one type of Form) - Show unknown external calls in VTable of dumped files (P-Code) - Open files with fake VB signature (with pointer to out of file) - Filter wrappers to SetMemObj, GetMemVar, PutMemVar, SetMemVar, GetMemEvent, PutMemEvent, SetMemEvent at procedures list (Native Code) - Add to the form header references to used ActiveX objects - Now you can mark/unmark any function/procedure at the tree - New Option "IgnoreCharsConvertions" to disable conversion of the text values in a Forms from local non English language to Unicode (like #0000#0001) - Trying to recovery methods from the Modules of Visual Basic 5.0 files (P-Code) - Analyze bound imports for supporting some features for VB5 applications - BugFix: Freezes on some obfuscated procedures (Native Code) - BugFix: Error on opening some protected/obfuscated files - BugFix: Error on obfuscating Form without controls but with incorrect number of controls - BugFix: UDT search in Sub Main - BugFix: Show "call esi" if esi is unknown function - BugFix: Error if Import Table at end of file and no free space after last name or ordinal - BugFix: Incorrect parsing UserControl property "HitBehavior" - BugFix: If filename contain "&" char then it can't be deleted from recent list |
|
|
|
|
|
[分享]Source Insight 4.0.0096 Patched
https://s3-us-west-2.amazonaws.com/assets.sourceinsight.com/download/v4/release/sourceinsight40113-setup.exe |
|
[推荐] X-ways WinHex 19.8 Specialist License - Keygen by DimitarSerg
dreampsp 感谢楼主分享 不过sr4好像 viewer 文件不全 没有64位版这时候所有的文件都齐全 |
|
[推荐] X-ways WinHex 19.8 Specialist License - Keygen by DimitarSerg
WinHexForensic_crk_xw_forensics_19.9_SR-6 xw_forensics_19.9_SR-6 xw_forensics_20.0_Preview 6 xw_viewer_854_18.04.2020 MPlayer
|
|
CreateFileMapping映射的最大值是多少
Jeffrey Richter, Christophe Nasarre - Windows via C_C++-Microsoft Press (2011).pdf |
|
CreateFileMapping映射的最大值是多少
The main purpose of the CreateFileMapping function is to ensure that enough physical storage is available for the file-mapping object. These two parameters tell the system the maximum size of the file in bytes. Two 32-bit values are required because Windows supports file sizes that can be expressed using a 64-bit value; the dwMaximumSizeHigh parameter specifies the high 32 bits, and the dwMaximumSizeLow parameter specifies the low 32 bits. For files that are less than 4 GB, dwMaximumSizeHigh will always be 0. Using a 64-bit value means that Windows can process files as large as 16 EB (exabytes). If you want to create the file-mapping object so that it reflects the current size of the file, you can pass 0 for both parameters. If you intend only to read from the file or to access the file without changing its size, pass 0 for both parameters. If you intend to append data to the file, you will want to choose a maximum file size that leaves you some breathing room. If the file on disk currently contains 0 bytes, you can't pass two zeros to CreateFileMapping's dwMaximumSizeHigh and dwMaximumSizeLow parameters. Doing so tells the system that you want a file-mapping object with 0 bytes of storage in it. This is an error and CreateFileMapping will return NULL. If you've paid attention so far, you must be thinking that something is terribly wrong here. It's nice that Windows supports files and file-mapping objects that can be anywhere up to 16 EB, but how are you ever going to map a file that big into a 32-bit process' address space, which has a maximum limit of 4 GB (little of which is even usable)? I'll explain how you can accomplish this in the next section. Of course, a 64-bit process has a 16-EB address space so that you can work with much larger file mappings, but a similar limitation still exists if the file is super-big. To really understand how CreateFile and CreateFileMapping work, you should try the following experiment. Take the following code, build it, and then run it in a debugger. As you single-step through each statement, jump to a command shell and execute a dir command on the C:\ directory. Notice the changes that are appearing in the directory as you execute each statement in the debugger. int WINAPI _tWinMain(HINSTANCE, HINSTANCE, PTSTR, int) { // Before executing the line below, C:\ does not have // a file called "MMFTest.Dat" HANDLE hFile = CreateFile(TEXT("C:\\MMFTest.Dat"), GENERIC_READ | GENERIC_WRITE, FILE_SHARE_READ | FILE_SHARE_WRITE, NULL, CREATE_ALWAYS, FILE_ATTRIBUTE_NORMAL, NULL); // Before executing the line below, the MMFTest.Dat // file does exist but has a file size of 0 bytes. HANDLE hFileMap = CreateFileMapping(hFile, NULL, PAGE_READWRITE, 0, 100, NULL);Windows via C/C++, Fifth Edition by Jeffrey Richter and Christophe Nasarre // After executing the line above, the MMFTest.Dat // file has a size of 100 bytes. // Cleanup CloseHandle(hFileMap); CloseHandle(hFile); // When the process terminates, MMFTest.Dat remains // on the disk with a size of 100 bytes. return(0); } If you call CreateFileMapping, passing the PAGE_READWRITE flag, the system checks to make sure that the associated data file on the disk is at least the same size as the size specified in the dwMaximumSizeHigh and dwMaximumSizeLow parameters. If the file is smaller than the specified size, CreateFileMapping makes the file on the disk larger by extending its size. This enlargement is required so that the physical storage will already exist when the file is used later as a memory-mapped file. If the file-mapping object is being created with the PAGE_READONLY or the PAGE_ WRITECOPY flag, the size specified to CreateFileMapping must be no larger than the physical size of the disk file. This is because you won't be able to append any data to the file. The last parameter of CreateFileMapping, pszName, is a zero-terminated string that assigns a name to this file-mapping object. The name is used to share the object with another process. (An example of this is shown later in this chapter. Chapter 3, "Kernel Objects," also discusses kernel object sharing in greater detail.) A memory-mapped data file usually doesn't need to be shared; therefore, this parameter is usually NULL. The system creates the file-mapping object and returns a handle identifying the object back to the calling thread. If the system cannot create the file-mapping object, a NULL handle value is returned. Again, please remember that CreateFile returns INVALID_HANDLE_VALUE (defined as -1) when it fails and CreateFileMapping returns NULL when it fails. Don't get these error values confused.
|