Drmd Loosing Its Savestates...

[Reesy]

Thanks for all the advice, sync() will now be appearing in a DrMD near you. I might get chance to fix this and a couple of other bugs tonight. I'll let you all know

 

[Quiest]

You didn`t fix the flickering menu yet, no? Just asking because you said it`s much work...

 

[Reesy]

Nah I haven't implemented quad buffering in 16bit mode yet, in fact I've not touch DrMD since the last release. I was suffering a bit of burnout so I've had a couple of days off. Might get some stuff done though

 

[miq01]

fclose() will perform fflush() automatically - so your buffered data will be written to the file system. However, that's not the problem - what you really need to do is call sync() after fclose(), which causes all filesystems to flush their writeback caches to the physical device.

Just to confirm that it works. I opened Tilematch, played for one minute, saved my score, and immediately after that, I turned GP2X off without quitting. After starting again, that score was there. Thanks!

 

[God Ginrai]

Heya guys,

I'm having trouble with DrMD. I am launching a rom ( for instance, Sonic3), playing a tad, then making a savestate ( L+R to go back in menu, i select "save state", choose slot0, menu says slot is used, perfect, fine).

I can then load it just fine, it works flawlessly.

However, sometimes, when i load back DrMD, it says that no savestate is used... i know somebody which had the same bug, all savestates disappearing.

I have trouble reproducing it though ( sorry reeesy, can't give you more info).

Anyone else has the very same problems ?

​

First off, why are you using Savestates with Sonic 3? I'm pretty sure that ROM can save onto itself, no save state required. (If it's not a dirty rom that is)

 

[Reesy]

Because you would have the same problem. I never use sync(), so even after saving a sram file, if you switch the gp2x before linux decides to actually write the file to disk you will be buggered.

I've just tested sync and it looks like it fixes the problem. I'll release another version a bit later then you lot can do your worst to it

 

[triton]

i hope you can get to fixing the menu thing sometime soon, it gets very distracting, and the savestate thing, i lost my save for gunstar heroes because of that had the game almost beat too. but drmd is simply awesome and keep up the great work man! if i had any money i would donate some to ya!

 

[Tetedeiench]

Heya guys,

I'm having trouble with DrMD. I am launching a rom ( for instance, Sonic3), playing a tad, then making a savestate ( L+R to go back in menu, i select "save state", choose slot0, menu says slot is used, perfect, fine).

I can then load it just fine, it works flawlessly.

However, sometimes, when i load back DrMD, it says that no savestate is used... i know somebody which had the same bug, all savestates disappearing.

I have trouble reproducing it though ( sorry reeesy, can't give you more info).

Anyone else has the very same problems ?

​

First off, why are you using Savestates with Sonic 3? I'm pretty sure that ROM can save onto itself, no save state required. (If it's not a dirty rom that is)

​

Because i'd rather loose a sonic3 savestate than a Story of thor that's the reason why

I'm happy this is fixed

 

[white]

Because you would have the same problem. I never use sync(), so even after saving a sram file, if you switch the gp2x before linux decides to actually write the file to disk you will be buggered.

I've just tested sync and it looks like it fixes the problem. I'll release another version a bit later then you lot can do your worst to it

​

I think we ought to put a reminder to call sync() after fclose() somewhere in the development help docs...

 

[Tetedeiench]

Reesy, the new DrMD version is solving the problem... working great great great !

Love you

 

[lubidog]

I can not get over how great Dr MD is now!!!!

Brian.....

Lara's......



T..h..a..n..k..y..o..u......




Now write me a snes emu, you naughty, beautiful boy!!!!

 

[FluffyPanda]

I wonder why GPH didn't mount the SD with the "-o sync" option. That would have avoided all these problems.

Anyway, great job Reesy

 

[white]

I wonder why GPH didn't mount the SD with the "-o sync" option. That would have avoided all these problems.

Anyway, great job Reesy

​

Probably too slow for random access to the drive; and they don't have an infinite amount of read/write cycles as far as I can recall. But what they definitely should have done is put a call to sync() at the start of the launcher, so when it gets reinvoked at the end of an application it syncs automatically.

Hmmm (thinks)... one could theoretically replace the launcher with a script which does sync() and then calls the old, real launcher. But if you did it wrong you'd brick the gp2x