Page 1 of 2 12 LastLast
Showing results 1 to 10 of 16

Thread: SiliconImage VIA SiS chipsets and WPCREDIT tool vs StarForce

  1. #1
    New User
    Join Date
    26.03.2006
    Posts
    19

    Default SiliconImage VIA SiS chipsets and WPCREDIT tool vs StarForce

    There are efficient methods to defeat StarForce on systems with SiliconImage, VIA or SiS controller. The main idea is to reprogram controller to report false vendor id, device id and other parameters. Personally I have VIA chipset mainboard and this method allows me to run all StarForce protected games without unplugging CD drive or switching it off in device manager. All I have to do is to run WPCREDIT and edit one number (or use WPCRSET to automate this process during each system startup). Here are the articles (they are in Russian so you have to use some online translator):
    SiliconImage vs StarForce
    VIA vs StarForce
    SiS vs StarForce

  2. #2

    Default

    Cuddles perhaps you can put it in a better perspective on how you do it cuz so far by reading all that russian text I got the impression that it's a very good method to avoid actually opening the chasis. If you can please put into detail what you do I'd appreciate it.
    The last of the best, the death of the rest. Hitman Forever...

  3. #3

    Default

    I tried to translate it with Wordlingo, but I don't really understand how it works. Maybe its due to the massive russian words in it, so is it possible for you to make a detailed English guide for this?

  4. #4
    New User
    Join Date
    26.03.2006
    Posts
    19

    Default

    I am not interrested in translating all these articles but here is what I do to get rid of that "Insert disc into another drive" message. I have a VIA KT266A chipset mainboard, but I think it will be the same for other VIA chipsets.

    1. Run WPCREDIT, press Ctrl+D to select device, choose IDE Controller. You will see something like this:
    http://images.people.overclockers.ru/62040.png
    2. Registers 02, 03 (red frame) hold device id (look at the "Device ID" label at the top of the window). StarForce uses this id to find out if it can communicate with device directly, bypassing Windows drivers.
    3. Registers D2, D3 (second red frame) are called device id backdoor registers. They are used to change contents of registers 02 and 03 (device id). Now all you need to do is to change this number using Edit button. For example, I have device id 0571 and I change it into 0572.

    The good thing here is Windows does not react to device id change. It looks like the only affected program is StarForce protection.
    If you want to change registers at every boot you can use WPCRSET.
    The method is the same for SiS and SI controllers but it uses different registers of course.

  5. #5

    Default

    Thx alot, I will try it later, I have a nforce 2 mobo and it detects the drives and I have a really really strict no-opening-the-chasis-ever-ever-ever-ever ... ever or loose waranty. :-D
    The last of the best, the death of the rest. Hitman Forever...

  6. #6
    New User
    Join Date
    26.03.2006
    Posts
    19

    Default

    Don't try it on nforce2 - it won't work. This method is intended for SiliconImage, VIA and SiS controllers only.

  7. #7

    Default

    Dammit. Well guess there's no other way than to wait for IDEblocker, if it's gonna come like DT4.0 came then guess I'll have to find a way to bypass SF5.9 by the time it's out.
    The last of the best, the death of the rest. Hitman Forever...

  8. #8

    Default

    Quote Originally Posted by Cuddles
    I am not interrested in translating all these articles but here is what I do to get rid of that "Insert disc into another drive" message. I have a VIA KT266A chipset mainboard, but I think it will be the same for other VIA chipsets.

    1. Run WPCREDIT, press Ctrl+D to select device, choose IDE Controller. You will see something like this:
    http://images.people.overclockers.ru/62040.png
    2. Registers 02, 03 (red frame) hold device id (look at the "Device ID" label at the top of the window). StarForce uses this id to find out if it can communicate with device directly, bypassing Windows drivers.
    3. Registers D2, D3 (second red frame) are called device id backdoor registers. They are used to change contents of registers 02 and 03 (device id). Now all you need to do is to change this number using Edit button. For example, I have device id 0571 and I change it into 0572.

    The good thing here is Windows does not react to device id change. It looks like the only affected program is StarForce protection.
    If you want to change registers at every boot you can use WPCRSET.
    The method is the same for SiS and SI controllers but it uses different registers of course.

    thank you, it works for me with prince of persia 3

  9. #9
    New User
    Join Date
    04.04.2006
    Posts
    2

    Default

    Sorry for that stupid question but how it works for you - you mount your pop3 image and thats it? Should i let starforce to install itself? it aint working for me - ive changed device id using wpcredit but starforce still saying that serial number that i entered is wrong ( that it doesnt correspond with cd in my drive )
    i have via based motherboard ( kt400a).

  10. #10

    Default

    Quote Originally Posted by TOJA
    Sorry for that stupid question but how it works for you - you mount your pop3 image and thats it? Should i let starforce to install itself? it aint working for me - ive changed device id using wpcredit but starforce still saying that serial number that i entered is wrong ( that it doesnt correspond with cd in my drive )
    i have via based motherboard ( kt400a).
    How did you create your image (which program/settings)?

Page 1 of 2 12 LastLast

Bookmarks

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •