View Full Version : Nero's DVD-Video files reallocation failed error?
Pfc Joker
22nd January 2004, 18:24
Ok, this is the closest thing in the forums I could find about this... Jafco's post four from the bottom (http://forum.doom9.org/showthread.php?s=&threadid=29863&highlight=reallocation+failed) sums up everything pretty well.
I use Nero 6.3.0.2 to burn my DVD's and use the DVD-Video mode, ever have since I started backing up DVD's with Shrink or Recode. Now I use the Big 3 method and Nero Burning ROM always give me a "DVD-Video files reallocation failed" error that says the disc might be unplayable. Also it lists that a required VOB file is missing, a VOB file that doesn't exist! I just click YES to continue, Nero tells me that "DVD-Video files compliance ignored" and the disc is burnt.
The resulting disc seems to work fine on everything? :confused:
I have tried various changes to the options of Nero to see if anything changes and no luck. One fix is supposed to be this posted by DMagic1 That reallocation error appears to have something to do with the modification dates. If the dates of some of your dvd files are different you will get that error.Use the full Nero Burning Rom, not Express. Once you select DVD-Video or DVD-UDF, go to the dates tab. Select "Set volume creation and modication to current date and time". Then below select "Use Current Date and Time" for file dates. Now you will not get that reallocation error anymore. You will also not get that fail to read file error that comes up sometimes.
No Joy :mad:
Do ya just burn using the DVD-ROM (UDF/ISO) mode instead of DVD-Video, if so what are the difference between the two modes, if any?
atreides93
22nd January 2004, 21:04
I use DVDShrink and various other programs and I don't get re-allocation errors. I'm fairly certain if you burn DVD's despite those errors, you're taking big risks that it won't play right on some dvd players.
As to the cause, I really don't know what causes it...
I'm not familiar with the "big 3 method" you refer to. what method is that?
Pfc Joker
22nd January 2004, 23:26
As to the cause, I really don't know what causes it...I'm not familiar with the "big 3 method" you refer to. what method is that?
Hold the phone, your a Doom9 moderator, with over 760 posts, and your fairly certain that if I burn disc despite those errors it's bad, and you have never heard of the "Big 3" method before? I'm speachless.
:readguid:
Kedirekin
22nd January 2004, 23:51
I wonder when people started using the 'Big 3' moniker.
@atreides93,
In the one click forums, you mentioned you were surpirsed to see a new release of DVDShrink. How long have you been away? Were people using DoItFast4U, DoCCE4U and ReAuthorist (AKA The Big 3) when you were here last.
Caedel
23rd January 2004, 02:37
I sometimes get that error in Nero... if i do, i just burn it with RecordNow MAX. Problem solved!
atreides93
23rd January 2004, 07:13
Originally posted by Pfc Joker
Hold the phone, your a Doom9 moderator, with over 760 posts, and your fairly certain that if I burn disc despite those errors it's bad, and you have never heard of the "Big 3" method before? I'm speachless.
:readguid:
I'm not sure how I'm supposed to respond to this. Sounds like you're trying to bait me. At least, you did make me regret trying to help you. Perhaps I should have just told you to read the guides or something?
I don't believe being a moderator or having a certain number of posts to my name means I should be well versed in every single guide on this site. I'm telling you what I know based on some guides I read a long time ago plus a lot of real-world experience backing up DVD's and burning DVD-R/RW's.
I have seen people go ahead and burn movies despite the allocation error message and claim its "ok", but then someone will come along and post that on such and such dvd player it messes up.
There is no real definitive answer to your question.
atreides93
23rd January 2004, 07:19
Originally posted by Kedirekin
I wonder when people started using the 'Big 3' moniker.
@atreides93,
In the one click forums, you mentioned you were surpirsed to see a new release of DVDShrink. How long have you been away? Were people using DoItFast4U, DoCCE4U and ReAuthorist (AKA The Big 3) when you were here last.
I thought most were using Dvdshrink and dvd2one and IC7/8 last time I was visiting the one click backup forum regularly.
I kept up with the DoitFast4u development posts, and even tried it a few times, but for CCE encodes, I just found it simpler to do it myself by hand since I had done it countless times and had full control over every aspect.
As for calling them the "big 3"...:rolleyes:
I never use any of them, since dvdshrink3.0 and 2.3 handles just about all backups I need to do these days.
RB
23rd January 2004, 08:59
Originally posted by Pfc Joker
Now I use the Big 3 method and Nero Burning ROM always give me a "DVD-Video files reallocation failed" error that says the disc might be unplayable. Also it lists that a required VOB file is missing, a VOB file that doesn't exist!
This happens when you forget to check "Transfer VTS_C_ADT Table" in IFOUpdate. Also make sure to get the latest IFOUpdate 0.78 (http://forum.doom9.org/showthread.php?s=&threadid=58897&perpage=20&pagenumber=2#post421970) so you can also safely transfer the time map (TM_APTI).
Pfc Joker
23rd January 2004, 11:51
This happens when you forget to check "Transfer VTS_C_ADT Table" in IFOUpdate. Also make sure to get the latest IFOUpdate 0.78 so you can also safely transfer the time map (TM_APTI).
Nope, tried that sugestion also.
RB
23rd January 2004, 12:41
Strange, that was definitely the reason when I got this error once before.
Nero is actually fairly good at detecting inconsistencies, so I still think maybe you did something wrong, i.e. did not replicate the IFO structures exactly when authoring or you blanked out some titles but did not IFOUpdate them. Maybe if you describe exactly what you did, I can be of more help. BTW, I'm using Nero 5.5.10.54 to burn all my DVDs and never had this happening again with the projects I manually authored in Scenarist.
Pfc Joker
23rd January 2004, 14:11
Thanks for the help RB, you are probably right when you said it's most likely something I did, or forgot to do. I'm in the middle of doing a backup of Open Range right now so give me some time and if the problem comes up again I'll be back with a detailed report, visa versa if I figure it out, I'll let you know either way.
Pfc Joker
23rd January 2004, 15:30
This happens when you forget to check "Transfer VTS_C_ADT Table" in IFOUpdate
I had this option checked, but I didn't have the check next to "VTS_TMAPTI Table Transfer (Time Map)". I had been doing everything else correct untill I reached the IFOUpdate part. Thanks RB for the start in the right direction.
@atreides93, No I was not trying to bait you and I'm sorry I made you feel like you regret trying to help. You can tell me to read the guides if you want and I will, again, because you never know when you might have missed something. But as far as your statement that "There is no real definitive answer to your question", yes there is. My question was why the hell does Nero give me this error and the answer is because I didn't have one little option checked in IFOUpdate.
atreides93
24th January 2004, 01:02
Originally posted by Pfc Joker
But as far as your statement that "There is no real definitive answer to your question", yes there is. My question was why the hell does Nero give me this error and the answer is because I didn't have one little option checked in IFOUpdate.
You asked more than one question. I wasn't referring to that question. I was referring to this one:
>>>
The resulting disc seems to work fine on everything?
>>>>
So I still say there is no definitive answer to that question....if you read the paragraph just before I said that, its pretty clear what question I'm talking about! I'm talking about how some people say they've burned lots of movies with that error message and they seem to work. But others have seen problems....
Pfc Joker
24th January 2004, 01:54
Dude everyone else got it, I was trying to figure out what was up with the error in Nero, stop being so picky. :rolleyes:
DMagic1
25th January 2004, 09:18
Originally posted by Pfc Joker
I have tried various changes to the options of Nero to see if anything changes and no luck. One fix is supposed to be this posted by DMagic1
Hehe, that was what I thought was a solution to a problem many were having back then. It seemed to work on one project but then it didn't on the next. Everytime I thought I found the reason it would turn up again on another project. This was back when I used CCE for all backups because there were no one click apps. I've seen many topics about different fixes for this and none worked all the time. It would seem that there are many factors that cause this same error msg. Too bad Nero isn't more specific.
Pfc Joker
25th January 2004, 14:02
Too bad Nero isn't more specific.
Ain't that the truth, so far keeping "Transfer VTS_C_ADT Table" and "VTS_TMAPTI Table Transfer (Time Map)" seems to keep Nero happy 90% of the time. :)
DnGermany
29th January 2004, 11:15
I use DvdShrink and Dvd2One alot and never get the error, unless i mess around with the files afterwards. Did you use Ifoedit or delete something after using shrink? Otherwise everything works fine when using nero for me.
Pfc Joker
29th January 2004, 12:11
This error is in relation to the Big 3 method not any of the one click backup solutions.
s41
30th January 2004, 12:47
I'm using DVD Decrypter, IFO edit and InstantCopy8 and i get
Nero's DVD-Video files reallocation failed error?
message almost everytime I cut some titles out, I understand this messsage like warning that there is something missing in project, but it's alright, cause I want it to be like that.
however my DVDs are playable on standalones without any problems.
That's what is it about, doesn't?
ps: sorry for my english - Slovakia forever! :-)
Mosaic
2nd February 2004, 01:30
I ignore that error......happens with DVD2one as well....usually when u drop audio trax etc.
mikegun
2nd February 2004, 16:42
hi,
I hope that I didn't miss s.th. but did you guys try to burn the disk as udf/iso ? if so, do you get the same error ?
regards,
m.
idbirch2
2nd February 2004, 23:29
I used to, as Mikegun said, burn using the UDF/ISO mode if Nero moaned about re-allocation but that was quite a long time ago. Since then I've been using ImgTools Burn (link on the main news page of Doom9) which has a tick box for 'Reallocate Video_ts structure' which I just leave unticked. Setting 'DVDROM booktype" in other settings seems to improve compatibility aswell.
DMagic1
3rd February 2004, 08:39
Originally posted by idbirch2
Setting 'DVDROM booktype" in other settings seems to improve compatibility aswell.
I just started using that app a few days ago. I hadn't even looked in that setting tab yet. Nice feature was being overlooked.
coona
3rd February 2004, 11:08
In my experience the most "compatible" solution is CouJo´s ImgTool Classic and LIGHTNING UK!´s DVD Decrypter. I was used to combination ImgTool and Nero. I burned more than 50 compilations and only one did not work. But the same compilation burned as image made by ImgTool Classic by DVD Decrypter works flawlesly. So the fault was in the way it was burned...
Raster
8th April 2004, 09:33
CouJo has mentioned that ImgTool Classic does not check the IFO's for errors so that is why you do not get the reallocation error message.
The errors can still exist but you would not know that.
And aside from ImgTool Burn using NERO's apps, there is no difference between "Classic" and "Burn". Infact, you can choose to burn anyway in ImgTool "Burn" ignoring the realocation error like in "Classic".
I'm sure the reallocation error messaage comes from the NERO apps and not from CouJo's ImgTool Burn.
I use to do the ImgTool "Classic"-DVD Decrypter thing until I found the above out from CouJo. Now I just burn with ImgTool "Burn" (latest version) and if I get the realocation error, I try to fix it. And if I can't, I burn to Re-Write first ignoring error and test before burning to DVD-R.
I don't think it's one thing in particular that causes that error but I have noticed that sometimes if the VOB group that I have replaced has a original VTS_XX_0.VOB with a zero file size, the error will show up. If I remove the original VTS_XX_0.VOB and "get sectors" in IFOEdit the error goes away.
The problem is in the IFO not in the burning.
boombastic
10th April 2004, 13:23
After i get the reallocation error and i ignored it Nero tells me "a non critical error occured whic can result in a defective write.Do you wish to continue?" Is it refering to th reallocation one or it's something else?Here is the log:
Windows XP 5.1
IA32
WinAspi: File 'Wnaspi32.dll': Ver=4.60 (1021), size=45056 bytes, created 10/09/1999 13.06.00
ahead WinASPI: File 'D:\Programmi\Ahead\nero\Wnaspi32.dll': Ver=2.0.1.59, size=160016 bytes, created 16/12/2003 20.18.06
Nero version: 6.3.1.6
Recorder: < Image Recorder> Version: Not available - HA -1 TA 0 - 6.3.1.6
Adapter driver: <Virtual Device> HA -1
Drive buffer :
CD-ROM: <LG CD-ROM CRD-8520B>Version: 1.00 - HA 1 TA 1 - 6.3.1.6
Adapter driver: <atapi> HA 1
=== Scsi-Device-Map ===
DiskPeripheral : Maxtor 6Y080L0 atapi Port 0 ID 0 DMA: On
CdRomPeripheral : CREATIVE CD-RW RW8438E atapi Port 1 ID 0 DMA: On
CdRomPeripheral : LG CD-ROM CRD-8520B atapi Port 1 ID 1 DMA: Off
CdRomPeripheral : Generic DVD-ROM 1.0 d346prt Port 2 ID 0 DMA: Off
CdRomPeripheral : NERO IMAGEDRIVE2 2.26 imagedrv Port 3 ID 0 DMA: Off
=== CDRom-Device-Map ===
CREATIVE CD-RW RW8438E E: CDRom0
LG CD-ROM CRD-8520B F: CDRom1
Generic DVD-ROM H: CDRom2
NERO IMAGEDRIVE2 G: CDRom3
=======================
AutoRun : 1
Excluded drive IDs:
CmdQueuing : 1
CmdNotification: 2
WriteBufferSize: 40894464 (0) Byte
ShowDrvBufStat : 0
EraseSpeed : 0
BUFE : 0
Physical memory : 255MB (261616kB)
Free physical memory: 85MB (87628kB)
Memory in use : 66 %
Uncached PFiles: 0x0
Use Static Write Speed Table: 0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)
10.4.2004
UDF/ISO compilation
14.18.52 #1 Phase 112 File dlgbrnst.cpp, Line 1841
DVD-Video files reallocation started
14.18.52 #2 DVDREALLOC -21 File DVDVideoCompilation.cpp, Line 1177
Required file 'VTS_02_1.VOB' is not present
14.18.52 #3 Phase 115 File dlgbrnst.cpp, Line 1841
DVD-Video files reallocation failed
14.18.54 #4 Phase 132 File dlgbrnst.cpp, Line 1841
DVD-Video files compliance ignored
14.18.54 #5 Text 0 File Isodoc.cpp, Line 6062
Iso document burn settings
------------------------------------------
Determine maximum speed : FALSE
Simulate : FALSE
Write : TRUE
Finalize CD : TRUE
Multisession : FALSE
Burning mode : DAO
Mode : 1
ISO Level : 1 (Max. of 11 = 8 + 3 char)
Character set : ISO 9660
Joliet :FALSE
Allow pathdepth more than 8 directories : TRUE
Allow more than 255 characters in path : TRUE
Write ISO9660 ;1 file extensions : TRUE
14.18.54 #6 Phase 111 File dlgbrnst.cpp, Line 1841
DVD-Video files sorted
14.18.54 #7 Text 0 File Reader.cpp, Line 118
Reader running
14.18.54 #8 ISO9660GEN -11 File geniso.cpp, Line 3898
First writeable address = 0 (0x00000000)
14.18.54 #9 ISO9660GEN -11 File geniso.cpp, Line 3898
First writeable address = 0 (0x00000000)
14.18.54 #10 Text 0 File Burncd.cpp, Line 3198
Turn on Disc-at-once, using DVD media
14.18.55 #11 Text 0 File DlgWaitCD.cpp, Line 244
Last possible write address on media: 2147483646 (477218:35.21, 4194303MB)
Last address to be written: 2311439 (513:39.14, 4514MB)
14.18.55 #12 Text 0 File DlgWaitCD.cpp, Line 249
Write in overburning mode: FALSE
14.18.55 #13 Text 0 File DlgWaitCD.cpp, Line 2107
Recorder: Image Recorder;
CD type reading failed
ATIP Data: ?
14.18.55 #14 Text 0 File DlgWaitCD.cpp, Line 410
>>> Protocol of DlgWaitCD activities: <<<
=========================================
14.18.55 #15 Text 0 File ThreadedTransferInterface.cpp, Line 813
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 (CTransferItem)
2 indices, index0 (150) not provided
original disc pos #0 + 2311440 (2311440) = #2311440/513:39.15
relocatable, disc pos for caching/writing not required/required, no patch infos
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2311440 blocks [ Image Recorder ]
--------------------------------------------------------------
14.18.56 #16 Text 0 File ThreadedTransferInterface.cpp, Line 982
Prepare recorder [ Image Recorder ] for write in CUE-sheet-DAO
DAO infos:
==========
MCN: ""
TOCType: 0x00; Session Closed, disc fixated
Tracks 1 to 1:
1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 307200 4734136320, ISRC ""
DAO layout:
===========
__Start_|____Track_|_Idx_|_RecDep_|_CtrlAdr_
-150 | lead-in | 0 | 0x00 | 0x41
-150 | 1 | 0 | 0x00 | 0x41
0 | 1 | 1 | 0x00 | 0x41
2311440 | lead-out | 1 | 0x00 | 0x41
14.18.56 #17 Phase 24 File dlgbrnst.cpp, Line 1841
Caching of files started
14.18.56 #18 Text 0 File Burncd.cpp, Line 4214
Cache writing successful.
14.18.56 #19 Phase 25 File dlgbrnst.cpp, Line 1841
Caching of files completed
Existing drivers:
File 'Drivers\ASPI32.SYS': Ver=4.60 (1021), size=25244 bytes, created 10/09/1999 13.06.00
File 'Drivers\PXHELP20.SYS': Ver=2.02.62a, size=20016 bytes, created 28/10/2003 12.02.00 (Prassi/Veritas driver for win 2K)
File 'Drivers\atapi.sys': Ver=?.?.?.?, size=86912 bytes, created 29/08/2002 3.27.50 (Adapter driver for src)
Registry Keys:
HKLM\Software\CPUCooL (Power saving: CPUCooL)
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)
Raster
10th April 2004, 20:50
Originally posted by boombastic
After i get the reallocation error and i ignored it Nero tells me "a non critical error occured whic can result in a defective write.Do you wish to continue?" Is it refering to th reallocation one or it's something else?Here is the log:
14.18.52 #1 Phase 112 File dlgbrnst.cpp, Line 1841
DVD-Video files reallocation started
14.18.52 #2 DVDREALLOC -21 File DVDVideoCompilation.cpp, Line 1177
Required file 'VTS_02_1.VOB' is not present
14.18.52 #3 Phase 115 File dlgbrnst.cpp, Line 1841
DVD-Video files reallocation failed
I'm not positive, but yes, I think is is related to the realocation error above. Check to see if you do have the 'VTS_02_1.VOB' file present. I've done that before, left out a file by mistake and when I replaced it everything was fine. If it is present, you can still try a burn (on Re-Write if possible) and see if it works.
I,ve had an error before where it stated that 'VTS_02_5.VOB' was missing. After compression, there was no such file as the compression brought it down to just 4 VTS's. I burned anyway and it was fine.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.