xboxscene.org forums

Author Topic: U64 Chd To Img  (Read 44 times)

typerkoncepts

  • Archived User
  • Newbie
  • *
  • Posts: 8
U64 Chd To Img
« on: April 13, 2005, 09:44:00 PM »

Does anyone know how to conver the mame CHD file for KI 1 and 2 to the IMG filetype that u64 requires to run both games? i've been trying all night to figure it out after ig ot the emulator working... any help would be greatly appreciate (i got a bunch of other mame chd's maybe you'd be interested in a trade)

Thanks
Logged

Prican24

  • Archived User
  • Sr. Member
  • *
  • Posts: 470
U64 Chd To Img
« Reply #1 on: April 13, 2005, 10:00:00 PM »

use the search, theres been a few topics about it ;)
Logged

typerkoncepts

  • Archived User
  • Newbie
  • *
  • Posts: 8
U64 Chd To Img
« Reply #2 on: April 14, 2005, 02:12:00 PM »

i can see how to do it using chdman and a hexeditor but i also dont know how to use a hexeditor i downloaded a freeware software and opened the RAW file that was split using chdman with the kinst.chd file and i see a bunch of numbers but i dont know which to edit...
Logged

typerkoncepts

  • Archived User
  • Newbie
  • *
  • Posts: 8
U64 Chd To Img
« Reply #3 on: April 14, 2005, 02:32:00 PM »

>Reversing - Not for the faint of heart
>To get usable image for U64Emu use the "hdcomp -extract" option and prepend the following hex strings
>KI: "4147 2034 3139 2031 3320 3437 0A" or KI2: "4147 2038 3133 2031 3620 3633 0A"
>Also, for KI2 trim the file length to 419,586,061 (With above header) bytes (LBA had been used)

The process is actually incredibly easy.

The first thing to do is extract the CHD to an IMG - and to do this you use a "hdcomp -extract" command, for example, something like this "hdcomp -extract kinst2.chd" or "hdcomp -extract kinst2.chd ki2.img" should work.

Then, you need to prepend those hex values - N.B. it says prepend - NOT append. So, grab your favourite Hex Editor - there are plenty of freeware ones on the internet, install this, load in the IMG file and type in the required bytes in the hex area - double check they are entered correctly, and then save the changes.

If you are doing KI2, then you can also use HexEdit to chop off the required ending bytes so that the file length is precisely 419,586,061 - go down to the end of the file, and then use the Backspace key to delete everything up to the required position.

Save the changes to disk, and away you go - the IMG file should now work with U64Emu.

Keep backups just in case you muck something up - such as entering the required strings of data as text instead of hex.

Hoefully, all it should take is a few minutes work, and you should then be ready to rock.

--------------------------------------------------------------------------------



Good luck, If needs be, I'll take a look later and post a diff file (if I can get it to work


This is the directions i'm using but they're not really specific to Hexeditor noobs.

This post has been edited by typerkoncepts: Apr 14 2005, 09:33 PM
Logged

Pasoa2021

  • Archived User
  • Newbie
  • *
  • Posts: 16
U64 Chd To Img
« Reply #4 on: April 14, 2005, 08:43:00 PM »

I tried to do this also with no luck.

You're better off "finding" the img file.
Logged

typerkoncepts

  • Archived User
  • Newbie
  • *
  • Posts: 8
U64 Chd To Img
« Reply #5 on: April 14, 2005, 08:49:00 PM »

this is really annoying, its my 3rd day in a row i've been trying to figure this out, nekkid can't be found anywhere, no one can tell me how to "prepend" the shit in hexeditor and if i ask anyone i get the "search" response anyway. piece of shit.
Logged

Scoobysnaxx

  • Archived User
  • Full Member
  • *
  • Posts: 113
U64 Chd To Img
« Reply #6 on: April 14, 2005, 10:19:00 PM »

SIMILAR THREAD

QUOTE(SpIdErXeN @ Mar 26 2005, 05:38 AM)
I used a converter called chdman to extract kinst.chd to kinst.raw.  I then renamed kinst.raw to ki1.bin.  Then next i used a bin to img converter called nekkid.com 1.0 to convert ki1.bin to KI.IMG.  I then copied KI.IMG directly into the KI1 folder along w/ the kinst roms from the basic kinst.zip file whcih can be found in the latest mame releases and the file for that is about 4 megs or so...

Problem is, Kinst2.chd came out way after nekkid.com 1.0, and i couldnt find a utility to convert kinst2.bin to KI2.IMG...therein lies the problem.  I can get ki1 to work w/ the new emu, but i cannot get ki2 to work with it because i cant convert the kinst2.bin to KI2.IMG.  If anybody has a fix or knows anything about resolving this, please let us know.
*

Seems he at least got the one working? Just wondering if you seen this. I've never tried it myself (not a big KI fan)

Have you also tried the TEAMxxx Site?I'm sure they have a board with a tonne of people asking the same question. Lots of French though.

Hope it helps  :beer:

This post has been edited by Scoobysnaxx: Apr 15 2005, 05:23 AM
Logged

typerkoncepts

  • Archived User
  • Newbie
  • *
  • Posts: 8
U64 Chd To Img
« Reply #7 on: April 15, 2005, 07:50:00 AM »

i understand what u're saying but "Problem is, Kinst2.chd came out way after nekkid.com 1.0, and i couldnt find a utility to convert kinst2.bin to KI2.IMG..."

I can't find a utility either since i cant find nekkid anywhere.
Logged

Nuroravage

  • Archived User
  • Newbie
  • *
  • Posts: 20
U64 Chd To Img
« Reply #8 on: April 16, 2005, 02:18:00 AM »

anyone have this problem ,

im using the same ki 1 and 2 files i used in the u64 windows emu, - half circles back and kick  always worked - and selecting idoll through cinder worked too  , with any versions of the xbox u64  i  have difficulty diubg hcb and kick and idol is not selectable   -, ive tried with xbox controller and arcade control - like i used with the pc version

 i also remember there being issues between versions of Killerinstinct 1 where these problems were issues  - just odd , that it works well in one and not in the other

 confirmation?

thanx
Logged