Make Zen V Plus drivers "open-source&quo

Zen V Plus firmware need a lot of improvements...
I'm waiting for new firmware 3 months...
If nobody from Creative team don't have time to work on this firmware i propuse to make it open source, or put source files on the website. I think that many people want to make this firmware better.
If you don't have to to do it please allow to make it by somebody other!
Simek
P.S. Sorry for my bad english!

wow, what kind of earphones/headphones do u guys use.. how come the volume is not loud enough for u.. i listen at volume level 4-6 and find them loud enough..
o_0?

Similar Messages

  • Zen:V plus drivers needed, ple

    i have lost my ZEN:V Plus Installation CD, and need to put drivers back on computer... Anyone know where i an get the drivers? Because?I cant find them on Creative's website :sThank you

    Hi.
    I'm having the very same problem as the above stated, i was "googling" for people who had lost their Zen V Plus drivers, and this was the only thread i found.
    So I beg you, or whoever has them, if you could send them to my e-mail : [email protected] , it would be really helpful.
    Thanks
    Jo?o Rocha

  • Petition to open-source OCCI

    We are a large Oracle site running 10g on Solaris. We have plenty of C++ code. We are using g++ 3.4.x and we wish to use OCCI. But we can't because it's not supported with g++ on Solaris. We refuse to backport our C++ code to Sun's ancient RogueWave C++ library (non-standard) and Oracle doesn't support STLPort (also provided by Sun).
    I know that there are many of you out there in a similar situation. You can't get OCCI to work with your combination of platform/compiler/std.library. For examples of exasperated users see:
    Re: occi doesn't support STLPORT
    Re: Lower level information
    OCCI with Red Hat Enterprise Linux 3
    C++ on Solaris with OCCI
    I understand that it is unreasonable expect Oracle to provide binary libraries for every combination of platform/compiler/library. The solution seems clear: open-source OCCI.
    The objection might be raised that this would make it hard for Oracle to provide support. In reality, most potential users of OCCI would (in my opinion) be happy to just have the opportunity of using it. The reality is that most of us that can't use it are trying to make do with (somewhat poor) open-source alternatives anyway. And Oracle can always continue to provide the "official" binaries with the current level of support.
    I raised a TAR back in July '05 (4562431.993) which resulted in the creation of an Enhancement Request (4522152). This ER seems to have disappeared into a black-hole.
    If you want Oracle to be more responsive to your needs with respect to OCCI, then please reply to this message. Hopefully, someone at Oracle will realise that their customers have an unfulfilled need here and act upon it.
    Cheers,
    Mike.
    mlambrellis(AT)powercor.com.au

    Please add my name to the petition.
    I also tried a tar.
    The Oracle person added all my comments to the ER, but the occi people basically said
    "libocci is not supported in SuSE 10.1"
    Here is some of what I sent originally for everyone's edification:
    We are trying to build a large 64 bit C++/Qt/OCCI application on
    SuSE 10.1 Linux. Here's a 'uname -a':
    Linux grima 2.6.16.21-0.13-smp #1 SMP Mon Jul 17 17:22:44 UTC 2006 x86_64 x86_64 x86_64
    SuSE 10.1 comes with gcc 4.1 and uses libstdc++.so.6.x.x. All
    the kde/qt libs have been compiled against libstdc++.so.6.x.x.
    libstdc++.so.6.x.x is not compile-time compatible with
    libstdc++.so.5.x.x. As far as we know, there is NO 64-bit
    libocci library available that links against libstdc++.so.6.x.x
    from any of oracle's public downloads. Thus, our application
    will not link. This is unacceptable.
    SuSE provides a libstdc++.so.5.x.x for backwards compatibility.
    If we link our app explicitly to the older libocci, we get a
    compile-time warning and a run time crash.
    We need Oracle to
    1) Release the source code for OCCI under an LGPL license or
    similar so that we and others can compile libocci ourselves
    for whatever version of compiler/libstc++/platform.
    or, minimally.
    2) make sure all major distros' versions of
    gcc/libstdc++/platform are tracked and a version of libocci
    exists for public download for each.
    This is a repeat of the gcc 2.96 fiasco that existed several
    years ago when one could not compile an occi program against gcc
    3.x because there the only libocci versions available had been
    linked against the incompatible 2.96 version.
    Please release source code!

  • Why Adobe doesn't use the open source codec x264vfw for Elements as .AVI?

    Well we all know who wants to work with the x264vfw that it does not work in Premiere Elements.
    But i think Adobe could have make it work with the open source x264vfw or with the AVC-Intra coder.
    I am still asking me also why it would work when i do re-encode it with another program to h264 again but as MP4?
    Adobe does itself make it really easy and messing with us. because they are saying there is support for h264 but only for MP4 and another one...
    Why they don't add .AVI support that goes to the support of Adobe because i can't get into the livechat.... because its only under the week....
    This Codec the H264 X264 and AVC-1 are the most used codecs today in my opinion so i don't know why they don't sit their Dev's on that.
    ALSO that it does not work on their 600$ Application named Premiere Pro is something that i don't understand...
    For me its unbelievable if i am honest.
    I now want to know why adobe is such a service desert in this point.
    They all yelling about that but Adobe does nothing.
    If somebody knows a solution without re-encoding or FFMPEG solution, because it does not work well with my Variable Frame Rate in Premiere Elements let it me know.
    Also i want an Answer from Adobe why they don't do anything.
    I tried to put the x264vfw .dll into plugins or the folder but the problem is not solved.
    I am sitting for Quiet a time behind that and see how many threads there existing... and it's only frustrating.
    ADOBE it's time to do something!!!

    I still think that a lot of peoples have done that. When you see how many persons are suffering by this problem...
    Well i have not known about the Adobe Staff tags that they are not the real help from the real support.
    Thank you about that.
    Normally i would send a mail but there is no option for that... to they're support team.
    I said that it hard for me to get some support under the week. I have to work from 6am until 5pm with driving. and have to do some things a home.
    Feature Request/Bug Report Form i think will not help or have you used it and got an answer? I want an answer not only request something.
    " We normally do not send personal replies to feature requests or bug reports. We do, however, read each and every message. We use the information to improve our products and services. Your comments, suggestions, and ideas for improvements are very important to us. We appreciate you taking the time to send us this information. "
    And yes i buied last year Premiere Elements to Christmas time.
    I still don't understand why they didn't add support for H264, h264, X264, x264 and AVC-1 for .AVI wrapper when they have the licenses for the codec...
    Also .AVI is really often used... not like .MKV

  • Zen V Plus successefully working with Via

    Does anyone know how to make Zen V Plus talk to Vista? The OS recognizes the mp3 player's identity, but transferring files doesn't take. Also, the formatting, resetting and rebooting stuff did not help. Any suggestions pls.

  • Making Java GUI code open source?

    Hi I am a beginner to Java. I was wondering if this was possible.
    Say I write a calculator applet to host on my website for other users to use. Can I make just the GUI code open source so users can modify the appearance of the applet and then save the GUI code to their usernames on the web server, so the next time they logon, the changed calculator appearance will be stored on the web server already. However, the core code should remain the same so new users who sign up won't be using some else's Calculator GUI code.

    IIRC correctly, most databases support storing binary data, so they should be able to store class files. But then you'd have to extract that class file to someplace where it can run everytime. You're probably better off just storing the class files in a separate dir and whopping up a page that uses user info to determine the correct class to load.
    But I agree with malcolmmc that it doesn't make much sense to have people upload their code to your server.

  • X11 and open source ATI drivers

    Hi. Well I have a little(big) broblem. I have ATI Radeon x1600 video card, and I need open source video drivers (not fglrx). I installed it by the article at archlinux wiki:
    Open Source ATI Drivers
    The open source drivers will work to some degree on Radeon chipsets up to the Radeon X850. Radeons up to the 9200 series are fully featured, stable, with full 2D and 3D acceleration. Radeons from 9500 to X850 have full 2D acceleration, the y provide 3D acceleration as well but it doesn't support all the features that the proprietary drivers do. A full list of supported chipsets can be found here.
    [edit]
    Installation and Configuration
    The package is xf86-video-ati. Note: if you have previously installed the proprietary driver make sure to remove fglrx, fglrx-beyond, and fglrx-utils.
    pacman -S xf86-video-ati libgl-dri
    Edit your xorg.conf, and add or make sure you have the following in their given sections. For
    Section "Module"
    Load "glx"
    Load "dri"
    Load "drm"
    EndSection
    Section "Device"
    Identifier "name" # your alias
    Driver "radeon"
    Option "XAANoOffscreenPixmaps" "true" #needed for aiglx
    EndSection
    Section "DRI"
    Group "video"
    Mode 0660
    EndSection
    When using this driver, make sure you do not have fglrx-utils installed but use libgl-dri instead. Otherwise you'll have the wrong libGL.so which will cause direct rendering not to work.
    So I did all this crap and i get, when i tryed to start X:
    (EE) Failed to load module "glx" (module does not exist, 0)
    (EE) Failed to load module "radeon" (module does not exist, 0)
    My xorg.conf:
    Section "ServerLayout"
    Identifier "Xorg Configured"
    Screen 0 "aticonfig-Screen[0]" 0 0
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "PS/2 Mouse" "CorePointer"
    EndSection
    Section "Files"
    RgbPath "/usr/share/X11/rgb"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc:unscaled"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/100dpi"
    FontPath "/usr/share/fonts/PEX"
    FontPath "/usr/share/fonts/cyrillic"
    FontPath "/usr/share/fonts/Type1"
    FontPath "/usr/share/fonts/ttf/western"
    FontPath "/usr/share/fonts/ttf/decoratives"
    FontPath "/usr/share/fonts/truetype"
    FontPath "/usr/share/fonts/truetype/openoffice"
    FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
    FontPath "/usr/share/fonts/latex-ttf-fonts"
    FontPath "/usr/share/fonts/defoma/CID"
    FontPath "/usr/share/fonts/defoma/TrueType"
    EndSection
    Section "Module"
    Load "ddc" # ddc probing of monitor
    Load "dbe"
    Load "dri"
    Load "drm"
    Load "extmod"
    Load "glx"
    Load "bitmap" # bitmap-fonts
    Load "type1"
    Load "freetype"
    Load "record"
    EndSection
    Section "ServerFlags"
    Option "AllowMouseOpenFail" "true"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "keyboard"
    Option "CoreKeyboard"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" ""
    Option "XkbVariant" ""
    EndSection
    Section "InputDevice"
    Identifier "Serial Mouse"
    Driver "mouse"
    Option "Protocol" "Microsoft"
    Option "Device" "/dev/ttyS0"
    Option "Emulate3Buttons" "true"
    Option "Emulate3Timeout" "70"
    Option "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
    Identifier "PS/2 Mouse"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "ZAxisMapping" "4 5"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "true"
    Option "Emulate3Timeout" "70"
    Option "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
    Identifier "USB Mouse"
    Driver "mouse"
    Option "Device" "/dev/input/mice"
    Option "SendCoreEvents" "true"
    Option "Protocol" "IMPS/2"
    Option "ZAxisMapping" "4 5"
    Option "Buttons" "5"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    HorizSync 28.0 - 96.0
    VertRefresh 50.0 - 75.0
    ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
    ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
    ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
    ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
    ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
    ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
    ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
    ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
    ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
    ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
    ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
    ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
    ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync interlace
    ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
    ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
    ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
    ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
    ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
    ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
    ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
    ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
    ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
    ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
    ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
    ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
    ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
    ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
    ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
    ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
    ModeLine "1800x1440" 230.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
    ModeLine "1800x1440" 250.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
    ModeLine "640x480" 43.2 640 680 744 848 480 481 484 509 -hsync +vsync
    ModeLine "768x576" 35.0 768 792 872 976 576 577 580 597 -hsync +vsync
    ModeLine "768x576" 42.9 768 800 880 992 576 577 580 601 -hsync +vsync
    ModeLine "768x576" 45.5 768 808 888 1008 576 577 580 602 -hsync +vsync
    ModeLine "768x576" 51.8 768 808 888 1008 576 577 580 605 -hsync +vsync
    ModeLine "768x576" 62.6 768 816 896 1024 576 577 580 611 -hsync +vsync
    ModeLine "800x600" 68.2 800 848 936 1072 600 601 604 636 -hsync +vsync
    ModeLine "1024x768" 113.3 1024 1096 1208 1392 768 769 772 814 -hsync +vsync
    ModeLine "1152x864" 81.6 1152 1216 1336 1520 864 865 868 895 -hsync +vsync
    ModeLine "1152x864" 119.7 1152 1224 1352 1552 864 865 868 907 -hsync +vsync
    ModeLine "1152x864" 143.5 1152 1232 1360 1568 864 865 868 915 -hsync +vsync
    ModeLine "1280x960" 124.5 1280 1368 1504 1728 960 961 964 1001 -hsync +vsync
    ModeLine "1280x960" 129.9 1280 1368 1504 1728 960 961 964 1002 -hsync +vsync
    ModeLine "1280x960" 179.0 1280 1376 1520 1760 960 961 964 1017 -hsync +vsync
    ModeLine "1280x1024" 191.0 1280 1376 1520 1760 1024 1025 1028 1085 -hsync +vsync
    ModeLine "1400x1050" 122.6 1400 1488 1640 1880 1050 1051 1054 1087 -hsync +vsync
    ModeLine "1400x1050" 149.3 1400 1496 1648 1896 1050 1051 1054 1094 -hsync +vsync
    ModeLine "1400x1050" 155.8 1400 1496 1648 1896 1050 1051 1054 1096 -hsync +vsync
    ModeLine "1400x1050" 179.3 1400 1504 1656 1912 1050 1051 1054 1103 -hsync +vsync
    ModeLine "1400x1050" 214.4 1400 1512 1664 1928 1050 1051 1054 1112 -hsync +vsync
    ModeLine "1600x1200" 280.6 1600 1728 1904 2208 1200 1201 1204 1271 -hsync +vsync
    Option "DPMS" "true"
    EndSection
    Section "Monitor"
    Identifier "aticonfig-Monitor[0]"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "radeon"
    Option "XAANoOffscreenPixmaps" "true"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    DefaultDepth 16
    SubSection "Display"
    Depth 1
    Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
    Depth 4
    Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
    Depth 8
    Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
    Depth 15
    Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
    Depth 16
    Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
    Depth 24
    Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
    Depth 32
    Modes "1024x768" "800x600" "640x480"
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "aticonfig-Screen[0]"
    Device "aticonfig-Device[0]"
    Monitor "aticonfig-Monitor[0]"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Section "DRI"
    Group "video"
    Mode 0666
    EndSection
    Any help? =/

    I may be wrong, but I dont think the open source drivers support the X1xxx series cards. 
    If I am wrong, then make doubly sure you actually did install xf86-video-ati and libgl-dri.  Then, maybe try starting from a fresh Xorg.conf by running this as root in the console (without X started):
    cp /etc/X11/xorg.conf /etc/X11/xorg.conf.bak
    X -configure
    mv xorg.conf.new /etc/X11/xorg.conf
    And see if that works, if it does, slowly build on top of it, until you have your desired result

  • LiveView: Make it 'open source' for the benefit of all

    First, let me start by saying LiveView is a great concept.  However...
    SonyEricsson needs more than just a great concept to make this a useful and successful product.
    At present, it is horrendous and they should be embarrassed with releasing this device to the market in its current state.
    The hardware is average but the software/firmware is absolutely awful, leading to an extremely unreliable / barely useful device.
    My experiences since receiving my LiveView have not been dissimilar to the rest of the users who have seen frequent disconnections / lockups / non-working features.
    It is clear that there is interest in this device from the Android Community / Xda-Developers, etc. with many members keen to resolve LiveView's issues themselves - yet they are limited by a closed platform. Given Engadget's review of the LiveView, SonyEricsson's poor track record of providing continued support / updates to their products and their statement that there will be no updates issued for the device - I would think it not inappropriate to demand that an update at least be made to make the software entirely open source, or firmware/code released with a vehicle/drivers for updating.
    I'm sure if the community were given the freedom, they could make the software reliable, customisable and perhaps even define innovative new ways to use the hardware.
    If that happens, there's increased interest in the community which in turn would lead to more sales.
    SonyEricsson, why not leverage the benefit of a willing (and free) workforce that are more interested in improving your device than you are?
    (TLDR) In short, SE's failure to provide a fully functioning reliable product combined with their lack of commitment to continued support has paved the way for a global community of very tech savvy individuals and groups, willing to devote their time freely to improving LiveView. I say to SonyEricsson, let them - everyone wins.
    To other customers, would you support making LiveView open source?
    If so - let SonyEricsson know here and by submitting an e-Mail via their Support site (for UK, where SE's global management team is based):http://www.sonyericsson.com/cws/common/contact/contactusemail/accessories?cc=gb&lc=en

    Once there is a successor model, I would welcome it very much if the source code is released, and the owner of the MN800 can finally use their device.

  • Open source r5xx drivers

    Hi, I've been playing around with new open source drivers for ati r5xx series. The driver is still in early development and it currently doesn't work on my card (ATI Mobility Radeon X1400), because the driver in git contains a limited number of PCI IDs for different Radeon X1000 graphics cards. I've created a package for this driver but didn't upload it on AUR because:
    1. i don't think i have enough knownledge about building packages (not yet)
    2. haven't looked into what dependencies to include in the package
    3. driver is still in early development with almost no use to end-user
    nevertheless, i have successfuly build a package and if anybody wants to add it to AUR or build it, here it is:
    pkgname=xf86-video-avivo-git
    pkgver=20070620
    pkgrel=1
    pkgdesc="Open source ATI/AMD R5xx drivers for Xorg"
    arch=('i686')
    url=""
    license=('GPL')
    depends=('xorg-server>=1.3.0' 'libpciaccess-git') #or does libpciaccess-git go to makedepends?
    makedepends=('git')
    provides=()
    conflicts=()
    replaces=()
    backup=()
    install=xf86-video-avivo-git.install
    source=()
    noextract=()
    md5sums=()
    _gitroot="git://anongit.freedesktop.org/git/avivo/xf86-video-avivo"
    _gitname="xf86-video-avivo"
    build() {
    cd $startdir/src
    git clone $_gitroot
    cd $_gitname
    ./autogen.sh --prefix=/usr/
    make || return 1
    make DESTDIR=$startdir/pkg install
    i also had to build libacpiaccess-git to be able to build the driver:
    pkgname=libpciaccess-git
    pkgver=20070620
    pkgrel=1
    pkgdesc="Generic PCI access library"
    arch=('i686')
    url=""
    license=('GPL')
    depends=()
    makedepends=('git')
    provides=()
    conflicts=()
    replaces=()
    backup=()
    install=libpciaccess-git.install
    source=()
    noextract=()
    md5sums=()
    _gitroot="git://anongit.freedesktop.org/git/xorg/lib/libpciaccess"
    _gitname="libpciaccess"
    build() {
    cd $startdir/src
    git clone $_gitroot
    cd $_gitname
    ./autogen.sh --prefix=/usr/
    make || return 1
    make DESTDIR=$startdir/pkg install
    you can find more info on Avivo driver on this page: http://www.phoronix.com/scan.php?page=a … 753&num=1#
    Last edited by billy (2007-06-20 09:57:27)

    This kind of sums it up, doesn't it?
    http://www.userfriendly.org/cartoons/archives/99feb/19990208.html

  • Do open source drivers detect S-Video port on ATI X1200?

    Hello All,
    I have a Dell Inspiron 1721 Laptop with an ATI "RS690M Radeon X1200 Series" graphics card (or rather my mother does...). I'm currently running Kubuntu 8.10 on it, but I really would like to get Arch64 back on it instead. I had to switch to Kubuntu because ATI dropped support for the X1200 card and the open source drivers wouldn't detect the S-Video port, which is a must, because she hooks it to the TV to watch movies.
    I'm trying to find out whether or not the open source drivers will now detect and support the S-Video out (it's been quite a while since I last tried Arch on it). Or alternatively if proprietary support has returned, I had heard talk of that happening a while back (via a legacy driver), but to my knowledge there's still no way to use the proprietary driver on Arch. Is this correct?
    The only way I know of to find out if the S-Video will work with the open source drivers is to reinstall Arch and try it. However, there's a lot of work that will need backed up first and she can't do without her computer for very long (which makes my job a bit tricky), so I was hoping to see if anyone with the same computer/video card knew the answer to this. I don't mean to come across as lazy, but it seems logical to me to see if someone knows before going through all the trouble again.
    Thank you for any advice on this matter.
    ***I just found this:
    http://www.x.org/wiki/RadeonFeature
    It doesn't list "RS690M" (M is for 'Mobility'?). Any idea if "RS690" or "RS690 (RHD)" is referring to my card?
    If mine is just the "RS690" then I 'may' be in luck. But if it's the "RS690 (RHD)" then it looks as though I'm out of luck for S-Video out support.
    Last edited by The Avatar of Time (2009-10-21 09:34:50)

    rogorido wrote:
    The Avatar of Time wrote:
    Hello All,
    I'm trying to find out whether or not the open source drivers will now detect and support the S-Video out (it's been quite a while since I last tried Arch on it). Or alternatively if proprietary support has returned, I had heard talk of that happening a while back (via a legacy driver), but to my knowledge there's still no way to use the proprietary driver on Arch. Is this correct?
    I have the same card. As far as I know, there is no prop support coming back. You have to use the free driver, which is getting better and better.
    Sorry, but I have no experience wt S-output...
    Thanks for the reply. You're card doesn't have an S-Video out on it?
    If you do have a port, could you run this in terminal:
    xrandr
    And post the results? Thanks. If not, that's anyway for the reply.
    Before when I tried the open source drivers 'xrandr' wouldn't detect a port at all.
    Last edited by The Avatar of Time (2009-10-21 23:41:35)

  • ATI Radeon drivers problems (both open-source and proprietary)

    Hi 2 All!!
    I have a problem with my ATI Radeon 9000-series. The open source drivers (xf86-video-ati) don't work very good for me, my monitor's fresh rate isn't "at-top" and the monitor projection is slightly translated to the right (say 8-12 pixels). So I've tried to build the official drivers with ABS, all is gone successfully, except for some worrying warnings, but I thought that it's normal. I have a customized kernel, build through ABS... So, when I've tried to load the fglrx module it says:
    # modprobe fglrx
    FATAL: Error inserting fglrx (/lib/modules/2.6.27-ARCH/video/fglrx.ko): Cannot allocate memory
    Please, help me! My machine is slow, I can't run any OpenGL-accelerated application, even Quake III!!! If you can suggest me how to improve the performance and how to resolve problems with open-source drivers, it also would be very good... Thank you and sorry for my poor English please.

    I had some problems with installing ATI drivers recently (could not build fglrx module, not even manually, I had to change some installation script), but with latest driver version (8.11 I think) from ati.amd.com was everything fine (I have Radeon 9600 Pro)
    Try to do this (and write here the output)
    glxinfo | grep vendor
    fglrxinfo
    In both cases, it should write something like OpenGL...: ATI... if there will be MESA or DRI, that means that you don't have loaded your fglrx module.
    If fglrxinfo output will be something like: no permission for...(should be first or second line of the output), then write this somewhere in your xorg.conf:
       Section "DRI"
           Mode 0666
       EndSection
    run:
    modprobe -a fglrx - and give here the output. If there will be none, run:
    lsmod | grep fglrx - to see wheter fglrx module is really loaded in kernel
    if you will have no module, you can install one, type:
    cd /lib/modules/fglrx/build_mod
    sh make.sh
    cd ../
    sh make_install.sh (as root)
    and post any warning or error here at forum, drivers (but not fglrx module) are installed at /usr/share/ati
    After installing drivers, you also need to configure your system (notice your system that it's there), commands:
    aticonfig --initial (for editing your xorg.conf)
    aticonfig --overlay-type=Xv (acceleration support in xorg.conf)
    Showing your xorg.conf file here is also good idea, here is mine (sections Device and Screen):
    Section "Device"
        #VideoRam    262144
        # Insert Clocks lines here if appropriate
        Identifier  "** ATI Radeon (generic)               [radeon]"
        Driver      "radeon"
    EndSection
    Section "Device"
        Identifier  "aticonfig-Device[0]-0"
        Driver      "fglrx"
        Option        "VideoOverlay" "on"
        Option        "OpenGLOverlay" "off"
        BusID       "PCI:1:0:0"
    EndSection
    Section "Screen"
        Identifier "Screen 1"
        Device     "** ATI Radeon (generic)               [radeon]"
        Monitor    "My Monitor"
        DefaultDepth     24
        SubSection "Display"
            Viewport   0 0
            Depth     8
            Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
            Viewport   0 0
            Depth     16
            Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
            Viewport   0 0
            Depth     24
            Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
    EndSection
    Section "Screen"
        Identifier "aticonfig-Screen[0]-0"
        Device     "aticonfig-Device[0]-0"
        Monitor    "aticonfig-Monitor[0]-0"
        DefaultDepth     24
        SubSection "Display"
            Viewport   0 0
            Depth     24
        EndSubSection
    EndSection

  • A plea to Adobe: Make Homesite open source

    I know this won't go anywhere, but I need to ask anyway.
    Please please please, make Homesite open source.
    I have tried other editors over the years but I come back to
    HS every time. Macromedia ignored Homesite when they bought
    Allaire, now Adobe is ignoring it after buying Macromedia. Homesite
    is a wonderful code editor, but it needs some tender loving care
    after being ignored for years.
    Keep it commercial, it doesn't have to be free. But please,
    open up the source. Let the few of us that still use it make it
    better.
    Steve Nelson

    I just love seeing replies here!
    I finally broke down and got CS4  and included Dreamweaver based on user groups saying in code view it is *almost* like Homesite.
    argh... the ambiguity of *almost*...
    a horse is almost like a giraffe...
    I still have homesite installed... there is NOTHING like HOMESITE!
    Hand coders do not want all the bells and whistles of Dreamweaver!!!!!
    Hey maybe APPLE would buy it!
    I don't think it ever worked on MAC but maybe they could make a cross platform and make it run on both!
    OPENSOURCE would be really awesome though!
    Anybody know anyone at Cisco?  now that they have openoffice maybe they would like to fund Homesite!
    Homesite to me is the OpenOffice of the web dev world.
    OR maybe the folks that have CSE Validator...

  • How to make Open Source work on Solaris 10, x86 ?

    I'm trying to make this Open Source code for MDBTools work on my
    Solaris 10, x86.
    What this tool does is to read in a Microsoft Access MDB file, and
    outputs the contents of that database file, into an ASCII text file.
    I unzipped these files already, but how do I make "mdbtools" work on
    Solaris x86, version 10?
    http://sourceforge.net/search/?type_of_search=soft&words=mdbtools
    http://sourceforge.net/projects/mdbtools/files/mdbtools/mdbtools-0.6pre1.tar.gz/download

    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking dlfcn.h usability... yes
    checking dlfcn.h presence... yes
    checking for dlfcn.h... yes
    checking for g++... no
    checking for c++... no
    checking for gpp... no
    checking for aCC... no
    checking for CC... no
    checking for cxx... no
    checking for cc++... no
    checking for cl... no
    checking for FCC... no
    checking for KCC... no
    checking for RCC... no
    checking for xlC_r... no
    checking for xlC... no
    checking whether we are using the GNU C++ compiler... no
    checking whether g++ accepts -g... no
    checking dependency style of g++... none
    checking how to run the C++ preprocessor... /lib/cpp
    checking for g77... no
    checking for f77... no
    checking for xlf... no
    checking for frt... no
    checking for pgf77... no
    checking for fl32... no
    checking for af77... no
    checking for fort77... no
    checking for f90... no
    checking for xlf90... no
    checking for pgf90... no
    checking for epcf90... no
    checking for f95... no
    checking for fort... no
    checking for xlf95... no
    checking for lf95... no
    checking for g95... no
    checking whether we are using the GNU Fortran 77 compiler... no
    checking whether accepts -g... no
    checking the maximum length of command line arguments... 262144
    checking command to parse /usr/ccs/bin/nm -p output from gcc object... ok
    checking for objdir... .libs
    checking for ar... false
    checking for ranlib... :
    checking for strip... :
    checking if gcc static flag works... yes
    checking if gcc supports -fno-rtti -fno-exceptions... no
    checking for gcc option to produce PIC... -fPIC
    checking if gcc PIC flag -fPIC works... yes
    checking if gcc supports -c -o file.o... yes
    checking whether the gcc linker (/usr/ccs/bin/ld) supports shared libraries... yes
    checking whether -lc should be explicitly linked in... yes
    checking dynamic linker characteristics... solaris2.10 ld.so
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... no
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... yes
    configure: creating libtool
    appending configuration tag "CXX" to libtool
    checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries... yes
    libtool.m4: error: problem compiling CXX test program
    checking for g++ option to produce PIC...
    checking if g++ supports -c -o file.o... no
    checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries... yes
    checking dynamic linker characteristics... solaris2.10 ld.so
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... no
    appending configuration tag "F77" to libtool
    checking for flex... no
    checking for lex... no
    checking for yywrap in -lfl... no
    checking for yywrap in -ll... yes
    checking for bison... no
    checking for byacc... no
    checking for ANSI C header files... (cached) yes
    checking fcntl.h usability... yes
    checking fcntl.h presence... yes
    checking for fcntl.h... yes
    checking limits.h usability... yes
    checking limits.h presence... yes
    checking for limits.h... yes
    checking for unistd.h... (cached) yes
    checking wordexp.h usability... yes
    checking wordexp.h presence... yes
    checking for wordexp.h... yes
    checking for an ANSI C-conforming const... yes
    checking for size_t... yes
    checking whether byte ordering is bigendian... no
    checking Are we using flex ... yes
    checking for SQLGetPrivateProfileString in -lodbcinst... no
    checking for pkg-config... /usr/bin/pkg-config
    checking for GLIB - version >= 2.0.0... yes (version 2.4.1)
    checking for libglade-2.0 libgnomeui-2.0... yes
    checking GNOME_CFLAGS... -DORBIT2=1 -mt -I/usr/include/libglade-2.0 -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/openwin/include -I/usr/sfw/include -I/usr/sfw/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libgnomeui-2.0 -I/usr/include/libgnome-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libart-2.0 -I/usr/include/gconf/2 -I/usr/include/libbonoboui-2.0 -I/usr/include/orbit-2.0 -I/usr/include/libbonobo-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/bonobo-activation-2.0
    checking GNOME_LIBS... -mt -lglade-2.0 -lgnomeui-2 -lSM -lICE -lbonoboui-2 -lxml2 -lpthread -lz -lgnomecanvas-2 -lgnome-2 -lpopt -lart_lgpl_2 -lpangoft2-1.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lmlib -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lbonobo-2 -lgconf-2 -lgnomevfs-2 -lbonobo-activation -lORBit-2 -lgobject-2.0 -lresolv -lnsl -lsocket -lm -lgmodule-2.0 -lgthread-2.0 -lglib-2.0
    checking gtk-doc version >= 1.0... yes
    checking for initscr in -lncurses... no
    checking for add_history in -lreadline... no
    configure: creating ./config.status
    config.status: creating src/Makefile
    config.status: creating libmdb.pc
    config.status: creating libmdbsql.pc
    config.status: creating src/util/Makefile
    config.status: creating src/extras/Makefile
    config.status: creating Makefile
    config.status: creating include/Makefile
    config.status: creating src/libmdb/Makefile
    config.status: creating src/sql/Makefile
    config.status: creating src/odbc/Makefile
    config.status: creating doc/Makefile
    config.status: creating src/gmdb2/Makefile
    config.status: creating src/gmdb2/gladefiles/Makefile
    config.status: creating src/gmdb2/pixmaps/Makefile
    config.status: creating src/gmdb2/help/Makefile
    config.status: creating src/gmdb2/help/C/Makefile
    config.status: creating mdbtools.spec
    config.status: creating include/mdbver.h
    config.status: creating include/config.h
    config.status: include/config.h is unchanged
    config.status: executing depfiles commands
    @

  • Mass Storage Drivers to save Zen Nano Plus...[HALLELUJAH SOLVEDDDD!

    Okay, my Zen Nano Plus was working fine until about two days ago, when it just started shutting off. The battery was full, and I switched batteries three times, but it still wouldn't stay on. I looked through the forums, and there was advice to update the firmware. [I had ..0] I downloaded it [.3.03], and ran it, but then it said that it couldn't find the hardware for the software [or the software for teh hardware?] and I didn't know what to do, but the computer [or whatever] decided to disconnect the Nano from the comp, so there was no firmware on the player at all. And now it won't turn on.
    So I looked on the forums for THAT, and it was advised to download the Mass Storage Drivers, so I did. Only I don't know if I'm supposed to double click the icon and execute the program before I do the whole "push play before connecting the player to yor computer and continue holding play for ten seconds" thing, but I did, and I don't know if I was supposed to do, and somebody please help meh because I love my Zen and if he dies I am going to die as well. And be really bored during my classes.
    Also, I am running on Windows ME.Message Edited by rubyandrest on 0-29-200708:4 PM

    Dude...i have been a loyal customer of creative for years....i just updated my firmware on my nano plus and my zen shut down....no reset...nothing. i sent an email and i recieved a generic email about paying for contact help. they have lost a loyal customer and i am telling all of my friends to never buy a creative product. mine was fine and then i saw a firmware upgrade and thought, "wow, this would be great". then after installing it is useless. no help from creative at all. i have always had soundblaster cards and creative speaker systems so i figured id get their mp3 player...now i will never patronize their company again. go get an ipod. i am on payday! they will probably delete this post and deny me access to the site after this, but i am a marketing management major and this is a big No No for companies that wish to stay around. Creative will be gone in a few years if this is the service they offer.

  • Make Onlocation open source.... PLEASE!!!

    Since the engineers at adobe are clueless in regards to the possibilities of onlocation, I think they would be well served to release the source code for onlocation and make it open source.

    too many police and government agencies are using it and I doubt BlackBerry will ever make it open source
    Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
    Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
    Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
    BESAdmin's, please make a signature with your BES environment info.
    SIM Free BlackBerry Unlocking FAQ
    Follow me on Twitter @knottyrope
    Want to thank me? Buy my KnottyRope App here
    BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

Maybe you are looking for