Talk:Main Page: Difference between revisions

no edit summary
No edit summary
No edit summary
(One intermediate revision by the same user not shown)
== Description ==
 
The bootleg is a modified (reference original_os from infobox) ISO. (Specify any integrations the bootleg comes with. For example, the DriverPacks version, RyanVM, etc). It comes with its own boot selector (if any). (Describe the purpose of the bootleg and what is added and what is removed, in brief). It comes with its own autorun (if any), and WPI (if any). It is (unattended (and/or) preactivated).
 
(if available:) The ISObootleg was made using (bootleg making software, for example, nLite) on (Host OS, if available), and (if other software was used to aid in parts of the mod's development, e.g. autorun software/WPI, include it here). (Mention ISO creation date which you can easily get in PowerISO, tools used to make the OOBE video, or anything else.)
 
(Feel free to put newlines when necessary.)
 
== Changes from (reference original_os from infobox) ==
 
(This section, along with Software, and Notes, should onlybe includesplit ainto list3 sections. InMinor itChanges, youChanges shouldin document all the places changes were made, such as the textpre-modedesktop and graphical setup, boot screen, OOBE (including the pre-OOBEprocedures, and the OOBE video), login graphics, themes, wallpapers, screensavers, icons, cursors, sounds, fonts, avatars,Look and OEM brandingFeel.)
 
In it, you should document all the places changes were made in the respective sections, such as the text-mode and graphical setup, boot screen, OOBE (including the pre-OOBE, and the OOBE video), login graphics, themes, wallpapers, screensavers, icons, cursors, sounds, fonts, avatars, and OEM branding.
 
Where goes into which ones should be clear as a result of these names being chosen, and therefore this new policy being inducted.)
 
== Software ==
(The software listing goes here. The software list needs to be sorted alphabetically, and by software type, in their own sub-sections. Acceptable software types are Customization Utilities, Updates, and Screensavers. This includes the WPI, which will be explained in more detail below this comment.)
 
(If the bootleg has a WPI, or "software packs", add a new sub-section named "Software on the CD", and put them in this section. If it's software packs, add another sub-section under "Software on the CD" named "Software Pack 1", if there is more than one, then make more than one section, and then include all the bundled software from there. The sorting should be exactly how it should be shown in the WPI.)
 
== Notes ==
(If there is nothing to note, then it's optional.)
 
(The notes listing goes here. If you can find anything particularly interesting about the bootleg you are making an article on, then feel free to put it in here! The first places you should look are: Full names, organizations, computer names, workgroup names, what interesting things are in the CD root, if the CD has its own icon, anything notable about the autorun, etc.)
 
This section is subject to the same subsection policies. The names to use are Bootleg Quirks, CD Contents and Other Info and WINNT.SIF metadata. The last section depends on what OS the bootleg is based on, which will likely vary.)
 
== Gallery ==
==== 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:
* For any <code>I386\WINNT.SIF</code> or <code>WINNT.ORG</code> file and look for a "Generated by nLite" line at the beginning of the document, for example:
: <code>; Generated by nLite 1.3</code>
: <code>; Generated by nLite 1.4.9.1</code>
: Any entries starting with "RVM". This is a reference to "RyanVM", a person well-known for making nLite addons and update packs
: Any entries starting with "Z-". This is a reference to "Zab". Mostly seen in Russian bootlegs
* 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.
 
To confirm if a program was integrated via the setup hotfix feature: