Hacking How to DLDI patch - Linux

[Azimuth]

Heres another small guide to help all those who use Linux and who dont have the time to read through the various readme files included with the patcher.

Grab the patching software and the patch for your flashcart from here

Extract the patching software and the patch and place them in one folder

Now place the .nds file you want to patch in the same folder.

Open up the terminal

go to the folder we just created: cd ~/folder containing files
Execute program: ./dlditool ./Your Cart.dldi ./Your NDS File.nds

This should be the final result( i patched scummvm-b with g6fl.dldi)

Note: There is a t parameter that can be added to patch specific extensions such as .ds.gba, this is useless
since the patcher auto-detects the extension and the patches the file accordingly

it takes 2 secs to patch a file on average

Hope this helped you, id like to here your feedback

 

[axx]

the patching seems to work fine, but even though I'm using sclt.dldi as a patch, my .nds file still won't launch.. frustrating

very neat guide though!

 

[nicko_510]

Hello.
I don't understand, but it doesn't work with me

Ubuntu feisty, M3ds simply

 

[KDH]

Hello.
I don't understand, but it doesn't work with me 

Ubuntu feisty, M3ds simply


NOTE: Every command below should be run as a normal user, not as root or using sudo.

It looks like you haven't actually extracted the archive. Open the file in your archive manager (Ark/File Roller/etc.) and extract it to ~/bin. Now open a terminal, cd to ~/bin and run:

chmod +x dlditool

Then you should be able to run it as you would any other command line program (assuming that ~/bin is in your PATH)

dlditool r4tf.dldi foo.nds

If you need to add ~/bin to your PATH then make sure the following is in either ~/.bashrc or ~/.bash_profile:

# set PATH so it includes user's private bin if it exists
if [ -d ~/bin ]; then
   PATH=~/bin:"${PATH}"
fi

That will make sure that as long as ~/bin exists it will be added to your PATH every time you login. To get it to work immediately, without having to logout run:

CODEexport PATH=~/bin:"$PATH"

See if that works for you.

 

[Azimuth]

@KDH

an easier method:

extract dldi tool to desktop,
chmod +x /home/user/Desktop/dldi
su
cp /home/user/Desktop/dldi /usr/bin/
now just type dldi to execute dldi in bash

this is a bit risky because you login as root. I see no need to do this unless you use the patcher a lot.

 

[foobar]

I seem to remember a Really Good Reason? for being careful of the permissions set on files in /usr/bin

You definitely want to make root the owner and group for these files, and set permissions so that only root can write to them. Otherwise another user could just overwrite that file with, say, a script containing "rm -rf ~/".

chmod 755 filename
sudo chown root filename
sudo chgrp root filename

 

[KDH]

@Azimuth

True, it is easier, assuming that a person using the method I posted happens to be using a distro that doesn't already have

# set PATH so it includes user's private bin if it exists
if [ -d ~/bin ]; then
 ÂPATH=~/bin:"${PATH}"
fi

in ~/.bashrc or ~/.bash_profile by default, or they haven't already added it themselves for another reason.

Both methods have the same end result, as you said, so its just personal preference. I prefer to keep programs that only I will use in my own ~/bin.

 

[James Kudo]

@KDH

an easier method:

extract dldi tool to desktop,
chmod +x /home/user/Desktop/dldi
su
cp /home/user/Desktop/dldi /usr/bin/
now just type dldi to execute dldi in bash

this is a bit risky because you login as root. I see no need to do this unless you use the patcher a lot.

Thanks! This worked great for me.

 

[flashermac]

Thanks a lot mate,

I'm a bit of a newb to linux, but this helped a lot.

Cheers
|fmc|

 

[ZeWarrior]

What Linux Distro are using in this example/How-To?