Hi, why you did the same fault, as alcohol/dt did too??
Also, you have the same wrong controller position, as Alcohol or Daemon tools.
Look self, in reality there do not exist any SCSI controllers, which
have same node position.
How Starforce checks for it, first it checks so: give me the parent
node of this cd-rom drive, so starforce knows, this cdrom drive belong
to this scsi controller, now after it starforce asks again, give me
the parent node of scsi controller. Also if it were an real SCSI
controller, starforce wouldn't get any parent response, thus in real
scsi controller there is no additional bus belonging to this scsi
controller. So in your case Starforce sees, aha, something like it
doesn't exist in the nature of Scsi controllers and blacklists the
drive belonging to SCSI controller and additional bus.
What i have done with unblacklisting, as you already understood, just
setting the GUID to another id. That is just temporary fix, it doesn't
unblacklist drive in reality. Just starforce sees this additional bus
not so, as it should, but if they want, they could fix it too. So that
way is not the way you should go. Just rewrite your drivers so, that
you get standalone SCSI controller without parent bus over it. Looks
in newer versions of Gamejack, that is the right way you should go.
Than carbon crack of drivers is actual just for older drivers and game
versions, someone maked it public just because they saw already in
newer starforce versions, that the functions are intercepted, so there
was no reason more to hide this crack. So this is not the real help
for you, if it doesn't work with newer versions. Mini image is ok, the
file system blocking can be overrided with such way forever, but it
works just so long the starforce protection doesn't check for sectors
integrity.
In newer starforce version, where is additional content check, you are
not allowed to use mini images, else the protection wouldn't see
cutted and needed content, so you have to use full image, but in this
case the file system blocking works.
There are few ways to override it, anyway the driver has to be
rewritten, but nothing is better, as to make your own sector accesses
to any harddrive, make your own geometrical transformation and use
your own file system implementation, FAT16, FAT32, NTFS and CDFS. So
you can access files on the drive on your way and not ask windows to
do it.
1. Make your own sector accesses, starforce cant disturb it, because
it has sector accesses too.
2. Then geometrical transformation can you get from universal ide
driver, there are free sources, so you can look and extract this
transformation from sources.
http://alter.org.ua/soft/win/uni_ata/index.php?lang=en&
3. Now the important part, file systems, linux contents sources where
you can extract all sources of file systems for reading files in
FAT16, FAT32, NTFS and CDFS.
If you had something like it, you would have the super weapon against
starforce :-)
The another part is the deactivating ide drives, ok, if you can
override starforces high irql, just as example, by forcing to set your
threads in the task planer, then you could go an better way as just
deactivating ide channels or drives separately.
Every time starforce wants to check for atapi on ide and cd check, it
stops all windows ports accesses to ide controller and can do its work
without to be disturbed, if they wouldnt do it, they would crach the
system. So, that is the point, where you can see, aha, fucking
starforce want to check for ide and at this time you can deactivate in
pci space whole ide controller, so starforce wouldnt be able to get
access to ide controller, and when starforce lets again the windows os
to make its ports access to ide controller, there you have quickly to
activate the controller again. This way of deactivating would work for
longer time and you don't need to collect datasheets to know, how to
deactivate any channel separatelly by different vendors, thus the
deactivating of any pci device in pci space is standart for any
device. You could look just for all controllers in pci space with IDE
subclass 01 01 ** and deactivate and reactivate it by changing just
one bit.
PS: you are allowed to use StarForce Nightmare.
But anyway, if you want to fuck starforce in its ass :), you should
do, what i have described. But if you are able to do it.
Bye
threads in the task planer, then you could go an better way as just
deactivating ide channels or drives separately.
Every time starforce wants to check for atapi on ide and cd check, it
stops all windows ports accesses to ide controller and can do its work
without to be disturbed, if they wouldnt do it, they would crach the
system. So, that is the point, where you can see, aha, fucking
starforce want to check for ide and at this time you can deactivate in
pci space whole ide controller, so starforce wouldnt be able to get
access to ide controller, and when starforce lets again the windows os
to make its ports access to ide controller, there you have quickly to
activate the controller again. This way of deactivating would work for
longer time and you don't need to collect datasheets to know, how to
deactivate any channel separatelly by different vendors, thus the
deactivating of any pci device in pci space is standart for any
device. You could look just for all controllers in pci space with IDE
subclass 01 01 ** and deactivate and reactivate it by changing just
one bit.
PS: you are allowed to use StarForce Nightmare.
But anyway, if you want to fuck starforce in its ass :), you should
do, what i have described. But if you are able to do it.
Bye
