[weinerbarn]

I noticed other tools like Best don't work after copying either. Gives a password error. I even changed the INI paths for EDIABAS. Ended up just copying the old files back and it works fine.

[blax123]

i replaced the ediabas folder, then ista is fast again but standard tools not working. then i replaced ediabas.ini, tool32.ini, remote.ini, obd.ini with my old ones, after this standard tools working but ista slow again. seems just to be just a setting thing in ini.

[dardan]

I cant make ISTA P to work together with ISTA 4.46.xx ... if i install ediabas 7.3.0 then ISTA 4.46.xx does not work for me... using ICOM NEXT clone

[Sedoy]

I cant make ISTA P to work together with ISTA 4.46.xx ... if i install ediabas 7.3.0 then ISTA 4.46.xx does not work for me... using ICOM NEXT clone

Why you install Ediabas for ISTA-P? It have self ediabas inside.

[dardan]

I get this all the time "ISTA P error 94201 Technical service initialization failed" solution i read was to install patched ediabas.

[BugFix]

You can delete the Ediabas folder, perform a Format C://,
or simply remove the entry in the environment variables

https://cartechnology.co.uk/attachment.php?aid=186115

[Red_bean_bun]

Just curious - if both sets of applications have their own Ediabas - why would ISTA be making calls to ST’s Ediabas ?

Does ISTA use the environment path to ediabas.ini as well ?

Since not everyone has problems with the new version, I think it's because not everyone installs a second version of Ediabas, e.g. with StandardTools. The problem exists because two different versions of Ediabas(v7.3.0 in StandardTools and v7.6.0 in ISTA) apparently lead to problems in ISTA. This situation cannot happen in a BMW workshop because only ISTA is installed there, which is why no one at BMW will have noticed it.

The problem is easy to solve, just delete/move/rename the ediabas.ini from C:\ec-apps\ediabas\bin.

Another option(not tested) is to copy the new Ediabas from "C:\Program Files (x86)\BMW\ISPI\TRIC\ISTA\Ediabas\BIN" to "C:\ec-apps\ediabas\bin". Of course, you first have to test whether all old tools such as INPA still work.

Other solutions welcome.

Edit:
Ok, after research with several users i can say that only one option for those who have problems with slow ISTA exist, you have to copy all files from "C:\Program Files (x86)\BMW\ISPI\TRIC\ISTA\Ediabas\BIN" to "C:\ec-apps\ediabas\bin" or "C:\ediabas\bin" depend on your installation. After that, INPA should also work, you may have to adjust the ediabas.ini a little, e.g. enter the IP of the car directly instead of autodetect(only if don't work). Check also paths.

---

You can delete the Ediabas folder, perform a Format C://,
or simply remove the entry in the environment variables

https://cartechnology.co.uk/attachment.php?aid=186115

So this environment variable is used by both ISTA and Standard Tools ?

[Node]

ISTA's internal ediabas DOES use that variable.

[sebastianfernandes]

Thanks to @sedoy and @bugfix to pointing out in the right direction, and Here is fix for this mess. I have edited ediabas.ini in both ista and ediabas. With this my ista works perfect and also INPA/tool32/etc. Copy both to respective ediabas location and ista location, assuming ediabas is installed in c:\ediabas, because .ini file is edited according to that. Also make sure you delete entry in SYSTEM VARIABLE ediabas_config_dir.
This works and tried it on my F20.
Glad to help.
If I helped then please thanks+rep

[Cerhio]

Thanks to @sedoy and @bugfix to pointing out in the right direction, and Here is fix for this mess. I have edited ediabas.ini in both ista and ediabas. With this my ista works perfect and also INPA/tool32/etc. Copy both to respective ediabas location and ista location, assuming ediabas is installed in c:\ediabas, because .ini file is edited according to that. Also make sure you delete entry in SYSTEM VARIABLE ediabas_config_dir.
This works and tried it on my F20.
Glad to help.

Hey. Your files help me as well
What did you change exactly in it?