Why does the Slackware USB flash drive boot installer creation process involve making a damn Windows partition to put the installer on?!

I made a new USB flash drive installer, and when the BIOS of the system I tried it on did not detect it but started starting Windows, I took the flash drive out, but Windows must have tried to access the flash drive's Windows partition--then it was ruined!

Slackware is the greatest system for development purposes (even has more than any default BSD install, AFAIK, though perhaps BSD is still more stable) and that is great, but one would not expect such a system to use a Windows partition on its installer, and I have a serious problem with that!

The Slackware USB flash drive creator makes a Windows partition because BIOSes can't boot from file systems such as e.g. ext4.

If your BIOS didn't boot from the flash drive, then either:
1) you've set the booting process wrong in the BIOS;
2) the flash drive didn't prepare correctly and is not bootable;
3) the BIOS doesn't have an option to boot from USB flash drives (usually in older computers).

What do you mean it's ruined? The USB stick is ruined? How?

You could tell us how you prepared your Slackware install flash drive.

1 members found this post helpful.

It's trivial to use another filesystem type that syslinux supports for the usb drive installer. I use ext2, for instance. This is no critical issue.

Are you sure you have your usb drive first in the boot device list, have syslinux installed on it, and the boot partition active?

BIOSes can't boot from any filesystem (UEFI firmware can read FAT partitions, BIOSes don't), they rely on finding executable code in the MBR of the medium you want to boot from.

To the original question, I never had to create a Windows filesystem when using the USB installer, all I ever do is writing the usbboot.img to the USB device using cat or dd. I also can't see any instructions to create a Windows partition in the USB README file?
Please elaborate where you did get those instructions and what exactly have you done, including why you think that the Windows installation has ruined your USB device.

1 members found this post helpful.

I recall when doing an fdisk on a USB flash drive set up by the instructions on Slackwiki's 'Install Slackware Using A USB Flash Drive', that its partition was listed as a hidden Windows type (those instructions use dd, so erase everything from the drive by overwriting it all with its own partition table and data). Ok, so the instructions are probably unofficial, but I am wondering not only what was the writer thinking, but why the software they used that is a part of Slackware made this ISO file that when dd was used made a Windows partition on the USB flash drive. I did not install Windows--I was trying to install Slackware on a system that currently has Windows on it, but since the Slackware installer process for a USB flash drive makes a Windows partition on the flash drive, Windows started reading it, without me remembering or noticing that, then I took it out, and can no longer detect the drive when it is plugged into any computer. Windows of course does not read from any type of ext partition, and it would have been ok to remove the drive if it had used an ext partition... but apparently it does not--otherwise it would not be ruined now (i.e., Windows 'mounted' it in the first few seconds of its boot process, and probably did something more that it should not have been doing, i.e. not just reading from it).

To answer another question asked above: the system I was trying this on does not even boot from USB--I selected something I thought might have been the USB flash drive after I plugged it in before turning on the computer on (since some BIOSes detect stuff plugged in, or have options that were updated but not documented) but it was the hard drive. This was not a question about the simple process of installing anything, which I have decades of experience with.

The flash drive was prepared correctly, because I have done this before, and the commands finished fine.

Coreboot is an example of a BIOS that can be compiled to boot from ext, if Coreboot even does not normally have an option or module to do that by default, but AFAIK it is as TobiSGD says--BIOS looks at a MBR to boot: if you have ever done fdisk on a new USB flash drive, or partitioned one like a new one, they have a little space at the beginning before the filesystem starts. I do not recall how it was with floppy discs; they might have worked similarly, though I do not recall if I ever did fdisk on one.

Try using the usbimg2disk script:
http://slackware.mirrors.tds.net/pub...xe-installers/

1 members found this post helpful.

I looked in that script, and it makes a 32-bit FAT partition, just like the instructions I used. I think one can make whatever partition type one wants on a USB flash drive--I recall doing so recently (and then using the drive)--so apparently my criticism may be correct!

I think that the labels from fdisk regarding the filesystems used are simply wrong. While fdisk reports this on my USB device with the installer copied to itI get this from parted(which is by the way impossible, since FAT16 does not support partitions of that size) and lsblk does not report any partition on that device, which relates to the dmesg output, that also does not see any partitionBut in any way, even if Windows altered something on that partition that should not alter in any way the partition table, so that the device can not be seen anymore may be a coincidence. What is the output of dmesg regarding this device?

Ok; and how did you make that installer? It looks like you did it differently than me, but the fact is, the script mentioned above makes a FAT partition. The fdisk output did not necessarily look wrong, but the parted output did. I would not trust fdisk for anything above 2 TB, though one needs something like parted for that, and if it is giving wrong data, that is unfortunate.

After I unplugged the USB flash drive from the Windows machine and into my Slackware one, there was some bizarre dmesg I am not sure I had ever seen before. I must have rebooted to try a pxe installation, and now there is simply no dmesg output about the USB flash drive, and no lights flashing on it. If one takes out such a drive when it is being written to--which apparently Windows must have done for some idiotic reason--that is what one is often left with (or soon after, after being only partly readable): a drive damaged to the extent it is not even detected.

I did it as the README stated, using dd to write the image to the USB device.

I extensively work with USB devices on Windows machines and this never happened to me. Therefore I mentioned that this may be just coincidence and the device was dying anyways.

1 members found this post helpful.

It was a completely new Lexar (Micron) drive. The problem with pulling out USB flash drives when they are not finished being written to (even if their lights are not flashing) has nothing to do with whether the partition table is changed--it has to do with hardware. You get results similar to if you had pulled a floppy disc out when it was being written to, and like cancelling an optical disc writing session in the middle of it.

According to the rough notes I made at the time:
I had the Slackware tree i ~/temp, then ran (as root):
/dev/sdb was a 8GB SanDisk Blade. Installation on an Asus eeepc 1001HA was successful.

Apparently not, as I have already made clear in my previous post.

Read the official Slackware script BrianL mentioned, and take a look at the partitions TobiSDG mentioned were created on his USB flash drive by following the README.

The README only tells you something can be done in some way. It does not say other ways are forbidden.