FILE OPEN ERROR MESSAGES
What Could Be Causing The File Open Error Messages
When you open a file in PE Explorer, you may receive one of these error messages.
1. Errors detected! Opening file in SAFE MODE.
The modification of resources is locked if the file has Import, Delay Import, or Export sections following the Resource section. It is also locked if the section contains other data (besides resources) present in the Data Directory. The exception is Debug Info since this information does not affect the program functionality. In the other cases PE Explorer adjusts all offsets in such a manner that the access to the Certificate Table and Debug Info remains correct and the given information is not lost.
If opening a file produces an error, PE Explorer opens that file in Safe mode. While in Safe mode, the data that caused the error cannot be operated on. This does not guarantee that the excluded file data is error free, but in many cases allows you to work with damaged files (e.g. compressed files).
PE Explorer displays lines of messages in the bottom log window as follows:
Most likely, the executable file has been compressed with one of a large number of packers to appear smaller. Since PE Explorer detects and automatically unpacks only files compressed with UPX, Upack and NsPack, you have to go through the trouble of manually unpacking this compressed exe before you can view or change it.
Another reason may be that the file has been protected from reverse engineering, analysis, modifications, and cracking.
This is not viewed as a bug. We are not going to defeat the security attempts of other software authors. Plus we cannot support decompressing few hundred packers and protectors available on public.
2. Error: This is an NE Executable. Not supported!
Our software works with 32-bit PE files only. An NE (short for "New Executable") file is a 16-bit application intended to run on ancient Windows 3 versions. The other notable executable types that run on MS platforms are "MZ" (DOS), "NE" and "LE" - those 16-bit formats are all obsolete.
We have no intention of supporting 16-bit files. After all, "PE" in PE Explorer stands for "Portable Executable". We would name it "NE Explorer" if it could work with 16-bit NE files.
3. Error: This is NOT an EXE or DLL File
PE Explorer does not care about a particular file extension, it doesn't make any difference whether it is .exe or .txt. You can rename your executable file with any file extension or even leave it without any extension: when opening a file, PE Explorer reads the PE format identifier in the file header within the file rather than file extensions.
With all of that being said, if PE Explorer says your file is NOT a valid executable file, this is true.
IF YOU WANT TO VIEW AND EDIT THE RAW DATA CONTENTS OF A FILE:
Then you need a binary hex editor: FlexHex editor. Use it for viewing and editing the raw data contents of files, inspecting binary output, examining the structure of proprietary closed-format data files or old data in unknown formats, quick fixing executable or data files, creating binary files for test runs, and more.