It's not a significant issue, as long as the file name is different it works perfectly as intended. Just seemed weird for that to have happened.

I'm in the practice of actually using 'current' as the name of my current working project when I back it up, then rename it to a name and datestamps when I store them permanently. I do this because of a mistake I made that cost me a few days worth of work a few months back.

I was super eager to copy over from my EMS cart onto the new cart I just got from ASM. When I did, Win7 asked me if I wanted to copy/replace the "current.sav" on the cart. Naturally, I said yes.  This is, apparently, A BAD THING to do.

My windows filesystem thought it had copied the file over. The cart, on the other hand, did not. When I ejected and turned on my DMG, it still had the demo songs on it. I spent the last hour and 20 minutes performing the same operation over and over, checking and re-checking my .sav file integrity with emulators and various ROM's, loading up the LSDSNG manager and was about to email saying I thought I had a broken cart.

Then I just tried copying over an older .sav with a different name than 'current.sav', and of course, it worked fine.

Let this be a warning to anyone who also uses the same naming schema or renames their files to 'current.sav' thinking they have to write over the cart in a traditional drag & drop sense.

My question, I suppose, is this...  what was happening when I was copying it initially, and what did Windows think it was replacing?

bitjacker wrote:

My new derp cart is named Heaps? why?

because, in order to do a hell actual chiptune, you need a heaps cart.

My new derp cart is named Heaps? why?

because, in order to do a hell actual chiptune, you need a heaps cart.

I feel like Tm Cruise in mission impossible right now, after getting the cart found by my pc I'm so afraid to do anything wrong and break it, I'm shaking and sweating .

Thansk for bearing with me