Talk:Main Page: Difference between revisions

VisualWikitext
(only ever use project namespace when referring to (WIKINAME))
No edit summary
 
It is advised that you do not include a newline after the Infobox bootleg template, as you will end up with an annoying bar at the top of the article.
 
For more information on the Bootleg infobox template, see its TemplateData.
 
<pre>
// file size(s) (The size format is: X.X Y (#.# floating number, Y size unit (In capitals)).)
 
|download = [{{Link|url=https://crustywindo.ws/collection/(OS%20NAME)/(BOOTLEG%20ISO%20NAME).iso |name=(BOOTLEG ISO NAME).iso]}}
// download link(s) (If the bootleg ISO name is too long to properly fit in the infobox, then use <wbr> to cut it down. - yellows111)
 
|timebombdate =
// timebomb date (Use this parameter for bootlegs based on operating systems in the beta stages, which don't have their timebomb already patched out)
 
|livecd =
// live cd (Use this parameter for marking Live CDs)
}}
</pre>
== 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).
 
It is (unattended (and/or) preactivated). (if available:) The bootleg 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 and format neatly when necessary.)
 
== Changes from (reference original_os from infobox) ==
 
(This section, along with Software, and Notes, should be split into 3 sections. Minor Changes, Changes in pre-desktop procedures, and Look and Feel.)
(In here there will be the subsections Minor changes, Changes in pre-desktop procedures, and Look and feel.
 
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.
(If there is absolutely no software bundled, then it's optional. Most of the time, it isn't.)
 
(The software listing goes here. The software list needs to be sorted alphabetically, and by software type, in their own sub-sections. AcceptableSome specific software types areinclude Customization Utilities (software made to modify the look and feel of Windows, e.g. ViStart, TrueTransparency, Vista Drive Indicator, WindowBlinds, etc), Updates (Visual C++ redistributables, .NET Framework, etc) and Screensavers. Any others can be included if necessary. 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. TheIt sorting shouldmust be sorted exactly how it should beis shown in the WPI.)
 
== Notes ==
(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 namesmain to usesections are Bootleg Quirksquirks, CD Contentscontents and Otherother Infoinfo and WINNT.SIF metadata. The last section depends on what OSversion of Windows the bootleg is based on, which will likely vary. If it is Windows Vista or later then it should be System information.)
 
== Gallery ==
<pre>
<gallery>
ForTo see how to properly take advantage of the bootleg gallery, see "How To Capture Screenshots For Your Bootlegs: A Guide Concerning Labels And Places To Capture".
</gallery>
</pre>
 
== If an article does not meet the wiki standards... ==
Use this template to mark articles as such, named Not met:
 
{{Not met}}
 
{{Not met|Reason goes here.}}
 
This template serves as a marker for others to look at and rectify if needed.
 
== Where to look to obtain information for... ==
===== archiveadd =====
The first places you should look are:
* [[Project:Changelog|The Wiki Changelogchangelog]]
* The Wayback Machine (see [[Project:Changelog|the Wiki Changelogchangelog]] 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)
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 and others
: DirectX, Microsoft .NET Framework, any other updates
: "WGAV", "WGAN", "Microsoft Update Engine", "XP SP3 Update Pack", "OUE/OGA". Addons usually by xable
You can use the hypervisor's screenshot function if it has it, and any hypervisor for testing the bootleg. Although you ''can'' just use the Install Any OS VMs (or soon, crusttest, but it's still in development stages right now and will be useful for later), using a virtual machine is highly recommended, as you don't have to deal with distractions and disruptions from any potential troublemakers, and you get a higher quality picture as it's not compressed by the CollabVM server itself.
 
=== LabellingLabeling your screenshots and formatting it in its own gallery ===
As for labeling your screenshots, and good places to look for capturing, this is how to label your screenshots:
 
Example:
 
<code>XP Magart Redivo 2010 DJ KHALED Themetheme.png</code>
 
<code>Vista Ganja Edition Desktop.png</code>
; 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 (most of the changes here are a lot more visual)
; Boot screen
; Pre-OOBE (''if it exists, some bootlegs omit this'')
; OOBE (''if it exists, some bootlegs omit this'')
; Login screen
; PostPre-logindesktop (''anything that is set to run on startup, such as a WPI, post-install script, or other such. this section directly succeeds the login portion'')
; Empty desktop (''if anything else is shown when you first arrive to the desktop, such as a WPI screen, a popup (like a welcome center or other such), a system shutdown prompt, etc, then that makes it a Desktop on First Boot portion, otherwise it's just a Desktop portion'')
; Start menu (''the start menu of the default theme'')
; 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 (''usually there will be OEM branding'')
: Support Information (''if it exists, then include it'')
: About Windows
: Run dialog (''if it's changed'')
: About Windows (''usually there will be changed branding'')
; Autorun (''if the bootleg has its own one'')
: Autorun splash, and post-exit screens (''if any'')
* 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 doing the Demo portion, and the programs are too big even after resizing them, take separate screenshots of them. If you're on Windows Vista and later, use the AeroShot(CRE) utility instead.
* 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 ===
 
=== Program screenshots ===
YouIf you're using Windows Vista and later, you should consider using a program like [https://www.softpedia.com/get/Multimedia/Graphic/Graphic-Capture/AeroShot.shtml AeroShot] (or [https://github.com/Cvolton/AeroShotCRE AeroShotCRE]) to capture programs in a more professional way by only including the window, along with the major benefit of having real transparency in the image itself.
 
Screenshot examples:
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 "LabellingLabeling 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 ==
Retrieved from "https://crustywindo.ws/Talk:Main_Page"