Last edited by Mark30001; 12-28-2007 at 11:50 PM.
should be closed by the rules.... i'll let it open for some more experienced mods to close... and to give some download time to interested people.
will die soon tought.
i'll let everything be until kev checks it. but if you already had a chat with him it's surely ok.The rules:
Anything up to current generation is fine to share and post.
Anything CURRENT generation is fine to DISCUSS and
share documents but NOT dev tools.
i guess that is my misunderstanding... i consider xbox, dc, ps2 and GC still of this generation. :POriginally Posted by Borman
This is fine. Only question PS3, Xbox 360 3rd part apps, 1st part is fine. -A
Last edited by ASSEMbler; 12-28-2007 at 11:31 PM.
I'll create a monument to non-existance! Kefka, FFVI
"there is no dark side of the Moon really... as a matter of fact it's all dark" (words hidden in pink floyd's "Eclipse" song )
I already sent a PM to ASSEMbler to move the 'Katana SDK R2' thread from another forum section to here, so I assumed it was okay to continue posting the other SDKs.
Can someone post it somewhere else besides Megaupload?
I hope nobody tries to include this in a sale or trade. Besides thinking how illegal posting dev stuff is, think of all the assholes out there...
Description says LIES.....
*wishes the ASSEMbler FTP was still around*Originally Posted by PrOfUnD Darkness
Is there a download limit on MegaUpload (can't check here)?
Last edited by Mark30001; 12-28-2007 at 11:20 PM.
This is not current generation.
Basically, only ps3 3rd part apps, and 360 sdks are off limits.
Last edited by ASSEMbler; 12-28-2007 at 11:32 PM.
Looks like the limit is 700MB, and then it makes you wait 17 (or so) minutes. I don't know if it will give me another 700MB then, or just one file at a time with a time limit in between...Originally Posted by Mark30001
Oh, and THANKS! Something I always needed to get, but was never motivated to pursue... :rolleyes:
Last edited by Psycho; 12-30-2007 at 09:26 AM.
part 3 is down
Xbox Live - XxHennersXx
I've mirrored it here:Originally Posted by Mark30001
(The link should only work when referred from this site, but please don't spread it.)
I've taken the liberty of extracting the RARs into the bin/cue, and then converting it into an ISO - it's a much more universal format and I use a Mac so it was more convenient for me :-) Everything is otherwise unchanged.
[edit: updated link post-drama, bin/cue available at
Last edited by Stone; 07-04-2008 at 09:14 AM.
I hope you noticed that the format of the BIN was MODE2/RAW (2352 bytes/sector). This is not valid for an ISO! ISO can only be MODE1 with no EDC/ECC (2048 bytes/sector). So unless you completely rebuild the filesystem, it's unlikely that your ISO is of any use. But even if you did, it's no longer an XA disc then, which may break parts of the software.I've taken the liberty of extracting the RARs into the bin/cue, and then converting it into an ISO
My tip of the day:
Don't mess about with disc images, unless you know EXACTLY what you're doing.
Last edited by WindowsKiller; 07-03-2008 at 11:16 AM.
I wonder if you knew that ISO files only represent a ISO9660 filesystem with 2048-byte-sized blocks. They aren't disc images; they are filesystem images. Mode 1 and Mode 2 XA Form 1 discs both use 2048 byte sized blocks in their filesystems. The difference is the way the sector is structured, not in its filesystem. Since the block size hasn't changed, it's very likely that his ISO is the exact same ISO fs that was written to disc. Unless the Katana installer tries to low-level access the CD (which, of course, it doesn't), nothing will be broken.Originally Posted by WindowsKiller
My tip of the day:
Don't bitch about people's disc images, unless you know EXACTLY what you're talking about.
@darcagn: You're telling nonsense, and I don't even know where to start. Mode 2 uses 2336 bytes/sector for data, there's no such thing as Mode 2 with 2048 byte-sized blocks (see e.g. Wikipedia). Also, ISO images are not bound to the ISO9660 filesystem either, only to Mode1/2048 - that part of your post is nonsense, too (just like the rest). ISO images can have any filesystem, HFS, UDF, whatever (ever dumped a DVD, by the way?). You're dumping sector data, not the filesystem (which is on a higher level, so it doesn't matter when dumping).
I know what I'm talking about. I've wrote dozens of tools in the past to convert disc images, to auto-generate cue files, to read and dump discs with custom filesystems like 3DO, etc...
Anyway, you showed that you have no clue about CD-ROMs, so don't try to be smart. And I fail to see the motivation for your post. Just wanted to say something clever? That didn't work. And I love when people try to post in a similar way to the person they try to attack, using the same phrases. Too bad that your "tip" now makes you look like a fool because it applies to you, not to me.
Last edited by WindowsKiller; 07-03-2008 at 07:50 PM.
All the files are the same. It's a Windows disc full of Windows files for access by Windows, not a DC. If you explain why converting the raw image into a filesystem image is a problem I'm happy to upload in the original format, but there's no need to be a dick about it. I don't have to mirror it!
And yes, I did rebuild the filesystem, but you were too busy finding fault to check. Forget I said anything.
All CD-ROM formats use 2352 bytes per sector, it's how you divide them up that makes the difference.Originally Posted by WindowsKiller
There is a mode 2 that uses 2048 byte-sized blocks. It's called Mode 2 XA Form 1, and it provides 2048 _user data_ bytes/sector. Let's quote your precious Wikipedia:
"CD-ROM Mode 2 Form 1, usually used for computer data, has the same user data and error correction as Mode 1, but with a slightly different layout."
Mode 2 XA Form 2 provides 2336 bytes/sector for user data, because it's used for less critical data that can afford data loss, like a few frame drops in a video.
"CD-ROM Mode 2 Form 2, intended to be used for error-tolerant data such as audio and video, divides the 2352 bytes into 12 bytes of synchronization information, 4 bytes of header data and 2336 bytes of user data."
You do realize that what an ISO file represents is not a native format, correct? Either your burner or software will generate the error correction data for each sector that pads it out to 2352 and then burns the sectors to disc.Originally Posted by WindowsKiller
Yes, you can put any filesystem in a file laid out in 2,048 user data bytes/sector blocks and name it .ISO, but that doesn't make it a true ISO file. Of course, it's been done so much that it doesn't matter anymore and the the line of distinguishment is certainly blurred.Originally Posted by WindowsKiller
I know what I'm talking about; I've done tons of dumping work with Dreamcast GD-ROMs, including plenty of work mucking around with ISOs and filesystems. And you thought you were the only person who's seen a CD-ROM!Originally Posted by WindowsKiller
How about calling out a jackass? The guy's image works fine. It was completely unnecessary for you to call him out for absolutely nothing.Originally Posted by WindowsKiller
I know you are, but what am I?Originally Posted by WindowsKiller