chalex20

Neither is recompiling software :-(

AVI is just a container, generally having approximately the same MPEG inside - DivX should be a good example of that. What kind of editing do you need to perform? Just cutting out ads etc?

Well, it's not so mandatory. Get Cooker source RPM, let your computer spend some two days compiling - and voila, you've got OO 2.0 final! :-)

Cinelerra has some abilities, though limited. Generally, in the eyes of "advanced amateurs", not to talk about professionals, MPEG is not considered "editable" - it's rather "final"/"demonstration" format, not "interim".

There exist CLI "dvdauthor" package, and GUI "qdvdauthor". Are you sure that the MPEG file you have is actually DVD-compliant? What DVD is made of is not some "regular" MPEG.

Use kdesu for that. kdesu -u sandbox whatever_application_you_want_to_run Issue kdesu --help for more help.

Most chances are that your DSL modem is actually a router and that it has some kind of firewall built-in, which disables port forwarding for requests coming "from within", or just blocks any request coming "from within" trying to address its "external" interface. This wouldn't work by definition.

Yes it does, but for MDK 10.0, i use 10.1 Will it work for me too? <{POST_SNAPBACK}> ftp://ftp.free.fr/pub/Distributions_Linux...9-1plf.i586.rpm This is PLF cinelerra package for 10.1. If you want some newer version, just recompile the correspondent PLF SRPM - it's a lot easier than recompiling the original source code.

Nope. Recompiling the module would suffice. I'd be pretty much interested to see the exact error message produced by the kernel. I remember several discussions at some Nvidia Linux forum regarding a compiler signature conflict, i.e. kernel is signed "blah blah blah gcc so-and-so blah blah blah custom blah blah blah", whereas the very same "custom" word is completely absent from the nvidia module signature.

PLF has RPMs of it, so there is no need to download the source code and recompile. I've had some bitter experience recompiling their source code - one who developed their makefiles deserves some sophisticated inquisition torture. That's not to mention that the code compilation gets sorely broken with each new gcc release - it's just full of "dirty tricks".

As far as I understand, you have to run "smart update" immediately after "smart channel --add", so that smart actually retrieves the channel information. At least, that's how I've configured my own system.

It may be. Try to load the "ehci_hcd" module forcefully ( issue "modprobe ehci_hcd" as root ), and see what happens. If the controller is detected, good. If the controller is not detected, your enclosure would work slooooooowly :-( .

Judging from the logs, I see that there may be some additional problem here. Note full speed and uhci_hcd . It means that all the transfers to and from the device would be performed at USB 1.1 speed ( 12 Mbit/s). If you have the device connected to a port able to support USB2, make sure that ehci_hcd module is loaded - this would enable USB2 transfers.

To add my own 2 cents: I encountered Linux for the first time when I was 25, decided to try it ( got some RedHat 4.x disks) , installed it on my home comp, tried to use it in my typical desktop usage scenarios, discovered that it could do none of those with the same ease as Windows, and removed it. Later, I tried RedHat 5.2 and then encountered Mandrake. Having tried that, I was really impressed with the speed of its development ( the negative impressions of RedHat 4 were still fresh, and Mandrake was a lot more workable, though not perfect ), and decided to keep the system and not to remove. Since then, I've upgraded my system through all the releases of Mandrake / Mandriva, now running MDV 2006, and gradually advanced from mainly booting Windows with occasional use of Linux now and then, to single boot Mandriva machine with long periods of Cooker usage. I do keep Windows XP on our second machine, due to there being a lot of Internet sites crucial to me, that refuse to work with free browsers ( or don't work well with them), and use it occasionally to browse these sites, or to reboot my Linux machine when it hangs ( Cygwin is a good thing :-) ).

You do something like the following : [root@linux alex]# smart query --path='*/DBD/SQLite.pm' Loading cache... Updating cache... ######################################## [100%] perl-DBD-SQLite-1.09-2mdk@i586

The most interesting thing is that I personally have not experienced a lot of problems with "nv" driver ( I'm to check how the "ati" driver behaves yet) even with X.org 6.9 CVS of Mandriva 2006. It's exactly the other way around - when using Nvidia proprietary driver, X just hangs from time to time, no display updates, no keyboard responses, mouse pointer moves and that's all. Logging in remotely and killing X helps, but further hangups are impreventible - sometimes X hangs again within minutes, sometimes within hours, and sometimes within days. So, it's relative slowness and no 3D ( sometimes I use it ) of "nv" driver vs. hangups of "nvidia" driver.

I'd suspect hardware, namely CPU or memory, problems. What happens if you invoke "Start - Run command" ( Alt-F2 on my system) and try to run "konsole" from there?

PLF has a lot of those. http://plf.zarb.org http://easyurpmi.zarb.org

What you observe "sitting there", is not the application itself, but rather "launch feedback". It is shown by KDE before running the application itself and held for some time (30 seconds by default and configurable). If the application being run shows some window, launch feedback taskbar entry is just replaced by this window one. Otherwise, the "launch feedback" taskbar entry just disappears. Now, the most probable reason for such behaviour may be the application just crashing at startup. Try to run the application from the console and see its output. If there are any signs of crash or some useful debug output, investigate it. If not, KDE has some bug :(

You do it like this gs -sDEVICE=x11alpha or like this gs -sDEVICE=x11

Go to "Skype for Linux" at forum.skype.com and rejoice :( - you're not the only ones having this "problem with sound device". Latest versions of Skype for Linux are a bit buggy in this regard, to say the least. Upon entering the forum, look for "skypedsphijack" - it provides some workaround. http://forum.skype.com/viewtopic.php?t=322...er=asc&start=90

Install libkdebase4-devel, libkdecore4-devel and libkdemultimedia1-common-devel. I believe it should suffice. If I guess correctly, you need to install "kernel-source-2.6" or "kernel-headers-2.6". Aside from that, Nvidia developers have got an excellent README, find some time to consult it, it will ease the installation.

May you provide more details so that I be able to provide you with step-by-step instructions? Which card is it? Nvidia? Go to http://easyurpmi.zarb.org . Follow the instructions to add PLF to your repositories. Install Amule. I'm eager to see normal mixer for SB Live / Audigy as well. Add PLF-non-free to your repositories. Install win32-codecs. Use mplayer, xine, kaffeine, kmplayer, kplayer, in short, anything based on mplayer or xine, to play your video files. They would play. The reason they don't "out of the box" is legal rather than technical. Another kind of legal problem. Go to Sun's site, download JRE or JDK ( they even have RPM), install it, enjoy java. Vast majority of video games are for Windows ( or Sony PS ) and not for Linux. Purchase Cedega, it may help you run most of the games. Or make the computer dual-boot and use each OS in its niche. You haven't to use Linux exclusively. If the particular piece of software you're trying to install, is packaged for Mandriva, it's "several clicks away" as well. Use "drakrpm" or "smart" ( in Mandriva 2006), it's exactly the tool for this matter. DOS 6.22 under Linux? I'm afraid there is indeed no way, for the very simple reason that DOS 6.22 is not Open Source. Try FreeDOS, it may enable you to make its bootable disk. You may also see countless posts in countless forums stating various kinds of software and hardware problems in Windows, and so? Have you tried to go to www.alsa-project.org and look at their soundcard-related Wiki? http://alsa.opensrc.org/AlsaMixers

And you had to be a good mechanic just to drive the car :) OTOH, there were neither "car licenses" nor "driving permits" nor "mandatory insurances" :)

There is one very simple reason for such things being easier in Windows - the web sites you relate to, were deliberately and intendedly designed for users of IE on Windows. Their designers care neither for alternative browsers nor for alternative OSes, for variety of reasons. To go even further, there are sites that do their best to check that you indeed use IE on Windows, and deliberately block all the other browsers, in spite of these very browsers being fully and completely capable of supporting all the tricks of these very websites. In a better case, you may be presented with some crippled version of the site. In some cases, just changing the "user agent" string of the browser shows you the site as needed. Gmail site interaction with e.g. Konqueror is an excellent approval for this - you enter the site with default identification and see some crippled version telling you to use "supported browser". You change the identification to "Internet Explorer" and surprise! all works, no complaints. For other sites ( Israeli banking sites come to mind) even changing the "user agent" string wouldn't help - they use a lot of other tricks to exclude non-IE browsers. Now, look at some "magic circle" here. Users enter a site using alternative browsers, fail to browse it, change the user agent string to "IE" - and hoopla, all works. The site logs show that the vast majority of its users use IE ( according to "user agent" strings), so there is no need to adapt the site to support alternative browsers - it wouldn't be worth the money invested. "Catch 22" at its best.