DCI4VMI v1.0

Printable View

January 26th, 2006, 02:32
wraggster

1 Attachment(s)

DCI4VMI v1.0

Date of Release

December 26th 2005

Title

DCI4VMI v1.0

Author

bucanero

Information

I´ve coded a simple tool to convert Dreamcast savegames between Nexus .DCI format and .VMI/.VMS format.

I know there are other tools to do this same job, but I think this is the first tool to handle both-way conversions (DCI <-> VMI/VMS) without any other parameter than source file (a DCI or VMI file) and destination file (for .DCI target) or resource name (for .VMI/VMS target).

Website

http://www.bucanero.com.ar/verpost.php?id_noticia=181
March 19th, 2006, 01:23
fackue

I tried converting to a DCI file and I get

[+] Reading crzytxi2.VMI ... ERROR: Can't open crzytxi2TIFIER".VMS!
[-] Source file crzytxi2.VMI could not be readed.
[-] Failed!
March 19th, 2006, 15:58
bucanero

can you send me the crzytxi2.VMI/VMS files you're trying to convert to see what's the error there? And also let me know your OS, version, and any other tip that might be useful for bugfixing.

btw, have you tried to convert the same VMI with my win32 tool "DC Save Converter"? if you can, try it and let me know if you get the same error there too.
March 19th, 2006, 22:00
fackue

vmu_saves.zip

I'm using WindowsXP Pro. I edited/created the VMI file with VMI File Writer and since I don't have the .NET FRAMWORK installed, I can't use DC Save Converter.
March 21st, 2006, 02:32
bucanero

thanks for the files... I'll check them out and post the results
March 22nd, 2006, 01:13
fackue

I'm curious what you found out.
March 26th, 2006, 16:13
fackue

The VMI was created with an older build of VMI Writer, but, even after using the new VMIs it's basically the same problem.

I could suggest, it might be the way it's reading the file name. You might wanna, if you want to, look there.
March 28th, 2006, 16:24
SiZiOUS

Quote:

[+] Reading crzytxi2.VMI ... ERROR: Can't open crzytxi2TIFIER".VMS!

May be it's a $00 string end missing.
March 30th, 2006, 13:07
bucanero

Quote:

Originally Posted by SiZiOUS

May be it's a $00 string end missing.

Yes, I agree, I had the same idea, but I'm over the edge lately! :( lots of work at my job and I'vent had time to check my hunch.

The other thing that I want to check is that the .vmi file and my read routine are 100% complaint with the standard (at least the standard posted by Marcus Comstedt at http://mc.pp.se/dc/vms/vmi.html )
March 30th, 2006, 15:14
fackue

That VMI didn't use $00 to pad the remaining bytes of the text fields, but the following does:

http://www.consolevision.com/members...pliant vmi.zip
March 30th, 2006, 15:22
SiZiOUS

I tested your proggy with fackue's VMI files. I got this :

Code:

F:\Documents and Settings\SiZiOUS\Bureau>dci4vmi crzytxi2.VMI crzytxi2.DCI DCI <-> VMI/VMS Tool v1.0 El Bucanero - www.bucanero.com.ar [+] Reading crzytxi2.VMI ... OK! [i] Name: C_TAXI02.SYS [i] Size: 10240 bytes [i] Type: Data File [i] Date: 13 Mar 2006 [i] Time: 01:27:30 [i] Copy Protected: No [+] Writing crzytxi2.DCI ... OK! [+] All done!

Code:

F:\Documents and Settings\SiZiOUS\Bureau>dci4vmi crzytxi2.DCI crzytxi2 DCI <-> VMI/VMS Tool v1.0 El Bucanero - www.bucanero.com.ar [+] Reading crzytxi2.DCI ... OK! [i] Name: C_TAXI02.SYS [i] Size: 10240 bytes [i] Type: Data File [i] Date: 13 Mar 2006 [i] Time: 01:27:30 [i] Copy Protected: No [+] Writing crzytxi2.VMI ... OK! [+] All done!

It works :D
March 30th, 2006, 17:35
fackue

Code:

C:\Documents and Settings\Cyle\Desktop>dci4vmi.exe crzytxi2.vmi crzytxi2.dci DCI <-> VMI/VMS Tool v1.0 El Bucanero - www.bucanero.com.ar [+] Reading crzytxi2.vmi ... ERROR: Can't open crzytxi2PATHEX".VMS! [-] Source file crzytxi2.vmi could not be readed. [-] Failed! C:\Documents and Settings\Cyle\Desktop>dci4vmi.exe crzytxi2.VMI crzytxi2.dci DCI <-> VMI/VMS Tool v1.0 El Bucanero - www.bucanero.com.ar [+] Reading crzytxi2.VMI ... ERROR: Can't open crzytxi2 Files".VMS! [-] Source file crzytxi2.VMI could not be readed. [-] Failed! C:\Documents and Settings\Cyle\Desktop>dci4vmi crzytxi2.VMI crzytxi2.DCI DCI <-> VMI/VMS Tool v1.0 El Bucanero - www.bucanero.com.ar [+] Reading crzytxi2.VMI ... ERROR: Can't open crzytxi2s\Comm".VMS! [-] Source file crzytxi2.VMI could not be readed. [-] Failed!

Same result.
June 16th, 2006, 20:31
Suxen

1 Attachment(s)

Any update on this one? It's definitely 8 character VMS files that are the culprit, as someone else said 00 is only used to pad when there is < 8 characters making up the name in the VMI file of the VMS file.

Example below, doesn't convert. When I edited the name in the VMI file to 7 characters and a 00 byte, it did work.

It's pretty much there, would be great to see this final little bug fixed :)

Error with the original is:

Code:

E:\DC\Copy>dci4vmi.exe 00001334.VMI 00001334.DCI DCI <-> VMI/VMS Tool v1.0 El Bucanero - www.bucanero.com.ar [+] Reading 00001334.VMI ... ERROR: Can't open 00001334JSE;.W".VMS! [-] Source file 00001334.VMI could not be readed. [-] Failed!