Newsgroup: it.comp.hardware
Titolo: Info su DAO

Vorrei sapere se può essere untilizzato con i masterizzatori IDE, io ho un
Mitsumi, posso con questo copiare i cd della Play. Dove posso trovarlo in
rete? In versione totale non aggiornamente poichè non ne possiedo nessuna.
Grazie
Matteo (
ama...@tin.it
)

Se esiste dove posso trovarlo????
www.goldenhawk.com
ma non penso proprio supporti masterizzatori IDE...
ciao
as


non e' che sapete di qualche sito dove si possa trovare la versione
registrata in "prova".... o il numero di serie per provarla un po'....



DAO Crack Files by Bruno
Name: xOANON
E-mail: UCF-97
Serial #: 3781705909
Bruno & Simona
bruno_...@geocities.com

 prova, prova, dicono tutti cosi'...  :-)
Non esistono limiti di tempo per una prova!
Sono 2 anni che provo a rendere stabile WinShit 95.....
e ancora non ci sono riuscito!
Ciao
********************************
Angelo Russello
ci...@geocities.com
PAY ATTENTION PLEASE:
REMOVE "skassa" BEFORE REPLYING!!
********************************

Ciao e senza rancore.
Ciao, saluti dai criminali informatici......per ora ancora liberi come
l'aria!!
Bruno & Simona
bruno_...@geocities.com


bruno_...@geocities.com
Vi faccio presente che siete OT: non potevate postarli su
alt.crackers?
Ciao
as



No, perché ce li hanno richiesti qui....ma perché non leggete tutti i
msg prima di criticare??
Bruno & Simona
bruno_...@geocities.com

masterizzazione e farli beneficiare delle esperienze altrui.
Benissimo, sarebbe il caso di controllare questa notizia sulla Golden
Hawk, perché se fosse davvero così (ma io lo escluderei) sono
veramente ai limiti del legale....e di questa cosa bisognerebbe
parlare di più.
B.
Bruno & Simona
bruno_...@geocities.com

 Serial #: 3781705909
per quale versione 
vanno bene
questi dati?
 
Ciao!
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Angelo Russello - 
ci...@geocities.com
PAY ATTENTION PLEASE:
REMOVE "skassa" BEFORE REPLYING!!
just for laughin':"new feature in
winshit95...supports the bug mastering!"
////////////////////////////////////////


dISC-AT-ONCE REC. TOOLS (DAO) v3.1E 32-bit
Ciao anche a te!
Bruno & Simona
bruno_...@geocities.com
VESTIGIA NULLA RETRORSUM


--------------DCAE3F1F1A085B7F2209A7F4
Content-Type: text/html; charset=us-ascii; name="Daoinfo1.htm"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="Daoinfo1.htm"
Content-Base: "file:///D|/Varie/Psx/Daoinfo1.htm"
<HTML>
<HEAD>
<script language="JavaScript">
<!--
var roadmapWin = null;
function startRoadmap() 
{
  roadmapWin = window.open("","Roadmap",'toolbar=0,location=0,directories=0,status=0,menubar=0,scrollbars=0,resizable=0,width=235,height=400');
  if (roadmapWin != null) {
    if (! roadmapWin.opener) roadmapWin.opener = self;
    roadmapWin.location = "
http://members.tripod.com/adm/roadmap.shtml
"; 
  }
}
// -->
</script>
   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
   <META NAME="GENERATOR" CONTENT="Mozilla/4.0b5 [en] (Win95; I) [Netscape]">
   <META NAME="Author" CONTENT="Steve Jackson">
   <META NAME="KeyWords" CONTENT="PSX,swapmethod,swap method,pic,sony playstation">
   <TITLE>The Truth About DAO CRACKS</TITLE>
</HEAD>
<BODY BACKGROUND="bluepaper.jpg" onLoad="startRoadmap()">
<CENTER></CENTER>
<CENTER>
<H1>
<B><FONT FACE="UpstartSSi"><FONT COLOR="#FF0000"><FONT SIZE=+2>&nbsp;&nbsp;
</FONT><FONT SIZE=+3>The truth about CDRWIN / DAO cracks and s/n generators!</FONT></FONT></FONT></B></H1></CENTER>
<CENTER>
<H1>
<B><FONT FACE="UpstartSSi"><FONT COLOR="#FF0000"><FONT SIZE=+3>Read here
why they don't work</FONT></FONT></FONT></B></H1></CENTER>
<CENTER>
<H1>
<B><FONT FACE="UpstartSSi"><FONT COLOR="#FF0000"><FONT SIZE=+3>and how
to save your CDR's</FONT></FONT></FONT></B></H1></CENTER>
<CENTER><B><FONT FACE="UpstartSSi"><FONT COLOR="#FF0000"><FONT SIZE=+3></FONT></FONT></FONT></B></CENTER>
<CENTER><B><FONT FACE="UpstartSSi"><FONT COLOR="#009900"><FONT SIZE=+2>Don`t
use DAO 3.0e or higher! (Yet)</FONT></FONT></FONT></B></CENTER>
<CENTER><B><FONT FACE="UpstartSSi"><FONT COLOR="#009900">The serial Numbers
might work BUT Dao will not Burn CD`s correctly, just to piss you off!</FONT></FONT></B></CENTER>
<P>&nbsp;
<BR>Dear CD-R lovers &amp; haters,
<BR>the time has come to make clear some facts about the
<BR>anti-piracy protection introduced by Jeff Arnold in his
<BR>WinDAO (aka CDRwin) version 3.0E and higher. Of course
<BR>the same protection scheme is used in the DOS 32bit and
<BR>16bit console version.
<P>As some of you may have noticed, from that version the
<BR>executable (.exe file) size suddenly grew 100K! Just
<BR>100K is the size of the code introduced to improve the
<BR>protection against cracks and key-generators.
<P>First of all I'd like to specify a concept that will
<BR>look more clear at the end of this reading:
<P>!
<BR>! The ONLY way to safely use a "cracked" DAO (at least
<BR>all the new
<BR>! versions with the anti-piracy system) is...
<BR>! TO GENERATE a *GENUINE* *VALID* registration code, a
<BR>code that
<BR>! makes the program thinks: "Oh, this is a good one,
<BR>generated by my
<BR>! dad Jeff" :)
<BR>!
<P>--------------------------------
<BR>How DAO performs key validation
<BR>--------------------------------
<P>It's important to understand that the key validation is
<BR>of the "distributed" kind: in other words the program
<BR>does not contain a single routine that takes user name,
<BR>company name, then calculates the registration code and
<BR>finally compares it with to the one supplied by the
<BR>user... This is the simple method used by most of the
<BR>silly shareware progs you can download from the net.
<P>DAO uses a different approach to the key validation
<BR>problem.
<BR>First there's a basic routine that makes a simple check
<BR>and reduces the number of keys accepted to a subset.
<BR>This subset is small enough to avoid the risk for a
<BR>legitimate user of the program to trigger the "Trojan
<BR>Horse mode" (see later) if he does a mistake when
<BR>typing the user code, BUT it's still too large to try a
<BR>brute-force guessing of the code.
<P>#
<BR># How do this routine work ?
<BR>#
<P>Quite simple.
<BR>A) The file CDRWIN.DAT (or the corresponding file in
<BR>the DOS version) is decoded. This file uses a simple
<BR>XOR encryption...
<BR>B) The "NAME" and "COMPANY" fields are extracted, from
<BR>this data (again with the XOR/SHR method) the
<BR>validation routine generates two dword which are mixed
<BR>together to produce the so called "mix-code": THIS CODE
<BR>HAS NOTHING TO DO WITH A GOOD REGISTRATION CODE!
<P>If the software is not yet registered, the "NAME" and
<BR>"COMPANY" fields are read directly from the dialog-box
<BR>that appears when you click on the "UNLOCK" button.
<P>The mix-code is now "compared", (using an "ad hoc"
<BR>algorithm) to the registration code found in CDRWIN.DAT
<BR>or typed by the user in the dialog-box.
<BR>The word "compared" has quotation marks because it's
<BR>not a real arithmetical comparison: it's more like
<BR>verifying if the mix-code is a divisor of the
<BR>registration code. This is not an *exact* description
<BR>but it's important for you to understand that at this
<BR>point of the verification procedure the progran accepts
<BR>a set of reg-codes, NOT ONLY ONE reg-code.
<P>If the comparison gives a positive result (the code
<BR>seems to be true), DAO fakes the user telling "software
<BR>unlocked" and will apparently behave as the registered
<BR>version...BUT when the user try and record something
<BR>with his CD recorder, if the code was not a genuine one
<BR>(this is determined by consecutive approximations
<BR>during the program execution), the resulting CD is
<BR>completely unreadable and you've just another coaster
<BR>to add to your collection :)
<P>You can tell if a code is not valid only when the
<BR>program is writing to the CD, because it's only during
<BR>this operation that the write buffers are filled with
<BR>random bytes instead of being filled with the ISO image
<BR>data.
<P>##
<BR>## So what about all the serial numbers by PC97
<BR>(PHRoZeN CReW), PerlX
<BR>## TripleZ, FRENCH HACKERS floating around the net ???
<BR>##
<P>All these s/n are *FAKES* and can't work with any
<BR>version of DAO/CDRWIN higher than 3.0D. Don't even try
<BR>to use them with 3.0E, 3.1A, 3.1B, 3.1C1, 3.1C2, 3.1D
<BR>and future versions (unless you need some golden cup
<BR>holder)!
<BR>In our tests we discovered that sometimes, even if
<BR>CDRWIN has been unlocked using a mix-code, you may
<BR>still be able to succesfully burn a CD if you're
<BR>copying files on-the-fly from hard disk to CDR... This
<BR>is probably the only recording mode not affected by J.
<BR>Arnold's f*cking protection, anyway try it at your own
<BR>risk!
<P>These are not good serial numbers but only "mix-codes"
<BR>calculated using the above-mentioned routine.
<BR>Let go back to the "divisor" example: a number is
<BR>divisible by itself, then a mix-code will be accepted
<BR>as part of the acceptable keys set... but will trigger
<BR>the "CDR Killer" mode.
<BR>This preliminary verification routine can also accept
<BR>XORed mix-codes,
<BR>for instance:
<P>CRCK still the best!
<BR>and.. PHRoZen CReW suckS
<BR>1893910482&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;-- WinDAO MIX-CODE
<BR>(FAKE!)
<P>May also be accepted as 1893910482 = 0x70E2C7D2,
<BR>0x70E2C7D2 xor 0x862100 = 0x7064E6D2 => 1885660882 in
<BR>decimal..
<P>then...
<P>CRCK still the best!
<BR>and.. PHRoZen CReW suckS
<BR>1885660882&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;-- WinDAO xored
<BR>MIX-CODE (ANOTHER&nbsp;&nbsp;&nbsp; FAKE!)
<P>The second code is the result of a XOR operation on the
<BR>first code: both codes will be accepted and, again,
<BR>both codes are invalid!
<P>Mix-codes are SYMMETRICAL, so the previous data can
<BR>also be entered in this order:
<P>and.. PHRoZen CReW suckS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;
Name &amp; Company fields
<P>CRCK still the best!&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt; are inverted
<BR>3352457442&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt; 0x70E2C7D2 ROR 16 =
<BR>0xC7D270E2 = 3352457442
<P>Of course a genuine and valid WinDAO code isn't
<BR>symmetrical!
<BR>As a rule of thumb, if you are looking warez sites or
<BR>NG for a valid registration code or you think to have
<BR>found one that looks good, do the following
<BR>verification before trying any operation that involves
<BR>writing to a CDR. First enter the registration data
<BR>exactly as reported by the author of the "crack", then
<BR>ask yourself: is my code symmetrical ? Find the answer
<BR>by simply entering the COMPANY when asked for NAME and
<BR>the NAME when the COMPANY is required, then XOR the
<BR>original s/n and use the result as your new s/n. If the
<BR>program says "unlocked an fully functional" in both
<BR>cases, your code is a fake!
<P>#
<BR># Then, where is the *real* code validation routine
<BR>located ?
<BR>#
<P>While the program is running, the validity of the
<BR>registration code is checked several times in many
<BR>different points. Many memory locations are involved in
<BR>this validation and some of them are used only to mix
<BR>things up and to make life harder to crackers...
<BR>What we're trying to make clear is that a
<BR>brute-force/memory-compare&amp;patch solution is absolutely
<BR>impossible with this kind of protection scheme.
<BR>Who wants to spend so many hours (maybe days or weeks)
<BR>to release a crack that can be defeated by the author
<BR>of&nbsp; DAO in five minutes ? Jeff would only have to
<BR>release a new recompiled version, maybe slightly
<BR>different in the data structures...and it would take at
<BR>least another week to write the new crack!
<P>There is only ONE safe way to get rid of all the
<BR>f*cking code checks used by this software: to generate
<BR>a perfect, true, real authentic registration number.
<BR>CRCK is working on it, but all I can say at the moment
<BR>is that we are VERY near to the final solution...STAY
<BR>TUNED!
<BR>Meanwhile we decided to write this message to put the
<BR>word END to all the BULLSHITS we read in this and other
<BR>cracks-related ng! And when we say bullshits we mean
<BR>things like: "Thiz reg-code worked with version 3.1C1
<BR>but works no longer with version 3.1C2...".
<BR>Serious crackers should concentrate on producing *few*
<BR>high quality tested cracks for "killer" applications,
<BR>not thousands of patches for useless programs dedicated
<BR>to computer-incompetent people! Not to mention the
<BR>blamewothy attempt to mask some gross mistake or the
<BR>inability to crack a particular software by spreading
<BR>false rumours...
<P>We strongly suggest the readers of this message to wait
<BR>for the release of our *real working* key generator,
<BR>meanwhile if you want to test the various registration
<BR>codes that periodically appear on this and other ng,
<BR>use one of the thousands of fake-generators available
<BR>on the net and save your CDRs (see above for detailed
<BR>explanations). Even if the code pass our test (reversed
<BR>data and XORed s/n are not accepted), you're not still
<BR>100% sure because the original code could have been
<BR>already XORed by the lamer who posted it on the
<BR>ng...Remember that in software piracy the basic idea is
<BR>TRUST-NO-ONE (uhmmm where did I hear this before???)
<BR>For example what have the 3 CRCK members Mr.Joiz,
<BR>MadMax and maGO to do with a legitimate Taiwanese DAO
<BR>customer called "Zoji Madago" ? :=)))
<P>Ok, it's the end of this very looong posting :) We
<BR>really hope to have made things a bit clearer...just
<BR>let us say a big HELLO and THANKS to all our friends
<BR>who supported us for all these many years.
<P>Mr.Joiz &amp; MadMax of CRCK
<BR><B><I><FONT FACE="Arial,Helvetica"><FONT COLOR="#0000FF"><FONT SIZE=-1>Email
me at&nbsp; <A HREF="mailto:
ja...@athene.co.uk
">
Ja...@athene.co.uk
</A></FONT></FONT></FONT></I></B>
<P>&nbsp;
</BODY>
</HTML>
--------------DCAE3F1F1A085B7F2209A7F4--

God bless you!!!


msg prima di criticare??
Siete OT lo stesso anche se ve lo hanno chiesto qui! Ma f@@a!
Ciao
as