Is it possible to boot roms from a pendrive with InfoNES? How?
|
|
|
|
Would you like to get all the new info from
PSX-Scene in your email each day?
Want to learn more about the team keeping you up to date with the latest scene news?
Read about them now! Check out our Developer bios, too! | ||
|
|
Is it possible to boot roms from a pendrive with InfoNES? How?
Sorry, but since no new versions have been released the mass: issue remains unchanged.
But if you need a NES emu that can use mass:, check out FCEU by ragnarok2040. This is a great NES emu which borrowed much of its interface and config code from uLE (with my blessings). So the config files are editable text, menu transitions are fluent, and when you tire of the emu you can exit to the boot program (norm uLE), just like SMS can.
The collaboration with ragnarok2040 is the main reason I didn't continue with infoNES, since FCEU in a very short time grew to surpass it in all ways.
Best regards: dlanor
Thanks! I've tested FCEU with bootsector's improvements
http://www.brunofreitas.com/portal/index.php?q=node/24
This is isn't specifically a question regarding mass: on Nes emulators, but I guess it fit's in here:
Neither Bootsector's updated emulators nor newer SMS versions (tested from 2.5 onwards) work with a pendrive of mine.
The pendrive works with ULE 3.79 as well as SMS 1.7 however. So, I'm wondering, was there some sort USB driver change, a change in the SDK, or something like that?
No it does NOT.
For an unrelated query you should always open a new thread, rather than hijack someone else's. So stay out of this one from now on.
Yes, probably hundreds, considering the incredibly ancient program versions you refer to. If you want any further discussion on USB with me, then you must first update to uLE v4.12. Then we can start talking (in a separate thread that time)Neither Bootsector's updated emulators nor newer SMS versions (tested from 2.5 onwards) work with a pendrive of mine.
The pendrive works with ULE 3.79 as well as SMS 1.7 however. So, I'm wondering, was there some sort USB driver change, a change in the SDK, or something like that?
| « Previous Thread | Next Thread » |