gbadev.org forum archive

This is a read-only mirror of the content originally found on forum.gbadev.org (now offline), salvaged from Wayback machine copies. A new forum can be found here.

DS homebrew announcements > [v0.93]My patcher, DLDIrc: neither commandline nor GUI based

#116781 - psychowood - Mon Jan 29, 2007 2:05 pm

Hi all,
I've spent some hours developing a little and useful (at least for me, and I hope for someone else too :) ) tool to apply a DLDI patch on homebrew roms. It is for Windows (XP/2k/NT), is different from the patchers already available because uses Chishm's dlditool to patch via right clicking the rom. No GUI, no command prompt. Two clicks, that's all. :)

If you use more than one flashcard, you can install more than one DLDI driver, and you'll have every single choice available in the context menu.

It can be downloaded from here (it is a direct download link, I'm just using that link to count the clicks :) ), if someone wants to try it and give me an opinion... well, I'm here. :)


Last edited by psychowood on Wed Oct 17, 2007 2:28 pm; edited 23 times in total

#116806 - dantheman - Mon Jan 29, 2007 10:12 pm

It doesn't work for me, using Windows XP. The Start Menu shortucts are created, and the DLDI files are extracted and all, but nothing has changed in my right-click menu when clicking on a .nds file. Rebooting after installation provided no changes.

According to the log file that is created when it is installed or uninstalled, it appears that all it does is extract the files to the location I specify and create shortcuts. Shouldn't it be writing to the registry or something, to modify the right-click menu of .ds.gba and .nds files? Or do registry edits not appear in this log?

Other people have reportedly gotten it to work, so I'm hoping it's merely an error on my end.

#116810 - psychowood - Mon Jan 29, 2007 10:38 pm

dantheman wrote:
It doesn't work for me, using Windows XP.


Hi dantheman, thanks for taking some time trying DLDIrc. :)

Can you tell me your exact version of XP, and what language are you using?

Quote:
The Start Menu shortucts are created, and the DLDI files are extracted and all, but nothing has changed in my right-click menu when clicking on a .nds file. Rebooting after installation provided no changes.


It should work out-of-the-box, no reboot required.

Quote:
According to the log file that is created when it is installed or uninstalled, it appears that all it does is extract the files to the location I specify and create shortcuts. Shouldn't it be writing to the registry or something, to modify the right-click menu of .ds.gba and .nds files? Or do registry edits not appear in this log?


Exactly, the setup simply copies files in the destination directory and creates (tries to..) some shorcuts and registry keys. Specifically:
-HKLM\Software\DLDIrc to store the install path
-HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\DLDIrc to add the uninstall option in the Add/Remove Software Control Panel page
-HKCR\.nds\shell\DLDI.....\Command (one key for every selected DLDI driver), which is the heart of the tool and is the context menu item

The only thing that comes up in my mind is the fact that I forgot about testing it in a non-administrator environment, and it is possible that writing a registry key in HKLM and in HKCR requires a high privileged user: did you install it using a standard user or a poweruser/administrator?

Quote:
Other people have reportedly gotten it to work, so I'm hoping it's merely an error on my end.


Yep, the download link counted about 2 hundred downloads, and your is the first non-working case. Lets solve it, then :)

#116812 - dantheman - Mon Jan 29, 2007 11:09 pm

I'm using Windows XP Home edition, English language. I'm running an administrator account, the only one on my system.

Looking at HKEY_LOCAL_MACHINE\Software\DLDIrc, I see a single key called Install_Dir with a value of C:\Program Files\DLDIrc. Nothing out of the ordinary there. The uninstall location seems to be fine as well. Even the HKEY_CLASSES_ROOT one looks correct. I tried making my own string value, with a name of "test" and the contents that you put in yours, but it doesn't show up either in my right-click menu. How odd.

#116825 - psychowood - Tue Jan 30, 2007 1:22 am

dantheman wrote:
I'm using Windows XP Home edition, English language. I'm running an administrator account, the only one on my system.


Haven't had a chance to try it on XP Home yet, but the differences with the Pro Edition should not be related with this problem.

Quote:
Looking at HKEY_LOCAL_MACHINE\Software\DLDIrc, I see a single key called Install_Dir with a value of C:\Program Files\DLDIrc. Nothing out of the ordinary there. The uninstall location seems to be fine as well. Even the HKEY_CLASSES_ROOT one looks correct. I tried making my own string value, with a name of "test" and the contents that you put in yours, but it doesn't show up either in my right-click menu. How odd.


What DLDI driver did you tried? I've already tested them all (even installing all together) and the only issue I noticed is that if you install both the M3 SD drivers, only one of them shows up in the context menu (but it isn't really a issue, I'd say).

Can you try making a whole new key, something like

HKEY_CLASSES_ROOT\.nds\shell\MYKEY\command\

with nothing in it, and seeing if it shows up when you right-click a .nds file?
And, could you export and send me the subkeys of the .nds class, too (in regedit, right click on ".nds" in HKCR, and then select "export", it will save a .reg text file)? You can find my email address at the end of the readme.txt file.

Thanks.

#116827 - dantheman - Tue Jan 30, 2007 1:54 am

I first tried the Supercard SD driver, but then when that didn't work, I tried installing several others. They all showed up in regedit, but none of them actually did anything.

Creating my own key also does nothing. I've sent you an e-mail with the .reg file.

#116829 - chishm - Tue Jan 30, 2007 2:12 am

psychowood:
I did get your email, but I am a little slow in answering I suppose. I was looking at ways that you could get the latest dlditool when installing, which isn't easy using SourceForge. Perhaps just grab the one included with DKA r20. I'm still not sure what to do about the DLDI files yet.
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com

#116835 - psychowood - Tue Jan 30, 2007 3:03 am

dantheman wrote:
I first tried the Supercard SD driver, but then when that didn't work, I tried installing several others. They all showed up in regedit, but none of them actually did anything.

Creating my own key also does nothing. I've sent you an e-mail with the .reg file.


Sorry, I'm almost sure that the problem lies in your PC :(
I added the key without a problem and it shows up correctly.. I really don't know what could be the problem, because if even the one you created isn't visible.... :|
Do you have some kind of strange system extension installed?

chishm:
Well, after only two or three days you aren't on the slow side yet :) I asked just because I did not got the return receipt (not that I expected it, after all you didn't know my address) and recently I've been "antispammed" more than once. :)
Actually I've put in the package the one you have in your site, v1.21, together with every working driver available, for now I'll manually update when needed, if I come up with a decent idea (I was thinking about a DLDI repositloty with pre-patched roms..) I'll let you know.

#116842 - dantheman - Tue Jan 30, 2007 4:38 am

Yeah, it's probably my computer. I've had some issues with .nds files before, refusing to open with the program I told them to, but oh well. Thanks for trying nonetheless.

#116845 - RVK - Tue Jan 30, 2007 4:46 am

Mine was not working either but I found that I had associated .nds files with my SC patch program. As soon as I removed the association, your tool works fine.

#116847 - dantheman - Tue Jan 30, 2007 4:54 am

There we go, that fixed it. By default, I have .nds files open with No$GBA since it has good homebrew compatibility. I went into Regedit and removed the "nds_auto_file" value data from the .nds key, which made it open in your script by default. Now that I added "nds_auto_file" back in, it runs by default in No$GBA again, but I now have an option in the "Open With..." menu for "Windows Command Processor" which patches with your script.

I haven't tested it much, but it appears to work. The best part is that you can easily update the DLDI patches or the dlditool since they're standalone files in the installation directory.

Thank you RVK for that tip.

#116888 - Goosey - Tue Jan 30, 2007 6:45 pm

dantheman wrote:
There we go, that fixed it. By default, I have .nds files open with No$GBA since it has good homebrew compatibility. I went into Regedit and removed the "nds_auto_file" value data from the .nds key, which made it open in your script by default. Now that I added "nds_auto_file" back in, it runs by default in No$GBA again, but I now have an option in the "Open With..." menu for "Windows Command Processor" which patches with your script.

I haven't tested it much, but it appears to work. The best part is that you can easily update the DLDI patches or the dlditool since they're standalone files in the installation directory.

Thank you RVK for that tip.


I was having the same issue, and your fix worked for me.

Somehow if DLDIrc could coexist with prexisting auto-open setups that would be a good fix for a future version. :)

#116896 - tyraen - Tue Jan 30, 2007 7:23 pm

You could probably make it create a context menu of its own, like WinRAR or 7-zip. :)

#116901 - psychowood - Tue Jan 30, 2007 9:43 pm

I'll give a look to see what I can do, the strange thing I really don't understand is that it should work this way, because it is the normal way Windows uses file associations...

tyraen wrote:
You could probably make it create a context menu of its own, like WinRAR or 7-zip. :)


You have a point here, but I'd like to avoid using .dll and .exe...

I'll look more deeply into this problem, and let you know :)

#116916 - psychowood - Tue Jan 30, 2007 11:21 pm

Hi again,
version 0.2 is up.
I rewrote the association code (now it uses batch files, if the problem regarded the lenght of the registry key now should be solved, if you want to giva a try..).
I also added the official AceKard+ DLDI driver and the ability to associate .nds files with a nice looking icon. :)

#116942 - HyperHacker - Wed Jan 31, 2007 4:55 am

FYI, Windows looks at HKEY_CLASSES_ROOT like so:

-Check for the file extension (.nds). Read its default value.
-Check for a key with this name. If it exists, use that key. Otherwise, continue using this key.
-The default value is the file type description.

So for example if you have .nds in your HKCR, and its default value is "ndsfile", then Windows will look for HKEY_CLASSES_ROOT\ndsfile. If that exists, then it's used for all .nds file information, and its default value specifies the file type description. Otherwise, the .nds key is used and the description is "ndsfile".
_________________
I'm a PSP hacker now, but I still <3 DS.

#116961 - psychowood - Wed Jan 31, 2007 11:34 am

Thanks HyperHacker, those are very very useful infos! They're probably going to solve the whole problem :)

I did not find that info in the document I used for reference, and it was an official MS doc. :|

#116966 - psychowood - Wed Jan 31, 2007 12:21 pm

Uploaded v0.3, now it should really register correctly, I've also tried overwriting .zip associations and it worked fine :)

Goosey, dantheman, RVK, would you mind trying it? Thanks.

#117005 - Darkflame - Wed Jan 31, 2007 7:05 pm

This works great :)
I can see this becoming the essiential tool for just about all ds homebrewers.
_________________
Darkflames Reviews --
Make your own at;
Rateoholic:Reviews for anything, by anyone.

#117053 - dantheman - Wed Jan 31, 2007 11:35 pm

It now works correctly. Thank you for the hard work. I made a copy of the key in my gba_auto_file one as well, since with the Supercard it's best to use .ds.gba files, even with the DLDI system.

#117406 - wintermute - Sun Feb 04, 2007 6:35 pm

dantheman wrote:
It now works correctly. Thank you for the hard work. I made a copy of the key in my gba_auto_file one as well, since with the Supercard it's best to use .ds.gba files, even with the DLDI system.


No it isn't, .nds files have worked just fine on SuperCard for quite some time.
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog

#117433 - dantheman - Sun Feb 04, 2007 9:23 pm

I realize that in many cases with newer homebrew, the .nds will work correctly as it is. I usually use the .nds unless I notice that there is a size difference between the .ds.gba file and the .nds one, in which case the .ds.gba usually works better. For instance, with the Word Wrap homebrew, patching the .nds creates a file that does not boot correctly on my Supercard, while patching the .ds.gba works fine. On the other hand, IRC DS works correctly with the default .nds file provided.

#117456 - chishm - Sun Feb 04, 2007 10:56 pm

wintermute wrote:
dantheman wrote:
It now works correctly. Thank you for the hard work. I made a copy of the key in my gba_auto_file one as well, since with the Supercard it's best to use .ds.gba files, even with the DLDI system.


No it isn't, .nds files have worked just fine on SuperCard for quite some time.

I wish I could say the same about SuperCard Lite :-(
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com

#117476 - wintermute - Mon Feb 05, 2007 1:39 am

chishm wrote:
wintermute wrote:
dantheman wrote:
It now works correctly. Thank you for the hard work. I made a copy of the key in my gba_auto_file one as well, since with the Supercard it's best to use .ds.gba files, even with the DLDI system.


No it isn't, .nds files have worked just fine on SuperCard for quite some time.

I wish I could say the same about SuperCard Lite :-(


What happens with SC Lite? I don't really understand why .ds.gba should be any different from .nds these days.
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog

#117503 - chishm - Mon Feb 05, 2007 5:20 am

Normal NDS files (even ones with the loader in the header) don't boot. They are loaded then the DS whitescreens. *.ds.gba files work, but I find them to be a PITA. Also, firmware v1.70 broke some homebrew, and you can't downgrade. It's okay though, I'm hacking the firmware enough to fix these problems. The thread is here.
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com

#117506 - dantheman - Mon Feb 05, 2007 5:32 am

chishm, have you tried loading the .nds files through Moonshell? Sometimes that helps. Real life example: the WinDS distro only comes in .nds format, and the Supercard Magic Homebrew Patcher doesn't recognize it as a valid DS binary. Loading the .nds file from the Supercard menu doesn't work, though loading from Moonshell does. I haven't tried manually appending the loader though, so perhaps I should try that...

#117507 - chishm - Mon Feb 05, 2007 5:34 am

Rather than use work-arounds, I'll just fix the problem at it's source.
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com

#118161 - psychowood - Sat Feb 10, 2007 4:13 pm

New version (0.32) is up, updated DLDI drivers and dlditool to v1.23.

[EDIT]There was a problem uploading the file, it is ok now.[/EDIT]
[EDIT]Added DS-X DLDI official driver[/EDIT]

#127218 - psychowood - Mon Apr 30, 2007 11:35 pm

Version 0.33: updated drivers (added also G6 v0.19) and corrected drivers name (that prevented installing more drivers if they had the very exact name).

#127906 - psychowood - Sun May 06, 2007 1:31 pm

*v0.4
EzV users, be happy, this is for you! :)
-Replaced EzV driver with v2, some bugs corrected (version v2
isn't available from chishm site yet, this one was released by
cory1492 himself, see here
http://ezflash.sosuke.com/viewtopic.php?p=30461#30461 )
-Integrated DLDIFixV to patch the gamecode with PASS, when EzV
is selected (no manual patching needed anymore)
Thanks Cory for the permission :)

#127909 - psychowood - Sun May 06, 2007 2:38 pm

Fastest update ever ^^

*v0.41
-Replaced DLDIFixV with HEADFixV (avoids double DLDI
patching doing only PASS patch)
-Corrected a little language messup introduced with v0.4 :)

#128444 - psychowood - Fri May 11, 2007 3:09 pm

*v0.5
-Now DLDIrc can be associated to .bin and .gba files (to be
used with .ds.gba roms, since Windows doesn't accept double
extensions the association must me done with .gba)
-Updated installer: now it checks online the latest version,
and requires uninstallation of previous installations.
-Minor text changes

#128454 - Devil_Spawn - Fri May 11, 2007 5:17 pm

psychowood wrote:
*v0.5
-Now DLDIrc can be associated to .bin and .gba files (to be
used with .ds.gba roms, since Windows doesn't accept double
extensions the association must me done with .gba)
-Updated installer: now it checks online the latest version,
and requires uninstallation of previous installations.
-Minor text changes


you dont think you could auto-rename .ds.gba to .nds could you? that would be awesome

#128457 - psychowood - Fri May 11, 2007 5:37 pm

Devil_Spawn wrote:
you dont think you could auto-rename .ds.gba to .nds could you? that would be awesome


After patching, you mean? It would be rather easy to do but.. are you sure that it would be useful?
I'm not used to .ds.gba, what would the meaning of the renaming be? Aren't .ds.gba files with this extension because they must end with .ds.gba?

#128460 - tepples - Fri May 11, 2007 5:44 pm

psychowood wrote:
Devil_Spawn wrote:
you dont think you could auto-rename .ds.gba to .nds could you? that would be awesome

After patching, you mean? It would be rather easy to do but.. are you sure that it would be useful?
I'm not used to .ds.gba, what would the meaning of the renaming be?

SuperCard in SLOT-2 expects DS programs to be in PassMe format (ds.gba) but expects their names to end in .nds. Some people use the convention "sc.nds" to denote a DS program that has been put in PassMe format and renamed to .nds for use with the SuperCard.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.

#128470 - psychowood - Fri May 11, 2007 8:10 pm

tepples wrote:
SuperCard in SLOT-2 expects DS programs to be in PassMe format (ds.gba) but expects their names to end in .nds.


Understood.
v0.51 available for download ;)

*v0.51
-Added the option to rename .gba in .nds after DLDI patching

#128473 - Devil_Spawn - Fri May 11, 2007 8:49 pm

psychowood wrote:
tepples wrote:
SuperCard in SLOT-2 expects DS programs to be in PassMe format (ds.gba) but expects their names to end in .nds.


Understood.
v0.51 available for download ;)

*v0.51
-Added the option to rename .gba in .nds after DLDI patching


wow, that was very fast, thanks!

#128474 - psychowood - Fri May 11, 2007 8:51 pm

Devil_Spawn wrote:
wow, that was very fast, thanks!


You're welcome :)

#128487 - felix123 - Fri May 11, 2007 10:48 pm

Thanks for the new version.
The $ donate link on the download page is broken.
_________________
Nintendo DS homebrew on Wikipedia

#128491 - psychowood - Fri May 11, 2007 11:00 pm

Quote:
The $ donate link on the download page is broken.


It seems to work just fine here.. what is the problem?
If you want, answer via pm, we are going here OT ;)

#128539 - psychowood - Sat May 12, 2007 3:22 pm

*v0.52
-Put the online check first in the installer, making possible
to check the version without uninstalling the current one

#129354 - dantheman - Tue May 22, 2007 2:54 am

Hey, I just remembered something I've been meaning to say for a while. Could you make sure you change the icon back to the default when uninstalling the program? I ticked the box by accident (didn't want your icon, sorry), and even after uninstalling DLDIrc and telling Windows to always open .nds files with No$GBA, your icon persisted. I had to use regedit to find the default icon key and delete it before my No$GBA icon showed up again.

Just a minor gripe, so no worries.

Oh, and could fcsr.dldi be added to the next version (stands for Flash Cart SRAM)? You can find it on the left hand side of http://gpf.dcemu.co.uk

#129388 - psychowood - Tue May 22, 2007 9:05 am

*v0.53
-Added Flash Cart SRAM driver

:)
Regarding the icon thing, I'll investigate further into it, because when you uninstall DLDIrc it actually also removes the icon file, so if it still stays, probably depends on the icon cache Windows has..

#129474 - dantheman - Wed May 23, 2007 2:41 am

Muchos gracias. Don't worry too much about the icon thing, as I am able to fix it if I forget to uncheck the box during installation. Perhaps this is just something that happens on my machine only.

#129509 - psychowood - Wed May 23, 2007 10:42 am

dantheman wrote:
Muchos gracias.


"No problemo." ;)
I didn't know what FCSR was till I found this post of yours. I was considering to integrate the whole FS image creating batch for FCSR, but I need some more accurate infos ("a couple of random files"... how many KB? It's a size problem or a file number problem?). Isn't there an official page/thread for FCSR?

Quote:
Don't worry too much about the icon thing, as I am able to fix it if I forget to uncheck the box during installation. Perhaps this is just something that happens on my machine only.


I don't think it's a problem of your machine, it's just the way Windows behaves (perhaps some reboots are needed to clear the cache, who knows). How did you fix it?

#129560 - dantheman - Wed May 23, 2007 7:34 pm

FCSR is maintained GBAdev's our own GPFerror, and the site I linked you to is the "official" download site for it.

I tried to automate the process with a batch file, but I think it got hung up on the build.bat part. Of course, just now I remembered that you have to use the CALL command to call a batch file from within another batch file, so now that I use that, it works fine. I used the following batch script, which would obviously have to be modified to work with any given filename:

call build.bat image.img fcsr
copy /Y /B ndsmall.bin + SNEmulDSv0.4-final.nds SNEmulDS.ds.gba
padbin 512 SNEmulDS.ds.gba
copy /Y /B SNEmulDS.ds.gba + image.img final.nds
dlditool.exe fcsr.dldi final.nds

I think my confusion about the "random files" was cleared up in another post, where someone said that the image needs to be 1 MB in size before it will work correctly. ...and now that I test that theory, I find that it works fine now all of a sudden. Man, dunno what the problem was before. At first I thought that it required at least one file in the "root" of the virtual filesystem, but it works fine now without one, and at the moment I've got an image here that's 700 KB and still works fine. Alright, you can ignore that whole thing about needing a few random files, as I'm really not sure what the truth is anymore.

Oh, and to "fix" the icon thing, I went into the registry and went into the HKEY_CLASSES_ROOT, and there was some icon entry under "nds_auto_file" that I deleted. I then again told windows to open all .nds files with no$GBA always, which restore the no$GBA icon to them.

EDIT: well, here's a modified batch script that might be helpful, but it requires that you put the .nds file in a subfolder called "ndsfile" (done so that only the .nds file you want to use is used):

Code:
for %%F in (ndsfile\*.nds) do call build.bat image.img fcsr && copy /Y /b ndsmall.bin + "%%F" "%%~nF.ds.gba"  && for %%F in (*.ds.gba) do padbin 512 "%%F" && copy /Y /b "%%F" + image.img final.nds && dlditool.exe fcsr.dldi final.nds

Not the best code ever, but it functions at least. Only works if only one .nds file is being used though, as it relies on a single image.img file being written. I'm trying to make it so that each *.nds file creates its own *.img and *-final.nds files, but I can't get it to work correctly at the moment.

EDIT 2: alright, got it working, but for some reason it patches each output file about 8 times, and I'm not sure why. Here's the code:
Code:
for %%F in (ndsfile\*.nds) do call build.bat "%%~nF.img" fcsr && copy /Y /b ndsmall.bin + "%%F" "%%~nF.ds.gba" && for %%F in (*.ds.gba) do padbin 512 "%%F" && for %%F in (*.img) do copy /Y /b "%%~nF.ds.gba" + "%%F" "%%~nF-final.nds" && for %%F in (*-final.nds) do dlditool.exe fcsr.dldi "%%F"

#129580 - psychowood - Wed May 23, 2007 10:04 pm

dantheman wrote:
FCSR is maintained GBAdev's our own GPFerror, and the site I linked you to is the "official" download site for it.


Ok, I was hoping to find a bit more documentation, but at least you gave me enough material to work on :)

Quote:
I think my confusion about the "random files" was cleared up in another post, where someone said that the image needs to be 1 MB in size before it will work correctly. ...and now that I test that theory, I find that it works fine now all of a sudden. Man, dunno what the problem was before. At first I thought that it required at least one file in the "root" of the virtual filesystem, but it works fine now without one, and at the moment I've got an image here that's 700 KB and still works fine. Alright, you can ignore that whole thing about needing a few random files, as I'm really not sure what the truth is anymore.


Perhaps that someone meant 1MBit -> 128KB?
If needed, I could simply generate a dummy file to pad it up to the minimum size...

Quote:
Oh, and to "fix" the icon thing, I went into the registry and went into the HKEY_CLASSES_ROOT, and there was some icon entry under "nds_auto_file" that I deleted. I then again told windows to open all .nds files with no$GBA always, which restore the no$GBA icon to them.


Ehr, actually there was a bug in that part of the uninstaller, I've just found it :|
Now the icon section of the registry is cleared correctly, BUT it seems that the Windows cache keeps the icon anyway, at least as long as you reboot (I haven't rebooted yet).

Oh, I also put the DS Icon section of the installer unchecked by default ;)

Quote:
EDIT: well, here's a modified batch script that might be helpful [...]


Thanks, but I already know that if I use some already ready code, I'll end up working on it for as long as three times the time I could've used writing it from zero :)
(I hope my bad english didn't mess up too much the previous sentence :/ )

I'll upload a beta and send you a pm with the download link, if you have some time to try it.

#129583 - dantheman - Wed May 23, 2007 10:12 pm

The build.bat file itself has some sort of padding code built-in:
Code:
if /I %size% LSS 10000  (                      set /A size="10000" )


So I think I'm completely wrong about needing a few random files.

Quote:
I'll upload a beta and send you a pm with the download link, if you have some time to try it.

Sure, that's fine.

#129591 - psychowood - Thu May 24, 2007 12:39 am

dantheman wrote:
The build.bat file itself has some sort of padding code built-in:
Code:
if /I %size% LSS 10000  (                      set /A size="10000" )


So I think I'm completely wrong about needing a few random files.


Ok, I jumped over it. :)

Quote:
Sure, that's fine.


Thanks. You've got a pm.

#129619 - psychowood - Thu May 24, 2007 11:01 am

*v0.6
-Added DSLink driver V4 Beta (works with DSLinux!) and EzSD_alt
(for slow SD cards)
-Corrected a bug which sometimes prevented the correct removal
of the icon association for .nds files
-Added online changelog: when there is an newer version available,
the installer also tells what the main changes are (you'll see from
the next update, of course)
-Added FCSR FS image creation:
Please remember that for this to work correctly, you must create
a folder with the same name (without extension) as your .nds/.ds.gba
file to act as the root of your virtual filesystem. For instance,
if you have 'game.nds' that requires 'wordlist.dat' to be on the
root of your media card, create a folder called 'game' (if you have
'game.ds.gba' the folder name must be 'game.ds') and add 'wordlist.dat'
to it. If this folder does not exist, unpredictable results may occur.
Thanks to Dark Fader, dantheman, GPF and tepples

#129682 - hedgehog - Fri May 25, 2007 12:08 am

Thanks for this really useful utility. I have a comment. I'm german and tried fcsrimage before but couldn't create an image due to an imagesize problem (just manually had to change the imagesize with corrections on:

if /I %size% LSS 10000 ( set /A size="10000" )

You are using the same build.bat. Looking into the output of dir /w /s /-c I've found a general solution. Its a simple language problem.
For german users it must be changed:
replace:
for /f "tokens=3,4*" %%a in ( 'dir /w /s /-C %2 ^| findstr "File(s)"') do @set info=%%a
with:
for /f "tokens=3,4*" %%a in ( 'dir /w /s /-C %2 ^| findstr "Datei(en)"') do @set info=%%a
That's the line checking for the filesize of the image.

#129698 - psychowood - Fri May 25, 2007 10:36 am

hedgehog wrote:
Thanks for this really useful utility. I have a comment. I'm german and tried fcsrimage before but couldn't create an image due to an imagesize problem (just manually had to change the imagesize with corrections on:

if /I %size% LSS 10000 ( set /A size="10000" )

You are using the same build.bat. Looking into the output of dir /w /s /-c I've found a general solution. Its a simple language problem.
For german users it must be changed:
replace:
for /f "tokens=3,4*" %%a in ( 'dir /w /s /-C %2 ^| findstr "File(s)"') do @set info=%%a
with:
for /f "tokens=3,4*" %%a in ( 'dir /w /s /-C %2 ^| findstr "Datei(en)"') do @set info=%%a
That's the line checking for the filesize of the image.


You're right, I didn't notice that the batch file was based on the english output :/
I edited it right now, now doesn't depend on language anymore:

for /f "tokens=3,4*" %%a in ( 'dir /w /s /-C %2 ^| tail -n 2 ^| head -n 1') do @set info=%%a

I love GNU tools ^^

So then:

*v0.61
-Corrected FCSR image creation (was not working on non-english
Windows)

:)

#129699 - hedgehog - Fri May 25, 2007 10:51 am

Feedback: its working in german environment.
That was quick.

#129700 - psychowood - Fri May 25, 2007 10:54 am

hedgehog wrote:
Feedback: its working in german environment.


Good news.

Quote:
That was quick.

A quick patch for a quick bug report :)

#130482 - psychowood - Sun Jun 03, 2007 11:49 pm

*v0.7
-Added dlditool command line support in the OS path, just call
"dldirc driver romfile" from the rom folder
-Corrected language bug with FCSR (italian installed even if
english was selected)

#131025 - psychowood - Sun Jun 10, 2007 8:11 am

*v0.71
-Added CycloDS DLDI driver

#131815 - psychowood - Wed Jun 20, 2007 1:37 pm

*v0.72
-Added dldi file for N-card, DSlinker and other clones (nrio.dldi)

#131857 - dantheman - Wed Jun 20, 2007 7:51 pm

For the N-card clones, it might be better to suggest that they use the updated firmware, as that supports auto-patching with an updated DLDI file that has full read/write support, whereas I believe the standalone DLDI file from the Wiki is read-only. I'm not very familiar with the card though, so I'm not entirely sure about the details of this.

#132011 - psychowood - Fri Jun 22, 2007 11:17 am

dantheman wrote:
For the N-card clones, it might be better to suggest that they use the updated firmware, as that supports auto-patching with an updated DLDI file that has full read/write support,


I'd prefer not to go out of scope with DLDIrc, I mean, if I should start noticing users about firmware updates and similar things, the app would bloat too much (R4 too has auto-patching now, and I'm sure that other cards will have it too). Perhaps I'm wrong, but I think that a flashcard user should at least keep its firmware updated ;)

Quote:
whereas I believe the standalone DLDI file from the Wiki is read-only. I'm not very familiar with the card though, so I'm not entirely sure about the details of this.


I've found it on GBATemp and it should support writing, indeed (with the last firmware).

#133481 - psychowood - Fri Jul 06, 2007 12:02 pm

*v0.73
-Added Datel Games'n'Music (v1 and v2, the latter has faster reading
speed) driver

#133507 - MechaBouncer - Fri Jul 06, 2007 4:36 pm

I must say that, short of autopatching, this is the fastest and easiest DLDI patcher out there. Great job and thank you for the continued support and updates. :D

Although I may have encountered a bug. It seems that no matter how much I try, I can't get DLDIrc to patch the DLDI version of nesDS. Using Chishm's Win32 GUI program I was able to patch it properly, but DLDIrc and DSOrganize's autopatching loader did not work. I don't have the old version of DLDIrc anymore to test, but I hear it does work for some people. I just found this very odd.
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3

#133541 - psychowood - Sat Jul 07, 2007 12:15 am

MechaBouncer wrote:
I must say that, short of autopatching, this is the fastest and easiest DLDI patcher out there. Great job and thank you for the continued support and updates. :D


You're welcome :)

Quote:
Although I may have encountered a bug. It seems that no matter how much I try, I can't get DLDIrc to patch the DLDI version of nesDS. Using Chishm's Win32 GUI program I was able to patch it properly, but DLDIrc and DSOrganize's autopatching loader did not work. I don't have the old version of DLDIrc anymore to test, but I hear it does work for some people. I just found this very odd.


That's odd, I've just downloaded nesDS from here and patched it succesfully with a bunch of (randomly selected) drivers... what kind of problem do you have? The only difference with old DLDIrc versions is that I was using Chishm's dlditool v1.10 instead of v1.23...
_________________
DLDIrc Developer

#133545 - MechaBouncer - Sat Jul 07, 2007 12:42 am

That's the same file I was trying to use. Well it looks like it patches fine, but no matter which Supercard SD drivers I patched it with, and no matter which launcher I used to start nesDS, I would always get an error from nesDS itself stating that the DLDI driver was missing and that I should download it from Chishm's site. The only way I was able to get it to run properly was to use bob_fossil's / Maxim's Win32 GUI patcher with Chishm's SCSD driver. It's what I used to use before I started using DLDIrc. I have not tried Chishm's command line or Win32 patchers, either. I just found it very strange that it seemed like it worked, but the patch didn't seem to take. And I made sure to repeat it several times, but no matter how many times I tried it, patching it with DLDIrc would result in the same error as though it wasn't patched at all.

Thinking about it some more, I'm not sure if it's normal, but the command prompt window goes away faster than I can see whether it succeeds or not. Out of curiosity, does the window stay open if the patch fails?
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3

#133590 - Dood77 - Sat Jul 07, 2007 9:16 am

You say that you've successfully patched with DLDItool GUI?
Some SD cards don't like the normal SD card patch for Supercard, I have one that only works with scsd_moon.dldi
Maybe this is the one you're actually using under DLDItool?
_________________
If I use a term wrong or something then feel free to correct, I?m not much of a programmer.

Original DS Phat obtained on day of release + flashme v7
Supercard: miniSD, Kingston 1GB, Kingston 2GB
Ralink chipset PCI NIC

#133594 - psychowood - Sat Jul 07, 2007 10:17 am

MechaBouncer wrote:
That's the same file I was trying to use. Well it looks like it patches fine, but no matter which Supercard SD drivers I patched it with, and no matter which launcher I used to start nesDS, I would always get an error from nesDS itself stating that the DLDI driver was missing and that I should download it from Chishm's site. The only way I was able to get it to run properly was to use bob_fossil's / Maxim's Win32 GUI patcher with Chishm's SCSD driver. It's what I used to use before I started using DLDIrc. I have not tried Chishm's command line or Win32 patchers, either. I just found it very strange that it seemed like it worked, but the patch didn't seem to take. And I made sure to repeat it several times, but no matter how many times I tried it, patching it with DLDIrc would result in the same error as though it wasn't patched at all.


I don't have a SC to try it, but on my DS Link it does work perfectly... Could you please give me some more details (where you installed DLDIrc, what is the filename you are patching and where it is, and so on...) and also post the contents of the scsd*.cmd files you have in DLDIrc install folder?


Quote:
Thinking about it some more, I'm not sure if it's normal, but the command prompt window goes away faster than I can see whether it succeeds or not. Out of curiosity, does the window stay open if the patch fails?


That's not normal, the window should stay open ("Press any key to continue...") in either way.

Code:

[DLDI Patching script by PsychoWood][v0.73]
Patching for EZ Flash 4 (SD Card)

ROM to be patched:
"C:\temp\nesDS.nds"

If it is not a homebrew ROM with DLDI
support, it will be CORRUPTED!

*Press a key to patch it,
or close the window to cancel.*

Dynamically Linked Disk Interface patch tool v1.23 by Michael Chisholm (Chishm)

Trying "C:\Program Files\DLDIrc\drivers\ezsd.dldi"
Old driver:          DSLink (microSD Card) - V4 Beta
New driver:          EZ Flash 4 (SD Card)

Position in file:    0x00006F60
Position in memory:  0x02006D60
Patch base address:  0xBF800000
Relocation offset:   0x42806D60

Patched successfully
Press any key to continue . . .


And I also get the "Patched succesfully - Press any key..." when I use SC drivers.
_________________
DLDIrc Developer

#133899 - MechaBouncer - Mon Jul 09, 2007 4:59 pm

psychowood wrote:
I don't have a SC to try it, but on my DS Link it does work perfectly... Could you please give me some more details (where you installed DLDIrc, what is the filename you are patching and where it is, and so on...) and also post the contents of the scsd*.cmd files you have in DLDIrc install folder?


Okay, here are the details:
1. The installation directory is the default "C:\Program Files\DLDIrc"
2. In the installation, I checked all installation check boxes except for "Associate with .bin files" and installed the DLDI drivers for the Max Media Dock, GBA Movie Player (CF), Supercard SD, and Supercard SD Moon (I own all three carts, but primarily use the SCSD and my GBAMP is on loan along with my only CF card).
3. The location of the nesDS.nds file is "C:\Documents and Settings\TODD.ENCO\My Documents\Games\NDS\nesDS", but I have also tried patching it directly on the root of the SD card, which is mounted as the H: drive. Both get the same results.
4. I have tried both the regular Supercard SD driver and the Moon driver, both get the same results.

psychowood wrote:
MechaBouncer wrote:
Thinking about it some more, I'm not sure if it's normal, but the command prompt window goes away faster than I can see whether it succeeds or not. Out of curiosity, does the window stay open if the patch fails?


That's not normal, the window should stay open ("Press any key to continue...") in either way.

Code:

[DLDI Patching script by PsychoWood][v0.73]
Patching for EZ Flash 4 (SD Card)

ROM to be patched:
"C:\temp\nesDS.nds"

If it is not a homebrew ROM with DLDI
support, it will be CORRUPTED!

*Press a key to patch it,
or close the window to cancel.*

Dynamically Linked Disk Interface patch tool v1.23 by Michael Chisholm (Chishm)

Trying "C:\Program Files\DLDIrc\drivers\ezsd.dldi"
Old driver:          DSLink (microSD Card) - V4 Beta
New driver:          EZ Flash 4 (SD Card)

Position in file:    0x00006F60
Position in memory:  0x02006D60
Patch base address:  0xBF800000
Relocation offset:   0x42806D60

Patched successfully
Press any key to continue . . .


And I also get the "Patched succesfully - Press any key..." when I use SC drivers.


That is strange. Okay, here is exactly what I do and what happens:
1. I right click on the nesDS.nds file located in "C:\Documents and Settings\TODD.ENCO\My Documents\Games\NDS\nesDS" and select the "DLDIrc SuperCard (SD Card) Patch".
2. The command prompt opens and closes too quickly for me to see what it says.
3. I copy the file to the root of my SD card and run the Windows dialog to disconnect it from the computer.
4. I insert the card into the Supercard and power it on.
5. I launch nesDS from the Supercard menu (or DSOrganize or Moonshell) and it prompts me with the error that the DLDI driver is missing.

As I stated before, if I do steps 1 and 2 with bob_fossil's DLDI Win32 GUI app, it patches successfully and displays the results within the program.

Now, there was something that I just noticed that interested me. Even though I chose the install option it to put information into the Path, I did not see anything when I just checked it. So I uninstalled and reinstalled DLDIrc and now it shows up in the Path Environment Variable. Although the Command Prompt window still opens and closes too quickly. I'm running Windows 2000 on this PC, could this have anything to do with it?
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3

#133901 - psychowood - Mon Jul 09, 2007 5:25 pm

MechaBouncer wrote:

[...]
2. The command prompt opens and closes too quickly for me to see what it says.
[...]
I'm running Windows 2000 on this PC, could this have anything to do with it?


Win2k could be the problem.

Two are the things that came up in my mind:
-NSIS (the installation script) doesn't correctly work with the Win2k registry (this could explain also why you had some problems adding dldirc to the path)
-AFAIK the Win2k batch syntax should be the same of WinXP but there could be something different. I haven't tried it directly but you are the 1st one reporting this issue (and with more than 5000 downloads I suppose that you aren't the only Win2k DLDIrc user ;) )

Try this to read the patching output:
-Open a command prompt (run "cmd")
-Inside the prompt, run (with quotes)
Code:
"C:\Program Files\DLDIrc\scds.dldi.cmd" "C:\Documents and Settings\TODD.ENCO\My Documents\Games\NDS\nesDS\nesDS.nds"


You can also replace scds.dldi.cmd with scds_moon.dldi.cmd if you want to try the moon driver.

PS.Do you have this problem only with nesDS/SC or with every homebrew/driver?
_________________
DLDIrc Developer

#133904 - MechaBouncer - Mon Jul 09, 2007 5:52 pm

Okay, I ran it through the Command Prompt on an unpatched version of nesDS. Here's what I got:
Code:
C:\Program Files\DLDIrc>scsd.dldi.cmd "c:\documents and settings\todd.enco\my do
cuments\games\nds\nesds\nesds.nds"
[DLDI Patching script by PsychoWood][v0.73]
Patching for SuperCard (SD Card)

ROM to be patched:
"c:\documents and settings\todd.enco\my documents\games\nds\nesds\nesds.nds"

If it is not a homebrew ROM with DLDI
support, it will be CORRUPTED!

*Press a key to patch it,
or close the window to cancel.*

Dynamically Linked Disk Interface patch tool v1.23 by Michael Chisholm (Chishm)

Trying "C:\Program Files\DLDIrc\drivers\scsd.dldi"
Old driver:          No DLDI driver
New driver:          SuperCard (SD Card)

Position in file:    0x00006F60
Position in memory:  0x02006D60
Patch base address:  0xBF800000
Relocation offset:   0x42806D60

Patched successfully
Press any key to continue . . .


So that succeeded. But I just tried patching it from the right-click menu again (even after it's been added to Path), and it still doesn't seem to patch it. I've checked by then patching it again with the DLDI Win32 GUI and it says that no DLDI driver was previously patched.

And so far, I've only noticed that nesDS does it. However, I'm now wondering whether it's patching anything else. DSOrganize has SC support from the start and Moonshell has several versions pre-patched from the installer. DSLiveWeather reads fine, but won't save (although I'm hearing that saving is problematic now anyway?). DScent runs and loads and saves data, but crashes after a while (not sure if it's related, but I would think it wouldn't run at all). Those are the main programs I've been running, but nesDS is the first to flat out refuse to run. It makes me wonder just how many have generic card support built-in (which would probably include the SCSD as it has been around for so long)?

It looks like I need to try this out some more on my XP machine at home. I've been using my 2000 machine at work without problems for a while. This is the first I've seen it give me trouble. Thanks for looking into this. I wonder if anyone else has had any issues?

EDIT:
And I just checked DSAIM 0.03e and it doesn't seem to patch with DLDIrc, either. And my DSOrganize 2.7 Final, even though I patched it with DLDIrc and it works, turns out that it wasn't patched and was probably using its native SCSD support. I even tried changing DSLiveWeather's (ver 2007/06/27) with the GBAMP DLDI driver through DLDIrc and when I ran the Win32 GUI app, it still said it was patched for SCSD. So it looks like DLDIrc v0.73 isn't working at all on this computer. Oddly enough, I do recall an older version working fine. Back then, when you right clicked on a file, it just said "DLDI SuperCard (SD Card)" instead of "DLDIrc SuperCard (SD Card)". At least, I seem to remember it working correctly.
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3


Last edited by MechaBouncer on Mon Jul 09, 2007 6:21 pm; edited 1 time in total

#133908 - psychowood - Mon Jul 09, 2007 6:18 pm

Since you get the "press any key" thing, probably the problem lies in the registry itself: with regedit, give a look in HKEY_CLASSES_ROOT\ndsfile\shell to see if there are all the correct DLDIrc calls. It is also possible that Win2k handles those calls differently than WinXP, and then they do not work even if they're there...

Btw, the "Add to path" option isn't related to the context menu, it just gives you the ability to run, in a command prompt, "dldirc driver romfile" without having to specify the full path of DLDIrc and of the driver (without that option, you'd have to run "C:\program files\dldirc\dldirc" "C:\program files\dldirc\drivers\driver" romfile). Moreover if you run "dldirc" without arguments, you get a complete list of the available drivers.

MechaBouncer wrote:
So that succeeded. But I just tried patching it from the right-click menu again (even after it's been added to Path), and it still doesn't seem to patch it. I've checked by then patching it again with the DLDI Win32 GUI and it says that no DLDI driver was previously patched.


This is very strange! If you run the patching command twice, do you get "Old driver: No DLDI driver" or "Old driver: SuperCard (SD Card)"?
The Win32 GUI tells me that my nesDS rom has the right driver inside, after DLDIrc patching...

If you want, try one last thing: download dlditool.exe from chishm's site and try a manual patch: if it still doesn't work, than simply dlditool.exe has some problems with (your?) Windows 2000 :)
_________________
DLDIrc Developer

#133915 - tepples - Mon Jul 09, 2007 7:47 pm

psychowood wrote:
Two are the things that came up in my mind:
-NSIS (the installation script) doesn't correctly work with the Win2k registry (this could explain also why you had some problems adding dldirc to the path)

Does it depend on whether the user running the installer is a member of Administrators or not?
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.

#133918 - MechaBouncer - Mon Jul 09, 2007 7:50 pm

Well I'm not sure what is supposed to be there in the registry, but they look like they're there. Here's the SCSD entry as an example:

HKEY_CLASSES_ROOT\ndsfile\shell\DLDIrc SuperCard (SD Card) Patch\command\

Name: (Default)
Type: REG_SZ
Data: C:\Program Files\DLDIrc\scsd.dldi.cmd "%1"


And sorry about that last part. I failed to state that "patching it again" wasn't patching the same file over. If I manually patch it with the command line like that again, it does properly patch the file if I open it in the Win32 GUI app. What I meant by "patch it again", was to patch a copy of the unpatched file (which doesn't have a driver to begin with). Running it from the command line twice will say "Old driver: SuperCard (SD Card)" as it should. Sorry about that.

Just to be sure, I did download dlditool and here's the results:
Code:
C:\Documents and Settings\TODD.ENCO\My Documents\Games\NDS\DLDI\dlditool-win32>d
lditool scsd.dldi "c:\documents and settings\todd.enco\my documents\games\nds\ne
sds\nesds.nds"
Dynamically Linked Disk Interface patch tool v1.23 by Michael Chisholm (Chishm)

Trying "scsd.dldi"
Old driver:          SuperCard (SD Card)
New driver:          SuperCard (SD Card)

Position in file:    0x00006F60
Position in memory:  0x02006D60
Patch base address:  0xBF800000
Relocation offset:   0x42806D60

Patched successfully



And my login account is a member of the Administrators group, just to be clearer. So I do have full administrator rights.
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3

#134001 - psychowood - Tue Jul 10, 2007 1:28 am

=======
IMPORTANT EDIT, put first because it could be THE solution ;)
In the same location of the registry as before, add the first part of the command in double quotes.

So

Code:
HKEY_CLASSES_ROOT\ndsfile\shell\DLDIrc SuperCard (SD Card) Patch\command\

Name: (Default)
Type: REG_SZ
Data: C:\Program Files\DLDIrc\scsd.dldi.cmd "%1"


becomes

Code:
HKEY_CLASSES_ROOT\ndsfile\shell\DLDIrc SuperCard (SD Card) Patch\command\

Name: (Default)
Type: REG_SZ
Data: "C:\Program Files\DLDIrc\scsd.dldi.cmd" "%1"


and see if the command prompt still opens/closes quickly. If it still does not work, go on reading my post ^^
=======

@tepples: You're right, but the installer simply doesn't go on if you aren't an admin :)

MechaBouncer wrote:
Well I'm not sure what is supposed to be there in the registry, but they look like they're there.


Yes, everything seems ok.

Quote:
And sorry about that last part. I failed to state that "patching it again" wasn't patching the same file over. If I manually patch it with the command line like that again, it does properly patch the file if I open it in the Win32 GUI app. What I meant by "patch it again", was to patch a copy of the unpatched file (which doesn't have a driver to begin with). Running it from the command line twice will say "Old driver: SuperCard (SD Card)" as it should. Sorry about that.


No need to be sorry, really :) it's my english that isn't that good ^^

Quote:
Just to be sure, I did download dlditool and here's the results:
[...]


Which are exactly the same results of DLDIrc :(

Sorry if I bother you, but to be sure I'm not misunderstanding anything I need you to do more annoying tests :| because I really can't keep up with what is happening :(

If you check the driver of nesds.nds with the Win32 GUI after you patched it via dlditool, what does the GUI say?

If, when you get a "Patched succesfully" message, the file isn't really patched, the problem isn't DLDIrc related.

Anyway, I'm sure that when the command prompt opens and closes too quickly, the file is not patched, so don't expect it to work on your SC (and on any other card either). It is probably not fully compatible with Win2k (old versions had a different integration method, but I can't use it anymore because it was too much limited), and now I need to check if I can "repair" it in some way or if I have to drop Win2k support :(

Next weekend if I have enough time I'll install Win2k again :)

Is anybody out there using DLDIrc succesfully on Windows 2000?
_________________
DLDIrc Developer

#134099 - MechaBouncer - Tue Jul 10, 2007 4:05 pm

psychowood wrote:
=======
IMPORTANT EDIT, put first because it could be THE solution ;)
In the same location of the registry as before, add the first part of the command in double quotes.

So

Code:
HKEY_CLASSES_ROOT\ndsfile\shell\DLDIrc SuperCard (SD Card) Patch\command\

Name: (Default)
Type: REG_SZ
Data: C:\Program Files\DLDIrc\scsd.dldi.cmd "%1"


becomes

Code:
HKEY_CLASSES_ROOT\ndsfile\shell\DLDIrc SuperCard (SD Card) Patch\command\

Name: (Default)
Type: REG_SZ
Data: "C:\Program Files\DLDIrc\scsd.dldi.cmd" "%1"


and see if the command prompt still opens/closes quickly. If it still does not work, go on reading my post ^^


That worked!! The prompt came up and waited for me to press a key to continue and waited after it had patched. Hooray!

Sorry it took so long. Since I've been testing this on my PC at work, I occasionally have to actually do stuff. <_< >_>

But thank you! I only hope that this fix for Win2K doesn't break something on WinXP. I'll have to try it on my WinXP machine when I get home to make sure it still works. Thanks again! ^_^
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3

#134101 - psychowood - Tue Jul 10, 2007 4:31 pm

MechaBouncer wrote:
That worked!! The prompt came up and waited for me to press a key to continue and waited after it had patched. Hooray!

Sorry it took so long. Since I've been testing this on my PC at work, I occasionally have to actually do stuff. <_< >_>

But thank you! I only hope that this fix for Win2K doesn't break something on WinXP. I'll have to try it on my WinXP machine when I get home to make sure it still works. Thanks again! ^_^


Great! :D

The patch does not broke WinXP compatibility, so...

*v0.74
-Fixed Win2k compatibility

And thanks to you for the bug reports ^^
_________________
DLDIrc Developer

#134123 - pas - Tue Jul 10, 2007 8:01 pm

Could you please make it that we can configure it so if you right click a NDSHomebrew, and then press... maybe patch !
then it will automatically use the patches we specificed,

and spit out all patched files to the source directory with names like

Homebrew_Gbamp.nds
Homebrew_M3CF.nds
Homebrew_R4&M3Simply.nds
Homebrew_DSLink.nds
.....


?

Do you understand what I mean ?
_________________
Starcraft DS ?

#134126 - MechaBouncer - Tue Jul 10, 2007 8:14 pm

Or maybe a separate option like "Patch All" that serves that function. While I can see that being useful, there are some cases where it'd just be overkill. Or maybe an option that's configured at install?
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3

#134147 - psychowood - Wed Jul 11, 2007 12:11 am

Good idea!

*v0.8
-Added Multipatch option (creates a renamed copy of the ROM for
each selected driver, except fcsr)

^^

MechaBouncer, could you please test the multipatch option under Win2k? TIA
_________________
DLDIrc Developer

#134212 - MechaBouncer - Wed Jul 11, 2007 5:18 pm

You're welcome. It seems to be working fine here. All files I've tested were copied and patched successfully.
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3

#134213 - psychowood - Wed Jul 11, 2007 5:29 pm

MechaBouncer wrote:
You're welcome. It seems to be working fine here. All files I've tested were copied and patched successfully.


Thanks :)
_________________
DLDIrc Developer

#134229 - pas - Wed Jul 11, 2007 8:14 pm

Thanks for implementing that psychowood ! Great stuff !
_________________
Starcraft DS ?

#134297 - psychowood - Thu Jul 12, 2007 10:19 am

*v0.81
-Added G6 Real and NEO2 SD v2 driver
_________________
DLDIrc Developer

#137653 - psychowood - Tue Aug 14, 2007 1:55 pm

*v0.9
-Added dldi autopatcher enabler-disabler option, used to avoid
firmware autopatching (where present). Credits for the idea go to
Nphinity
-Updated EzV driver and GBA Movie Player (SD Card) driver
-Added Max Media Player 4gb hdd driver
_________________
DLDIrc Developer


Last edited by psychowood on Wed Aug 15, 2007 7:26 am; edited 4 times in total

#137661 - MechaBouncer - Tue Aug 14, 2007 3:50 pm

Oh awesome! So, in order to make this work, do we need to first patch it with the proper DLDI patch and then disable the autopatching on it?
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3

#137662 - psychowood - Tue Aug 14, 2007 4:01 pm

MechaBouncer wrote:
Oh awesome! So, in order to make this work, do we need to first patch it with the proper DLDI patch and then disable the autopatching on it?


Yes, the enabler/disabler simply changes the DLDI header in the ROM so that it is no longer (at least as long as you don't change it again) seen as a DLDI app.
You can see it like a DLDI lock, if you prefer :)
_________________
DLDIrc Developer

#137667 - MechaBouncer - Tue Aug 14, 2007 5:06 pm

It would seem that there is a new EZ-Flash V DLDI driver by ps2aich that fixes unaligned reads. He made a request to you to add it to DLDIrc:
ps2aich wrote:
To Psychowood: I think you have still an ez5s_v2.dldi in your
excellent tool DLDI Right Click (I can recommend it to all EZ-V users, because
it also does the Headerfix for homebrew, which is needed for the EZ-V) ,
you can replace it by this new driver.


And I'm not sure that it matters or not, but the CycloDS DLDI driver has been confirmed by Team Cyclops to be for the Slot-2 CycloDS and not for the Slot-1 CycloDS Evolution. I don't know if any additional information needs to be added to avoid confusion or not.
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3

#137669 - psychowood - Tue Aug 14, 2007 5:22 pm

MechaBouncer wrote:
It would seem that there is a new EZ-Flash V DLDI driver by ps2aich that fixes unaligned reads. He made a request to you to add it to DLDIrc:
ps2aich wrote:
To Psychowood: I think you have still an ez5s_v2.dldi in your
excellent tool DLDI Right Click (I can recommend it to all EZ-V users, because
it also does the Headerfix for homebrew, which is needed for the EZ-V) ,
you can replace it by this new driver.


Oh, I missed that request, thanks for pointing it up. I'll update it right now. (EDIT: Updated)

Quote:
And I'm not sure that it matters or not, but the CycloDS DLDI driver has been confirmed by Team Cyclops to be for the Slot-2 CycloDS and not for the Slot-1 CycloDS Evolution. I don't know if any additional information needs to be added to avoid confusion or not.


Ok, edited driver name to "CycloDS mini/micro" :)
Btw, about your post on the CycloDS forum: DSLink already supports SDHC :P
_________________
DLDIrc Developer

#137687 - MechaBouncer - Tue Aug 14, 2007 7:55 pm

True, but I don't plan on putting FlashMe on my DS Lite, so the missing NoPass is a deal-breaker. My NDSL's a refurb with a quirky touch screen and I don't want to mess with trying to unflash it should I need to send it back for repairs. Not to mention that it wouldn't work if I ever wanted to use another Slot-2 device again. Thanks for the tip, but I'll pass.
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3

#137690 - psychowood - Tue Aug 14, 2007 8:18 pm

MechaBouncer wrote:
True, but I don't plan on putting FlashMe on my DS Lite, so the missing NoPass is a deal-breaker. My NDSL's a refurb with a quirky touch screen and I don't want to mess with trying to unflash it should I need to send it back for repairs. Not to mention that it wouldn't work if I ever wanted to use another Slot-2 device again. Thanks for the tip, but I'll pass.


Just joking.. I mean, I love my DS-Link but I don't think that today it is worth buying new, especially because the team seems to lack support lately (last update was 2 months ago), even if I don't really know if new updates are needed, I haven't tried any recent games yet.
_________________
DLDIrc Developer

#137700 - tepples - Tue Aug 14, 2007 9:22 pm

MechaBouncer wrote:
True, but I don't plan on putting FlashMe on my DS Lite, so the missing NoPass is a deal-breaker.

If you buy a Games n' Music adapter for SLOT-1 and use it without inserting a microSD card, then it will act as a NoPass. If you buy an Action Replay DS accessory and hold Select while you turn on the DS power, it will also act as a NoPass. A lot of SLOT-1 accessories have this feature in some form.


Quote:
My NDSL's a refurb with a quirky touch screen and I don't want to mess with trying to unflash it should I need to send it back for repairs.

You don't need to unflash it. Just installing FlashMe Stealth is enough.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.

#137715 - MechaBouncer - Tue Aug 14, 2007 10:41 pm

I still haven't found much reason to FlashMe the Lite, aside from the inconvenience of needing a NoPass for my SCSD. I did FlashMe my original DS, which a friend has been borrowing indefinitely with my old GBAMP, so it's worked out for him. It's just not something I think I necessary anymore. So unless some kind of homebrew WMB method absolutely takes off and requires me to FlashMe it, I'll just stick with a NoPass solution.

Although I am in the market for a Slot-1 card to replace my SCSD (which has been acting up lately and sticks out too much for my tastes). So I've been looking at the R4/M3DSS and CycloDS Evo the most and a little bit at the EZ-Flash V. I bought a EZ 3-in-1 pack (even bought a R4, but was refunded due to it being out of stock too long), so I'm definitely getting a Slot-1 card to make use of it. The question is which one to get? I'm almost decided on the CycloDS Evo, but the unreleased DLDI driver is holding me back (even if it does do autopatching). I'll probably still get it when the new batch is available (the casing has been slightly retooled to fit better and it's available in black and white).

As for the others, they all seem to have flaws I don't like. The GnM is slow and of cheap construction. I have little interest in the Action Replay DS and would probably use NitroHax instead. The SCDS1 is picky about what cards it works with and I've been weary about SC products as of late. Even the EZ-V has the need for extra patching to get any apps to work. I'm not sure if any others are worth looking at.
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3

#138117 - derula - Mon Aug 20, 2007 12:40 am

Hi,
assuming that this is the official thread for DLDIrc, I have a usability suggestion:

Rename the registry keys, maybe to
Code:
HKEY_CLASSES_ROOT\ndsfile\shell\toggle
HKEY_CLASSES_ROOT\ndsfile\shell\multipatch
HKEY_CLASSES_ROOT\ndsfile\shell\patch


Then assign the names for the items as the default value for these keys instead of using them as key names.

That has two advantages: key names are more flexible (as they don't differ for which driver is used). As long as only one driver is used, for patching always HKEY_CLASSES_ROOT\ndsfile\shell\patch\command will be read. For multiple drivers you might use something like HKEY_CLASSES_ROOT\ndsfile\shell\patch2 and so on.

But the main advantage is that it will allow you to select a default option (which will occur on double click): After I've updated to 0.9 from... 0.3 or so xD, I wanted to patch my NDS file, double-clicked - and what did it? turn DLDI off. I wasn't quite amused :)

So you can just assign "patch" as the default value for HKEY_CLASSES_ROOT\ndsfile\shell, and it will be used on double-click. I tried to use the key name the installer created there, but it didn't work; obviously no spaces are allowed.

Er. I don't think you got too much of what I posted, so let pix do the talking :> :

[Images not permitted - Click here to view it]

Hope you'll add that to next version!
_________________
visit my blog. please.

#138135 - laos - Mon Aug 20, 2007 3:28 am

Awesome! Now i dont need to keep a run on my desktop to access the command prompt

Works so far for me

using vista home premium
_________________
laos,
In charge of Storyline: Tales of Dagur 2

#138312 - MechaBouncer - Wed Aug 22, 2007 9:10 pm

Team Cyclops released a BETA DLDI driver for the CycloDS Evo. You can get it here:
http://www.cyclopsds.com/downloads/CycloEvoDLDI_v1.0.zip

It is worth mentioning that it does not properly initialize SDHC cards:
TeamCyclops wrote:
Hrm, there is one problem with this DLDI driver. The driver relies on a flag getting set by the loader to tell it if you're using a SDHC card or not. It doesnt detect this internally. Therefore, this DLDI driver will not work with SDHC MicroSD's. I'll work on a fix, but in the meantime, the DLDI driver posted should be considered BETA ONLY!


Here's the original topic:
http://www.teamcyclops.com/forum/showthread.php?p=11382#post11382
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3

#138314 - psychowood - Wed Aug 22, 2007 9:56 pm

@derula,
I understood what you meant ;) and it is a good suggestion, but that would require a major rewrite of DLDIrc, so I think I'll postpone it. By now I have reordered the menu voices though, now Multipatch and Lock/Unlock are after the DLDI patches, do you think this could be a workaround?

@laos: Thanks for your compatibility report.

@MechaBouncer: As always, thanks for keeping me informed :)

And here we go....

*v0.91
-Added CycloDS Evolution driver (BETA: it doesn't work with SDHC)
-Reordered menu: Multipatch and Lock/Unlock option are now after
the standard DLDI patches


:)
_________________
DLDIrc Developer

#138315 - derula - Wed Aug 22, 2007 10:03 pm

psychowood wrote:
By now I have reordered the menu voices though, now Multipatch and Lock/Unlock are after the DLDI patches, do you think this could be a workaround?


Sure, if that works. I think Windows sorts the items alphabetically, and the first one is usually the default (which will apply on double click) if not defined differently. Not 100% sure though.
_________________
visit my blog. please.

#138316 - psychowood - Wed Aug 22, 2007 10:08 pm

derula wrote:

Sure, if that works. I think Windows sorts the items alphabetically


Yep, that's why the patches are named "DLDIrc......." and the other two options now are "Multi DLDI Patch" and "Lock/Unlock DLDI", because D comes first than L and M ;)
The only "bad" thing is that if you use more than one driver, they will be always sortered alphabetically, so the default one will still be the one that comes first.

I'll work on it, but actually giving the user the option to order the menu itself (or simply the option to choose a default driver) will be rather tough to do.

EDIT: So many typos... :|
_________________
DLDIrc Developer

#138686 - MechaBouncer - Mon Aug 27, 2007 9:04 pm

When asked if I could post the CycloDS Evo beta driver elsewhere, this was the response:
TeamCyclops wrote:
No, please dont post this driver anywhere else yet - its currently BETA and for testing only. It's going to be replaced soon with a fixed driver which will work with SDHC cards properly.


So I don't know if you want to leave it in there or not. I'll let you know if there are any updates.
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3

#139465 - MechaBouncer - Thu Sep 06, 2007 4:52 pm

There's a new CycloDS Evolution driver out now in this topic:
http://www.teamcyclops.com/forum/showthread.php?t=1203&page=4

Here's what TeamCyclops reports:
TeamCyclops wrote:
We've just uploaded v1.1 of the DLDI driver for CycloDS Evolution. Download it here. There have been quite a few changes from the last file released, most notably:

* Now contains full SD init code. This means it will work with both standard and SDHC MicroSD cards, and it should work with homebrew executed via WMB (untested) or other alternative loading methods, allowing you to completely bypass loading through the CycloDS Evolution GUI if you wish. We've personally tested the driver by loading homebrew from slot2 CycloDS, which works fine.
* Various workarounds are included to enable support for the various ways in which 3rd party loaders use the DLDI driver. Its been tested to work with DSOrganise (Chishm loading method only), DSChannels and Chishm's standalone loader.

This is the same DLDI driver which is included in the new v1.2 BETA #3 firmware. Unless you're not using CycloDS Evolution to actually load your homebrew (which would be the case if you're executing code via WMB) then you dont actually need to manually patch anything, even in the case of 3rd party loaders.


I've tested it with Chishm's NDS_loader, DSOrganize 2.9, and DSChannels Beta 5. NDS_loader and DSO launch and run without issue, but apps launched from DSChannels can't read from the memory card unless they are manually DLDI patched. Considering that DSO seems to permanently patch what it launches, all that needs to be done is launch them from DSO once and they'll work. I'd say this is a pretty substantial update!
_________________
Cobalt/Black NDSL
CycloDS Evolution (firmware 1.55 BETA 3) and EZFlash 3-in-1
Kingston SD-C02G JAPAN 2GB MicroSD
MoonShell 1.71, DSOrganize 3.1129, QuakeDS Pre3, ScummVM DS 0.11.1, Pocket Physics 0.6, OpenTyrian DS 0.3

#141035 - psychowood - Fri Sep 21, 2007 11:58 am

MechaBouncer wrote:
There's a new CycloDS Evolution driver out now in this topic:
http://www.teamcyclops.com/forum/showthread.php?t=1203&page=4


How did I miss your post? Sorry for being late :)

*v0.92
*-Added CycloDS Evolution non-Beta driver
_________________
DLDIrc Developer

#143157 - psychowood - Wed Oct 17, 2007 2:28 pm

*v0.93
-Updated EZ4 and SCDSOne driver, added SC Rumble driver
_________________
DLDIrc Developer

#144480 - ghOst - Fri Nov 02, 2007 6:57 pm

Thanks for this usefull tool.

The new CycloDS evolution DLDI 1.2 is here http://www.cyclopsds.com/downloads/CycloEvoDLDI_v1.2.zip

It works like a charm ;-)