Cannot connect TRF error

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • NE5
    Junior Member
    Junior Member
    • Aug 2006
    • 11

    Cannot connect TRF error

    Apologies if this is in the wrong section

    I've just bought a new DVD writer, my other one was broken, or stopped burning DVD's.

    Anyway I'm running it with the version of nero and after reading the files and backing them up, using DVD Shrink, when it gets to the burn stage, I am getting a message which says cannot connect TRF

    I have the full message pasted if it needs to be posted ? It appears to include an intialising code.

    Should I use my older version of nero with DVD Shrink ?
  • locoeng
    Who Farted?
    • Dec 2005
    • 2509

    #2
    Why not use Recode if you have Nero? It is slightly faster than the program you are using and will also autoburn when the compression is complete.


    "I refuse to have a battle of wits with an unarmed person. It's not fair to you and no challenge for us."
    Walt Kelly

    Comment

    • NE5
      Junior Member
      Junior Member
      • Aug 2006
      • 11

      #3
      what is recode ?

      Comment

      • locoeng
        Who Farted?
        • Dec 2005
        • 2509

        #4
        It is a compression tool much like what you are already using, but it is usually bundled with Nero or can be downloaded separately if the OEM version doesn't contain it.



        "I refuse to have a battle of wits with an unarmed person. It's not fair to you and no challenge for us."
        Walt Kelly

        Comment

        • NE5
          Junior Member
          Junior Member
          • Aug 2006
          • 11

          #5
          here is the error log


          1A20-920E-0012-2525-1282-4753*
          <?xml:namespace prefix = o ns = "urn:schemas-microsoft-comfficeffice" /><o></o>
          Windows XP 5.1
          IA32
          WinAspi: File 'Wnaspi32.dll': Ver=4.71 (0002), size=45056 bytes, created 21/11/2005 06:48:21
          ahead WinASPI: File 'C:\Program Files\Ahead\Nero\Wnaspi32.dll': Ver=2.0.1.74, size=164112 bytes, created 02/11/2006 07:55:36
          <o></o>
          NT-SPTI used
          Nero API version: 6.6.1.6
          Using interface version: 6.3.1.4
          Installed in: C:\Program Files\Ahead\Nero\
          Application: ahead\Nero - Burning Rom
          Internal Version: 6, 6, 1, 6
          <o></o>
          Recorder: <HL-DT-ST DVDRAM GSA-H42L>Version: SL00 - HA 1 TA 0 - 6.6.1.6
          Adapter driver: <IDE> HA 1
          Drive buffer : 2048kB
          Bus Type : default (0) -> ATAPI, detected: ?
          <o></o>
          === Scsi-Device-Map ===
          DiskPeripheral : ExcelStor Technology J680 atapi Port 0 ID 0 DMA: On
          CdRomPeripheral : HL-DT-ST DVDRAM GSA-H42L atapi Port 1 ID 0 DMA: On
          CdRomPeripheral : HL-DT-ST CD-RW GCE-8525B atapi Port 1 ID 1 DMA: On
          <o></o>
          === CDRom-Device-Map ===
          HL-DT-ST DVDRAM GSA-H42L E: CDRom0
          HL-DT-ST CD-RW GCE-8525B F: CDRom1
          =======================
          <o></o>
          AutoRun : 1
          Excluded drive IDs:
          WriteBufferSize: 40894464 (0) Byte
          ShowDrvBufStat : 0
          BUFE : 0
          Physical memory : 255MB (261616kB)
          Free physical memory: 129MB (132500kB)
          Memory in use : 49 %
          Uncached PFiles: 0x0
          Use Inquiry : 1
          Global Bus Type: default (0)
          Check supported media : Disabled (0)
          <o></o>
          19.6.2007
          NeroAPI
          15:54:38 #1 Phase 112 File APIProgress.cpp, Line 275
          DVD-Video files reallocation started

          15:54:39 #2 Phase 114 File APIProgress.cpp, Line 275
          DVD-Video files reallocation completed (no file modified)

          15:54:39 #3 Phase 111 File APIProgress.cpp, Line 275
          DVD-Video files sorted

          15:54:39 #4 NEROAPI 7 File Burncd.cpp, Line 3095
          Error:\nCannot connect TRF.

          15:54:39 #5 Text 0 File AudioCompilationImpl.cpp, Line 867
          DRM: DRM burn session terminated.

          15:54:39 #6 Text 0 File AudioCompilationImpl.cpp, Line 896
          DRM: Closing entire DRM handling. Bye.

          <o></o>
          Existing drivers:
          File 'Drivers\CDRALW2K.SYS': Ver=5.3.5.10, size=23436 bytes, created 15/08/2005 13:07:36
          File 'Drivers\ASPI32.SYS': Ver=4.71 (0002) built by: WinDDK, size=16512 bytes, created 21/11/2005 06:48:21
          <o></o>
          Registry Keys:
          HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)
          <o></o>

          Comment

          • locoeng
            Who Farted?
            • Dec 2005
            • 2509

            #6
            Google this... "Cannot connect TRF"

            I/we cannot help you with this error here, that is why I was trying to suggest Recode...good luck.


            "I refuse to have a battle of wits with an unarmed person. It's not fair to you and no challenge for us."
            Walt Kelly

            Comment

            • NE5
              Junior Member
              Junior Member
              • Aug 2006
              • 11

              #7
              thank you, I understand now.

              Do you also think that imageburn is better as the brand new software on the block etc etc ?

              Comment

              • locoeng
                Who Farted?
                • Dec 2005
                • 2509

                #8
                Yes I do....it is my burn engine of choice.

                I can also tell you that your firmware is one revision behind...current version is SL01 and can be found here:



                "I refuse to have a battle of wits with an unarmed person. It's not fair to you and no challenge for us."
                Walt Kelly

                Comment

                • Chewy
                  Super Moderator
                  • Nov 2003
                  • 18971

                  #9
                  that looks like 1st gen firmware, might want to update


                  good lean setup for 256 megs of ram(pass the robitussin loco)

                  imgburn would a better choice for an older computer w/o a lot of ram

                  Comment

                  • locoeng
                    Who Farted?
                    • Dec 2005
                    • 2509

                    #10
                    good lean setup for 256 megs of ram(pass the robitussin loco)
                    I could only hope for lean and mean...


                    "I refuse to have a battle of wits with an unarmed person. It's not fair to you and no challenge for us."
                    Walt Kelly

                    Comment

                    • NE5
                      Junior Member
                      Junior Member
                      • Aug 2006
                      • 11

                      #11
                      I did what you said, and found a solution here, which seems to have done the trick



                      Thank you for the help ... I would have used the imageburn if I hadn't found anything.

                      As it happens, as you keep reading that firmware can damage your hardware, is this true ?

                      The reason for my problem that I have just wrestled with, is because I had a DVD writer that I think either stopped writing films due to wear and tear, or a firmwared upgrade ruined it ?

                      So, I was setting up my new one.

                      Comment

                      • locoeng
                        Who Farted?
                        • Dec 2005
                        • 2509

                        #12
                        As it happens, as you keep reading that firmware can damage your hardware, is this true ?
                        Applying firmware is called "flashing"...a bad flash can ruin (fry) a drive. In most instances the downloaded firmware comes with a readme.txt that contains instructions on how to flash the drive. These instructions need to be followed to the letter to avoid ruining the drive. Not to scare you away from doing this because it is really easy to do...the firmware update was just an observation and this is one of those "if it ain't broke, don't fix it" type of deals. If you experience problems in the future this may be your only recourse...just something to think about.

                        is because I had a DVD writer that I think either stopped writing films due to wear and tear, or a firmwared upgrade ruined it ?
                        Neither...reread the thread in your link.


                        "I refuse to have a battle of wits with an unarmed person. It's not fair to you and no challenge for us."
                        Walt Kelly

                        Comment

                        Working...