Trim v0.22
Heres a new version of the trim.exe which outputs the file as blah.trim.nds. No other changes made, windows and linux versions included. If you find an image that this prog over trims please comment below.
Heres a new version of the trim.exe which outputs the file as blah.trim.nds. No other changes made, windows and linux versions included. If you find an image that this prog over trims please comment below.
Bad Behavior has blocked 50 access attempts in the last 7 days.
February 28th, 2007 at 6:53 am
Thank you i will test it on linux
March 1st, 2007 at 6:07 pm
thanks dude I’ll gonna give it a try because the rom trimmer which is included in the R4 don’t work
March 6th, 2007 at 3:45 pm
This fails for me, if i specify or drag on a file in the windows version, it screws up the output file
adds three or for jibberish chars, you must not be limiting the string, or getting the correct substring or something, and getting a minor overflow?
would you ever release the source for this?
March 7th, 2007 at 1:26 am
Rejk: damm I was hoping no one would report that bug. I’ve released a fixed version. I will release the source one day; just have a few more features to add first.
March 18th, 2007 at 11:25 pm
Tested your app (v0.22) on the first rom I picked outa my bunch, and it seemed to leave blank junk at the end of the file. About 2019 bytes could have been left off. I experimented with rom #0035 - Touch! Kirby’s Magic Paintbrush (J)(GBXR).nds. I used the supplied R4 DS Rom Trimmer and it gets it almost exactly, only 28 bytes of 0’s at the end of the file, I’m assuming they’re left for padding. Your program read the size as 0×32b8143.
I suggest getting a hex editor like UltraEdit or something and peeking at the output and getting a closer look at what’s really going on here when it’s trimmed. If I manually trim a rom using a hex editor by removing the 0’s or F’s from the end of the file and stopping when I get to data, I could almost reproduce the output of what the R4 trimmer does. I’m only off about 4-10 bytes due to either offset boundaries or padding. Probably needs a size of multiples of 16 or something.
With this particular ROM #35, offset 0×80-0×83 = 60 79 2B 03. Convert to HEX it’s 0×32B7960. Convert to DEC it’s 53180768, which is the exact filesize R4’s ROM Trimmer created when it was trimmed from 64MB. Somehow your program added 2019 to the value extracted from 0×80-0×83.
May 1st, 2007 at 5:27 am
Sorry for the delay in response - thanks for your comments. For various reasons trim leaves a small amount blank space at the end of the file. I may in future make this a command line option but for now since I have not much time to spend, I go with a cautionary approach to trimming.
October 17th, 2007 at 12:31 pm
i dont no how to work it i try running the trim.exe and it just goes into a command promt then closses! im on a computer on windows. but soz im a rookie!
December 20th, 2007 at 4:48 am
drag the file onto trim.exe