#125237 - chishm - Thu Apr 12, 2007 8:34 am
As you may have noticed, I've been a bit busy lately and have been missing DLDI driver updates. Since DLDI was meant to be a way for libfat device drivers to be updated independent of me, it is a bit stupid for them all to be listed on one web page that only I can edit. Therefore I've decided to make a DLDI Wiki.
Sections I've thought of so far are:
- A page for each device
- A page for each device for users to report compatibility
- A page for each tool / utility
- Tutorials on how to use the tools
- Instructions for developers using libfat / DLDI-enabled gba_nds_fat
- Instructions on how to write a DLDI driver
Since I'm obviously not perfect, I've probably missed something, so I'm looking for suggestions of what else can be included. Keep in mind that this is specifically for DLDI, and not homebrew in general.
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com
#125259 - felix123 - Thu Apr 12, 2007 12:05 pm
Maybe in different languages?
_________________
Nintendo DS homebrew on Wikipedia
#125290 - dantheman - Thu Apr 12, 2007 3:51 pm
A brief description of what DLDI is and why it was created would be good for newbies. Currently I link people to a summary I made, but it's hosted on That Other Site (tm) so I can't post it in certain places like GBAdev.
#125351 - ps2aich - Thu Apr 12, 2007 7:03 pm
Very good idea :-)
I'm happy with your initial sections, hopefully a wiki is
dynamic enough to change.
I think one language (englisch) should be sufficient, since
imho it should be developer oriented.
The only exception may be the tutorials for endusers
to patch the homebrews.
#125398 - chishm - Fri Apr 13, 2007 2:27 am
I like the idea of multiple languages. I know that someone translated (an outdated version of) my page into Japanese, and the DS community isn't purely english-speaking.
dantheman:
An intro to DLDI would definitely help newbs. Maybe it could have a list of articles for beginners, including an introduction and patching tutorials.
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com
#125399 - HyperHacker - Fri Apr 13, 2007 2:58 am
There are a fair number of Japanese DS coders out there that would probably appreciate a translation. I'd say if we can find someone willing to maintain a version in their choice of language, do it.
_________________
I'm a PSP hacker now, but I still <3 DS.
#125418 - SyntaxGS - Fri Apr 13, 2007 4:20 am
| felix123 wrote: |
| Maybe in different languages? |
http://www.google.com/translate_t
http://babelfish.altavista.com/
_________________
Nintendo DS Onyx :: Supercard Lite :: Superkey :: 1GB microSD
#125420 - dantheman - Fri Apr 13, 2007 4:39 am
For reference, here is the summary I posted on that site, already in Wiki formatting for convenience. Obviously some things would need to be reworded if it were to be used on the official site, and the "getting started" section is highly outdated, and the "Supercard Issues" section would either require its own page or be a part of the SCSD_moon.dldi page, but it's a good starting point.
I apologize if any of the information here is incorrect. I am not a programmer, so though I attempted to do research before writing the summary, I'm sure I inadvertedly posted some incorrect or incomplete info.
You'll also notice that I stole much of the info directly from the original libfat page, hehe. Ah well.
| Quote: |
==History of libfat==
For many DS applications to be useful, it is necessary for the application to read and write data to and from the storage medium (SD card, microSD, CF, etc) used by the homebrew device. This lets you save your login for IRC, save your TODO list, delete files, read MP3 files, etc.
To do this, a coder named Chishm came up with a pair of libraries called gba_nds_fat and libfat, some reusable programming code that allowed for read/write access to the CF and SD cards of a few popular devices of the time, like the Supercard and M3. Since coders typically don't like to reinvent the wheel, pretty much every homebrew application out there used one of these libraries.
However, herein lied the problem. What if you weren't using a supported device? New devices started coming out more rapidly, faster than Chishm could successfully add stable, usable code to libfat. Some cards, like the DS-X and G6, didn't even release drivers at all, so they remained incompatible with many DS homebrew applications. In addition, after each new device was added to libfat, each and every homebrew program would have to recompile with the new libfat to add support for the device. Needless to say, this became a problem for older homebrew that was abandoned by its authors. In December of 2006, Chishm decided that a change was necessary. He proposed a new system called DLDI that would replace the current system, bringing with it great benefits. Most of the GBAdev community seemed acceptable to the idea, and thus Chishm gave the community a great Christmas present, releasing the first version of the DLDI interface.
==What is DLDI?==
DLDI is a '''D'''ynamically '''L'''inked '''D'''evice '''I'''nterface for libfat. What does that mean? Basically, instead of including static drivers for each device in every homebrew program, a 32 KB placeholder is inserted into the code instead. This placeholder is then replaced by the user, who patches the homebrew program with a specific DLDI patch for his or her specific homebrew device.
==Benefits of DLDI==
*Chishm no longer has to maintain all the drivers for all the cards. As soon as a driver is written by anyone, it is usable by everyone.
*Cards that aren't even released yet are supported by programs that have already been compiled. No more having to recompile to add support for a card.
*Manufacturers don't have to release source code to release an easily usable driver. No more having to recompile using other libraries. They don't need to make publicly available their trade secrets. Of course, this means we have to disassemble whatever they do release to understand the hardware, but we already have to do this (M3, G6, GBAMP).
==Downsides of DLDI==
*There is an extra step added to compile then copy to card then run a debug build. The tool is command line based, so this can be added to the makefile.
*Users need to patch any apps that use libfat for their particular card. This is okay, as they already do it for commercial ROMs. Alternatively, multiple builds can be released on a website, but this kinda reduces the utility of such a scheme.
Because users must patch each piece of homebrew they wish to add to their flash cart, users of devices already supported by libfat might view it as nothing but an inconvenience. However, the benefits outweigh the downsides. With the recent onslaught of new slot-1 devices being released, the DLDI interface allows for each device to be instantly compatible with many homebrew applications as soon as a DLDI patch file is made for the device.
==Getting Started==
To begin using the DLDI system, first ensure that the homebrew program you wish to try has indeed been compiled with DLDI support. Anything last updated before December 2006 will not have DLDI support at all. Once you've found a suitable homebrew program, download it and extract it to a folder. Then go to http://chishm.drunkencoders.com/DLDI/ where you will download several files:
#The correct DLDI patch for your specific device.
#The patcher program itself, called dlditool.exe
#The GUI program if you are using Windows and do not wish to use the command-line
Disclaimer: The GUI and the dlditool.exe program are made by two separate people. As such, the GUI may sometimes be out of date.
Command-line instructions: once you've obtained the required files, place the DLDI patch file into the directory where dlditool.exe resides. Open a command shell and type "dlditool.exe" to receive the simple syntax instructions. As an example, typing
dlditool.exe scsd.dldi WordWrap.nds
will patch the WordWrap.nds file with the Supercard SD DLDI file.
The Windows GUI should be fairly self-explanatory.
==Supercard Issues==
Some newer Supercards have different internal workings that do not work with the default DLDI file. Supercard Lites were the first to exhibit this behavior, but issues with regular Supercard SD units have also been reported. They show few signs of being modified, and it is not a change that was ever announced by the Supercard team. However, due to differences in the internal workings of the devices, normal libfat code does not work. Moonlight, the creator of Moonshell, has created an alternate SCSD_moon.dldi patch file that has been reported to work on these Supercards when the standard SCDS.dldi and SCLT.dldi patches have failed.
This modified DLDI patch is reportedly made up of Supercard SD fat code taken from older versions of Moonshell, which were different than that of libfat. [http://forum.gbadev.org/viewtopic.php?t=12410&start=15]
There are several locations to download this file:
*[http://mdxonlinemirror.dyndns.org/resources/20070101_dldi_scsd_ver10_20070101.zip Moonlight's blog] - this file was previously reported to have only reading capability, not writing. However, it has the same CRC as the reportedly fully working ones.
*[http://www.cryptosystem.org/projects/nds/scsd_moon.dldi Cryptosystem mirror]
*[http://www.sendspace.com/file/5j8j65 SendSpace mirror]
*[http://pinocchio.jk0.org/gbaforum/supercard_lite_dldi.zip Tepples' temp server]
==External Links and References==
*[http://chishm.drunkencoders.com/DLDI/ DLDI homepage]
*[http://forum.gbadev.org/viewtopic.php?t=12001&postdays=0 GBAdev forum thread where it all originated]
*[http://www.monroeworld.com/forum/showthread.php?t=8691 DLDI summary that influenced this one]
|
#125429 - FifthE1ement - Fri Apr 13, 2007 6:28 am
Chishm, I would be willing to provide the space if you need it and I already have a wiki setup.
links to piracy rmoved
I would give you full administrator privileges and I also have free wordpress mu blogs for developers on the sister site.
I too created a great DLDI guide from scratch which you can find on moddz, and I really think you have done a great job with everything. You give your time and dedication to something you don't get paid for, as do I. Let me know if you need any web-space or want to use the Wiki.
FifthE1ement
links to piracy rmoved
#125459 - chishm - Fri Apr 13, 2007 3:01 pm
Thanks for the offer, FifthE1ement, but I already have the server organised.
dantheman:
I might write my own summary, as I can give my thoughts on it. However, being a wiki, I'll let other people edit it to make it easier to understand.
SyntaxGS:
Machine translation is good for some things, but translated detailed instructions tend to become very confusing.
HyperHacker:
There's also a thriving french DS community that could do with some translated instructions.
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com
#125490 - Lynx - Fri Apr 13, 2007 10:18 pm
Open the Wiki.. you can always improve as it goes.. isn't that part of it being a Wiki?
_________________
NDS Homebrew Roms & Reviews
#125805 - tondopie - Tue Apr 17, 2007 4:24 am
Great idea Chishm. That will stop all those n00bs on DCEmu emailing and pming me all the damn time and posting comments on my blog of 'how do patch GBAMP MB selector or DSdiag?'... argh...
#125810 - chishm - Tue Apr 17, 2007 5:29 am
Well here it is, the DLDIWiki.
Big thanks to Dovoto for hosting and setting up the software.
As you can see, I've gone and added all the original information from my original DLDI page, and there's been some extra contributions from Lynx and Jevinskie. I'm looking for a logo for the wiki (you can probably see that I don't have one yet), so if you want to design one, post it here and I will chose my favourite.
Anyone can register for the Wiki and you can edit any page after you've registered. You'll need special permission to upload files, which can be granted by a Wiki Sysop or Beauracrat.
When adding a device driver, please follow the existing examples (use the template). If a driver is usable by more than one device, create a page for the other device and use a redirect like this:
| Code: |
#REDIRECT [[original device]]
[[Category:Devices]] |
If you have come across problems with a device, you may wish to use the Discussion page first, to see if it is just you or other people are experiencing the same issue. If it is a confirmed issue, then make a note of it under the particular device driver. For example, you might post this on the GBA Movie Player (Compact Flash) page:
| Code: |
{{Driver | name=MPCF | dldifile=mpcf | sourcefile=mpcf | author=Chishm | lastupdate=2006-12-25 | readtest=Works | writetest=Fails }}
Writing fails with program X |
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com
#125818 - viruseb - Tue Apr 17, 2007 8:16 am
Good work, that sound really promising.
If I can risk an improvement on the driver template, adding a table listing homebrews compability can be interesting. A table with columns like : Homebrews name, reading ok?, writing ok ?, issue and fixing instructions.
So people can readily know if he can play with its favorite homebrew with its favorite card.
#125819 - chishm - Tue Apr 17, 2007 8:32 am
| viruseb wrote: |
Good work, that sound really promising.
If I can risk an improvement on the driver template, adding a table listing homebrews compability can be interesting. A table with columns like : Homebrews name, reading ok?, writing ok ?, issue and fixing instructions.
So people can readily know if he can play with its favorite homebrew with its favorite card. |
I was thinking more along the lines of a page for each DLDI-enabled homebrew app and listing any incompatibilities there.
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com
#125852 - tepples - Tue Apr 17, 2007 4:07 pm
| chishm wrote: |
| Anyone can register for the Wiki and you can edit any page after you've registered. You'll need special permission to upload files, which can be granted by a Wiki Sysop or Beauracrat. |
How do users apply for upload rights, and what criteria shall admins use to evaluate these applications?
| chishm wrote: |
| I was thinking more along the lines of a page for each DLDI-enabled homebrew app and listing any incompatibilities there. |
Then the criteria for granting upload rights will have to be lax in order to allow for screen shots on the pages.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#125853 - chishm - Tue Apr 17, 2007 4:10 pm
I'll slowly add guidelines to this thread as I finalize them.
Here are some guidelines for Sysops / Bureaucrats:
Add users to the programmer group if they need to upload a DLDI file or an image. Use your judgement and don't add them to the group if they are unlikely to contribute to the wiki in a beneficial manner, or if they are likely to cause vandalism. This process is meant to prevent abuse of the file server capabilities, and not to block all but a select few individuals.
Here are some general guidelines for all users:
Users are not to upload illegal content. The first time they do so, they get a warning, via email (if possible) and on their User: page. If they do it again, they are removed from the programmer group.
Users are not to link directly to illegal content, nor to a page that contains illegal content. Pages that are hosted on servers containing only legal content are of course linkable (just making this explicit). If a linked-to page is hosted on the same server as illegal content, and if the the page itself doesn't contain illegal content, and if there is no alternative source of information, then the page may also be linked. If a user links to illegal content, they get one warning, again via email (if possible) and on their User: page. If they do it again, their account is blocked for one week. For a third offense they get a permanent block.
The Wiki is intended for DLDI related topics, not general DS homebrew. Pages about individual homebrew apps are allowable and encouraged, but the focus should be on how that homebrew relates to DLDI. For example, information on converting movies for MoonShell is not relevant, but information on which devices have trouble saving the position in an e-book within MoonShell is relevant. All pages about DS homebrew should be added to the category DS Homebrew by adding the tag [[Category:DS Homebrew]] to the bottom of the page.
Users can apply for upload rights by posting to this thread or in this page. I'll link that page properly within the wiki when I add a DLDIWiki:Guidelines page.
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com
#125865 - silent_code - Tue Apr 17, 2007 6:29 pm
| tepples wrote: |
| Then the criteria for granting upload rights will have to be lax in order to allow for screen shots on the pages. |
true. plus, you don't want porn on your site... ;^) (what's the first thing that comes to minds of some random "users" of what to post *something* just because they can? ... just look at the internet itself. you all know that song "the internet is for porn", don't you?)
#125884 - tondopie - Tue Apr 17, 2007 10:51 pm
you should probaly apoint a few mods. you don't want whats happening to the homebrewcast.com forums do you?
#125910 - chishm - Wed Apr 18, 2007 4:24 am
I have written up a set of Guidelines now. They are the official guidelines and should be refered to when making decisions with regards to DLDIWiki. The guidelines in this thread can be considered drafts meant for discussion only.
I am contacting a few people privately, offering for them to become Sysops (wiki equivalent of admins/mods).
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com
#125912 - tepples - Wed Apr 18, 2007 4:45 am
| chishm wrote: |
| I'm looking for a logo for the wiki (you can probably see that I don't have one yet), so if you want to design one, post it here and I will chose my favourite. |
Entry #1: cards
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#125933 - Stuk - Wed Apr 18, 2007 9:50 am
| chishm wrote: |
| I'm looking for a logo for the wiki (you can probably see that I don't have one yet), so if you want to design one, post it here and I will chose my favourite. |
And my entries. All variations of the same logo:
1. [Images not permitted - Click here to view it]
2. [Images not permitted - Click here to view it]
I'm not too happy with the thing on top, but I thought I'd post it anyways:
3. [Images not permitted - Click here to view it]
Enjoy :)
#125939 - Lick - Wed Apr 18, 2007 10:27 am
My entry: http://lickr.org/files/dldi.png
Stuk, I looove your #2. Look at this, it fits perfectly!
_________________
http://licklick.wordpress.com
#125942 - chishm - Wed Apr 18, 2007 11:01 am
Ooh, these are looking very nice. I won't mention which ones I like the best until I've made my final decision, so as not to influence future designs. That reminds me, I'll make my decision this Saturday (2007-04-18) night (local time is UTC+10).
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com
#125984 - Lynx - Wed Apr 18, 2007 9:21 pm
I agree with Lick.. very nice.
_________________
NDS Homebrew Roms & Reviews
#125987 - Stuk - Wed Apr 18, 2007 10:22 pm
Thanks very much :D
#126019 - chishm - Thu Apr 19, 2007 7:19 am
A few people have told me that the devices page is a bit confusing and a big table of all the devices would be better. I'm not sure about how to do that, but I think one big category would work just as well. Are there any problems with putting all devices into Category:Devices as well as their relevant slot's category?
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com
#126035 - tepples - Thu Apr 19, 2007 2:31 pm
Wikipedia recommends against putting an article in both a category and its subcategory.
If you want to make devices easier to find, I'd suggest making a photograph of each card and making a separate navigation page rather than trying to shoehorn it into the category system.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#126036 - Lynx - Thu Apr 19, 2007 2:32 pm
My poor attempt at a logo that just doesn't seem to get it there.. but maybe someone (if it's not complete crap) can take it to a usable state.
Pics
Pic 1
Pic 2
_________________
NDS Homebrew Roms & Reviews
#126041 - chishm - Thu Apr 19, 2007 2:52 pm
That's a good idea having photographs of the devices. An image of the device placed in its article would also be useful. This means we'll need to decide on a standard size for the photo, and a suitable angle for the shot. I suggest square-on facing the label side with the contact edge at the bottom of the shot. I don't know what a useful image size would be, and whether the wiki software can automatically thumb-nail them for displaying in a device table.
I'm aware of copyright problems with using images from manufacturer's websites, so that means all photos should be taken by the submitter, or express written permission given by the copyright holder.
Also, keep the logos coming. They're all already better than what I could do.
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com
#126634 - chishm - Wed Apr 25, 2007 7:00 am
Okay, we have a winner! Stuk's first logo is now on the main page of DLDIWiki. I know I'm a bit late in choosing, trust me to set a time when I'm not near my PC.
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com
#126651 - Stuk - Wed Apr 25, 2007 5:31 pm
Yay! :D
#126679 - dantheman - Wed Apr 25, 2007 10:55 pm
I've discovered something interesting related to the SCSD vs SCSD_moon thing. Perhaps it's been discovered before, and if so I apologize for being repetitive.
In essence, I'm not sure if the issue is really with newer revisions of the Supercard or simply different types of SD cards. My Supercard miniSD with its cheap $20 miniSD card always worked with the SCSD.dldi file previously, and pre-DLDI homebrew that accessed the filesystem did so correctly. Last night however I got a new miniSD card to increase my storage and found that MCtool, Moonshell, and DSFTP were all unable to initiate the filesystem. After patching with SCSD_moon.dldi, all worked fine.
Previously I was under the assumption that the failure of SCSD.dldi was caused solely by new revisions in the Supercard hardware itself. My best guess now is that it's a combination of SC revisions and SD card revisions.
Thoughts on this? Obviously I'm eagar to contribute this info to the Wiki, but I don't want to post inaccurate data, and there's always the chance that this is an isolated incident that's caused by user error.
#126692 - HyperHacker - Thu Apr 26, 2007 12:47 am
Could there be information about the devices (what features they have, how much they cost etc) as well? Perhaps information on similar systems like Lick's RAM library?
| chishm wrote: |
| Users are not to link directly to illegal content, nor to a page that contains illegal content. Pages that are hosted on servers containing only legal content are of course linkable (just making this explicit). If a linked-to page is hosted on the same server as illegal content, and if the the page itself doesn't contain illegal content, and if there is no alternative source of information, then the page may also be linked. |
I'm not entirely clear on a few cases here, whether it would be a problem:
-linking to somewhere.com/files/coolhomebrew.nds, when somewhere.com/files/piraterom.nds also exists and directory listing is enabled (so users who try going to somewhere.com/files also see piraterom.nds)
-linking directly to a legal file on somewhere.com, when the site itself is piracy-related
-linking to a section of a site dealing with homebrew, when the site has other sections dealing with piracy
How strict are the rules about these?
_________________
I'm a PSP hacker now, but I still <3 DS.
#126725 - tepples - Thu Apr 26, 2007 2:46 am
In general, moderators tend to remove links to a couple specific sites whose domain names contain "ethe" or "bate".
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#126734 - Dood77 - Thu Apr 26, 2007 5:27 am
Is Goatse illegal? xD
What I understood HyperHacker was that is if the website contains illegal material/instructions then its not to be linked to.
#126758 - chishm - Thu Apr 26, 2007 11:10 am
dantheman:
It's entirely possible that some SD cards don't like the initialisation process performed by my DLDI file. MoonShell's DLDI relies on the SuperCard firmware to do the initialisation procedure. There may well be cards that would work with my DLDI and not the MoonShell one, but you won't really notice this as the SuperCard wouldn't boot to a state where it could load homebrew patched with my DLDI.
If you can't confirm the info, you can add it under speculation/theories. It would help other people track down the problem in any case.
| HyperHacker wrote: |
| Could there be information about the devices (what features they have, how much they cost etc) as well? Perhaps information on similar systems like Lick's RAM library? |
Sure, just add them to the device's page, in a separate section (under a level 2 (==heading name==) heading).
| HyperHacker wrote: |
| chishm wrote: | | Users are not to link directly to illegal content, nor to a page that contains illegal content. Pages that are hosted on servers containing only legal content are of course linkable (just making this explicit). If a linked-to page is hosted on the same server as illegal content, and if the the page itself doesn't contain illegal content, and if there is no alternative source of information, then the page may also be linked. |
I'm not entirely clear on a few cases here, whether it would be a problem:
-linking to somewhere.com/files/coolhomebrew.nds, when somewhere.com/files/piraterom.nds also exists and directory listing is enabled (so users who try going to somewhere.com/files also see piraterom.nds)
-linking directly to a legal file on somewhere.com, when the site itself is piracy-related
-linking to a section of a site dealing with homebrew, when the site has other sections dealing with piracy
How strict are the rules about these? |
With these cases, I'd suggest you first try to find an alternate source, and only link to the pirate site if you have no other choice. Tainted knowledge is better than complete ignorance. As for the first case, I don't know of any homebrew authors that host illegal files alongside their projects.
Check the DLDIWiki Guidelines for the official rules.
Dood77:
That's covered under the rule on immoral content.
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com
#126767 - tepples - Thu Apr 26, 2007 1:13 pm
| chishm wrote: |
dantheman:
It's entirely possible that some SD cards don't like the initialisation process performed by my DLDI file. MoonShell's DLDI relies on the SuperCard firmware to do the initialisation procedure. There may well be cards that would work with my DLDI and not the MoonShell one, but you won't really notice this as the SuperCard wouldn't boot to a state where it could load homebrew patched with my DLDI. |
So it's the same situation as R4 in SLOT-1, right? Are you saying scsd_moon.dldi doesn't work if you yank the SuperCard, put in a GBA Game Pak, read its SRAM, yank the GBA Game Pak, put in the SuperCard, and call fatInitDefault()?
| chishm wrote: |
| HyperHacker wrote: | | chishm wrote: | | Users are not to link directly to illegal content, nor to a page that contains illegal content. |
I'm not entirely clear on a few cases here, whether it would be a problem:
-linking to somewhere.com/files/coolhomebrew.nds, when somewhere.com/files/piraterom.nds also exists and directory listing is enabled (so users who try going to somewhere.com/files also see piraterom.nds)
-linking directly to a legal file on somewhere.com, when the site itself is piracy-related
-linking to a section of a site dealing with homebrew, when the site has other sections dealing with piracy
How strict are the rules about these? |
With these cases, I'd suggest you first try to find an alternate source, and only link to the pirate site if you have no other choice. Tainted knowledge is better than complete ignorance. As for the first case, I don't know of any homebrew authors that host illegal files alongside their projects. |
Case 3 would hurt GeoCities and similar free shared hosting services, where all sites are under the same domain. Case 3 would also hurt sites that are protesting specific edge cases of the copyright statutes through civil disobedience, such as hosting some the oldest works of authorship that are subject to a copyright term extension (in the case of USA, those published in the year 1923; in the case of Australia, those whose last surviving author died in the year 1955).
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#126773 - chishm - Thu Apr 26, 2007 1:47 pm
| tepples wrote: |
| So it's the same situation as R4 in SLOT-1, right? Are you saying scsd_moon.dldi doesn't work if you yank the SuperCard, put in a GBA Game Pak, read its SRAM, yank the GBA Game Pak, put in the SuperCard, and call fatInitDefault()? |
Yes, it may be a similar situation, although I'm guessing the R4 also suffers the problem of the DS card interface not being initialised when it's inserted.
| tepples wrote: |
| Case 3 would hurt GeoCities and similar free shared hosting services, where all sites are under the same domain. Case 3 would also hurt sites that are protesting specific edge cases of the copyright statutes through civil disobedience, such as hosting some the oldest works of authorship that are subject to a copyright term extension (in the case of USA, those published in the year 1923; in the case of Australia, those whose last surviving author died in the year 1955). |
By "server" I mean a collection of pages and files all under the control of a person or group of people. I really do need a better word to describe this. Each homepage on GeoCities would be considered separately.
_________________
http://chishm.drunkencoders.com
http://dldi.drunkencoders.com
#126775 - Lynx - Thu Apr 26, 2007 1:57 pm
I think everyone gets the point.. He wants to have a clean, healthy envirnment to provide information that doesn't require an NC-17 rating to be able to visit. If you have problems understanding if your link should be posted, then don't post it. If you really think it is valuable to the wiki, PM Chishm or Tepples and they will let you know.
But, picking the rules apart isn't going to make it OK to post content we all know shouldn't be added. But, the "confusing" wording is there because I'm sure there will be a case that a warzer releases something that is valuable to the wiki and the rest of us shouldn't lose access to that information just because of the rules. And, there is a big difference between Geocities.com/DLDIPatch and warezwarezwarez.com/DLDIPatch
_________________
NDS Homebrew Roms & Reviews
#126817 - dantheman - Fri Apr 27, 2007 12:18 am
| tepples wrote: |
| So it's the same situation as R4 in SLOT-1, right? Are you saying scsd_moon.dldi doesn't work if you yank the SuperCard, put in a GBA Game Pak, read its SRAM, yank the GBA Game Pak, put in the SuperCard, and call fatInitDefault()? |
Well, reinserting a Supercard without having the DS reboot is a difficult task by itself. There's a method to prevent the reboot, but it's difficult and doesn't work all the time.
This may or may not be relevant, depending on my understanding of what you're saying: I used Chishm's cart save program on both of these cards, with interesting results. My first card worked fine with it the one time I was able to prevent a reboot when using it, and the save file was backed up correctly to the folder of my choice. It also worked on the second card that requires SCSD_moon, but in this case the filesystem did not appear. I could move the cursor up and down, but there was no text beside it. I simply hit B and it successfully created the savefile on the root of my card. I'm attempting to do it again now that I've patched the .gba file with the SCSD_moon.dldi file, but it keeps rebooting the DS on me.
EDIT: How interesting. I managed to get it to go back in without rebooting, but this time it froze before even getting to the file browser. I see "Press A to write save" and do so, but now thing responds.
Not sure what to make out of any of this though.
#126910 - HyperHacker - Sat Apr 28, 2007 12:38 am
| chishm wrote: |
| By "server" I mean a collection of pages and files all under the control of a person or group of people. I really do need a better word to describe this. Each homepage on GeoCities would be considered separately. |
Website or Domain might be the word you're looking for, depending on the situation.
_________________
I'm a PSP hacker now, but I still <3 DS.
#131751 - dantheman - Tue Jun 19, 2007 7:15 pm
It appears that the MMD and the MMP have slight differences that make the MMD DLDI file not work for some MMP users. Could someone upload the following DLDI file for the Max Media Player? (I have no clue what the source is, as I found it on a random website)
http://danthemanms.googlepages.com/mpds.dldi
That's what it was named when I found it.
#139477 - MechaBouncer - Thu Sep 06, 2007 6:16 pm
I wasn't sure where to ask this, so I'm reviving this topic. Do you need to request upload rights to add a new device? The reason I ask is because it recently came to my attention that the DLDI drivers listed for the Slot-1 CycloDS Evolution are actually for the Slot-2 CycloDS (Mini/Micro). I've made note of that on the CycloDS Evolution page in the DLDIwiki, but was not sure how to add a new device to the Slot-2 section to put the CycloDS (Mini/Micro) drivers there instead. I admit, I've never added a page to a wiki before, so I'm not entirely sure how. So what exactly is involved/required? Thanks.
_________________
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
#139501 - tepples - Thu Sep 06, 2007 9:21 pm
| MechaBouncer wrote: |
| I wasn't sure where to ask this, so I'm reviving this topic. Do you need to request upload rights to add a new device? |
Yes. First see upload.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#139506 - MechaBouncer - Thu Sep 06, 2007 10:02 pm
Ah, thanks for the info and for making that fix. I knew I had to put some kind of information there so that people didn't mistakingly use the wrong drivers by mistake.
_________________
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
#169798 - canapi - Tue Aug 04, 2009 10:29 am
Can anyone upload also the dldi device for iPlayer?
thanks
![[Images not permitted - Click here to view it]](http://www.thejunkyard.co.uk/ds/DLDIonly.png){kind=link}
![[Images not permitted - Click here to view it]](http://www.thejunkyard.co.uk/ds/DLDIandBack.png){kind=link}
![[Images not permitted - Click here to view it]](http://www.thejunkyard.co.uk/ds/DLDIandTop.png){kind=link}