Rename tune files after backup?

[Speedy!]

This seems like a basic question, but searching didn't find anything.

I've used DSDL to backup my original tune file as well as my custom tune file to my laptop. However the file names are just a sequence of numbers for the original, and a sequence of number with "_custom" added on for the custom tune.

Can I rename those files to something more intuitive like ChallengerOriginaTune and ChallengerCustomTune or do they need to have keep that numerical file name in order to be loaded back to the predator and subsequently the car in the event that's necessary?

[brandy16]

No if you do the tune will not load again. The diablo will be comparing the file size. If you rename it the file size will be different and will not install. I tried it once and found out the hard way.

[Weedahoe]

renaming the file has nothing to do with the contents of the file and thus its size.

[brandy16]

Then go ahead and do it. The file already has a name which is part of the file size. I know I have tried several times it screws up the file.

[jimb]

the "sequence number" that DSDL prefixes as a filename is actually the CALID. Renaming it to something else should not effect the size of the file. However, DSDL only show files with *.grg, *.frg, *.drg extensions when scanning for the original back for the purpose of installing a custom tune.

[Weedahoe]

Thank you Jimb for backing me up. Glad to see someone else here knows a bit about computers and file sizes

Im not trying to get into a pissing match here but I know what Im talking about. For Brandy16, here is a screen shot I did for you with my original backup with the file name changed 3 times. Each file is still 61kb.

http://dooxkg.bay.livefilestore.com/y1p ... JPG?psid=1

[FAhemiST]

[duster360]

Personally, I don't suggest anyone rename their "Original backup". Any other file thats been changed, imo, it doesn't really matter. I like to keep the Original backup file unmolested so it matches the Tool's name exactly.

For U7134 users at least , there's real issues with CMR custom tune changes appling properly to the original backup when the tune is downloaded to teh tool and/or flashed. I have yet to hear the exact cause but sometimes after DSDL downloads the custom tune to the tool, NONE of the CMR changes are there. So basically the custom tune is just a stock tune.

Rumor and Speculation is that this pita issue might have something to do with a renamed Original Backup but no one really knows.

The fix is in the way the CMR saves the tune file and the 'fix' does work everytime. But the real head ache is that it doesn't happen consistantly. On my own car for example, most of the time, I don't have to save my custom made tune files in any special way(I have a renamed orginal backup) On rare occassion I've had a tune that didn't have any of my changes appied. I was fiddeling with any other guy's car and the tune will be fubared if I don't save it in a specific way in CMR.

Maybe its a DSDL issue, may its a CMR issue, maybe its a pc or tool crom issue, beats me. When ever I save a custom tune for anyone I just have to make three files instead of one to make 100% sure the tune's changes will apply properly.

I also had a similiar incident as brandy. Before i had a CMR, I had made changes with the tool and wanted to save a copy as a 'backup' to se later. So I extracted the tune and renamed it. Well when I added the tune back to the tool a short time later, the result was nothing more than the stock tune.

[Houdini]

Im not trying to get into a pissing match here but I know what Im talking about. For Brandy16, here is a screen shot I did for you with my original backup with the file name changed 3 times. Each file is still 61kb.

True, a file name change won't change a files check-sum or hash (if that's what the predator is looking for)

But you are incorrect in saying those files are 61kb. That number is rounded to the nearest k, or 1024 bytes (those files could be 61,500 bytes, 61,999 bytes, or even 62,024 bytes, and still show 61kb where you are looking.

I'm not trying to get into a pissing match either, but your way of determining the file size is like looking at the gas gauge and saying you have 1/2 a tank (but you could siphon out a dozen ounces and your gauge would still show 1/2 a tank, when actually you have 12 ounces less).

.