While I tend to not like people asking like this, a tutorial would be really nice. I basically have a ton of files, and no clue how to configure them.how about a fucking tutorial!!!!
While I tend to not like people asking like this, a tutorial would be really nice. I basically have a ton of files, and no clue how to configure them.how about a fucking tutorial!!!!
I did call it W95.IMG.exe but, it didn't load... then I take off the exe, and it can't load disk image files...
--------------------- MERGED ---------------------------
how about a fucking tutorial!!!!
Only Arrow keys for games are working currently afaik...now... how do I use the controls for it?
@Team Fail I said I was sorry...got it!!! thank you... sorry I exploded all over the place...
It's just RetroArch, so no. You're controlling DOS/Windows with whatever buttons you can manage to map in RetroArch's input mapping screen. Even then, input seems a bit iffy, some software behaves as if up+left are being held constantly. It's an interesting proof of concept, but you won't have much fun yet.So my original question, is there an on screen keyboard for this?
or a better question is: how can I make the A button the enter button?A new problem is on the horizon.... please help me defeat it!
Nope, it's not working. I've tried the .3dsx, cia, and .3ds and none boot.So... no o3DS?
Aww ok thanksNope, it's not working. I've tried the .3dsx, cia, and .3ds and none boot.
I think he'd be better off waiting until he can see why it doesn't boot on O3DS systems. It works on N3DS, but O3DS just completely dies, unfortunately. I think a requirement of the nightly builds is that it works on both systems regardless of performance.Nice job. You might want to submit your changes as a pull request to the dosbox-libretro repository, see if you can get it added to the official nightly builds.
From what I've heard, some of the nightlies don't work on either system right now.I think he'd be better off waiting until he can see why it doesn't boot on O3DS systems. It works on N3DS, but O3DS just completely dies, unfortunately. I think a requirement of the nightly builds is that it works on both systems regardless of performance.
if you're talking about the "No Core" issue, that was solved some time ago. other than that, it's been working fine on my systems so far.From what I've heard, some of the nightlies don't work on either system right now.
However, it does make sense to see why it doesn't work on O3DS first, I suppose.
Nah, it just doesn't boot at all. Nothing is printed to the screen, it just blackscreens, or if it's the 3dsx, it just has garbage on the screen and nothing happens.if you're talking about the "No Core" issue, that was solved some time ago. other than that, it's been working fine on my systems so far.
that's weird...I've not gotten that issue unless it happened within the past day or so. I use the .3dsx on new, and .cia on oldNah, it just doesn't boot at all. Nothing is printed to the screen, it just blackscreens, or if it's the 3dsx, it just has garbage on the screen and nothing happens.