xboxswap not working

[theroflol]

Version 20220909

Describe the bug The "xboxswap" command does not work despite having theoretically done the swap procedure correctly.

Screenshots DiscImageCreator.exe xboxswap G X:\mgs2.iso 16 292928 520508 759578 915118 1066092 1218024 1377954 1527140 2218604 2367520 2526692 2681858 2832350 2991436 3143584 3453874

Disc title Metal Gear Solid 2: Substance

Disc ringcode Unknown

URL Tell me the link to get the disc. Amazon: https://www.amazon.com/Metal-Gear-Solid-2-Substance-xbox/dp/B00006F2ZQ/ref=sr_1_5?keywords=metal+gear+solid+xbox&qid=1669684247&sr=8-5 eBay: https://www.ebay.com/sch/i.html?_from=R40&_trksid=m570.l1313&_nkw=metal+gear+solid+2+xbox&_sacat=0 discogs:

Log file ~~stranger_20220809T091705.txt stranger_disc.txt stranger_drive.txt stranger_mainError.txt stranger_mainInfo.txt stranger_volDesc.txt~~ mgs2_20220909T220450.txt mgs2_disc.txt mgs2_drive.txt mgs2_mainError.txt mgs2_mainInfo.txt mgs2_volDesc.txt

The drive I'm using is an iHAS124. If I run the command quickly after the drive closes, I get NOT_READY - LUN_NOT_READY - BECOMING_READY rather than the error from the log files. Similar results with test version. Is the problem with my drive, my trap disk, or something else? EDIT: uploaded the wrong log files

[saramibreak]

mgs2_mainError.txt says

NOT_READY - MEDIUM NOT PRESENT - TRAY CLOSED

It seems the drive failed to recognize the trap disc.

[theroflol]

That’s the error message I’m getting after swapping the game. It reads the trap disk just fine.

[theroflol]

The following file contains the output of the console if I run the xboxswap command with the trap disk in the drive. trap.txt Could this have something to do with the game not being read when swapped in?

[saramibreak]

The size of the trap disc is short. Your disc is 3629408, but 3820880 is needed to use xboxswap.

[theroflol]

That's probably the issue. I'll try to get a proper image to burn.

[theroflol]

I was able to get xboxswap to begin copying the game once I created an image file of the right length and an mds file that specified the right layerbreak, burned it to a DVD, then removed the drive cover instead of using the emergency eject method. When I used the emergency eject method, I got the same results as initially. However, at precisely the layerbreak, I get the results shown in the following log files. mgs2_20220909T220450.txt mgs2_disc.txt mgs2_drive.txt mgs2_mainError.txt mgs2_mainInfo.txt mgs2_volDesc.txt Since it's at the layerbreak, I suspect it may be an issue with how the trap disc was burned as defined by the mds file. Would using PTP or OTP be correct for an XBOX game, or is that even what the issue is?

[saramibreak]

Was dumping failed partway?

[theroflol]

Yes. Dumping failed once it reach the layerbreak.

[saramibreak]

https://github.com/saramibreak/DiscImageCreator/wiki#how-to-create

XBOX: DVD (Length is 3820880 or larger, Layerbreak is 1913776 or larger)

Did you prepare the DVD that has above enough size to create the trap disc?

Setting LayerBreak manually (L0 sector num is about a half size of DVD length)
e.g. If DVD length is 3900304, L0 sector num is about 1950160

Did you set LayerBreak correctly?

[theroflol]

According to ImgBurn, My image has 3820880 sectors and the layerbreak is set at 1913776.

[theroflol]

I burned this image to a blank DVD+R DL.

[saramibreak]

The advice I can is here...

• Try to dump other xbox disc. If it's success, the burned image is no problem.
• If other xbox disc also fails to dump, please create the image file using length is larger than 3820880 and layerbreak is larger than 1913776.
• If still it fails, change the other drive.

[theroflol]

I have yet to successfully dump a disc, but I have done some further testing. Any other game on the iHAS124 has failed immediately with L-EC - UNCORRECTABLE ERROR. However, after switching drives, specifically to a Hitachi-LG GSA-H30L, it is now failing with MEDIUM_ERROR - ID CRC OR ECC ERROR, which is new. Also, with some of my games I've actually gotten a partial dump out of them. Here are some log files from all the ones from which I've gotten a partial dump: stranger_disc.txt stranger_drive.txt stranger_mainError.txt stranger_mainInfo.txt stranger_volDesc.txt kotor_disc.txt kotor_drive.txt kotor_mainError.txt kotor_volDesc.txt kotor_mainInfo.txt mgs2_20220809T091705.txt mgs2_disc.txt mgs2_drive.txt mgs2_mainError.txt mgs2_mainInfo.txt mgs2_volDesc.txt With these results in mind, is the problem at this point that my game discs are just bad? None of them are in pristine condition, though the amount of damage varies. They do all still play on an actual xbox, however.

[saramibreak]

I only confirmed it by GSA-4163B. I'm not sure but your drive may not support...