LinuxQuestions.org - Creating a bootable slackware ISO in Windows XP!?!?!

- Linux - Newbie (http://www.linuxquestions.org/questions/linux-newbie-8/)

- - Creating a bootable slackware ISO in Windows XP!?!?! (http://www.linuxquestions.org/questions/linux-newbie-8/creating-a-bootable-slackware-iso-in-windows-xp-203206/)

Creating a bootable slackware ISO in Windows XP!?!?!

:newbie:

Yes, I am.

However I've got a problem. I got the two CDs of Slackware 10 off the official torrent, however they are winRAR archives, and not ISOs.

In Windows Xp, how can I create a pair of bootable ISOs with slackware's image on them?

This is covered for Linux in the CD1/isolinux/readme.txt directory, but not for us using Bill Gate's' OS...

Keep in mind that I DO know how to burn stuff to CD-ROMs...I'm not THAT bad :p

Help :confused:

Welcome to LQ!

They must be iso images. Even though they have a WinRar icon,
what are the file extensions? If .iso then they're okay.

Windoze eXperiment will not make a bootable CD with an
iso image. You must use something like Nero. There's a trial version
if you'll search for it.

Edit: Maybe torrents have to be unzipped first?

Quote:

Originally posted by Chinaman
Welcome to LQ!

They must be iso images. Even though they have a WinRar icon,
what are the file extensions? If .iso then they're okay.

Windoze eXperiment will not make a bootable CD with an
iso image. You must use something like Nero. There's a trial version
if you'll search for it.

Edit: Maybe torrents have to be unzipped first?

Thanks for the welcome!

They are indeed .iso's, I was confused by not only the WinRAR icon but also the description, "WinRAR Archive" under "Type of file."

And yes, they are torrents, but I don't think they should be unzipped? If I do that it will lose the ISO format and just get a bunch of folders and files, so I should leave it like it is...right?

Anywany...what I basically should is this - just burn the ISO's onto two CDs with Nero 6 demo, then select to boot from the first CD from the BIOS boot menu? Do I need to configure Nero in any particular way, or do I just burn them like I would any other file and just use the Nero Express wizard?

Thanks for putting up with my insipid questions, I bet you normally deal with problems a LOT more difficult than mine :p I'm sort of anxious because this is the first OS besides Windows I'm using. I've already used Partition Magic 8 to free up some partition space for Slackware, I think 30 gigs ought to be enough, and I am ready to go once these questions are answered :D :cool:

Quote:

Originally posted by black hole sun
Thanks for the welcome!

They are indeed .iso's, I was confused by not only the WinRAR icon but also the description, "WinRAR Archive" under "Type of file."

And yes, they are torrents, but I don't think they should be unzipped? If I do that it will lose the ISO format and just get a bunch of folders and files, so I should leave it like it is...right?

Good deal. You are correct, do not unzip them. I've never used BitTorrent because I wasn't willing
to leave any ports open on my computer to people I don't know.

Quote:

Originally posted by black hole sun
Anywany...what I basically should is this - just burn the ISO's onto two CDs with Nero 6 demo, then select to boot from the first CD from the BIOS boot menu? Do I need to configure Nero in any particular way, or do I just burn them like I would any other file and just use the Nero Express wizard?

Correct again! Choose "Burn Image To Disc" and then when you get an "Open" dialog box you will
have to change "All Nero Compilation and Images" to "Image Files."

Quote:

Originally posted by black hole sun
Thanks for putting up with my insipid questions, I bet you normally deal with problems a LOT more difficult than mine :p I'm sort of anxious because this is the first OS besides Windows I'm using. I've already used Partition Magic 8 to free up some partition space for Slackware, I think 30 gigs ought to be enough, and I am ready to go once these questions are answered :D :cool:

Didn't think they were insipid at all. But if you want more reference, you can look at information
on LinuxISO especially for how to burn iso images.

My desire is to help you along with Linux, and maybe you'll dump Windoze one day.

After you burn the Slack CD's, print the file Slackware-HOWTO off of CD1. Read through it so
that you won't have as many surprises - then keep it right there with you while you install.

Need more help? This is a good place to come!

You've been a big help so far, thanks!

Now I've just finished installing slackware 10 off the CD-Rs...but now how do I actually get into Linux? I've got it set up so Windows is my boot OS; how can I manually access Linux, or do I need to set it as the boot OS instead of Windows (which I'd prefer not to, other people use this machine and they only use Windows)? :confused:

Quote:

Originally posted by black hole sun
You've been a big help so far, thanks!

Now I've just finished installing slackware 10 off the CD-Rs...but now how do I actually get into Linux? I've got it set up so Windows is my boot OS; how can I manually access Linux, or do I need to set it as the boot OS instead of Windows (which I'd prefer not to, other people use this machine and they only use Windows)? :confused:

Hey kid, did you print and read that Slackware-HOWTO? You should have setup a dual-boot
with Windoze as the first OS when you installed. You get out that HOWTO and start reading,
but in the meantime, did you create a bootable floppy? If you did, boot with it, and then when
you get to a login prompt do so. Then type as su (superuser, root)
# pico /etc/lilo.conf
and post it in here. You'll have to write it down or something...maybe you got a digital camera
and you can take a shot so it's easier to type it into Windoze. I'll post the one on this laptop
and show you which lines we need to see, okay?

Code:

bash-2.05b$ cat /etc/lilo.conf

# LILO configuration file

# generated by 'liloconfig'

#

# Start LILO global section

boot = /dev/hda  <-- post this

#compact        # faster, but won't work on all systems.

prompt

timeout = 50  <-- post this

# VESA framebuffer console @ 1024x768x256

vga = 773  <-- post this

# Normal VGA console

# vga = normal

# VESA framebuffer console @ 1024x768x64k

# vga=791

# VESA framebuffer console @ 1024x768x32k

# vga=790

# VESA framebuffer console @ 1024x768x256

# vga=773

# VESA framebuffer console @ 800x600x64k

# vga=788

# VESA framebuffer console @ 800x600x32k

# vga=787

# VESA framebuffer console @ 800x600x256

# vga=771

# VESA framebuffer console @ 640x480x64k

# vga=785

# VESA framebuffer console @ 640x480x32k

# vga=784

# VESA framebuffer console @ 640x480x256

# vga=769

# ramdisk = 0     # paranoia setting

# End LILO global section

# Linux bootable partition config begins

image = /boot/vmlinuz  <-- post this

  root = /dev/hda6  <-- post this

  label = Slack-10.0  <-- post this

  read-only # Non-UMSDOS filesystems should be mounted read-only for checking

# Linux bootable partition config ends

# Windows bootable partition config begins

other = /dev/hda1  <-- post this

  label = Windoze  <-- post this

  table = /dev/hda  <-- post this

# Windows bootable partition config ends

This lappy is going to Beijing this week, but it's setup to boot Slack first and
then Windoze eXperiment. That shows you what I want to see, and the rest
of it you don't need to post. Hey, put [_code_] without the underscores in
front of your output and [_/code_] without the underscores after your output
so that it will be easy to read...okay?

You'll want the machine to boot Windoze first, so we'll reverse your order.

Also post the output from issuing this command:
# fdisk -l
and this one
# df -h
and tell me how your Windoze box is partitioned. Like how many partitions,
and what file system, etc. If you can get into Slack I'll see that from those
other two posts.

I might not get back with you for a little bit. I ran a program to recover some
lost data and hosed my Slack-10.0 system. Depends upon how quick I either
figure it out or get some help.

I'll get to reading that HOW-TO, but I think it'll be talking over my head. Anyway, here's my info you wanted - I booted from the floppy boot disk the installation recommended I make.

Code:

from #pico /etc/lilo.conf



boot = /dev/hda3

timeout = 1200

vga = 790



...



table = /dev/hda

...



image = /boot/vmlinuz



  root = /dev/hda3

  label = Linux

Continuing....

Code:

 from fdisk -l 



Disk /dev/hda: 80.0GB such-and-such Bytes 



255 heads, 63 sectors/track, 9729 cylinders



                Boot         |   Start   |     End   |    blocks   |      id       |        system



/dev/hda                         1           5           ~40MB           de           Dell Utility partition (this came with my computer, haven't bothered to remove it)



/dev/hda2        *                6          6413         ~53GB          7             HPFS/NTFS (Windows XP)



/dev/hda3                        6414         9729        ~27GB          83           Linux

One more to go...

Code:

 df -h



Filesystem                    Size          |          Used         |           Avail          |             Use         |          Mount on



/dev/hda3                   26GB                     2.5GB                      23GB                       10%                     /

Ok, I got into Linux! Handy file, that HOW-TO :D Turns out I had to write the LILO thingy into the Master Boot Record (which thankfully didn't corrupt anything on my Windows partition)

But now, how do I get into the fancy-looking KDE graphics shell (correct word?), which I selected? Atm it's just a command prompt.

You see, reading's not all bad! Before you get too deep into Linux,
you really should read those first two links in my sig, plus the
Rute User's Tutorial and Exposition

You are not required to read this stuff, but if you don't you will continue
to suffer from lack of knowledge. If you'll just stop and read those now,
you'll get some Linux knowledge a lot faster, and you won't mess up
your system, get frustrated, and run back to Micro$loth Windoze.

To get another window manager you will issue, from that prompt
$ xwmconfig
and choose one. Then when you return to the prompt, issue
$ startx
which interestingly enough, "starts the X server."

Notice that I have a $ in front of those commands and not a # because
$ is a normal user's prompt and # is superuser's (root) prompt. Do not
run your system as superuser or you will live to regret it!

Thanks a bunch! I will be reading that.

Just one more question from me (for now ;) ), though - how can I add a resolution of 1280x1024 (native to my monitor)? The KDE control panel only goes up to 1024x768.

I've googled this, and have found that I need to edit one 'XF86Config' file - however I have no such file in etc/x11!

:confused:

In Slack-10.0 we've gone from XFree86 to X.Org so you'll need to edit
/etc/X11/xorg.conf
in this section

Code:

# **********************************************************************

# Screen sections

# **********************************************************************



# Any number of screen sections may be present.  Each describes

# the configuration of a single screen.  A single specific screen section

# may be specified from the X server command line with the "-screen"

# option.

Section "Screen"

    Identifier  "Screen 1"

    Device      "VESA Framebuffer"

    Monitor     "My Monitor"



# If your card can handle it, a higher default color depth (like 24 or 32)

# is highly recommended.



#   DefaultDepth 8

#   DefaultDepth 16

   DefaultDepth 24  <-- this is your monitor depth

#   DefaultDepth 32



# "1024x768" is also a conservative usable default resolution.  If you

# have a better monitor, feel free to try resolutions such as

# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your

# card/monitor can produce)



    Subsection "Display"

        Depth       8

        Modes "1024x768" "800x600" "640x480"

    EndSubsection

    Subsection "Display"

        Depth       16

        Modes "1024x768" "800x600" "640x480"

    EndSubsection

    Subsection "Display"  <-- so it uses this display

        Depth       24

        Modes "1024x768" "800x600" "640x480"  <-- so you should add "1280x1024" in front of this

    EndSubsection

    Subsection "Display"

        Depth       32

        Modes "1024x768" "800x600" "640x480"

    EndSubsection



EndSection