This guide explains installing and running DiagBox versions 7.02 and 7.57 in a VMware virtual machine, and updating/using the “MHH Auto — Page 1” functionality (commonly referenced in the context of PSA/Peugeot/Citroën diagnostic software). Assumptions: you have a valid DiagBox license and installation files, and basic familiarity with VMware and Windows VMs.
: This version typically requires a 32-bit environment (like Windows 7 32-bit) to run the older 16-bit Lexia/PP2000 components properly, making the VMware approach essential for users on modern 64-bit Windows 10 or 11 systems. User Perspectives diagbox 702 plus 757 vmware mhh auto page 1 upd
: When VMware asks if you moved or copied the machine, always select "I moved it" to maintain existing hardware IDs and activation. 3. Hardware Interface Connection (Lexia 3 VCI) This guide explains installing and running DiagBox versions
: You must ensure your VMware settings correctly "pass through" the Lexia interface to the guest OS. If the "CAN clip" or Lexia device isn't visible in the VM's device manager, the software won't connect to the car. User Perspectives : When VMware asks if you
If you are using the files found on page 1 of the MHH Auto thread, follow these best practices: "I Moved It" vs. "I Copied It":
To understand the importance of the specific "702 plus 757" configuration, one must first understand the software lineage. For years, PSA vehicles were diagnosed using two distinct interfaces: Lexia for Citroën and PP2000 (Planet 2000) for Peugeot. These were robust, stand-alone applications, but they required separate hardware cables and separate installations. As vehicle electronics became more unified under the PSA umbrella, the need for a consolidated diagnostic platform became apparent. This led to the development of Diagbox, a unified software suite capable of diagnosing both brands.
For vehicles older than 2019, this setup is better than the official dealer tool because it allows "telecoding" (changing BSI options) without an online server check.