As part of my investigations with HRev51877 for data recovery and transfer, I followed the first method described in ( https://www.haiku-os.org/guides/installing/making_haiku_usb_stick/ ), that of using Etcher.
Etcher is a nice and easy-to-use tool - especially for one who uses Windows most of the time.
I elected to use the portable version which is a ~50 MiB download. While the portable version does not temper with the Registry, it first create a temporary expanded version of it-self weighting at close to 260 MiB; something which takes a few minutes to complete. Then one can flash the anyboot.iso image to a USB Flash Drive.
The process is very similar to that for creating a Recovery image in the ChromeOS world. However, the Recovery app is a tiny download, around 1.5 MB, expends to 6.2 MB on installation, and offers the possibility to “erase” the SD card or USB Drive so that it can be re-used for other purposes.
As the image is only 600 MiB, this leaves the rest of the flash drive un-allocated; the same as if “dd” had been used. Using DriveSetup, the un-allocated space can be defined as a BFS, FAT32 (<32Gib) or NTFS (>32Gib), or any one of a number of Linux flavored volume. I used a boringly descriptive name “BFS_Transit” as the intended use was for data recovery and transfer. Another time, I’ll pick FAT32 (or NTFS) and assess if Windows can “see” this volume on inserting the drive into a port.
One little issue is that the name of the bootable partition is simply “Haiku”. It does not appear to be possible to rename it with DriveSetup. Mounting the volume in Haiku causes an USB-Drive Icon with the name Haiku to overly the Haiku boot volume one. While both volumes are distinct within Haiku, this behavior brings confusion to an user.
Suggestion: Could the nightly images be created with a distinctive name such as Haiku_HRevnnnnn with nnnnn being the HRev number?