Search

[gamekill]

I read a lot of people stating the new (2.43) converter "saves up space" by trimming the nds roms. But what if I do NOT want the roms trimmed? I want to be albe to see everything the game has to offer including the videos!!!

:cry:  :oops:  :shock:    :cry:

[ratx]

trimming just removes "blank" sections of the rom. Its NOT the same as "ripping" ( removing actual content ).

[scoobos]

From what I understand of trimming , it just removes "padding" data from the end of the rom. The roms are all padded with placeholder values.

I think you are getting confused with the difference between ripping and trimming.

Trimming removes padding - you lose no content. Ripping, removes content.

[scoobos]

although we both simulataneously posted, honor must go to ratx for saying it in less words  

[Jango Fett]

I myself am glad of the feature and as long as it

   saves space
   doesn't "rip" any contents
   is fully compatible i.e doesnt make any previously working roms not working. Then I'm all for it

Just like to say big thanks to sc team for such versatile product and for all their hard work b.t.w

[jweaver]

I have just found that Mario 64 no longer works after re-converting ever ROM with 2.431

I have looked around the forum and it seems that this is a problem with the converter, and simply using a ROM converted with 2.42 works.

However, I am wondering if this isn't a probelm with the 2.431 patcher, but a problem with the 'trimming'.. Perhaps Mario 64 has data in the 'trimmed' area, or needs to be full size to run.

When I get home later, I plan to re-test by converting the ROM again with 2.42, but also with trimming turned off!

If my theory is right, trimming may not always be a good thing!

Jon

[CabaretVoltaire]

Unless there's something very wrong with the patcher then I very much doubt that it's trimming actual data.  

It will look for a big block of constant 0x00 or 0xff at the end of the rom and remove them.  

If you have something like:

38795788975498543000000000000

Then it will trim it to

38795788975498543

But if you put a 1 or something in those zeros somewhere like:

38795788975498543000000001000

Then it will only trim off the 3 zeros at the end.  There is no preset area to trim and there is no "full" size of nds roms.  I think you are barking up the wrong tree.

If you want to look into this more though then you could compare the rom sizes between mario64 patched with 2.42 (and then trimmed with GBATA) and patched with 2.43.  

If the file patched with 2.42 and then trimmed with GBATA doesn't work then maybe Mario 64 doesn't like being trimmed.  (this is very unlikely)

If the file patched with 2.431 is significantly smaller than the file patched with 2.42 and then trimmed wth GBATA then it would mean that 2.431 might be trimming too much of the rom.


I think the problem is more likely to be caused by Vin Diesel though.

[Koji]

The reason that there are usually space at the end of all games is because it's cheaper to create several carts of specific sizes and burning all games to them then creating carts the exact size for every game (a LOT cheaper) so there are 64, 128, 256, 512, and 1024mbit DS roms.

Now since it's pretty hard to get exactly the size of the cart when you are programming the game that's why there is usually a fairly sizable chunk of free space at the end.