Search

[bigfootale]

I have a SC SD and Flashme installed on my v2 DS, and have used NDSPatcher.exe and the SC app to patch NDS roms but get nothing but whitescreens.  I have searched many forums for research but find nothing that addresses this problem.  I am using Nintendogs as my DS cart inserted, as I can't find my Metroid demo cart, which may be the problem.  Can anyone point me to a thread that will help me, or confirm that Nintendogs can't be used as the NDS cart?  Thanks in advance.

[ratx]

Nintendogs works fine as a boot cart. Can you confirm you're using the latest SC patcher and kernel software? ( You can find out the kernel version by booting into GBA mode and holding L+R, then pressing A a few times )

Also have you tried booting any Homebrew?

[cory1492]

Make sure you are using the correct patch for your card, that you can double click on the nds file in the supercard patcher and see the correct options for SD or CF, depending on which one you have.

Also look into a checker like offlinelist, nintenren or real auditor (there are others too) to be sure your ROM files are clean and good, and arent prepatched like GST ones or something else like non-proper'd releases.

Also, just so you know in case you test what ratx suggests, to use homebrew you must get the .ds.gba file and rename it to .nds for it to run right from the supercard, no patching required.

[WarGames]

Okay, this is something that I don't necessarily understand completely.   But from my experience, you will always get white screens if you try to boot a game without the passme inserted,

or, Importantly, if its flashed like yours, you need to press A+B+X+Y during the booting process!

I have a v1 flashed silver nintendo ds, and when i write homebrew code i dont need to convert it to nds.gba, i simply run the code binary files with ndstool and play that .nds file off of my supercard.

Ive had my problems with the DS and all but that hasnt been one of the things ive needed to do.  I've always used the patcher for roms, and running flashme.nds also worked fine.  What do these .gba files do, ive heard it makes the software run off the gba slot (by patching certain code probably), but mine does it anyway without using DSbuild or any tool like it so its hard for me to see the validity of the tool, maybe someone could compare it to how the Supercard Patcher software works.

peace guys

[cory1492]

:lol:  you obviously havent subscribed to the devkitARM mailout list - if you come across any odd problems like variables getting initialized weird and stuff not doing what its supposed to with the supercard - its because of the way the ndstool header loader works; it doesnt play well with supercard and the dsbuild loader added fixes it up. The guy who was doing the python port figured out it was because the ndsloader wasnt attached; even though it runs on supercard, the loader that is in the logo code in the nds header does it differently.

At any rate, I was suggesting to finda nds.gba homebrew file, and dont do any patching to it except the name, and try it on the supercard to see if it runs and is just their method of patching that is at fault. They are more likely to find many nds.gba than they are to find a new .nds build that will try to autoload (and besides, how are they to know this stuff, considering the problem)