How to determine active DMA issue? - Mandriva

This is a discussion on How to determine active DMA issue? - Mandriva ; Hi, Newly interested in Linux, I have Mandriva 2006 installed using with Creative Infra CD-ROM which is great for audio playing. However the problem is that: If i play audio CD through Amarok or KsCD which came with Mandriva 2006, ...

+ Reply to Thread
Results 1 to 19 of 19

Thread: How to determine active DMA issue?

  1. How to determine active DMA issue?

    Hi,
    Newly interested in Linux, I have Mandriva 2006 installed using with
    Creative Infra CD-ROM which is great for audio playing. However the
    problem is that: If i play audio CD through Amarok or KsCD which came
    with Mandriva 2006, the sound
    is distorted and skipping occurs, the audio playing method seems to be
    done with audio extraction or buffering method. Because drive's
    activity LED is not steady, it flashes due to a kind of extraction. If
    i play audio CD
    directly on my Creative Infra's built-in buttons, no problem occurs,
    activity LED is steady as it should be when playing an audio through
    audio channel.

    Also, if i play files through my harddrive no major problems occur
    during playback.

    So, i suspected if Linux distros runs on the same UDMA level which are
    set inside BIOS or how can i determine in which DMA level my CD-ROM
    runs on Linux operation?

    There were some diagnostic tools for Windows don't know for Linux.

    Note: I have audio cable plugged on sound card and the cd-rom. No
    problem in Windows.

    Thanks

  2. Re: How to determine active DMA issue?

    On Sun, 13 Jan 2008 03:45:58 -0800 (PST), kimiraikkonen wrote:
    > Hi,
    > Newly interested in Linux, I have Mandriva 2006 installed using with


    Yeouch, missing a ton of security updates there.
    http://www.mandriva.com/en/security/...ies?dis=2007.0
    http://www.mandriva.com/en/security/...ies?dis=2007.1
    http://www.mandriva.com/en/security/...ies?dis=2008.0


    > So, i suspected if Linux distros runs on the same UDMA level which are
    > set inside BIOS or how can i determine in which DMA level my CD-ROM
    > runs on Linux operation?


    You can use hardparm to get parameters

    man hardparm


  3. Re: How to determine active DMA issue?

    On Jan 13, 3:16 pm, Bit Twister wrote:
    > On Sun, 13 Jan 2008 03:45:58 -0800 (PST), kimiraikkonen wrote:
    > > Hi,
    > > Newly interested in Linux, I have Mandriva 2006 installed using with

    >
    > Yeouch, missing a ton of security updates there.http://www.mandriva.com/en/security/...ies?dis=2008.0
    >
    > > So, i suspected if Linux distros runs on the same UDMA level which are
    > > set inside BIOS or how can i determine in which DMA level my CD-ROM
    > > runs on Linux operation?

    >
    > You can use hardparm to get parameters
    >
    > man hardparm


    What's the relationship between an CD-ROM and security updates you've
    mentioned?

  4. Re: How to determine active DMA issue?

    On Sun, 13 Jan 2008 05:19:02 -0800 (PST), kimiraikkonen wrote:
    >
    > What's the relationship between an CD-ROM and security updates you've
    > mentioned?


    I was trying to show you the security fixes since 2006's release.
    2006 is kinda like running Win95

    PS: Do not try to upgrade 2006. Do a format/clean install if you ever
    get around to it.

    I keep spare ~12 gig partitions around so I can install new
    releases. That way I can boot either one until I get the new
    install like I want it. The old partition becomes the next
    installs's partition

  5. Re: How to determine active DMA issue?

    On Jan 13, 3:16 pm, Bit Twister wrote:
    > On Sun, 13 Jan 2008 03:45:58 -0800 (PST), kimiraikkonen wrote:
    > > Hi,
    > > Newly interested in Linux, I have Mandriva 2006 installed using with

    >
    > Yeouch, missing a ton of security updates there.http://www.mandriva.com/en/security/...ies?dis=2008.0
    >
    > > So, i suspected if Linux distros runs on the same UDMA level which are
    > > set inside BIOS or how can i determine in which DMA level my CD-ROM
    > > runs on Linux operation?

    >
    > You can use hardparm to get parameters
    >
    > man hardparm


    Plus why do Amarok and especially KsCD access audio with an weird
    method to play audio CD? Why don't they use direct audio channel to
    play audio which provides the cleanest skip-free sound?

    Actually, Mandriva 2006 was provided with my Linux book, and don't
    know if Mandriva 2006 is worse than newers.

    Meanwhile another question comes here:
    I installed Mandriva 2006 onto an old machine as the specs:

    Intel Celeron 400MHZ
    Soyo motherboard
    384MB SD-RAM
    20GB HDD
    32MB Nvidia TNT2 graphic card
    Creative Vibra sound-card
    Creative CD-ROM

    but operation is "extremely" slow. I suspect from KDE 3.4 and GUI
    elements.
    This macine was operating awesome on Windows 98SE, then decided to
    choose a distro for this machine and i heard Linux distros are so
    popular about their speed within resource usages.
    But on this machine Mandriva 2006 is so slow that a right click on
    desktop gives you the context menu after several seconds, applications
    are opened a few minutes lates after you double-click, window
    movements slutters, corrupts as performance + color.

    Isn't Mandriva 2006 right distro for this PC whose specs are listed
    above?

    Thanks!

  6. Re: How to determine active DMA issue?

    On Sun, 13 Jan 2008 05:26:10 -0800 (PST), kimiraikkonen wrote:
    >
    > Plus why do Amarok and especially KsCD access audio with an weird
    > method to play audio CD? Why don't they use direct audio channel to
    > play audio which provides the cleanest skip-free sound?


    Can not help there.

    > Actually, Mandriva 2006 was provided with my Linux book, and don't
    > know if Mandriva 2006 is worse than newers.


    As a rule the new releases have run faster for me.

    > Meanwhile another question comes here:
    > I installed Mandriva 2006 onto an old machine as the specs:
    >
    > Intel Celeron 400MHZ 384MB SD-RAM
    > 32MB Nvidia TNT2 graphic card


    > but operation is "extremely" slow. I suspect from KDE 3.4 and GUI
    > elements.


    kde is heavy, but I have a AMD-K6 450MHZ 256MB and TNT2

    > But on this machine Mandriva 2006 is so slow that a right click on
    > desktop gives you the context menu after several seconds, applications
    > are opened a few minutes lates after you double-click, window
    > movements slutters, corrupts as performance + color.


    Could be several things. tmdns, kerry/beagle search, other kde services
    running,....

    That box happens to be my old firewall box. Just booted and it is
    running 2007.0

    Took about a minute for kde to come up after startx.
    Right click on desktop gets popup in about a second.
    Double clicking my xterm shortcut gets me a working xterm in about 4
    seconds. Trust me I have a lot of .bashrc to run through.


  7. Re: How to determine active DMA issue?

    On Jan 13, 4:23 pm, Bit Twister wrote:
    > On Sun, 13 Jan 2008 05:26:10 -0800 (PST), kimiraikkonen wrote:
    >
    > > Plus why do Amarok and especially KsCD access audio with an weird
    > > method to play audio CD? Why don't they use direct audio channel to
    > > play audio which provides the cleanest skip-free sound?

    >
    > Can not help there.
    >
    > > Actually, Mandriva 2006 was provided with my Linux book, and don't
    > > know if Mandriva 2006 is worse than newers.

    >
    > As a rule the new releases have run faster for me.
    >
    > > Meanwhile another question comes here:
    > > I installed Mandriva 2006 onto an old machine as the specs:

    >
    > > Intel Celeron 400MHZ 384MB SD-RAM
    > > 32MB Nvidia TNT2 graphic card
    > > but operation is "extremely" slow. I suspect from KDE 3.4 and GUI
    > > elements.

    >
    > kde is heavy, but I have a AMD-K6 450MHZ 256MB and TNT2
    >
    > > But on this machine Mandriva 2006 is so slow that a right click on
    > > desktop gives you the context menu after several seconds, applications
    > > are opened a few minutes lates after you double-click, window
    > > movements slutters, corrupts as performance + color.

    >
    > Could be several things. tmdns, kerry/beagle search, other kde services
    > running,....
    >
    > That box happens to be my old firewall box. Just booted and it is
    > running 2007.0
    >
    > Took about a minute for kde to come up after startx.
    > Right click on desktop gets popup in about a second.
    > Double clicking my xterm shortcut gets me a working xterm in about 4
    > seconds. Trust me I have a lot of .bashrc to run through.


    Hi,
    Thanks however mine is lower than you maybe (celeron 400mhz, tnt2
    32mb).

    At which X settings and which distro you run smooth indeed with KDE?
    Please say optimal configuration with a understanding way, i'm newbie
    for Linux :-)

    I really want to choose a correct distro for this system, Mandriva
    2006 is completely a disappoinment for this old system, sorry.

    Thanks for your care.

  8. Re: How to determine active DMA issue?

    kimiraikkonen wrote:
    > So, i suspected if Linux distros runs on the same UDMA level which are
    > set inside BIOS or how can i determine in which DMA level my CD-ROM
    > runs on Linux operation?


    Look at /etc/sysconfig/harddisk. Mandriva by default ships with
    DMA disabled, as there are some chipsets that do not play nicely
    with Linux DMA. Disk read-ahead likewise may or may not be set.
    Modify using an ascii editor (not word processor) and save the
    file harddisk as needed.
    >
    > There were some diagnostic tools for Windows don't know for Linux.


    man hdparm

    Cheers!

    jim b.

    --
    UNIX is not user-unfriendly; it merely
    expects users to be computer-friendly.

  9. Re: How to determine active DMA issue?

    On Sun, 13 Jan 2008 08:11:18 -0800 (PST), kimiraikkonen wrote:

    >
    > At which X settings and which distro you run smooth indeed with KDE?


    Usually 1024x768 15 bit color @72HZ refresh

    > Please say optimal configuration with a understanding way,


    72hz reduces eye strain
    1024x768 because I want room for several terminals.
    15 bit color because not enough video card memory.

    You may want to read http://www.catb.org/~esr/faqs/smart-questions.html
    I do not know what you have your linux setup is or what you want/are
    using it for.

    You will have to bear with me. 2006 is years ago for me.
    I assume you have gone to
    http://easyurpmi.zarb.org/
    picked 2006, main, contrib, updates, plf-free, and plf-nonfree mirrors,
    and have done your updates.

    Just tried to boot 2006 on another system and video card cannot use my
    new LCD size.

    First thing is to get into the KDE Control Center. Under
    KDE Components
    Service Manager
    uncheck all services and stop them
    Session Manager
    set Offer shutdown options
    set Start with an empty session
    set End current session

    File Quit the KDE Control Center

    Now check if right click desktop and/or terminal launch is still slow.

    Still slow, I want you to turn off and disable On Boot some system
    services/daemons which may already be off.

    NOTE: You may not have indicated services installed.
    Some of my suggestions may break what you have running, like network
    file sharing. You can turn each service back on later.

    Click up a terminal
    su - root


    First thing is make a backup copy of what services/daemons are running:
    chkconfig --list > /etc/chkconfig_orig

    Now I am suggesting disabling the following services by running

    mcc

    The you stop the service and Uncheck the On Boot for:
    freshclam
    httpd
    lisa
    mDNSResponder
    mandi
    mysqld
    netfs
    netplugd
    nfs
    nfslock
    nifd
    oki4daemon
    pg_autovacuum
    smb
    vncserver
    webmin

    Click OK
    File Quit


    I would like to see the output from

    cat /etc/hosts
    cat /etc/resolv.conf

  10. Re: How to determine active DMA issue?

    On Jan 13, 7:22*pm, Jim Beard wrote:
    > kimiraikkonen wrote:
    > > So, i suspected if Linux distros runs on the same UDMA level which are
    > > set inside BIOS or how can i determine in which DMA level my CD-ROM
    > > runs on Linux operation?

    >
    > Look at /etc/sysconfig/harddisk. *Mandriva by default ships with
    > DMA disabled, as there are some chipsets that do not play nicely
    > with Linux DMA. *Disk read-ahead likewise may or may not be set.
    > Modify using an ascii editor (not word processor) and save the
    > file harddisk as needed.
    >
    >
    >
    > > There were some diagnostic tools for Windows don't know for Linux.

    >
    > man hdparm
    >
    > Cheers!
    >
    > jim b.
    >
    > --
    > UNIX is not user-unfriendly; it merely
    > * * * expects users to be computer-friendly.


    Jim,
    Thanks for helping, i'm surprised that DMA was disabled by default!
    Wow, i hope you're joking :-) DMA is the most efficent and newest
    technology for modern storage devices, especially for harddrives and
    optical drives. But i don't know if Mandriva has an internal or kernel-
    related problem about enabling DMA. If there's, it's horrible!

    An Audacity article confirms your acknowledgement:
    http://audacityteam.org/wiki/index.php?title=DMA_mode

    ...says DMA is off by default in most of Linux distros. But i'm %100
    sure that this dramatically decreases data transfer performance. And
    says this command enables DMA:

    # hdparm -d1 /dev/hda

    Is it same in Mandriva 2006 or hardparam...?


    Bit Twister,
    Thank you also, my KDE was running on 1024x768@60hz which is my VGA
    +monitor's native/stable resolution, however it was too hard to test
    OK result during setup of Mandriva :-( (Needed to select "Generic" as
    display configuration).

    Do you suggest Mandriva 2008 or 2007 for this old system? (Celeron
    400, 384MB RAM, 32MB TNT2)
    Are you using 2007or 2008 with your old system "smooth" with KDE?
    (yours was Athlon 450, 256MB memory)

    i'll keep in mind your other suggestions.

    Thanks!

  11. Re: How to determine active DMA issue?

    kimiraikkonen wrote:
    > On Jan 13, 7:22 pm, Jim Beard wrote:
    >> kimiraikkonen wrote:
    >>> So, i suspected if Linux distros runs on the same UDMA level which are
    >>> set inside BIOS or how can i determine in which DMA level my CD-ROM
    >>> runs on Linux operation?

    >> Look at /etc/sysconfig/harddisk. Mandriva by default ships with
    >> DMA disabled, as there are some chipsets that do not play nicely
    >> with Linux DMA. Disk read-ahead likewise may or may not be set.
    >> Modify using an ascii editor (not word processor) and save the
    >> file harddisk as needed.
    >>
    >>
    >>
    >>> There were some diagnostic tools for Windows don't know for Linux.

    >> man hdparm
    >>
    >> Cheers!
    >>
    >> jim b.
    >>
    >> --
    >> UNIX is not user-unfriendly; it merely
    >> expects users to be computer-friendly.

    >
    > Jim,
    > Thanks for helping, i'm surprised that DMA was disabled by default!
    > Wow, i hope you're joking :-) DMA is the most efficent and newest
    > technology for modern storage devices, especially for harddrives and
    > optical drives. But i don't know if Mandriva has an internal or kernel-
    > related problem about enabling DMA. If there's, it's horrible!


    There is a DMA problem with a Linux kernel on a very few chipsets.
    Linux puts reliability above speed, and disables DMA to avoid this
    serious problem. As the owner/operator of your system, otherwise
    known as the system administrator, change it.

    > An Audacity article confirms your acknowledgement:
    > http://audacityteam.org/wiki/index.php?title=DMA_mode
    > ...says DMA is off by default in most of Linux distros. But i'm %100
    > sure that this dramatically decreases data transfer performance.


    Correct on both counts. The version of DMA used also has
    an impact.

    And
    > says this command enables DMA:
    > # hdparm -d1 /dev/hda
    > Is it same in Mandriva 2006 or hardparam...?
    >

    In a terminal window, run the command
    man hdparm
    as I suggested in my earlier post. This will
    bring up the manual page for the command hdparm.
    Read and learn.

    Cheers!

    jim b.


    --
    UNIX is not user-unfriendly; it merely
    expects users to be computer-friendly.

  12. Re: How to determine active DMA issue?

    On Sun, 13 Jan 2008 10:20:39 -0800 (PST), kimiraikkonen wrote:

    > Thank you also, my KDE was running on 1024x768@60hz which is my VGA
    > +monitor's native/stable resolution, however it was too hard to test
    > OK result during setup of Mandriva :-( (Needed to select "Generic" as
    > display configuration).


    Another post to another thread jogged my memory.
    Under KDE sound system, I have set auto suspend after 2 seconds.
    And disabled all System/window sound events.


    > Do you suggest Mandriva 2008 or 2007 for this old system? (Celeron
    > 400, 384MB RAM, 32MB TNT2)


    I am not happy at all with my ATI Radeon Xpress 200G video driver
    on 2008.

    > Are you using 2007or 2008 with your old system "smooth" with KDE?
    > (yours was Athlon 450, 256MB memory)


    2007.0 on the AMD-K6 450, 256MB, tnt2 (32m). I have been looking around for my
    2007.1 cds to see how it would look.
    Looks like I would have to download the 3 cds again.

    Video is not clean on my LCD display driven from that old system.
    No idea if it is 2007.0 or what.

    If I recall correctly, 2007.0 was a bit more buggy than 2007.1

  13. Re: How to determine active DMA issue?

    On Sun, 13 Jan 2008 17:39:22 +0000, Bit Twister wrote:

    > On Sun, 13 Jan 2008 08:11:18 -0800 (PST), kimiraikkonen wrote:
    >
    >
    >> At which X settings and which distro you run smooth indeed with KDE?

    >
    > Usually 1024x768 15 bit color @72HZ refresh
    >
    >> Please say optimal configuration with a understanding way,

    >
    > 72hz reduces eye strain


    Quite a lot of people are now using LCD panels, which renders that
    requirement moot.

    On a CRT, I get headaches unless the refresh is at least 85 Hz.

    > 1024x768 because I want room for several terminals. 15 bit color because
    > not enough video card memory.


    I doubt that you notice the absence of any colours unless you do a side-
    by-side comparison :-)

  14. Re: How to determine active DMA issue?

    kimiraikkonen writes:

    >On Jan 13, 7:22=A0pm, Jim Beard wrote:
    >> kimiraikkonen wrote:
    >> > So, i suspected if Linux distros runs on the same UDMA level which are
    >> > set inside BIOS or how can i determine in which DMA level my CD-ROM
    >> > runs on Linux operation?

    >>
    >> Look at /etc/sysconfig/harddisk. =A0Mandriva by default ships with
    >> DMA disabled, as there are some chipsets that do not play nicely
    >> with Linux DMA. =A0Disk read-ahead likewise may or may not be set.
    >> Modify using an ascii editor (not word processor) and save the
    >> file harddisk as needed.
    >>
    >>
    >>
    >> > There were some diagnostic tools for Windows don't know for Linux.

    >>
    >> man hdparm
    >>
    >> Cheers!
    >>
    >> jim b.
    >>
    >> --
    >> UNIX is not user-unfriendly; it merely
    >> =A0 =A0 =A0 expects users to be computer-friendly.


    >Jim,
    >Thanks for helping, i'm surprised that DMA was disabled by default!
    >Wow, i hope you're joking :-) DMA is the most efficent and newest
    >technology for modern storage devices, especially for harddrives and
    >optical drives. But i don't know if Mandriva has an internal or kernel-
    >related problem about enabling DMA. If there's, it's horrible!


    NO. Some CD manufacturers do not know about standards, and screw up their
    implimentations. So to play safe...
    Anyway go switch it on.

    >An Audacity article confirms your acknowledgement:
    >http://audacityteam.org/wiki/index.php?title=3DDMA_mode


    >=2E..says DMA is off by default in most of Linux distros. But i'm %100
    >sure that this dramatically decreases data transfer performance. And
    >says this command enables DMA:


    ># hdparm -d1 /dev/hda


    >Is it same in Mandriva 2006 or hardparam...?


    hardparam was his very bad memory playing tricks on him. It is hdparm.




    >Bit Twister,
    >Thank you also, my KDE was running on 1024x768@60hz which is my VGA
    >+monitor's native/stable resolution, however it was too hard to test
    >OK result during setup of Mandriva :-( (Needed to select "Generic" as
    >display configuration).


    >Do you suggest Mandriva 2008 or 2007 for this old system? (Celeron
    >400, 384MB RAM, 32MB TNT2)
    >Are you using 2007or 2008 with your old system "smooth" with KDE?
    >(yours was Athlon 450, 256MB memory)


    >i'll keep in mind your other suggestions.


    >Thanks!


  15. Re: How to determine active DMA issue?

    On 13 Jan 2008 20:01:05 +0100, Mark South wrote:
    >
    > On a CRT, I get headaches unless the refresh is at least 85 Hz.


    Yep, I hate 60hz on a crt. To much flicker for me. I set several peoples
    crt to 72 or higher where hardware/monitor supported it at work.

    A few of those people told me they no longer had the headache at the
    end of day.

  16. Re: How to determine active DMA issue?



    > hardparam was his very bad memory playing tricks on him. It is hdparm.


    Unruh,

    i just wanted ask correct command because Bit Twister's reply to my
    first post as follows:

    "You can use hardparm to get parameters"

    man hardparm

    and correct one is "hdparm" i suppose.

    That's all.

    Meanwhile, Refresh rates above 60hz (85 or 72) may be sufficent for
    high-res monitors such as 17 or 19 inches, but my monitor only handles
    60hz at 1024x768 which is an very old CRT, will have a look for a
    replacement with a LCD one.

    And i hope to see an smooth Mandriva distro for the old PC mentioned
    above.

    Thanks.

  17. Re: How to determine active DMA issue?

    On Sun, 13 Jan 2008 12:52:01 -0800 (PST), kimiraikkonen wrote:
    >
    > and correct one is "hdparm" i suppose.


    Yes, my fault, brain was using hard drive parameters and got in the
    way of typing.

    > And i hope to see an smooth Mandriva distro for the old PC mentioned
    > above.


    Downloading 2007.1 to see how well it works on old hardware.
    Would have been done but ran of out space. So getting it again.

  18. Re: How to determine active DMA issue?

    On Sun, 13 Jan 2008 05:26:10 -0800, kimiraikkonen wrote:

    > Plus why do Amarok and especially KsCD access audio with an weird method
    > to play audio CD? Why don't they use direct audio channel to play audio
    > which provides the cleanest skip-free sound?
    >

    I don't listen cd's on my PC and never ran amarok, but to check the drives
    dma usage is simple with hdparm.
    [root@wes2 wes]# hdparm -id /dev/hdc

    /dev/hdc:
    using_dma = 1 (on)

    Model=_NEC DVD_RW ND-3550A, FwRev=1.05, SerialNo=
    Config={ Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
    RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
    BuffType=unknown, BuffSize=0kB, MaxMultSect=0
    (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
    IORDY=yes, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
    PIO modes: pio0 pio1 pio2 pio3 pio4
    DMA modes: mdma0 mdma1 mdma2
    UDMA modes: udma0 udma1 *udma2
    AdvancedPM=no

    * signifies the current active mode

    [root@wes2 wes]#

    > Meanwhile another question comes here: I installed Mandriva 2006 onto an
    > old machine as the specs:
    >
    > Intel Celeron 400MHZ
    > Soyo motherboard
    > 384MB SD-RAM
    > 20GB HDD
    > 32MB Nvidia TNT2 graphic card
    > Creative Vibra sound-card
    > Creative CD-ROM
    >
    > but operation is "extremely" slow. I suspect from KDE 3.4 and GUI
    > elements.


    Kde is slow. Whay do you need to use it? Try IceWM or one of the other
    lean window managers.

    > This macine was operating awesome on Windows 98SE, then decided to
    > choose a distro for this machine and i heard Linux distros are so
    > popular about their speed within resource usages. But on this machine
    > Mandriva 2006 is so slow that a right click on desktop gives you the
    > context menu after several seconds, applications are opened a few
    > minutes lates after you double-click, window movements slutters,
    > corrupts as performance + color.


    Try loading Win XP on that machine and see how it performs. W98 is
    extremely old and only required 16M ram. All newer OS's require 64M or
    more to run the same as W98 did on 16M. And with only 16M of W98 was slow
    to. Why? Because it has to continually swap it. If you want to speed that
    machine up go back to Mandrake 8.2 (which is still a lot newer than W98)
    and don't run KDE.
    >
    > Isn't Mandriva 2006 right distro for this PC whose specs are listed
    > above?
    >

    Was that hardware circa 2006? I don't think so.More like 1998 or earlier.
    Which is why W98 runs so well on it. If you want to run a current OS, it's
    best to have somewhat current hardware. Also, you need to install the
    legacy nvdia driver if they still have it on their website. That TNT card
    is really old. Would help to run it in lower res and less colors too.

    --
    Want the ultimate in free OTA SD/HDTV Recorder? http://mythtv.org
    My Tivo Experience http://wesnewell.no-ip.com/tivo.htm
    Tivo HD/S3 compared http://wesnewell.no-ip.com/mythtivo.htm
    AMD cpu help http://wesnewell.no-ip.com/cpu.php

  19. Re: How to determine active DMA issue?

    On Sun, 13 Jan 2008 21:03:26 +0000 (UTC), Bit Twister wrote:
    >
    > Downloading 2007.1 to see how well it works on old hardware.
    > Would have been done but ran of out space. So getting it again.


    Ok, 2008.0 would not install. could be 256m memory not enough.
    Tried 2007.1 it crashed.
    Appears the hardware gave up. cdrom no longer works.

    I suggest we tinker with your 2006 settings to see if we can get to
    the bottom of your speed problem.

+ Reply to Thread