Jump to content

devries

Members
  • Posts

    4118
  • Joined

  • Last visited

Posts posted by devries

  1. Packages submitted by external packagers end up in contrib. Or if external packagers choose so they can start their own repo like MDE or mcnl did. There are more pacakges available for Mandriva then for almost any other distro.

     

    I agree with you that Mandriva doesn´t know how to make money. However that is not a bad thing. Most businesses only rip you off an i prefer a componay that doesn´t have a clue how to make money from me. As long as they make enough to survive I don´t care.

  2. I don´t know about your IQ but if you need a program like chemoffice it´s high enough to get it working with wine. If you didn´t pull it off I´m pretty sure it won´t work. Google is known sometimes to be wrong. :)

     

    Another option is using an emulator. Read in the wiki (link top of the page) about qemu. It will allow you to install windows and you can then install chemoffice on windows.

  3. What software is lagging behind? Sure the official packages are now almost 9 months old but there are lots of community repo's out there if you want to run the latest software. (and if you really want to have the latest you can always build from source). The postive aspect of keeping with a version for a year means that its very stable. It's almost impossible to crash Mandriva 2006.0. I managed to do it only 2 times since I installed it. :)

  4. Basically building a kernel is the same as building any other piece of software. However Mandriva patches its kernels so that they are not the same as the ones you can download from kernel.org. However the only thing I missed when I used to build kernels was supermount. With that in mind download the source from kernel.org. Untar in /usr/src/. Open a console. cd to /usr/src/<linux source> and type: make xconfig. Click 'open', browse to /boot and select 'config' (that will give you the working Mandriva config. If you know what you're doing you can have a look at the options and change some stuff). Save and exit

     

    Type: make && make modules_install

    Type: make install

     

    Reboot and that is it (do all these steps as root)

     

    Good luck.

  5. You mean this:

     

    p.png

     

    Update to KDE 3.5.2 :)

     

    Or edit the kickerrc:

     

    Under [general] add this line: BackgroundTheme=/usr/share/apps/kicker/wallpapers/default.png (or edit it to reflect your preferences)

     

    Restart kicker with: dcop kicker Panel restart

  6. Fine tuning of the installation directories:

    --bindir=DIR user executables [EPREFIX/bin]

    --sbindir=DIR system admin executables [EPREFIX/sbin]

    --libexecdir=DIR program executables [EPREFIX/libexec]

    --datadir=DIR read-only architecture-independent data [PREFIX/share]

    --sysconfdir=DIR read-only single-machine data [PREFIX/etc]

    --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]

    --localstatedir=DIR modifiable single-machine data [PREFIX/var]

    --libdir=DIR object code libraries [EPREFIX/lib]

    --includedir=DIR C header files [PREFIX/include]

    --oldincludedir=DIR C header files for non-gcc [/usr/include]

    --infodir=DIR info documentation [PREFIX/info]

    --mandir=DIR man documentation [PREFIX/man]

     

    Try that. But if you just want to install the program and are not building it for fun you really should install an rpm. If you can't find it you haven't setup urpmi correctly. Read the wiki (link at top of the page) for more information.

  7. Works for me. I scan in Kooka, click the printer icon in Kooka, from the dropdown menu I select print tp pdf file and a few seconds later I get a pdf file with my scan.

     

    Try the convert to pfd from normal file (for example in kwrite). What happens then?

  8. To help you best when you ask a question on the MUB we need a minimum amount of relevant information and you need to have done some things yourself. That's why I've made a small list of things to check when you open a new topic on Mandrivausers.org. It's just a first try so if you want to give any input on these items, or maybe want to add something, feel free to reply.

     

    Practical posting guidelines:

     

    1: Use the search function to check if your question has been answered in an earlier post.

     

    2: Post your problem in the correct sub-forum.

     

    3: Use a clear topic-title and, if you use Mandriva, tell us what version you're using. Example: Mandriva 2006 - No sound after configuring Audigy 2 ZS.

     

    4: Always tell us what you have tried yourself and what tools you have used.

     

    5: Describe your problem coherently.

     

    6: Do not ask the same question twice.

     

    7: If you problem is solved, edit your post and add the word [solved] to the topic title

     

    8: If people help you, say thank you. Don't just leave the thread. (suggestion made by Dustpuppy)

     

    9 If you solve a problem, say how you did it, rather than just saying it's now solved. Then other people with the same problem can find the solution. (suggestion made by Dustpuppy)

  9. Have a look at tv-card. Perhaps the tuner number can be found at the chip on the card. Or look at the box in which the card came. I´m afraid there is no easy wy to find out what the tuner number should be. You could also download the source of the driver and look if there is a tuner.h file in it. Look in there for what you can try.

×
×
  • Create New...