[Simple]

The software provided and the procedures proposed are intended for personal, educational and experimental use to install DiagBox 8.xx related updates. I hold no responsibility for any illegal or improper usage. Carry out this procedure at your own risk.

APP_Update_847-850.exe update should only be attempted if you have a working DiagBox v07.847.

Link is provided in the attachment for "APP_Update_847-850.exe". This is intended to update Lexia and PP2000 components of DiagBox 8.47 to 8.50. The versions of Lexia and PP2000 will remain 500.74 and 600.80 respectively.

Procedure:
1- Ensure you have a backup copy of the file "C:\AWRoot\bin\fi\APPDIAG.SYS" before you start.
2- Download and execute the appropriate file for your own setup. The process will copy all necessary files to the updt folder, it will then automatically kill all associated processes to enable overwriting without conflicts.
3- Run DiagBox to start the update process and wait until DiagBox is operational. Close DiagBox and restart your computer to ensure all processes are running.

Done..! you may run DiagBox as usual.. Notice that DiagBox version will change to 07.850 after the update..

Have fun!

Lexia language is set to English and PP2000 to french, if you wish to change them, edit the DICO.TXT file in the EXE folders of LEXIA or OUTILREP (PP2000) and replace "GB" with "FR" or vise versa. Full instructions here:

http://cartechnology.co.uk/showthread.php?tid=11087

P.S. DiagBox has been running on Firmware 4.3.5 since 8.45.

Regards, Simple.

[kmaverick]

All installed and Working / Tested on a Pug 208 2012.

Still no Expert 4 - 66 plate - coverage

[pieman64]

What hardware do you guys recommend to accompany this software?

Do you have a link for a supplier of the required hardware at a sensible price?

[kmaverick]

What hardware do you guys recommend to accompany this software?

Do you have a link for a supplier of the required hardware at a sensible price?

Hi,

I use just a dell latitude 3380 with a XP partition and I also run it on a PC with a windows xp VM using VMware 12 free.

This software doesn't need anything special to run. Just need to follow scarymistake and simples instructions to get the latest version working.

It should work with a Windows 7 32 bit laptop as well but i have never tried it.

hope this help's

[Simple]

If you are inquiring about the OBDII hardware, it is called XS Evolution VCI or Lexia 3.
You can obtain this from Ebay or Aliexpress (it may be available on this site), but ensure you get a Full Chip revision C clone.

If you are inquiring about the laptop, any recent laptop should do, but you need a 32 bit Windows for DiagBox to run properly.

I have a capable Intel i7 (Kaby Lake) with 16 GB RAM running Windows 10 RS2 x64. So I use both VMware Workstation and VirtualBox 5.1.xx. running 32 bit Windows XP, Windows 7 and Windows 10. Windows XP is swift and need very few resources.

Both VMware and VirtualBox are good and have the advantage over running the software directly on the laptop, like being portable (moving the installation to another laptop) and taking snapshots (freezing current status, in case of corruption). However, VirtalBox is faster and can take videos. Also, if you have an SSD, DiagBox 7.01 installation on XP could take less than 5 minutes.

P.S. If your laptop is NOT fast, but you have access to a fast Desktop, you can install DiagBox/Windows XP or 7/VirtualBox or VMware on the DeskTop, then copy/move the installed Virtual Machine folder to the laptop. choose Moved NOT Copied if challenged by VM software.

If you intend to use VirtualBox, do NOT use 5.1.24, it has a couple of bad bugs that has been fixed in 5.1.25-117130 beta, so install 5.1.22, the beta or wait for 5.1.26, which should come anytime.. Also use Administrator's CMD to insert a System Serial in the VM like this:
C:\Program Files\Oracle\VirtualBox>VBoxManage setextradata "Your VM" "VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial" "DIAGBOX7"

If you use VMware Workstation and you experience freezing, it is advisable to use this line in the VMX file:
mainMem.useNamedFile = "FALSE"
It will disable memory swap files .vmem files.

You may also wish to use these (some are standard setting on recent versions):
Remark: Disable memory trimming:
MemTrimRate = "0"
Remark: Disable page sharing:
sched.mem.pshare.enable = "FALSE"
Remark: Disable scale down of memory allocation:
MemAllowAutoScaleDown = "FALSE"
Remark: Memory allocation configuration:
prefvmx.useRecommendedLockedMemSize = "TRUE"
prefvmx.minVmMemPct = "100" (optional)

[pieman64]

Yes it's the ODB2 hardware I am interested in.

So the common chip Diagbox $20 will not do key copying, right?

Needs to be full chip for $50+, right?

[Simple]

This looks like mine (I am not sure if I am not allowed to provide these links as examples):
https://www.aliexpress.com/item/Lexia-3-...cb032075dc

Or this, notice the different (metal cylinder) oscillator:

https://www.aliexpress.com/item/Free-shi...cb032075dc

However, you need to ensure what you receive is what's in the pictures.

[DTech]

And in both cases you will need to rework your board and program it with a "good" sn and for that you can see Titoun's tutorial.

[pieman64]

@DTech and others I found threads created by @titoun but I couldn't see which one might relate to reworking the board.

A link to the @titoun tutorial would be very helpful.

Does this mean I need to get out the soldering iron when the hardware arrives, surely not?

[Simple]

I bought my device end of 2014 and have not changed the serial, it has been working fine. I am aware that people who bought Revision B (old clones) were blocked in DiagBox v5.30 and had to update their Firmware if they needed to use DiagBox v5.30+, v6, v7 and/or v8.

Both listed examples are Revision C and unless one receives a bad quality product, they should work from the box; like mine. I am not aware of cases who bought Revision C needing to change firmware serial!!..

I understand that if PSA decides to pick on clone users, they will release DiagBox updates that will block clones, but it has not happened and I don't see that happening for many reasons.

Is there any other reason to why would you need a unique serial??

May be some other users can share their experiences in a thread dedicated for this subject.