Mac OS Extended. Choose one of the following Mac OS Extended file system formats for compatibility with Mac computers using macOS 10.12 or earlier. Mac OS Extended (Journaled): Uses the Mac format (Journaled HFS Plus) to protect the integrity of the hierarchical file system. Choose this option if you don’t need an encrypted or case-sensitive.

1. Copy a Bootable Mac OS 9 Install Disc So with the recent turning of the calendar, I looked at my Tiger and OS 9 install discs and it occurred to me they're getting on in years and very far from invincible.
2. The media creation tool mentioned previously can also write a downloaded ISO file to a USB drive in one go, and so create a bootable USB – but it only works with Windows 10. There are, though, many freeware programs suitable for all operating systems (including Linux) that can take over the tasks of the otherwise manual device management.
3. Partition and format the drive as a boot volume. Copy the Windows CD and the recovered data to the drive. Make sure to copy device drivers and the ZIP software onto the drive.

First of all, you'll need Roxio's Toast, CharisMac's Discribe or other CD burning software to make a bootable CD, because Apple's Disc Burner can't create bootable CDs.
This is a way that can be used with different burning applications (they just have to be able to install the necessary wrapper code to make a volume bootable):
*start Disk Copy (usually located in the Utilities-folder), select Image>>>Create new Image.. from the menu
* fill in a name for the CD, make sure that a size of 663,000K (CD-ROM 12cm, full) is selected and 'Mount Image' is checked (checking the 'Zero blocks'-option also is a good idea)
*save the image (usually to the desktop)
*you can now use a Mac OS installer (your original Mac OS install CD, for example) to install a System Folder to that disc image (once installed, you can also update that system using any [download] updater) and add all applications you want (try to install them whenever possible, because simply copying things over will not always work)
*when using Mac OS 9.2.x, remove these files from the System Folder: 'Classic', 'Classic Support' and 'Classic Support UI'
*now run those applications on the disk image which require registration (e.g. a serial number) - otherwise they will ask for registration when booted from the CD and therefore might not work
*disable any AutoUpdate- / LiveUpdate-features, as the applications on the CD can't be updated anyway once they've been burned
*when running applications from the disk image, some applications might create preference files in the System Folder you are currently booted to - in that case, just copy those preference files to the System Folder on the disk image afterwards
*now you should remove anything that may have been stored in 'Startup Items' or 'Shutdown Items' inside the disk image's System Folder; you might also want to remove some useless control panels, extensions, etc. and set the Energy Saver control panel to 'never go to sleep'; also set all other preferences/control panels to your preferred settings (once again, you might need to copy files over from the System Folder you're booted to for these changes to take effect)
*when finished, burn the CD [when using Toast Titanium, set it to 'Other', select 'Mac Volume', click 'Select', choose the disc image from the menu, select 'bootable' and click 'Record'] - in case you're given the choice, make sure to select 'Mac OS Standard (HFS)' volume format, not 'Mac OS Extended (HFS+)'
Useful links:
* Mac OS 9.1 updater (updates Mac OS 9.0 - 9.0.4 to 9.1)
* Mac OS 9.2.1 updater (updates Mac OS 9.1 or 9.2 to 9.2.1)
* Mac OS 9.2.2 updater (updates Mac OS 9.2.1 to 9.2.2)
* Disk First Aid 8.6.1 (in case you use an earlier version)
* Movie from Macworld on the subject
* How do I make a bootable CD for my Mac using Toast? (Article from Roxio's Knowledge Base)
* Bootable CD tips from Symantec (Norton Utilities)

This page discusses various multi-platform methods on how to create an Arch Linux Installer USB drive (also referred to as 'flash drive', 'USB stick', 'USB key', etc) for booting in BIOS and UEFI systems. The result will be a LiveUSB (LiveCD-like) system that can be used for installing Arch Linux, system maintenance or for recovery purposes, and that, because of the nature of SquashFS, will discard all changes once the computer shuts down.

If you would like to run a full install of Arch Linux from a USB drive (i.e. with persistent settings), see Installing Arch Linux on a USB key. If you would like to use your bootable Arch Linux USB stick as a rescue USB, see Change root.

BIOS and UEFI bootable USB

Using automatic tools

In GNU/Linux

Using basic command line utilities

This method is recommended due to its simplicity and universal availability, since these tools are part of coreutils (pulled in by the base meta-package).

Run the following command, replacing /dev/sdx with your drive, e.g. /dev/sdb. (Do not append a partition number, so do not use something like /dev/sdb1):

• using cat:
• using cp:
• using dd:
• using tee:

See [1] and [2] for a comparison and perspective on the use of those tools and why dd may be the least adapted one.

Using GNOME Disk Utility

Linux distributions running GNOME can easily make a live CD through nautilus and gnome-disk-utility. Simply right-click on the .iso file, and select Open With Disk Image Writer. When GNOME Disk Utility opens, specify the flash drive from the Destination drop-down menu and click Start Restoring.

Using MultiWriter

gnome-multi-writer is a simple GTK3 based graphical tool to write an ISO file to one or multiple USB devices at once.

Using Kindd

Kindd is a Qt based graphical frontend for dd. It is available as kindd^AUR.

Using etcher

Etcher is a OS image flasher built with node.js and Electron, capable of flashing an SDCard or USB drive. It protects you from accidentally writing to your hard-drives and ensures every byte of data was written correctly. There are 5 related packages in the AUR.

Using ventoy

Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. With ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)EFI files to the USB drive and boot them directly. You can copy many files at a time and ventoy will give you a boot menu to select them. It is available in the AUR as ventoy-bin^AUR.

In Windows

Using Rufus

Rufus is a multi-purpose USB ISO writer. It provides a graphical user interface and does not care if the drive is properly formatted or not.

Simply select the Arch Linux ISO, the USB drive you want to create the bootable Arch Linux onto and click START.

Using USBwriter

This method does not require any workaround and is as straightforward as dd under Linux. Just download the Arch Linux ISO, and with local administrator rights use the USBwriter utility to write to your USB flash memory.

Using win32diskimager

win32diskimager is another graphical USB iso writing tool for Windows. Simply select your iso image and the target USB drive letter (you may have to format it first to assign it a drive letter), and click Write.

Create Bootable Copy Of Mac Os 9.1 On Zip Driver

Using Cygwin

Make sure your Cygwin installation contains the dd package.

Place your image file in your home directory:

Run cygwin as administrator (required for cygwin to access hardware). To write to your USB drive use the following command:

where image.iso is the path to the iso image file within the cygwin directory and .x: is your USB flash drive where x is the windows designated letter, e.g. .d:.

On Cygwin 6.0, find out the correct partition with:

and write the ISO image with the information from the output. Example:

dd for Windows

Create Bootable Copy Of Mac Os 9.1 On Zip Drive Windows 10

A GPL licensed dd version for Windows is available at http://www.chrysocome.net/dd. The advantage of this over Cygwin is a smaller download. Use it as shown in instructions for Cygwin above.

To begin, download the latest version of dd for Windows. Once downloaded, extract the archive's contents into Downloads or elsewhere.

Now, launch your command prompt as an administrator. Next, change directory (cd) into the Downloads directory.

If your Arch Linux ISO is elsewhere you may need to state the full path, for convenience you may wish to put the Arch Linux ISO into the same folder as the dd executable. The basic format of the command will look like this.

Simply replace the various null spots (indicated by an 'x') with the correct date and correct drive letter. Here is a complete example.

The factual accuracy of this article or section is disputed.

Note: Alternatively, replace the drive letter with .PhysicalDriveX, where X is the physical drive number (starts from 0). Example:

You can find out the physical drive number by typing wmic diskdrive list brief at the command prompt or with dd --list

Any Explorer window must be closed or dd will report an error.

Using ventoy

Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. With ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)EFI files to the USB drive and boot them directly. You can copy many files at a time and ventoy will give you a boot menu to select them.

In macOS

First, you need to identify the USB device. Open /Applications/Utilities/Terminal and list all storage devices with the command:

Your USB device will appear as something like /dev/disk2 (external, physical). Verify that this is the device you want to erase by checking its name and size and then use its identifier for the commands below instead of /dev/diskX.

A USB device is normally auto-mounted in macOS, and you have to unmount (not eject) it before block-writing to it with dd. In Terminal, do:

Now copy the ISO image file to the device. The dd command is similar to its Linux counterpart, but notice the 'r' before 'disk' for raw mode which makes the transfer much faster:

On newer dd you should use 'bs=1M', e.g.

This command will run silently. To view progress, send SIGINFO by pressing Ctrl+t. Note diskX here should not include the s1 suffix, or else the USB device will only be bootable in UEFI mode and not legacy. After completion, macOS may complain that 'The disk you inserted was not readable by this computer'. Select 'Ignore'. The USB device will be bootable.

In Android

EtchDroid

EtchDroid is a OS image flasher for Android. It works without root permissions on Android 5 to Android 8. According to bug reports it doesn't always work on Android 9 and Android 4.4.

To create an Arch Linux installer, download the ISO image file on your Android device. Plug the USB drive to your device, using a USB-OTG adapter if needed. Open EtchDroid, select 'Flash raw image', select your Arch ISO, then select your USB drive. Download uc browser for mobile. Grant the USB API permission and confirm.

Keep your phone on a table while it's writing the image: a lot of USB-OTG adapters are a bit wobbly and you might unplug it by mistake.

Using manual formatting

This article or section needs expansion.

In GNU/Linux

This method is more complicated than writing the image directly with dd, but it does keep the flash drive usable for data storage (that is, the ISO is installed in a specific partition within the already partitioned device without altering other partitions).

• If not done yet, create a partition table on /dev/sdX.
• If not done yet, create a partition on the device. The partition /dev/sdXn must be formatted to FAT32.
• Mount the ISO image, mount the FAT32 filesystem located in the USB flash device, and copy the contents of the ISO image to it. Then unmount the ISO image, but keep the FAT32 partition mounted (this may be used in subsequent steps). For example:

Booting requires specifying the volume on which the files reside. By default the label ARCH_YYYYMM (with the appropriate release year and month) is used. Thus, the file system’s label has to be set accordingly. Alternatively, you can change this behaviour by altering the lines ending by archisolabel=ARCH_YYYYMM in the file /mnt/usb/arch/boot/syslinux/archiso_sys.cfg (for BIOS boot), and in /mnt/usb/loader/entries/archiso-x86_64.conf (for UEFI boot). For example, to use an UUID instead, replace those portions of lines with archisodevice=/dev/disk/by-uuid/YOUR-UUID.

Syslinux files for BIOS systems are already copied to /mnt/usb/arch/boot/syslinux. Install the syslinux package and follow Syslinux#Manual install instructions to make the partition bootable.

In Windows

Note:

• For manual formatting, do not use any Bootable USB Creator utility for creating the UEFI bootable USB. For manual formatting, do not use dd for Windows to dd the ISO to the USB drive either.
• In the below commands, X: is assumed to be the USB flash drive in Windows.
• Windows uses backward slash as path-separator, so the same is used in the below commands.
• All commands should be run in Windows command prompt as administrator.
• > denotes the Windows command prompt.

• Partition and format the USB drive using Rufus USB partitioner. Select partition scheme option as MBR for BIOS and UEFI and File system as FAT32. Uncheck 'Create a bootable disk using ISO image' and 'Create extended label and icon files' options.
• Change the Volume Label of the USB flash drive X: to match the LABEL mentioned in the archisolabel= part in <ISO>loaderentriesarchiso-x86_64.conf. This step is required for Official ISO (Archiso). This step can be also performed using Rufus, during the prior 'partition and format' step.
• Extract the ISO (similar to extracting ZIP archive) to the USB flash drive using 7-Zip.
• Download official Syslinux 6.xx binaries (zip file) from https://www.kernel.org/pub/linux/utils/boot/syslinux/ and extract it. The version of Syslinux should be the same version used in the ISO image.

• Run the following command (in Windows cmd prompt, as admin):

• Install Syslinux to the USB by running (use win64syslinux64.exe for x64 Windows):

Note:

• The above step installs Syslinux's ldlinux.sys to the VBR of the USB partition, sets the partition as 'active/boot' in the MBR partition table and writes the MBR boot code to the 1st 440-byte boot code region of the USB.
• The -d switch expects a path with forward slash path-separator like in *unix systems.

Other methods for BIOS systems

In GNU/Linux

Using a multiboot USB drive

This allows booting multiple ISOs from a single USB device, including the archiso. Updating an existing USB drive to a more recent ISO is simpler than for most other methods. See Multiboot USB drive.

Making a USB-ZIP drive

For some old BIOS systems, only booting from USB-ZIP drives is supported. This method allows you to still boot from a USB-HDD drive.

• Download syslinux and mtools from the official repositories.
• Find your usb drive with lsblk.
• Type mkdiskimage -4 /dev/sdx 0 64 32 (replace x with the letter of your drive). This will take a while.

From here continue with the manual formatting method. The partition will be /dev/sdx4 due to the way ZIP drives work.

Create Bootable Copy Of Mac Os 9.1 On Zip Drivers

Using UNetbootin

UNetbootin can be used on any Linux distribution or Windows to copy your iso to a USB device. However, Unetbootin overwrites syslinux.cfg, so it creates a USB device that does not boot properly. For this reason, Unetbootin is not recommended -- please use dd or one of the other methods discussed in this topic.

Edit syslinux.cfg:

In /dev/sdx1 you must replace x with the first free letter after the last letter in use on the system where you are installing Arch Linux (e.g. if you have two hard drives, use c.). You can make this change during the first phase of boot by pressing Tab when the menu is shown.

In Windows

The Flashnul way

flashnul is an utility to verify the functionality and maintenance of Flash-Memory (USB-Flash, IDE-Flash, SecureDigital, MMC, MemoryStick, SmartMedia, XD, CompactFlash etc).

From a command prompt, invoke flashnul with -p, and determine which device index is your USB drive, e.g.:

When you have determined which device is the correct one, you can write the image to your drive, by invoking flashnul with the device index, -L, and the path to your image, e.g:

As long as you are really sure you want to write the data, type yes, then wait a bit for it to write. If you get an access denied error, close any Explorer windows you have open.

If under Vista or Win7, you should open the console as administrator, or else flashnul will fail to open the stick as a block device and will only be able to write via the drive handle windows provides

Loading the installation medium from RAM

This article or section is a candidate for merging with Multiboot USB drive#Using Syslinux and memdisk.

This method uses Syslinux and a Ramdisk (MEMDISK) to load the entire Arch Linux ISO image into RAM. Since this will be running entirely from system memory, you will need to make sure the system you will be installing this on has an adequate amount. A minimum amount of RAM between 500 MB and 1 GB should suffice for a MEMDISK based, Arch Linux install.

For more information on Arch Linux system requirements as well as those for MEMDISK see the Installation guide and here. For reference, here is the preceding forum thread.

Preparing the USB flash drive

Begin by formatting the USB flash drive as FAT32. Then create the following folders on the newly formatted drive.

• Boot
  • Boot/ISOs
  • Boot/Settings

Copy the needed files to the USB flash drive

Next copy the ISO that you would like to boot to the Boot/ISOs folder. After that, extract from the following files from the latest release of syslinux from here and copy them into the following folders.

• ./win32/syslinux.exe to the Desktop or Downloads folder on your system.
• ./memdisk/memdisk to the Settings folder on your USB flash drive.

Create the configuration file

Create Bootable Copy Of Mac Os 9.1 On Zip Drive Thru

After copying the needed files, navigate to the USB flash drive, /boot/Settings and create a syslinux.cfg file.

For more information on Syslinux see the Arch Wiki article.

Final steps

Finally, create a *.bat file where syslinux.exe is located and run it ('Run as administrator' if you are on Vista or Windows 7):

Troubleshooting

• If you get the 'device did not show up after 30 seconds' error due to the /dev/disk/by-label/ARCH_YYYYMM not mounting, try renaming your USB medium to ARCH_YYYYMM (e.g. ARCH_201501).
• If you get errors, try using another USB device. There are case scenarios in which it solved all issues.

See also