13,066
edits
Talk:Main Page: Difference between revisions
no edit summary
Undefishin (talk | contribs) No edit summary |
Undefishin (talk | contribs) No edit summary |
||
|
* Autounattend.xml on the CD root, if it has this string <code><nowiki><!--</nowiki>This answer file generated by RT Seven Lite<nowiki>--></nowiki></code> or not.
* <code>HKEY_LOCAL_MACHINE\Software\RT 7 Lite</code> in the install image's registry data. You can either load it offline on your computer or look for it using the bootleg itself.
* fppset.inf in the WINDOWS directory, and RTSLCS.dll in the System32 directory (both in the install image, latter useful if the author removed the CD root session files, usually they forget to also remove RTSLCS.dll)
To confirm if a bootleg was made with NTLite or not, look for:
* The bootleg's bootloader code itself, obviously
* Any folders named "EZBOOT" or "CDBOOT" with any files with a EZB extension (''EasyBoot'', most common), "AIRBOOT" (''Aero Studio'', also common) "BCDW" (''Bootable CD Wizard'', mostly used in Russian bootlegs), or "BOOT\cdshell.ini" (''CDShell'', uncommon) in the CD root
* Watermarks in the ISO image (EasyBoot will leave one in the ISO image)
To confirm the program used to make a bootleg's autorun:
* Look for any files pertaining to the autorun maker itself, such as:
* ''For autoruns made with StartCD:'' Click the program's icon at the top left of the program window, or right click the program in the tasklist, and click "About"
* Check the file's version information
To confirm the program used to modify the bootleg's ISO / what software was used to make the ISO:
* If you use the program PowerISO, open the ISO image you desire, go to Tools > View / Edit sector data..., then view the LBAs 16-18. There you will find:
===== The methods used to integrate various objects in a bootleg =====
To confirm if a program was integrated via an nLite addon:
* Your first stop is the <code>SYSOC.INF</code> file in the I386 folder. Look for an nLite entry, and check both directions of the entry for any entries pertaining to certain INF files. Some examples:
* Second is to look for the nLite session files (usually in the root of the CD or hidden somewhere) and scroll to the very end, it may reveal filenames which may be important to identifying and cataloguing them.
| |||