SLAX Cheat codes; Booting parameters or cheat codes are used to manipulate the startup booting process of Linux. Some of them are common for all Linux versions, others are specific to SLAX only. You can use cheat codes to enable or disable specific hardware detection, to start SLAX from a hard disk or other media, to skip the login prompt and start GUI, etc.
How and when to use SLAX Cheat Codes:
Start to boot your computer waiting until the SLAX logo appears with a boot menu. Select your entry and hit Tab key, enabling you to edit the command string. Add any of the following boot code arguments to the end of command string.
SLAX Cheat codes and their functions
Disables specified hardware autodetection in the case of hangups. Your hardware won’t be detected at all, you’ll have to use the “pcimodules” command after logging into SLAX and you’ll have to try to modprobe all needed modules from the list manually
Disable DMA for all CD-ROMs and disks
Don’t mount any harddisks at all.
Don’t mount any cdroms at all.
Mute sound instead of raising volume to 77%
To load SLAX data from different place instead of the boot device. First example will search for slax.iso, only on hda1. Second example will search for ‘path/to/slax.iso’ on all devices. The first device containing the path/file is used. Third example expects that the ISO is unpacked to hda1. Fourth example searches through all disks for a directory ‘path/to/slax’ and expects the contents of unpacked ISO in there.
Set root’s password to “somepass”, or ask (with =ask) for a new password during the boot, before starting slax (don’t worry, the new password won’t be shown at the login screen)
All changes you made in SLAX are kept in memory until you reboot. But with this boot parameter, you tell SLAX to use different device then memory for storing changes. You can, for example, format your disk partition /dev/hda1 with some Linux filesystem (eg. ext2) and then use changes=/dev/hda1 to store all changes to that disk. This way you won’t loose your changes after reboot.
toram copies all files (all required and optional modules) to RAM. You’ll need at least as much RAM as the ISO to do this and boot SLAX properly. This will slow down the boot phase but it will speed up SLAX!
perch is used For enabling persistence. Persistently saving and restoring your changes on subsequent boots.
Load optional modules from /optional/ directory on the CD. You can use full module name (module.mo) or you can skip the extension.
Disable loading of any modules specified. This affects all the modules on SLAX CD, including /base and /modules, so using noload=kde will disable loading of all modules with ‘kde’ in the name. noload=apps|chromium would disable loading of the chromium browser. This boot parameter is useful with copy2ram or toram cheatcode, because any un-used module is not copied to ram, therefore saving space.
Enable debug mode (start bash several times during the boot) hit Ctrl+D to continue booting.
Execute specified command(s) instead of SLAX login. In this example, skip slax login prompt and automatically start XWindow system. Use semicolon (;) as command separator.
This concludes the usage of SLAX cheat codes or boot codes. Learn more about SLAX from the authors Site