Capitalized = "A-SPEC"?
no, "A-Spec"
I think it's "specification".
You are not logged in. Please login or register.
Redump Forum → Posts by fuzzball
Capitalized = "A-SPEC"?
no, "A-Spec"
I think it's "specification".
Why isn't "A-spec" capitalized?
Have you tried to dump it several times with DIC? If yes, were the checksums the same every time?
I have tried several versions and they all have the same checksum.
20191116, 20190629, 20181022, 20180630
verifying http://redump.org/disc/28214/
dic: doesn't match db (1 error), logs: https://www.mediafire.com/file/t6kw2n7jz1buy8w
IsoBuster: matches db (no error)
Which is correct?
@sadikyo (or another mods)
bump
Again IMHO, it's significant to indicate different print runs/different ringcodes, at least when they result in different dumps when using the same standard dumping method.
I agree with you, but what I want to know is the current rules.
This is a continuation of http://forum.redump.org/post/74976/#p74976
Because 2 different prints are known, the first was dumped as 0 (as usual), another needs the -294 offset to match the entry (it's pointless to add different prints of the same disc as separate entries, since the whole disc contents is shifted).
Aren't these pointless?
Vampire Hunter: Darkstalkers' Revenge (Japan) (1M)
Vampire Hunter: Darkstalkers' Revenge (Japan) (2M, 4M)
Vampire Hunter: Darkstalkers' Revenge (Japan) (3M)
e:\tmp>fff -crc=$9921da39 "Vampire Hunter - Darkstalkers' Revenge (Japan) (2M, 4M) (Track 2).bin"
FindFileFragment @20100709 / themabus@inbox.lv
----------------------------------------------
Input: Vampire Hunter - Darkstalkers' Revenge (Japan) (2M, 4M) (Track 2).bin
Offset: 0
Size: 3880800
CRC: 9921da39
Shift: both
Step: 4
Range: 20000
Offset correction 0 bytes, CRC-32 ea2afe21
Offset correction 4 bytes, CRC-32 9921da39
Fragment found!
e:\tmp>fff -crc=$9921da39 -shift=r "Vampire Hunter - Darkstalkers' Revenge (Japan) (3M) (Track 2).bin"
FindFileFragment @20100709 / themabus@inbox.lv
----------------------------------------------
Input: Vampire Hunter - Darkstalkers' Revenge (Japan) (3M) (Track 2).bin
Offset: 0
Size: 3880800
CRC: 9921da39
Shift: right
Step: 4
Range: 20000
Offset correction 0 bytes, CRC-32 8b3d5dce
Offset correction -4 bytes, CRC-32 54b68c45
Offset correction -8 bytes, CRC-32 5929eff5
Offset correction -12 bytes, CRC-32 1930b238
Offset correction -16 bytes, CRC-32 9921da39
Fragment found!
Has the rule changed?
@sadikyo
If it has not been changed, please discard EXE date change.
need to fix the foreign title of Wizardry V
I see. I respect the title screen and the size of the logo.
I want to search the data including the Japan region.
Can the Japan region include "Japan, Asia", "Japan, Europe", etc.?
Why is the original title used instead of the Japanese title?
http://redump.org/disc/39005/
http://redump.org/disc/64842/
Also, "災禍の中心" will not appear in the TOWNS version of Wizardry V.
http://redump.org/disc/40347/
I do not have an opinion and follow the decided rules.
Understood. I don't care.
I need an account for DICUI.
username: fuzzball_for_dicui
I noticed that the cause was login by DICUI.
There are no unread posts recently.
DICUI is fixed now in WIP builds. The error file was renamed between builds. This has been addressed. If anything like this comes up again, please ping on Discord in the #discimagecreator channel. I rarely look in this thread for DICUI related anything.
Thank you for the quick fix.
I do not use Discord, so I will report on GitHub.
Has the new version (2019-03-26) changed the return code?
Error in DICUI (1.12.1).
I think Shift-JIS with its wide symbols is a standard for Japanese typing.
I feel ASCII characters are often half-width.
DICUI(1.10) extracts Sega Saturn's PVD from sector 0.
It has already been fixed.
https://github.com/reignstumble/DICUI/issues/118
Redump Forum → Posts by fuzzball
Powered by PunBB 1.4.4, supported by Informer Technologies, Inc.
Currently installed 6 official extensions. Copyright © 2003–2009 PunBB.