Talk:Main Page: Difference between revisions

no edit summary
No edit summary
No edit summary
(3 intermediate revisions by the same user not shown)
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 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. Format like so: the autorun was made with X, and the boot selector used was Y). (Mention the ISO creation date which you can easily get in PowerISO or any other ISO software, tools used to make the OOBE video (viewable in MediaInfo), or anything else.)
 
(Feel free to put newlines and format neatly when necessary.)
* Search for strings in the binary itself. It may lead you to extra clues such as version information which you may not be obvious otherwise
* You may use any binary checking tool, such as Detect It Easy, to help you
 
To confirm the program used to modify the bootleg's ISO / what software was used to make the ISO:
* If you use the program PowerISO, open the ISO image you desire, go to Tools > View / Edit sector data..., then view the LBAs 16-18. There you will find:
: CDImage (used by nLite)
: Markers for e.g. UltraISO, Nero, etc.
 
===== The methods used to integrate various objects in a bootleg =====
To create a gallery in the Source Editor, just expand the Advanced section and click the Gallery button next to the "Insert" label, and fill everything out. The procedures to do this are covered below.
 
For Visual Editor users, click the Insert dropdown, then expand it by clicking More, then click Gallery. This is not recommended, as it may prove to be inefficient since there doesn't appear to be an option to add images in bulk.
 
All screenshots '''must''' be captured in PNG format. ,Screenshots should be taken fromin a VM screen (doesn't matter how you get a VM running) and if the screenshot is taken from a hypervisor, be cropped to just the VM screen (for obvious reasons).
 
You can use the hypervisor's screenshot function if it has it, and any hypervisor that is applicable for testing the bootleg. Although you ''can'' just use the Install Any OS VMs (or soon, Crusttest, which is nearly done, but not yet ready for public release. It will come in handy for later, but for now it is not applicable) using a virtual machine is highly recommended, as you don't have to deal with distractions and disruptions from any potential troublemakers that can arise in using a public environment, and you get a higher quality picture as there isn't any JPEG compression from the server.
 
This is the minimum baseline for taking screenshots. You can take screenshots of anything else you want, as long as you have taken screenshots of the necessary portions.
 
Remember, screenshotting portions count towards the Changes section, and '''must always be included'''. That being said, if there is a pre-OOBE screenshot, it counts as a "New pre-OOBE graphics" change. If there's a Setup screenshot, it's "New setup graphics".
 
=== Structure of a themes gallery ===