Jump to content

uradodah

Members
  • Content Count

    8
  • Joined

  • Last visited

About uradodah

  • Rank
    ISF Newbie
  1. uradodah

    New notebook - issue burning DVD+R DL

    It's OK, your drive can burn "DVD-RAM" format. More info here Thanks for the reply, ianymaty. I like to be thorough when troubleshooting so I also checked out my 360 console and found the issue was related to the console's drive. So - I have figured everything out. I'm still confused as to why the ImgBurn logs indicate "N/A" under the Book Type Setting since I've never seen it listed that way before. Maybe it's more common than I think. Once again, your help is appreciated. Thanks a ton!
  2. Hello. I'm having a problem burning an Xbox 360 game and I need your help. I have checked the forum for info on my issue but I can't find anything that matches my situation. If I missed a post, please forgive me in advance. I've been ripping and burning 360 games for quite a while now - yes, my own games, FYI - and haven't ever run into any problems. However, I recently got a new Alienware M15x notebook and the first time I tried to burn a game, it appeared to successfully complete the burn but my 360 console won't read the disc. I've also reinserted the disc into my notebook's DVD drive so that I can check the game data with another program and it appears to work ok - i.e. - the other program can read the data on the DVD. I'm wondering if the book type setting is possibly having a negative effect on whether or not my console can read the disc. I'm not an expert on this stuff, but I noticed something a bit weird in the ImgBurn log and would like to get your opinion. Specifically, under the "Book Type Setting" part of the log, it says "N/A". If memory serves me correctly, I don't believe I've ever seen "N/A" listed for the Book Type Setting. Shouldn't it read as "DVD-Rom"? I also noticed that my drive was listed as a "DVD±RW/RAM" towards the top of the log. Shouldn't the drive be listed as "DVD±RW/ROM"? Before I paste the log data, here's a bit more info about my setup: * Windows 7 HP x64 * Verbatim DVD+R DL Media * This is the first burn I've attempted on this new PC & I haven't made any changes to the drive (such as firmware) * I did not make any changes to ImgBurn's "default" settings If you need additional information, please let me know. I would really appreciate a bit of help with this issue. Thanks in advance for taking time to reply! Here's the log data: //****************************************\\ ; ImgBurn Version 2.5.1.0 - Log ; Saturday, 21 August 2010, 01:45:22 ; \\****************************************// ; ; I 00:58:22 ImgBurn Version 2.5.1.0 started! I 00:58:22 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7600) I 00:58:22 Total Physical Memory: 6,279,672 KB - Available: 4,523,560 KB W 00:58:22 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 00:58:22 Initialising SPTI... I 00:58:22 Searching for SCSI / ATAPI devices... I 00:58:22 -> Drive 1 - Info: HL-DT-ST DVD+-RW GA31N A102 (D:) (ATAPI) I 00:58:22 -> Drive 2 - Info: KBGRSH 0PAZODMJ 1.03 (Z:) (SCSI) I 00:58:22 Found 1 DVD±RW/RAM and 1 BD-ROM/HD DVD-ROM! I 00:58:55 Operation Started! I 00:58:55 Source File: F:\Xbox 360\Madden NFL 11\Madden NFL 11.dvd I 00:58:55 Source File Sectors: 3,827,488 (MODE1/2048) I 00:58:55 Source File Size: 7,838,695,424 bytes I 00:58:55 Source File Volume Identifier: DVD_ROM I 00:58:55 Source File Volume Set Identifier: ec67c000MS UDFBridge I 00:58:55 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM) I 00:58:55 Source File Implementation Identifier: Microsoft CDIMAGE UDF I 00:58:55 Source File File System(s): ISO9660, UDF (1.50) I 00:58:55 Destination Device: [0:1:0] HL-DT-ST DVD+-RW GA31N A102 (D:) (ATAPI) I 00:58:55 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x) I 00:58:55 Destination Media Sectors: 4,173,824 I 00:58:55 Write Mode: DVD I 00:58:55 Write Type: DAO I 00:58:55 Write Speed: 2.4x I 00:58:55 Link Size: Auto I 00:58:55 Lock Volume: Yes I 00:58:55 Test Mode: No I 00:58:55 OPC: No I 00:58:55 BURN-Proof: Enabled I 00:58:55 Write Speed Successfully Set! - Effective: 3,324 KB/s (2.4x) I 00:58:55 Book Type Setting: N/A I 00:58:55 Optimal L0 Data Zone Capacity: 1,913,760 I 00:58:55 Optimal L0 Data Zone Method: Copied From Original Disc I 00:58:55 Set L0 Data Zone Capacity Succeeded! I 00:58:55 Filling Buffer... (40 MB) I 00:58:57 Writing LeadIn... I 00:59:16 Writing Session 1 of 1... (1 Track, LBA: 0 - 3827487) I 00:59:16 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3827487) I 00:59:16 Writing Layer 0... (LBA: 0 - 1913759) I 01:19:23 Writing Layer 1... (LBA: 1913760 - 3827487) I 01:39:08 Synchronising Cache... I 01:39:37 Closing Track... I 01:40:31 Finalising Disc... I 01:40:49 Exporting Graph Data... I 01:40:49 Graph Data File: C:\Users\[MY USER NAME]\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_DVD+-RW_GA31N_A102_SATURDAY-AUGUST-21-2010_12-58_AM_MKM-001-00_2.4x.ibg I 01:40:49 Export Successfully Completed! I 01:40:49 Operation Successfully Completed! - Duration: 00:41:47 I 01:40:49 Average Write Rate: 3,201 KB/s (2.3x) - Maximum Write Rate: 3,359 KB/s (2.4x) I 01:45:22 Close Request Acknowledged I 01:45:22 Closing Down... I 01:45:22 Shutting down SPTI... I 01:45:22 ImgBurn closed!
  3. I'm hoping someone might be able to help explain an error I'm experiencing when trying to burn dual layer discs. I spent about 20 minutes searching the forum for info related to my specific problem and didn't find anything. Please forgive me in advance if I missed a post that was relevant to my issue. A bit of background info: My Dell XPS M1330 notebook is running Windows 7 Home Premium (32-bit) and I'm also using the latest version of ImgBurn. I only use Verbatim brand Dual Layer discs - nothing else! After checking Dell's available drivers for my notebook, it appears as though I'm using the latest chipset drivers and BIOS version. I'm not able to locate any info on whether or not my DVD drive's firmware is up-to-date. I believe I'm using the last firmware version created for the drive. If you know of an updated version, please let me know. I hadn't burned any discs in a while - using ImgBurn or any other app - prior to attempting this one. However, the only change made to my PC was the addition of the application "Alcohol 120%." I'm utilizing the software's virtual drive capabilities. I'm not sure if this app has created a conflict or not but I thought I'd mention it. The last time I burned a disc with ImgBurn (a month ago or so), everything was fine and the burn completed successfully. Here's the log details: ; //****************************************\\ ; ImgBurn Version 2.5.1.0 - Log ; Wednesday, 12 May 2010, 06:22:11 ; \\****************************************// ; ; I 01:57:34 ImgBurn Version 2.5.1.0 started! I 01:57:34 Microsoft Windows 7 Home Premium Edition (6.1, Build 7600) I 01:57:34 Total Physical Memory: 3,143,724 KB - Available: 1,886,896 KB W 01:57:34 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 01:57:34 Initialising SPTI... I 01:57:34 Searching for SCSI / ATAPI devices... I 01:57:34 -> Drive 1 - Info: HL-DT-ST DVD+-RW GSA-S10N A103 (E:) (ATA) I 01:57:34 -> Drive 2 - Info: WHU 4DEN016V 3.5Z (Z:) (SCSI) I 01:57:34 Found 1 DVD±RW and 1 BD-ROM/HD DVD-ROM! I 01:59:04 Operation Started! I 01:59:04 Source File: C:\Users\Sko\Desktop\dgr-dtr3.dvd I 01:59:04 Source File Sectors: 3,827,488 (MODE1/2048) I 01:59:05 Source File Size: 7,838,695,424 bytes I 01:59:05 Source File Volume Identifier: DVD_ROM I 01:59:05 Source File Volume Set Identifier: ec67c000MS UDFBridge I 01:59:05 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM) I 01:59:05 Source File Implementation Identifier: Microsoft CDIMAGE UDF I 01:59:05 Source File File System(s): ISO9660, UDF (1.50) I 01:59:05 Destination Device: [1:0:0] HL-DT-ST DVD+-RW GSA-S10N A103 (E:) (ATA) I 01:59:05 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x) I 01:59:05 Destination Media Sectors: 4,173,824 I 01:59:05 Write Mode: DVD I 01:59:05 Write Type: DAO I 01:59:05 Write Speed: 2.4x I 01:59:05 Link Size: Auto I 01:59:05 Lock Volume: Yes I 01:59:05 Test Mode: No I 01:59:05 OPC: No I 01:59:05 BURN-Proof: Enabled I 01:59:05 Write Speed Successfully Set! - Effective: 3,324 KB/s (2.4x) I 01:59:05 Book Type Setting: DVD-ROM I 01:59:05 Optimal L0 Data Zone Capacity: 1,913,760 I 01:59:05 Optimal L0 Data Zone Method: Copied From Original Disc I 02:00:20 Set L0 Data Zone Capacity Succeeded! I 02:00:21 Filling Buffer... (40 MB) I 02:00:22 Writing LeadIn... I 02:00:32 Writing Session 1 of 1... (1 Track, LBA: 0 - 3827487) I 02:00:32 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3827487) I 02:00:32 Writing Layer 0... (LBA: 0 - 1913759) W 02:15:55 Failed to Write Sectors 1506272 - 1506303 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x90) W 02:15:55 Retrying (1 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (2 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (3 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (4 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (5 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (6 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (7 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (8 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (9 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (10 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (11 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (12 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (13 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (14 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (15 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (16 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (17 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (18 of 20)... W 02:15:55 Retry Failed - Reason: Medium Not Present W 02:15:55 Retrying (19 of 20)... W 02:15:56 Retry Failed - Reason: Medium Not Present W 02:15:56 Retrying (20 of 20)... W 02:15:56 Retry Failed - Reason: Medium Not Present E 06:21:53 Failed to Write Sectors 1506272 - 1506303 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x90) I 06:21:53 Synchronising Cache... W 06:21:53 Synchronise Cache Failed! - Reason: Medium Not Present W 06:21:53 Retrying (1 of 3)... W 06:21:53 Retry Failed - Reason: Medium Not Present W 06:21:53 Retrying (2 of 3)... W 06:21:53 Retry Failed - Reason: Medium Not Present W 06:21:53 Retrying (3 of 3)... W 06:21:53 Retry Failed - Reason: Medium Not Present E 06:22:02 Synchronise Cache Failed! - Reason: Medium Not Present W 06:22:07 User opted to skip the 'Close Track/Session/Disc' functions. E 06:22:07 Failed to Write Image! I 06:22:09 Exporting Graph Data... I 06:22:09 Graph Data File: C:\Users\Sko\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST DVD+-RW GSA-S10N A103 WEDNESDAY-MAY-12-2010 1-59 AM MKM-001-00 2.4x.ibg I 06:22:09 Export Successfully Completed! E 06:22:09 Operation Failed! - Duration: 04:23:02 I 06:22:09 Average Write Rate: 192 KB/s (0.1x) - Maximum Write Rate: 3,393 KB/s (2.4x) I 06:22:11 Close Request Acknowledged I 06:22:11 Closing Down... I 06:22:11 Shutting down SPTI... I 06:22:11 ImgBurn closed! *** Please Note: The reason the log says "Retry Failed - Reason: Medium Not Present" is because I had selected the "Eject" option after starting the burn session. The session seemed to be moving along just fine until about 15-16 minutes into it. At that point, the disc ejected and I knew something was wrong. Since I started this session before heading to bed, I just left the disc ejected until later - when I eventually proceeded to cancel the session and also skipped the "Close Track/Session/Disc" functions at the end. That's why you see it listed as such in the log (including the huge gap in time). While I've seen a few errors using ImgBurn over the years, I've never seen this one and would appreciate some assistance in sorting out the root cause of the problem. Once again, please accept my apologies if I missed a previous post related to this issue. Keep up the great work you're doing on this fantastic application! Your continued efforts to improve and evolve are appreciated - as are your efforts to help me resolve my problem. Thanks!
  4. uradodah

    The ' Program Memory Area Update Failure ' Thread!

    Cynthia, Thanks for the reply. My post was meant from a more 'generic' perspective - meaning - not focused on any one specific drive. I currently have a Matshita drive and am experiencing this issue. You posted some helpful information in the topic I created specific to my issue. Thanks for that as well. I guess, where I'm coming from, is what does this error really mean - OTHER THAN attributing it to the quality of media being used? Does it mean that a firmware update (if available) may help resolve the issue? Does it mean the drive is likely dying and needs to be replaced? Does it mean a good lens cleaning may help - and if so - any idea on how to clean the lens in a slot-load notebook drive? That's what I'm after. Thus far, through searching here (and I could have missed something), searching Google and reading a ton of info from other sites/forums, the majority of the posts just tell people to 'buy a better quality media'. I'm trying to look past that since it's not an issue for everybody every time. I know it's hard to accurately diagnose (if not impossible) every problem someone has related to this issue. However, a few educated guesses would definitely help! For example, in my case, if you 'experts' believe my Matshita drive may be (or is likely) on a slippery slope to its eventual death, I could call Dell to begin the process of getting it replaced prior to my warranty expiring. This kind of info also helps reduce the likelihood of producing 'average' burns that work *for now* only to start burning expensive coasters down the road because we didn't take proactive steps ahead of time. I hope you can understand where I'm coming from. The information in this topic - and in this forum - is top-notch and informative. I just think it's too easy at times to fall back on the 'old faithful' solution - 'go buy a better quality media'.
  5. uradodah

    The ' Program Memory Area Update Failure ' Thread!

    I know this is a late post based on date of the original - but it appears that the topic is still active. With that said, "nxpa76" appears to be asking a valid question IMHO. While I'm thankful that the research was done for us - and posted for everyone else to see - it doesn't do a whole lot to actually *help* anyone. I just started experiencing this issue and am doing research on it to get better educated. This info does help, no question. However, telling someone to use a better burning application that tells us about the error instead of ignoring it doesn't help anyone. It doesn't explain WHY we're getting the issue and WHAT can be done to RESOLVE it. In my case, I'm already using Verbatim discs - and always have. The overwhelmingly 'typical' or standard response on this forum appears to be 'use a better media'. Well - I'm already doing that. So - this information doesn't do a whole lot for me. 1. I'm already using an application that doesn't mask or gloss over the OPC or PMA issue. Thanks ImgBurn! 2. I'm already using a high quality media and don't use anything other than Verbatim. Please help me understand how this info helps me actually attempt to resolve my issue based on these 2 facts. If I'm missing something, great. I'll offer my apologies in advance. I *have* posted specific, detailed information about my errors in a separate post and have gotten responses that have been VERY helpful. However, nobody has offered any possible root causes for this error - nor has anyone offered advice on possible solutions...outside of enabling OPC. All of this said, I appreciate your time and attempts to provide assistance to all of us!
  6. Thanks, Cynthia. Fantastic info! As I was researching the OPC setting (Google is my friend!) I came across and awesome PDF file called "The ImgBurn Settings". It appears you put that guide together - am I right? If so, I'd like to say Thanks. It's a great resource - and one that I hadn't seen in the past. I always feel like it's important for me - or anyone else - who posts about their problems on forums to try and do some research on their own before AND after posting. In this particular instance, I did a lot of research over the past several days but I never noticed anything regarding the PDF file. It's very likely I was so focused on finding an answer to my specific issue that I missed it. Anyway, thanks for putting it together...if it was you. I'm going to try enabling OPC and will let you guys know what happens. My fear is that I'm still dealing with a dying drive though. I wish I could just get my own drive but the Dell XPS M1330 drives are the thin, built-in type where you insert the disc instead of opening a tray. Forgive my ignorance...I don't the proper name for those types of drives. I have no idea if those drives can even be replaced by an end-user or OEM drives have to be used as replacements. Thanks.
  7. Thanks for the response! I'll give it a try and will let you know how it goes. What does that setting mean? I'll try to research it...I just didn't know if this was an obvious setting that I missed or something. Also, if my drive truly is going bad, will this setting only mask the real issue by forcing ImgBurn to burn the data anyway? Thanks again!
  8. Hello all. I love ImgBurn but have suddenly begun to run into an issue when trying to burn and ISO image to a dual layer DVD. I will paste the latest log info shortly. Before that, a bit of background... First, and foremost, so that I can be spared the 'buy a better brand of media' comments - I've always used Verbatim media and continue using Verbatim discs for all of my burning needs. Personally, I've never had an issue that was ultimately attributed directly to the brand of media, but I've literally used Verbatim 99% of the time so I don't have a lot of experience with other media brands to draw from. With that said, I had been happily burning away on my Dell XPS M1330 notebook for going on 2 years now. ImgBurn has been used for all of my ISO buring needs. I've never had a problem until recently. Currently, after loading a '.dvd' file in preparation to burn an Xbox 360 game ISO, I keep getting the "Power Calibration Area Error" just before the point where ImgBurn would begin loading the buffer to start burning the data. I've done all the standard troubleshooting procedures on my end - uninstalled/reinstalled the driver for my Matshita DVD drive (there's a reason the word 'sh*t' is in the name of that drive...Dell had to replace it about 8 months ago), I also uninstalled/reinstalled ImgBurn just to see if that would have a positive outcome and I even tried a different brand of media. Nothing works. Also, there are no updated drivers for my Matshita drive. I wish there was a custom driver available. Where my confusion comes from is that when I try to burn the same '.dvd' and/or ISO file using another program - such as CloneCD - everything works PERFECTLY! The data burns just fine and the Xbox 360 reads the discs and allows me to play the games as usual. This begs the question then: Why would ImgBurn give me this error when other programs appear to work fine? Does ImgBurn do hardware checks that other burning software does not? My gut tells me that, in all likelihood, my Matshita DVD drive is going out AGAIN . I may have to place another warranty replacement call to Dell. However, I'd like to hear the forum's resident 'experts' feedback prior to moving forward. Do you agree that my drive may be dying again - or could there be a different issue going on in this case - since other software appears to work? Thanks in advance for putting up with my long post and for offering any feedback or advice that may help resolve this issue. I sincerely appreciate your efforts! As promised, here's a copy of the latest log file: ; //****************************************\\ ; ImgBurn Version 2.4.2.0 - Log ; Sunday, 22 March 2009, 03:19:18 ; \\****************************************// ; ; I 03:16:29 ImgBurn Version 2.4.2.0 started! I 03:16:29 Microsoft Windows Vista Home Premium Edition (6.0, Build 6001 : Service Pack 1) I 03:16:29 Total Physical Memory: 3,142,972 KB - Available: 1,931,560 KB I 03:16:29 Initialising SPTI... I 03:16:29 Searching for SCSI / ATAPI devices... I 03:16:29 Found 1 DVD
×

Important Information

By using this site, you agree to our Terms of Use.