YASU 1.3.7070 released

[ganimed]

It is the same on me:
100 percent cpu using.
If i see all the post's before is it a amd prob, isn't it?

[Jito463]

(i have plenty of spare parts flying around)

What, you mean like Poltergeist style? I'd be getting out of there if I was you...

On a serious note, it appears to work OK on both of my AMD systems, too. I doubt it has anything to do with AMD. I think that's more coincidence than anything.

[cryo]

CPU Type AMD Athlon XP, 2200 MHz (11 x 200) 3200+ (Barton 2500+)
Motherboard Name Gigabyte GA-7N400 (5 PCI, 1 AGP, 4 DDR DIMM, Audio)
Motherboard Chipset nVIDIA nForce2 Ultra 400
System Memory 768 MB (PC3200 DDR SDRAM)
Disk Drive JetFlash TS1GJF2A/120 USB Device (996 MB, USB) (flash drive)
Disk Drive ST380011A (80 GB, 7200 RPM, Ultra-ATA/100)
Disk Drive WDC WD1200JB-00DUA3 (111 GB, IDE)
Optical Drive _NEC DVD_RW ND-3540A (DVD+R9:8x, DVD-R9:4x, DVD+RW:16x/8x, DVD-RW:16x/6x, DVD-ROM:16x, CD:48x/32x/48x DVD+RW/DVD-RW)
Optical Drive FF1409L JFD891Y SCSI CdRom Device (daemon)
I have the same problem (99% cpu usage and no interface)

[noib]

[*]Fixed Lame SecuROM 7.330012 Blacklist of Y.A.S.U.

"Lame" is the official Copyprotection name ??

[Reef]

Could also be the same problem I had, permissions set to deny on this registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdrom\Enum

YASU can't cloak drives properly when access to this key is denied.

[ghost_zero]

Maybe it is some SecuROM bug... Have you tested your original already? If that one doesn't work too, you should contact SecuROM support...

MrFrost is not the only one that confirms that it is working, therefore I guess it is some specific problem you have...
Have you tried renaming your DT-Drive? I mean changing Model and Vendor and maybe also drive letter?
I had often a SecuROM problem regarding this already...
It either took far longer to verify (it always takes longer the first time - because it has to find out the correct parameters - but after that it should be verified in a couple of seconds) or didn't work at all if this happened (which is a result of wrong parameters for verification)...

Also: What error message do you get exactly?

[MRFRoST]

Test Drive Unlimited with patch still dosent work with new yasu, deamon tools still gets detected.

I tested YASU V1.3 with Test Drive Unlimited 1.66a and it works perfect. Mayby your image is bad, or you have other programs installed wich are blacklisted.

[rockmanxy]

100% CPU using too.
AMD Athlon 64 3200+.
waiting for a fix.

[sickchok]

Test Drive Unlimited with patch still dosent work with new yasu, deamon tools still gets detected.

[Nemrod]

sYk0, great job!! thanks for the great work!

[flubba86]

Thanks very much. I am having the same problem, 99% cpu usage and non-working yasu with the new version. Any news on when the fix is due?

[Xtreme2damax]

Still getting an "Emulator Detected" Error with Resident Evil 4 USA version.

Resident Evil 4 appears to be using Securom (Version unknown).

Tried all available known fixes such as using the -c -s and -usuck parameters, renaming Yasu.exe to Wazu.exe.

Tried changing registry permissions like Reef did for keys cdrom and enum, also didn't work.

Using latest Yasu 1.3 7070, and Daemon-Tools 4091 HE.

System Specs:

Amd Athlon64 x 2 3800+ @ 2.0 Ghz, 1024 Megabytes (1 Gig) of Ram, and a Geforce 6150LE integrated graphics chip.

Running game.exe for Resident Evil 4 in Windows 2000 Compatibility mode will allow Resident Evil 4 to start up without an Emulator Detected error.

I don't like to run things like to run things like this in compatibility mode because RE4 was made for WinXP/Vista and causes more problems than does good.

Thanks if anyone can help or let me know what is wrong.

[rayden24]

same problem for me here, 100%cpu usage and no window

my config:
motherboard asus a8n-e
Cpu: athlon 64 3200+ (venice)
memory:2gb ram
2 SATA hdd's
2 physical dvd drives (reader and writer)
4 virtual daemon 4.09HE drives
alcohol not installed

[swiss-cs]

Hm, i also have a AMD Athlon but no errors, it REALLY works PERFECT. There are TWO Important things, i think everyone, should do:

• Rename the YASU.exe

• Make s shortcut in your autostart dir (Start->Programs) with a link to the exe and the parameters "-s -c -usuck" (example
  "C:\antiblacklisting.exe -s -c -usuck")

You dont HAVE TO, but its good to have it in autostart

[..::shiFt::..]

But does this explain why it gives you the same problem under VMWare too?

mmh no. but Prataten has the same configuration and the same problem so i think it has to do with it.

ok, i know what the problem is and will release an update A.S.A.P...

thanks, we will wait...