The above video goes away if you are a member and logged in, so log in now!
Mode1 to Mode2/XA conversion possible?
Mode1 to Mode2/XA conversion possible? –
It seems that most tools when converting a BIN/CUE to ISO will change the Mode from Mode2/XA to Mode1. Is there any tool existing that can convert the mode back to 2? Any image format is okay. Thanks.
what exactly are you trying to do?
I'm trying to convert a Mode1 ISO or BIN/CUE to Mode2/XA because I am under the impression that PS2s only play Mode 2 discs?
burn the iso with cdrwin, it has an option you can tick that will force an iso to be burned in mode2 XA
Beginning with what version of CDRWin has this option?
Well I don't know what you're going to convert. But let me explain what will be your problem: (probably)
12 byte of syncronisation data, 4 byte header (min, sec, frame, mode), 2048 byte USER DATA, 288 extra data (4 byte edc, 8 byte empty, 172 byte P, 104 byte Q subcahnnel data (these two are as ECC))
Mode 2 XA:
12 byte of syncronisation data, 4 byte header (min, sec, frame, mode), 8 byte subheader (2 byte data, 2 byte channel, 2 byte submode, 2 byte data type), 2324 byte USER DATA, 4 byte EDC (optinal)
As you can see, there is much more data on the Mode2/XA disk. If an original disk was grabbed as Mode1, then converting it back to Mode2/XA, well none will fill the missing data, but you'll get a shorter file in the end, which is shifted, as the missing bytes will be filled from the next mode 1 sector. This is the first problem. In case that was a Mode2/XA image (not that probable, but who knows) then the problem is much easier as you simply have to create a cue file for that. As earlier said, the question is that what you're going to convert to PS2 format. Just a note: Mode1 disks also can be read on a PS2, I always write my divx films in Mode1 (just because of a much better error correction) and Mediaplyer plays them just fine. Ok, those won't boot that's sure, BUT as I said, if you had a game grabbed the wrong way, and you're going to convert that back, that won't be successfull.
pS: Most tools are smart enough and knows that ISO means Mode1, and the original ISO file can contain only ONE data track. This is why they convert your bin/cue to Mode1. (and that way, they lose "some" byte, that's it) Your original CUE was the descriptor file how to handle the bin, in worst case the bin file contains audio tracks aswell, the chance to get them separated from the data well, it's a dirty work.
Many thanks for the indepth reply (although I admit I didn't quite understand all of it).
Here is my issue. I ripped an image to BIN/CUE to patch it with a PPF. At this point it is Mode2/XA. Then I decided to upload it to my PS2 using HDL_dump 0.6 network transfer but to do that you have to convert it to ISO format (at least I think so...). So like you said, it is now a Mode1 disc. It boots fine from the HD.
I have some of my originals in storage since I've moved. So I want to just extract the game off my HD and burn it to make more room on my HD, but I am afraid if I burn the ISO as is, it won't boot. So yes, I do need Mode2/XA as I need it to boot. However, with the shifting bytes, is that similar to LBA values changing? If so, I don't think the precise values affect booting that much (as I boot homebrew apps and it doesn't seem to have a huge impact if I shift LBA values around). If I convert Mode1 back to Mode2/XA it should still work. Assuming such a tool exists (like G mentioned CDRWin forcing mode burning).
If it is an .ISO format file can I even create a CUE file for it? Telling it to handle the .ISO file as a Mode2/2324 image when it burns it? Or should I just convert it back to BIN/CUE and edit the cue to handle the BIN file as a Mode2? If so, should I change the size of the USER DATA from 2048 to 2324?
By the way I did run an experiment in which I tried to create an ISO image that was Mode2 with Alcohol 120% and it worked. All the other burning applications I have recognized it as an ISO image in Mode2 format. I burned it and it booted fine.
Thanks again for the input, it is greatly appreciated.
Well, there are two type of iso's.
One is the original: mode1 data 2048 byte/sector the other is the one todays cd/dvd software create: 2352 byte/sector. This later is not really an iso, but a raw file that contains everything, and we can call it as we want. Clever programs will scan its content and tell what mode it uses. Programs like burnatonce or cdrwin need a descriptor file that tells what mode this raw file uses. (and how many USER bytes are in one sector) If you create an image with alcohol, it will create a file with 2352 byte/sector, and it names it as ISO. Grabbing the same disk with cdrwin will create a BIN file and a descriptor file with the following content:
FILE "XXXXXXXXX.BIN" BINARY
TRACK 01 MODE2/2352
INDEX 01 00:00:00
Is there any difference ? No, you could use the same ISO as created with Alcohol here, just rename it to BIN. The two files (bin and iso) will contain the same data. This is why there are so many problems as file extensions cause a lot of missunderstandings. As the converter programs will convert your data to MODE1 (as the original ISO means Mode1, data track).
You can easily check whether your image is an original ISO or not. Divide the file length by 2352, if the results is a number with no remainder, then you can burn it with Alcohol (check whether it reports Mode2 Form1 or not) and it will boot. If there is any remainder, then that image is not a 2352 raw mode file, you then have an original 2048 byte Mode 1 ISO image (which is not going to boot on the PS2). Unfortunatelly I do not know (as I do not have any PS2 HDD) how the files are stored on the PS2 hdd, and how can you create an image from the hdd. But I am sure those tools that I know of will create an original iso with 2048 byte/sector that won't be ok for you. The solution may be not to use iso, but raw/bin image those are 2352 byte/sector files and can be written with almost any sw, and those probably will boot. I'll look into it as I have time.
So essentially, Mode2 images are a raw read, and when Alcohol makes an ISO of a Mode2 disc it simply creates a BIN file that does not use a CUE descriptor file? Okay it makes more sense now, much appreciated.
The programs I use to extract an ISO from the HD creates an ISO image, which by the standard defintion you've given me is a Mode1 ISO. I haven't checked but I am pretty certain as the file size is more consistent with a Mode1 image rather than the notably larger Mode2 sizes. So I already have the image, Mode1 ISO, I just need to convert it into something bootable.
So back to the original question, is it possible to convert this Mode1 ISO into a Mode2 CUE/BIN or other image format? By your proposed solution I would convert it into a Mode1 BIN file, and then somehow convert that BIN into a Mode2 BIN?
Many thanks for your input.
The problem will be that several games check where files are phisically located on the disk... (this is why a lot of games do not work from hdd) If you create an image with a tool, the files won't be on the same physical address as they were on the original disk... http://ps2dev.org/kbversions.x?T=593 will help. Also, there are tools that generate PS2 disk images, which can be simply burnt to a disk with any burning software. NOTE: to boot a disk, files have to be arranged and cd checks can cause problems, except if you have a TRUE 1:1 copy.