Содержание
- Session fixation error writing lead in
- Session fixation error writing lead-in
- Session fixation error writing lead-in
Session fixation error writing lead in
Exactly. It’s one 6,5 GB file, so I have to use a DVD-R Double-Layer media.
Nero failed with error during «Writing Lead-in», so I think it was the same error.
Nevertheless I doubt it’s a hardware failure, as I burned a few disc yesterday and they all came out fine (I always enable data verification).
I’d test the file size theory, but I don’t want to waste yet another media 
You may not have wasted ANY of your media. I could br wrong but, I don’t believe anything was written to the discs.
I’d suggest you test your theory about filesize by splitting the file.
Unfortunately a short time later it said:
Retry Failed — Reason: Power Calibration Area Is Full
Retry Failed — Reason: Power Calibration Area Is Full
But I’d highly prefer to keep my movie in one chunk.
Then it’s not a «single data file», it’s a movie.
If that’s the case, what’s the format?
Whatever — it is not software related. Both Ner0 and ImgBurn report errors. I’d switch to Verbatim, +R, 2.4x, MKM-001-00, Made in Singapore.
Only use genuine Verbatim or Taiyo Yuden media.
Unless your few successful disks burned later were also DL, you haven’t completely ruled out hardware. The drive could be failing where it’s unable to focus the lens on the second layer but is still able to write single-layer media.
Also, on the PC the file will always be truncated because ISO doesn’t support over 2GB files. You should use UDF instead if you are burning large files.
Personally do not know anything about your problem
Maybe something with this? Why not use SPTI?
That’s exactly the kind of discs I have here 
Then it’s not a «single data file», it’s a movie.
If that’s the case, what’s the format?
It’s a MKV file. The original TS file was captured from TV. Then re-muxed to MKV, since I didn’t want to re-encode.
But from a burner’s point of view it’s as much a «data» file as any other binary file, I guess.
So I will spend the day to re-encode the movie to 4,7 GB and then I’ll try to burn it to a Single-Layer media.
I didn’t use SPTI because I had another ImgBun problem in the past. Don’t think the problem is caused by the I/O driver.
Nero uses it’s own ASPI driver and it failed too.
Also, on the PC the file will always be truncated because ISO doesn’t support over 2GB files. You should use UDF instead if you are burning large files.
I just successfully used NERO in UDF mode to burn a single 6.08Gb file to D/L Verbatim disc (2.4X Singapore manufacture, burned at 4X).
1) If you have the NERO «InCD» tool (packet writing program) installed, you probably want to completely eliminate it from your system (use the NERO «clean» tool), as it’s been noted (for years now) to cause conflicts.
2) Likewise, the «Patin-Couffin» driver has been noted in numerous postings (Do a Googlesearch) to also be a problem causer, particularly if more than one burning program is installed on a system
3) Most likely, however, despite your protestations, is that the «Power calibration» error is telling you that you have a hardware problem
I 22:47:04 Destination Device: [4:0:0] BENQ DVD DD DW1620 B7W9 (G 
(SCSI)
I 22:47:04 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00) (Speeds: 2,4x)
Are you sure that drive / firmware even supports MKM-003-00 properly?
It could just be attempting to use a very generic (2.4x) write strategy and it’s failing.
Источник
Session fixation error writing lead-in
I’m in need of help. Trying to write a project to dual layered disc using DVD Studio Pro. Have done everything by the book, but still getting an error every time. Is there a step I am missing? Here is my log:
Starting DVD Build PUNK.
Compiler Initializing.
Precompiling Project PUNK
Compiling VMG Information.
Created 65 PGCs in VTSM1
Created 5 PGCs in VTSM2
Created 8 PGCs in VMG.
8 Menu(s) will be created.
Compiling Menu PGCs.
Compiling Menu#1 (Menu 1).
Rendering Menu:Menu 1,Language:1.
Compiling Menu#2 (Menu 2).
Rendering Menu:Menu 2,Language:1.
Compiling Menu#3 (Menu 3).
Rendering Menu:Menu 3,Language:1.
Compiling Menu#4 (Menu 4).
Rendering Menu:Menu 4,Language:1.
Compiling Menu#5 (Menu 5).
Rendering Menu:Menu 5,Language:1.
Compiling Menu#6 (Menu 6).
Rendering Menu:Menu 6,Language:1.
Compiling Menu#7 (Menu 7).
Rendering Menu:Menu 7,Language:1.
Compiling Menu#8 (Menu 8).
Rendering Menu:Menu 8,Language:1.
Generating Transition: VTSM #01, VOB #1.
Generating Transition: VTSM #01, VOB #2.
Generating Transition: VTSM #01, VOB #3.
Generating Transition: VTSM #01, VOB #4.
Generating Transition: VTSM #01, VOB #5.
Generating Transition: VTSM #01, VOB #6.
Generating Transition: VTSM #01, VOB #7.
Generating Transition: VTSM #01, VOB #8.
Generating Transition: VTSM #01, VOB #9.
Generating Transition: VTSM #01, VOB #10.
Generating Transition: VTSM #01, VOB #11.
Generating Transition: VTSM #01, VOB #12.
Generating Transition: VTSM #01, VOB #13.
Generating Transition: VTSM #01, VOB #14.
Generating Transition: VTSM #01, VOB #15.
Generating Transition: VTSM #01, VOB #16.
Generating Transition: VTSM #01, VOB #17.
Generating Transition: VTSM #01, VOB #18.
Generating Transition: VTSM #01, VOB #19.
Generating Transition: VTSM #01, VOB #20.
Generating Transition: VTSM #01, VOB #21.
Generating Transition: VTSM #01, VOB #22.
Generating Transition: VTSM #01, VOB #23.
Generating Transition: VTSM #01, VOB #24.
Generating Transition: VTSM #01, VOB #25.
Generating Transition: VTSM #01, VOB #26.
Generating Transition: VTSM #01, VOB #27.
Generating Transition: VTSM #01, VOB #28.
Generating Transition: VTSM #01, VOB #29.
Generating Transition: VTSM #01, VOB #30.
Generating Transition: VTSM #01, VOB #31.
Generating Transition: VTSM #01, VOB #32.
Generating Transition: VTSM #01, VOB #33.
Generating Transition: VTSM #01, VOB #34.
Generating Transition: VTSM #01, VOB #35.
Generating Transition: VTSM #01, VOB #36.
Generating Transition: VTSM #01, VOB #37.
Generating Transition: VTSM #01, VOB #38.
Generating Transition: VTSM #01, VOB #39.
Generating Transition: VTSM #01, VOB #40.
Generating Transition: VTSM #01, VOB #41.
Generating Transition: VTSM #01, VOB #42.
Generating Transition: VTSM #01, VOB #43.
Generating Transition: VTSM #01, VOB #44.
Generating Transition: VTSM #01, VOB #45.
Generating Transition: VTSM #01, VOB #46.
Generating Transition: VTSM #01, VOB #47.
Generating Transition: VTSM #01, VOB #48.
Generating Transition: VTSM #01, VOB #49.
Generating Transition: VTSM #01, VOB #50.
Generating Transition: VTSM #01, VOB #51.
Writing HV000M02.EVO
Compiling Menu PGCs.
Writing HV002M01.EVO
2 VTSs and 2 Titles will be created.
Compiling VTS#1 (Show-PUNK-MPEG-2 3.7Mbps 1-pass).
Muxing HV001T01.EVO
Done.
Compiling VTS#2 (1-Bay1-Scenework-PUNK-MPEG-2 3.7Mbps 1-pass).
Writing HV002M01.EVO
Muxing HV002T01.EVO
Done.
Linking VMG.
Linking VTS#1.
Linking VTS#2.
Writing VTS#1.
Writing VTS#2.
Writing VMG.
Writing Layout Info.
Compile Completed Successfully
Note: The file ‘PUNK.layout’ found in the ‘HVDVD_TS’ folder is not a DVD-Video file and will not be included in the final disc or DLT.
Note: The file ‘VOB_DATA.LAY’ found in the ‘HVDVD_TS’ folder is not a DVD-Video file and will not be included in the final disc or DLT.
Start formatting
Formatting as Standard DVD
Simulation mode is off
Lossless linking is on
Number of layers is 2
Doing opposite track path
Setting layer switch at sector 1974048.
Doing side 1 of 1
Playable in region 1,2,3,4,5,6,8
Disc size is 12 cm
Disc has no copyright material
Writing UDF 2.50 structures
Writing files
The recording device reported the media error: Session fixation error writing lead-in. (0x72, 0x01.)
Is this a Superdrive problem or a formating problem?
Power Mac G5, Mac OS X (10.5.8), Dual 2Ghz Power PC G5
Источник
Session fixation error writing lead-in
I’m in need of help. Trying to write a project to dual layered disc using DVD Studio Pro. Have done everything by the book, but still getting an error every time. Is there a step I am missing? Here is my log:
Starting DVD Build PUNK.
Compiler Initializing.
Precompiling Project PUNK
Compiling VMG Information.
Created 65 PGCs in VTSM1
Created 5 PGCs in VTSM2
Created 8 PGCs in VMG.
8 Menu(s) will be created.
Compiling Menu PGCs.
Compiling Menu#1 (Menu 1).
Rendering Menu:Menu 1,Language:1.
Compiling Menu#2 (Menu 2).
Rendering Menu:Menu 2,Language:1.
Compiling Menu#3 (Menu 3).
Rendering Menu:Menu 3,Language:1.
Compiling Menu#4 (Menu 4).
Rendering Menu:Menu 4,Language:1.
Compiling Menu#5 (Menu 5).
Rendering Menu:Menu 5,Language:1.
Compiling Menu#6 (Menu 6).
Rendering Menu:Menu 6,Language:1.
Compiling Menu#7 (Menu 7).
Rendering Menu:Menu 7,Language:1.
Compiling Menu#8 (Menu 8).
Rendering Menu:Menu 8,Language:1.
Generating Transition: VTSM #01, VOB #1.
Generating Transition: VTSM #01, VOB #2.
Generating Transition: VTSM #01, VOB #3.
Generating Transition: VTSM #01, VOB #4.
Generating Transition: VTSM #01, VOB #5.
Generating Transition: VTSM #01, VOB #6.
Generating Transition: VTSM #01, VOB #7.
Generating Transition: VTSM #01, VOB #8.
Generating Transition: VTSM #01, VOB #9.
Generating Transition: VTSM #01, VOB #10.
Generating Transition: VTSM #01, VOB #11.
Generating Transition: VTSM #01, VOB #12.
Generating Transition: VTSM #01, VOB #13.
Generating Transition: VTSM #01, VOB #14.
Generating Transition: VTSM #01, VOB #15.
Generating Transition: VTSM #01, VOB #16.
Generating Transition: VTSM #01, VOB #17.
Generating Transition: VTSM #01, VOB #18.
Generating Transition: VTSM #01, VOB #19.
Generating Transition: VTSM #01, VOB #20.
Generating Transition: VTSM #01, VOB #21.
Generating Transition: VTSM #01, VOB #22.
Generating Transition: VTSM #01, VOB #23.
Generating Transition: VTSM #01, VOB #24.
Generating Transition: VTSM #01, VOB #25.
Generating Transition: VTSM #01, VOB #26.
Generating Transition: VTSM #01, VOB #27.
Generating Transition: VTSM #01, VOB #28.
Generating Transition: VTSM #01, VOB #29.
Generating Transition: VTSM #01, VOB #30.
Generating Transition: VTSM #01, VOB #31.
Generating Transition: VTSM #01, VOB #32.
Generating Transition: VTSM #01, VOB #33.
Generating Transition: VTSM #01, VOB #34.
Generating Transition: VTSM #01, VOB #35.
Generating Transition: VTSM #01, VOB #36.
Generating Transition: VTSM #01, VOB #37.
Generating Transition: VTSM #01, VOB #38.
Generating Transition: VTSM #01, VOB #39.
Generating Transition: VTSM #01, VOB #40.
Generating Transition: VTSM #01, VOB #41.
Generating Transition: VTSM #01, VOB #42.
Generating Transition: VTSM #01, VOB #43.
Generating Transition: VTSM #01, VOB #44.
Generating Transition: VTSM #01, VOB #45.
Generating Transition: VTSM #01, VOB #46.
Generating Transition: VTSM #01, VOB #47.
Generating Transition: VTSM #01, VOB #48.
Generating Transition: VTSM #01, VOB #49.
Generating Transition: VTSM #01, VOB #50.
Generating Transition: VTSM #01, VOB #51.
Writing HV000M02.EVO
Compiling Menu PGCs.
Writing HV002M01.EVO
2 VTSs and 2 Titles will be created.
Compiling VTS#1 (Show-PUNK-MPEG-2 3.7Mbps 1-pass).
Muxing HV001T01.EVO
Done.
Compiling VTS#2 (1-Bay1-Scenework-PUNK-MPEG-2 3.7Mbps 1-pass).
Writing HV002M01.EVO
Muxing HV002T01.EVO
Done.
Linking VMG.
Linking VTS#1.
Linking VTS#2.
Writing VTS#1.
Writing VTS#2.
Writing VMG.
Writing Layout Info.
Compile Completed Successfully
Note: The file ‘PUNK.layout’ found in the ‘HVDVD_TS’ folder is not a DVD-Video file and will not be included in the final disc or DLT.
Note: The file ‘VOB_DATA.LAY’ found in the ‘HVDVD_TS’ folder is not a DVD-Video file and will not be included in the final disc or DLT.
Start formatting
Formatting as Standard DVD
Simulation mode is off
Lossless linking is on
Number of layers is 2
Doing opposite track path
Setting layer switch at sector 1974048.
Doing side 1 of 1
Playable in region 1,2,3,4,5,6,8
Disc size is 12 cm
Disc has no copyright material
Writing UDF 2.50 structures
Writing files
The recording device reported the media error: Session fixation error writing lead-in. (0x72, 0x01.)
Is this a Superdrive problem or a formating problem?
Power Mac G5, Mac OS X (10.5.8), Dual 2Ghz Power PC G5
Источник
M-Disc is a variation of the DVD+R standard. While any device that can read DVD+R discs will read M-Disc DVD+R, they can only be written by a drive capable of writing to M-Disc media. Certain models of Pioneer and LG Blu-Ray burners support writing to M-Disc. Both of my Pioneer and LG models do. You will need to buy a drive that says it expressly writes to M-Disc. Or get different DVD+R discs that are not M-Disc.
M-Disc is designed to last for like a thousand years. It basically burns pits into metal oxide. Normal DVD+R are organic dye discs and are said to last for a hundred years, but probably won’t last that long. The comparison is like writing something in ink on paper to chiseling it in stone. The stone will obviously last longer than the ink on paper.
I don’t buy DVD burners anymore, just Blu-Ray ones. So, I don’t know of any DVD only burners that support M-Disc. For instance, these are the 2 burners I have that support M-Disc:
It will be easier to just get different DVD+R discs. However, M-Disc are about 5 times the price of regular DVD+R, so you have already invested some money in those. But, getting a disc that supports them will mean you’re out more expenditure. Plus, there’s the time and necessary expertise to install an internal burner, if you can’t find an external one that supports M-Disc. Or you can get an internal one that does and put it in an external enclosure. But, you’re out more money for the enclosure, too.
If you want different Verbatim DVD+R, don’t get the ones you find in brick and mortar stores. They will be the Life Series made by CMC Magnetics, the worst optical manufacturer out there. What you’ll want are the DataLife Plus series you can only find at places like Amazon.com. And even they will offer Life Series. Even if they don’t say Life Series, if they don’t say DataLife Plus, they will be CMC, most likely. CMC causes about 50 percent of the issues we see on these boards.
|
|
#1 | Link |
|
Software Developer
Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,243 |
ImgBurn: Session Fixation Error Writing Lead In Okay, I just wasted four Verbatim Double-Layer medias on this Code: I 22:36:58 ImgBurn Version 2.4.2.0 started! I 22:36:58 Microsoft Windows XP Professional x64 Edition (5.2, Build 3790 : Service Pack 2) I 22:36:58 Total Physical Memory: 4.192.460 KB - Available: 2.761.088 KB I 22:36:58 Initialising Patin-Couffin... I 22:36:58 Patin-Couffin - VSO Software - Internal Revision 37 I 22:36:58 Searching for SCSI / ATAPI devices... I 22:36:58 Found 1 DVD�RW and 1 BD-ROM/HD DVD-ROM! I 22:37:21 Operation Started! I 22:37:21 Building Image Tree... I 22:37:21 Calculating Totals... I 22:37:21 Preparing Image... [...] I 22:45:15 Average Write Rate: N/A - Maximum Write Rate: N/A I 22:46:57 Operation Started! I 22:46:58 Building Image Tree... I 22:46:58 Calculating Totals... I 22:46:58 Preparing Image... I 22:46:58 Contents: 2 Files, 0 Folders I 22:46:58 Size: 7.717.968.311 bytes I 22:46:58 Sectors: 3.768.541 I 22:46:58 Image Size: 7.718.535.168 bytes I 22:46:58 Image Sectors: 3.768.816 I 22:46:58 Operation Successfully Completed! - Duration: 00:00:00 I 22:47:02 Operation Started! I 22:47:02 Building Image Tree... I 22:47:03 Calculating Totals... I 22:47:03 Preparing Image... I 22:47:03 Contents: 2 Files, 0 Folders I 22:47:03 Size: 7.717.968.311 bytes I 22:47:03 Sectors: 3.768.541 I 22:47:03 Image Size: 7.718.535.168 bytes I 22:47:03 Image Sectors: 3.768.816 I 22:47:04 Operation Successfully Completed! - Duration: 00:00:01 I 22:47:04 Operation Started! I 22:47:04 Source File: -==//[BUILD IMAGE]/==- I 22:47:04 Source File Sectors: 3.768.816 (MODE1/2048) I 22:47:04 Source File Size: 7.718.535.168 bytes I 22:47:04 Source File Volume Identifier: Die Wolke (720p) I 22:47:04 Source File Application Identifier: ImgBurn v2.4.2.0 I 22:47:04 Source File Implementation Identifier: ImgBurn I 22:47:04 Source File File System(s): UDF (1.02) I 22:47:04 Destination Device: [4:0:0] BENQ DVD DD DW1620 B7W9 (G:) (SCSI) I 22:47:04 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00) (Speeds: 2,4x) I 22:47:04 Destination Media Sectors: 4.173.824 I 22:47:04 Write Mode: DVD I 22:47:04 Write Type: DAO I 22:47:04 Write Speed: 2,4x I 22:47:04 Link Size: Auto I 22:47:04 Test Mode: No I 22:47:04 OPC: No I 22:47:04 BURN-Proof: Enabled I 22:47:04 Book Type Setting: DVD-ROM I 22:47:04 Advanced Settings - WOPC: Yes I 22:47:04 Optimal L0 Data Zone Capacity: 1.884.416 I 22:47:04 Optimal L0 Data Zone Method: ECC Block Boundary I 22:47:04 Filling Buffer... (40 MB) I 22:47:04 Writing LeadIn... W 22:47:52 Failed to Write Sectors 0 - 31 - Reason: Session Fixation Error Writing Lead In W 22:47:52 Retrying (1 of 20)... W 22:48:38 Retry Failed - Reason: Session Fixation Error Writing Lead In W 22:48:38 Retrying (2 of 20)... W 22:49:25 Retry Failed - Reason: Session Fixation Error Writing Lead In W 22:49:25 Retrying (3 of 20)... W 22:50:12 Retry Failed - Reason: Session Fixation Error Writing Lead In W 22:50:12 Retrying (4 of 20)... W 22:50:59 Retry Failed - Reason: Session Fixation Error Writing Lead In W 22:50:59 Retrying (5 of 20)... W 22:51:46 Retry Failed - Reason: Session Fixation Error Writing Lead In W 22:51:46 Retrying (6 of 20)... W 22:52:33 Retry Failed - Reason: Session Fixation Error Writing Lead In W 22:52:33 Retrying (7 of 20)... W 22:53:20 Retry Failed - Reason: Session Fixation Error Writing Lead In W 22:53:20 Retrying (8 of 20)... W 22:54:08 Retry Failed - Reason: Session Fixation Error Writing Lead In W 22:54:08 Retrying (9 of 20)... W 22:54:38 Retry Failed - Reason: Power Calibration Area Is Full W 22:54:38 Retrying (10 of 20)... W 22:54:40 Retry Failed - Reason: Power Calibration Area Is Full W 22:54:40 Retrying (11 of 20)... W 22:54:42 Retry Failed - Reason: Power Calibration Area Is Full W 22:54:42 Retrying (12 of 20)... W 22:54:45 Retry Failed - Reason: Power Calibration Area Is Full W 22:54:45 Retrying (13 of 20)... W 22:54:47 Retry Failed - Reason: Power Calibration Area Is Full W 22:54:47 Retrying (14 of 20)... W 22:54:48 Retry Failed - Reason: Power Calibration Area Is Full W 22:54:48 Retrying (15 of 20)... W 22:54:51 Retry Failed - Reason: Power Calibration Area Is Full W 22:54:51 Retrying (16 of 20)... W 22:54:52 Retry Failed - Reason: Power Calibration Area Is Full W 22:54:52 Retrying (17 of 20)... W 22:54:55 Retry Failed - Reason: Power Calibration Area Is Full W 22:54:55 Retrying (18 of 20)... W 22:54:57 Retry Failed - Reason: Power Calibration Area Is Full W 22:54:57 Retrying (19 of 20)... W 22:54:59 Retry Failed - Reason: Power Calibration Area Is Full W 22:54:59 Retrying (20 of 20)... W 22:55:01 Retry Failed - Reason: Power Calibration Area Is Full W 22:55:05 Retrying (21)... W 22:55:07 Retry Failed - Reason: Power Calibration Area Is Full W 22:55:07 Retrying (22)... W 22:55:10 Retry Failed - Reason: Power Calibration Area Is Full E 22:55:11 Failed to Write Sectors 0 - 31 - Reason: Session Fixation Error Writing Lead In I 22:55:11 Synchronising Cache... W 22:55:14 User opted to skip the 'Close Track/Session/Disc' functions. E 22:55:14 Failed to Write Image! E 22:55:14 Operation Failed! - Duration: 00:08:10 I 22:55:14 Average Write Rate: N/A - Maximum Write Rate: N/A Also tried Nero, but it failed too. So what could be the reason? I try to burn a 6,5 GB file. So maybe it’s just not possible to burn a file to disc that exceeds the size of one layer ??? And no, the burner is fine. I burned several Verbatim Double-Layer medias with no problem…
Last edited by LoRd_MuldeR; 27th December 2008 at 23:13.
|
|
|
|
|
#2 | Link |
|
Custom User Title
Join Date: Mar 2005 Posts: 3,733 |
Is this a single data file you’re burning as a data disk? I believe there’s a file size limitation, but I’m unsure what it is. The «Power calibration error» generally indicates hardware failure. Did Nero’s log show the same error? |
|
|
|
|
|
#3 | Link |
|
Software Developer
Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,243 |
Quote:
Originally Posted by CWR03 Is this a single data file you’re burning as a data disk? I believe there’s a file size limitation, but I’m unsure what it is. Exactly. It’s one 6,5 GB file, so I have to use a DVD-R Double-Layer media. Quote:
Originally Posted by CWR03 The «Power calibration error» generally indicates hardware failure. Did Nero’s log show the same error? Nero failed with error during «Writing Lead-in», so I think it was the same error. Nevertheless I doubt it’s a hardware failure, as I burned a few disc yesterday and they all came out fine (I always enable data verification). I’d test the file size theory, but I don’t want to waste yet another media |
|
|
|
|
|
#4 | Link |
|
Registered User
Join Date: Aug 2005 Posts: 16,267 |
Hi! Quote: Failed to Write Sectors 0 — 31 You may not have wasted ANY of your media. I could br wrong but, I don’t believe anything was written to the discs. I’d suggest you test your theory about filesize by splitting the file…
|
|
|
|
|
|
#5 | Link |
|
Software Developer
Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,243 |
Quote:
Originally Posted by setarip_old Hi!You may not have wasted ANY of your media. I could br wrong but, I don’t believe anything was written to the discs. Unfortunately a short time later it said: Quote:
Originally Posted by setarip_old I’d suggest you test your theory about filesize by splitting the file… Okay, I’ll do so, even if it costs me another media. But I’d highly prefer to keep my movie in one chunk… |
|
|
|
|
|
#6 | Link |
|
Registered User
Join Date: Aug 2005 Posts: 16,267 |
Quote: Retry Failed — Reason: Power Calibration Area Is Full Regardless, if you haven’t already done so, load it into IMGBurn and see if it says it’s no longer writeable. Quote: But I’d highly prefer to keep my movie in one chunk… Then it’s not a «single data file», it’s a movie. If that’s the case, what’s the format?
|
|
|
|
|
|
#7 | Link |
|
Country Member
Join Date: Sep 2004 Location: is everything! Posts: 6,499 |
Whatever — it is not software related. Both Ner0 and ImgBurn report errors. I’d switch to Verbatim, +R, 2.4x, MKM-001-00, Made in Singapore. Regards
__________________ Only use genuine Verbatim or Taiyo Yuden media.
|
|
|
|
|
|
#8 | Link |
|
Custom User Title
Join Date: Mar 2005 Posts: 3,733 |
Unless your few successful disks burned later were also DL, you haven’t completely ruled out hardware. The drive could be failing where it’s unable to focus the lens on the second layer but is still able to write single-layer media. Quote: Originally Posted by setarip_old Then it’s not a «single data file», it’s a movie. What does the content of the data file have to do with it? Whether he’s burning an ISO image of a video DVD or a large MKV movie, it’s still a single data file. |
|
|
|
|
|
#9 | Link |
|
Registered User Join Date: Oct 2004 Location: India Posts: 321 |
Found by googling Quote: Also, on the PC the file will always be truncated because ISO doesn’t support over 2GB files. You should use UDF instead if you are burning large files. from Personally do not know anything about your problem
__________________ |
|
|
|
|
|
#10 | Link |
|
Member of a Library Join Date: Oct 2002 Posts: 463 |
Quote:
Originally Posted by LoRd_MuldeR I 22:36:58 Initialising Patin-Couffin… Maybe something with this? Why not use SPTI? GL |
|
|
|
|
|
#11 | Link |
|
Software Developer
Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,243 |
Quote:
Originally Posted by blutach I’d switch to Verbatim, +R, 2.4x, MKM-001-00, Made in Singapore. That’s exactly the kind of discs I have here Quote:
Originally Posted by setarip_old Then it’s not a «single data file», it’s a movie. If that’s the case, what’s the format? It’s a MKV file. The original TS file was captured from TV. Then re-muxed to MKV, since I didn’t want to re-encode. But from a burner’s point of view it’s as much a «data» file as any other binary file, I guess. So I will spend the day to re-encode the movie to 4,7 GB and then I’ll try to burn it to a Single-Layer media… Quote: Originally Posted by GrofLuigi Maybe something with this? Why not use SPTI? I didn’t use SPTI because I had another ImgBun problem in the past. Don’t think the problem is caused by the I/O driver. Nero uses it’s own ASPI driver and it failed too… Quote: Also, on the PC the file will always be truncated because ISO doesn’t support over 2GB files. You should use UDF instead if you are burning large files. I used the UDF filesystem, as no other disc type did allow my to even start the burning with my 2+ GB file
Last edited by LoRd_MuldeR; 28th December 2008 at 14:52.
|
|
|
|
|
|
#12 | Link |
|
Registered User
Join Date: Aug 2005 Posts: 16,267 |
I just successfully used NERO in UDF mode to burn a single 6.08Gb file to D/L Verbatim disc (2.4X Singapore manufacture, burned at 4X). 1) If you have the NERO «InCD» tool (packet writing program) installed, you probably want to completely eliminate it from your system (use the NERO «clean» tool), as it’s been noted (for years now) to cause conflicts. 2) Likewise, the «Patin-Couffin» driver has been noted in numerous postings (Do a Googlesearch) to also be a problem causer, particularly if more than one burning program is installed on a system 3) Most likely, however, despite your protestations, is that the «Power calibration» error is telling you that you have a hardware problem
Last edited by setarip_old; 28th December 2008 at 19:24.
|
|
|
|
|
|
#13 | Link |
|
Author of ImgBurn
Join Date: Oct 2001 Location: United Kingdom Posts: 1,973 |
Quote: I 22:47:04 Destination Device: [4:0:0] BENQ DVD DD DW1620 B7W9 (G Are you sure that drive / firmware even supports MKM-003-00 properly? It could just be attempting to use a very generic (2.4x) write strategy and it’s failing. |
|
|
|
(SCSI)|
|
#14 | Link |
|
Software Developer
Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,243 |
Quote:
Originally Posted by LIGHTNING UK! Are you sure that drive / firmware even supports MKM-003-00 properly? It could just be attempting to use a very generic (2.4x) write strategy and it’s failing. I burned Verbatim Double-Layer media with that drive before. And it worked fine. But now I got a new cakebox and have yet to successfully burn one single disc. Maybe the discs are bad, maybe the drive is failing. Maybe something else. BTW: What exactly is «MKM-003-00» and how can use a different write strategy? @setarip_old: Nope, «In CD» is not installed I will try to burn the movie to a Single-Layer media, once the re-encoding is completed. 633 minutes left…
Last edited by LoRd_MuldeR; 28th December 2008 at 21:43.
|
|
|
|
|
|
#15 | Link |
|
Country Member
Join Date: Sep 2004 Location: is everything! Posts: 6,499 |
MKM-003 is the media ID code. It is 8x Verbatim +R dual layer media. The preferred media is MKM-001 (2.4x). As LUK says, look for a firmware update. Regards
__________________ Only use genuine Verbatim or Taiyo Yuden media.
|
|
|
|
|
|
#16 | Link |
|
Software Developer
Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,243 |
Quote:
Originally Posted by blutach MKM-003 is the media ID code. It is 8x Verbatim +R dual layer media. The preferred media is MKM-001 (2.4x). As LUK says, look for a firmware update. Regards I was burning at 2.4x speed, as I always did for Double-Layer media. Faster speed isn’t even selectable. Code: I 22:47:04 Write Speed: 2,4x I’ll check for a Firmware update though… [EDIT] It seems «B7W9» is the latest Firmware available for my «DW1620» drive, which is the installed version.
Last edited by LoRd_MuldeR; 29th December 2008 at 00:16.
|
|
|
|
|
|
#17 | Link |
|
Registered User
Join Date: Aug 2005 Posts: 16,267 |
Again, the «Patin-Couffin» driver has been noted in numerous postings (Do a Googlesearch) to also be a problem causer, particularly if more than one burning program is installed on a system. You might want to try temporarily disabling it — and (risk possibly wasting another disc) see if either IMGBurn or NERO will then get past the «Power calibration» error… |
|
|
|
|
|
#18 | Link |
|
Software Developer
Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,243 |
Don’t think «Patin-Couffin» is at fault, as Nero doesn’t use it. AFAIK it uses it’s very own ASPI library. And I think Patin-Couffin was installed for a very long time on my system, as it ships with DVDFab. Nevertheless I successfully burned Verbatim Double-Layers not so long ago. However I will try uninstalling Patin-Couffin too. Just to be sure. But not today, as my encode still takes 191 minutes and I also need to sleep a few hours ^^ |
|
|
|
|
|
#19 | Link |
|
Registered User Join Date: Jul 2007 Posts: 15 |
Check Where The Disc Were Made… Verbatims made in India are to be avoided, I’m told. Might make a difference. I’ve been able to burn Memorex dual-layer disc with ease, until a recent batch and they fail during power calibration. What few of the older ones I have left continue to burn perfectly. Verbatims are the best, but harder to find locally, so I buy Memorex to fill in sometimes… |
|
|
|
|
|
#20 | Link |
|
Software Developer
Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,243 |
Quote:
Originally Posted by JCKitchens Verbatims made in India are to be avoided, I’m told. Might make a difference. I’ve been able to burn Memorex dual-layer disc with ease, until a recent batch and they fail during power calibration. What few of the older ones I have left continue to burn perfectly. Verbatims are the best, but harder to find locally, so I buy Memorex to fill in sometimes… According to the label on the cakebox, my Verbatim Double-Layer discs are «Made in Singapore» |
|
|
|
Позже запишу лог.
———————————————
I 22:14:25 ImgBurn Version 2.5.0.0 started!
I 22:14:25 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3)
I 22:14:25 Total Physical Memory: 523,252 KB — Available: 120,024 KB
I 22:14:25 Initialising SPTI…
I 22:14:25 Searching for SCSI / ATAPI devices…
I 22:14:25 Found 1 DVD-RW!
I 22:42:40 Operation Started!
I 22:42:40 Source File: D:Automobile
I 22:42:40 Source File Sectors: 3,827,488 (MODE1/2048)
I 22:42:40 Source File Size: 7,838,695,424 bytes
I 22:42:40 Source File Volume Identifier: DVD_ROM
I 22:42:40 Source File Volume Set Identifier: fd244000MS UDFBridge
I 22:42:40 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)
I 22:42:40 Source File Implementation Identifier: Microsoft CDIMAGE UDF
I 22:42:40 Source File File System(s): ISO9660, UDF (1.50)
I 22:42:40 Destination Device: [1:0:0] TSSTcorp CD/DVDW SH-S182D SB07 (F:) (ATA)
I 22:42:40 Destination Media Type: Smarttrack DVD-RW DVD8601 KD10 (Disc ID: MKM-003-00) (Speeds: 4x)
I 22:42:40 Destination Media Sectors: 4,173,824
I 22:42:40 Write Mode: DVD
I 22:42:40 Write Type: DAO
I 22:42:40 Write Speed: 4x
I 22:42:40 Link Size: Auto
I 22:42:40 Lock Volume: Yes
I 22:42:40 Test Mode: No
I 22:42:40 OPC: No
I 22:42:40 BURN-Proof: Enabled
I 22:42:40 Optimal L0 Data Zone Capacity: 1,913,760
I 22:42:40 Optimal L0 Data Zone Method: Copied From Original Disc
I 22:42:40 Set L0 Data Zone Capacity Succeeded!
I 22:42:42 Filling Buffer… (20 MB)
I 22:42:43 Writing LeadIn…
W 22:43:04 Failed to Write Sectors 0 — 31 — Reason: Session Fixation Error Writing Lead In
W 22:43:04 Retrying (1 of 20)…
W 22:43:17 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:43:17 Retrying (2 of 20)…
W 22:43:31 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:43:31 Retrying (3 of 20)…
W 22:43:44 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:43:44 Retrying (4 of 20)…
W 22:43:57 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:43:57 Retrying (5 of 20)…
W 22:44:10 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:44:10 Retrying (6 of 20)…
W 22:44:23 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:44:23 Retrying (7 of 20)…
W 22:44:36 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:44:36 Retrying (8 of 20)…
W 22:44:50 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:44:50 Retrying (9 of 20)…
W 22:45:03 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:45:03 Retrying (10 of 20)…
W 22:45:16 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:45:16 Retrying (11 of 20)…
W 22:45:29 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:45:29 Retrying (12 of 20)…
W 22:45:43 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:45:43 Retrying (13 of 20)…
W 22:45:57 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:45:57 Retrying (14 of 20)…
W 22:46:11 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:46:11 Retrying (15 of 20)…
W 22:46:24 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:46:24 Retrying (16 of 20)…
W 22:46:38 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:46:38 Retrying (17 of 20)…
W 22:46:52 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:46:52 Retrying (18 of 20)…
W 22:47:06 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:47:06 Retrying (19 of 20)…
W 22:47:20 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:47:20 Retrying (20 of 20)…
W 22:47:25 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:47:38 Retrying (21)…
W 22:47:44 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 22:47:50 Retrying (22)…
W 22:47:50 Retry Failed — Reason: Session Fixation Error Writing Lead In
E 22:47:52 Failed to Write Sectors 0 — 31 — Reason: Session Fixation Error Writing Lead In
I 22:47:52 Synchronising Cache…
W 22:48:42 User opted to skip the ‘Close Track/Session/Disc’ functions.
E 22:48:42 Failed to Write !
E 22:48:42 Operation Failed! — Duration: 00:06:01
I 22:48:42 Average Write Rate
Physical Format Information (Last Recorded):
Disc ID: MKM-003-00
Book Type: DVD-RW DL
Part Version: 1
Disc Size: 120mm
Maximum Read Rate: Not Specified
Number of Layers: 2
Track Path: Opposite Track Path (OTP)
Linear Density: 0.293 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 16,580,607
Last Physical Sector in Layer 0: 2,110,368
Performance (Write Speed):
Descriptor 1…
-> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00
-> EL: 3827519 (0x003A673F)
-> RS: 2,176 KB/s (1.6x) — WS: 3,324 KB/s (2.4x)
: N/A — Maximum Write Rate: N/A
.xm
Шаблон для разработчиков
Сообщение отредактировал K0DAK47 — Пятница, 06 Мая 2011, 21:25
Страница 2 из 2
-
Mak
Пользователь- Регистрация:
- 14.07.2011
- Сообщения:
- 644
- Симпатии:
- 61
Ладно займусь потихоньку, спасибо.
-
Kudesnik
Пользователь- Регистрация:
- 30.08.2011
- Сообщения:
- 320
- Симпатии:
- 25
Убей демона!!! Привод целый, не паникуй!
Самый долгий, но верный способ — снеси винду!
И ф топку демона, пользуюсь Ультроисой — проблем не знаю. -
aledjo
Пользователь- Регистрация:
- 10.10.2011
- Сообщения:
- 22
- Симпатии:
- 0
http://www.firmwarehq.com/index.php обнови прошивку привода!
Да причем тут демон? он никак не влияет на то что резак не может прожечь первые сектора. -
Kudesnik
Пользователь- Регистрация:
- 30.08.2011
- Сообщения:
- 320
- Симпатии:
- 25
SPTD driver can have a detrimental effect on drive performance.
Точно?! А я бы не был так уверен…
-
aledjo
Пользователь- Регистрация:
- 10.10.2011
- Сообщения:
- 22
- Симпатии:
- 0
Mak, в общем пробуй разные комбинации)
-
Mak
Пользователь- Регистрация:
- 14.07.2011
- Сообщения:
- 644
- Симпатии:
- 61
-
Sahalin
Пользователь- Регистрация:
- 07.10.2011
- Сообщения:
- 24
- Симпатии:
- 0
Убил демона,надпись не пропала((
-
Vegos
Пользователь- Регистрация:
- 16.05.2011
- Сообщения:
- 1.456
- Симпатии:
- 127
Толку убивать его, нужно удалять
-
SeriousAlexej
Пользователь- Регистрация:
- 03.10.2011
- Сообщения:
- 10
- Симпатии:
- 1
Точно такая же проблема. Никто еще не нашел решение? Болванки вроде бы нормальные, образ abgx одобрил, привод, кажись, фурычит, Daemon tools не ставил.
-
Mak
Пользователь- Регистрация:
- 14.07.2011
- Сообщения:
- 644
- Симпатии:
- 61
У меня проблема была в приводе.
Что то с лазером наверно, не пишет двухслойный болванки. Хотя читает.
Записывал в ноуте, там всё пучком и болванки те же и образ.Потом перешёл на фри бут и диски уже не пользую.
Хотя когда комп апгрейдил взял всё же iHAS 124, на всякий случай
-
zaharbaz
Пользователь- Регистрация:
- 07.10.2012
- Сообщения:
- 3
- Симпатии:
- 0
Ребят, достался мне на днях старенький xbox360 2008го года рождения, не шитый.
Покурил мануалы, прошил на LT+3.0, дашборд 14699. Все без проблем.Решил записать игры Skate 3 и Red Dead Redemption.
Убил 3 диска, записывал с разными настройками, которые советуют в интернете. Для записи использовал ImgBurn 2.5.6.0.
Как я понял, для LT+3, все игры нужно записывать с LayerBreak 2133520 что я и делал. Записывал на Вербатиум со скоростью 2,4. С OPC и без.результат — Нераспознанный диск
Гуру подскажите, что не так делаю. С боксом общаюсь второй день.
Спасибо. -
Запомни, ни когда не прописывай LB вручную!!! Для этого есть DVD файл, как раз для таких умников. Верни настройки берна «Вычислить оптимум», или сбрось все на дефолт, и открывай в нем .dvd файл. OPC касается только владельцев приводов прошитых iXtreme Burner MAX.
Суть — LB 2133520 только для XGD3 образов (которые на балванку не влезают), для остальных, LB какой был, тот и остался — 1913760. -
zaharbaz
Пользователь- Регистрация:
- 07.10.2012
- Сообщения:
- 3
- Симпатии:
- 0
Спасибо большое, перед записью спросил в двух местах, надо ли менять LB, говорят типа «конечно, раз у тебя LT+3»
Значит попробую по умолчанию все и скорость 2.4, верно? -
zaharbaz
Пользователь- Регистрация:
- 07.10.2012
- Сообщения:
- 3
- Симпатии:
- 0
Сегодня записывал снова, все по умолчанию, скорость 2.4
при финализации полезли ошибки, результат — вместо игры «открыть лоток»лог:
I 13:05:30 ImgBurn Version 2.5.6.0 started! I 13:05:30 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1) I 13:05:30 Total Physical Memory: 4 193 524 KB - Available: 2 523 848 KB W 13:05:30 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 13:05:30 Initialising SPTI... I 13:05:30 Searching for SCSI / ATAPI devices... I 13:05:31 -> Drive 1 - Info: Optiarc DVD RW AD-7580S FX20 (E:) (ATAPI) I 13:05:31 -> Drive 2 - Info: SNK A3K9MNCD 1.04 (F:) (SCSI) I 13:05:31 -> Drive 3 - Info: SNK A3K9MNCD 1.04 (G:) (SCSI) I 13:05:31 Found 1 DVD±RW/RAM and 2 BD-ROMs! I 13:12:31 Operation Started! I 13:12:31 Source File: D:GamesSkate 3 RUSSkate3_by_riprip_by_rg_dshock.dvd I 13:12:31 Source File Sectors: 3 827 488 (MODE1/2048) I 13:12:31 Source File Size: 7 838 695 424 bytes I 13:12:31 Source File Volume Identifier: DVD_ROM I 13:12:31 Source File Volume Set Identifier: ec67c000MS UDFBridge I 13:12:31 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM) I 13:12:31 Source File Implementation Identifier: Microsoft CDIMAGE UDF I 13:12:31 Source File File System(s): ISO9660; UDF (1.50) I 13:12:31 Destination Device: [0:1:0] Optiarc DVD RW AD-7580S FX20 (E:) (ATAPI) I 13:12:31 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00) I 13:12:31 Destination Media Supported Write Speeds: 2,4x; 4x; 6x I 13:12:32 Destination Media Sectors: 4 173 824 I 13:12:32 Write Mode: DVD I 13:12:32 Write Type: DAO I 13:12:32 Write Speed: 2,4x I 13:12:32 Link Size: Auto I 13:12:32 Lock Volume: Yes I 13:12:32 Test Mode: No I 13:12:32 OPC: No I 13:12:32 BURN-Proof: Enabled I 13:12:34 Write Speed Successfully Set! - Effective: 3 324 KB/s (2,4x) I 13:12:34 Book Type Setting: N/A (Reason: Invalid Command Operation Code) I 13:12:34 Optimal L0 Data Zone Capacity: 1 913 760 I 13:12:34 Optimal L0 Data Zone Method: Copied From Original Disc I 13:12:34 Set L0 Data Zone Capacity Succeeded! I 13:12:39 Filling Buffer... (40 MB) I 13:12:43 Writing LeadIn... I 13:14:29 Writing Session 1 of 1... (1 Track, LBA: 0 - 3827487) I 13:14:29 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3827487) I 13:14:29 Writing Layer 0... (LBA: 0 - 1913759) I 13:34:34 Writing Layer 1... (LBA: 1913760 - 3827487) I 13:54:42 Synchronising Cache... I 13:54:46 Closing Track... I 13:54:48 Finalising Disc... W 13:54:54 Potential 'WaitImmediateIO' Deferred Error - (18%, 0/3) - Session Fixation Error Writing Lead In W 13:54:54 Finalise Disc Failed! - Reason: Session Fixation Error Writing Lead In W 13:54:54 Retrying (1 of 3)... W 13:55:03 Potential 'WaitImmediateIO' Deferred Error - (23%, 0/3) - Session Fixation Error Writing Lead In W 13:55:03 Retry Failed - Reason: Session Fixation Error Writing Lead In W 13:55:03 Retrying (2 of 3)... W 13:55:16 Potential 'WaitImmediateIO' Deferred Error - (18%, 0/3) - Session Fixation Error Writing Lead In W 13:55:16 Retry Failed - Reason: Session Fixation Error Writing Lead In W 13:55:16 Retrying (3 of 3)... W 13:55:53 Potential 'WaitImmediateIO' Deferred Error - (99%, 0/3) - Session Fixation Error Writing Lead Out W 13:55:53 Retry Failed - Reason: Session Fixation Error Writing Lead Out E 14:00:14 Finalise Disc Failed! - Reason: Session Fixation Error Writing Lead In I 14:00:14 Finalising Disc (Last Attempt!)... I 14:02:41 Exporting Graph Data... I 14:02:41 Graph Data File: C:Users1AppDataRoamingImgBurnGraph Data FilesOptiarc_DVD_RW_AD-7580S_FX20_7-ОКТЯБРЬ-2012-Г-_13-12_MKM-003-00_2,4x.ibg I 14:02:41 Export Successfully Completed! I 14:02:41 Operation Successfully Completed! - Duration: 00:50:09 I 14:02:41 Average Write Rate: 3 173 KB/s (2.3x) - Maximum Write Rate: 3 359 KB/s (2.4x) I 14:02:41 Cycling Tray before Verify... W 14:02:56 Waiting for device to become ready... I 14:30:58 Abort Request Acknowledged E 14:30:58 Device Not Ready - Reason: Logical Unit is in process of becoming ready E 14:30:58 Operation Aborted!
уже вся надежда ушла((
-
LeoUA
Пользователь- Регистрация:
- 14.06.2012
- Сообщения:
- 2
- Симпатии:
- 0
Небольшая предыстория: скачал RE 6, записал прошитым приводом, 100% на вербатим, все прошло отлично. Запускаю диск на ящичке с диска игра работает до определенного момента в заставке, потом ошибка. При установке на хард, на 48% проценте ошибка. Я естественно полез в интернеты искать, что да как. И увидел, что люди пишут, что записывают игры шитым приводом на 100% не только на вербатимы.
Мне не дано было найти ни каких мануалов по записи других дисков дисков кроме вербатима шитым приводом на 100%.
По этому у меня возникли такие вопросы к уважаемому сообществу.
1. Как записывать на 100% шитым приводом диске НЕ вербатим?
2. Какие диски нужно использовать?
Заранее спасибо -
Electro
Пользователь- Регистрация:
- 06.12.2011
- Сообщения:
- 993
- Симпатии:
- 101
1.точно так-же, как и вербатим, imgburn-ом
2.пробовать разные, какие запишутся, те и юзать! -
zloj
Пользователь- Регистрация:
- 28.09.2012
- Сообщения:
- 54
- Симпатии:
- 0
Страница 2 из 2
Поделиться этой страницей
As the title says… I get Session Fixation Error
Tried Force package… ImgBurn… Nero 7 Ultra
No one solved it for me…I enclose the logs for ImgBurn and Nero 7 Ultra….. can anyone help?
Thanksss a lot.
Img burn log
I 21:02:30 ImgBurn Version 2.4.2.0 started!
I 21:02:30 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)
I 21:02:30 Total Physical Memory: 1.039.724 KB — Available: 292.680 KB
I 21:02:30 Initialising SPTI…
I 21:02:30 Searching for SCSI / ATAPI devices…
I 21:02:30 Found 1 DVD-ROM/CD-RW and 1 DVD�RW!
I 21:05:53 Operation Started!
I 21:05:53 Source File: H:pubsharedstoredsoftwareBmw Dvd Navi Business Europe 2008-2.nrg
I 21:05:53 Source File Sectors: 2.342.656 (MODE1/2048)
I 21:05:53 Source File Size: 4.797.759.488 bytes
I 21:05:53 Source File Volume Identifier: KN074EU16X11T01
I 21:05:53 Source File Application Identifier: Nero — Burning Rom
I 21:05:53 Source File File System(s): ISO9660; Joliet
I 21:05:53 Destination Device: [0:0:0] BENQ DVD DD EW162I 47F9 (I
I 21:05:53 Destination Media Type: DVD+R DL (Disc ID: RITEK-S04-66) (Speeds: 2,4x)
I 21:05:53 Destination Media Sectors: 4.173.824
I 21:05:53 Write Mode: DVD
I 21:05:53 Write Type: DAO
I 21:05:53 Write Speed: 1x
I 21:05:53 Link Size: Auto
I 21:05:53 Test Mode: No
I 21:05:53 OPC: No
I 21:05:53 BURN-Proof: Enabled
I 21:05:53 Book Type Setting: DVD-ROM
I 21:05:53 Advanced Settings — WOPC: Yes
I 21:05:53 Optimal L0 Data Zone Capacity: 1.171.328
I 21:05:53 Optimal L0 Data Zone Method: ECC Block Boundary
I 21:05:53 Filling Buffer… (40 MB)
I 21:05:55 Writing LeadIn…
W 21:06:10 Failed to Write Sectors 0 — 31 — Reason: Session Fixation Error Writing Lead In
W 21:06:10 Retrying (1 of 20)…
W 21:06:23 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 21:06:23 Retrying (2 of 20)…
W 21:06:36 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 21:06:36 Retrying (3 of 20)…
W 21:06:50 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 21:06:50 Retrying (4 of 20)…
W 21:07:04 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 21:07:04 Retrying (5 of 20)…
W 21:07:19 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 21:07:19 Retrying (6 of 20)…
W 21:07:33 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 21:07:33 Retrying (7 of 20)…
W 21:07:48 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 21:07:48 Retrying (8 of 20)…
W 21:08:02 Retry Failed — Reason: Session Fixation Error Writing Lead In
W 21:08:02 Retrying (9 of 20)…
W 21:08:13 Retry Failed — Reason: Power Calibration Area Is Full
W 21:08:13 Retrying (10 of 20)…
W 21:08:14 Retry Failed — Reason: Power Calibration Area Is Full
W 21:08:14 Retrying (11 of 20)…
W 21:08:15 Retry Failed — Reason: Power Calibration Area Is Full
W 21:08:15 Retrying (12 of 20)…
W 21:08:16 Retry Failed — Reason: Power Calibration Area Is Full
W 21:08:16 Retrying (13 of 20)…
W 21:08:16 Retry Failed — Reason: Power Calibration Area Is Full
W 21:08:16 Retrying (14 of 20)…
W 21:08:17 Retry Failed — Reason: Power Calibration Area Is Full
W 21:08:17 Retrying (15 of 20)…
W 21:08:18 Retry Failed — Reason: Power Calibration Area Is Full
W 21:08:18 Retrying (16 of 20)…
W 21:08:19 Retry Failed — Reason: Power Calibration Area Is Full
W 21:08:19 Retrying (17 of 20)…
W 21:08:20 Retry Failed — Reason: Power Calibration Area Is Full
W 21:08:20 Retrying (18 of 20)…
W 21:08:20 Retry Failed — Reason: Power Calibration Area Is Full
W 21:08:20 Retrying (19 of 20)…
W 21:08:21 Retry Failed — Reason: Power Calibration Area Is Full
W 21:08:21 Retrying (20 of 20)…
W 21:08:22 Retry Failed — Reason: Power Calibration Area Is Full
E 21:08:32 Failed to Write Sectors 0 — 31 — Reason: Session Fixation Error Writing Lead In
I 21:08:32 Synchronising Cache…
W 21:08:42 User opted to skip the ‘Close Track/Session/Disc’ functions.
E 21:08:42 Failed to Write Image!
E 21:08:42 Operation Failed! — Duration: 00:02:49
I 21:08:42 Average Write Rate: N/A — Maximum Write Rate: N/ANero log:
Windows XP 5.1
IA32
WinAspi: —
ahead WinASPI: File ‘C:Program FilesNeroNero 7CoreWnaspi32.dll’: Ver=2.0.1.74, size=164112 bytes, created 11/2/2004 2:54:32
NT-SPTI used
Nero Version: 7.5.7.0
Internal Version: 7, 5, 7, 0
Recorder: <BENQ DVD DD EW162I> Version: 47F9 — HA 1 TA 3 — 7.5.7.0
Adapter driver: <USB 2.0> HA 1
Drive buffer : 2048kB
Bus Type : set to ATAPI (3) -> ATAPI, detected: ?
CD-ROM: <SCSIVAX DVD/CD-ROM >Version: 2.7a — HA 1 TA 2 — 7.5.7.0
Adapter driver: <SCSI> HA 1
=== Scsi-Device-Map ===
CdRomPeripheral : MAT****A UJDA775 DVD/CDRW atapi Port 0 ID 0 DMA: On
DiskPeripheral : ST96812AS iaStor Port 1 ID 0 DMA: On
CdRomPeripheral : SCSIVAX DVD/CD-ROM 2.7a Vax347s Port 2 ID 0 DMA: Off
CdRomPeripheral : NERO IMAGEDRIVE2 2.26 imagedrv Port 3 ID 0 DMA: Off
=== CDRom-Device-Map ===
MAT****A UJDA775 DVD/CDRW E: CDRom0
SCSIVAX DVD/CD-ROM F: CDRom2
NERO IMAGEDRIVE2 G: CDRom1
BENQ DVD DD EW162I I: CDRom3
=======================
AutoRun : 1
Excluded drive IDs:
WriteBufferSize: 83886080 (0) Byte
BUFE : 0
Physical memory : 1015MB (1039724kB)
Free physical memory: 192MB (196672kB)
Memory in use : 81 %
Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)
11.10.2008
Burn DVD Image
9:16:05 #1 Text 0 File SCSIPassThrough.cpp, Line 583
LockMCN — completed sucessfully for IOCTL_STORAGE_MCN_CONTROL9:16:05 #2 Text 0 File Burncd.cpp, Line 3435
Turn on Disc-At-Once, using DVD media9:16:05 #3 Text 0 File DlgWaitCD.cpp, Line 301
Last possible write address on media: 4173823 (927:30.73, 8151MB)
Last address to be written: 2342655 (520:35.30, 4575MB)9:16:05 #4 Text 0 File DlgWaitCD.cpp, Line 313
Write in overburning mode: NO (enabled: CD)9:16:05 #5 Text 0 File DlgWaitCD.cpp, Line 2863
Recorder: BENQ DVD DD EW162I, Media type: DVD+R9 Double Layer
Disc Manufacturer ID: RITEK, Media Type ID: S04, Product revision number: 66
Disc Application Code: 0, Extended Information Indicators: 09:16:05 #6 Text 0 File DlgWaitCD.cpp, Line 485
>>> Protocol of DlgWaitCD activities: <<<
=========================================9:16:05 #7 Text 0 File ThreadedTransferInterface.cpp, Line 820
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 (2 — CD-ROM Mode 1, Joliet)
2 indices, index0 (150) not provided
original disc pos #0 + 2342656 (2342656) = #2342656/520:35.31
not relocatable, disc pos for caching/writing not required/not required, no patch infos
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2342656 blocks [Main]
—————————————————————9:16:05 #8 Text 0 File ThreadedTransferInterface.cpp, Line 1033
Prepare recorder [BENQ DVD DD EW162I] for write in CUE-sheet-DAO
DAO infos:
==========
MCN: «»
TOCType: 0x00; Session Closed, disc fixated
Tracks 1 to 1: Idx 0 Idx 1 Next Trk
1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 4797759488, ISRC «»
DAO layout:
===========
___Start_|____Track_|_Idx_|_CtrlAdr_|_____Size_|__ ____NWA_|_RecDep__________
0 | lead-in | 0 | 0x41 | 0 | 0 | 0x00
0 | 1 | 0 | 0x41 | 2342656 | 2342656 | 0x00
0 | 1 | 1 | 0x41 | 2342656 | 2342656 | 0x00
2342656 | lead-out | 1 | 0x41 | 0 | 0 | 0x009:16:05 #9 Text 0 File SCSIPassThrough.cpp, Line 41
SPTILockVolume — completed successfully for FCTL_LOCK_VOLUME9:16:05 #10 Phase 36 File dlgbrnst.cpp, Line 1746
Burn process started at 2.4x (3,324 KB/s)9:16:05 #11 Text 0 File ThreadedTransferInterface.cpp, Line 2730
Verifying disc position of item 0 (not relocatable, no disc pos, no patch infos, orig at #0): write at #09:16:05 #12 Text 0 File DVDPlusDualLayer.cpp, Line 470
Disc finalized, LBA total Image size: 2342656 (4575MB), Last LBA L0: 1171343 (2287MB)9:16:05 #13 Text 0 File DVDPlusDualLayer.cpp, Line 635
L0 Data Zone Capacity set to 1171344 (11DF90h, 2287MB) -> OK, confirmed setting9:16:05 #14 CDR -1205 File DVDPlusDualLayer.cpp, Line 662
Burning Layer 19:16:05 #15 Text 0 File DVDPlusDualLayer.cpp, Line 672
Start writing layer 1 at address 0 (0h)
Recording mode: unknown Recording Mode9:16:05 #16 Text 0 File Cdrdrv.cpp, Line 9234
—- DVD Structure: Physical Format Information (00h) —-
Media Type: 0, Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
Book Type: DVD+R DL (14), Part Version: 1.0x (1)
Disc Size: 120 mm, Maximum Rate: <not specified> (F h)
Number of Layers: 2, Track Path: Opposite Track Path (OTP), Layer Type: recordable
Linear Density: 0,293 um/bit, Track Density: 0,74 um/track
Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW, DVD+R/+RW)
End Physical Sector Number of Data Area: FCFFFF h
End Sector Number in Layer 0: 14DF90 h (LBN: 11DF90 h, 2287 MB)
Data in Burst Cutting Area (BCA) does not exist
Disc Application Code: 0 / 0 h
Extended Information indicators: 0 h
Disc Manufacturer ID: RITEK…
Media type ID: S04
Product revision number: 66
Number of Physical format information bytes in use in ADIP up to byte 63: 64
Media Specific [16..63]:
00 00 00 52 49 54 45 4B — 00 00 00 53 30 34 42 40 …RITEK…S04B@
25 25 37 10 00 2C 6C 00 — 2C 6C 20 1F 0C 0C 14 14 %%7..,l.,l……
02 01 01 20 00 20 1F 0C — 0C 14 14 02 01 01 20 00 …………….9:16:05 #17 Text 0 File DVDR.cpp, Line 7051
Drive: BENQ DVD DD EW162I
Book Type request [gen]: DVD-ROM, write to EEPROM
Changing the Book Type was finished successfully, return code 09:16:05 #18 CDR -1211 File DVDR.cpp, Line 6123
Book Type set to: DVD-ROM9:16:05 #19 Text 0 File DVDPlusRW.cpp, Line 662
Start write address at LBA 0
DVD high compatibility mode: Yes9:16:26 #20 SPTI -1176 File SCSIPassThrough.cpp, Line 293
I: CdRom3: SCSIStatus(x02) WinError(0) NeroError(-1176)
Sense Key: 0x03 (KEY_MEDIUM_ERROR)
Sense Code: 0x72
Sense Qual: 0x01
CDB Data: 0x2A 00 00 00 00 00 00 00 20 00 00 00
Sense Area: 0x70 00 03 00 00 00 00 12 00 00 00 00 72 01
Buffer x06f02400: Len x10000
0x00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 009:16:26 #21 CDR -1176 File Writer.cpp, Line 278
Session fixation error
I: BENQ DVD DD EW162I9:16:26 #22 SPTI -1176 File SCSIPassThrough.cpp, Line 293
I: CdRom3: SCSIStatus(x02) WinError(0) NeroError(-1176)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x72
Sense Qual: 0x03
CDB Data: 0x5B 01 05 00 00 00 00 00 00 00 00 00
Sense Area: 0x70 00 05 00 00 00 00 12 00 00 00 00 72 039:16:26 #23 Phase 127 File dlgbrnst.cpp, Line 1746
Generating DVD high compatibility borders9:16:26 #24 Text 0 File DVDR.cpp, Line 7051
Drive: BENQ DVD DD EW162I
Book Type request [gen]: DVD-ROM, write to EEPROM
Changing the Book Type was finished successfully, return code 09:16:26 #25 CDR -1176 File WriterStatus.cpp, Line 161
Session fixation error
I: BENQ DVD DD EW162I9:16:26 #26 TRANSFER -24 File WriterStatus.cpp, Line 161
Could not perform end of Disc-at-once9:16:26 #27 Phase 38 File dlgbrnst.cpp, Line 1746
Burn process failed at 2.4x (3,324 KB/s)9:16:26 #28 Text 0 File Cdrdrv.cpp, Line 10459
DriveLocker: UnLockVolume completed9:16:26 #29 Text 0 File SCSIPassThrough.cpp, Line 583
UnLockMCN — completed sucessfully for IOCTL_STORAGE_MCN_CONTROLExisting drivers:
File ‘DriversCDRALW2K.SYS’: Ver=8.0.0.212 , size=2560 bytes, created 10/5/2006 4:42:42
File ‘DriversPXHELP20.SYS’: Ver=3.00.67a, size=43872 bytes, created 2/23/2008 4:38:33 (Prassi/Veritas driver for win 2K)
File ‘Driversscsiport.sys’: Ver=5.1.2600.2180 (xpsp_sp2_rtm.040803-2158), size=96256 bytes, created 8/4/2004 8:05:44 (Adapter driver for src)
Registry Keys:
HKLMSoftwareMicrosoftWindows NTCurrentVersionWinLogonAllocateCDROMs : 0 (Security Option)
(USB)