10,744
edits
 | If you plan to make a YouTube video or other content using bootlegs downloaded from our site, although we can't and won't force you to do anything, we greatly appreciate attribution for the large amounts of time and effort we spend finding these bootlegs. Thank you! |
Talk:Main Page: Difference between revisions
no edit summary
Undefishin (talk | contribs) No edit summary |
Undefishin (talk | contribs) No edit summary |
||
| (20 intermediate revisions by 2 users 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
(Feel free to put newlines when necessary.)
== Changes from (reference original_os from infobox) ==
(This section, along with Software, and Notes, should
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 ==
{{Not met}}
{{Not met
== Where to look to obtain information for... ==
===== creator =====
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.
===== country =====
===== size, download =====
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.
===== othervers =====
Try looking around for other versions.
===== archiveadd =====
; You will need to be in the Crusty Windows Discord server to access these destinations.
* [https://discord.com/channels/1070582862698520667/1070840062578794627 #collection-updates] (very useful resource, this will usually do the trick)
* [https://discord.com/channels/1070582862698520667/1109895513366593579 #bootleg-submissions] (there will be usually a comment saying "Added" or
* [https://discord.com/channels/1070582862698520667/1070591801272062024 #bootleg-submissions-archive] (the original bootleg-submissions channel, before it got replaced with a forum channel for easier organization,
===== timebombdate =====
==== Characteristics of a bootleg, particularly... ====
===== The tools used to make a bootleg =====
To confirm if a bootleg was made with nLite or not, look
* For any <code>
: <
: <
: <
* The version number may be different - there have been cases where bootlegs were made with really old versions going back to 1.0 or even beta versions of nLite. You should include this version number in the "This ISO was made using ..." portion if possible. Ditto for all the other tools with visible version numbers.
* Any files named <code>nlite.inf</code> and all INF files for the keywords "nLite" including comments (usually at EOF) 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> in <code>I386</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, and if it contains a comment with the keywords "Windows Unattended CD Creator" as the first line of the file.
* A file named <code>RunOnceEx.js</code> or the entry <code>wucdcreator="wscript.exe %systemroot%\RunOnceEx.js"</code> or similar in <code>WINNT.SIF</code>. This is the most used feature of Windows Unattended CD Creator, its software post-installer.
To confirm if a bootleg was made with VistaPE or not, look in:
* A file named <code>VISTAPE.CD</code> in the CD root
To confirm if a bootleg uses any boot selectors or not, look in:
* 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
* A file named "AUTORUN.ARU" (''Longtion Autorun (Pro (Enterprise (II)))'')▼
To confirm the program used to make a bootleg's autorun:
* Look for any files pertaining to the autorun maker itself, such as:
* Check the file's version information. This will usually do the trick, in most cases▼
: A file named "AUTORUN.CDD". Any "Docs" / "dat0X/ap0X.dat" entries, in an "AutoPlay" folder. (''AutoPlay Media Studio'', most common)
* Search for strings in the binary itself. It may lead you to extra clues such as version information which may be inaccessible otherwise▼
: A file named "SETUP.INI" with any mentions of "Авторан для Windows", or sections "Default" and any "Item" entries (''Advanced CD Launcher'' by Boa Software, mostly seen in Russian bootlegs)
* ''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"▼
▲
: A file named "AUTORUN.APM" (''AutoPlay Menu Builder'')
: A file named "AUTORUN.EXE" which is packed with ASPack, the Visual Basic 6 runtimes and OCX files in the root, along with any "Data" folders with files with "pic" and "esr" extensions (''Power AutoPlay Menu Creator'')
▲* ''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"
▲* Search for strings in the binary itself. It may lead you to extra clues such as version information which you may not be
* You may use any binary checking tool, such as Detect It Easy, to help you
===== 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:
: Most software programs. Usually repacked by ricktendo64
: DirectX, Microsoft .NET Framework, any other updates
: "WGAV", "WGAN", "Microsoft Update Engine", "XP SP3 Update Pack", "OUE/OGA". Addons usually by xable
: 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:
* Usually, they will be in the SVCPACK folder, but be sure to check <code>SVCPACK.INF</code>. It may be especially important if it's in a different folder (CatalogSubDir entry), the specific order of installing programs (SetupHotfixesToRun section), product catalogs (ProductCatalogsToInstall section) etc.
== Linux articles ==
And as for places to look, here are a few good places to look:
You must order the screenshots in the gallery in the way that the portions down below are ordered. You can only take one of each screenshot, and if there are multiple sections of one portion, it doesn't exclude it from capture. The Desktop, Start Menu, and Demo portions must always be included, even if it's unchanged from stock. Do not attempt to alter or change anything in the bootleg, and try to keep everything as is in its default configuration. An exception to this is if the resolution is raised to 1024x768.
; Pre-boot selector / Boot selector (''if it exists'')
; Text-mode setup (usually the only changes here are string changes, that is better suited for the 'Changes' section and not worth screenshotting)
: Partition screen, format screen, copying screen (ditto)
; Graphical setup
; Boot screen
; Pre-OOBE (''
; OOBE video (''if it exists, some bootlegs omit this'')
; OOBE (''if it exists, some bootlegs omit this'')
; Login screen
; Post-login (''anything that is set to run on startup, such as a WPI, post-install script, or other such'')
;
; Start
; Demo (''a Demo portion involves showcasing various system and user information dialogs, where there will usually be changes. the list of the programs involved will be included in its own listing'')
: System Properties
: Support Information (''if it exists, then include it'')
: Autorun splash, and post-exit screens (''if any'')
; WPI (''if the bootleg has one'')
: The WPI installation
; A picture of an Explorer window of the CD root or the C drive (''if it has a custom folder background'')
=== Some other things you need to know ===
* Try to maintain a consistent resolution of 1024x768 across all screenshots, if possible. The reasoning behind that specific resolution is because it is a good balance of size and content. (that being, it's not too big or small, and just about everything else will properly fit in that resolution without any cramming).
* Don't forget to specify the default theme's name when you're captioning the start menu image. You can find it by simply opening the Display Properties applet and looking in the theme selector.
* If you're reviewing a Windows Vista+ bootleg, if the System Properties window has changed branding, and you have the About Windows dialog open, move the About Windows dialog to down to the left and the System Properties window up to the right. This will make sure all of the branding will be shown, otherwise the About Windows dialog will cover part of it and not show everything.
* When you're operating the WPI in a bootleg, you should select the full configuration to install every program available. This makes sure that you get the most out of the preincluded programs. You don't necessarily have to do this, however. Make sure not to screenshot the WPI in full configuration - if it isn't already set by default.
=== Structure of a themes gallery ===
What is also important to capture are the themes of a bootleg, as there are many bootlegs with many themes (and we do mean many, there are [[Windows 7 Infinium Edition|known bootlegs]] with more than 100 themes), so this is how to deal with it:
You must take a screenshot of the theme by applying the theme in the theme selector, then you open the Start menu and then capture the screenshot.
As for labeling it, you do it like this: <code>(Original OS name) (Bootleg OS name) (Theme name) theme.png</code>.
As for captioning it in the gallery, you do it like this: <code>"(Theme name)" theme</code>. You can also append the internal theme name if the theme selector's name doesn't accurately represent what it is, but it takes more time to caption in bulk. Example: <code>"(Theme name)" theme ("(Internal theme name)" theme)</code>.
If the theme has any other names, you title it like this: <code>"(Theme name)" theme ("(Theme name 1)" theme, "(Theme name 2)" theme)</code>.
It is generally recommended to leave everything in its default configuration, and not change anything when you're capturing bootleg screenshots.
On Windows, you can also hold ALT + Print Screen to capture the window. I don't know when this was added but I know it works on XP, 7, and 10. [[User:Dartz|Dartz]] ([[User talk:Dartz|talk]]) 20:46, 7 February 2023 (UTC)
As for the Alt + PrtScr feature, the best way to use this feature is to take advantage of the shared clipboard feature found in the guest additions of hypervisors such as VirtualBox, VMware, etc. First, you enable the Shared Clipboard feature itself, then you configure it to be able to copy from Guest to Host. (or Bidirectional, either one). Then, you paste the clipboard's contents into an image viewer/editor (such as IrfanView, which I use) and save it there. As for labelling the screenshot, again, see "Labelling your screenshots and formatting it in its own gallery". --[[User:Undefishin|Undefishin]] ([[User talk:Undefishin|talk]]) 11:57, 9 December 2023 (UTC)
== How to deal with multiple bootlegs with the same name ==
| |||