I was sent a corrupted rpg file. I believ it was damaged by a bad hard
drive. After inputting the password in custom, it would just show a
blank screen. After some experimentation, I found that the palettes.bin
file was corrupted, and if I copied in a palettes.bin from some other
game, everythi
On 6 April 2012 10:46, James Paige wrote:
> I was sent a corrupted rpg file. I believ it was damaged by a bad hard
> drive. After inputting the password in custom, it would just show a
> blank screen. After some experimentation, I found that the palettes.bin
> file was corrupted, and if I copied i
On Sat, Apr 07, 2012 at 04:40:52PM +1200, Ralph Versteegen wrote:
> On 6 April 2012 10:46, James Paige wrote:
> > I was sent a corrupted rpg file. I believ it was damaged by a bad hard
> > drive. After inputting the password in custom, it would just show a
> > blank screen. After some experimentat
On 7 April 2012 17:24, James Paige wrote:
> On Sat, Apr 07, 2012 at 04:40:52PM +1200, Ralph Versteegen wrote:
>> On 6 April 2012 10:46, James Paige wrote:
>> > I was sent a corrupted rpg file. I believ it was damaged by a bad hard
>> > drive. After inputting the password in custom, it would just
On Sun, Apr 8, 2012 at 2:38 PM, Ralph Versteegen wrote:
> Anyway, while I was looking at the relumping code I realised it was
> quite delicate. If something goes wrong, you'll probably just get a
> silently corrupted RPG file. It should be possible to add some safety
> checks. Of course I have tro
On 7 April 2012 17:24, James Paige wrote:
> On Sat, Apr 07, 2012 at 04:40:52PM +1200, Ralph Versteegen wrote:
>> On 6 April 2012 10:46, James Paige wrote:
>> > I was sent a corrupted rpg file. I believ it was damaged by a bad hard
>> > drive. After inputting the password in custom, it would just
