Jump to content

asc/ascq interpretation: session fixation error writing lead in


Please Help

Recommended Posts

Post the log of the failed burn.  Under Help, choose the Logs option.  Then, open the .LOG file, find the appropriate part of the log, and copy and paste it into a reply.  I have a pretty good idea what it possibly could be, but a log would tell me what precisely I needed to know.

Link to comment
Share on other sites

I 13:17:15 ImgBurn Version 2.5.8.0 started!
I 13:17:15 Microsoft Windows 7 Home Premium Edition (6.1, Build 7601 : Service Pack 1)
I 13:17:15 Total Physical Memory: 2,873,200 KiB  -  Available: 1,771,392 KiB
I 13:17:15 Initialising SPTI...
I 13:17:15 Searching for SCSI / ATAPI devices...
I 13:17:15 -> Drive 1 - Info: TSSTcorp CDDVDW TS-L633F TF01 (D:) (ATAPI)
I 13:17:15 Found 1 DVD±RW/RAM!
I 13:17:37 Operation Started!
I 13:17:37 Source File: C:\Users\AMAL\Desktop\ps2 dvd\All PS2 Slims - English language.iso
I 13:17:37 Source File Sectors: 667 (MODE1/2048)
I 13:17:37 Source File Size: 1,366,016 bytes
I 13:17:37 Source File Volume Identifier: CDROM
I 13:17:37 Source File Volume Set Identifier: 5EFDB845000C86F8
I 13:17:37 Source File Application Identifier: MKISOFS ISO9660/HFS/UDF FILESYSTEM BUILDER & CDRECORD CD/DVD/BluRay CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING
I 13:17:37 Source File Implementation Identifier: mkisofs
I 13:17:37 Source File File System(s): ISO9660, UDF (1.02)
I 13:17:37 Destination Device: [0:0:0] TSSTcorp CDDVDW TS-L633F TF01 (D:) (ATAPI)
I 13:17:37 Destination Media Type: DVD-R (Disc ID: CMC MAG. AM3)
I 13:17:37 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8x
I 13:17:37 Destination Media Sectors: 2,297,888
I 13:17:37 Write Mode: DVD
I 13:17:37 Write Type: DAO
I 13:17:37 Write Speed: 4x
I 13:17:37 Link Size: Auto
I 13:17:37 Lock Volume: Yes
I 13:17:37 Test Mode: No
I 13:17:37 OPC: No
I 13:17:37 BURN-Proof: Enabled
I 13:17:38 Write Speed Successfully Set! - Effective: 5,540 KB/s (4x)
I 13:17:38 Filling Buffer... (80 MiB)
I 13:17:38 Writing LeadIn...
W 13:19:06 Failed to Write Sectors 160 - 191 - Reason: Session Fixation Error Writing Lead In
W 13:19:06 Retrying (1 of 20)...
W 13:19:06 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:06 Retrying (2 of 20)...
W 13:19:06 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:06 Retrying (3 of 20)...
W 13:19:06 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (4 of 20)...
W 13:19:07 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (5 of 20)...
W 13:19:07 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (6 of 20)...
W 13:19:07 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (7 of 20)...
W 13:19:07 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (8 of 20)...
W 13:19:07 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (9 of 20)...
W 13:19:07 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (10 of 20)...
W 13:19:07 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (11 of 20)...
W 13:19:07 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (12 of 20)...
W 13:19:07 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (13 of 20)...
W 13:19:07 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (14 of 20)...
W 13:19:07 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (15 of 20)...
W 13:19:07 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (16 of 20)...
W 13:19:07 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (17 of 20)...
W 13:19:07 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:07 Retrying (18 of 20)...
W 13:19:08 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:08 Retrying (19 of 20)...
W 13:19:08 Retry Failed - Reason: Logical Block Address out of Range
W 13:19:08 Retrying (20 of 20)...
W 13:19:08 Retry Failed - Reason: Logical Block Address out of Range
E 13:19:47 Failed to Write Sectors 160 - 191 - Reason: Session Fixation Error Writing Lead In
I 13:19:48 Synchronising Cache...
E 13:19:51 Failed to Write Image!
E 13:19:51 Operation Failed! - Duration: 00:02:14
I 13:19:51 Average Write Rate: 0 KiB/s (0.0x) - Maximum Write Rate: 0 KiB/s (0.0x)
 

 

 

 

 

 

 

 

Also look at the screenshot

Screenshot_18.png

Link to comment
Share on other sites

Yeah, it's what I thought.  This is most likely your problem:

I 13:17:37 Destination Media Type: DVD-R (Disc ID: CMC MAG. AM3)

 

CMC Magnetics makes the worst discs out there.  Unfortunately, most companies use them to maximize profits.  You probably bought some Verbatim Life Series in a brick and mortar store?  Those will be CMC.  While it's not 100% guaranteed to solve your problem, more than 50% of the problems on this board are caused by cheap CMC junk and generally disappear when people switch to higher quality media.  Try genuine Taiyo Yuden DVD-R, the ones not made by CMC, or Verbatim DataLife Plus.  NOT the Life Series.  DataLife Plus can only be found in online stores.  Or look for Verbatim DVD that is listed as AZO brand dye.  Those will also be DataLife Plus quality discs.

 

Another possibility is the TSST drive you're using.  Those have proven to be somewhat picky and problematic according to posts on this board.

Link to comment
Share on other sites

I'm from ethiopia (african country) and it's not easy that buying things in online as you told but when i try to burn another iso file to a other disc that is similar to this disc i successfully burned it btw I have 3 blank dvd-r copy that i bought. But when i try this iso file it fails in all of them

The file is in the second one (All PS2 Slims - English language.iso) 

https://github.com/CTurt/FreeDVDBoot/tree/master/PREBUILT ISOs

Try it by yourself and tell me what happened when you burn it

Edited by Please Help
Link to comment
Share on other sites

If one ISO works and another doesn't, it's most likely the fault of the ISO that is failing.  Particularly if you downloaded the ISO, which if it's a PS2 game, as it appears it may be, then it's higher likely the ISO itself is at fault.  However, it is also the nature of CMC media that you'll get discs from the same package that work when others don't.

Link to comment
Share on other sites

Well, what you should do, you can't.  What you should do is get some better media and see if that clears it up.  But, you can't do that.

 

You could try trying a different burner.  That may help.  May not.  You could check for a firmware update, but there most likely isn't one and probably wouldn't help here even if it did.  In Write mode, right click on the TSST burner and choose the option at the bottom of the context menu list for checking for firmware update.

 

I could try burning your ISO to a DVD+RW but it's hardly an apples to apples comparison.  I'm not using the same drive as you are.  I'm not using the same media manufacturer.  I'm not using the same media type, even.  But, it would determine if the ISO is at fault.  If I can successfully burn it on my end, the problem is either the media you're using, which is my guess, or your drive.

 

So, give me a bit to do that.

Link to comment
Share on other sites

Oh, I did that before, and failed to see the Download button.

 

1.3 MB seems like an awfully small amount for PS2 ISO's.  It's also an awfully small amount to be burning to DVD-R.  I'd try CD-R instead.  And the fact that it's so small may be the reason it fails.  I'd expect an ISO to be significantly larger than that.

Link to comment
Share on other sites

It just launches Ulaunchelf by telling ps2 it's DVD Video but It is very very very helpful when you have unmodified ps2 just like me

I'm just trying to do this cause I accidentally deleted the memory card (free mcboot) and my ps2 is not that much good with dvds and cds

It was good with usb games and this happened 5 to 6 years ago, I just wanted to work again

Link to comment
Share on other sites

Oh, I see.  It's a soft mod.

 

No, I did not try it with DVD-R because it won't make a difference.  If it burns to one, it burns to another.  If you were try it on a DVD+RW it might or might not work.  Might work if it's not a CMC DVD+RW.  Might work because it isn't a DVD-R in that drive.  Might not work because your TSST is picky with DVD+RW.  But, we know it's not a faulty ISO.  So, it's on your end, which means most likely the medium or the drive.

 

As I said, a firmware update might help, but I'll tell you right now, it's either the CMC discs or your TSST.  Replacing either option seems out of reach for you, though.  You could try updating the firmware, but I doubt it would help and I doubt there even is a firmware update.  Could be one and it could help, but unlikely.

Link to comment
Share on other sites

Quote from earlier:

"You could try trying a different burner.  That may help.  May not.  You could check for a firmware update, but there most likely isn't one and probably wouldn't help here even if it did.  In Write mode, right click on the TSST burner and choose the option at the bottom of the context menu list for checking for firmware update."

Link to comment
Share on other sites

Every program you run on a laptop can "affect" your laptop.  You're more likely to "affect" the optical burner in it if you update the firmware and it fails for whatever reason.  Or if your battery dies during firmware update.  The check for update feature in ImgBurn does not actually execute anything other than your default web browser.  It sends the Drive ID string for your burner model to a web site where it checks to see if a database has any entries for firmware for that model.  You then choose to instigate to download anything you might find useful.  Then, you choose to execute that firmware updater package executable.

Link to comment
Share on other sites

What do you mean what option should you use?  The right click context menu one?  The one at the bottom for checking for firmware updates.

 

If you mean which update package from the web page check for firmware updates opens, you'll want one for your TSST drive, which is model TS-L633F and a firmware greater than TF01.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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