Hacking Bad Timestamps on Save files created by DSTwo

[Nimbus]

So apparently, and I have no clue how long this has been going on, but it's kind of annoying. I have noticed it as of EOS Version 1.07 or so.

Every single .sav file that the DSTwo seems to make has a bad timestamp, as well as a capitalized extension, but it's very conditional.

For example

If I create a blank text file and rename it to GameNameHere.sav to match the game that currently does not have an associated .sav file, it's timestamp is just fine, because it's already created, and since the file is invalid for any game to be a save file, it assumes that it has no save data associated with it and utilizes it for said save data.

However if I don't create said file, it makes a file GameNameHere.SAV with a capitalized extension. It also creates them with a bad timestamp.

In my case the files typically show up like this

Linux
Date Created: 1/1/1987
Date Modified: Whatever the current date is
Actual Time Created (Provided I have it show it's exact time of creation): 0:00
Actual Time Modified: Whatever the actual time was supposed to be when it was created

Windows
Shows nothing at all, seems to detect that the Timestamp could not possibly be right. Linux must be detecting it as being improper, but still displays it as I have instructed/configured it to do with all files by default.

OSX
I rarely use my Macbook since my new Laptop literally drops a train on it, but OSX seems to think that the .SAV files are damaged and refuses to let me do anything with them. It displays only the modified date, and the creation date is blank.

Now using some tools on either OS I can correct the timestamps manually (touch via command line on Linux, or a plugin for Explorer on Windows), but that seems like a chore and I'd rather the DSTwo and EOS just do this properly from the start.

Additionally this has a bad effect on some save files, where if I rename them to .sav as they are supposed to be, the game is never able to detect them as existing, or in some cases detects them as being damaged or corrupted, and deletes them.

This issue did not occur with my Supercard DSOnei, and still does not occur with the DSOne. All of my flashcarts sans the DSTwo create save files properly with good/valid timestamps and non capitalized .sav extensions.

This cant possibly be normal behavior, and I assume that others are having this same issue that I am.

The DSTwo firmware I am using, as well as the EOS version are both the latest version.

 

[alidsl]

Strange, I get the capitals but the timestamp on my XP computer is right

 

[Nimbus]

Strange, I get the capitals but the timestamp on my XP computer is right

So yours show up on the day the .SAV file was actually created, rather than 1/1/1987!?

How odd. The DSTwo itself, or rather the EOS is still likely the culprit seeing as in my case, I get bad dates on the timestamp, and henceforth bad timestamps.

It shouldn't be doing this either way, the save files should be being created with a .sav extension, and should have valid timestamps. It's not my MicroSD either, as I have formatted it time and time again, and this issue persists only when the .sav file does not already exist.

 

[alidsl]

Strange, I get the capitals but the timestamp on my XP computer is right

So yours show up on the day the .SAV file was actually created, rather than 1/1/1987!?

How odd. The DSTwo itself, or rather the EOS is still likely the culprit seeing as in my case, I get bad dates on the timestamp, and henceforth bad timestamps.

It shouldn't be doing this either way, the save files should be being created with a .sav extension, and should have valid timestamps. It's not my MicroSD either, as I have formatted it time and time again, and this issue persists only when the .sav file does not already exist.

Just checked again it seems all my saves were created: 26 September 2011, 19:43:28

 

[Nimbus]

The fact of the matter is, you're still getting valid timestamps, while I am not.

What EOS version are you running, and which firmware. I'm running whatever the latest one is EOS 1.11 and I forgot the latest firmware version, all I know is it's the one that allows it to run on the latest 3DS Menu.

 

[alidsl]

The fact of the matter is, you're still getting valid timestamps, while I am not.

What EOS version are you running, and which firmware. I'm running whatever the latest one is EOS 1.11 and I forgot the latest firmware version, all I know is it's the one that allows it to run on the latest 3DS Menu.

But ALL of my saves are 26 September 2011, 19:43:28

 

[chemistryfreak]

I have the same issue with mine too. All my newly created Save files show up on my Windows7 without any time stamp on it and they are all in the format of "GameName.SAV"
I find it kind of irritating since I can't determine when was the last time I played the game/save it...anyone know how to solve this? All the time stamp was ok when I was using AK2i...weird...

Btw I am also running the latest firmware version with the latest EOS