DeathStalker
-
Posts
50 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by DeathStalker
-
-
Ok, interesting tried your advice, and also burned at 4x - 1 successful burn so far (keeps fingers crossed!)
-
I'll try those things. The discs burn just fine for the first couple of months, then the drives seem to "die" on them - and this is ANY brand (LiteOn, Asus, LG, Sony, HP - only one I haven't tried is Plextor). And I've tried multiple firmwares on the other drives.
-
I 21:07:12 Initialising SPTI...I 21:07:12 Searching for SCSI / ATAPI devices...I 21:07:13 -> Drive 1 - Info: ASUS DRW-24B1ST i 1.00 (N:) (SATA)I 21:07:13 Found 1 DVD±RW/RAMI 21:07:46 Operation Started!I 21:07:46 Source File: XXXXXXXXXXXXI 21:07:46 Source File Sectors: 4,124,928 (MODE1/2048)I 21:07:46 Source File Size: 8,447,852,544 bytesI 21:07:47 Source File Volume Identifier:I 21:07:47 Source File Volume Set Identifier: 44319AE2003EF0F5I 21:07:47 Source File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER!I 21:07:47 Source File Implementation Identifier: ImgBurnI 21:07:47 Source File File System(s): ISO9660, UDF (1.02)I 21:07:47 Destination Device: [5:0:0] ASUS DRW-24B1ST i 1.00 (N:) (SATA)I 21:07:47 Destination Media Type: DVD+R DL (Disc ID: MBIPG101-R10-65)I 21:07:47 Destination Media Supported Write Speeds: 4x, 6x, 8xI 21:07:47 Destination Media Sectors: 4,173,824I 21:07:47 Destination Media L0 Data Zone Capacity: 2,086,912 (Changeable: Yes)I 21:07:47 Write Mode: DVDI 21:07:47 Write Type: DAOI 21:07:47 Write Speed: 8xI 21:07:47 DVD+R DL Reserve Track: NoI 21:07:47 Link Size: AutoI 21:07:47 Lock Volume: YesI 21:07:47 Test Mode: NoI 21:07:47 OPC: YesI 21:07:47 BURN-Proof: EnabledI 21:07:47 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x)I 21:07:47 Book Type Setting: N/A (Reason: Invalid Command Operation Code)I 21:07:47 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: YesI 21:08:32 Optimal L0 Data Zone Capacity: 2,062,464I 21:08:32 Optimal L0 Data Zone Method: Copied From Original DiscI 21:08:32 Set L0 Data Zone Capacity Succeeded!I 21:08:32 L0 Data Zone Capacity - Effective: 2,062,464I 21:08:32 Filling Buffer... (512 MiB)I 21:08:37 Writing LeadIn...I 21:08:43 Writing Session 1 of 1... (1 Track, LBA: 0 - 4124927)I 21:08:43 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4124927)I 21:08:43 Writing Layer 0... (LBA: 0 - 2062463)I 21:17:29 Writing Layer 1... (LBA: 2062464 - 4124927)I 21:26:25 Synchronising Cache...I 21:26:31 Closing Track...I 21:26:32 Finalising Disc...I 21:27:07 Operation Successfully Completed! - Duration: 00:19:20I 21:27:07 Average Write Rate: 7,768 KiB/s (5.7x) - Maximum Write Rate: 10,903 KiB/s (8.1x)I 21:27:07 Cycling Tray before Verify...W 21:27:14 Waiting for device to become ready...I 21:27:26 Device Ready!I 21:27:26 Operation Started!I 21:27:26 Source Device: [5:0:0] ASUS DRW-24B1ST i 1.00 (N:) (SATA)I 21:27:26 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MBIPG101-R10-65)I 21:27:26 Source Media Supported Read Speeds: 4x, 6x, 8x, 12xI 21:27:26 Source Media Supported Write Speeds: 4x, 6x, 8xI 21:27:26 Source Media Sectors: 4,124,928 (Track Path: OTP - L0: 2,062,464 - L1: 2,062,464)I 21:27:26 Source Media Size: 8,447,852,544 bytesI 21:27:26 Image File: XXXXXXXXXXXXXXI 21:27:26 Image File Sectors: 4,124,928 (MODE1/2048)I 21:27:26 Image File Size: 8,447,852,544 bytesI 21:27:26 Image File Volume Identifier:I 21:27:26 Image File Volume Set Identifier: 44319AE2003EF0F5I 21:27:26 Image File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER!I 21:27:26 Image File Implementation Identifier: ImgBurnI 21:27:26 Image File File System(s): ISO9660, UDF (1.02)I 21:27:26 Read Speed (Data/Audio): MAX / MAXI 21:27:27 Hardware Read Error Retries: 20I 21:27:28 Read Speed - Effective: 4.8x - 12x, 12x - 4.8xI 21:27:28 Verifying Session 1 of 1... (1 Track, LBA: 0 - 4124927)I 21:27:28 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 4124927)I 21:27:28 Verifying Layer 0... (LBA: 0 - 2062463)I 21:33:30 Verifying Layer 1... (LBA: 2062464 - 4124927)W 21:39:32 Failed to Read Sectors 4111360 - 4111391 - Reason: L-EC Uncorrectable ErrorW 21:39:43 Failed to Read Sector 4111385 - Reason: L-EC Uncorrectable ErrorW 21:39:43 Sector 4111385 maps to File: XXXXXXXXXW 21:39:48 Retrying (1 of 20)...W 21:39:54 Retry Failed - Reason: L-EC Uncorrectable ErrorW 21:39:59 Retrying (2 of 20)...W 21:40:06 Retry Failed - Reason: L-EC Uncorrectable ErrorW 21:40:10 Retrying (3 of 20)...W 21:40:17 Retry Failed - Reason: L-EC Uncorrectable ErrorW 21:40:21 Retrying (4 of 20)...W 21:40:28 Retry Failed - Reason: L-EC Uncorrectable Erroretc .....And yes, I have also tried 4x - same issues. Not a firmware issue, as this is the only firmware for this model (this is Rev i, so v1.03 is not compatible)
-
Same mfr (diff codes), but I get a LOT of L-EC Uncorrectable Errors on the DL discs - *never* on SL discs - almost always at ~99% of verify.
ImgBurn is the only program I know of that has the VERIFY function - anyone know of any others that I could use for a comparison?
I have tried different I/o interfaces, but still get the error.
It is not "cheap" media either.
Thanks.
-
Ok, a month gone by an no response?
I *love* ImgBurn, but absolutely will not use it to burn audio CDs, it is too much of a PITA. I would very much like to know why the d-n-d method (and be able to set 0 sec gap and CD-Text) can't be enabled in it. It would make it the *only* burn software necessary.
Thanks.
-
Is there ANY way that ImgBurn can simply drag & drop files to burn to an audio CD and be able to set a 0 sec gap between tracks, as well as CD-Text the way that Nero does?
It would be VERY helpful (creating the CUE sheet is just a PITA).
I can understand needing to have the appropriate plugin for file type (flac, wv, ape, etc)
Thank you!
-
Ah, am running avast!, so will check that. Thanks!
Adding it to the Exclusions seems to have resolved the issue.
Thanks much!
-
I just installed ImgBurn on my wife's system (Win7 x64 Home Premium). It installed with no errors and starts up fine, then just closes by itself (no errors) after a few seconds.
Any ideas?
Thanks!
(Even setting Compatibility to Run As Admin doesn't stop it from closing)
-
Ok, that makes a bit more sense (my bad on the kb vs mb, lol). I thought the error was from ImgBurn, not Windows (kinda hard to tell if you're not a programmer
-
It's quite simple, just don't use such a big buffer if your machine can't handle it.
Of course I already told you that here :-
Yes, you said that, but you didn't *explain* it. I've got 8gb of RAM and a Dual Core 3.1 cpu. Please explain how my system can't handle a 512k buffer - AND why it only occurs when trying to burn files/folders but images are fine.
Thank you.
-
Reason: Not enough storage is available to process this command.
Followed by -
Failed to initialise FIFO Buffer (536,870,912 bytes)
This ONLY happens when trying to burn files/folders, and not *every* time.
I 15:07:32 ImgBurn Version 2.5.6.0 started!
I 15:07:32 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)
I 15:07:32 Total Physical Memory: 8,387,052 KB - Available: 2,140,968 KB
I 15:07:32 Initialising SPTI...
I 15:07:32 Searching for SCSI / ATAPI devices...
I 15:07:33 -> Drive 1 - Info: (ATA)
I 15:07:33 -> Drive 2 - Info: (SCSI)
I 15:07:33 Found 1 DVD±RW/RAM and 1 BD-ROM/HD DVD-ROM!
I 15:09:53 Operation Started!
I 15:09:53 Building Image Tree...
I 15:09:53 Calculating Totals...
I 15:09:53 Preparing Image...
I 15:09:53 Contents: 12 Files, 2 Folders
I 15:09:53 Content Type: DVD Video
I 15:09:53 Data Type: MODE1/2048
I 15:09:53 File System(s): ISO9660, UDF (1.02)
I 15:09:53 Volume Label: XXXXXXXX
I 15:09:53 IFO/BUP 32K Padding: Enabled
I 15:09:53 Region Code: 1, 2, 3, 4, 5, 6, 7, 8
I 15:09:53 TV System: NTSC
I 15:09:53 Size: 3,117,830,144 bytes
I 15:09:53 Sectors: 1,522,378
I 15:09:53 Image Size: 3,118,465,024 bytes
I 15:09:53 Image Sectors: 1,522,688
I 15:09:54 Operation Successfully Completed! - Duration: 00:00:01
The popup for the Size appears, I click OK, then I get the VirtulAlloc, followed by the FIFO.
There are NO problems *creating* an image, OR burning an image - only when burning files/folders - regardless of the type (Joliet/UDF)
Thanks for any assistance. (It's getting quite annoying having to build an image for everything first).
-
Hi Cynthia!
I wanted to update you on things - did a LOT of research today and posyed my findings over on MYCE - http://club.myce.com/f44/new-liteon-plds-patched-firmware-thread-new-267641/index46.html#post2604360
-
I've searched for that MID (and Googled), but found few results - you'll also see that I've posted quite frequently over there (http://club.myce.com/f87/asus-drw-24b3st-24b3lt-results-discussion-316003/ & http://club.myce.com/f44/ - among others)
Seems lots of people have the 24B3ST and the 21B3ST, but few have the 243BLT
-
So how can I find a burner that likes them? Doesn't seem to be a lot of info on them available. They're Kodak branded, and Kodak has been *exceptionally* supportive in my efforts to get successful burns (they've replaced a couple batches of them for me) - I've also contacted Asus regarding their firmware and writing strategies for the drive.
I believe the HP 1270i (which is *apparently* a LiteOn-based drive, but I don't know the specifics) handles them ok, so I'm also trying tofind out of I can crossflash the drive to the 1270i (NOT the d or the r!), but I've been unable to find any firmware for the 1270i (might have to break down and buy one from BB to copy the firmware from it). If I do "rent" one from BB is there a way to tell what it's based on without opening it up?
Thanks!
-
Yes, that seems to be the consensus. I've already contacted Asus to see if I can get any higher level support from them. Considering MBI is the 3rd largest mfr in the world, there's really no excuse for their MIDs to not be included in current firmware (imho).
-
It's an Asus 24B3LT. I've tried crossflashing it to a LiteOn iHAS424B as well as the Plextor PX-890SA, but they all seem to burn/fail about the same (yes, latest firmwares - from FWHQ
-
Ok. As I've indicated in other posts, I've been having considerable problems with a couple of specific Media IDs and am trying to do whatever I can to mitigate the problems.
MBIPG101-R10-65 & MKM-001-00 DL discs (RICOHJPN-D01-67 burn almost flawlessly).
-
The selection defaults to SPTI - Microsoft, and I know ASPI/ASAPI are out-dated, but what about Elby & P-C? How do they compare? (Under Win 7 x64)
Thanks!
-
Hi Lightning UK!
First off, I'd like to thank you for the BEST burning program around!
I have a small "favor" to ask. I have been having trouble with a couple of specific Manufacturer IDs on some discs (MBIPG101-R10-65 & MKM-001-00) which result in about a 90% failure rate even when burning at 4x (2.4x in the case of the MKMs - both dual layer). I have spoken with the COO of the media distributor who has assured me the problem lies not with the quality of the discs, but with the burner's firmware not including the proper write strategies for them to burn properly. I have contacted the burned manufacturer to inform them of this situation, and they are forwarding it to their department that handles the firmware updates. The failure code I get with ImgBurn is (the well documented) "Failed to Read Sector XXXXXXX - Reason: L-EC Uncorrectable Error"
The favor would simply be a detailed response on what that error indicates and why it is occurring only with these MIDs (the discs burn just fine on a couple other burners and other MIDs burn just fine on this one), and this is the same media (and MBI code) sold under half a dozen major band names. I would like to be able to forward your response to the burner manufacturer as supporting documentation that a firmware update is in order.
Thank you SO much for your assistance!
==============================
***Hey Lightning UK! As you can see by my latest post below, a response is no longer necessary - the cause of the error IS clear; missing MID in the firmware of all 3 drives.
-
Ok but that doesn't change the answer.
If the API is failing because there's not enough memory available in the format it needs it, you need to make the buffer smaller.
I assume you mean 'recover' rather than 're-allocate'. A hdd should easily be able to cope with any speed burn (it's only ~32mb/s at 24x after all) - unless it's a really slow old one, heavily fragmented and/or being taxed by other applications.
Building an ISO and then burning it will be easier on the system that trying to burn lots of little files on-the-fly. You have to take the antivirus overhead into account when you do that, along with general random access involved in burning lots of little files.
Yes, I meant "recover" - yes, the disc is heavily fragmented, as it gets the most use and changes. I'm just surprised it stopped working all of a sudden (I don't burn at >16x, FWIW). The files in question are 350mb-500mb. The last one had only 5x500mb files.
==========================
I guess I should also add that it burns VIDEO_TS files (UDF Format) just fine - the *ONLY* problem is with Joliet Format.
-
Stop using such a big buffer.
For whatever reason, the 'VirtualAlloc' API function is unable to allocate 512MB.
I've had it that way for months and it's never been a problem (as a matter of fact, I made a post on how to change it to that). When it was set to the default, I had a lot of pauses waiting for it to re-allocate.
And it has no problems burning ISO/UDFs of any size, JUST straight Joliet structures.
-
All of a sudden (with no system changes, to my knowledge), ImgBurn has stopped burning files in Joliet. They will compile just fine into an ISO image, but no longer burn directly. This is, understandingly, rather frustrating.
VirtualAlloc Failed!
Reason: Not enough storage is available to process this command.
Followed by -
Failed to initialise FIFO Buffer (536,870,912 Bytes)
Any ideas for a solution?
Thanks much!
-
Ok, duh! I feel foolish now. Somehow I missed that tab. Working fine now
Thanks.
-
Hello:
I have adjusted the Buffer Size from the default of 40mb to 512mb, and it displays as 512mb in the settings every time I open the program and check Settings, yet when I burn, the log display indicates that the Buffer Size is still the default 40mb.
How can I ensure that the size is, in fact, 512mb?
Using Win7 64-bit, ImgBurn v2.5.5.0.
Thanks much.
I/O Errors *ONLY* on DL Discs
in ImgBurn Support
Posted
Ok, so this makes things even more ....... interesting (more like a PAIN, but ....)
I decided to shell out for a Plextor (retail, not bulk) and got the PX-891SAW.
SAME issue.
Could you explain what turning off the hardware retries does, and how that would not still result in a bad burn?
Very frustrated with this
Thanks.