hello everybody


I have a 1998 xj8 x308 and ive installed jaguar jlr v130. When I manually put in my VIN then comes a link to go to IDS. When I click the link, the IDS splash screen opens for an instant and goes away...and that's it. I can't get past this point. I have tried running tabman.exe directly from Windows Explorer, but the same thing happens.


I am lost, anyone solved this problem yet? i really need my software to work properly, ive read so many forums but i have found no answer, please help me


Thank you for any help you can offer!

 

Hi,
tell us a bit more about your setup. What laptop are you using (hardware specs as CPU, RAM, harddisk etc)? Which OS or is it running in a virtual machine? Where you got the JLR from? Did you set up the OS fresh and clean?
A few weeks ago, I struggled with the same issue and there may be some hints I can offer.
Cheers, Alexander

 

Hey Alexander,

Thank you very much for your reply, I have it New installed on my windows tablet, virtualbox installed with a feest windows xp sp3, I gave it 1600 MB ram, my tablet is a chuwi hi12 and i got the jlr from another jaguar forum

 

Hi,
so you got the JLR version with the 9 *.rar-files, which include 6 applications (1st.IDS_DVD130_FULL.exe, 2nd.IDS_DVD130.01.exe, 3rd.SPA_DVD130_V2.exe etc) and a password file? I'm just trying to establish if we got the same version, since I got mine presumably from the same source.

If so, then there are 2 major requirements which I experienced:

• proper english version of Win XP SP3 needed (not just switch languages when installing)
• virtual machine does not work (don't know why, since a lot of people use IDS in virtual machines)

Concerning the second condition, I tried to setup it in various virtual machines (under Windows, Linux etc. on a regular Dell laptop) and I never got it to work properly. I always stuck at starting IDS - exact at the same point as you.

So here is what I did to get it running:

1. Set up a fresh and clean WinXP SP3 (english) installation - stand-alone, no virtualbox, dedicated laptop with no other OS on it
2. no connection to internet ever (so I didn't even install the wlan drivers or rather deactivated the wlan function. I copied the JLR installation files via USB stick/external hard drive)
3. deactivation of Windows Firewall, automatic updates etc
4. installation of JLR
   (in contrast to the README, I didn't restart the computer when the installation routines wanted me to do so...I don't think it makes any differences, but worth a try)
5. ignoring all attempts of JLR or others to get a internet connection

It is a quite simple procedure. As mentioned before I did that several times before when using virtual machines, but I never succeeded in starting IDS properly. Doing the same procedure on a dedicated laptop was a gamechanger. I'm using an old laptop with i3 CPU, 2 GB RAM (JLR is supposed to use quite a lot of RAM, so the more the better, but 2 GB is ok) and a 60 GB SDD.


Best regards, Alexander

 

Yes it the same!!!!!! Its the same jlr!! Thanks ill try that!!!!

 

Good luck going down that route. Keep smiling - it's annoying to install the same thing over and over again and varying only small things, but in the end you'll succeed too.
Just a few hints when working with IDS:

• I do have a batch file which I placed in the autostart folder and which sets the date back to August 2012 everytime the systems starts up and no matter what's the date in the BIOS. Create a new file with notepad.exe and save it as "date.bat", select "All file types" as file type, not *.txt file". And then copy the file to the autostart folder, so that it is launched for every startup. The content of "date.bat" is:
  
  Code:

  @ECHO OFF
  DATE 08-08-12

• Once installed JLR, never let it connect to the internet, as it will try to update itself and in a consequence deactivate the version. Even if JLR is not running, there are JLR background jobs running which are listening for internet connections. Reusing the software only possible after re-installation of the whole system (Windows and JLR). This fact can't be stressed enough - so please be indulgent with me ;-)
• Place a shortcut for the password file onto your desktop or stick a post-it to your laptop, as the JLR software will ask for that from time to time. Don't know why, but I think it has sth to do with the date reset.
• Do not use the driver for the mongoose cable, which came with the cable (if you ever got some with it). All/Most cables will work with the driver included in the JLR package.
• When you're experiencing issues with reading the VIN automatically from the car: Leave the cable disconnected as you start the JLR software. Enter your VIN manually - you can put it together with the password on the post-it note. When the screen for starting the IDS legacy tools appears, connect the cable, wait a second and start the tools. Everything should work fine then.
  

Cheers and good luck!

 

Legacy IDS on versions 125-> does same on all the Virtual Machine installations of SDD I have seen no matter what you do!

I have found that if you replace eg on SDD 131 tabman.exe with tabman.exe from IDS118.5 (which last true IDS only version) it works!

 

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: https://www.virtualbox.org/ticket/17696

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.

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.

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:
Because "hardware" has now changed you need to login to SDD again.

Click "Launch Legacy IDS Tools" and yo and behold, after a while
it opens. (It may also "blink" and go away, but after a while it comes up.

You're very very welcome,
tlindi

DM for donation payment terms ;-)