ryan_the_leach Posted June 30, 2006 Share Posted June 30, 2006 Any ideas on software which can compare two directorys to each other to find changes, im trying to work out if its possible to hex the setup so i can remove redundant copys of files, to fit more on the disc Link to comment Share on other sites More sharing options...
Delprat Posted June 30, 2006 Share Posted June 30, 2006 you don't need to "hex" anything, just use cdimage to create an optimized ISO before burning.read the guide :http://flyakite.msfn.org/++ Link to comment Share on other sites More sharing options...
ryan_the_leach Posted June 30, 2006 Author Share Posted June 30, 2006 i just ccame to check on the thread to say if it could be locked or deleted becuase i found what i was looking for, thanx anyways for the reply, probably if i checked back sooner it would of saved myself some hunting Link to comment Share on other sites More sharing options...
The008 Posted July 8, 2006 Share Posted July 8, 2006 hey don't worry, you only need to Optimize the ISO, so it will write the same file only one time, so you can put many XP CDs in only 1! NO NEED TO HACK/EDIT the setup files! Link to comment Share on other sites More sharing options...
ladude626 Posted July 9, 2006 Share Posted July 9, 2006 I had the same question myself and I used SFV Creater 2.7 to compare the difference between different types of Windows XP, here's what I found:Difference between OEM and CORP version of Windows XP Pro:"I386\DPCDLL.DL_""I386\EULA.TXT""I386\OEMBIOS.BI_""I386\OEMBIOS.CA_""I386\OEMBIOS.DA_""I386\OEMBIOS.SI_""I386\PIDGEN.DLL""I386\SETUPP.INI"Difference between different OEMs (eg. HP vs. Dell):"I386\OEMBIOS.BI_""I386\OEMBIOS.CA_""I386\OEMBIOS.DA_""I386\OEMBIOS.SI_""I386\SETUPP.INI" Link to comment Share on other sites More sharing options...
Innocent Devil Posted July 11, 2006 Share Posted July 11, 2006 (edited) DPCDLL.dll for validating the install by checking the cd key (may be of slight change in algo or somewhat ....!! )may be (Digital Productid Check) PIDGEN.dll contains the Public Key for checking the Product key (public key is different for diff version)OEM* activation details for each product (generic for Retail and Corp ,have fixed BIOS signatures for the system along with the CD came in case of OEM)SETUPP.ini just open it ...u can see the PID base numebrs and a hashPID last three digits indicate000 ==RetailOEM == OEM270 == VLKthese used for calculating the PIDu can see that the PID's first set of digits are always these 5 numbers EULA.txtopen the two and u can visibly see the diff !!!All these files are related to windows product activation so it varies for diff versionsto know more about it go Licenturion Edited July 11, 2006 by Innocent Devil Link to comment Share on other sites More sharing options...
Delprat Posted July 11, 2006 Share Posted July 11, 2006 DPCDLL.dll for validating the install by checking the cd key (may be of slight change in algo or somewhat ....!! )may be (Digital Productid Check) DPC = Deferred Procedure Callhttp://www.sysinternals.com/information/advanceddpcs.htmlIt can also be "Dead PC", or anything you taste Anyway, if one copies DPCDLL.DLL, PIDGEN.DLL, SETUPP.INI, OEMBIOS.* and some others (LOL) from one disk to another, he can use the key of the first disk on the second one.This is on the "things not to do to stay legit" list !++ Link to comment Share on other sites More sharing options...
Innocent Devil Posted July 11, 2006 Share Posted July 11, 2006 @Delprat thanx dudeactually i don't what it is ... ,that was a wild guess Link to comment Share on other sites More sharing options...
gamehead200 Posted July 11, 2006 Share Posted July 11, 2006 Use the board's SEARCH function or the Google Search function above.This question has been answered many times before.[ Closed. ] Link to comment Share on other sites More sharing options...
Recommended Posts