BMW GT1 / DIS / SSS Progman - OBD2 Diagnostic Suite Final

wow this is incredible. do you have setup instructions how to make sure a USB OBD cable is configured to run on sss progman? I cant see any setup instructions for help how to get the USB OBD cable running with it?

bikhs said:

wow this is incredible. do you have setup instructions how to make sure a USB OBD cable is configured to run on sss progman? I cant see any setup instructions for help how to get the USB OBD cable running with it?

Click to expand...

SSS/Progman normally expects an OPS/ICOM/GT1 “diagnostic head” (Ethernet style), so a generic USB OBD (K+DCAN) won’t work directly.
If you want to use your USB cable anyway, you’ll need a DiagHead/OPS-ICOM emulator + DIS-ICOM bridge that makes the VM see a virtual diagnostic head and forwards traffic to EDIABAS.
This resource looks like exactly that: “BMW Diagnostic Head and DIS-ICOM Helper Toolkit

Bin said:

SSS/Progman normally expects an OPS/ICOM/GT1 “diagnostic head” (Ethernet style), so a generic USB OBD (K+DCAN) won’t work directly.
If you want to use your USB cable anyway, you’ll need a DiagHead/OPS-ICOM emulator + DIS-ICOM bridge that makes the VM see a virtual diagnostic head and forwards traffic to EDIABAS.
This resource looks like exactly that: “BMW Diagnostic Head and DIS-ICOM Helper Toolkit

BMW Diagnostic Head and DIS-ICOM Helper Toolkit

16.11.2025

BMW Diagnostic Head Emulator v1.2 with DIS-Icom bridge and ECC EDIABAS tools for GT1, SSS and INPA

• Bin
• diagnostics bmw icom ediabas inpa diagnostic-software bmw-diagnostics
• 🏁 BMW Group – Diagnostics

Transfer.it

transfer.it

Click to expand...

superstar thank you so much!!

nice !

Hello everyone,
I tried to start GT1 DIAG 1.0.OVA on a fairly recent version of VMware Workstation Pro.
Unfortunately, the system takes a very long time to load, and even after 10–20 minutes nothing happens.
There’s just a blinking cursor on the screen.
Am I doing something wrong? Do I need to configure something first?

sebe65 said:

Hello everyone,
I tried to start GT1 DIAG 1.0.OVA on a fairly recent version of VMware Workstation P...

Click to expand...

That's a common issue with these GT1 OVA images. A few things to check:

1. VMware version & compatibility
These VMs were built for older VMware versions. If you're on Workstation 17.x, try changing the hardware compatibility:

• Right-click the VM → Manage → Change Hardware Compatibility
• Try setting it to Workstation 10.x or 12.x
• Make sure the guest OS type is set to Windows XP Professional (32-bit) — that's what GT1/DIS runs on

2. VM settings to check

• RAM: assign 1–2 GB max (these are XP-based, too much RAM can cause issues)
• CPU: 1 processor, 1 core
• Display: disable 3D acceleration
• Network: set to Bridged or Host-only depending on your DiagHead/interface setup
• USB controller: make sure it's present (USB 2.0 / EHCI)

3. BIOS vs EFI
This is the most likely culprit for a blinking cursor that never boots. These old XP images need BIOS firmware, not UEFI/EFI:

• Open the .vmx file in a text editor
• Look for a line like
  Code:

  firmware = "efi"

• Change it to
  Code:

  firmware = "bios"

  or simply remove the line entirely (VMware defaults to BIOS)
• Save and try booting again

4. Disk controller
If the OVA imported with an NVMe or SATA controller, the old XP guest may not have drivers for it. Check that the virtual disk is attached to an IDE or LSI Logic / BusLogic SCSI controller.

Start with the BIOS/EFI fix — a blinking cursor with no progress after 10–20 minutes is almost always the VM trying to EFI-boot an MBR/BIOS disk. Let us know if that gets you past the black screen.