[intesisParticipant 15 December 2022 at 07:36 Post count: 10]

#33433

I guess
C=”Compatible”
N=”Normal”
Just check the program directory.

[m00Participant 15 December 2022 at 11:50 Post count: 30]

#33436

Absolutely wonderful!
Everything works – Importing, exporting, integrated Apps (like Replace Device / Extended Copy), external Apps (like Recontruction).
You did it, debbe.

I guess all thats left to dream about is cracking the signing process.
The only “issue” left is: A project that has been exported through a cracked version (if its larger than 5 devices) cannot be imported with a original version. Thats because the exported .knxproj file does not contain the “P-xxxx.certificate” File (because you need a valid license to sign a project – as far as i know its probably impossible to crack.)
The idea that i had was: Could we probably use the “free” Lite-License you get from completing the online course? I checked it and the signing of a lite- home- and professional-license are basically the same, so we could potentially use a Lite license (just register with the my.knx.org using a fake name and address, complete the course which should take 30min, get the lite-cloudlicense for free) to sign projects.

Thats not a huge deal anyways – it just matters for ppl who use the cracked version for themselves and need to give the project to a professional system integrator. Those would not be able to import the cracked project so far.

[sinn3rParticipant 15 December 2022 at 14:12 Post count: 345]

#33442

Nice work!
But I cannot use it, as my project contains some older devices that need to run ETS6C, which is not cracked.
@debbe Could you have a look at this? The crack should be the same.

[asdfasdfasdParticipant 15 December 2022 at 15:39 Post count: 59]

#33444

@intesis & @sinn3r ok

@m00 ok but I can’t do the test because I don’t have an original key.. however I read that it was the opposite, a cracked version could not read a project with an original key.. if so, send me a project and I’ll see what I can do. .

PS:

I puted the update let me know if it works…

as I said I have no experience with ETS, can you help me with some components, broadly speaking I think I understand how it works but I haven’t done the tests yet.. the part that worries me a bit is the use of ABB FCC/ S1.3.1.1 Fan coils

thank you

• This reply was modified 5 months, 2 weeks ago by asdfasdfasd.

[sinn3rParticipant 15 December 2022 at 18:13 Post count: 345]

#33447

@debbe with the new version ETS6C and ETS6N both crash on startup with:
“ETS cannot be started due to a severe error and has to be closed. Please restart your computer. If the problem persists, please contact KNX support. Interne Einschränkung im JIT-Compiler.”
Previous version worked for me (ETS6N).

[asdfasdfasdParticipant 15 December 2022 at 18:27 Post count: 59]

#33448

Strange.. in the N version I haven’t made any changes apart from 5 but it’s irrelevant.. let’s wait for some other feed

[sinn3rParticipant 15 December 2022 at 18:39 Post count: 345]

#33450

Ok, I just found out that ETS6.exe always starts ETS6C.exe on my system, I think because compatibility-mode was enabled somewhere in the registry when importing my project. Even when starting ETS6N.exe manually the process ETS6C.exe is spawned. So I cannot start ETS6N anymore.
I even reinstalled it and copied the old crack and then the Demo is started (ETS6C).
So the problem always is in ETS6C, not ETS6N.

The error occures with the program tries to check the license and for updates.

• This reply was modified 5 months, 2 weeks ago by sinn3r.