avada
-
Posts
22 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by avada
-
-
Well, I removed the drive in windows, switched ports and cable ends and now I had a successful testwrite. So it looks like one of them fixed the problem...
-
Hi!
Had a write failure last time I wanted to write a cd, right at the start. Can't comment much on it. Here is the log. What does this mean?
; //****************************************\\ ; ImgBurn Version 2.5.5.0 - Log ; szombat, 15 október 2011, 22:47:57 ; \\****************************************// ; ; I 22:34:40 ImgBurn Version 2.5.5.0 started! I 22:34:40 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1) I 22:34:40 Total Physical Memory: 4 192 756 KB - Available: 1 872 376 KB W 22:34:40 Drive S:\ (FAT32) does not support single files > 4 GB in size. I 22:34:40 Initialising SPTI... I 22:34:40 Searching for SCSI / ATAPI devices... I 22:34:40 -> Drive 1 - Info: PLEXTOR DVDR PX-810SA 1.01 (F:) (SATA) I 22:34:40 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (G:) (SCSI) I 22:34:40 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (H:) (SCSI) I 22:34:40 -> Drive 4 - Info: ELBY CLONEDRIVE 1.4 (I:) (SCSI) I 22:34:40 -> Drive 5 - Info: ELBY CLONEDRIVE 1.4 (J:) (SCSI) I 22:34:40 Found 1 DVD±RW/RAM and 4 BD-ROM/HD DVD-ROMs! I 22:35:02 Operation Started! I 22:35:02 Source File: D:\Letöltés\Yuri Bashmet - Brahms - Viola Sonatas.wav.cue I 22:35:02 Source File Sectors: 209 672 (AUDIO/2352) I 22:35:02 Source File Size: 493 148 544 bytes I 22:35:02 Source File Volume Identifier: Yuri Bashmet - Brahms - Viola Sonatas I 22:35:02 Source File File System(s): None I 22:35:02 Destination Device: [4:0:0] PLEXTOR DVDR PX-810SA 1.01 (F:) (SATA) I 22:35:02 Destination Media Type: CD-R (Disc ID: 97m15s17f, Ritek Co.) (Speeds: 4x; 10x; 16x; 24x; 32x) I 22:35:02 Destination Media Sectors: 359 843 I 22:35:02 Write Mode: CD I 22:35:02 Write Type: SAO I 22:35:02 Write Speed: 4x I 22:35:02 Lock Volume: Yes I 22:35:02 Test Mode: No I 22:35:02 OPC: No I 22:35:02 BURN-Proof: Enabled I 22:35:02 Write Speed Successfully Set! - Effective: 705 KB/s (4x) I 22:35:03 Filling Buffer... (40 MB) I 22:35:03 Writing LeadIn... (CD-TEXT) W 22:35:03 Failed to Write Sectors -12508 - -11827 - Reason: Unknown (ASC: 0x91, ASCQ: 0x00) W 22:35:03 Retrying (1 of 20)... W 22:35:03 Retry Failed - Reason: Invalid Address For Write W 22:35:03 Retrying (2 of 20)... W 22:35:03 Retry Failed - Reason: Invalid Address For Write W 22:35:03 Retrying (3 of 20)... W 22:35:03 Retry Failed - Reason: Invalid Address For Write W 22:35:03 Retrying (4 of 20)... W 22:35:03 Retry Failed - Reason: Invalid Address For Write W 22:35:03 Retrying (5 of 20)... W 22:35:03 Retry Failed - Reason: Invalid Address For Write W 22:35:03 Retrying (6 of 20)... W 22:35:03 Retry Failed - Reason: Invalid Address For Write W 22:35:04 Retrying (7 of 20)... W 22:35:04 Retry Failed - Reason: Invalid Address For Write W 22:35:04 Retrying (8 of 20)... W 22:35:04 Retry Failed - Reason: Invalid Address For Write W 22:35:04 Retrying (9 of 20)... W 22:35:04 Retry Failed - Reason: Invalid Address For Write W 22:35:04 Retrying (10 of 20)... W 22:35:04 Retry Failed - Reason: Invalid Address For Write W 22:35:04 Retrying (11 of 20)... W 22:35:04 Retry Failed - Reason: Invalid Address For Write W 22:35:04 Retrying (12 of 20)... W 22:35:04 Retry Failed - Reason: Invalid Address For Write W 22:35:04 Retrying (13 of 20)... W 22:35:04 Retry Failed - Reason: Invalid Address For Write W 22:35:04 Retrying (14 of 20)... W 22:35:04 Retry Failed - Reason: Invalid Address For Write W 22:35:04 Retrying (15 of 20)... W 22:35:04 Retry Failed - Reason: Invalid Address For Write W 22:35:04 Retrying (16 of 20)... W 22:35:04 Retry Failed - Reason: Invalid Address For Write W 22:35:04 Retrying (17 of 20)... W 22:35:04 Retry Failed - Reason: Invalid Address For Write W 22:35:04 Retrying (18 of 20)... W 22:35:04 Retry Failed - Reason: Invalid Address For Write W 22:35:04 Retrying (19 of 20)... W 22:35:04 Retry Failed - Reason: Invalid Address For Write W 22:35:04 Retrying (20 of 20)... W 22:35:04 Retry Failed - Reason: Invalid Address For Write E 22:35:44 Failed to Write Sectors -12508 - -11827 - Reason: Unknown (ASC: 0x91, ASCQ: 0x00) I 22:35:44 Writing Sectors... I 22:35:44 Synchronising Cache... W 22:35:56 User opted to skip the 'Close Track/Session/Disc' functions. E 22:35:56 Failed to Write Image! E 22:35:56 Operation Failed! - Duration: 00:00:53 I 22:35:56 Average Write Rate: N/A - Maximum Write Rate: N/A I 22:47:49 Close Request Acknowledged I 22:47:49 Closing Down...
-
Imgburn lets me put a "." as the last character of a folder name, but instead of a dot I get something like "#1B5D". I suppose the last character can't be a dot, so imgburn shouldn't let me put a dot at the end of a folder name.
-
Ok so the real problem is that your drive had a 'Write Error' when trying to burn to the disc.
Have you also tried the 1.22 firmware?
Try setting the write speed to one of the other available ones, it might actually do a better job.
I 14:01:34 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 6x, 8x)I suppose the answer is for me. (Since I had a write error and not aspen). I have a plextor px-810sa. And since last time I succesfully burned another dual layer verbatim, so I guess that particular disc was faulty or might have been sratched/stained accidentally.
-
There's normally an error before the 'Invalid Address For Write' one and it's that one you should be paying attention to.
I didn't notice that. In my case it was: "Failed to Write Sectors 3427392 - 3427423 - Reason: Write Error"
-
This "Invalid Address For Write" error surely means that there is something wrong with the disc? Or could it be something else. Because I had this error with a a verbatim +R dual layer disc. I didn't have any problems with any others before this.
-
Any hints as to some of the new features ?
I suppose the build mode will be revamped and multi session will be added. -> click
-
It'll be added when build mode gets a revamp to make it more 'explorer' like.
Don't ask when that'll happen because I don't know yet.
Looking forward to it.
-
Aside from the issue of whether a multisession feature is needed, I am wondering if this feature is quite difficult to program into the app.
I don't think that it would take more than a few hours. I think its not much more than adding a checkbox so that the program wouldn't close the disk, making imgburn to check the disk and calculating the free space. And if I understand correctly imgburn can write multi session disks using a .cue file, so it's just adding some gui elements.
-
It would be a good thing if burning wouldn't start when pressing cancel while filling the buffer. It makes sense. Sometimes a user might realize starting the process that he forgot something (like disc label, or setting the correct burning speed), or did something stupid (forgot to put all of the files for writing ).
-
Multisession Is only missed by Scrooge and anyway 1 person is hardly a lot of people or at a push 2
A disc to be burnt is either full or no need to be written.
But do not get too upset about it hardly the end of the world if you have to use 500 meg to install nero
:& Nero is for masochists. I don't think there is any possibility that I ever consider installing Nero.
-
I can't understand why multi session is added. It is missed by a lot of people.
-
Nope, post number 4 (above) still applies.
-
I think it would be a very useful feature.
-
So in short, I don't know when (if ever) it'll be implemented. Sorry.
-
No. Doubtful. What is the meaning of life?
I don't know.
-
You might try the search function and look for 'multi session'. This has been asked and answered many, many times.
I found only a few topics wich were old. The answers were like:"Maybe one day" Is that day near?
Will it be implemented in the next version? And when it will be released? In a month, or in a few months? -
I would like to suggest some features, that I think would be useful. First Cue/bin support, I'm missing that very often (possibly I'm not the only one). I miss multi session support the most. Is it possible that it will be implemented in the near future?
And the possibility to create folders in build mode would be nice.
-
avada,
Please don't hijack other peoples threads. Your question is more likely to be answered if you start your own one.
You're attempting to overburn and the drive isn't having it. You should have had a warning message to that affect when you started off the burn.
So basically, your image (or rather the files you're attempting to burn) is too big for the disc.
Thanks for the reply. Next time I will start an own.
-
I get this error message when I'm triyng to burn in build mode. It worked previously without problem.
-
Hi!
I like imgburn but I am missing some features in build mode. I use build mode only for burning directly to cd. It would be better if it were possible to create folders in build mode. And I'm missing multisession support. If these were implemented I would hardly use anithing else at all. (Except for audio cd-s)
Can I burn XGD3 games with Samsung SH-224BB?
in ImgBurn Support
Posted · Edited by avada
Hello!
I looked around, some people reported it working without any details, but it's generally missing from lists of drives wich succeed.
Also settings are confusing. Some guides suggest setting OPC off or on, disable burnproof. Also sometimes Force Hypertuning is mentioned. But where is that setting?
Also I'm not sure, but I guess I don't need to use the BurnerMAX Payload Tool with imgburn? Is it a problem that I used it anyway? (a different drive, but verificiation failed at 49%.)
Edit:
Meant to say "TSSTcorp SH-224BB".