chris z

the path should be /dev/cdrom(0,1,2........etc) with the number depending on how many cdrom devices you have & where it is installed (as master or slave device). you can check in /dev/cdroms & see what yours is listed as. Chris

well, the work around would be just to make the path to your cdrw player, not your dvd player. i'm not entirely sure, but i don't think KSCD can play cd's from a dvd player. try changing the path. can't be that much a big deal to listen to cd's in your cdrw player, can it? Chris

install all of them & any dependencies they might require. Chris

also, when you say you checked the volume settings in your mixer, which mixer did you check? kmix or aumix? if it was kmix, check the settings in aumix because they override kmix settings. kicker->mutlimedia->sound->aumix. Chris

what cd player are you using? KSCD in KDE? if so, or for any cd player for that matter, check to make sure you have the proper path to your cd player in the options. in KSCD, click on the button with the hammer & screwdriver on it & look where it says cd-rom device & make sure it points to your cd player, not your dvd player, "apply" "ok", quit KSCD & restart it. Chris

family portrait, edited in gimp to fit the required size dimensions here....... <------- pa spauldiing, ma firefly, brother otis, sister baby (adopted), brother tiny i took the picture, so that's why i'm not in it. Chris

not to sound like a smarta**, but it could it be something as simple as your ISP is temporarily down? it happens from time to time. i mean, if your internet was working earlier, you didn't do anything that could have screwed up your settings, & now it's not working at the moment, i'd wait a bit & try it later before playing around with interent settings. or, call your ISP & ask them if there's any known toubles in your area. Chris

instead of using DrakConnect or having it start during boot, once booted you can issue the following commands in terminal as root........ to start connection: adsl-start to check connection status: adsl-status to stop: adsl-stop Chris

hi again jimdunn....... well, to answer your questions first........ yes, when i issued the commands you listed (cAp SensiTIve) it made my kicker turn into a pencil thin line, but not completely invisible. i did get some warnings in terminal after following your instructions about minimum size can't be negative (it wasn't, it was 0,0 like you posted) & something about trouble resizing the clock. i don't have the errors verbatim because since then i've found another solution which is prolly as good as it's gonna get it. sort of a "dirty hack", but it accompolishes the effect i was looking for. what i did was the following........... (thanks to LinuxLearner for pointing me down the right path & Hook in #kde for showing me how to do this.....) to make kicker become invisible without using a script or set of commands, but still run (thereby giving full functionality to the KlearDock K Menu), i did the following..... start Kicker, right click on it, choose "panel menu"->"configure panel"->"hiding". select "hide automatically", select "immediately" where it says "after the cursor leaves the panel", & uncheck the "show panel hide buttons" (if you have them checked). then, in the "arrangement" tab, for it to work with KlearDock already docked at the bottom of my screen, i needed to set the hiding position to top center. (though i think any place will work except for the bottom points of the screen) click "apply" "ok" & walla........Kicker disappears completely. to make it reappear, simply hover your cursor over where Kicker was located. as long as your cursor is on the Kicker it will stay visible. move it, & Kicker goes outta sight, outta mind. so, now that i've got this worked out, i can recommend the app KlearDock wholeheartedly if you want to have a really nice, fully functional, transparent Kicker in KDE! thanks again for your help jimdunn! Chris

jimdunn....... almost.....but not quite. that set of commands doesn't give me the effect i'm hoping for. it reduces my kicker to a very thin still visible line. almost invisible, but not quite totally. thanks for the info, though. any other ideas? Chris

hi guys & gals..... i'm stumped with something. maybe somebody can unstump me........ here's the story..... i installed a KDE addon app called Kleardock. what it is basically, is a KDE Kicker that you can make transparent. (sorta along the lines of Slicker, or some Karamba themes out there). it installed fine & i really like it, except for one annoying problem. it apparently needs Kicker to be running in order for the K "start applications" menu to work. if i kill Kicker or stop Kicker from loading with KDE, i can still use Kleardock but the K "start applications" menu doesn't work. (IE: i click on it but absolutely nothing happens.......no app menus, no nuthin') i've searched high & low for a solution, but can't find one. i've tried editing the panel.desktop config file in /usr/share/autostart several different ways (commenting out the Exec=kicker line, replacing kicker with kleardock, commenting out the dcop & service start lines) to no avail. the executable path under properties to the K shortcut in Kleardock reads as such.... dcop kicker kicker popupKMenu 0 i've tried editing that in every way imaginable..........no go. my 2 lines of thought to get this working are this......... 1. find the correct exectuable path to the K "start applications" menu (if there is one) 2. find a way to make Kicker load or run, but having it running in the background where it's not visible. anybody have any ideas on how to do either of the above? or, maybe a totally different solution? currently i'm running Kicker along with Kleardock, but i have Kicker hidden to the left by using the hide arrow. i really don't like the look of this half assed solution, but it's all i can come up with for now. i'm all ears (or eyes, i suppose) :P Chris

the Mozplugger solution i posted above should work. if it doesn't, then use spiedra's solution in conjunction with MozPlugger. i just helped somebody out in MUSB a few days ago with the same problem you're having & that's what did the trick. Chris

instead of using CLI, just for shits & giggles try adding the contrib source using GUI. open MCC (Mandrake Control Center)->software->sources manager->add. when the "add" dialogue box opens up, choose the "ftp" option button at the top for your source type. copy the ftp source location address from your browser into the location address box in the add dialogue box. for example, the ftp contrib source from the forum here would be....... ftp://mandrake-forum.org/pub/Mandrake/stable/Contrib/ that's what you'd copy & paste. give the source a name of your own choice in the "name" dialogue box. leave the hdlist & all other options blank. click "save". it should add the source, build the hdlist automatically, & add it to your source list. when it's done, click "save" to exit software sources manager. if that method doesn't work, then i'm running out of ideas. :unsure: Chris

get the MozPlugger Mozilla plugin. works for many different types of audio/video files, RealPlayer included. the version for mdk9.1 also works on mdk9.2. also, if you look around, some contrib sources (i think plf & texstar) have a newer version of. or, you can also try the cooker version. Chris

i'm not entirely sure, but i get that sometimes too. some of the contrib sites can be buggy, or just as the message is telling you, they can be out of date & the hdlists are no good. i'd suggest adding non contrib sources first, then try different contrib sources last until you find one that works for you. might i suggest the contrib source right here in the forum dowloads section? that always works fine for me. Chris

3 things............ 1. you're in the wrong directory to run the script. you must be in........ /usr/share/bootsplash/scripts not....... /usr/share/bootsplash/themes 2. that might be all it takes, unless you're not paying attention to CaP SensiTiVe spelling. make sure you spell the theme exactly as it is named. 3. i don't have a bootsplash theme named tuxonblue. that's not to imply you don't. but...... you can only use bootsplash themes located in the /bootsplash/themes directory. if by any chance you're trying to use a regular desktop theme package, that won't work. PS: i just checked. the correct location to change KDE bootsplash screens is KCC->system->login manager, first tab. Chris

yes to both of your questions......... to change Mandrake bootsplash screens, see the following Tips N' Tricks link in the forum. look for my post. it's currently the last one in that thread. i just did it over this past weekend using the method i posted & it worked just fine. to change KDE bootsplash, open KCC (Kontrol Center)->system->boot. log into that as adminstrator, then check the tabs for the appropriate panel to change the KDE boot items. (i forget which tab it is right now, i'm at work) read the help files associated with that section if you get confused. it's not hard at all....... EDIT now that i thought about it a bit more, it might be KCC->system->login manager where you change KDE bootsplash things. it's one of those 2, at least .... :) Chris

or.........see my post in THIS THREAD about 3/4 down the page for how to properly install java with Mozilla without an mdk.rpm. Chris

at the risk of sounding redundant, i thought i'd add an easy to understand way to change the bootsplash screens for logout & bootup in MDK9.2. no offense, but i found the above explanations to either be outdated or a bit incomplete, especially for newbie understanding. so, the method i used to change my stock MDK9.2 ugly blue bootsplash screens is as follows. 1. first, using Mandrake Control Center (MCC), you need to get the following package....... bootsplash-(version number)mdk. the version on the mdk cd's is 2.0.6-1mdk, which works fine. there are newer versions in some contrib sites & cooker. get whichever you want, but the usual caveats apply to cooker apps (IE: use at your own risk. they may be buggy). so, in MCC->install software, type bootsplash in the search box & install it. 2. now you have to make a few scripts executable. you need to be in the directory where they are located. to do so, in terminal as root, issue the following command..... cd /usr/share/bootsplash/scripts hit enter type ls hit enter that will show you the scripts you need to make executable. they are as follows........ ./make-boot-splash ./remove-theme ./rewritejpeg ./switch-themes to make them executable, issue the following command for each one....... chmod 777 ./name-of-script (where "name-of-script" is the actual name of the script) hit enter after each instance example... chmod 777 ./make-boot-splash hit enter 3. now, the fun part. if you look in the directory /usr/share/bootsplash/themes you will see about a dozen or so themes that came with the boot splash package you installed. each of them has an image directory inside it that contains the bootsplash image files. use your preferred file browser to explore them & find one that you'd like for your new bootsplash screen. make note of the theme directory name. (not the image file itself!) now, if you're still in the /usr/share/bootsplash/scripts directory as root in terminal, yer good to go. if not, get back there & issue the following command to change your bootsplash screen.......... ./switch-themes nameoftheme (where "nameoftheme" is the actual name of the theme directory. this is CaP SensITivE!) for example, i used the Linux theme, so the command to install that would be....... ./switch-themes Linux you won't see any output after issuing the command to change themes. it will just appear to hang a few seconds, but that's ok. after issuing the command & you're back at the # prompt, it's into the home stretch. as for the other scripts......... "make-boot-splash" does the same thing as "switch-themes" as far as i can tell, "remove-theme" is sorta self explanatory, & "rewritejpeg" makes the image conform to the parameters (size, colour depth, etc.) that it needs to be in order for it to work properly as a bootsplash image. 4. you must now update lilo for it to recognize & be able to use the new theme. to do so, in terminal as root, issue the following command....... /sbin/lilo hit enter or, you can also do the following to accomplish the same effect.......... lilo -v hit enter 5. now, reboot your computer. you should see a new splash screen upon shutdown, & a new splash screen upon boot! enjoy! PLEASE NOTE since you are gonna be dicking around with your lilo.conf by doing this, it is always a good idea to make a backup of your known good lilo.conf file to a safe place, should something go horribly awry. and, use at your own risk! this worked fine for me without any problems, but i can't guarantee that for everybody this will be fool proof! also, one other thing you may wish to investigate if you're so inclined. from what i'm reading, you don't necessarily have to use the prefabbed bootsplash themes. you can (supposedly) use any image you want as long as you........ 1. use .jpg or .jpeg images 2. make sure the size fits the standard screen resolution standards (IE: 1024x768, 800x600, etc.) 3. make sure you make the proper images (you need at least three.......bootsplash, silent, & vt) 4. you place the theme in the same directory as the other themes & the images in a directory named images, & name those images per their respective screen resolutions i have not yet played with making my own bootsplash theme. if/when i get around to it, i'll post an addendum to this thread. hope this might have helped somebody out there. {a big thanks to DragonMage for helping me out with the chmod-ing stuff! :) } Chris

just guessing here, but it sounds like you might have chosen to high of a security level during setup....... what security level did you select during setup? if you selected anything higher than "standard", that could be the reason for you problem. if you're not sure, open Mandrake Control Center (MCC)->security->DrakSec. look at the first tab (basic) & down at the bottom where it says "security level" make sure that says "standard". check the other 3 tabs (network options, system options, periodic checks) & make sure all the options under each of those tabs are set to "default". save the configuration & reboot. then try doing things that need root permissions as normal user (like su in terminal, MCC, KDE Super User Mode, etc.). you should get the normal dialogue box asking for the root password that will let you access them. standard is a safe option, unless you have some uber secretive info on your computer (like the whereabouts of the WMD's, Jimmy Hoffa's body, my sanity) that you want to keep top secret. :D Chris

did you get all the updates/security/bug fixes for 9.2 yet? somewhere amongst them is a fix for the missing menu problems. Chris

without ever having used this particular app, i really can't offer exact instructions on how to install it. generally, with a tar.gz file, if your're using KDE or Gnome, you can just right click on the tar.gz file & choose "ark" "gnuzip" or some other unzipping program to untar it. or (preferred method), in terminal as root , do the following...... tar -xzvf nameofpackage.tar.gz hit enter (where nameofpackage is the exact name of the tar.gz file......CaP SenSitIVe!) then you'd issue the following commands....... as user..... ./configure enter make enter as root....... make install enter but, PLEASE NOTE.......depending on how the app was compiled, what dependencies it might need, if there's any specific installation path, etc, those commands might not install it properly. so, again, the only things i can suggest (in lieu of somebody else helping that has actually used this package) is to look a bit further for install or readme docs. sometimes they are buried in a subfolder of the directory. or, you can always try Google......... :unsure: Chris

never tried NVU, but since it's a tar.gz file, untar the file to a location of your own choice & look for a "README" &/or "INSTALL" file(s). one or both of them should provide you with proper installation instructions. they don't seem to provide much info on their website. but you probably know that already, huh? B) Chris

ok...........here's the best i can come up with at the moment. go to this Google Search for the error you're getting. there's several pages of info on it & several different solutions. one thing that is mentioned is checking if you have aRts set to load at KDE startup. to check that, go to Kontrol Center->peripherals->sound & check your aRts setup in there. other than those ideas, i'm sorta stumped for now.............sorry. :unsure: Chris

CLI=Command Line Interface............ IE: terminal, console, konsole, xterm, etc. sorry 'bout the shorthand....... so.......when you try to run aumix in terminal (CLI) what error output do you get, if any? you say nothing happens. to run it in terminal, type aumix then hit enter. gotta get going to work. i'll put more thought into this later.......... Chris