Jump to content

Ichinichi

Members
  • Posts

    15
  • Joined

  • Last visited

Ichinichi's Achievements

ISF Newbie

ISF Newbie (1/5)

  1. Just a quick update of a solution of sorts. I reinstalled Windows. No problem now.
  2. So your system is timing out the I/O after only 10 seconds and totally ignoring that I've set a much longer timeout on all the commands. I have no idea exactly which driver is responsible for doing that, sorry. This is why I love imgburn; where the hell else will the creator still actively participate at this level? lightning uk, I will take a look at my registry entries, perhaps i've set them in the past (although i do not recall doing so between october and now)...
  3. Where are the error descriptions generated from? Internal to IMGBURN or is "Semaphore timeout" just passed through IMGBURN from the OS? Semaphore timeout means that the OS has detected a starvation/deadlock scenario on some shared resource. It cannot be the file itself, since IMGBURN is just reading it, and no one ought to be writing to the image at the same time as it is being burned anyway, so there's no risk of Read-After-Write. Meaning that the resource must be the burner itself; Windows is detecting that at least one other some other process is reserving the drive and has determined that a deadlock has occured. This then kills all processes and resets the semaphore values.
  4. Well, the thing is, nothing has changed in my system since the last successful DL write. Its the same install of Windows, the same sticks of RAM, the same spindle of disks, the same drivers, same motherboard, same everything.
  5. for serious? you mean there isn't an understood cause?
  6. Argh! Its happening again! Semaphore timeout, then retry fails. Please help. Disks: Verbatim DVD+R DL 2.4X from Best Buy store Origin: Singapore Drive: Sony DRX-840U History: I purchased this drive and these disks in October 2008. Successfully burned 5 DL and several Audio CDs and Data DVDs since then. All DL disks are from the same spindle as the other five. Last successful burn was data DVD. I have not installed anything since my last successful DL burn. Log: I 19:53:46 ImgBurn Version 2.4.2.0 started! I 19:53:46 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 19:53:46 Total Physical Memory: 2,096,364 KB - Available: 1,704,456 KB I 19:53:46 Initialising SPTI... I 19:53:47 Searching for SCSI / ATAPI devices... I 19:53:47 Found 1 DVD
  7. Hello? All Sunday and no suggestions? I cannot afford to keep a $200 burner. What is the most dependable, internal, sub $50 DL burner on the market these days?
  8. Hello all! Phew! It was a dark, dark night. I ended up trying to reinstall windows since it was complaining of consistency issues with one of my logical partitions every time it booted up (never finds anything wrong). Well, using the ASUS drive I ended up getting caught between where a Windows installation is registered by the system and where ntldr is copied over. That's when the ASUS crapped out on me. It wouldn't boot from CD. I tried everything. Finally, observing daylight once more, I had a friend bring over an old HP CD-ROM and successfully reinstalled Windows. Went to the local big box retailer and bought a SONY USB External DL Burner to see if the media might be at fault as well. The ASUS is going RMA, for sure. To answer LIGHTNING UK's last queries: I am on an ASUS P4P-800SE from 2003. Its got two onboard 1.5GB/s SATA ports plus the Rosewill PCI SATA/RAID controller card, which has three SATA ports. Since the $200 SONY external DL burner is just for test purposes (I'm sure as hell not keeping it at that price), I'm still not sure what drive to buy now and any suggestions would be appreciated.
  9. I have also noticed that the log indicates the "next writable" address is almost always 500 sectors earlier than the unwritable ones... Here's the log from the WinXP SP2 ; //****************************************\\ ; ImgBurn Version 2.4.2.0 - Log ; Friday, 24 October 2008, 22:35:54 ; \\****************************************// ; ; I 22:03:15 ImgBurn Version 2.4.2.0 started! I 22:03:15 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 22:03:15 Total Physical Memory: 2,096,364 KB - Available: 1,681,932 KB I 22:03:15 Initialising SPTI... I 22:03:15 Searching for SCSI / ATAPI devices... I 22:03:15 Found 1 DVD
  10. point being to find out if the drive IS screwed or not, process of elimination Again they are 'marked' 2.4x , maybe newer drives will write them faster, but as yours is a new drive we dont know that yet DO WE ?, where was they made ( i asked earlier for a reason, India or Singapore ?) Yes, it means the drive is struggling to write to those discs the drive thinks that it can STILL write to a part its already written to '163017' , notice it got to 163520 when it errored out . and the same in the first log you posted i reckon youve got either discs made in India or your drive needs changing ( RMA ) or it could even be a dirty lense on the drive or dirty discs. Personally, i would return the drive ( while you can) and get a better branded one thats known to be reliable with DL verbs Right. In the spirit of Process of Elimination I tried to burn with Alcohol 120 using the exact same image file, drive and media. It got to 98% completion and abruptly threw a write error. So we know its not the image I'm trying to burn... The error code was S:KEY - 03/0C/00 - "Write Error". Googling for sense codes I get: Sense Code Results SCSI Error Code Lookup: 3-0C-00 Error Description(s): (3-0C-00) Vendor assigned code. The read-after-write retry limit was exceeded during a write operation. Does this shed any new light? I doubt the lens is dirty since it came out of its antistatic bag a little over 12 hours ago. How do I tell whether my discs are from India or Singapore? Even if the discs are from India, there's no way I'm getting 12 coasters from 12 attempts! I have since tried burning using a different Windows Install (WinXP Pro SP2, same system, spare primary HDD). Oddly enough, when I tried to reinstall WinXP, the Installer for continually reported errors/corruption on the genuine WinXP disc, which installed w/o a hitch using a Samsung drive three days ago. Maybe it is time for an RMA. What drive does LIGHTNING_UK and friends recommend?
  11. I also switched out the ATA cable for a brand new one. Sometimes, when imgburn is waiting for me to select an image to burn, the status at the bottom left of the window says "Power On, Device Reset, Bus [something]"...or something of the like. I've plugged the drive into the Primary IDE Controller and the Secondary Controller. I'm out $12 in discs. WTF is the deal? I set the write speed to 2.0x and here's the log. It gets 163xxx sectors in and chokes. I 19:03:05 ImgBurn Version 2.4.2.0 started! I 19:03:05 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 19:03:05 Total Physical Memory: 2,096,364 KB - Available: 1,711,988 KB I 19:03:05 Initialising SPTI... I 19:03:05 Searching for SCSI / ATAPI devices... I 19:03:05 Found 1 DVD
  12. I'm hoping to resolve this issue in house before going through the hassle of an RMA. The drive is from NewEgg, so I'm not pressed on time wrt RMA deadlines.
  13. It's not an Imgburn issues....the 2.4X is down to your hardware/firmware. As you can see from your log 2.4 isn't supported so you'll need to choose 2X. The discs are rated for 2.4X so choosing anything above that will be overspeeding and not recommended, especially with DL projects. If you've updated the firmware to 1.01 it didn't take...I'd try again. The firmware may fix the compatiblity issues you are seeing with the Verbatim media. EDIT: Actually, checking the ASUS website it lists 1.00 as the current firmware for your drive.... http://support.asus.com/download/download....p&f_type=20 Its weird since when I flashed it this morning, downloading the exe from the same link as you listed, I remember distinctly that the firmware installer said I had 1.00 and that 1.01 is newer. I tried burning at 2.0x this morning with no luck. Does the fact that each burn fails at an early sector indicate anything?
  14. I have not tried writing SL discs since my objective is to have DL writing capability. The discs are marked 2.4x and these are the exact discs that LIGHTNING_UK suggests on the front page sticky to use Verbatim discs (MKM-001-00). It is curious that you mention how there is no 2.4x explicitly recognized by imgburn, but again referencing from LIGHTNING_UK's sticky post, the MKM-001-00 discs can be written at 8X by newer drives (which I believe mine to be). I have tried hardsetting the write speed to 2x, 2.4x and AUTO (MAX). From all my reading, I recall something about needing to do booksetting in certain cases (I forget which ones).
  15. Hello all, Briefly, the drive sets L0 boundary without problem, writes lead-in, but throws a Write Error at an early sector. Sometimes its in the 20,xxx (like in the log below), other times its in the hundreds (lowest is sector 6xx). 1. I am using a 1-day old ASUS DRW-2014S1 with the 1.01 FW (even though it doens't seem to read as such). 2. I am using Verbatim MKM-001-00 DL discs from amazon. I have 7 coasters on my desk. 3. The very first time I tried to burn a DL disc (using 1.00 FW), it got 48MB into the burn before the Write Error/Invalid Address for Write. Since then, the write error has occurred much earlier than that. Three discs later, I updated the FW but no dice. Yes I restarted the machine first. 4. I have noticed that the drive has trouble ejecting after the errors. I must exit imgburn and wait 15sec or so before the tray will eject. 5. I have not changed the booktype at all. 6. I am testing on burning backup X360 discs 7. Windows XP SP3, Intel P4 2.8GHz, 2GB PC3200 RAM, 1.7GB free Thank you so very much for any help. Here's the disc/drive info: ASUS DRW-2014S1 1.00 (ATA) Current Profile: DVD+R DL Disc Information: Status: Incomplete Erasable: No Sessions: 1 Free Sectors: 3,806,681 Free Space: 7,796,082,688 bytes Free Time: 845:57:56 (MM:SS:FF) Supported Write Speeds: 2x, 4x, 6x, 8x DVD
×
×
  • Create New...

Important Information

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