Jaguar Forum banner
421 - 437 of 437 Posts
Discussion starter · #421 ·
Is the WinXP (or Win7) OS built into the .ova file or do I have to fend for myself getting that installed?
No! The .OVA file is the complete thing!
Install it with VirtualBox (Not sure if latest version is still compatible?)
Depending on hardware and storage it can take a while on older hardware.
Also it might be slow on old hardware, as you are literally running 2 operating systems at the same time.
If there are any issues with Virtual Box. Try using a legacy version from around 2017/18.
If your unfamiliar with Virtual Machines and I apologise if you already are.
Its basically running a operating system in a window on top of what you already have running!
So for example, you can run my VM of 130 which is Window XP in a window. On any OS that has a version of Virtual Box (MS Windows, OSX, Linux). Its great for experimenting with an OS or software, that's not compatible to your systems operating system. Also it is in a self contained environment.
Also all connections are controlled by you. As all the software is cracked. You don't want any of these versions to check in with Topix as it will reduce options, and ask to be updated to the latest version. So no longer being cracked (Free)!
For example! You only have say access to a works Apple Laptop, or you have a shiny new Windows 11 gaming laptop.
Like for SDD 160.4. It requires Windows 7 32bit to run. Thankfully version 167 can be run natively on Windows 11 and you can further reduce its footprint in both size and resources by using Ghost Spectres Windows 11. But for older versions relying on outdated operating systems or systems where installing non critical software is frowned on. The Virtual Machines are a great way to still have vital tools available for the future, no matter the operating system.

P.S I have been sharing these for about 7/8 years they will always be available on here.
I do update this thread when something comes my way that I think will be useful to myself, or the community.
So always handy to check the first post every 12 months!
 
No! The .OVA file is the complete thing!

P.S I have been sharing these for about 7/8 years they will always be available on here.
I do update this thread when something comes my way that I think will be useful to myself, or the community.
So always handy to check the first post every 12 months!
Awesome, thank you sir!

I will test it on a 3y old laptop and may do a deprecated version of VirtualBox and see what works. I’ll post my results so others will know.
 
Discussion starter · #424 ·
Go to page 1 of this post, everything you need it there TheMindBudda keeps the software downloads updated (or the link in his signature), you'll need a Laptop, a Mongoose Cable & a 12v Power Supply to keep the car powered (not a battery charger) if your not doing a quick check.
 
Thanks to TheMindBuddah for making the files available.

In case it helps anyone with the v138VM in future, some things I found with my install were:

On Gentoo Linux, VirtualBox wouldn't open the .ova file. I've previously had issues with spaces in virtual machine names; the .ova file can be untarred and spaces removed from the .vmdk file with sed:

sed -ie 's/XPJLR 138 Clone/WinXPJLR_138_Clone/g' WinXPJLR_138_Clone-disk001.vmdk

The .vmdk file can be added as a disk to a new XP machine created in VirtualBox, or presumably used in VMWare. Re-tarring the files (after changing the .ovf file to match) produced an ova file which wouldn't load with a checksum error.

VirtualBox did give some errors when loading the VM with the .vmdk file, it appeared to run OK but in the end I used a Windows 10 host to be safe.

WinXP doesn't have a USB3 controller, so I found USB sticks weren't recognised. On the VirtualBox forums it was suggested installing the RENESAS USB3 host driver, but that wasn't recognised in XP. If you need to transfer files to and from the VM with a USB stick, setting the guest controller to USB 1 allowed old, non-USB3 sticks to be used. The Mongoose cable worked fine with the controller set to USB3, so probably best to use that setting for any reprogramming.

Version 166 works natively in Windows 11, with the softwareupdate file renamed and a relevant patch it could go online and download files needed to reprogramme modules without any issues.
Hello friend, I read in your post that the version 166 work online. Can you please help me to get this version ?
 
Subscriptions are expensive from JLR!


@mindbuddah I have both thanks to you - truely - and a request... Many of us happen to be stuck in the brick state with our cars right now, due to the hack.
Are you possibly able to post some files so that we are able to get our cars running? I changed out my (xf 2014 2.2 ) alternator last weekend and found that my keys were not recognised so...
the specific file I need for the Keyless entry module is cpla-14c107-aa
Not sure if I need something for the body control module yet
Thanks in advance.
Adam
 
I've noticed a couple of people with X100s saying IDS doesn't work when SDD tries to launch it. To fix this you need a later version of IDS (tabman.exe) which you can find here:-


To replace the old IDS/Tabman.exe do the following (in your virtual machine or Windows XP laptop where you installed SDD):-

1) Find the existing tabman.exe in c:\Program Files\JLR\IDS\runtime\ and rename it (eg tabmanOLD.exe)
2) Find IDS118.5 tabman.exe from the archive link above and copy it over to your Windows XP/Virtual Machine (a USB stick is the easiest way to do this). Rename it to tabman.exe
3) Copy the new tabman.exe to c:\Program Files\JLR\IDS\runtime\ replacing the old non working version.

Now when you run SDD and it decides your VIN number isn't supported, it will successfully run IDS.

@TheMindBuddah it might be a good idea to copy the files from the archive link above to your drive for completeness. I don't know where the files came from, so the usual safety caveats apply (I would only ever run them in a virtual box).
 
Discussion starter · #435 ·
@TheMindBuddah it might be a good idea to copy the files from the archive link above to your drive for completeness. I don't know where the files came from, so the usual safety caveats apply (I would only ever run them in a virtual box).
Absolute fantastic find!

Raiding Internet Archive now!
 
Discussion starter · #436 ·
@TheMindBuddah it might be a good idea to copy the files from the archive link above to your drive for completeness. I don't know where the files came from, so the usual safety caveats apply (I would only ever run them in a virtual box).
Thank you Nerja!

Was interesting poking around tlindi files!

It seems the issue with IDS is not IDS as such, but a issue with Virtual Box.

Text Below of a solution for anyone who wants to have a quick read!

"Reason for ids not to launch on virtual machines
Goo'd day!
The tabman.exe from IDS 118.5 was temporary fix as I was looking into
real solution. Now I have spent some 100+ hours to find what is this issue.
There is a bug in VirtualBox (that will never get fixed) and
it is the reason for IDS is not able to launch on virtual machines.
Over 7 years old bug report is here: #17696 (Processor ID and MotherBord ID Missing) – Oracle VirtualBox
You can verify issue by running and learing of all following
system detail query commands will return "null" in you
Virtual Box SDD/IDS Windows XP or Windows 7 too.
wmic BaseBoard get SerialNumber /FORMAT:list
wmic BIOS get SerialNumber /FORMAT:list
wmic CPU get ProcessorID /FORMAT:list[/QUOTE]
SDD/IDS uses same functions to find details of PC running SDD/IDS.
With the details it will generate deviceId="" key in to
encrypted session_authentication.exml file. Cause wmic returns
nothing, the deviceID is not generated into .exml and "the device" is unknown.
This everything is bound to business decision that software is
licensed onto one hardware and onto one authenticated user at the time.
So together software and bug causes issue that IDS cannot get properly
authorized and will just "blink" and disappear when tried to open.

Then the good news - we can fix this issue!

You need to shutdown and de-register (ie remove, but only remove
don't delete files!) your SDD VM from VirtualBox.
Add folloging three (3) <ExtraDataItem....> lines to you Virtual Machine
.vbox file between <ExtraData></ExtraData>.
If there is no ExtraData in advance add them below MediaRegistry,
like following.
<VirtualBox
<Machine ...
<MediaRegistry>
...
</MediaRegistry>
<ExtraData>
<ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/DmiExposeProcInf" value="1"/>
<ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/DmiBoardSerial" value="JAGUARGOINTO"/>
<ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial" value="YOURSELF"/>
</ExtraData>
...
</Machine>
</VirtualBox>
Add (ie Register) you virtual machine back to VirtualBox.
Boot you VM and do all the normal magics of yours.

You can verify correct hardware setup with following commands:
wmic BaseBoard get SerialNumber /FORMAT:list
wmic BIOS get SerialNumber /FORMAT:list
wmic CPU get ProcessorID /FORMAT:list
Because "hardware" has now changed you need to login to SDD again.
And yo and behold - Click "Launch Legacy IDS Tools" and
opens after a small while. It also may "blink" and go away, but after a while
it comes up.
You're very very welcome,
tlindi
"
 
Discussion starter · #437 · (Edited)
UPDATE 23/09/2025
Added SDD 131 (Native) and IDS 118,119,125
Also the Tabman.Exe files mentioned in post #434 by Nerja
All untested as they have been uploading using my phone!
 
421 - 437 of 437 Posts