yasu and aa 1.05

[carld2002]

Well... I just got the new yasu 1.1 build ... 35

it fixed my securities my problem but it does nothing to bypass the aa 1.05 copy protection.

any ideas?

[Blazkowicz]

It does bypass SecuRom on Armed Assault, give us SecuRom error.

[evlncrn8]

hmm i wouldnt call getting the securom error a successfull bypass m8

[Blazkowicz]

You are misunderstanding me ^^.

He should give us SecuRom error he gets.


Armed Assault 1.05 starts successfully with latest YASU.

[evlncrn8]

ah yep, sorry misread , but yeh giving the securom error number/code would be more helpful

[carld2002]

does it help to know that I have the czech version?

[evlncrn8]

nope, telling us the message you get does help, along with the error code

[Blazkowicz]

Oh, czech version has starforce, when version 1.0 works your image is not bad.

[carld2002]

well... it doesn't directly give me an error number but I have the error report

the first bit of it:
[Error Information]
UK: 8JRW-ZS3N4Q-K3KNMN-WV32CL-BEU963
HC: CLT5-6KJ8GN-PV9GUB-SXYTS6-TZPLBC-5C2EE4-94Y3NY
4.70.6.8; 3141; ES: 101AF, 101B0, 2, 101AE, 1019E, 1A0, 116, 1011C, 1011B, 1019D, 101C1, 1B6, 101B4, 10030, 10028, 10005, 6E, 10004, 0

[Protected Product Information]
CompanyName = Bohemia Interactive
ProductName = Armed Assault
BuildSignature = 4.70.006.008, 28.02.07
ProductGuid = {CED476AAFEA75A3F8B7A0843E03E9187}
BuildGuid = {92b3b86c-5baf-4e5f-9a97-52445443c493}

any of that help?

[Blazkowicz]

And what does Starforce say before you can click on this report?