Employee of the month; Recode fails to rellocate VTS_11_0.vob

vbimport

#1

This is a Region 1 DVD running AnyDVD 6.1.0.2 Drag and drop files to Hard Drive start Nero Recode all is fine until file reallocation start’s then recive the folowing error:

AutoRun : 1
Excluded drive IDs:
WriteBufferSize: 83886080 (0) Byte
ShowDrvBufStat : 0
BUFE : 0
Physical memory : 2046MB (2095848kB)
Free physical memory: 1435MB (1470036kB)
Memory in use : 29
Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)

11.1.2007

NeroAPI

5:33:13 PM #1 Phase 112 File APIProgress.cpp, Line 275

DVD-Video files reallocation started

5:33:13 PM #2 DVDREALLOC -21 File DVDVideoCompilation.cpp, Line 1198

Required file 'VTS_11_0.VOB' is not present

5:33:13 PM #3 Phase 115 File APIProgress.cpp, Line 275

DVD-Video files reallocation failed

5:33:13 PM #4 Text 0 File NeroAPIBurnFS.cpp, Line 213

Failed to realloc DVD video files

Existing drivers:

File ‘Drivers\CDRALW2K.SYS’: Ver=8.0.0.212 , size=2560 bytes, created 11/3/2005 2:00:00 AM

File ‘Drivers\ASPI32.SYS’: Ver=4.60 (1021), size=25244 bytes, created 9/10/1999 11:06:00 AM

File ‘Drivers\PXHELP20.SYS’: Ver=3.00.33a, size=36528 bytes, created 8/24/2006 7:47:00 PM (Prassi/Veritas driver for win 2K)

Registry Keys:

HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)

17:33:13 File NeroRecorderBase.cpp, Line 906
Burn failed (3)

17:33:13 File burn_dvdfiles.cpp, Line 301
Compile DVD: exit

AnyDVD Status is as follows:

Summary for drive D: (AnyDVD 6.1.0.2)
PIONEER DVD-RWDVR-109 1.00
Drive (Hardware) Region: 1

Media is a Data DVD.
Booktype: dvd-rom (version 1), Layers: 2 (opposite)
Size of first Layer: 2084960 sectors (4072 MBytes)
Total size: 4169920 sectors (8144 MBytes)

Video DVD (or CD) label: EMPLOYEE_OF_THE_MONTH
Media is CSS protected!
Video Standard: NTSC
Media is locked to region(s): 1!

RCE protection not found.
DVD structure appears to be correct.
Found & removed structural copy protection (Arccos, Puppetlock)!
Found & removed error zones between files!
Found & removed bogus title set!
Autorun not found on Video DVD.
Found & removed 7 bad sector protections!
Emulating RPC-2 drive with region 1!

Processed the AnyDVD files with VOB Blanker and was able to burn scussfully with Recode.


#2

Try 6.1.0.4:
http://sandbox.slysoft.com/SetupAnyDVD6104.exe

You can also directly import the disc into Recode without ripping first to the hard drive, provided Anydvd is running on your toolbar.


#3

Has 6.1.0.4 been released, then? I haven’t gotten either a popup or an email notification…


#4

It’s a BETA. So it hasn’t been made public yet besides these forums.


#5

Right, thanks!


#6

New beta

6.1.0.5

http://sandbox.slysoft.com/SetupAnyDVD6105.exe


#7

New beta

6.1.0.6

http://sandbox.slysoft.com/SetupAnyDVD6106.exe


#8

Anybody knows what are the new changes have the latest betas?


#9

6.1.0.6 2007 01 12

  • New: Added support for new versions of the SONY Arccos protection
    (e.g., Saw 3) to the option to remove “Protection based on unreadable
    Sectors”
  • New: Improved “Jump to title menu” with some discs containing
    TV episodes
  • New: Workaround for bug in I/O subsystem of Windows Vista,
    which can cause BSOD with copy protected DVDs
  • New: Workaround for problem with U3 USB memory sticks
  • New: improved display of drive type in AnyDVD status and drive
    selection window

6.1.0.6 seems to have mainly been related to resolving issues with U3 USB flash devices but, of course, includes the prior updates from the prior betas.


#10

I even don’t know what were the changes in the previous betas


#11

Essentially remove

  • New: Workaround for problem with U3 USB memory sticks

from the changes and that’s what the previous changes were.

6.1.0.5 & 6.1.0.6 were mostly U3 changes, I believe. I think the I/O Vista problem was 6.1.0.4 and 6.1.0.3 was for Saw 3 & Jump to Title Menu fixes.

It’s not really that important. You’re best updating to 6.1.0.6 if you are having a problem with anything that the changelog appears to have resolved. If not you can stay with 6.1.0.2 or update. Whichever.