Hex Editor Neo supports several documents to be viewed and edited in its environment. All supported document types are listed below.
The first and most commonly used document type is a file. Hex Editor Neo allows you to edit any file for which you have Modify access and allows you to view the contents of any file for which you have a Read access. In addition, full support for NTFS alternate data streams is provided.
Starting from version 6.12, Hex Editor Neo provides a way to open files for which you normally receive “Sharing Violation” error.
Hex Editor Neo has native support for Intel Hex and Motorola S-Records encoded binary files. It automatically decodes these files when the user opens them in the editor using the File » Open » Open File… or File » Open » Open Hex… commands.
When the user saves changes made to the HEX files, the editor automatically saves the file using the original format.
Hex Editor Neo normally locks opened files, granting only Read access to other processes. The lock is held until a file is closed, preventing other applications from making modifications to a file. In addition, if the file is already opened by another application, Hex Editor Neo may fail to open a file if it fails to install a lock.
While this scheme allows an editor to work with files of virtually any size in a very effective way, it sometimes may be convenient to work with a file in a shared mode.
Starting from version 4.85 Hex Editor Neo supports opening files in shared mode.
Hex Editor Neo allows you to view or edit contents of any mounted volume, or logical disk. Hex Editor Neo is also able to open volumes that do not have associated drive letters, that is volumes, only mounted to directory on another volume.
Starting from version 6.12, Hex Editor Neo allows you to create and open volume snapshots.
In addition to volume editing, direct access to physical disk is provided by the Hex Editor Neo. Thus, you can get access to disk's partition table, boot sector and so on.
With Hex Editor Neo you can view and modify the virtual memory of any running process, provided you are granted required rights. The editor gives you detailed representation of the edited process memory space.
Each opened document is represented by individual scripting object that implements the IDocument interface.