13,824
edits
Talk:Main Page: Difference between revisions
no edit summary
Undefishin (talk | contribs) No edit summary |
Undefishin (talk | contribs) No edit summary |
||
|
==== Infobox parameters, particularly... ====
===== forked_from =====
If you've looked at a bootleg before and then check another bootleg, and if you notice any similarities between the two, then you should look for more evidence to confirm if it's forked or not. Try comparing the two ISO's together and doing some digging. Good examples of forked bootlegs are [[Android XP]] vs. [[Skype XP]], and [[Windows 7 FaceBook Edition 2012]] vs. [[Windows 7 Angry Birds Edition]].
===== release_date =====
* [[CrustyWin Wiki:Changelog|The Wiki Changelog]]
* The Wayback Machine (see [[CrustyWin Wiki:Changelog|the Wiki Changelog]] for details)
* [[User:Yellows111/All Bootlegs By Filename/XP|Yellows' XP bootlegs by filename]] (to get a general idea of the release date)
* Simply ask around (it's always faster to look for it yourself, but you really won't get an answer anywhere else in some cases)
===== timebombdate =====
Use the same method you use to find the build number of a beta build. If you don't know, then just look in the system files for a version number and you'll find it. Or better yet, use Winver to get the build number. Then it's just a matter of looking the build up and getting the timebomb date. BetaWiki and other such sites will usually have it.
==== Characteristics of a bootleg, particularly... ====
===== The tools used to make a bootleg =====
To confirm if a bootleg was made with nLite or not, look in:
* <code>I386\WINNT.SIF</code> and look for a "Generated by nLite" line at the beginning of the document, for example:
: <pre>; Generated by nLite 1.3</pre>
: <pre>; Generated by nLite 1.4.9.1</pre>
: <pre>; Generated by nLite 1.4.9.3</pre>
* Any files named <code>nlite.inf</code> and all INF files for the keywords "nLite" in <code>I386</code>
* The line <code>"rundll32 advpack.dll,LaunchINFSection nLite.inf,U"</code> in the file <code>cmdlines.txt</code> in the folder <code>$OEM$</code>. This will also confirm the existence of <code>nLite.inf</code>, which is the file that holds the component tweaks done by nLite according to the user.
To confirm if a bootleg was made with Windows Unattended CD Creator or not, look in:
* A file named <code>settings.txt</code> in the CD root
To confirm if a bootleg uses any boot selectors or not, look in:
* The bootleg's bootloader itself, obviously
* Any folders named "EZBOOT" (''EasyBoot''), "AIRBOOT" (''Aero Loader'') "BCDW" (''Bootable CD Wizard'')
To confirm the program used to make a bootleg's autorun:
* Check the file's version information. This will usually do the trick
* ''For 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"
== Linux articles ==
| |||