[jaramillo]

Ista P 3.72

Standalone

Thanks to Shawn

[tinkerman]

Thanks for sharing this.

Your upload is about 13GB, and Shawn's upload is about 9GB. What's the difference in the uploaded content?

[____ANGEL___]

standalone and installer

[tinkerman]

Ista P 3.72 Standalone
Thanks to Shawn

jaramillo, what is your experience in the "proper" way to install this standalone version? I ask because I've noted the difference below between this standalone version and what is installed by the installer*:
* Note: the installer installs a bunch of other folders and files (not included in the standalone).

Standalone File Structure
ISTA-P (top folder in archive)
- BMW (folder)
- BrokerIspiNext (folder)
- Inventory (folder)
- Open-Source-Software (folder)
- Operation (folder)
- Protocols (folder)
- Taurus (folder)
- application.xml
- application.xsd
- ConfigPaths.xml
- ConfigPaths.xsd


Installer Installed File Structure
C:\ProgramData\BMW\ISPI
- config (folder)

- data (folder)
-- TRIC (folder)
--- ISTA-P (folder)
---- BMW (folder)
---- BrokerIspiNext (folder)
---- Inventory (folder)
---- Open-Source-Software (folder)
---- Operation (folder)
---- Protocols (folder)
---- Taurus (folder)
---- application.xml
---- application.xsd
---- ConfigPaths.xml
---- ConfigPaths.xsd
--- temp (folder)
--- tests (folder)

- logs (folder)

Questions
1. Are the "other" folders & files installed by the installer (those not included in the standalone) not necessary?
2. Where should the ISTA-P folder of the standalone version be copied to?
3. Other than installing/running the Loader, are there any tweaks or edits* required after copying the standalone files?
*Such as editing EDIABAS.INI(version 7.2 installed by installer, not 7.3!?), adding OBD.INI(missing in installer installed EDIABAS>BIN folder!?), network/firewall settings etc.?
4. What interfaces have you tried or are known to work with this version?

Thank you...

[jaramillo]

Hello,
1. Just unpack and use

1. Standalone version works well without other files
2. The place you like more
3. There are no tweaks needed, just use loader
4. I only work with icom to flash E/R series, dont recomend kdcan... but if you want you can use loader with kdcan emu

[tinkerman]

I just realized that the ISTA-P Loader 6.1 folder from the following thread:
"ISTA-P Loaders 6.1 to 6.6"
https://cartechnology.co.uk/showthread.php?tid=63902

includes the file "Einstellung bei Loader V6.1F.de" which has instructions(in German) for enabling 6.1(with support for K+DCAN/ENET) to "work"* with more recent ISTA-P (e.g. 3.72 confirmed with this standalone version).

Translated:
1. Open the ISTA-P installation folder and locate the “application.xml” file and
open it with the editor. (e.g. notepad)

2. Change the value “distributionVersion="xx.x.xxx" to the value “distributionVersion=“3.xx.x.xxx“
So just expand the beginning of the version with 3.
Don't enter xx.x.xxx there!! Only at the beginning 3. (Save file)!!
!!Everything else stays as it is!!

* The Loader 6.1 notifies during initial boot that EDIABAS 7.3.0 needs to be installed. So I installed my "patched EDIABAS 7.3.0" then rebooted Loader 6.1, selected K+DCAN, selected "BMW cars", then ISTA-P 3.72 started booting and eventually I was able to confirm K+DCAN/"ICOM" connection in ISTA-P!

But it would be reassuring to have a more recent version Loader with the K+DCAN support as I'm not sure how reliable the 6.1 would be with more recent versions of ISTA-P. I hope beemerboy will come through at some point...

Cheers...