Announcement

Collapse
No announcement yet.

Command and Conquer Patch 1.05

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • KoRn
    replied
    There will be YASU 1.3 released
    in "a couple of days".

    Please report if the problem
    then still exists.
    Until then I will stay with
    C&C3 1.05.

    Leave a comment:


  • masteryoda34
    replied
    Same problem. WinXP 32bit. Command and Conquer 1.06. YASU 7060. Tried -usuck. Gives "conflict with emulation software detected".

    Leave a comment:


  • debolaz
    replied
    Originally Posted by burli View Post
    CNC 3 1.06 doesnt work with latest (7060) YASU.
    It recognize the emulation software.
    I've got Windows Vista Ultimate 32 Bit.
    Same problem here, Windows XP 32 bit, YASU 7060.

    Leave a comment:


  • john753
    replied
    Same here, problems came with the new patch 1.06 released this week.

    I also have Windows Vista Ultimate 32-bit and YASU v1.2b.7060. I already tried the -usuck parameter but without effect. I guess therefore that an update of YASU is required to bypass the new protection.

    If you need any help with testing, let me know.

    Leave a comment:


  • burli
    replied
    Command and Conquer Patch 1.06

    CNC 3 1.06 doesnt work with latest (7060) YASU.

    It recognize the emulation software.
    I've got Windows Vista Ultimate 32 Bit.

    Leave a comment:


  • ghost_zero
    replied
    You should read this post too:
    http://www.daemon-tools.cc/dtcc/show...3&postcount=35

    Leave a comment:


  • GmY
    replied
    Originally Posted by Benni View Post
    CNC 3 1.05 doesnt work with latest (7060) YASU.

    It tells me that a security module cannot be loaded.
    I've got Windows Vista Business x64.

    @Syko: I emailed you the protected exe.

    Exactly your problem . But using Windows Vista Ultimate 32Bit.

    Leave a comment:


  • evlncrn8
    replied
    well, securom 'recommendation', doesnt necessarially mean its their bug... windows is weird sometimes too

    Leave a comment:


  • ..::shiFt::..
    replied
    I guess thats a SecuROM bug, as it can happen with the original DVD inserted in the physical drive too.

    Leave a comment:


  • evlncrn8
    replied
    other warning -> you might bsod if you do this (some controller chipsets/drivers poll this registry key).. so reboot as soon as you can after deleting the keys..

    Leave a comment:


  • Benni
    replied
    Of course.

    Leave a comment:


  • Hanschke
    replied
    have u testet it? i dont want to do it

    Leave a comment:


  • Benni
    replied
    English
    Read this:
    http://forums.ea.com/mboards/message...&sls=2#2314829

    German
    An alle, bei denen es nicht mehr funktioniert:
    Start => Ausführen => regedit (eintippen, bestätigen)
    Den Schlüssel
    Code:
    HKEY_LOCAL_MACHINE / SYSTEM / MountedDevices
    aufsuchen.
    Darin alle blauen Einträge löschen (alle REG_BINARY-Einträge). Anschließend muss ein Neustart gemacht werden.
    Das ist eine Lösung aus dem C&C3-Forum von EA, die bei mir funktioniert hat!

    Edit
    WARNING: Devices will be reassigned to their drive letters. So you might have to re-order them manually in the devices management panel of Windows.
    Warnung: Die Laufwerksbuchstaben werden nach diesem Vorgang neu zugeordnet. Möglicherweise muss das in der Computerverwaltung beim Datenträger-Management rückgängig gemacht werden.
    Last edited by Benni; 08.06.2007, 13:20.

    Leave a comment:


  • Silver Fox
    replied
    Originally Posted by Reef View Post
    You're not using the latest YASU. Get 1.2b here.
    Thanks but I tried that last night bro. Still no dice for me, i tried the same combinations of renaming etc. The official C&C3 forum has a thread about it. Might be some more info in there.

    http://forums.ea.com/mboards/thread....32410&tstart=0

    Leave a comment:


  • Benni
    replied
    Hi sYk0,

    doesnt work. That command line parameter hides the tooltip of YASU, doesnt it?
    But still the same message for me :-(. Security module couldnt be loaded... etc.

    Leave a comment:

Working...
X