Hello Guys there are 2 files in particular that I'm talking about
kinst.chd and kinst2.chd

I'm using Mame32k v0.67 this is the version that has netplay
when i do audit games it tells me this

kinst : kinst.chd 6d4c2f152c9a18ab3a9b05b8804306a8 NOT FOUND
kinst2 : kinst2.chd 2563b089b316f2c8636d78af661ac656 NOT FOUND
Audit complete.


I Have no idea what to do i have the chd files
i put the chd files in the root /rom dir
i put them in the zip folder
and i also put them in a folder by themselves i.e /rom/kinst


no matter what i do I get that error all the time
my question is how do i fix it

i have mame v0.95 and that does not have netplay but it runs the roms perfectly
what can i do to make these roms work id like to play online with people

thanks in advance
anthony


I am using Mame v0.95 this dosent have netplay and both killer instincts work fine

I noticed that in version 0.95 i can Killer instinct version 1.4, 1.5d , and 4.7 and ki2 i have version 1.4 and 1.4 upgrade kit these work fine i can play them no problem

but in mame32k v0.67 it wants killer instinct version 1.0 and killer instinct 2 version 2.1

are the chd files i have only for the versions that mame 0.95 supports if yes where can i get the chd files that are supported by mame's multiplayer version
thanks in advance!

The problem most likely is that MAME v0.67 requires a version 1 format CHD file, while your MAME v0.95 is using a version 2 format CHD file.

You can use chdman from MAME 0.95 to extract the image:

chdman --extract kinst.chd kinst.raw

and then use chdman(1) from MAME 0.67 to create the CHD:

chdman(1) --createhd kinst.raw kinst.chd

NOTE: 1. chdman may have a different name for MAME 0.67

ok i did that but it creates the exact same file size :( is there a way to revert the chd back to an older state? is it ok if i use the same chd file to create both files????

i did what u said and it creates a file the same size as the chd file i currently had


the chdman.exe that i am using is from mame 0.84b because the 2 versions i have (version 0.67 and version 0.95) didnt come with a chdman.exe

Maybe it's the version of mame you're using that's not compatible with those CHDs. That would be my best guess.

where would i go about finding different chd files???
i.e. different versions of these chd files?

You will need hdcomp from MAME 0.67 to create the version 1 CHD files. You can get hdcomp from the MAME 0.67 binary located on theMAME.net - Older MAME Versions page.

When you create the kinst.chd for MAME 0.67 you should do the following:

1. cd ../ROMS-104/kinst

2. extract the kinst.raw image as mentioned in previous post

3. change to a directory where you have your MAME 0.67 ROM set

cd ../../ROMS-67/kinst

4. Now use hdcomp to create the chd

hdcomp -create ../../ROMS-104/kinst/kinst.raw kinst.chd

This way you will still have both the version 1 and version 2 format CHDs.

anyone have an idea of where i can get older chd files or how to make an existing chd file turn into an older one?

My previous post which stated you needed to use chdman to extract the image, and hdcomp (from MAME 0.67) to create the CHD didn't work?

As this is the only way to change a current CHD file into the older CHD format.

kinst : kinst.chd 6d4c2f152c9a18ab3a9b05b8804306a8 INCORRECT MD5: 9c25d9ff2404f759e1c646b966cb7b18


thats my new error after i did the remaking of the file 95629312 is the size of my original one my new one is 95621120 so i might be getting somewhere what is this md5 error?


what exactly is the md5??? and why is there an error now?

If I put the NEW kinst.chd (the one that I just made with the size 95621120) into the mame that had the other kinst.chd (95689312) <--this was the file that is not allowing me to play on the internet via kaillera i get this error doing an audit

kinst : kinst INCORRECT CHECKSUM:
EXPECTED: SHA1(a37a2c5e52ea936a715210d237874dd573bb002f) MD5(6d4c2f152c9a18ab3a9b05b8804306a8)
FOUND: MD5(9c25d9ff2404f759e1c646b966cb7b18)
kinst14 : kinst INCORRECT CHECKSUM:
EXPECTED: SHA1(a37a2c5e52ea936a715210d237874dd573bb002f) MD5(6d4c2f152c9a18ab3a9b05b8804306a8)
FOUND: MD5(9c25d9ff2404f759e1c646b966cb7b18)
kinstp : kinst INCORRECT CHECKSUM:
EXPECTED: SHA1(a37a2c5e52ea936a715210d237874dd573bb002f) MD5(6d4c2f152c9a18ab3a9b05b8804306a8)
FOUND: MD5(9c25d9ff2404f759e1c646b966cb7b18)
Audit complete.

I would assume kinst.chd that needs to work on the net needs MD5: 9c25d9ff2404f759e1c646b966cb7b18 and the kinst.chd that I have that is working has MD5: 6d4c2f152c9a18ab3a9b05b8804306a8

How would i go about making the md5 be 9c25d9ff2404f759e1c646b966cb7b18????


I tried doing an update with chdman -update kinst.chd newkinst.chd
when i tried to audit with the new chd file i get the same error as b4 file not found....it would seem updating the md5 file via chdman brings me back to square one therefore id maybe like to know how to get my chd to have this 9c25d9ff2404f759e1c646b966cb7b18 hash #???




btw i cant extract the kinst2.chd it is giving me this error
"ERROR READING HUNK 27577 FROM CHD FILE: DECOMPRESSION ERROR"
but that i can worry about later im more interested in getting this one to work

Quote:

MD5 is a checksum for the original HardDisk Image, the error indicates that the conversion to a CHD file failed.

This is from a 'chdman -info kinst.chd':

chdman - MAME Compressed Hunks of Data (CHD) manager 0.90 (Jan 19 2005)
Input file: kinst.chd
Header Size: 120 bytes
File Version: 3
Flags: NO_PARENT, READ_ONLY
Compression: zlib+
Hunk Size: 4096 bytes
Total Hunks: 32002
Logical size: 131,076,608 bytes
MD5: 6d4c2f152c9a18ab3a9b05b8804306a8
SHA1: a37a2c5e52ea936a715210d237874dd573bb002f
Metadata: Tag=47444444 Length=34
CYLS:419,HEADS:13,SECS:47,BPS:512.

The most likely problem with the conversion using hdcomp is that hdcomp didn't use the correct CYLS, HEADS, SECS, or BPS when it created the file.

If you use 'hdcomp -info kinst-067.chd', it will show the MD5 checksum that it calculated, and what CYLS, HEADS, SECS, and BPS it is using.

If it doesn't match the above 'CYLS, HEADS, SECS', then try creating kinst-067.chd with:

hdcomp -create kinst.raw kinst-067.chd 0 419 13 47

NOTE: The meanings of these numbers are as follows:
Input Offset: 0
Cylinders 419
Heads: 13
Sectors: 47

then use 'hdcomp -info kinst-067.chd' to see if it created the CHD with the correct MD5 checksum.

If this works, then your going to need to do the same when creating the kinst2.chd.

hdcomp -create kinst2.raw kinst2-067.chd 0 1463 13 47