||07-29-2013 05:21 AM
Originally Posted by TobiSGD
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.
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.