[Sedoy]

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.

Other solution:
Replace attached api32.dll in ISTA\Ediabas\BIN, then is possible use "old" Ediabas without conflict with ISTA.

[tonemoz]

I haven't noticed any issues so far with both Standard Tools and official Ista 4.46 as of yet. Both seem to working as normal.

[B O S S]

thank you very much, you are the best finally works 4:46 best regards

[Sedoy]

thank you very much, you are the best finally works 4:46 best regards

Can you search on C drive to all Api32.dll? Maybe find it in Windows\System32.

[Node]

I also had no problems with ISTA 4.46's v7.6 and standard tools v7.3 installed on the same computer at the same time. Both worked perfectly. But I was using ICOM and direct ENET. The only issue I can think of if people are using ediabas connection in ISTA, then it could be a problem because clearly something was changed in ediabas' internal protocol.

So now the only remaining issue is error returned by ediabas while ISTA is trying to enable ICOM's DHCP server. Or does this solve that too?

[tste1982]

thank you very much, you are the best finally works 4:46 best regards

Can you search on C drive to all Api32.dll? Maybe find it in Windows\System32.

I haven‘t tried deleting ediabas.ini, since it worked with icom, but what should we do with the api32.dll, when we find it? 

@sedoy: can I ask you a question in pm since it has nothing to do with this problem?  

Regards

[Sedoy]

I think everything works on a clean system, I only suspect the problem is on systems with dead data, so I suspect that the Api32.dll is somewhere in the system and is causing problems.

Problem with DHCP is maybe from new ICOM Firmware.

---

thank you very much, you are the best finally works 4:46 best regards

Can you search on C drive to all Api32.dll? Maybe find it in Windows\System32.

I haven‘t tried deleting ediabas.ini, since it worked with icom, but what should we do with the api32.dll, when we find it? 

@sedoy: can I ask you a question in pm since it has nothing to do with this problem?  

Regards

For first need a list where existing files.

Yes you can PM me.

[Node]

I tried new ICOM firmware with 4.45 and DHCP worked perfectly. It's only a problem on 4.46.

[NeRkO20]

@sedoy

Regarding the DHCP problem....I have downgraded ICOM Next from the latest version to the last 3 versions in the past...

With every version DHCP doesn't work. On 2 Laptops!

After that I have installed ista 4.45.xx on 1 laptop...and DHCP is working.

Regarding ediabas, I have 2 ediabas Versions...the only problem is the fact thst ista is slover a little bit but works.

[Sedoy]

1. DHCP Problem is maybe from interaction new ediabas and icom, i don't know.
2. I'm particularly interested in the slowdown ISTA. Can anyone with this problem search to Api32.dll on C drive and list all finds?