SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
From the installation CD/DVD... slackware-13.0/usb-and-pxe-installers/README_USB.TXT
Quote:
Transfering the usbboot.img file to a USB device
------------------------------------------------
In order to create a bootable USB stick with the Slackware installer on it,
copy the 'usbboot.img' file to a USB stick as follows:
(1) In a Linux terminal if you're in X, or just from the console, change
directory to where the file 'usbboot.img' is located - you may have to
mount your Slackware CDROM or DVD first.
(2) Insert a USB stick that is going to become your Slackware installer.
Note that all data the stick contains will be erased in the next steps!
You need to find out the device name for this USB stick. Sometimes it
helps to run the command 'rescan-scsi-bus' if the USB stick is not
being detected right away.
On systems without SCSI or SATA disks, the USB stick will usually be
assigned '/dev/sda' as the device name. If '/dev/sda' already is your
SCSI or SATA hard drive, then '/dev/sdb' would become the device name
for the USB stick. Be very convinced that you know which device name
represents your stick before you advance to the next step!
(3) Transfer the image file to the USB stick using the 'dd' program. In the
example command line below, I am assuming that the USB stick is known as
'/dev/sdx'.
dd if=usbboot.img of=/dev/sdx bs=512
Be careful about the device name for your USB stick! The above 'dd'
command will wipe out any existing data on the device, so you had better
be sure that it is not the SATA hard disk you're targeting!
If you're trying to create a Slackware installer on the flash drive then you're taken care of. If you're trying to actually install Slackware to a flash drive then you just partition and specify that drive during the install process (wherever you run the installer from).
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
Nah, I'm trying to make a "bootstick" (not an installer). The Slackware installer asks if you want to make a USB bootstick (so you can boot the thing if the MBR gets screwed up somehow or other). I've installed Win7 64-bit then reinstalled Slackware 64-bit, ran Lilo and I can boot Slackware just fine but Win7 fails with a message about the BOOTMGR missing -- the fix for that seems to be to use the Win7 install disk to repair the MBR and I'm afraid that when I do that I won't be able to get Slackware booted again without a lot of grief. So, what I need, is a USB bootstick that will boot me into my existing Slackware partition if Win7 screws thing up during the "fix."
I've installed Win7 64-bit then reinstalled Slackware 64-bit, ran Lilo and I can boot Slackware just fine but Win7 fails with a message about the BOOTMGR missing -- the fix for that seems to be to use the Win7 install disk to repair the MBR
As far as I understand, the missing BOOTMGR error message is reported after the boot record is done, so the problem must be different.
It is a bit strange that you do not emphasize the fact that BOOTMGR is in place. Do you see the hidden Boot folder in the Windows 7 boot partition?
Just in case there is no Boot, did you allow Windows 7 to use a whole disk on installation?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
