chalex20

SANE has several frontends, such as CLI scanimage, hell-knows-what-based xscanimage, GTK-based Xsane and KDE-based Kooka (surprise, surprise :)) Kooka is not and never has been. OTOH, K3B is. As far as I remember, Kooka has been designed as SANE frontend with kind of "integrated" OCR abilities. Sort of running GOCR from within, sparing users the need to issue a number of cryptic commands.

Is it just me or there indeed is some little bug in your review? After this sentence, you put some image to illustrate your words. Here, the image appearing is the same as the previous one. It should have been different, IMO. Otherwise, well done :-)

Note this managed option. Clear sign of udev at work.

SB Audigy DE here, same problem with KMix. No problem with Alsamixer, though. Try kamix, it handles Audigys much better, all the tabs are in place.

Wait... Smart is a command line tool, is it not? You don't have to run it in GUI mode! :) My opinion - barring little annoyances here and there, smart is what rpmdrake should have been.

Good to know there is a script for this matter :) And why not just rpm --rebuild /path/to/source/rpm rpm -Uvh rpm/RPMS/586/rpmname.rpm ? BTW, what about build- and run- time dependencies?

mencoder may do the trick. transcode tools may do it as well ( PLF ). Nevertheless, take into account that due to the very nature of MPEG compression, converting DivX( which has already been converted from the original DVD) back into DVD would result in quality degradation, and the result wouldn't generally be equal to the original DVD. And one more thing : transcode / avidemux / mencoder wouldn't bring you complete DVD image but rather MPEG files in DVD compatible format. You'd need the "dvdauthor" application to form VIDEO_TS and AUDIO_TS directories for you, and it's these two directories you need to feed K3B with, in order to burn your Video DVD.

Unfortunately, a lot of otherwise good applications tend to introduce a lot of incompatible changes of their configuration file formats. You run the new version, and suddenly, the old one starts misbehaving. So, I'd add "/mnt/althome" to your proposal. One may do even some more radical thing, namely, allocate a separate partition for documents/pictures/music files/etc, and restrict /home to configuration files only. Hmmm.... I wonder why there are scores of text editors etc, most of them half-baked, if there is indeed no tendency to duplicate efforts... Unfortunately, there certainly is. By the way, "handling png files". If I'm not mistaken, there are about some dozen of different image viewers in Mandriva, all doing approximately the same thing with slight variations here and there. This is applicable to any platform using dynamic/shared libraries wisely. And what should one do if some interesting software has just got a new shining version finally repairing some long-standing bug? There may be a package for it, that's only that it would be a Cooker one, and not one for 2005LE/2006. There, you're stuck with an old buggy version. Unless you know to recompile source RPMs.

As far as I understand, this embroidery machine emulates serial printer, not parallel. If it's on a USB port, it should emulate some serial-to-USB converter. "Generic non-Postscript" printer is called "raw printer" in CUPS. So, what needs to be done is the following, IMHO: - Check /dev/usb/ttyS0 or /dev/ttyUSB0 for existence ( check what appears in /var/log/messages or in "dmesg" when attaching the printer) - Using CUPS or Drakprint, define some "raw" printer attached to /dev/ttyUSB0 ( or whatever seems relevant).

My TV-Out used to work with GF5200 and Mandriva 2005/Cooker 2006, so there should be no reason for it to stop working. I'm not able to check it right now, though, due to some technical problems. Now, to the xorg.conf Section "Monitor" Identifier "monitor1" VendorName "Plug'n Play" ModelName "Flatron" HorizSync 30-83 VertRefresh 50-75 EndSection Section "Monitor" Identifier "tv" HorizSync 30-50 VertRefresh 60 EndSection You may drop "HorizSync" and "VertRefresh" and use "UseEdidFreqs" only. I use them because Nvidia driver has some problems reading my keyboard/mouse/monitor switch EDID data. Section "Device" Identifier "device1" VendorName "nVidia Corporation" BoardName "GeForce FX 5200" Driver "nvidia" Screen 0 BusID "PCI:2:0:0" Option "DPMS" Option "NoLogo" "1" Option "RenderAccel" "False" Option "UseEdidFreqs" Option "ConnectedMonitor" "CRT" Option "NvAGP" "2" EndSection Pay attention to "Screen 0", "BusID" and also "ConnectedMonitor". These options are mandatory. Section "Device" Identifier "device2" VendorName "nVidia Corporation" BoardName "GeForce FX 5200" Driver "nvidia" Screen 1 BusID "PCI:2:0:0" Option "DPMS" Option "NoLogo" "1" Option "RenderAccel" "False" Option "ConnectedMonitor" "TV" Option "NvAGP" "2" EndSection The same for "Bus ID","Screen 1" and "ConnectedMonitor". These are mandatory. Section "Screen" Identifier "screen1" Device "device1" Monitor "monitor1" DefaultColorDepth 24 Subsection "Display" Depth 8 Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 15 Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 16 Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 24 Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubsection EndSection Section "Screen" Identifier "screen2" Device "device2" Monitor "tv" DefaultColorDepth 24 Subsection "Display" Depth 24 Modes "640x480" EndSubsection Option "TVOutFormat" "COMPOSITE" Option "TVStandard" "PAL-B" EndSection Section "ServerLayout" Identifier "layout1" InputDevice "Keyboard1" "CoreKeyboard" InputDevice "Mouse1" "CorePointer" Screen 0 "screen1" Screen 1 "screen2" rightOf "screen1" EndSection And finally, we define the Server consisting of two separate displays. Not clone, but good for watching films on TV. I used to get work done on my main monitor while watching films on my TV, at the same time. Just run the player as follows: DISPLAY=:1.0 player your_movie_file

If I'm not mistaken, they do use DMA, it's only that you have no influence upon it.

The module is now called it821x, and not iteraid. No need to compile, it is provided by default Mandriva kernel "out of the box".

You need to use a CD player that supports digital audio extraction, such as KSCD, Amarok, Kaffeine etc.

My guess is that Windows configures the card to perform digital output, hence the need to switch ports.

It may actually work, but there is one little problem - your new 160 GB is partitioned exactly ( almost ) as your old one was, so the 120 free GB are in an unpartitioned space. And one more thing - it works only for new big disks, that ( logically ) do not differ in geometry.

Correct me if I'm wrong, but isn't a wheel supposed to work as a regular button, when you press it rather than rotate it? It has been like this on all wheel mice I've encountered. IMHO, there is no sense to enable 3 button emulation for a wheel mouse.

I believe that it has a lot to do with driver loading order. "alias eth0" and "alias eth1" have an effect only when the drivers are loaded along the lines of "modprobe eth0", or if there is any request to eth0. If the USB driver loads first, it catches eth0 regardless of the aliases. So, what you have to do ( and what I've successfully done before to solve a similar problem ) is to force 8139too to load before the USB driver. One way to do this is to put "8139too" line into /etc/modules ( for kernel 2.4.x ) or into /etc/modprobe.preload ( for kernel 2.6.x).

DON'T REMOVE #s HERE. Leave them as is!!!!!! :-( Why not? Don't load it by force, the driver knows to load this module by itself.

Here is the XF86Config-4 file: XF86Config_4.txt Many Thanks, -SP <{POST_SNAPBACK}> It seems to be all right, just replace 'driver "vesa"' with 'driver "nvidia"'. Don't change anything else.

Can you post your XF86Config-4 as well?

Generally, PnP must kick in. But if it doesn't, there is not much work to correct the situation. Regarding "clean re-install" - forget it, it's not needed :-) Do the following before you switch the card. It would be useful even in case PnP does actually kick in. - Download NVIDIA drivers for your card. Read their instructions regarding installation, they have VERY GOOD README. - Upon popping the new card in and switching on your computer for the first time, load linux in text mode instead of graphical. It's done by hitting ESC at the LILO prompt and typing "linux 3" ( or whatever you use ) instead of choosing "linux". - Install the NVIDIA drivers and edit XF86Config-4 according to instructions. - "init 5" - and enjoy your new card in GUI.

You may have a control over it, it's present in XP PRO, as far as I remember it's called "Partition management" or smth. like this. It also gives you a possibility to see which drive is which. hda is "master device attached to primary IDE channel". hdb is "slave device attached to primary IDE channel". hdc is "master device attached to secondary IDE channel" ( I strongly suspect that you have a CD-ROM or smth attached there, and not a harddisk ). hdd is "slave device attached to secondary IDE channel". The most chances are that hda corresponds to your C: disk, hdb - to your D:, and hdc to your E:. But you better check it with Windows partition manager.

May it be that the sound is just muted? ALSA tends to such a stupidity.

He's completely right. ISA devices started as non-PNP. PNP was defined for them later. PCI devices are PNP by definition. They don't start working till they are configured.

http://www.mostang.com/sane - look for "Supported devices". If your devices are listed there as supported - go for it.