@k3nny

Thank you very much for the report. I tested it on 5-6 systems (Windows XP, 7, 8.1) but I never saw this missing dependency error. I have uploaded v0.9.9 r2 to address this issue. I also included a Changelog.txt file now.

The ME is not recognized properly in the picture. It's showing it as Partial Update which makes no sense for an SPI/BIOS image. What image did you load exactly? I downloaded the latest Dell Latitude E6430 A16 BIOS and this is what I got:

@gpvecchi

Thank you for your feedback regarding Admin privileges not working. I decided to convert the .bat file to .exe and add an Administrator manifest instead. This should fix any such issue and work for Windows XP, Vista, 7, 8.x, 10 etc operating systems. The new main file is ME_Analyzer_Run.exe and it replaced ME_Analyzer.bat script. For the record, administrator privileges are needed for ME_Utility_Cut to work since it needs to access the HECI driver.

Can you guys let me know if the Driver/Firmware reporting works properly? It does on my system.

@lordkag

ME Analyzer should tell you right away if you have anything newer via the drag&drop feature. Thank you for letting me know about the outdated libraries, I didn't even think of that for some weird reason. ME Analyzer was built with Python 3.4.2 and that's why the python interpreter dll was outdated. I updated to 3.4.3 now. The Msvcr100.dll library is only needed for Windows XP as shown by various operating system tests before release. Initially I was planning to release v1.0.0 but I went with v0.9.9 as a beta in order to fix any missing python dependencies based on user feedback.

Update:

ME Analyzer v0.9.9 r3

ME Analyzer & ME Utility Cut were rebuilt using Python 3.4.3
Fixed bug where Admin privileges were not given (ME_Analyzer.bat --> ME_Analyzer_Run.exe)
Fixed all missing dependency errors (all cpXXX.py files now included)
Updated Python Interpreter & Visual C DLL libraries to latest versions
Release version (rX) is now shown at all program headers

Zitat von lordkag im Beitrag #9

---

Just a quick question, to confirm I understood this right: the "Updated: Yes/No" field reports if you have the latest version of that firmware branch, while the yellow "Note, .. you have a rare firmware ..." is the one that tell us to report the firmware for database inclusion?

---

Zitat von lordkag im Beitrag #9

---

If someone tries to run Me Analyzer -> I option on a system with no ME firmware/driver, the script reports an error in ME_Utility_Cut.py, line 296, about HECI interface not present. Maybe wrap that one in a try - except? This only with the old .bat file, because the new exe displays nothing at all, not even that error message.

---

@lordkag

At the ME thread, you asked me this:

Zitat

---

When you say you want to release an exe, does this mean you already tested this and you were happy with the result? Because I tried to use py2exe from SVN and resulted in a few files next to the exe and the pack was 15-20MB, so not much of a help. The alternative is not better, when you think you have to write a tutorial about installing a specific version of python, installing to path, installing pip, installing colorama and the rest of the dependencies.

---

Since it's related to ME Analyzer I decided to reply here now that I have a little more py2exe experience.

The result is satisfactory. This is the process (with py2exe, colorama etc installed):

1. I created two py2exe setup files (one for ME_Analyzer and one for ME_Utility_Cut):



2. I created a batch script that automatically builds the executables by calling the two py2exe setup files:



3. The .exe icon as well as the actual python files for ME_Analyzer and ME_Utility Cut need to be at the same folder:

Note: Py2exe does not find Colorama automatically so you need to copy-paste it's folder at the same folder which for me is Python34 root.



4. The dist folder holds Py2exe's output which for me is two .exe files and one .zip dependency package:

Note: It's ONE .zip dependency package. Normally you get one .zip file for every .exe but after research I saw that ME_Analyzer's .zip package "includes" the Utility's one so both py2exe setup scripts point to ME_Analyzer.zip file.



5. As you can see the .zip file py2exe creates by default is huge. This is the boring/tiring part but thankfully it needs to be done once usually. Basically remove everything from the zip, run the .exe and add one-by-one the files that are missing (+ all cpXXX encoding dependencies). The end result is this:

Note: As you can see the "cut" .zip file is now 320KB which is a lot smaller than the original 2.75MB one.



6. To call the python .exe files I have created some batch scripts and to convert them to .exe (Run only, not Drop) I use Bat to Exe Converter:



7. Then I add some other dependences like Msvcr100.dll for Windows XP, Database, Batch files etc and the Release version is ready:

Zitat von lordkag im Beitrag #14

---

Can you read minds? What I'm thinking right now? It is strange that I actually thought of PM you about this, just to have the basics, in case I will someday decide to make an exe from .py script.

---