illogic-al

but there is 2-d accel which you don't get with vesa.

during the RC phase i had problems installing from burned CD-RWs. As soon as I switch to CD-Rs the problems stopped. I guess the CD-RWs were old so they could not be burnt with. :~(

i have tightvnc and kde 3.1 installed and have no problems. care to post more of the error. where exactly does it happen. starting X from a console or once you're logged in to kde (i know you said doesn't start fully but that could just mean klipper doesn't start up or ksplash doesn't go away).

on mandrake linux you may not have seen this (i sure didn't) but from what i've heard (dolson's tutorial) you can make it do this manually. I've also been to the forums on the nvidia website and actual company employees have said that the source is available. I think they have compiled a driver for the stock mdk 9.1 (and redhat 9) kernel and installed that if you haven't modified (recompiled) your kernel. I you have i suspect that you'll see the option that dolson show's on his tutorial. I also installed the drivers while running X (which i don't think is recommended) so that might have something to do with it. To answer your question no, i don't think their installer is compiling a driver for your machine, but it can.

nah, you can still get 'em. there's a command line option to do it. I read the little blurb in their policy about that though. i think they meant they won't distibute it separately (same goes for rpms)

it won't crash... right away :) If you don't do anything processor intensive (compiling kde, installing UT 2003) you should be just fine :)

quanta and lisa do not need to be installed

nope. not i.

libpng.so.3 comes with 9.1. Having said that I think the rest of your files may be old and not one the distro anymore

Mdk 9.1 now handles ntfs resizing :)

Hmm.. there is an updated kernel from the cooker, try installing that.. remember.. this is still beta.. Everytime mandrake does a kernel, they have to repatch supermount in it. IIRC mandrake said that kernel 2.4.x doesn't like supermount that much.. it takes some kind of kludge to make it work properly. Anyway, kdeartwork rpm is in the disks I think, just not installed by default (or even a choice in the initial installation). After finishing installation, check rpmdrake, I think you find kdeartwork in there. [dmage@dragonmage dmage]$ rpm -qa |grep kdeartwork kdeartwork-3.1-1mdk i didn't find it on the disks and a lot of people on the cooker mailing list were complaining because it was left out so I doubt that was from the disks, you got it from cooker without knowing maybe. And yes some sort of kdeartwork package will be available for the final.

yup. there's definitely problems with utf from what i've seen. maybe these've been fixed by now.

The missing packages are probably due to something being wrong with your cds. Didn't use cd-rw by chance did you? Bugs are being fixed. If you want more to be fixed report bugs on cooker. Also if you update packages from a cooker source most of you bugs will probably be fixed.

You're probably using alsa. It doesn't create /dev/mixer or /dev/dsp files unless you use OSS emulation. I'd suggest you use the draksound program that mandrake provides and reconfigure you card. Which card do you have btw?

k0nqueror for kde 3.1. There's also a new plugin which they say works with konqueror (i guess 3.0.x version).

try this and tell us if it works: amixer set Master 100 unmute amixer set PCM 100 unmute aplay /usr/kde/3/share/sounds/pop.wav you have to install alsa-utils before btw. And one more thing, you didn't happen to turn off any of the sound services by accident (when installing maybe) did you?

ahh yes, nimbus sans. brings back fond memories. I've converted from nimbus to arial since I got windows fonts from textar's site and on kde3.1 it looks righteouser. If only I could get the login screen to antialias ... oh well I only see it once every couple of days anyway.

I was mistaken and my cdrom is using DMA. Still having probs with the dvd playback. Tell us if you fixed it why dontcha.

Am I the only one who finds it a little weird that konqueror/nautilus was not mentioned here. rox-filer is good though. and fast :D

you have to make it the master drive. On your hard drive there should be switches (kinda sorta) on the back of it that tells the computer to designate it as a master or slave drive. Some hard drives have the configuration clearly marked. Others you'll have to check the instructions that came with the box. It's also possible to do this using the cable on older computers but I think this is rare (only seen it on my old compaq) and you still have to set the drive as master or it won't work.

It's true, it's true. Supermount is go. Finally

What's wrong with qtella is that it doesn't connect at all even after hours of trying. I was thinking that it might be do to the school's firewall (if they have one) but gtk-gnutella was working. just really slow a la bvc

It is a pretty bright idea. You're menu wouldn't be updated with new packages otherwise unless you add them by hand, which is a pain, then mandrakes menus wouldn't be better than the default kde ones.

Thinks it's too hard to set up a samba share. Well then it just became easier. We'll mainly be using the graphical goodies provided by Mandrake. 1. First open up the mandrake control center. You should now see an icon on the very bottom which says Server Configuration. If it's missing, like in the one shown here, you'll need to install it. 2. So open up rpmdrake from the control center since you're already there. 3. Once you've clicked on the Install Software and rpmdrake shows up you'll need to install these a few things. If they don't show up when you search for them that probably means they're installed already samba-server samba-client (for LinNeighbourhood) samba-common drakwizard samba-swat (optional) 3. You might want to consider using Mandrake Upadte at this point and updating your samba packages. While you're at it just update anything else that needs updating. 4. To update choose a mirror and select ok If your mirror doesn't work you can try another or give up (like I did). I seriously recommend updating because in addition to getting security updates you can also get bugfix releases and general updates which help things to run smoother. At the very least get the security updates (for packages that you use). 5. Close rpmdrake and then reopen it. You should now see an icon on the very bottom which says Server Configuration. There endeeth the screenshots. 6. Click on the Samba icon choose Next and choose the options you want (if any) and then move on. 7. Choose a name for your workgroup, move on. The server banner which comes next will bw a sort of description for you workgroup so you can put a description like "Only company file server immune to outlook viruses" or "music mp3s and other sh*t here" or something along those lines. 8. Hit next Mandrake will tell show you what it's doing you have the choice to go back and change thigs if you feel so inclined. 9. Hit next Mandrake congratulates you on your point and click skills. Hit Finish and then it's all over. Quite boring, no? 10. Well its not over yet. Now the FUN begins. Or at the very least it gets interesting. If you have a firewall running you have to reconfigure it so that it allows samba to work. Firestarter has a nice point click interface with a wizard that allows you to select servers that you want to allow. I was using it for the longest while too but I couldn't get it to work with LinNeighbourhood or Komba2. It wouldn't allow samba net access through the wizard so I ditched it and went with the KDE compatible and option freindly Guarddog. All these apps are in the contrib section of the Mandrake. Instructions on adding them to rpmdrake as sources can be found here. 11. Assuming you've taken care of the firewall we move on to adding shares to the samba config file. That's where the samba-swat program comes in. It's in the menu under Configuration --> Networking --> Samba Configuaration. You need to put in your root username and password initially to log on. 12. Remember whatever you do don't share you're shares in read write mode with everybody. Bad things can happen (like what's about to happen to this guy who's shared his whole windows C drive). To be continued....[/i]

The whole purpose of these is to pick up on these bugs and for you the user to report them. It's meant for testing not use, so if you gonna use it at least file a bugzilla report telling of your problem or join the cooker mailing list.