title
Products            Buy            Support Forum            Professional            About            Codec Central
 

Rip as one: crash

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Saint Russell

    • Jun 2008
    • 9

    Rip as one: crash

    Because I had installed a trial R12, which I could not evaluate because I intended to use Rip as One nearly exclusively, I could not evaluate R13. So I bought it. I hope I didn't make a mistake by doing that.

    I just tried to rip a CD and I got this dialog:

    Microsoft Visual C++ Runtime Library
    Runtime Error!
    Program: C:\Program Files\Illustrate\dBpoweramp\CDGrab.exe
    abnormal program termination

    I rebooted and tried again. Same result.

    I'm running XP SP2. Very stable.
  • LtData
    dBpoweramp Guru

    • May 2004
    • 8288

    #2
    Re: Rip as one: crash

    What steps are you doing that lead to this crash? Does it happen with multiple CDs or just a few?

    Comment

    • Saint Russell

      • Jun 2008
      • 9

      #3
      Re: Rip as one: crash

      Originally posted by LtData
      What steps are you doing that lead to this crash? Does it happen with multiple CDs or just a few?
      Procedure:

      Start CD Ripper
      Insert CD and wait for it to be read
      Click "Rip as 1"
      Click "OK"
      Click "Rip"
      CD ripping begins, gets to "Rip Status: Pass 1 Ripping 99%"

      First CD: Visual C++ Runtime error as noted above
      Second CD: ditto
      Third CD: CD Ripper terminated, Windows reported "Virtual memory minimum too low" in taskbar

      Adjusted virtual memory settings
      Old: 384 minimum, 768 maximum
      New: 1024 mininum, 1024 maximum

      Fourth CD: Both errors appear (Visual C++ Runtime and "Virtual memory minimum too low")

      I rebooted before each attempt.

      This is a P4 2.4 GHz with 512MB RAM.

      Comment

      • bhoar
        dBpoweramp Guru

        • Sep 2006
        • 1173

        #4
        Re: Rip as one: crash

        512MB? Ouch. Burst or Secure ripping?

        I'd double the VM, but I'd also suggest at least 1GB of RAM, preferably 2GB for Rip As One.

        -brendan

        Comment

        • Spoon
          Administrator
          • Apr 2002
          • 44506

          #5
          Re: Rip as one: crash

          Secure mode is not recommended for rip as one with less than 2GB + 2GB of virtual memory.
          Spoon
          www.dbpoweramp.com

          Comment

          • Saint Russell

            • Jun 2008
            • 9

            #6
            Re: Rip as one: crash

            Originally posted by Spoon
            Secure mode is not recommended for rip as one with less than 2GB + 2GB of virtual memory.
            Thanks, that's useful information that somehow I missed learning about before purchase. Where are the system requirements/recommendations?

            Comment

            • Spoon
              Administrator
              • Apr 2002
              • 44506

              #7
              Re: Rip as one: crash

              Depends on what options you confgure, for example if you use rip as one with a minimum of 10 passess then you could need 6GB of memory (virtual), that is why there is a memory warning on the rip as one page.
              Spoon
              www.dbpoweramp.com

              Comment

              • Saint Russell

                • Jun 2008
                • 9

                #8
                Re: Rip as one: crash

                Originally posted by Spoon
                Depends on what options you confgure, for example if you use rip as one with a minimum of 10 passess then you could need 6GB of memory (virtual), that is why there is a memory warning on the rip as one page.
                Which I couldn't see until I bought the product, because I installed a trial of R12, from which Rip at One had been removed, and so was barred from evaluating R13, and was not warned by any specification of system requirements that a hardware upgrade would be required. Lesson learned, I suppose.

                Comment

                Working...

                ]]>