silent hunter 4 (version 1.1!)has blacklisted yasu 1.1035

[Fercyful]

I solve my problems with SH4 1.1 like this:

1. have daemon tools 0.48 + latest yasu not active.

2. I went to system manager and disabled all my drives there (virtual and IDE ones) not need to disconnect any cable.. even you donґt need to restart...

3. activate daemon 0.48 (ON mode BUT still donґt mount the sh4 image) and I select to have 1 virtual drive...

4. run and activate yasu ON.

5. double click on the SH4 icon... it will bring the message that I have not dvd... left there the message...

6. NOW mount the image and hit RETRY at that moment...

you are in game!! good hunt!!

ps:maybe this tip will help to know why ths is happening... before 1.1 I can use yasu and dameon without any problems... sure the protection of the new sh4.exe have something that you have to do all that to get it running...

[AndreP]

There is the same problem mentioned in the german customer section.

Iґm this customer

When YASU is running (uncloaked)-->emulation detected
YASU with Safedisc (cloaked)-->emulation detected
YASU with Securom (cloaked)-->nothing

YASU is only Blacklisting bei Securom (my opinion)

Sorry, for my English

[Terramex]

no man its not. i guess the newer version of securom is checking other sectors of the dvd.

AFAIK Securom never did that (also not with NWN2), and i doubt they'll ever change ISO check with a patch just to sort out Maxi-Images.

afaik daemon tools can't be blacklisted anymore, its just the general SCSI Blacklisting [click] thing.

If this would be true, i guess we wouldn't have seen AntiSecuROM, CureROM and YASU but only devcon-batches.
With drivernames (mostly) randomized there are still ways to blacklist

[dermoritz]

the procedure above didn't work for me. the only "mistake" i made was one more reboot after the installation of sptd. but this shouldn't be a mistake?

[Blazkowicz]

-=[ ProtectionID v0.5.2.12 BETA NON-DISTRO]=-
(c) CDKiLLER & [x/xxx]
Build 03/23/07-01:24:23
Ready...
Scanning -> M:\Silent Hunter 4 Wolves of the Pacific\sh4.exe
File Type : Exe, Size : 6282888 (05FDE88h) Byte(s)
-> File Appears to be Digitally Signed @ Offset 05FD000h, size : 0E88h / 03720 byte(s)
-> Suspicious MZ Header..
[!] SecuROM Detected - Version 07.32.0007
[!] Possible CD/DVD-Key or Serial Check -> CDKey
- Scan Took : 0.141 Seconds

[blackhand]

information syk0 provided in another thread appears to have solved the problem, it certainly works for me -

Uninstall DAEMON-Tools...
go to \Program Files\DAEMON-Tools\ delete any exsisting files...
Download SPTD Uninstaller, run it...
Reboot your computer...
Download SPTD 1.42 Installer (32Bit) or SPTD 1.42 Installer (64Bit) depending on your O/S
Install latest SPTD driver (above)
Install DAEMON-Tools 4.08 (in the downloads section)
Reboot your pc again...

from http://www.daemon-tools.cc/dtcc/yasu...-t16092p4.html

[blackhand]

i just want to lend support for this issue, i'm exerpiencing the same problem.

the original release ran fine with daemon and yasu, but after patching to 1.1 it just does nothing. you double click the icon, and it works for a few seconds, then it goes dead with sh4.exe still actively running in the process list. i've tried almost everything and i cannot get it to work with just yasu.

hopefully the cause can be pinpointed and resolved.

[DomiOh]

There is the same problem mentioned in the german customer section.

Same "symptoms" as told here.
When Yasu isn't running they get "Emulation detected", when Yasu is running, nothing happens.

Not all images can be bad.

[..::shiFt::..]

afaik daemon tools can't be blacklisted anymore, its just the general SCSI Blacklisting [click] thing.

[dermoritz]

protectionid says securom 7.xx.

"If it where blacklisted there would be a SecuROM error (Security Module, blah blah),"

that is what i am talking about. the "error" isn't securom related. it's related with the new silent hunter 4 version and yasu.
i think its a fast "nightly" workaround for yasu 1.1.7035 from ubisoft to counter the pirated copies out there?!

i got the security module blahblah with version 1.07 of yasu, but fortunately you released the new yasu exactly at the right time :-).

and i guess with unplugging physikal drives i get the same error with yasu disabled - deamon tools it self is blacklisted, i think?!

[sYk0]

If it where blacklisted there would be a SecuROM error (Security Module, blah blah), maybe just some crappy coding (not YASU) .

But i'll try find out more...

[..::shiFt::..]

Well _if_ you are right, and yasu is blacklisted, then shutdown your computer, disconnect all optical drives and play the game without yasu!

If its working then yasu is blacklisted. If not, then its a image problem.


Could you scan the game executable with ProtectionID and tell us the exact securom version?

only one thing left: please don't tell me how to make a good image

no comment on that!

[dermoritz]

if it's the image securom would check it and then stuck or give an error message. but the securom-check-spinning-cd occurs only if i don't run yasu. i know the errors caused by bad images you allways see the spinning-cd and then the game stucks or gives an error.
i made many images. all with alcohol dpm at highest quality and slowest speed.
and before i posted here i made some additional images to check it.

the main problem is, you don't have this specific problem. this problem is simlar to the first patches for titan quest - one patch one new version of curerom ...

but this time it the new blacklist seems outside/before securom.

only one thing left: please don't tell me how to make a good image

[..::shiFt::..]

no man its not. i guess the newer version of securom is checking other sectors of the dvd.


Again: if it would be a blacklist, it would not take 100% and stuck. It would show a error message.


How did you create your image? Are you using a Full Image or a Fixed Image?

[dermoritz]

the image works fine with version 1.0. so the image can't be bad.
after patching it doesn't come to a securom check if yasu is running! the game simply stucks and nothing happens. without yasu running the normal emulationblacklist error occurs. there are 2 workarounds: downgrading to 1.0 and living with many bugs or using the original dvd 'til a new yasu is released. i choose the 2nd one :-).

i guess its an blacklist from the game.exe and not from securom. it simply checks if an yasu task is running or something.