Jump to content
LaunchBox Community Forums

Nologic

Members
  • Content Count

    7
  • Joined

  • Last visited

Everything posted by Nologic

  1. @Zombeaver I'm certain with Dreamcast on being able to read the hex of a certain file on the disc to get the ID, and I'm fairly confident of being able to find the ID for PSX...no clue about Saturn or other optical disc's. But an INI or XML could be created that stores settings to be used based off an ID. Then a script could be written to load each person's disc's read the ID from them, then create a config based on the name of the disc, using the XML. The same could be done with Cart based games...only using the MD5 hash value. PlayStation DataCenter has a listing of PSX ID's While I still haven't found where the ID is stored on PSX...this tool Psx2PSP seems to find it no problem.
  2. What does this solve: Manually applying xDelta patches Manually downloading xDelta patches Requirements: 7zip AutoIt xDelta Internet Connection How: Upon execution of the script, it will unarchive any 7z, Zip, Rar files you have & get the CRC-32 value of the file, then use this to download the correct xDelta patch, then apply the patch. Then afterwords you will need to process the resulting file with ClrMamePro & DAT from No-Intro for proper naming and archiving. Instructions: Install 7zip if it's not already installed on your system. Install AutoIt and set it to execute scripts when double clicked. Now Right Click on Desktop and select "New\Folder" from the context menu, and Rename it "NDS Rom Update". Now open the folder "NDS Rom Update" and Right Click on it's background and select "New\Folder" from the context menu, and Rename it "Bin". Now once again Rick Click on the folders background and select "New\Folder" from the context menu, and Rename it "Fix". Now download & extract xDelta into "Bin" folder. Now download the AutoIt script "NDS Rom Update.au3" from this thread and save it to "NDS Rom Update" folder on your Desktop. Now open Windows Explorer or whatever your favorite File Manager happens to be and navigate the location of your ClrMamePro backups. i.e. "C:\Program Files\clrmamepro\backup\No-Intro\Nintendo - Nintendo DS (Decrypted)\" Now copy all the files there and any that might be under a folder called "_unknown" to your "Fix" folder. Now finally execute the AutoIt script "NDS Rom Update.au3" by Double Clicking it and if all went well after some time you'll get a dialog box saying the batch has completed...and you should have the resulting files in a new folder called "Fixed" Next time you run ClrMamePro use "Add-Paths" under Settings to add Fixed as one of the paths, you'll also need to check "Use Add-Paths" under ReBuilder then when you press the "Rebuild..." button it should pull in the new files. This is an old script of mine...and basically forgot about it...till I just did an audited on my NDS roms...600 M.I.A....ran this..did another audit...came down to about 200 M.I.A....so a big improvement. Your mileage will most certainly very. NDS Rom Update.au3
  3. Nologic

    CCD2CHD

    Question how are you guys going about converting CCD+IMG+SUB to CHD? So far because of the SUB file I've had to mount the whole thing in DaemonTools...then rip with ether UltraISO or PowerISO to get a workable BIN file with matching SHA-1 values. However the markup of the CUE files seems to create a noticeable size difference in the resulting CHD...so clearly the SHA-1 values aren't going to match at all. UltraISO CUE FILE "cd.bin" BINARY TRACK 01 MODE1/2352 INDEX 01 00:00:00 TRACK 02 AUDIO INDEX 01 00:32:32 TRACK 03 AUDIO INDEX 01 01:42:51 TRACK 04 AUDIO INDEX 01 03:33:61 TRACK 05 AUDIO INDEX 01 04:44:22 TRACK 06 AUDIO INDEX 01 05:17:00 TRACK 07 AUDIO INDEX 01 06:39:40 TRACK 08 AUDIO INDEX 01 11:58:05 TRACK 09 AUDIO INDEX 01 13:26:60 TRACK 10 AUDIO INDEX 01 18:57:53 TRACK 11 AUDIO INDEX 01 22:19:48 TRACK 12 AUDIO INDEX 01 27:14:57 PowerISO CUE FILE "cd.bin" BINARY TRACK 01 MODE1/2352 INDEX 01 00:00:00 TRACK 02 MODE1/2352 INDEX 01 00:32:32 TRACK 03 MODE1/2352 INDEX 01 01:42:51 TRACK 04 MODE1/2352 INDEX 01 03:33:61 TRACK 05 MODE1/2352 INDEX 01 04:44:22 TRACK 06 MODE1/2352 INDEX 01 05:17:00 TRACK 07 MODE1/2352 INDEX 01 06:39:40 TRACK 08 MODE1/2352 INDEX 01 11:58:05 TRACK 09 MODE1/2352 INDEX 01 13:26:60 TRACK 10 MODE1/2352 INDEX 01 18:57:53 TRACK 11 MODE1/2352 INDEX 01 22:19:48 TRACK 12 MODE1/2352 INDEX 01 27:14:57 UltraISO by the way made the smaller resulting CHD. IsoBuster when used to make a CUE\BIN created a larger BIN file & a more simplistic CUE file...and an massively smaller CHD file that I don't trust at all...I haven't tested it...just looked at the resulting file and called bullshit on it. Anyway here are the commands for the tools I'm using: \\ Mount CCD Image In Virtual CD Drive DTCommandLine.exe --mount --letter "I" --ro --path "G:\Emulation\Sega CD\After Burner III (USA)\After Burner III (USA).ccd" \\ UltraISO Rip Virtual CD Drive to CUE\BIN ultraiso.exe -silent -copy I: -output "G:\Emulation\Sega CD\After Burner III (USA)\After Burner III (USA).bin" >> OR \\ PowerISO Rip Virtual CD Drive to CUE\BIN piso.exe make-image I: -o "G:\Emulation\Sega CD\After Burner III (USA)\After Burner III (USA).bin" >> OR \\ ImgBurn Rip Virtual CD Drive to CUE\BIN ImgBurn.exe /MODE READ /OVERWRITE YES /SRC I: /DEST "G:\Emulation\Sega CD\After Burner III (USA)\After Burner III (USA).bin" /START /CLOSE \\ UnMount CCD Image From Virtual CD Drive DTCommandLine.exe --unmount --letter "I" \\ Convert CUE\BIN to CHD chdman.exe createcd -i "G:\Emulation\Sega CD\After Burner III (USA)\After Burner III (USA).cue" -o "G:\Emulation\Sega CD\After Burner III (USA)\After Burner III (USA).chd" \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\ CLI For DAEMON Tools Lite & Ultra DTCommandLine.exe --mount --letter "I" --ro --path "G:\Emulation\Sega CD\After Burner III (USA)\After Burner III (USA).ccd" DTCommandLine.exe --unmount --letter "I" \\ CLI For DAEMON Tools Pro DTAgent.exe -mount scsi, I,"G:\Emulation\Sega CD\After Burner III (USA)\After Burner III (USA).ccd" DTAgent.exe -unmount I So what tools are you using? I'll likely write an AutoIT script to do all this once I have things nailed down fairly well. Oh some FYI 267mb 7z archive 320mb Flat Files 200mb CHD UltraISO 269mb CHD PowerISO 169mb CHD IsoBuster
  4. Have you tried some of your games in CHD format?
  5. Not sure how that could be...as I send a command line string to CHDMan myself...the only thing I do while it's processing is peek at it's error stream to be able to display a progress dialog. Maybe you are running a x64 CHDMan and it's making better use of your memory and/or CPU...if that is the case swap CHDMan.exe's and it should result in more or less the same time. I'm doing a few more call's & doing more setup than CMD...but the difference should be Nano-Seconds. Past that...are you feeding my App Zip/Rar/7z...but only feeding CMD GDI...because that would be an unfair comparison...as decompressing stuff doesn't come free....time is involved. If doing GDI in both...mine will be slower as I said...but again only by a few nanoseconds or at most a couple of milliseconds. Look at the source code...I'm not doing anything crazy to CHDman to slow it down. I'll look into it all the same...but there should be no real measurable difference.
  6. If you are using a RetroArch core for SegaCD then you can probably use CHD conversions. File sizes should be close to that of RAR. A tool can be found here.
  7. Late to the show I see...but there is an update for GDI2CHD Only took me 9 years to get around to it. :) This is a Beta...some cosmetic stuff needs to be done and a few more features added. @ Thatman84 "CHDman FE" works with v5 syntax...but it's currently more limited in what it can do vs GDI2CHD v2...mostly because I haven't updated that (CHDman FE) in like 8 years. However whats left to cover that CHDman supports, is really only for those dumping games. However AntoPISA will probably want those features since I'm back at it again for the time being.
×
×
  • Create New...