Your commands for the QEMU monitor look OK to me. You do not need to (u)mount any physical CDROM outside of QEMU (i.e. on the host) because the Slackware installer running inside QEMU will mount and umount the CD's.
I never tried installing Slackware in QEMU with two physical CDROM's AFAIR, but it should be entirely possible. You will have to wait until Slackware asks you to remove CD1 and replace it before you try and run the eject/change commands in QEMU's monitor though.
Steps:
- Slackware asks for the second CD
- go to qemu monitor
- run "eject -f cdrom"
- change the physical CD media in the computer's drive
- in the qemu monitor run "change cdrom /dev/hdd"
- continue with the Slackware install, Slackware will "find" the second CDROM now.

Eric

You need to hit CTRL+ALT+2 in your qemu session. That will bring up the qemu console, then you can eject & change cd-roms. Edit: OK, Eric beat me to it!
Regards,
Bill

Ok ty, I'm trying it now.

I hope I don't have a bad dvd rom drive, I swapped out a new ribbon/cable we'll see. I wound up getting error's today in windows too, as I'm dual boot, and got an error today on that too just trying to read data off a cd/rw.

However, I have a slightly smaller issue now, LOL as I always do right. Anyway, I have on that same ribbon/cable as my dvd rom drive a hard drive. It had my qemu image for my slackware image I made before. Before I changed cables, I moved all my data over to a fat32 partition, as it had room. After I changed the cable, I moved the qemu image back to the big hard drive that is on the same ribbon as the DVD and that is linux ext3. Now I cant use that slackware qemu image. I checked the ownership of it, and I'm allowed full on it. However, even the icon is different for it now. Before, it had an icon that looked like a "kwrite" icon in my KDE konqueror's file manager. And it used to be shown as file type "text document" and now it shows up as "unknown". Is there some kind of file information parameters that got lost on this file when I moved it onto a fat32 drive and then back? Is there anyway I can key them in and change it?

Moving it from one linux partition to another before seemed ok. But something went awry here.

If not no big deal, as I am re-loading and making a new image now anyway, but this might be good to know for future use, etc.

just an update:

eric your scripts worked flawlessly for new versions of the kqemu

i had to remake my iso of my slackware cd's, i used paranoia 3 on k3b to make my iso

maybe i had bad iso file, or a flaw on my cd. they're riddled with coffee stains and scratches.

so I did get an install off of cd's finally

the new kqemu does seem faster to me

I havent figured out how to mount an ext3 yet as read write for a /dev/hdb but i have some reading to do

I put in the testing kernel of slackware and I get networking now in the slackware guest so that
helps my issue of moving packages around once I make them for the time being.

I wonder if you could : ddcopy your current running slackware partition into a qemu.img file, then
mount it as a file system as eric points out on the wiki..then run qemu and do stuff to your guest
slackware OS that is identical to your current running slakcware to test new packages, kernels and the like.

maybe overkill, but I think i might try and play with it and see.

The QEMU image file resembles a full hard disk, i.e. including a MBR and a partition scheme. It would be impossible I think to copy your current Slackware partition into a QEMU image using 'dd'.
However, what about loop-mounting an existing QEMU image file (after you used QEMU and the Slackware install CD to partition it) as I describe in this Wiki section and then "cp -a" everything from your Slackware host partition into the mounted QEMU imagefile's partition?

NOTE: you must not be running QEMU when you mount that imagefile on the host!

Eric

thanks eric, I wasn't sure how to "skin the cat" as they say.

I'm going to give that a shot.

I'm really liking this QEMU by the way, this is truly an incredible piece of software.

Wow..

Dr. Who would love this: Recursive reality. Running an installed Slackware inside a running Slackware install....Where does the madness end????

lol. Love it. Gonna try myself.

it's incredible, the only thing that is a little akward but I'm sure will be enhanced after time:

-mounting iso's as cdrom's sometimes, need to be done twice. tho maybe it's my pc.
-i'm using a ps/2 mouse at the moment, and sometimes the cursor is a little, and I mean milliseconds, delayed on screen.
-the qcow rocks.

the goals that eric listed of this app on his wiki are truly achieved.

the program has not crashed once on my pc.

compiling a kernel only took about 5 minutes more, but allowed me to stay in my running slack and not reboot, so the time
is definitely worth it.

I don't know this is a really good program, how cool would that be to see this ship with a distro like slakware.

As I said, make your own live cd or dvd. As much stuff as you want, a dvd maybe the way to go.

In the meantime you can just keep grabbing my packages :-)

Cheers, Eric

qcow just owns!!

it's fixed me everytime yast breaks something ROFL.

SuSe should give up on zen and build in qcow as they refuse to fix yast LOL...just kidding

I'm going to be a broken record here, this qemu is incredible!!!!!!!!!!!!!!!!!

Your packages/scripts, this qemu...incredible.

Why this is not on the nightly news ?

lol, let me stop while I'm ahead, and not let my conspiracy theories run wild.

thanks again.

I couldn't possibly agree more. For me, QEMU has been the missing link for learning how to build packages. I'm still doing really basic things, but now I can work thru SlackBuild scripts without worrying about messing up my system. And I can restore to a clean install in seconds.

Dude, we sound like a commercial. "It's both a floor wax AND a dessert topping!"

Thanks Alien Bob for your most excellent tutorial. I was able to sucessfully install Win2k on my MEPIS laptop and I am attempting WinXP on my Slack Desktop. Have any of you tried Vista Beta 2 using this method?

believe it or not, I read an article today on zdnet i believe it was, that said vista for virtual pc's will need it's own special license.

that is if you load it on a pc, then you can't dual boot into linux let's say and run it virutally there too. and it has to be pro version or whatever it is they call it.

hey Eric, btw, 2 packages that you do not have and linuxpackages do not have that I find really fast to package for slackware 10.2 is 'ktorrent' and 'komparator' just an fyi i really like them. they fit really well into the kde theme.