Talk:Main Page: Difference between revisions

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.)

(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.)

(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.)

(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.)

It can be difficult to determine the original author at times, but it should be pretty easy. Looking at the bootleg's submission entry and asking others about it can be pretty beneficial too. It is highly recommended that you consider using these methods as the last line of defense, if you really can't find a necessary piece of information.

You can find the size by literally just looking at the ISO itself. If it's already in the collection, it's asinine - look at the size column of the pertaining ISO entry, and use that as the size. The download link is really easy to find too - you can simply just copy and paste the link from the Crusty Windows collection.

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:

* Any folders named "EZBOOT" or "CDBOOT" with any files with a EZB extension (''EasyBoot'', most common), "AIRBOOT" (''Aero LoaderStudio'', also common) "BCDW" (''Bootable CD Wizard'', mostly used in Russian bootlegs), or "BOOT\cdshell.ini" (''CDShell'', uncommon) in the CD root

: A file named "AUTORUN.ARUCDD". (''LongtionAny Autorun"Docs" Pro/Enterprise "dat0X/IIap0X.dat" entries, in an "AutoPlay" folder. ('',AutoPlay seenMedia inStudio'', Vietnamesemost bootlegscommon)

: A file named "SETUPAUTORUN.INIARU" and any mentions of "Авторан для Windows", or sections "Default" and any "Item" entries (''Longtion Autorun for WindowsPro/Enterprise/II'', by Boa Software,usually seen in RussianVietnamese bootlegs)