Latest DOSBOX : with PPC dynamic recompiler and stuff , right there!

@samo
Yes, i check all the things he mention and whole diff he provide.

1. Activated C_CORE_INLINE : that one activated in my build by default
2. paging.h fixed : now we use dynamic core, those fixes not fits anymore (and probabaly have no needs).
3. there was some changes in mem.h back in years with inline ppc asm, but tests showsm that latest dosbox ones + endian fixes i applied when add dynamic core are faster and better.
4. fix in render.h make things with dynamic core is MUCH SLOWER than without.

and so on.

Quote:

Yes of course, i always use window mode. In the config file i have:

fullscreen=false
fulldouble=false
fullresolution=1920x1080
windowresolution=original


also double-triple check that you didn't have "fullscreen=true" anywhere in the config file.

@kas1e

Ok in dosbox config i have:

fullscreen=true
fulldouble=true
fullresolution=original
windowresolution=original

DOSBox indeed now start by default in fullscreen as it should
And/Or in window mode if fullscreen and fulldouble are set to "false"

But in RunInDOSBox.config (that pratically it have the same variable configuration of dosbox.config) it doesn't ...

As RunInDOSBox will runs exe directly instead of just DOSBox alone, probably the mechanism was studied to always open things in fullscreen by default ...

@kas1e

man this new version is at least 3 times faster than old one !

here's a few of test results using all full screen using RunInDOSBOX on my X1000:

Chris's Benchmark score- 19.1
3DBench 1.0- 55.4FPS
3DBench 1.0c- 55.2 FPS
TopBench 3.0- 449
PCPlayer Benchmark- 18.2
Quake time demo- 12.6 FPS
Quake time demo 640x480- 4.3 FPS
Doom max details time demo- 2134 gametics, 2616 realtics

@kas1e

Quote:

Yes timedemo demo1, new DOSBox 9.7fps, old version 2.7fps.


BTW
Have you tried installing Windows 95? I tried, but unfortunately the command to create filepartition - imgmake does not work.
I can't mount blank filepartition file downloaded from the internet.

To the extremes and beyond...

Anyone tried Linux on it yet?

https://www.reddit.com/r/linux/comment ... lld/linux_for_486_laptop/
https://itsfoss.com/lightweight-linux-beginners/
http://yeokhengmeng.com/2018/01/make-the-486-great-again/

@Mufa
Quote:

That the next thing i want to try. I already tried to download some "img" files from intertent , and they mounts for sure fine. For example i have some "95.img" file of 536mb of size, which i mount just like this :

imgmount d 95.img -t hdd -fs fat -size 512,63,16,600

And there is (press open in new tab for fullscreen):



See its 527mb img file. I can upload somewhere that empty img file. Its in fat16

@kas1e

WELL. If you can complete the installation of Windows 95, please complete the tutorial.

@Mufa
(press open in new tab for fullsize):

.

That with working SB16 and S3 Trio drivers (desktop on screenshot 1024x768x256).

The only issue that it _didn't_ work with JIT. It only works with cpu type "NORMAL", so, not very fast. Also it pretty crashy. I mean offten. Dosbox authors says that win95 support is out of their skope, so if it works, good, if it not , sorry :)

Through that the version i got from internet (some .img) file , will try to install my own one, maybe it will be better.

@kas1e

Win98 would be interesting to test into

@all
There is an archive which I want to upload to os4depot:

http://kas1e.mikendezign.com/aos4/dosbox/dosbox.lha

If someone has some time, give it a go that it works, etc.

In this version in comparison with the one I upload early all builds with -O3 instead of -O2, also link it against the very latest SDL2 where pthread dependency removed and native os4 threads added (Capehill for president!), and also this SDL2 is non-debug one in comparison with one used early. So things can be a bit faster there and there.

Also in an archive, old DOSBox port by Corto included (the whole archive, in directory "old", just in case someone may need it someday)

Tomorrow I want to upload it to os4depot, so if someone can give a little check (just like replacing binary in your DOSBox setup) that will be good.

Thanks!

@kas1e

Just had a quick look and noted some cosmetics:

1 - The black icon of the main folder is missed compared to the Corto archive .. imho it's very nice and you can reuse it

2 - Same for the icons of "dosbox.config" and the "C" folder .. that are nice and could be reused aswell

3 - Is it possible to add an informative version related to the binary release ?
Something like:

#if defined(__amigaos4__ )
char ver[] = "\0$VER: DOSBox SVN (xx.xx.2020)";
#endif

@kas1e

Ok tested, this version crash always at startup
(tested with both RunInDosBox and/or just starting dosbox standalone)

---------
Crash log for task "DOSBox"
Generated by GrimReaper 53.19
Crash occured in module DOSBox at address 0x6F8E6B58
Type of crash: DSI (Data Storage Interrupt) exception
Alert number: 0x80000003

Register dump:
GPR (General Purpose Registers):
0: 6F8E6B38 54582710 00000000 00000000 00000000 00000001 00000000 17637C60
8: 00000001 00000000 5666115F 00000004 2A422444 588EE1A0 58A8A530 58984340
16: 6F7942B0 00000000 00000000 00350019 02280000 54D16650 00000000 00000000
24: 53E006B4 00000000 57FD03CC 6F8AFDC8 51F8D8A0 51F8D560 54A69F0C 56661140


FPR (Floating Point Registers, NaN = Not a Number):
0: nan nan 325 0
4: 0 649.8 30.8 0
8: 0 4.5036e+15 649.8 54.9254
12: 4.5036e+15 356 0 -0
16: 1.32625e-315 0 0 0
20: 0 0 0 1.61895e-319
24: 0 0 2.65249e-315 0
28: 0 1.35808e-312 1.3581e-312 -0.25

FPSCR (Floating Point Status and Control Register): 0x82000000


SPRs (Special Purpose Registers):
Machine State (msr) : 0x0002F030
Condition (cr) : 0x52114DA0
Instruction Pointer (ip) : 0x6F8E6B58
Xtended Exception (xer) : 0x018233AC
Count (ctr) : 0x00000000
Link (lr) : 0x00000000
DSI Status (dsisr) : 0x01842B34
Data Address (dar) : 0x00000000



680x0 emulated registers:
DATA: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
FPU0: 0 0 0 0
FPU4: 0 0 0 0



Symbol info:
Instruction pointer 0x6F8E6B58 belongs to module "DOSBox" (HUNK/Kickstart)

Stack trace:
module DOSBox at 0x6F8E6B58 (section 5 @ 0x2AAB34)
module DOSBox at 0x6F8E6B38 (section 5 @ 0x2AAB14)
module DOSBox at 0x6F8B220C (section 5 @ 0x2761E8)
module DOSBox at 0x6F749EDC (section 5 @ 0x10DEB8)
module DOSBox at 0x6F876C48 (section 5 @ 0x23AC24)
module DOSBox at 0x6F79485C (section 5 @ 0x158838)
native kernel module newlib.library.kmod+0x000020ac
native kernel module newlib.library.kmod+0x00002d5c
native kernel module newlib.library.kmod+0x00002ef0
DOSBox:_start()+0x170 (section 1 @ 0x1920)
native kernel module dos.library.kmod+0x000255c8
native kernel module kernel+0x0003e7b4
native kernel module kernel+0x0003e7fc

PPC disassembly:
6f8e6b50: 831e8004 lwz r24,-32764(r30)
6f8e6b54: 7d234b78 mr r3,r9
*6f8e6b58: 8129005c lwz r9,92(r9)
6f8e6b5c: 92c10108 stw r22,264(r1)
6f8e6b60: 93210114 stw r25,276(r1)

System information:

CPU
Model: AMCC PPC440EP V1.3
CPU speed: 799 MHz
FSB speed: 133 MHz
Extensions:

Machine
Machine name: Sam440EP
Memory: 1048576 KB
Extensions: bus.pci

I also found a small problem.
If video is not scaled (scaler = none), then lo-res mode is not centered in fullscreen mode.

@samo
Icons stuff is of no interest for me currently, its fine as it. I done it all as it specially for reassons.

But crash.. Are you 100% sure you do everything correctly this time and i will not loose time on your issues because of bad check ?

What i mean, is you 100% sure that previous version in that thread work, and you "just replace the binary" from new one and it crashes on startup and previous one not ? Recheck it plz twice. Crash is null-pointer, so dunno what can cause it.

Only difference is new SDL2 with no debug , usage of native threads in , and -O3.

@Mufa
Its the same for both version ? Previous one uploaded and last one ?

Anyway issues core of dosbox itself also probably will be as it, as it up to dosbox authors.

And new version didn't crash for you on startup, all fine, right ?

@kas1e

Quote:

Well, as you said you wanted to release shortly i just checked the archive and pointed out what was missed, in that case part of the old iconset was not included...

Quote:

Yes, i tried everyhing, copying the binary over the old one, and even reinstalling everything from scratch ,, same crash .. no luck
As soon as i double click into the icon i can see the dosbox window opening until it show its dosbox logo, then it crash instantanely

Maybe the new threads implementation of SDL2 could be to blame ?
or the -O3 optim ?

Pls try compile a test binary with -O2,

@kas1e

Quote:

Yes Your last and previous version the same problem:

















Old Corto Version no problem:

@samo79
There is new test bins:
http://kas1e.mikendezign.com/aos4/dosbox/samo_bins.zip

Inside 2 bins compiled with -O2, one with new SDL2 with native threads, and another one older SDL2 with pthreads, compiled with -O2 as well. Check it plz.


@mufa
Will check, that can be also and not DOSBox itself, but due to SDL2 migrate, or SDL2 itself , we can it sort later. At moment want to make some release which works while dealing with other things.

There is another issue which i dont like : switching to/from window/fullscreen via alt+enter feels a bit buggy. I.e. when you switch from window to fullscreen, its like "alt" is pressed anyway, and didn't realised, so pressing pure "enter" will switch to window back, and so on, until you didn't make the window be inactive and then active. Dunno if it SDL2 migrate or SDL2 itself, that also to be seen later. Or maybe DOSBox's code itself.

@kas1e:

Test with the -O3 bin and it crashed on start when in the config "nosound=false" is set. With "nosound=true" it works.

EDIT:

Test the samo bins. The dosbox_O2_SDL2_pthreads works with "nosound=false" the dosbox_O2_SDL2_native_threads crashed.

EDIT2: tested on AmigaOneX1000

@TearsOfMe

So.. that mean that native threads by some unluck crashes. And now when you say about "nosound=false" it somehow related to the audio-threads probabaly (as natively there audio and timer now), which emulated by should be silent.

Through, it didn't explain why it didn't crashes on my setup. But its again x5000, with more up2date components (as in case with Mufa too), so maybe its again something somewhere about dos.library must be opened or of that sort.

In other words, will use pthread version of SDL then for now, and check with Capehill later wtf.

Thanks for tests!

On X1000 I don't have any problems with sound or crashed, neither with yesterday's version nor with today's builds.