NEW Xentry Awesome Solution

[Qrius]

It is possible to have a key for Xenrty 07.2010

HW-ID: 597E9FA2CC0
App-Id: 252

Thank you

I guess you could here: http://www.digital-kaos.co.uk/forums...19/#post779564

[gmatj]

This solution allows you to use your old keys with Xentry 05.2010 and 07.2010.

Features:
* Works with ANY old key. No matter it is standard or developer!
* Works in VMware without any modifications.
* Does not change your AppID.
* Does not block addon installation or software upgrades.

Please note that this solution is not compatible with version 09.2010.

You should know that Patrian Normal Tool replaces your key and changes your AppID. I have attached Normal Tool removal utility. Use it if you have Patrian Normal Tool installed as it is no longer needed.

Mr Zolookas

I would like to express my gratitude to a low profile but high caliber guy who has put a lot of effort and a lot of his personal time and has created some very usefull tools for the whole of the DK community.

Thanks to a guy that has done all this, without big words and verbalism that we see these days in DK.

Sincere Thanks m8 (for the solutions and for your style in providing them)

G.

[zolookas]

You are welcome.

[antvorskov2006]

Thanks mr. ZOLOOKAS you are the
And thanks for bother to spend your time on finding a
solution and share it with us.







Antvorskov.

[tomtom0785]

Great man!!
I'm always surprised about new genial solutions in this forum here!!

[PremierD]

Ok mate .. The key you posted will not work ... this thread is about Zoolokas's Fix ..... and the keys supplied in the proper thread will work only with that .. so please do not cloud the Issue here ...

[strda50es]

Once more mate.
I want to tell you that i am glad to be a member of a forum with members like you zolookas.
I will agree with gmatj and would also like to add that your contribution all these months to this place is much appreciated by all of us.
Congratulations mate for what you've done so far.

[GDB]

I'd like to thank all of you on this great forum. Special thanks to Zolookas, it took me a few days to get everything worked out but I have DAS and Xentry 07.2010 running now. Next is to get it to work with a multiplexer, does anyone here know where best to buy such a multiplexer from e reliable seller ? ( I have read the "clone tools from China" thread and would like to avoid problems )

Thank you very much for great tutorial, helpful tips and simple solutions !

[DB_member]

Dear Xentry enthusiasts, I've tried the 07/2010 Xentry with both tools (the zolookas approach and the Patrian tool).

Both seem to work in simulation mode but when I connect to an Xentry car I get the (blacklist) error (1.17)-7.780.

Have I been blind or is there a fix available for this issue or do both solutions only work with an original mux?

[wsc]

Dear Xentry enthusiasts, I've tried the 07/2010 Xentry with both tools (the zolookas approach and the Patrian tool).

Both seem to work in simulation mode but when I connect to an Xentry car I get the (blacklist) error (1.17)-7.780.

Have I been blind or is there a fix available for this issue or do both solutions only work with an original mux?

Try this M8
Go: F:\Xentry\Bin\asam3d and asam3d.ini make Drivers from T to D

[DB_member]

Try this M8
Go: F:\Xentry\Bin\asam3d and asam3d.ini make Drivers from T to D

I did try, but not for the Patrian approach, have to try again. asam3d.ini indeed had T after installation.

Can you explain what prevents me to edit the file "directly". I cannot save it with the same name. What I did was I saved it with a different name, then "deleted" the original and renamed the modified file back to the original. I wonder if something gets broken this way. The file is "protected" even if I log in with a different XP account.

Do you mean asam3d.ini and asam3d_RealCom.ini?

Thanks for your proposal.

PS. I changed the file attributes and now I can save the edited file with the original name.

[wsc]

I did try, but not for the Patrian approach, have to try again. asam3d.ini indeed had T after installation.

Can you explain what prevents me to edit the file "directly". I cannot save it with the same name. What I did was I saved it with a different name, then "deleted" the original and renamed the modified file back to the original. I wonder if something gets broken this way. The file is "protected" even if I log in with a different XP account.

Do you mean asam3d.ini and asam3d_RealCom.ini?

Thanks for your proposal.

Properties and unchecked read-only

[wsc]

I did try, but not for the Patrian approach, have to try again. asam3d.ini indeed had T after installation.

Can you explain what prevents me to edit the file "directly". I cannot save it with the same name. What I did was I saved it with a different name, then "deleted" the original and renamed the modified file back to the original. I wonder if something gets broken this way. The file is "protected" even if I log in with a different XP account.

Do you mean asam3d.ini and asam3d_RealCom.ini?

Thanks for your proposal.

PS. I changed the file attributes and now I can save the edited file with the original name.

Yes these two files

[DB_member]

Yes these two files

I tried it again after I had Xentry 07/2010 installed with the Patrian tool and I still get the same error (followed by (2.27)-7.870).

At the Patrian tool thread someone else had the same issue but no solution was provided.

Someone must have successfully used one or the other (or both) solution, would anyone confirm this only works if the mux is not blacklisted (when doing real diagnosis, not simulation) or should there be another solution for the error?

[wsc]

I tried it again after I had Xentry 07/2010 installed with the Patrian tool and I still get the same error (followed by (2.27)-7.870).

At the Patrian tool thread someone else had the same issue but no solution was provided.

Someone must have successfully used one or the other (or both) solution, would anyone confirm this only works if the mux is not blacklisted (when doing real diagnosis, not simulation) or should there be another solution for the error?

Mate do you have the same error with DAS and XENTRY ?
Or only with Xentry ?