691
Applications / Re: OS/4 (technical details only)
« on: March 06, 2019, 02:38:23 am »
Still traps at the youtube page and still traps at avcode56, Attached trap file.
OS2World.com Forum is back !!!
Remember to visit OS2World at:
http://www.os2world.com
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.
David,OS2user, I am not that savvy with programs like this. I installed it, but don't know how to set it up or what I would use it for.
Do you have a WINx box on your LAN/network that you could try connecting to?
I just tried the SandyBridge version with the lastest OS/4 kernel and FF works now
try this http://hobbes.nmsu.edu/download/pub/incoming/freerdp-wpi-20190301.zip
it also requires AVX
Dave, I just tried the SandyBridge version with the lastest OS/4 kernel and FF works now. Don't know why it did not start before. Cannot test further since I am at work.
I take it you are using the AVX enabled build of the OS4 kernel. Is that bad web page now working for you with avcod56 and the Sandybridge Firefox?
If not I can build some test builds of FFmpeg this evening.
There's already one open about looking into the feasibility of adding AVX support to the IBM kernel, which you probably can't access. Not much there besides a description of the needed feature.
The problem is that during a context switch, the AVX registers need to be preserved. Those registers can be up to 512 bits wide. Think of what happens if two programs are using AVX when the OS switches between them. I doubt that we'll see AVX support in the official kernels anytime soon.
You may have hit on a bug in the OS4 kernel, at least OS4USER is aware of your crash.
Would still be interesting to know what function was crashing in libavcodec though I wouldn't be surprised if something just wasn't aligned correctly. Interesting that the AVX enabled Firefox didn't run for you as well. Did it generate a trp?
Exceptq could also use an update to correctly disassemble AVX opcodes. Luckily Lars can spot them.
PS- I posted another graphic of the CPU cabilities (feature flags) above at reply #55.
Yes, it seems to be incomplete, only showing up to SSE2.
Hmm, looking at Intel's site, it does seem to support AVX, which is what I was wondering.
Hi David, that crash looks like one I get now and again, I believe font related.
Have you tested with the Firefox build that OS4USER mentioned?
I made a quick and dirty PMChart PNG icon.In general, does the full file name of those PNG files matter when the user or the system has to assign it to a WPS object?
Compared with the *.ICO equivalent (e.g. HELLO.ICO being a default icon for a HELLO.EXE in the same directory), that is.
I just installed the noAVX kernel and my traps have disappeared.
P.S.
It was suggested by BWW to remove libc-debug 0.6.6-40 and install libc-debuginfo instead of it.
Looking at it again:
If it is true that all SSE/AVX code in AVCODE56.DLL is handwritten in assembler then I suspect either one of 2 possibilities:
....
To Lars:
What you saying is quite possible. One more way to check it - is test OS/4 kernel without AVX support.
To David:
Pls, open your site on this test kernel http://gus.biysk.ru/os4/os4krnl_noAVX.zip
Thanks to both Daves: Graser and Yeo. And everyone else.
The unpack (Yeo) and creating directories (Graser) were what I needed.
I have attached a zip file with the app files - arranged in a directory structure that more closely matches AOS and ECS. And as Dave Graser said, it appears to work. I will also upload this in the next couple of days to Hobbes.