Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Jochen Schäfer

Pages: [1] 2 3 ... 10
1
Games / Re: PrBoom+
« on: June 07, 2021, 09:35:37 am »
IIRC, in the original DOS DOOM there was no mouse support. So possibly the addons can be not well tested.
I will look into it.

2
Games / Re: PrBoom+
« on: June 06, 2021, 08:49:47 pm »
The mouse is fine. In Doom, you can't look up or down. It's a limit of the engine.

@Martin: I don't know, what the problem is. Since I needed some bugfixes in SDL2 and SDL-Mixer is officially still missing, I linked them all statically. The SDL2 requirement comes from SDL-Image, which is linked as a DLL. I never had any problem with the Timidity patches.

3
Games / Re: PrBoom+
« on: June 06, 2021, 08:57:17 am »
Hi Jochen,

  If I start pmboom-plus.exe by itself, my system locks solid and I have to do a hard reset. If I start the server, then run pmboom-plus.exe, it works fine. So this is not correct? Is there a way to enable some logs?

Regards,
That is really strange behaviour. Can you tell me which video and audio drivers, you use?
When you start PrBoom+ without the server, is it really a hack lock or does it only seem so, because the fullscreen window is blocking everything?
Does ALT+ENTER still work? Do you hear sound?
PrBoom is really talkative on startup, so you can redirect the output to a file and look for clues. Also, you could try to start with "-window".

Bye Jochen

4
Games / Re: PrBoom+
« on: June 06, 2021, 08:51:09 am »
Hi

I'm trying it out, it works on my side, I'm trying to understand how the keys are mapped, up and down arrows keys does not goes forward or backward, W and S does that.
Hi Martin.

Good to hear, it's working for you. PrBoom updated the keyboard mapping to more modern standard (i.e. WASD), but you should be able to change them somewhere in the options.

5
Games / Re: PrBoom+
« on: June 05, 2021, 10:12:04 pm »
Thanks Jochen! It seems to work great here (once I realized you have to start the server first). And KMidi and Timidity work fine together... KMidi will be the default, but if you right-click on a *.mid file, and choose 'Open as..', then you should have Timidity++Player as a choice in the drop-down list.

Regards,
Actually, you only need to start prboom-plus.exe to play a single player game. The server should only be needed, when playing a multiplayer game. What problem are you having when starting without the server?

Regarding Timidity: SDL-Mixer is used for sound generation, which uses Timidity code for MIDI playback. So the Timidity application is not used.

6
Games / PrBoom+
« on: June 05, 2021, 03:28:07 pm »
Hi guys.

I have ported PrBoom+, which is a source port of DOOM, running on SDL2.
I have put a prereleases package on my Github repo here: https://github.com/josch1710/prboom-plus/releases/tag/v2.6um-alpha1
In the archive, you find the two binaries for the game and the multiplayer server, as well as prboom.wad and the shareware version of Doom.
If you have the original DOOM games, you can put the WADs in the program directory or under /@unixroot/usr/(local/)share/(games/)doom.
If you want the midi to play, you need to download the timidity patches from here: https://www.libsdl.org/projects/SDL_mixer/timidity/timidity.tar.gz and install them in /@unixroot/usr/(local/)share/timidity.

My plan is to submit all my bugfixes for SDL/2 and patches for PrBoom+ in the next days.
After that I want to package everything for easier installation.



Enjoy!

7
Applications / Re: OpenSource WishList
« on: January 20, 2021, 12:34:08 pm »
I would like to see KDevelop or something similar.

8
Multimedia / Re: Updated Uniaud32 build
« on: January 12, 2021, 02:24:52 pm »
I tried uniaud32-linux-5.10.5-20210108.zip on an Yoga 11e (1st gen) and now I have no stutters anymore, volume control works and Dosbox makes noise again.
Good job, Paul.

PS: I will also test the test builds on a T420.

9
Article Discussions / Re: OS/2 - ArcaOS 64Bits Kernel Discussion
« on: December 11, 2020, 09:46:56 am »
Physical addresses under OS/2 are also limited to 32-bit. Which means your approach of "4 GB of physical memory per core" cannot work.
I remember, reading that the 64bit Darwin kernel always presents 32bit software with a 4 GB address space of its own. It does this via virtual addressing. This could be a way to go for OS/2, I think.

10
Article Discussions / Re: OS/2 - ArcaOS 64Bits Kernel Discussion
« on: December 11, 2020, 09:42:36 am »
And 64-bit is a hoax. I have a W10 64-bit from work, everything is bigger [..]
That's not a hoax, it is to be expected. If you want to address 64bit instead of 32bit, you need a bigger pointer. Most C/C++ compilers will make their types bigger, e.g. int going from 32bit to 64bit, so the data grows.  Everything grows, if you switch word size (32bit vs. 64bit). It was like that with the translation from 8bit to 16bit, then from 16bit to 32bit.
So, in a nutshell: Making your word size bigger, makes your executables and your data bigger. That's the downside for getting a so much bigger address space.

11
Programming / Re: Compile under ArcaOS
« on: November 24, 2020, 09:44:48 am »
Should almost never need -Zexe now a days. Last time I used it was for testing building something that only had a makefile. When it worked I fixed the makefile to use $exeext which on OS/2 was set to .exe, eg foo$(exeext)
Autoconf on OS/2 will set $exeext correctly and for configure scripts created somewhere else, export exeext=.exe in the environment (I prefer config.site) will add the .exe suffix.
Yes, you are correct, if it's a autoconf system. Otherwise, you have to add -Zexe, which does not hurt anyway ;-)

12
Programming / Re: Compile under ArcaOS
« on: November 23, 2020, 10:00:27 am »
I'd like to add to Dave's comment about -Zomf, that sometimes -Zexe is required, especially on configure scripts, because they sometimes assume, that you are a Unix box and so have no exe extension. -Zexe appends .exe, if it is not given as part of the -o outfile.

13
Applications / Re: Windows 95 in DOSBox/2
« on: November 19, 2020, 07:48:00 pm »
I did some tests on Linux with an version of Dosbox installed through the package system and the newest source code compilation. With the packaged version, Windows 95 boots and with the newest one, it does not.
Interesting enough, the FreeDOS works with both versions.

I think, we have a regression here. I will try to issue an bug report.

14
Applications / Re: Windows 95 in DOSBox/2
« on: November 13, 2020, 10:13:46 pm »
I could boot from a FreeDOS boot disk. So, I guess, the boot in itself should work.
Until now, I couldn't figure out why the Windows 95 boot image doesn't work. It seems, that the image is not mounted anymore after boot.
The missing os message comes form the bootsector of the image.

15
Applications / Re: Windows 95 in DOSBox/2
« on: November 11, 2020, 01:48:46 pm »
Damn it. I knew, I'd miss something.
Thanks Paul.

EDIT: It worked.

Pages: [1] 2 3 ... 10