When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
To recap: I successfully loaded V125 and then went in search of a cable. My car is a 1999 XJ8. I tried the Ford “VCM” cable shown in post #32. No joy. I then ordered and received a "Mangoose" from OBDII365.com for about $40:
As shown, it comes with some pretty authentic-looking Mongoose badges, and comes with a DVD with drivers and a copy of V162. I stuck with V125, and the LED's in the Mangoose change from flashing red to green when connected to the laptop.
In fact, as shown, the SDD recognizes the cable as a MongoosePro JLR.
Also, in the SDD “System Information", it records Mongoose Pro JLR as the Gateway Device. (However, under “Supported Models" it doesn't list X308. It does, however, have X100. What’s the difference?)
So, my car, being a 1999 X308, SDD takes me to IDS. And from there, when prompted to check trouble codes, it freezes:
I let it run for 20 minutes or so, just to be sure it wasn’t just slow-- I'm running a Dell D630 with a new hard drive and clean install of XP Pro. After a few minutes it even shows the MongoosePro disconnected! WTF? Only a hard reboot of the Dell will clear everything.
After reboot, I tried some innocuous tests, like power antenna and courtesy lights, and those seemed to work okay, but I wonder if those are just rote teaching, and not really communicating with the car???
So, I’m pretty close to admitting defeat… Unless, you wise sages have any further advice.
In the recesses of my often-lubricated-with-ETOH brain, I seem to recall a MongoosePro JLR will not work on pre-2000 models, and the original Mongoose JLR is the only one that works (a unicorn)… (Note, the Jag service bulletin on J2534 says the Mongoose JLR is supported, and doesn't use the term "MongoosePro".) Did I just prove this? Or, is it just the IBKB (idiot behind the keyboard)?
And, finally, should I try V162? Or, is that a waste of time on the 1999 X308?
I don't know what that error is?
Glad it recognized the Mangoose but you may have some Microsoft problems?
I ended up using Win7 Pro 64bit and yes I am using the V160.xxx software too. I have not used anything below V157 either?
A little further searching of the program freeze problem...
...reveals I'm not alone. Others using IDS for the first time have had this occur when trying to read codes... Unfortunately, no one has ever posted a solution...
Does anyone have a solution? Sorry to ask again, but wanted readers to know, I haven't found the fix. I'll post if I figure it out...
For now, I might try to reinstalling everything (V125 and Mongoose), and try it again.
To recap (again): After 17 years of ownership, I found the need to program another key, and found this useful thread on SDD V125. I successfully loaded V125 and then went in search of a cable. My car is a 1999 XJ8. I tried the Ford "VCM" cable shown in post #32. No joy. I then ordered and received a "Mangoose" from OBDII365.com for about $40. Then, I ran into the screen freeze described in post #41 (I've included the offending program's name in this post's title because this is a known problem in search of a fix-- at least for those of us trying to use SDD V125 on a 24 year old-- or older-- car for the first time! Presumably, anyone searching the problem on Google-- where I found most of my info-- will come across my fix. And we older car owners need all the help we can get...)
Solved:
I tried several tricks to fix the protocolaccessserver error, like setting the XP firewall "Off", and reinstalling V125 and the Mongoose msi. No joy...
I found and installed IDS_DVD130_FULL with these other programs (the SDD V130 worked without these other programs, but I figured the other programs weren't just included for "cocktail chatter", so I added those too):
No small task to find, download and install these 8Gb total-size files....
Success!!!
This is a screen shot of V130 IDS reading trouble codes (DTC) on a Second scan... Note the blue bar at the bottom with "Please Wait". So, this screen shot shows both the reading process and the result from the previous scan....
Five of the 6 systems were successfully read. (Note, Climate Control Module had an error, and was never able to be read-- not an issue, at least, not for me...)
The 3 DTC's shown in the screen shot were: P1000, and two other old DTC's (Mfg specific) that a generic scanner will not clear, but were cleared in IDS! Who knew??? After 17 year of ownership, my vehicle is DTC-free, maybe for the first time!!!
Now, on to key programming; which I may post elsewhere, so as to not clutter this Very Useful thread...
I have SDD 125,126,127,128,129,130,131,132 with SPA and updates for all.(off-line authentication)
I also have many versions of WDS and IDS.
The files can be put on a USB flashdrive or uploaded to a file-sharing site.
Let me know if I can upload somewhere?
Could you upload .ISO image of original IDS125 DVD?
Do you happen to have recovery disks for 1stGen IDS set with Panasonic CF-18 ToughBook?
You can create images easy with https://www.imgburn.com/ Its working W10x64 22H2 even it is old software.
PM:ed you the upload link.
I've shared the folder so melhoov12 should be able to download the fileset.
Graham
Originally Posted by tlindi
Could you upload .ISO image of original IDS125 DVD?
Do you happen to have recovery disks for 1stGen IDS set with Panasonic CF-18 ToughBook?
You can create images easy with https://www.imgburn.com/ Its working W10x64 22H2 even it is old software.
PM:ed you the upload link.
IDS125 files were found. But no trace of IDS CF-18 recovery DVD. I heard they look like this:
They are Panasonic Recovery, not IDS Recovery. IDS Creates Windows setup where IDS and other tools are show by default on special Ui. Panasonic Recovery is just Windows and drivers.
Panasonic CF-18 Recovery can be found from Internet Archive for free, but is not Recovery disk kit :/ (https://archive.org/details/panasoniccf18recovery). I made bootable ghost recovery DVD ISO image of it and I'll see how it looks when I get my hands onto one CF-18/IDS Laptop.
Last edited by tlindi; Sep 21, 2023 at 08:13 AM.
Reason: I was not able to test recovery image at the moment
