Wiki - User contributions [en-ca]

Marble Blast on Linux

2025-07-21T19:52:14Z

Kon:

Marble Blast Gold, Ultra and PlatinumQuest work fine with Wine, a compatibility layer for Linux/macOS that allows you to run Windows programs. There are a few ways to get MBG, MBU and PQ working. All games were tested on Wine 9.14 on EndeavourOS. I use both an AMD CPU and GPU.

== Wine ==
=== Marble Blast Gold ===
Gold runs on Wine 9.14 with minor issues. I have only tried OpenMBG, but I'm sure that the original 2003 version works too.

There are issues. For one, the game attempted to start in a low resolution in fullscreen, which made my system freak out. You will need to change the resolution and settings in prefs.cs. Additionally, exiting the settings screen crashes the game.

==== Native binary ====
There is a native MBG binary for Linux, but it's very outdated and will not work on a new system. Enough said.

=== Marble Blast Ultra (OpenMBU) ===
OpenMBU works with minor issues.

Starting in fullscreen mode makes a black bar appear at the top. The game is also stretched. This can be fixed by simply re-setting it to fullscreen. On Wine, the interiors will bug out when you change video settings, but using Proton does not do this.

=== PlatinumQuest ===
PQ works with some minor and major(?) issues.

The launcher is simply Java, you don't need Wine to run it. You will need wine to run the game however.

Minor issues include your marble disappearing when you have reflections on. Simply disable reflections to fix this. There is also some slight graphical artifacts when exiting a level, but these aren't too bad. Hitting an ice shard will lag the game down to ~20 FPS. Getting unfrozen will remove the lag.

A major issue that there will be no sound under Wine. Switching to Proton will make the sound come back. On Steam Deck, the 2.10.0 update (I am unsure about 2.10.1) will refuse to launch under Gaming Mode. 2.9.4 works, however you must nullroute marbleblast.com in the hosts file to dismiss the changelog as it is unclosable with a controller (thus making the game unplayable). Additionally, on versions 2.10 and later, you must set the driver to D3D12 or D3D11 because under other drivers, the game window will be very bright. Do note that the game will take 1-2 minutes to fully be playable now.

Everything else works fine.

== Native (Haxe Port) ==
You can build the [https://github.com/RandomityGuy/MBHaxe Marble Blast Haxe port] with Hashlink and optionally compile it to C. This will give you native versions of Marble Blast Gold, Ultra and Platinum.

How to make a Windows bootleg/WindowsXP

2025-01-02T16:37:17Z

Kon: remove advertising

{{DISPLAYTITLE:How to make a Windows XP bootleg}}
In this tutorial, I'll be going through how I make Windows XP bootlegs. It's unfortunately not as easy as Windows 7+ and a pain in the ass to do, but you can get a basic crusty mod out of it. This will also work for Windows 2000 and Windows Server 2003, though I wouldn't see the point in modding those.

== Pre-requisites ==
We'll be using these tools in the tutorial:
* A Windows XP ISO: You can find these basically anywhere and use any one you want, but I'd recommend you use the one I host, as it has SP3 and every update up to November 2013. [https://egg.l5.ca/files/ISO/Windows/WindowsXP.iso Click here to download it]
* Access to a Windows install: You will need a Windows install with basic utilities such as makecab. Most Windows installs already have this, so you shouldn't worry too much about this.
* nLite: This is optional, but highly recommended for making any finishing touches to your mod. These include things like unattended installs, update sideloading and some patches like 3rd-party themes.
* Any file hosting service: You'll need this to host your ISO obviously. I personally host mine on our own server, but you can use something like Google Drive or MediaFire.

== Preparation ==
=== Acquiring themes ===
You can acquire themes through sites like DeviantArt, or rip them out of already existing bootlegs. I host a few that I took out of a bootleg from 2010, you can find them [https://egg.l5.ca/files/Other/Crusty%20XP%20Themes/ here]

=== Acquiring programs ===
If you want to slipstream programs into your bootleg, gather every program you want to include. You'll also need a tool like WPI to have a crusty GUI for installing your programs, or you can just write a simple batch script to install all of them. You can later add the WPI/script as a program to run automatically at first boot later in nLite.

=== Extract the ISO ===
Once you have obtained an ISO, open it with a extraction utility like 7-Zip or WinRAR. You need a writable working directory to mod the files, simply mounting the ISO will not do anything. Extract it to your Desktop folder in a folder named whatever you want. And now it's time to get into the meat and potatoes of this article, actually making the bootleg.

== Mod the files ==
In Windows Vista and later, the setup engine uses a highly compressed file called "install.wim" for all the files that it needs to copy. Windows 2000, XP and Server 2003 use a different format... it stores all the files it needs to copy in a folder called "I386" on the root of the CD. Most, if not all files in here are cabinet files, which contain the actual file that setup copies, so for shell32.dll it is stored in I386 as "SHELL32.DL_". This is proven upon opening the file with your file extraction software. So, for every file you want to modify:

* You will need to open it with a file extraction utility
* Copy it to where-ever
* Open it with a resource modifier tool like Resource Hacker
* Save it and run the following command: <code>makecab file.ext FILE.EX_</code> (for example: <code>makecab logonui.exe LOGONUI.EX_</code>, <code>makecab shell32.dll SHELL32.DL_</code>)
* Move the newly created cabinet back to I386, replacing the old one.

Unfortunately, it has to be that way and that's why I said it's a real pain in the ass to create XP bootlegs, and mods in general. There ARE ways to make Windows XP install from a wim file, but that's out of the scope for this article and we won't be covering that.

You will need to do this for every file you modify, but if you want a specific theme for your bootleg, programs like Isso Pack can automatically go in and replace every file with a specific theme, like a Windows 7 theme.

=== Some important files ===
* The graphical setup engine introduced in XP contains all of its resources in <code>WINNTBBU.DLL</code>. You can use software like [https://egg.l5.ca/files/Software/Customization/WinntbbuED_3.1.exe WinntbbuED] to edit it easily or modify it yourself. WINNTBBU is an uncompressed file on the CD. (For me, anyway)
* Most icons and dialogs are stored in <code>shell32.dll</code> (SHELL32.DL_)
* Explorer resources are stored in <code>explorer.exe</code> (EXPLORER.EX_)

== Using nLite ==
[[File:Nlite1.png|thumb|The location step should look like this if you did it correctly.]]
Once you've either easily or painstakingly finished the file modding part, it's time to use nLite. nLite is a program to slipstream updates, create unattended setups and customize Windows XP installations. It's a pretty neat tool. Grab the latest version from [https://www.nliteos.com/download.html here], and run the installer. This requires .NET 2.0, but if you're running a modern Windows version then .NET 2.0 should already be installed. If not, go into optional features and enable the .NET 3.5 feature which also installs 2.0.

On startup of nLite, it will ask you to select the language you want to use, then it will tell you to locate your Windows installation files. Click Browse and select the folder where you extracted the files. After that, it should automatically detect what version of Windows you are going to modify. Click Next until you get to the task selection page.

=== Selecting Tasks ===
[[File:Nlite2.png|thumb|You'll really only need these.]]
Okay, there's a lot of stuff here, from updates to bootable ISOs. Select these: Components (optional: if you want to remove things), Unattended, Options, Tweaks and Bootable ISO.

=== Performing Tasks ===
You'll then be brought to the Components page. A window will pop up asking you what you want to keep. If you want to remove things without accidentally removing something you want, make sure to select some options here. From here, you can go in and select anything you want to remove, from applications to even support for hardware. These are sometimes useful if you are creating a minimal build (a "lite ISO") but generally useless if you want to create a full on bootleg. You will be brought to the Unattended page next, where you can enter in stuff that the setup will do automatically, like entering a product key, creating users and also running scripts. You will only need to use a few things here: General, RunOnce and Desktop themes.

==== General ====
Here you can enter in stuff like product keys, if you want to turn off OOBE or the firewall, anything really. Nothing much to say here.

==== RunOnce ====
Remember the acquiring programs part from earlier? Assuming you have already compiled the WPI or written a script to do it and it is already in the Windows installation files, you can enter in the path to it in here. For example, if your script is located in <code>(folder containing install files)\Programs\Install.bat</code>, you can enter in <code>%SOURCE%\Programs\Install.bat</code>

==== Desktop themes ====
Here you can integrate the themes into your bootleg. If you had already downloaded some and put them into a separate folder, click Add, and then select the .theme file. nLite will automatically add the .msstyles and other files the theme needs to function. You can also select the default theme to apply if you wish.

=== Options and Tweaks ===
==== Options ====
This is where you'll find little options and patches for you to use. If you have integrated themes, '''make sure to go to the Patches page and turn on Unsigned Themes Support, otherwise the themes will not function properly.''' You can also disable SFC if you want, which is usually what I do anyway. Nothing other than those in the Options page really matters anyway.
==== Tweaks ====
This is where you can find little tweaks you can make to the install like desktop icon size, if you prefer the classic logon screen and many more. If you don't care about that, move on.

== Finishing touches ==
Finally, you'll be brought to the processing page. A confirmation window will pop up asking if you want to apply these changes. Click Yes if you are confident that you're finished, though you can always go back into nLite later to make some changes. Depending on how much stuff you removed and integrated, this may take a few minutes. After that, it'll tell you how big the new installation is. Click Next and you will be brought to the Bootable ISO page. Select "Create Image" under Mode and change the label to whatever you want. After that, click Make ISO and select the location where you want your ISO to be. It will now begin creating the ISO. After that, you can close nLite.

== Uploading to a file host ==
Congratulations, you've done it! If you've followed everything correctly, you should have a shiny new ISO containing your beautiful creation. I'm sure it's great. Anyway, you should test it out under a virtual machine or if you have another computer laying around, you can test it there too. If testing went well, you can upload it to a file host of your choice and share it with people. If you found something that went wrong, you can go back into nLite and attempt to fix it.
[[Category:Tutorials]]

How to make a Windows bootleg/Windows7

2025-01-02T16:37:05Z

Kon: remove advertising

{{DISPLAYTITLE:How to make a Windows 7+ bootleg}}
In this tutorial, I'll be going through how I make Windows 7 bootlegs. It's actually a very different process from Windows XP, however it is much easier. This tutorial will also work with Windows 8.x, 10 and 11 but we're going over Windows 7 in this guide. We're going to be using something called Audit Mode, introduced with Windows Vista.

== Pre-requisites ==
We'll be using these tools in the tutorial:
* A Windows 7 ISO: These are very common, I would recommend you use Windows 7 Professional SP1.
* Hiren's Boot CD: This is the PE you will be using to capture the image using DISM.
* Access to a Windows install: This could either be on your host or in a VM. I'm using Linux personally, so I'll have to install Windows in a VM to make the ISO, though you can just follow the steps on your host if you run Windows.
* Any file hosting service: Because where else will you store your ISO?
* A VM: Where else are we going to make the thing? You can use your favourite hypervisor, but we're using VMware Workstation in this tutorial. I have not tested VMware Player.
* Various utilities: Tools like Resource Hacker and UxTheme will be crucial to making your bootleg and also post-production. ImgBurn is also needed to make the ISO.
== Preparation ==
=== Download post-production tools ===
* [https://www.angusj.com/resourcehacker/ Resource Hacker]
* [https://www.imgburn.com/index.php?act=download ImgBurn]
* [https://www.autoitconsulting.com/site/software/gimagex/ GImageX]
=== Create a VM ===
Create a VM in Workstation, go through the necessary steps.
=== Acquire themes and programs ===
You'll actually be doing this step inside the VM, so wait until we reach Audit Mode, then gather everything.
== Boot into Audit Mode ==
You'll be greeted with the usual Windows 7 installer. Go through it as you would normally and wait for it to install. Go play a game, take a walk or whatever and when you come back you should be at the OOBE screen. This is the important part: Do '''''NOT''''' continue. Instead, press CTRL+SHIFT+F3. This will exit the OOBE and enter you into Audit Mode. And finally, here comes the real fun, making the bootleg.

== Make your changes ==
[[File:AuditModeFirstBoot.png|thumb|This is what you should see if you didn't fuck it up.]]
[[File:ThemePolicy.png|thumb|Theme policy setting. Replace "a.theme" with the name of your theme file.]]
You'll be greeted with that same Windows 7 desktop. You can close that sysprep window for now, it won't matter until you actually finish making your bootleg. Except, not yet. A few things to note here in Audit Mode and in general while creating your bootleg:
* You cannot log off or lock. This will disable the Administrator account, but this can be fixed with a reboot.
* You cannot modify the boot screen. This will invalidate the signature of winload and will make your bootleg unbootable upon installing it.
* Install programs for all users. Shortcuts should go in Public Desktop and the All Users start menu.
* To change the theme for all users at first login, go into gpedit.msc, navigate to User Configuration > Administrator > Control Panel > Personalization > Load a specific theme and put the path to your theme file.
This pretty much functions like a normal Windows 7 install, and you're now on your own to customize it. Any questions should be redirected to my discord server in #bootleg-authoring.

== Post-production ==
=== Sysprepping ===
[[File:Sysprep.png|thumb|Sysprep options that should be selected]]
Reboot the system after you are finished editing and Sysprep should open when you logon. Check "Generalize" and "Shutdown" from the dropdown. This is a good time to check if you have anything else you want to do. If you want to do anything else, do it now because you won't get a chance later. Once you're ready, click OK and it should start. Wait a bit then it will shut down. Create a new disk in VMware to store the install.wim file on.

=== Capturing ===
Insert the HBCD ISO into the VM and then power it on to the BIOS. You'll need to change the boot order to boot from the DVD first, then reboot. HBCD should now start loading. When it does load, go into Disk Management and partition the new disk. Now, go into the Windows installation drive and delete the Administrator user folder. This will wipe all your previous traces. Now, FINALLY, start the command prompt and enter in the following command:
<pre>dism /capture-image /imagefile:(wim drive letter):\install.wim /capturedir:(windows install drive letter):\ /name:"Whatever You Want"</pre>
DISM will now start making your install.wim file. This may take a few minutes.

=== Finalization ===
As I said before, I'm running Linux, which means I don't have any access to the tools I need to do post-production. So, I'll need to do finalization on this VM instead of my host. Start by installing Resource Hacker, ImgBurn and GImageX. Now, make a folder on your desktop called whatever you want and put two folders in there: "root" (for all the installation files) and "boot" (for the boot.wim file). Extract the contents of the Windows 7 ISO you used to the "root" folder. Open GImageX, navigate to Mount, then choose the boot.wim file from (root folder)/sources as the source and the "boot" folder as the destination. Also make sure to make it readable and writable. There's a lot of files here, most of them are system protected so you'll need to make them writable by you. There are many things you can modify but here's some important ones:
* <code>sources/background.bmp</code> - Background for the initial setup window asking for your language
* <code>sources/spwizimg.dll</code> - Most setup resources
* <code>Windows/System32/setup.bmp</code> - Background behind the initial setup window asking for your language
After you are done modifying, make sure to commit the changes before unmounting so your changes will take effect. Now to move onto the actual installer. The setup files to modify are the same as boot.wim, sans setup.bmp.

Copy the install.wim from the other drive to <code>sources/install.wim</code>.

== Create the ISO ==
Okay, I lied, this is the actual finalization. Open ImgBurn, select Create image file from files and folders. There are a few things to do here so lets get that out of the way.
=== Adding files ===
Pretty straightforward, click the folder icon next to Source and add each 5 folders to the ISO (boot, efi, sources, upgrade, support). Then, click the file icon and add the 4 files on the root (autorun.inf, bootmgr, bootmgr.efi, setup.exe). If you have any other files/folders you put on the root, add those too.
=== Make it bootable ===
Go to the Bootable Disc tab under Advanced, select Make Image Bootable then select (install files root)/boot/etfsboot.com and set the sectors to load to 8.
=== Labels ===
Go to the Labels tab and pick a label. Nothing much.
=== Create the image ===
Select a location for your ISO and click Build. If it says that it thinks its an OS installation disc, let it adjust the settings. It will then ask you if you want to create the image, select Yes. Wait for it to be finished and you should be notified with a sound that jumpscares me every time I hear it.

== You're done! ==
Congratulations, you've done it! If you've followed everything correctly, you should have a shiny new ISO containing your beautiful creation. I'm sure it's great. Anyway, you should test it out under a virtual machine or if you have another computer laying around, you can test it there too. If testing went well, you can upload it to a file host of your choice and share it with people. If you found something that went wrong, well uh, you're going to need to do that whole audit mode thing again. Hope you didn't screw anything up!

Marble Blast on Linux

2024-12-31T03:41:19Z

Kon: Now that I have a Steam Deck, I should put this here.

Marble Blast Gold, Ultra and PlatinumQuest work fine with Wine, a compatibility layer for Linux/macOS that allows you to run Windows programs. There are a few ways to get MBG, MBU and PQ working. All games were tested on Wine 9.14 on EndeavourOS. I use both an AMD CPU and GPU.

== Wine ==
=== Marble Blast Gold ===
Gold runs on Wine 9.14 with minor issues. I have only tried OpenMBG, but I'm sure that the original 2003 version works too.

There are issues. For one, the game attempted to start in a low resolution in fullscreen, which made my system freak out. You will need to change the resolution and settings in prefs.cs. Additionally, exiting the settings screen crashes the game.

==== Native binary ====
There is a native MBG binary for Linux, but it's very outdated and will not work on a new system. Enough said.

=== Marble Blast Ultra (OpenMBU) ===
OpenMBU works with minor issues.

Starting in fullscreen mode makes a black bar appear at the top. The game is also stretched. This can be fixed by simply re-setting it to fullscreen. On Wine, the interiors will bug out when you change video settings, but using Proton does not do this.

=== PlatinumQuest ===
PQ works with some minor and major(?) issues.

The launcher is simply Java, you don't need Wine to run it. You will need wine to run the game however.

Minor issues include your marble disappearing when you have reflections on. Simply disable reflections to fix this. There is also some slight graphical artifacts when exiting a level, but these aren't too bad. Hitting an ice shard will lag the game down to ~20 FPS. Getting unfrozen will remove the lag.

A major issue that there will be no sound under Wine. Switching to Proton will make the sound come back. On Steam Deck, the 2.10.0 update (I am unsure about 2.10.1) will refuse to launch under Gaming Mode. 2.9.4 works, however you must nullroute marbleblast.com in the hosts file to dismiss the changelog as it is unclosable with a controller (thus making the game unplayable)

Everything else works fine.

== Native (Haxe Port) ==
You can build the [https://github.com/RandomityGuy/MBHaxe Marble Blast Haxe port] with Hashlink and optionally compile it to C. This will give you native versions of Marble Blast Gold, Ultra and Platinum.

How to make a Windows bootleg/Windows7

2024-08-20T23:59:31Z

Kon: /* Make your changes */

{{DISPLAYTITLE:How to make a Windows 7+ bootleg}}
{{Warn|I wrote this article at 2 AM. Beware of any things that sound stupid.}}
[[File:LMv2-Desktop.png|thumb|Windows 7 Linux Mint V2, a CollabSysOS release that I have worked on.]]
In this tutorial, I'll be going through how I make Windows 7 bootlegs. It's actually a very different process from Windows XP, however it is much easier. This tutorial will also work with Windows 8.x, 10 and 11 but we're going over Windows 7 in this guide. We're going to be using something called Audit Mode, introduced with Windows Vista.

== Pre-requisites ==
We'll be using these tools in the tutorial:
* A Windows 7 ISO: These are very common, I would recommend you use Windows 7 Professional SP1.
* Hiren's Boot CD: This is the PE you will be using to capture the image using DISM.
* Access to a Windows install: This could either be on your host or in a VM. I'm using Linux personally, so I'll have to install Windows in a VM to make the ISO, though you can just follow the steps on your host if you run Windows.
* Any file hosting service: Because where else will you store your ISO?
* A VM: Where else are we going to make the thing? You can use your favourite hypervisor, but we're using VMware Workstation in this tutorial. I have not tested VMware Player.
* Various utilities: Tools like Resource Hacker and UxTheme will be crucial to making your bootleg and also post-production. ImgBurn is also needed to make the ISO.
== Preparation ==
=== Download post-production tools ===
* [https://www.angusj.com/resourcehacker/ Resource Hacker]
* [https://www.imgburn.com/index.php?act=download ImgBurn]
* [https://www.autoitconsulting.com/site/software/gimagex/ GImageX]
=== Create a VM ===
Create a VM in Workstation, go through the necessary steps.
=== Acquire themes and programs ===
You'll actually be doing this step inside the VM, so wait until we reach Audit Mode, then gather everything.
== Boot into Audit Mode ==
You'll be greeted with the usual Windows 7 installer. Go through it as you would normally and wait for it to install. Go play a game, take a walk or whatever and when you come back you should be at the OOBE screen. This is the important part: Do '''''NOT''''' continue. Instead, press CTRL+SHIFT+F3. This will exit the OOBE and enter you into Audit Mode. And finally, here comes the real fun, making the bootleg.

== Make your changes ==
[[File:AuditModeFirstBoot.png|thumb|This is what you should see if you didn't fuck it up.]]
[[File:ThemePolicy.png|thumb|Theme policy setting. Replace "a.theme" with the name of your theme file.]]
You'll be greeted with that same Windows 7 desktop. You can close that sysprep window for now, it won't matter until you actually finish making your bootleg. Except, not yet. A few things to note here in Audit Mode and in general while creating your bootleg:
* You cannot log off or lock. This will disable the Administrator account, but this can be fixed with a reboot.
* You cannot modify the boot screen. This will invalidate the signature of winload and will make your bootleg unbootable upon installing it.
* Install programs for all users. Shortcuts should go in Public Desktop and the All Users start menu.
* To change the theme for all users at first login, go into gpedit.msc, navigate to User Configuration > Administrator > Control Panel > Personalization > Load a specific theme and put the path to your theme file.
This pretty much functions like a normal Windows 7 install, and you're now on your own to customize it. Any questions should be redirected to my discord server in #bootleg-authoring.

== Post-production ==
=== Sysprepping ===
[[File:Sysprep.png|thumb|Sysprep options that should be selected]]
Reboot the system after you are finished editing and Sysprep should open when you logon. Check "Generalize" and "Shutdown" from the dropdown. This is a good time to check if you have anything else you want to do. If you want to do anything else, do it now because you won't get a chance later. Once you're ready, click OK and it should start. Wait a bit then it will shut down. Create a new disk in VMware to store the install.wim file on.

=== Capturing ===
Insert the HBCD ISO into the VM and then power it on to the BIOS. You'll need to change the boot order to boot from the DVD first, then reboot. HBCD should now start loading. When it does load, go into Disk Management and partition the new disk. Now, go into the Windows installation drive and delete the Administrator user folder. This will wipe all your previous traces. Now, FINALLY, start the command prompt and enter in the following command:
<pre>dism /capture-image /imagefile:(wim drive letter):\install.wim /capturedir:(windows install drive letter):\ /name:"Whatever You Want"</pre>
DISM will now start making your install.wim file. This may take a few minutes.

=== Finalization ===
As I said before, I'm running Linux, which means I don't have any access to the tools I need to do post-production. So, I'll need to do finalization on this VM instead of my host. Start by installing Resource Hacker, ImgBurn and GImageX. Now, make a folder on your desktop called whatever you want and put two folders in there: "root" (for all the installation files) and "boot" (for the boot.wim file). Extract the contents of the Windows 7 ISO you used to the "root" folder. Open GImageX, navigate to Mount, then choose the boot.wim file from (root folder)/sources as the source and the "boot" folder as the destination. Also make sure to make it readable and writable. There's a lot of files here, most of them are system protected so you'll need to make them writable by you. There are many things you can modify but here's some important ones:
* <code>sources/background.bmp</code> - Background for the initial setup window asking for your language
* <code>sources/spwizimg.dll</code> - Most setup resources
* <code>Windows/System32/setup.bmp</code> - Background behind the initial setup window asking for your language
After you are done modifying, make sure to commit the changes before unmounting so your changes will take effect. Now to move onto the actual installer. The setup files to modify are the same as boot.wim, sans setup.bmp.

Copy the install.wim from the other drive to <code>sources/install.wim</code>.

== Create the ISO ==
Okay, I lied, this is the actual finalization. Open ImgBurn, select Create image file from files and folders. There are a few things to do here so lets get that out of the way.
=== Adding files ===
Pretty straightforward, click the folder icon next to Source and add each 5 folders to the ISO (boot, efi, sources, upgrade, support). Then, click the file icon and add the 4 files on the root (autorun.inf, bootmgr, bootmgr.efi, setup.exe). If you have any other files/folders you put on the root, add those too.
=== Make it bootable ===
Go to the Bootable Disc tab under Advanced, select Make Image Bootable then select (install files root)/boot/etfsboot.com and set the sectors to load to 8.
=== Labels ===
Go to the Labels tab and pick a label. Nothing much.
=== Create the image ===
Select a location for your ISO and click Build. If it says that it thinks its an OS installation disc, let it adjust the settings. It will then ask you if you want to create the image, select Yes. Wait for it to be finished and you should be notified with a sound that jumpscares me every time I hear it.

== You're done! ==
Congratulations, you've done it! If you've followed everything correctly, you should have a shiny new ISO containing your beautiful creation. I'm sure it's great. Anyway, you should test it out under a virtual machine or if you have another computer laying around, you can test it there too. If testing went well, you can upload it to a file host of your choice and share it with people. If you found something that went wrong, well uh, you're going to need to do that whole audit mode thing again. Hope you didn't screw anything up!

Marble Blast on Linux

2024-08-18T03:08:21Z

Kon:

Marble Blast Gold, Ultra and PlatinumQuest work fine with Wine, a compatibility layer for Linux/macOS that allows you to run Windows programs. There are a few ways to get MBG, MBU and PQ working. All games were tested on Wine 9.14 on EndeavourOS. I use both an AMD CPU and GPU.

== Wine ==
=== Marble Blast Gold ===
Gold runs on Wine 9.14 with minor issues. I have only tried OpenMBG, but I'm sure that the original 2003 version works too.

There are issues. For one, the game attempted to start in a low resolution in fullscreen, which made my system freak out. You will need to change the resolution and settings in prefs.cs. Additionally, exiting the settings screen crashes the game.

==== Native binary ====
There is a native MBG binary for Linux, but it's very outdated and will not work on a new system. Enough said.

=== Marble Blast Ultra (OpenMBU) ===
OpenMBU works with minor issues.

Starting in fullscreen mode makes a black bar appear at the top. The game is also stretched. This can be fixed by simply re-setting it to fullscreen. On Wine, the interiors will bug out when you change video settings, but using Proton does not do this.

=== PlatinumQuest ===
PQ works with some minor and major(?) issues.

The launcher is simply Java, you don't need Wine to run it. You will need wine to run the game however.

Minor issues include your marble disappearing when you have reflections on. Simply disable reflections to fix this. There is also some slight graphical artifacts when exiting a level, but these aren't too bad. Hitting an ice shard will lag the game down to ~20 FPS. Getting unfrozen will remove the lag.

A major issue that there will be no sound under Wine. Switching to Proton will make the sound come back.

Everything else works fine.

== Native (Haxe Port) ==
You can build the [https://github.com/RandomityGuy/MBHaxe Marble Blast Haxe port] with Hashlink and optionally compile it to C. This will give you native versions of Marble Blast Gold, Ultra and Platinum.

Marble Blast on Linux

2024-08-18T03:07:49Z

Kon:

Marble Blast Gold, Ultra and PlatinumQuest work fine with Wine, a compatibility layer for Linux/macOS that allows you to run Windows programs. There are a few ways to get MBG, MBU and PQ working. All games were tested on Wine 9.14 on EndeavourOS. I use both an AMD CPU and GPU.

== Wine ==
=== Marble Blast Gold ===
Gold runs on Wine 9.14 with minor issues. I have only tried OpenMBG, but I'm sure that the original 2003 version works too.

There are issues. For one, the game attempted to start in a low resolution in fullscreen, which made my system freak out. You will need to change the resolution and settings in prefs.cs. Additionally, exiting the settings screen crashes the game.

==== Native binary ====
There is a native MBG binary for Linux, but it's very outdated and will not work on a new system. Enough said.

== Marble Blast Ultra (OpenMBU) ==
OpenMBU works with minor issues.

Starting in fullscreen mode makes a black bar appear at the top. The game is also stretched. This can be fixed by simply re-setting it to fullscreen. On Wine, the interiors will bug out when you change video settings, but using Proton does not do this.

== PlatinumQuest ==
PQ works with some minor and major(?) issues.

The launcher is simply Java, you don't need Wine to run it. You will need wine to run the game however.

Minor issues include your marble disappearing when you have reflections on. Simply disable reflections to fix this. There is also some slight graphical artifacts when exiting a level, but these aren't too bad. Hitting an ice shard will lag the game down to ~20 FPS. Getting unfrozen will remove the lag.

A major issue that there will be no sound under Wine. Switching to Proton will make the sound come back.

Everything else works fine.

== Native (Haxe Port) ==
You can build the [https://github.com/RandomityGuy/MBHaxe Marble Blast Haxe port] with Hashlink and optionally compile it to C. This will give you native versions of Marble Blast Gold, Ultra and Platinum.

Marble Blast on Linux

2024-08-17T03:30:09Z

Kon: Created page with "Marble Blast Gold, Ultra and PlatinumQuest work fine with Wine, a compatibility layer for Linux/macOS that allows you to run Windows programs. There are a few ways to get MBG, MBU and PQ working. All games were tested on Wine 9.14 on EndeavourOS. I use both an AMD CPU and GPU. == Wine == === Marble Blast Gold === Gold runs on Wine 9.14 with minor issues. I have only tried OpenMBG, but I'm sure that the original 2003 version works too. There are issues. For one, the gam..."

File:Neofetch.png

2024-08-17T03:09:30Z

Kon:

Coke and Fries Halo

2024-06-18T19:35:44Z

Kon:

[[File:Coke and Fries Halo.jpg|thumb|Coke and fries Halo]]
Back in 2007, you could go to Burger King and get a Coke and Fries Halo. This was to market Halo 3, which was set to release later that year. In this promotion, they put Halo on Coca-Cola and fries, featuring Master Chief and the release date of Halo 3. Because of this, we have Coke and Fries Halo. The cool thing about Coke and Fries Halo is the design, it looks like Halo.

This was to promote their upcoming game, Halo 3. To do this, they made Coke and Fries Halo. This is back in 2007, when people consumed a lot of Coke and fries, and liked to play Halo, so they decided to combine them, giving us Coke and Fries Halo. They made this in 2007, uhm, by putting Master Chief and Halo-related things on the design for both their Coca-Cola cup and their fry container. Uh, so you could go to Burger King and say "I would like a Coke and Fries Halo." and they, then, you'd get this. This- what you're seeing on screen is Coke and Fries Halo, uhm

Coke and Fries Halo

2024-06-18T19:35:32Z

Kon: Created page with "Coke and fries Halo Back in 2007, you could go to Burger King and get a Coke and Fries Halo. This was to market Halo 3, which was set to release later that year. In this promotion, they put Halo on Coca-Cola and fries, featuring Master Chief and the release date of Halo 3. Because of this, we have Coke and Fries Halo. The cool thing about Coke and Fries Halo is the design, it looks like Halo. This was to promote their upcoming game, Ha..."

[[File:Coke and Fries Halo|thumb|Coke and fries Halo]]
Back in 2007, you could go to Burger King and get a Coke and Fries Halo. This was to market Halo 3, which was set to release later that year. In this promotion, they put Halo on Coca-Cola and fries, featuring Master Chief and the release date of Halo 3. Because of this, we have Coke and Fries Halo. The cool thing about Coke and Fries Halo is the design, it looks like Halo.

This was to promote their upcoming game, Halo 3. To do this, they made Coke and Fries Halo. This is back in 2007, when people consumed a lot of Coke and fries, and liked to play Halo, so they decided to combine them, giving us Coke and Fries Halo. They made this in 2007, uhm, by putting Master Chief and Halo-related things on the design for both their Coca-Cola cup and their fry container. Uh, so you could go to Burger King and say "I would like a Coke and Fries Halo." and they, then, you'd get this. This- what you're seeing on screen is Coke and Fries Halo, uhm

File:Coke and Fries Halo.jpg

2024-06-18T19:34:51Z

Kon:

How to make a Windows bootleg

2024-05-25T17:25:20Z

Kon:

* [[How to make a Windows bootleg/WindowsXP|Windows XP]]
* [[How to make a Windows bootleg/Windows7|Windows 7-10]]

How to make a Windows bootleg/Windows7

2024-05-03T22:14:13Z

Kon:

{{DISPLAYTITLE:How to make a Windows 7+ bootleg}}
{{Warn|I wrote this article at 2 AM. Beware of any things that sound stupid.}}
[[File:LMv2-Desktop.png|thumb|Windows 7 Linux Mint V2, a CollabSysOS release that I have worked on.]]
In this tutorial, I'll be going through how I make Windows 7 bootlegs. It's actually a very different process from Windows XP, however it is much easier. This tutorial will also work with Windows 8.x, 10 and 11 but we're going over Windows 7 in this guide. We're going to be using something called Audit Mode, introduced with Windows Vista.

== Pre-requisites ==
We'll be using these tools in the tutorial:
* A Windows 7 ISO: These are very common, I would recommend you use Windows 7 Professional SP1.
* Hiren's Boot CD: This is the PE you will be using to capture the image using DISM.
* Access to a Windows install: This could either be on your host or in a VM. I'm using Linux personally, so I'll have to install Windows in a VM to make the ISO, though you can just follow the steps on your host if you run Windows.
* Any file hosting service: Because where else will you store your ISO?
* A VM: Where else are we going to make the thing? You can use your favourite hypervisor, but we're using VMware Workstation in this tutorial. I have not tested VMware Player.
* Various utilities: Tools like Resource Hacker and UxTheme will be crucial to making your bootleg and also post-production. ImgBurn is also needed to make the ISO.
== Preparation ==
=== Download post-production tools ===
* [https://www.angusj.com/resourcehacker/ Resource Hacker]
* [https://www.imgburn.com/index.php?act=download ImgBurn]
* [https://www.autoitconsulting.com/site/software/gimagex/ GImageX]
=== Create a VM ===
Create a VM in Workstation, go through the necessary steps.
=== Acquire themes and programs ===
You'll actually be doing this step inside the VM, so wait until we reach Audit Mode, then gather everything.
== Boot into Audit Mode ==
You'll be greeted with the usual Windows 7 installer. Go through it as you would normally and wait for it to install. Go play a game, take a walk or whatever and when you come back you should be at the OOBE screen. This is the important part: Do '''''NOT''''' continue. Instead, press CTRL+SHIFT+F3. This will exit the OOBE and enter you into Audit Mode. And finally, here comes the real fun, making the bootleg.

== Make your changes ==
[[File:AuditModeFirstBoot.png|thumb|This is what you should see if you didn't fuck it up.]]
[[File:ThemePolicy.png|thumb|Theme policy setting. Replace "a.theme" with the name of your theme file.]]
You'll be greeted with that same Windows 7 desktop. You can close that sysprep window for now, it won't matter until you actually finish making your bootleg. Except, not yet. A few things to note here in Audit Mode and in general while creating your bootleg:
* You cannot log off or lock. This will disable the Administrator account, but this can be fixed with a reboot.
* You cannot modify the boot screen. This will invalidate the signature of winload and will make your bootleg unbootable upon installing it.
* Install programs for all users. Shortcuts should go in Public Desktop and the All Users start menu.
* To change the theme for all users at first login, go into gpedit.msc, navigate to User Configuration > Control Panel > Personalization > Load a specific theme and put the path to your theme file.
This pretty much functions like a normal Windows 7 install, and you're now on your own to customize it. Any questions should be redirected to my discord server in #bootleg-authoring.

== Post-production ==
=== Sysprepping ===
[[File:Sysprep.png|thumb|Sysprep options that should be selected]]
Reboot the system after you are finished editing and Sysprep should open when you logon. Check "Generalize" and "Shutdown" from the dropdown. This is a good time to check if you have anything else you want to do. If you want to do anything else, do it now because you won't get a chance later. Once you're ready, click OK and it should start. Wait a bit then it will shut down. Create a new disk in VMware to store the install.wim file on.

=== Capturing ===
Insert the HBCD ISO into the VM and then power it on to the BIOS. You'll need to change the boot order to boot from the DVD first, then reboot. HBCD should now start loading. When it does load, go into Disk Management and partition the new disk. Now, go into the Windows installation drive and delete the Administrator user folder. This will wipe all your previous traces. Now, FINALLY, start the command prompt and enter in the following command:
<pre>dism /capture-image /imagefile:(wim drive letter):\install.wim /capturedir:(windows install drive letter):\ /name:"Whatever You Want"</pre>
DISM will now start making your install.wim file. This may take a few minutes.

=== Finalization ===
As I said before, I'm running Linux, which means I don't have any access to the tools I need to do post-production. So, I'll need to do finalization on this VM instead of my host. Start by installing Resource Hacker, ImgBurn and GImageX. Now, make a folder on your desktop called whatever you want and put two folders in there: "root" (for all the installation files) and "boot" (for the boot.wim file). Extract the contents of the Windows 7 ISO you used to the "root" folder. Open GImageX, navigate to Mount, then choose the boot.wim file from (root folder)/sources as the source and the "boot" folder as the destination. Also make sure to make it readable and writable. There's a lot of files here, most of them are system protected so you'll need to make them writable by you. There are many things you can modify but here's some important ones:
* <code>sources/background.bmp</code> - Background for the initial setup window asking for your language
* <code>sources/spwizimg.dll</code> - Most setup resources
* <code>Windows/System32/setup.bmp</code> - Background behind the initial setup window asking for your language
After you are done modifying, make sure to commit the changes before unmounting so your changes will take effect. Now to move onto the actual installer. The setup files to modify are the same as boot.wim, sans setup.bmp.

Copy the install.wim from the other drive to <code>sources/install.wim</code>.

== Create the ISO ==
Okay, I lied, this is the actual finalization. Open ImgBurn, select Create image file from files and folders. There are a few things to do here so lets get that out of the way.
=== Adding files ===
Pretty straightforward, click the folder icon next to Source and add each 5 folders to the ISO (boot, efi, sources, upgrade, support). Then, click the file icon and add the 4 files on the root (autorun.inf, bootmgr, bootmgr.efi, setup.exe). If you have any other files/folders you put on the root, add those too.
=== Make it bootable ===
Go to the Bootable Disc tab under Advanced, select Make Image Bootable then select (install files root)/boot/etfsboot.com and set the sectors to load to 8.
=== Labels ===
Go to the Labels tab and pick a label. Nothing much.
=== Create the image ===
Select a location for your ISO and click Build. If it says that it thinks its an OS installation disc, let it adjust the settings. It will then ask you if you want to create the image, select Yes. Wait for it to be finished and you should be notified with a sound that jumpscares me every time I hear it.

== You're done! ==
Congratulations, you've done it! If you've followed everything correctly, you should have a shiny new ISO containing your beautiful creation. I'm sure it's great. Anyway, you should test it out under a virtual machine or if you have another computer laying around, you can test it there too. If testing went well, you can upload it to a file host of your choice and share it with people. If you found something that went wrong, well uh, you're going to need to do that whole audit mode thing again. Hope you didn't screw anything up!

How to make a Windows bootleg/Windows7

2024-04-29T19:18:45Z

Kon: forgot this

{{Warn|I wrote this article at 2 AM. Beware of any things that sound stupid.}}
[[File:LMv2-Desktop.png|thumb|Windows 7 Linux Mint V2, a CollabSysOS release that I have worked on.]]
In this tutorial, I'll be going through how I make Windows 7 bootlegs. It's actually a very different process from Windows XP, however it is much easier. This tutorial will also work with Windows 8.x, 10 and 11 but we're going over Windows 7 in this guide. We're going to be using something called Audit Mode, introduced with Windows Vista.

== Pre-requisites ==
We'll be using these tools in the tutorial:
* A Windows 7 ISO: These are very common, I would recommend you use Windows 7 Professional SP1.
* Hiren's Boot CD: This is the PE you will be using to capture the image using DISM.
* Access to a Windows install: This could either be on your host or in a VM. I'm using Linux personally, so I'll have to install Windows in a VM to make the ISO, though you can just follow the steps on your host if you run Windows.
* Any file hosting service: Because where else will you store your ISO?
* A VM: Where else are we going to make the thing? You can use your favourite hypervisor, but we're using VMware Workstation in this tutorial. I have not tested VMware Player.
* Various utilities: Tools like Resource Hacker and UxTheme will be crucial to making your bootleg and also post-production. ImgBurn is also needed to make the ISO.
== Preparation ==
=== Download post-production tools ===
* [https://www.angusj.com/resourcehacker/ Resource Hacker]
* [https://www.imgburn.com/index.php?act=download ImgBurn]
* [https://www.autoitconsulting.com/site/software/gimagex/ GImageX]
=== Create a VM ===
Create a VM in Workstation, go through the necessary steps.
=== Acquire themes and programs ===
You'll actually be doing this step inside the VM, so wait until we reach Audit Mode, then gather everything.
== Boot into Audit Mode ==
You'll be greeted with the usual Windows 7 installer. Go through it as you would normally and wait for it to install. Go play a game, take a walk or whatever and when you come back you should be at the OOBE screen. This is the important part: Do '''''NOT''''' continue. Instead, press CTRL+SHIFT+F3. This will exit the OOBE and enter you into Audit Mode. And finally, here comes the real fun, making the bootleg.

== Make your changes ==
[[File:AuditModeFirstBoot.png|thumb|This is what you should see if you didn't fuck it up.]]
[[File:ThemePolicy.png|thumb|Theme policy setting. Replace "a.theme" with the name of your theme file.]]
You'll be greeted with that same Windows 7 desktop. You can close that sysprep window for now, it won't matter until you actually finish making your bootleg. Except, not yet. A few things to note here in Audit Mode and in general while creating your bootleg:
* You cannot log off or lock. This will disable the Administrator account, but this can be fixed with a reboot.
* You cannot modify the boot screen. This will invalidate the signature of winload and will make your bootleg unbootable upon installing it.
* Install programs for all users. Shortcuts should go in Public Desktop and the All Users start menu.
* To change the theme for all users at first login, go into gpedit.msc, navigate to User Configuration > Control Panel > Personalization > Load a specific theme and put the path to your theme file.
This pretty much functions like a normal Windows 7 install, and you're now on your own to customize it. Any questions should be redirected to my discord server in #bootleg-authoring.

== Post-production ==
=== Sysprepping ===
[[File:Sysprep.png|thumb|Sysprep options that should be selected]]
Reboot the system after you are finished editing and Sysprep should open when you logon. Check "Generalize" and "Shutdown" from the dropdown. This is a good time to check if you have anything else you want to do. If you want to do anything else, do it now because you won't get a chance later. Once you're ready, click OK and it should start. Wait a bit then it will shut down. Create a new disk in VMware to store the install.wim file on.

=== Capturing ===
Insert the HBCD ISO into the VM and then power it on to the BIOS. You'll need to change the boot order to boot from the DVD first, then reboot. HBCD should now start loading. When it does load, go into Disk Management and partition the new disk. Now, go into the Windows installation drive and delete the Administrator user folder. This will wipe all your previous traces. Now, FINALLY, start the command prompt and enter in the following command:
<pre>dism /capture-image /imagefile:(wim drive letter):\install.wim /capturedir:(windows install drive letter):\ /name:"Whatever You Want"</pre>
DISM will now start making your install.wim file. This may take a few minutes.

=== Finalization ===
As I said before, I'm running Linux, which means I don't have any access to the tools I need to do post-production. So, I'll need to do finalization on this VM instead of my host. Start by installing Resource Hacker, ImgBurn and GImageX. Now, make a folder on your desktop called whatever you want and put two folders in there: "root" (for all the installation files) and "boot" (for the boot.wim file). Extract the contents of the Windows 7 ISO you used to the "root" folder. Open GImageX, navigate to Mount, then choose the boot.wim file from (root folder)/sources as the source and the "boot" folder as the destination. Also make sure to make it readable and writable. There's a lot of files here, most of them are system protected so you'll need to make them writable by you. There are many things you can modify but here's some important ones:
* <code>sources/background.bmp</code> - Background for the initial setup window asking for your language
* <code>sources/spwizimg.dll</code> - Most setup resources
* <code>Windows/System32/setup.bmp</code> - Background behind the initial setup window asking for your language
After you are done modifying, make sure to commit the changes before unmounting so your changes will take effect. Now to move onto the actual installer. The setup files to modify are the same as boot.wim, sans setup.bmp.

Copy the install.wim from the other drive to <code>sources/install.wim</code>.

== Create the ISO ==
Okay, I lied, this is the actual finalization. Open ImgBurn, select Create image file from files and folders. There are a few things to do here so lets get that out of the way.
=== Adding files ===
Pretty straightforward, click the folder icon next to Source and add each 5 folders to the ISO (boot, efi, sources, upgrade, support). Then, click the file icon and add the 4 files on the root (autorun.inf, bootmgr, bootmgr.efi, setup.exe). If you have any other files/folders you put on the root, add those too.
=== Make it bootable ===
Go to the Bootable Disc tab under Advanced, select Make Image Bootable then select (install files root)/boot/etfsboot.com and set the sectors to load to 8.
=== Labels ===
Go to the Labels tab and pick a label. Nothing much.
=== Create the image ===
Select a location for your ISO and click Build. If it says that it thinks its an OS installation disc, let it adjust the settings. It will then ask you if you want to create the image, select Yes. Wait for it to be finished and you should be notified with a sound that jumpscares me every time I hear it.

== You're done! ==
Congratulations, you've done it! If you've followed everything correctly, you should have a shiny new ISO containing your beautiful creation. I'm sure it's great. Anyway, you should test it out under a virtual machine or if you have another computer laying around, you can test it there too. If testing went well, you can upload it to a file host of your choice and share it with people. If you found something that went wrong, well uh, you're going to need to do that whole audit mode thing again. Hope you didn't screw anything up!

How to make a Windows bootleg/Windows7

2024-04-29T06:08:53Z

Kon:

{{Warn|I wrote this article at 2 AM. Beware of any things that sound stupid.}}
[[File:LMv2-Desktop.png|thumb|Windows 7 Linux Mint V2, a CollabSysOS release that I have worked on.]]
In this tutorial, I'll be going through how I make Windows 7 bootlegs. It's actually a very different process from Windows XP, however it is much easier. This tutorial will also work with Windows 8.x, 10 and 11 but we're going over Windows 7 in this guide. We're going to be using something called Audit Mode, introduced with Windows Vista.

== Pre-requisites ==
We'll be using these tools in the tutorial:
* A Windows 7 ISO: These are very common, I would recommend you use Windows 7 Professional SP1.
* Hiren's Boot CD: This is the PE you will be using to capture the image using DISM.
* Access to a Windows install: This could either be on your host or in a VM. I'm using Linux personally, so I'll have to install Windows in a VM to make the ISO, though you can just follow the steps on your host if you run Windows.
* Any file hosting service: Because where else will you store your ISO?
* A VM: Where else are we going to make the thing? You can use your favourite hypervisor, but we're using VMware Workstation in this tutorial. I have not tested VMware Player.
* Various utilities: Tools like Resource Hacker and UxTheme will be crucial to making your bootleg and also post-production. ImgBurn is also needed to make the ISO.
== Preparation ==
=== Download post-production tools ===
* [https://www.angusj.com/resourcehacker/ Resource Hacker]
* [https://www.imgburn.com/index.php?act=download ImgBurn]
* [https://www.autoitconsulting.com/site/software/gimagex/ GImageX]
=== Create a VM ===
Create a VM in Workstation, go through the necessary steps.
=== Acquire themes and programs ===
You'll actually be doing this step inside the VM, so wait until we reach Audit Mode, then gather everything.
== Boot into Audit Mode ==
You'll be greeted with the usual Windows 7 installer. Go through it as you would normally and wait for it to install. Go play a game, take a walk or whatever and when you come back you should be at the OOBE screen. This is the important part: Do '''''NOT''''' continue. Instead, press CTRL+SHIFT+F3. This will exit the OOBE and enter you into Audit Mode. And finally, here comes the real fun, making the bootleg.

== Make your changes ==
[[File:AuditModeFirstBoot.png|thumb|This is what you should see if you didn't fuck it up.]]
[[File:ThemePolicy.png|thumb|Theme policy setting. Replace "a.theme" with the name of your theme file.]]
You'll be greeted with that same Windows 7 desktop. You can close that sysprep window for now, it won't matter until you actually finish making your bootleg. Except, not yet. A few things to note here in Audit Mode and in general while creating your bootleg:
* You cannot log off or lock. This will disable the Administrator account, but this can be fixed with a reboot.
* You cannot modify the boot screen. This will invalidate the signature of winload and will make your bootleg unbootable upon installing it.
* Install programs for all users. Shortcuts should go in Public Desktop and the All Users start menu.
* To change the theme for all users at first login, go into gpedit.msc, navigate to User Configuration > Control Panel > Personalization > Load a specific theme and put the path to your theme file.
This pretty much functions like a normal Windows 7 install, and you're now on your own to customize it. Any questions should be redirected to my discord server in #bootleg-authoring.

== Post-production ==
=== Sysprepping ===
[[File:Sysprep.png|thumb|Sysprep options that should be selected]]
Reboot the system after you are finished editing and Sysprep should open when you logon. Check "Generalize" and "Shutdown" from the dropdown. This is a good time to check if you have anything else you want to do. If you want to do anything else, do it now because you won't get a chance later. Once you're ready, click OK and it should start. Wait a bit then it will shut down. Create a new disk in VMware to store the install.wim file on.

=== Capturing ===
Insert the HBCD ISO into the VM and then power it on to the BIOS. You'll need to change the boot order to boot from the DVD first, then reboot. HBCD should now start loading. When it does load, go into Disk Management and partition the new disk. Now, go into the Windows installation drive and delete the Administrator user folder. This will wipe all your previous traces. Now, FINALLY, start the command prompt and enter in the following command:
<pre>dism /capture-image /imagefile:(wim drive letter):\install.wim /capturedir:(windows install drive letter):\ /name:"Whatever You Want"</pre>
DISM will now start making your install.wim file. This may take a few minutes.

=== Finalization ===
As I said before, I'm running Linux, which means I don't have any access to the tools I need to do post-production. So, I'll need to do finalization on this VM instead of my host. Start by installing Resource Hacker, ImgBurn and GImageX. Now, make a folder on your desktop called whatever you want and put two folders in there: "root" (for all the installation files) and "boot" (for the boot.wim file). Extract the contents of the Windows 7 ISO you used to the "root" folder. Open GImageX, navigate to Mount, then choose the boot.wim file from (root folder)/sources as the source and the "boot" folder as the destination. Also make sure to make it readable and writable. There's a lot of files here, most of them are system protected so you'll need to make them writable by you. There are many things you can modify but here's some important ones:
* <code>sources/background.bmp</code> - Background for the initial setup window asking for your language
* <code>sources/spwizimg.dll</code> - Most setup resources
* <code>Windows/System32/setup.bmp</code> - Background behind the initial setup window asking for your language
After you are done modifying, make sure to commit the changes before unmounting so your changes will take effect. Now to move onto the actual installer. The setup files to modify are the same as boot.wim, sans setup.bmp.

== Create the ISO ==
Okay, I lied, this is the actual finalization. Open ImgBurn, select Create image file from files and folders. There are a few things to do here so lets get that out of the way.
=== Adding files ===
Pretty straightforward, click the folder icon next to Source and add each 5 folders to the ISO (boot, efi, sources, upgrade, support). Then, click the file icon and add the 4 files on the root (autorun.inf, bootmgr, bootmgr.efi, setup.exe). If you have any other files/folders you put on the root, add those too.
=== Make it bootable ===
Go to the Bootable Disc tab under Advanced, select Make Image Bootable then select (install files root)/boot/etfsboot.com and set the sectors to load to 8.
=== Labels ===
Go to the Labels tab and pick a label. Nothing much.
=== Create the image ===
Select a location for your ISO and click Build. If it says that it thinks its an OS installation disc, let it adjust the settings. It will then ask you if you want to create the image, select Yes. Wait for it to be finished and you should be notified with a sound that jumpscares me every time I hear it.

== You're done! ==
Congratulations, you've done it! If you've followed everything correctly, you should have a shiny new ISO containing your beautiful creation. I'm sure it's great. Anyway, you should test it out under a virtual machine or if you have another computer laying around, you can test it there too. If testing went well, you can upload it to a file host of your choice and share it with people. If you found something that went wrong, well uh, you're going to need to do that whole audit mode thing again. Hope you didn't screw anything up!

How to make a Windows bootleg/Windows7

2024-04-29T06:03:02Z

Kon:

[[File:LMv2-Desktop.png|thumb|Windows 7 Linux Mint V2, a CollabSysOS release that I have worked on.]]
In this tutorial, I'll be going through how I make Windows 7 bootlegs. It's actually a very different process from Windows XP, however it is much easier. This tutorial will also work with Windows 8.x, 10 and 11 but we're going over Windows 7 in this guide. We're going to be using something called Audit Mode, introduced with Windows Vista.

== Pre-requisites ==
We'll be using these tools in the tutorial:
* A Windows 7 ISO: These are very common, I would recommend you use Windows 7 Professional SP1.
* Hiren's Boot CD: This is the PE you will be using to capture the image using DISM.
* Access to a Windows install: This could either be on your host or in a VM. I'm using Linux personally, so I'll have to install Windows in a VM to make the ISO, though you can just follow the steps on your host if you run Windows.
* Any file hosting service: Because where else will you store your ISO?
* A VM: Where else are we going to make the thing? You can use your favourite hypervisor, but we're using VMware Workstation in this tutorial. I have not tested VMware Player.
* Various utilities: Tools like Resource Hacker and UxTheme will be crucial to making your bootleg and also post-production. ImgBurn is also needed to make the ISO.
== Preparation ==
=== Download post-production tools ===
* [https://www.angusj.com/resourcehacker/ Resource Hacker]
* [https://www.imgburn.com/index.php?act=download ImgBurn]
* [https://www.autoitconsulting.com/site/software/gimagex/ GImageX]
=== Create a VM ===
Create a VM in Workstation, go through the necessary steps.
=== Acquire themes and programs ===
You'll actually be doing this step inside the VM, so wait until we reach Audit Mode, then gather everything.
== Boot into Audit Mode ==
You'll be greeted with the usual Windows 7 installer. Go through it as you would normally and wait for it to install. Go play a game, take a walk or whatever and when you come back you should be at the OOBE screen. This is the important part: Do '''''NOT''''' continue. Instead, press CTRL+SHIFT+F3. This will exit the OOBE and enter you into Audit Mode. And finally, here comes the real fun, making the bootleg.

== Make your changes ==
[[File:AuditModeFirstBoot.png|thumb|This is what you should see if you didn't fuck it up.]]
[[File:ThemePolicy.png|thumb|Theme policy setting. Replace "a.theme" with the name of your theme file.]]
You'll be greeted with that same Windows 7 desktop. You can close that sysprep window for now, it won't matter until you actually finish making your bootleg. Except, not yet. A few things to note here in Audit Mode and in general while creating your bootleg:
* You cannot log off or lock. This will disable the Administrator account, but this can be fixed with a reboot.
* You cannot modify the boot screen. This will invalidate the signature of winload and will make your bootleg unbootable upon installing it.
* Install programs for all users. Shortcuts should go in Public Desktop and the All Users start menu.
* To change the theme for all users at first login, go into gpedit.msc, navigate to User Configuration > Control Panel > Personalization > Load a specific theme and put the path to your theme file.
This pretty much functions like a normal Windows 7 install, and you're now on your own to customize it. Any questions should be redirected to my discord server in #bootleg-authoring.

== Post-production ==
=== Sysprepping ===
[[File:Sysprep.png|thumb|Sysprep options that should be selected]]
Reboot the system after you are finished editing and Sysprep should open when you logon. Check "Generalize" and "Shutdown" from the dropdown. This is a good time to check if you have anything else you want to do. If you want to do anything else, do it now because you won't get a chance later. Once you're ready, click OK and it should start. Wait a bit then it will shut down. Create a new disk in VMware to store the install.wim file on.

=== Capturing ===
Insert the HBCD ISO into the VM and then power it on to the BIOS. You'll need to change the boot order to boot from the DVD first, then reboot. HBCD should now start loading. When it does load, go into Disk Management and partition the new disk. Now, go into the Windows installation drive and delete the Administrator user folder. This will wipe all your previous traces. Now, FINALLY, start the command prompt and enter in the following command:
<pre>dism /capture-image /imagefile:(wim drive letter):\install.wim /capturedir:(windows install drive letter):\ /name:"Whatever You Want"</pre>
DISM will now start making your install.wim file. This may take a few minutes.

=== Finalization ===
As I said before, I'm running Linux, which means I don't have any access to the tools I need to do post-production. So, I'll need to do finalization on this VM instead of my host. Start by installing Resource Hacker, ImgBurn and GImageX. Now, make a folder on your desktop called whatever you want and put two folders in there: "root" (for all the installation files) and "boot" (for the boot.wim file). Extract the contents of the Windows 7 ISO you used to the "root" folder. Open GImageX, navigate to Mount, then choose the boot.wim file from (root folder)/sources as the source and the "boot" folder as the destination. Also make sure to make it readable and writable. There's a lot of files here, most of them are system protected so you'll need to make them writable by you. There are many things you can modify but here's some important ones:
* <code>sources/background.bmp</code> - Background for the initial setup window asking for your language
* <code>sources/spwizimg.dll</code> - Most setup resources
* <code>Windows/System32/setup.bmp</code> - Background behind the initial setup window asking for your language
After you are done modifying, make sure to commit the changes before unmounting so your changes will take effect. Now to move onto the actual installer. The setup files to modify are the same as boot.wim, sans setup.bmp.

== Create the ISO ==
Okay, I lied, this is the actual finalization. Open ImgBurn, select Create image file from files and folders. There are a few things to do here so lets get that out of the way.
=== Adding files ===
Pretty straightforward, click the folder icon next to Source and add each 5 folders to the ISO (boot, efi, sources, upgrade, support). Then, click the file icon and add the 4 files on the root (autorun.inf, bootmgr, bootmgr.efi, setup.exe). If you have any other files/folders you put on the root, add those too.
=== Make it bootable ===
Go to the Bootable Disc tab under Advanced, select Make Image Bootable then select (install files root)/boot/etfsboot.com and set the sectors to load to 8.
=== Labels ===
Go to the Labels tab and pick a label. Nothing much.
=== Create the image ===
Select a location for your ISO and click Build. If it says that it thinks its an OS installation disc, let it adjust the settings. It will then ask you if you want to create the image, select Yes. Wait for it to be finished and you should be notified with a sound that jumpscares me every time I hear it.

== You're done! ==
Congratulations, you've done it! If you've followed everything correctly, you should have a shiny new ISO containing your beautiful creation. I'm sure it's great. Anyway, you should test it out under a virtual machine or if you have another computer laying around, you can test it there too. If testing went well, you can upload it to a file host of your choice and share it with people. If you found something that went wrong, well uh, you're going to need to do that whole audit mode thing again. Hope you didn't screw anything up!

How to make a Windows bootleg/Windows7

2024-04-29T06:00:45Z

Kon:

{{Warn|
'''Under Construction!'''
This article is still being worked on.}}
[[File:LMv2-Desktop.png|thumb|Windows 7 Linux Mint V2, a CollabSysOS release that I have worked on.]]
In this tutorial, I'll be going through how I make Windows 7 bootlegs. It's actually a very different process from Windows XP, however it is much easier. This tutorial will also work with Windows 8.x, 10 and 11 but we're going over Windows 7 in this guide. We're going to be using something called Audit Mode, introduced with Windows Vista.

== Pre-requisites ==
We'll be using these tools in the tutorial:
* A Windows 7 ISO: These are very common, I would recommend you use Windows 7 Professional SP1.
* Hiren's Boot CD: This is the PE you will be using to capture the image using DISM.
* Access to a Windows install: This could either be on your host or in a VM. I'm using Linux personally, so I'll have to install Windows in a VM to make the ISO, though you can just follow the steps on your host if you run Windows.
* Any file hosting service: Because where else will you store your ISO?
* A VM: Where else are we going to make the thing? You can use your favourite hypervisor, but we're using VMware Workstation in this tutorial. I have not tested VMware Player.
* Various utilities: Tools like Resource Hacker and UxTheme will be crucial to making your bootleg and also post-production. ImgBurn is also needed to make the ISO.
== Preparation ==
=== Download post-production tools ===
* [https://www.angusj.com/resourcehacker/ Resource Hacker]
* [https://www.imgburn.com/index.php?act=download ImgBurn]
* [https://www.autoitconsulting.com/site/software/gimagex/ GImageX]
=== Create a VM ===
Create a VM in Workstation, go through the necessary steps.
=== Acquire themes and programs ===
You'll actually be doing this step inside the VM, so wait until we reach Audit Mode, then gather everything.
== Boot into Audit Mode ==
You'll be greeted with the usual Windows 7 installer. Go through it as you would normally and wait for it to install. Go play a game, take a walk or whatever and when you come back you should be at the OOBE screen. This is the important part: Do '''''NOT''''' continue. Instead, press CTRL+SHIFT+F3. This will exit the OOBE and enter you into Audit Mode. And finally, here comes the real fun, making the bootleg.

== Make your changes ==
[[File:AuditModeFirstBoot.png|thumb|This is what you should see if you didn't fuck it up.]]
[[File:ThemePolicy.png|thumb|Theme policy setting. Replace "a.theme" with the name of your theme file.]]
You'll be greeted with that same Windows 7 desktop. You can close that sysprep window for now, it won't matter until you actually finish making your bootleg. Except, not yet. A few things to note here in Audit Mode and in general while creating your bootleg:
* You cannot log off or lock. This will disable the Administrator account, but this can be fixed with a reboot.
* You cannot modify the boot screen. This will invalidate the signature of winload and will make your bootleg unbootable upon installing it.
* Install programs for all users. Shortcuts should go in Public Desktop and the All Users start menu.
* To change the theme for all users at first login, go into gpedit.msc, navigate to User Configuration > Control Panel > Personalization > Load a specific theme and put the path to your theme file.
This pretty much functions like a normal Windows 7 install, and you're now on your own to customize it. Any questions should be redirected to my discord server in #bootleg-authoring.

== Post-production ==
=== Sysprepping ===
[[File:Sysprep.png|thumb|Sysprep options that should be selected]]
Reboot the system after you are finished editing and Sysprep should open when you logon. Check "Generalize" and "Shutdown" from the dropdown. This is a good time to check if you have anything else you want to do. If you want to do anything else, do it now because you won't get a chance later. Once you're ready, click OK and it should start. Wait a bit then it will shut down. Create a new disk in VMware to store the install.wim file on.

=== Capturing ===
Insert the HBCD ISO into the VM and then power it on to the BIOS. You'll need to change the boot order to boot from the DVD first, then reboot. HBCD should now start loading. When it does load, go into Disk Management and partition the new disk. Now, go into the Windows installation drive and delete the Administrator user folder. This will wipe all your previous traces. Now, FINALLY, start the command prompt and enter in the following command:
<pre>dism /capture-image /imagefile:(wim drive letter):\install.wim /capturedir:(windows install drive letter):\ /name:"Whatever You Want"</pre>
DISM will now start making your install.wim file. This may take a few minutes.

=== Finalization ===
As I said before, I'm running Linux, which means I don't have any access to the tools I need to do post-production. So, I'll need to do finalization on this VM instead of my host. Start by installing Resource Hacker, ImgBurn and GImageX. Now, make a folder on your desktop called whatever you want and put two folders in there: "root" (for all the installation files) and "boot" (for the boot.wim file). Extract the contents of the Windows 7 ISO you used to the "root" folder. Open GImageX, navigate to Mount, then choose the boot.wim file from (root folder)/sources as the source and the "boot" folder as the destination. Also make sure to make it readable and writable. There's a lot of files here, most of them are system protected so you'll need to make them writable by you. There are many things you can modify but here's some important ones:
* <code>sources/background.bmp</code> - Background for the initial setup window asking for your language
* <code>sources/spwizimg.dll</code> - Most setup resources
* <code>Windows/System32/setup.bmp</code> - Background behind the initial setup window asking for your language
After you are done modifying, make sure to commit the changes before unmounting so your changes will take effect. Now to move onto the actual installer. The setup files to modify are the same as boot.wim, sans setup.bmp.

== Create the ISO ==
Okay, I lied, this is the actual finalization. Open ImgBurn, select Create image file from files and folders. There are a few things to do here so lets get that out of the way.
=== Adding files ===
Pretty straightforward, click the folder icon next to Source and add each 5 folders to the ISO (boot, efi, sources, upgrade, support). Then, click the file icon and add the 4 files on the root (autorun.inf, bootmgr, bootmgr.efi, setup.exe). If you have any other files/folders you put on the root, add those too.
=== Make it bootable ===
Go to the Bootable Disc tab under Advanced, select Make Image Bootable then select (install files root)/boot/etfsboot.com and set the sectors to load to 8.
=== Labels ===
Go to the Labels tab and pick a label. Nothing much.
=== Create the image ===
Select a location for your ISO and click Build. If it says that it thinks its an OS installation disc, let it adjust the settings. It will then ask you if you want to create the image, select Yes. Wait for it to be finished and you should be notified with a sound that jumpscares me every time I hear it.

== You're done! ==
Congratulations, you've done it! If you've followed everything correctly, you should have a shiny new ISO containing your beautiful creation. I'm sure it's great. Anyway, you should test it out under a virtual machine or if you have another computer laying around, you can test it there too. If testing went well, you can upload it to a file host of your choice and share it with people. If you found something that went wrong, well uh, you're going to need to do that whole audit mode thing again. Hope you didn't screw anything up!

How to make a Windows bootleg/Windows7

2024-04-29T06:00:12Z

Kon:

{{Warn|
'''Under Construction!'''
This article is still being worked on.}}
[[File:LMv2-Desktop.png|thumb|Windows 7 Linux Mint V2, a CollabSysOS release that I have worked on.]]
In this tutorial, I'll be going through how I make Windows 7 bootlegs. It's actually a very different process from Windows XP, however it is much easier. This tutorial will also work with Windows 8.x, 10 and 11 but we're going over Windows 7 in this guide. We're going to be using something called Audit Mode, introduced with Windows Vista.

== Pre-requisites ==
We'll be using these tools in the tutorial:
* A Windows 7 ISO: These are very common, I would recommend you use Windows 7 Professional SP1.
* Hiren's Boot CD: This is the PE you will be using to capture the image using DISM.
* Access to a Windows install: This could either be on your host or in a VM. I'm using Linux personally, so I'll have to install Windows in a VM to make the ISO, though you can just follow the steps on your host if you run Windows.
* Any file hosting service: Because where else will you store your ISO?
* A VM: Where else are we going to make the thing? You can use your favourite hypervisor, but we're using VMware Workstation in this tutorial. I have not tested VMware Player.
* Various utilities: Tools like Resource Hacker and UxTheme will be crucial to making your bootleg and also post-production. ImgBurn is also needed to make the ISO.
== Preparation ==
=== Download post-production tools ===
* [https://www.angusj.com/resourcehacker/ Resource Hacker]
* [https://www.imgburn.com/index.php?act=download ImgBurn]
* [https://www.autoitconsulting.com/site/software/gimagex/ GImageX]
=== Create a VM ===
Create a VM in Workstation, go through the necessary steps.
=== Acquire themes and programs ===
You'll actually be doing this step inside the VM, so wait until we reach Audit Mode, then gather everything.
== Boot into Audit Mode ==
You'll be greeted with the usual Windows 7 installer. Go through it as you would normally and wait for it to install. Go play a game, take a walk or whatever and when you come back you should be at the OOBE screen. This is the important part: Do '''''NOT''''' continue. Instead, press CTRL+SHIFT+F3. This will exit the OOBE and enter you into Audit Mode. And finally, here comes the real fun, making the bootleg.

== Make your changes ==
[[File:AuditModeFirstBoot.png|thumb|This is what you should see if you didn't fuck it up.]]
[[File:ThemePolicy.png|thumb|Theme policy setting. Replace "a.theme" with the name of your theme file.]]
You'll be greeted with that same Windows 7 desktop. You can close that sysprep window for now, it won't matter until you actually finish making your bootleg. Except, not yet. A few things to note here in Audit Mode and in general while creating your bootleg:
* You cannot log off or lock. This will disable the Administrator account, but this can be fixed with a reboot.
* You cannot modify the boot screen. This will invalidate the signature of winload and will make your bootleg unbootable upon installing it.
* Install programs for all users. Shortcuts should go in Public Desktop and the All Users start menu.
* To change the theme for all users at first login, go into gpedit.msc, navigate to User Configuration > Control Panel > Personalization > Load a specific theme and put the path to your theme file.
This pretty much functions like a normal Windows 7 install, and you're now on your own to customize it. Any questions should be redirected to my discord server in #bootleg-authoring.

== Post-production ==
=== Sysprepping ===
[[File:Sysprep.png|thumb|Sysprep options that should be selected]]
Reboot the system after you are finished editing and Sysprep should open when you logon. Check "Generalize" and "Shutdown" from the dropdown. This is a good time to check if you have anything else you want to do. If you want to do anything else, do it now because you won't get a chance later. Once you're ready, click OK and it should start. Wait a bit then it will shut down. Create a new disk in VMware to store the install.wim file on.

=== Capturing ===
Insert the HBCD ISO into the VM and then power it on to the BIOS. You'll need to change the boot order to boot from the DVD first, then reboot. HBCD should now start loading. When it does load, go into Disk Management and partition the new disk. Now, go into the Windows installation drive and delete the Administrator user folder. This will wipe all your previous traces. Now, FINALLY, start the command prompt and enter in the following command:
<pre>dism /capture-image /imagefile:(wim drive letter):\install.wim /capturedir:(windows install drive letter):\ /name:"Whatever You Want"</pre>
DISM will now start making your install.wim file. This may take a few minutes.

=== Finalization ===
As I said before, I'm running Linux, which means I don't have any access to the tools I need to do post-production. So, I'll need to do finalization on this VM instead of my host. Start by installing Resource Hacker, ImgBurn and GImageX. Now, make a folder on your desktop called whatever you want and put two folders in there: "root" (for all the installation files) and "boot" (for the boot.wim file). Extract the contents of the Windows 7 ISO you used to the "root" folder. Open GImageX, navigate to Mount, then choose the boot.wim file from (root folder)/sources as the source and the "boot" folder as the destination. Also make sure to make it readable and writable. There's a lot of files here, most of them are system protected so you'll need to make them writable by you. There are many things you can modify but here's some important ones:
* <code>sources/background.bmp</code> - Background for the initial setup window asking for your language
* <code>sources/spwizimg.dll</code> - Most setup resources
* <code>Windows/System32/setup.bmp</code> - Background behind the initial setup window asking for your language
After you are done modifying, make sure to commit the changes before unmounting so your changes will take effect. Now to move onto the actual installer. The setup files to modify are the same as boot.wim, sans setup.bmp.

=== Create the ISO ===
Okay, I lied, this is the actual finalization. Open ImgBurn, select Create image file from files and folders. There are a few things to do here so lets get that out of the way.
=== Adding files ===
Pretty straightforward, click the folder icon next to Source and add each 5 folders to the ISO (boot, efi, sources, upgrade, support). Then, click the file icon and add the 4 files on the root (autorun.inf, bootmgr, bootmgr.efi, setup.exe). If you have any other files/folders you put on the root, add those too.
=== Make it bootable ===
Go to the Bootable Disc tab under Advanced, select Make Image Bootable then select (install files root)/boot/etfsboot.com and set the sectors to load to 8.
=== Labels ===
Go to the Labels tab and pick a label. Nothing much.
=== Create the image ===
Select a location for your ISO and click Build. If it says that it thinks its an OS installation disc, let it adjust the settings. It will then ask you if you want to create the image, select Yes. Wait for it to be finished and you should be notified with a sound that jumpscares me every time I hear it.

== You're done! ==
Congratulations, you've done it! If you've followed everything correctly, you should have a shiny new ISO containing your beautiful creation. I'm sure it's great. Anyway, you should test it out under a virtual machine or if you have another computer laying around, you can test it there too. If testing went well, you can upload it to a file host of your choice and share it with people. If you found something that went wrong, well uh, you're going to need to do that whole audit mode thing again. Hope you didn't screw anything up!

File:Sysprep.png

2024-04-29T05:12:25Z

Kon:

File:ThemePolicy.png

2024-04-29T05:04:13Z

Kon:

File:AuditModeFirstBoot.png

2024-04-29T03:40:24Z

Kon:

How to make a Windows bootleg/Windows7

2024-04-29T03:34:11Z

Kon: professional is what i use

How to make a Windows bootleg/Windows7

2024-04-29T03:31:47Z

Kon: waiting for my thing to install

How to make a Windows bootleg/Windows7

2024-04-29T03:24:21Z

Kon:

Template:Warn

2024-04-29T03:18:50Z

Kon: Created page with "<div class="user-block" style="padding: 5px; margin-bottom: 0.5em; border: 1px solid #ffffaa; background-color: #ffff66; min-height: 40px;">alt=Warning icon<div style="margin-left:45px">{{{1}}}</div></div>"

<div class="user-block" style="padding: 5px; margin-bottom: 0.5em; border: 1px solid #ffffaa; background-color: #ffff66; min-height: 40px;">[[File:Warning.png|40px|left|alt=Warning icon]]<div style="margin-left:45px">{{{1}}}</div></div>

File:Warning.png

2024-04-29T03:18:40Z

Kon:

File:LMv2-Desktop.png

2024-04-29T03:05:35Z

Kon:

Super Monkey Ball unused levels

2024-04-24T05:15:57Z

Kon: /* Arcade leftovers */ Redundant

[[File:SMB1-ArcadeMaster.png|thumb|Unused Stage 30]]
Super Monkey Ball 1 on the GameCube has its fair share of unused levels. Most of these are direct rips from the arcade version, or broken/cut content from the official game. To access these, you'll need to enter the debug mode with this Action Replay code: FP4C-4E4V-9BN0U (atleast for GMBE8P)

== Arcade leftovers ==
=== Stage 10 ===
Exactly the same as Expert 28 from Monkey Ball.
=== Stage 19 ===
Exactly the same as Beginner 2 from Monkey Ball.
=== Stage 20 ===
Exactly the same as Expert 9 from Monkey Ball. Noticing a pattern?
=== Stage 30 ===
Exactly the same as the original Monkey Ball master stage. This would later re-appear in Master 9 in the final game.
=== Stage 49 ===
Exactly the same as Advanced 4 from Monkey Ball. Why were these even left in any way?
=== Stage 50 ===
Exactly the same as Expert Extra 6 from Monkey Ball.
=== Stage 60 ===
Exactly the same as Expert Extra 9 from Monkey Ball.
=== Stage 70 ===
Exactly the same as Beginner Extra 2 from Monkey Ball.
=== Stage 80 ===
Exactly the same as Beginner Extra 3 from Monkey Ball.
=== Stage 96 ===
Exactly the same as Expert 23 from Monkey Ball.
=== Stage 97 ===
Exactly the same as Expert 12 from Monkey Ball.
=== Stage 98 ===
Exactly the same as Expert 29 from Monkey Ball.
=== Stage 100 ===
Exactly the same as Advanced Extra 5 from Monkey Ball.
=== Stage 114 ===
This is an unused level from Monkey Ball. It goes unused in this game, too. The arrows do nothing.
=== Stage 117 ===
Exactly the same as Advanced 7 from Monkey Ball. Unfortunately the sky box is gone.
=== Stage 118 ===
Exactly the same as Advanced 19 from Monkey Ball.
=== Stage 119 ===
Exactly the same as Expert 11 from Monkey Ball.
=== Stage 120 ===
Exactly the same as Expert 6 from Monkey Ball.
<gallery>
SMB1-Stage10.png|Stage 10
SMB1-Stage19.png|Stage 19
SMB1-Stage20.png|Stage 20
SMB1-Stage30.png|Stage 30
SMB1-Stage49.png|Stage 49
SMB1-Stage50.png|Stage 50
SMB1-Stage60.png|Stage 60
SMB1-Stage70.png|Stage 70
SMB1-Stage80.png|Stage 80
SMB1-Stage96.png|Stage 96
SMB1-Stage97.png|Stage 97
SMB1-Stage98.png|Stage 98
SMB1-Stage100.png|Stage 100
SMB1-Stage114.png|Stage 114
SMB1-Stage117.png|Stage 117
SMB1-Stage118.png|Stage 118
SMB1-Stage119.png|Stage 119
SMB1-Stage120.png|Stage 120
</gallery>

== Cut official content ==
This is where stuff gets interesting. Not a whole lot here though.
=== Stage 99 ===
A completely empty stage. Quite stellar to look at!
=== Stage 132 ===
An unused Monkey Race track.
=== Stage 141 ===
A goal-less orange platform with the rocks from extra's background.
=== Stage 142 ===
Another goal-less platform. This time with walls and a water effect!
=== Stage 146 ===
A grey platform with a goal and a start position with the rocks from extra's background.
=== Stage 150 ===
Technically not unused, but this is the tutorial level that is shown on the title screen.
=== Stage 154 ===
It's a ramp.
=== Stage 155 ===
Nothing but water.
<gallery>
SMB1-Stage99.png|Stage 99
SMB1-Stage132.png|Stage 132
SMB1-Stage141.png|Stage 141
SMB1-Stage142.png|Stage 142
SMB1-Stage146.png|Stage 146
SMB1-Stage150.png|Stage 150
SMB1-Stage154.png|Stage 154
SMB1-Stage155.png|Stage 155
</gallery>

Super Monkey Ball unused levels

2024-04-24T05:10:10Z

Kon:

[[File:SMB1-ArcadeMaster.png|thumb|Unused Stage 30]]
Super Monkey Ball 1 on the GameCube has its fair share of unused levels. Most of these are direct rips from the arcade version, or broken/cut content from the official game. To access these, you'll need to enter the debug mode with this Action Replay code: FP4C-4E4V-9BN0U (atleast for GMBE8P)

== Arcade leftovers ==
When we say Monkey Ball, we are referring to the arcade version, as the arcade version was called that.
=== Stage 10 ===
Exactly the same as Expert 28 from Monkey Ball.
=== Stage 19 ===
Exactly the same as Beginner 2 from Monkey Ball.
=== Stage 20 ===
Exactly the same as Expert 9 from Monkey Ball. Noticing a pattern?
=== Stage 30 ===
Exactly the same as the original Monkey Ball master stage. This would later re-appear in Master 9 in the final game.
=== Stage 49 ===
Exactly the same as Advanced 4 from Monkey Ball. Why were these even left in any way?
=== Stage 50 ===
Exactly the same as Expert Extra 6 from Monkey Ball.
=== Stage 60 ===
Exactly the same as Expert Extra 9 from Monkey Ball.
=== Stage 70 ===
Exactly the same as Beginner Extra 2 from Monkey Ball.
=== Stage 80 ===
Exactly the same as Beginner Extra 3 from Monkey Ball.
=== Stage 96 ===
Exactly the same as Expert 23 from Monkey Ball.
=== Stage 97 ===
Exactly the same as Expert 12 from Monkey Ball.
=== Stage 98 ===
Exactly the same as Expert 29 from Monkey Ball.
=== Stage 100 ===
Exactly the same as Advanced Extra 5 from Monkey Ball.
=== Stage 114 ===
This is an unused level from Monkey Ball. It goes unused in this game, too. The arrows do nothing.
=== Stage 117 ===
Exactly the same as Advanced 7 from Monkey Ball. Unfortunately the sky box is gone.
=== Stage 118 ===
Exactly the same as Advanced 19 from Monkey Ball.
=== Stage 119 ===
Exactly the same as Expert 11 from Monkey Ball.
=== Stage 120 ===
Exactly the same as Expert 6 from Monkey Ball.
<gallery>
SMB1-Stage10.png|Stage 10
SMB1-Stage19.png|Stage 19
SMB1-Stage20.png|Stage 20
SMB1-Stage30.png|Stage 30
SMB1-Stage49.png|Stage 49
SMB1-Stage50.png|Stage 50
SMB1-Stage60.png|Stage 60
SMB1-Stage70.png|Stage 70
SMB1-Stage80.png|Stage 80
SMB1-Stage96.png|Stage 96
SMB1-Stage97.png|Stage 97
SMB1-Stage98.png|Stage 98
SMB1-Stage100.png|Stage 100
SMB1-Stage114.png|Stage 114
SMB1-Stage117.png|Stage 117
SMB1-Stage118.png|Stage 118
SMB1-Stage119.png|Stage 119
SMB1-Stage120.png|Stage 120
</gallery>

== Cut official content ==
This is where stuff gets interesting. Not a whole lot here though.
=== Stage 99 ===
A completely empty stage. Quite stellar to look at!
=== Stage 132 ===
An unused Monkey Race track.
=== Stage 141 ===
A goal-less orange platform with the rocks from extra's background.
=== Stage 142 ===
Another goal-less platform. This time with walls and a water effect!
=== Stage 146 ===
A grey platform with a goal and a start position with the rocks from extra's background.
=== Stage 150 ===
Technically not unused, but this is the tutorial level that is shown on the title screen.
=== Stage 154 ===
It's a ramp.
=== Stage 155 ===
Nothing but water.
<gallery>
SMB1-Stage99.png|Stage 99
SMB1-Stage132.png|Stage 132
SMB1-Stage141.png|Stage 141
SMB1-Stage142.png|Stage 142
SMB1-Stage146.png|Stage 146
SMB1-Stage150.png|Stage 150
SMB1-Stage154.png|Stage 154
SMB1-Stage155.png|Stage 155
</gallery>

File:SMB1-ArcadeMaster.png

2024-04-24T05:09:00Z

Kon:

Super Monkey Ball unused levels

2024-04-23T23:04:10Z

Kon: Created page with "Super Monkey Ball 1 on the GameCube has its fair share of unused levels. Most of these are direct rips from the arcade version, or broken/cut content from the official game. To access these, you'll need to enter the debug mode with this Action Replay code: FP4C-4E4V-9BN0U (atleast for GMBE8P) == Arcade leftovers == When we say Monkey Ball, we are referring to the arcade version, as the arcade version was called that. === Stage 10 === Exactly the same as Expert 28 from M..."

Super Monkey Ball 1 on the GameCube has its fair share of unused levels. Most of these are direct rips from the arcade version, or broken/cut content from the official game. To access these, you'll need to enter the debug mode with this Action Replay code: FP4C-4E4V-9BN0U (atleast for GMBE8P)

== Arcade leftovers ==
When we say Monkey Ball, we are referring to the arcade version, as the arcade version was called that.
=== Stage 10 ===
Exactly the same as Expert 28 from Monkey Ball.
=== Stage 19 ===
Exactly the same as Beginner 2 from Monkey Ball.
=== Stage 20 ===
Exactly the same as Expert 9 from Monkey Ball. Noticing a pattern?
=== Stage 30 ===
Exactly the same as the original Monkey Ball master stage. This would later re-appear in Master 9 in the final game.
=== Stage 49 ===
Exactly the same as Advanced 4 from Monkey Ball. Why were these even left in any way?
=== Stage 50 ===
Exactly the same as Expert Extra 6 from Monkey Ball.
=== Stage 60 ===
Exactly the same as Expert Extra 9 from Monkey Ball.
=== Stage 70 ===
Exactly the same as Beginner Extra 2 from Monkey Ball.
=== Stage 80 ===
Exactly the same as Beginner Extra 3 from Monkey Ball.
=== Stage 96 ===
Exactly the same as Expert 23 from Monkey Ball.
=== Stage 97 ===
Exactly the same as Expert 12 from Monkey Ball.
=== Stage 98 ===
Exactly the same as Expert 29 from Monkey Ball.
=== Stage 100 ===
Exactly the same as Advanced Extra 5 from Monkey Ball.
=== Stage 114 ===
This is an unused level from Monkey Ball. It goes unused in this game, too. The arrows do nothing.
=== Stage 117 ===
Exactly the same as Advanced 7 from Monkey Ball. Unfortunately the sky box is gone.
=== Stage 118 ===
Exactly the same as Advanced 19 from Monkey Ball.
=== Stage 119 ===
Exactly the same as Expert 11 from Monkey Ball.
=== Stage 120 ===
Exactly the same as Expert 6 from Monkey Ball.
<gallery>
SMB1-Stage10.png|Stage 10
SMB1-Stage19.png|Stage 19
SMB1-Stage20.png|Stage 20
SMB1-Stage30.png|Stage 30
SMB1-Stage49.png|Stage 49
SMB1-Stage50.png|Stage 50
SMB1-Stage60.png|Stage 60
SMB1-Stage70.png|Stage 70
SMB1-Stage80.png|Stage 80
SMB1-Stage96.png|Stage 96
SMB1-Stage97.png|Stage 97
SMB1-Stage98.png|Stage 98
SMB1-Stage100.png|Stage 100
SMB1-Stage114.png|Stage 114
SMB1-Stage117.png|Stage 117
SMB1-Stage118.png|Stage 118
SMB1-Stage119.png|Stage 119
SMB1-Stage120.png|Stage 120
</gallery>

== Cut official content ==
This is where stuff gets interesting. Not a whole lot here though.
=== Stage 99 ===
A completely empty stage. Quite stellar to look at!
=== Stage 132 ===
An unused Monkey Race track.
=== Stage 141 ===
A goal-less orange platform with the rocks from extra's background.
=== Stage 142 ===
Another goal-less platform. This time with walls and a water effect!
=== Stage 146 ===
A grey platform with a goal and a start position with the rocks from extra's background.
=== Stage 150 ===
Technically not unused, but this is the tutorial level that is shown on the title screen.
=== Stage 154 ===
It's a ramp.
=== Stage 155 ===
Nothing but water.
<gallery>
SMB1-Stage99.png|Stage 99
SMB1-Stage132.png|Stage 132
SMB1-Stage141.png|Stage 141
SMB1-Stage142.png|Stage 142
SMB1-Stage146.png|Stage 146
SMB1-Stage150.png|Stage 150
SMB1-Stage154.png|Stage 154
SMB1-Stage155.png|Stage 155
</gallery>

File:SMB1-Stage142.png

2024-04-23T22:44:52Z