Hello fishbone,

I uploaded the whole directory for you, get it here.
It also contains the version of Julian.
The last time I tried to debug it, I managed to make the prompt works but, for some reason, every time I type a character it adds an extra space.
I still don't know why it doesn't work, it could come from my backend or how DOSBox handles dynrec in big endian architecture (or both), if someone modifies dynrec, let me know I could try again.
Good luck. 😀

Hi,
thank you for the upload.
your response has confused me a little bit: since the previous upload was located on the epitech-server, i assumed a connection between the epitech-port of dosbox-wii and your file. i thought you're one of the authors, and assumed that you already got the dynarec working.

that "epitech"-port already sets core in dosbox.conf to dynamic and the authors state that it's faster than tantric's version. atm i experienced tantric's version being faster without using the dynamic recompiler, so i assumed that he did some other optimizations.
my idea was to merge the dynarec with tantric's project to get maximum speed.

until now i tried three things:
1. merging your older upload with tantric's version -> dosbox crashes immediately due to a segmentation fault
2. (today) building your source code -> after starting dosbox, the screen stays black
3. (today) merging your newer dynarec upload with tantric's version ->
A) after the first start i could see a mouse cursor, then dosbox immediately returns to the homebrew channel
B) after the second start dosbox crashed immediately (same behaviour like 1. )

note that i built your sourcecode with the release-makefile, because i don't own a usb-gecko, so i can't use gdb (i'll try using gdb over network)

maybe, you have an idea why i only get a black screen?

fishbone

Hello,

You are right about the "epitech"-port (even if I dislike this term, it's just a port on wii 😀).
But this version was faster than the old tantric's version (because we used gcc4 earlier) since they recompiled dosbox using the last version of devkitpro they got a faster version.
About the dynrec, it still doesn't work : wd told me that it could be a big endian issue in dynrec, as I said I tried to debug it (using a usb gecko) but no result.

About the blackscreen, I have no idea, do you use the latest devkitpro ? And make sure debug feature are disabled.

hi,

yes, i have the latest devkitpro version. maybe the config-filename is wrong or it is in the wrong directory...

why does your port (binaries provided by the homebrew-community) work, although core is set to dynamic? that makes absolutely no sense to me, because the binaries are working just fine on my wii. the only issue is that the zero-key doesn't work.

Hi fishbone,

Actually we(my teammate and myself) work on this port as a school project and for the final defense we release a working version.
I keep the version that I uploaded in order to make the dynrec working (but I failed).

By "zero-key" you mean the virtual keyboard ?

hi,

Actually we(my teammate and myself) work on this port as a school project and for the final defense we release a working version.

sorry, i can't understand the meaning of this sentence 😉 what do you mean with "final defense"?

so i still don't know why

1core=dynamic

in dosbox.conf although you're stating that the dynarec doesn't work.

i mean the "0"-key on my usb-keyboard. (however, this is not a real problem: if i need a "0" i type alt+(num4,num8) )[/quote]

Hello,

By "final defense" I mean we had to introduce this project to examiners in order to be evaluated.
About the core=dynrec, well if it's written on the source code I uploaded it's for testing purpose, else I don't remember why.

dosbox-wii.conf (binary-package from homebrew-community, named dosbox_epitech.rar):

1[cpu]
2# core -- CPU Core used in emulation: normal,simple.
3# cycles -- Amount of instructions DOSBox tries to emulate each millisecond.
4#           Setting this value too high results in sound dropouts and lags.
5#           You can also let DOSBox guess the correct value by setting it to max.
6#           The default setting (auto) switches to max if appropriate.
7# cycleup   -- Amount of cycles to increase/decrease with keycombo.
8# cycledown    Setting it lower than 100 will be a percentage.
9
10core=dynamic
11cputype=auto
12cycles=max
13cycleup=500
14cycledown=20

to use the dynrec you have to set core=dynamic. now i think i know what's going on here: dosbox was built without dynrec, so dosbox automatically switches back to core=normal if core==dynamic.