Jump to content

Recommended Posts

Posted

hi everybody am trying to burn an iso file i tried everything (which is nothing as i keep running in dead ends) but still no progress

 

i think it could be my laptop that has a problem burning but i cann't understand what anything on these logs means, what could be the problem ?

 

TSSTcorp CDDVDW TS-L633F TF01 (SATA)
Current Profile: DVD-R

Disc Information:
Status: Complete
State of Last Session: Complete
Erasable: No
Sessions: 1
Free Sectors: 316,320
Free Space: 647,823,360 bytes
Free Time: 70:19:45 (MM:SS:FF)
Next Writable Address: 0
MID: RITEKF1
Supported Write Speeds: 2x

TOC Information:
Session 1... (LBA: 0)
-> Track 01  (Audio, 3684:34:59, LBA: 0 - 16580608)
-> LeadOut  (LBA: 16580609)

Pre-recorded Information:
Manufacturer ID: RITEKF1

Physical Format Information (Last Recorded):
Disc ID: 0@P-!-00
Book Type: DVD-R
Part Version: 5
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 512,927
Last Physical Sector in Layer 0: 0

Performance (Write Speed):
Descriptor 1...
-> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00
-> EL: 2297887 (0x0023101F)
-> RS: 11,080 KB/s (8x) - WS: 2,770 KB/s (2x)
 

 

 

and

 

 

the log 

I 13:54:33 ImgBurn Version 2.5.8.0 started!
I 13:54:33 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1)
I 13:54:33 Total Physical Memory: 4,140,908 KiB  -  Available: 1,655,692 KiB
I 13:54:33 Initialising SPTI...
I 13:54:33 Searching for SCSI / ATAPI devices...
I 13:54:38 -> Drive 1 - Info: TSSTcorp CDDVDW TS-L633F TF01 (F:) (SATA)
I 13:54:38 Found 1 DVD±RW/RAM!
I 13:55:16 Operation Started!
I 13:55:16 Source File: C:\Users\Noor\Downloads\pcriver.com_Windows_XP_Pro_SP3_32_bit.iso
I 13:55:16 Source File Sectors: 316,320 (MODE1/2048)
I 13:55:16 Source File Size: 647,823,360 bytes
I 13:55:16 Source File Volume Identifier: GRTMPVOL_EN
I 13:55:16 Source File File System(s): ISO9660 (Bootable), Joliet
I 13:55:16 Destination Device: [2:0:0] TSSTcorp CDDVDW TS-L633F TF01 (F:) (SATA)
I 13:55:16 Destination Media Type: DVD-R (Disc ID: RITEKF1)
I 13:55:16 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8x
I 13:55:16 Destination Media Sectors: 2,297,888
I 13:55:16 Write Mode: DVD
I 13:55:16 Write Type: DAO
I 13:55:16 Write Speed: MAX
I 13:55:16 Link Size: Auto
I 13:55:16 Lock Volume: Yes
I 13:55:16 Test Mode: No
I 13:55:16 OPC: No
I 13:55:16 BURN-Proof: Enabled
I 13:55:16 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x)
I 13:55:17 Filling Buffer... (80 MiB)
I 13:55:24 Writing LeadIn...
W 13:56:50 Failed to Write Sectors 192 - 223 - Reason: The request could not be performed because of an I/O device error.
W 13:56:50 Retrying (1 of 20)...
W 13:56:50 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:50 Retrying (2 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (3 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (4 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (5 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (6 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (7 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (8 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (9 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (10 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (11 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (12 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (13 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (14 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (15 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (16 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (17 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (18 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (19 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
W 13:56:51 Retrying (20 of 20)...
W 13:56:51 Retry Failed - Reason: Logical Block Address out of Range
E 14:01:35 Failed to Write Sectors 192 - 223 - Reason: The request could not be performed because of an I/O device error.
I 14:01:35 Synchronising Cache...
W 14:01:46 User opted to skip the 'Close Track/Session/Disc' functions.
E 14:01:46 Failed to Write Image!
E 14:01:46 Operation Failed! - Duration: 00:06:30
I 14:01:46 Average Write Rate: 0 KiB/s (0.0x) - Maximum Write Rate: 0 KiB/s (0.0x)
 

i will really appreciate help!

Posted

Was the disc info you posted there from a blank disc?

 

Your drive doesn't seem to have initialised it correctly.

 

If that's what you get with all blanks, it might not support that MID (RITEKF1) at all.

Posted

yes the disks are blank, I think I should get a new computer I have updated the drivers even once completely unrelated to this problem , the problem still persists, thank you for the help

Posted

Neither a new computer nor updated drivers are going to help. The only thing that MIGHT help is to see if there's newer firmware for that optical drive. If not, swap to better quality blanks. Ritek is about the cheapest crap you can get, and you get what you pay for.

 

Sent from my Nexus 6P with Tapatalk

Posted

Yes, don't go replacing all your hardware as a first step to troubleshooting.  Ritek is a common compatibility problem for many users, particularly when using DL media.  Personally, I've rarely had any problem with them, except their RiData line, but then I only use Ritek for their 8x DVD+RW, because the only other kinds out there are CMC, and sometimes a few BD-R/E that I don't plan on playing on my PS3.

 

 

Your first step should be try using Verbatim media and see if you get the same problems.  Verbatim is about the best you can get out there, with the fold of Taiyo Yuden.  However, don't get the Life Series discs you find in brick and mortar stores or online.  Get the DataLife Plus media you can only find online.  I get mine from Amazon.com.  If you get the Life Series, you will get CMC media, which IS the cheapest media out there.

Posted

The cheap ones can be just as problematic, though, because many are slim model drives.  Slim models have a low performance track record in correlation to the posts we see about them on here.  Get a full height external drive when you can.  Or get a full height internal model and put in in an external drive enclosure.  But, if what you have works, stick with it.

Posted

Yeah, I have no direct, empirical experience with slim model drives.  So, I can't say from actual use of them.  I'm just going by the general experience of people who have reported problems here with them.

 

 

I think I had a Matshita full height DVD-R/RAM drive back in 2002.  I ended up replacing it when the dual format model from Sony came out.  However, I had no problems with what I used it for.  Then again, it was a full height one, too.

Posted

The main issue with matSHITa ones is if you plan on using it with eg AnyDVD to decrypt foreign region discs. (Eg disc is region 1, drive region 2) even with a set hardware region, there's something in them or the firmware that prevents eg AnyDVD from doing it's job and remove DVD disc region.

 

Sent from my Nexus 6P with Tapatalk

Posted

They prevent you from reading anything (scrambled at least) on the disc when the region code of the disc doesn't match that of the drive - thus even brute force CSS cracking isn't possible.

Posted

That's what I'm saying, though I ain't sure if it's something done hardware wise or in the firmware. I think James said it's done the trough the firmware.

 

Sent from my Nexus 6P with Tapatalk

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

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