OS2 World Community Forum
OS/2, eCS & ArcaOS - Technical => Applications => Topic started by: Eugene Tucker on June 08, 2019, 08:03:35 pm
-
I cannot get the newest version of VLC to run.IN fact VLC would not run either on my system. And the issue is that several other apps will not run after trying to get VLC to run. Yes it is in my lib path and I have QT and the other dependencies installed.
-
Do you get an error if run from the cmd line?
-
No error just violation of the DosCall
-
No error just violation of the DosCall
In popuplog.os2 or a trp file? Either way, you should test on a newly booted system in case it is simply a shortage of memory issue and report to KOMH if it still won't run.
It does run fine here, unzipped to x:\vlc2.
-
I just downloaded it and tried it. I used the way I always have with VLC, put vlc.exe and icon in the lib dir and run it from there. It works but does give video distortion when I close a video, this could be because I haven't changed any of the settings which I may need to do.
Now to get sound working on this Ryzen machine and I should be happy.
-
I just downloaded it and tried it. I used the way I always have with VLC, put vlc.exe and icon in the lib dir and run it from there. It works but does give video distortion when I close a video, this could be because I haven't changed any of the settings which I may need to do.
Now to get sound working on this Ryzen machine and I should be happy.
Mine also would not start. Moved the vic.exe to the lib directory as you suggested and it is now working. Thanks!
-
Hmm...yeah, belly-up here as well, all I get is this:
06-08-2019 20:28:53 SYS3171 PID 01ba TID 0001 Slot 00fe
G:\APPS\MULTIMEDIA\VLC2\USR\LOCAL\BIN\VLC.EXE
c0000005
1ffba4ec
P1=00000001 P2=0012f770 P3=XXXXXXXX P4=XXXXXXXX
EAX=00150160 EBX=0012f76c ECX=001502c4 EDX=00000020
ESI=0012f7b0 EDI=0012f838
DS=0053 DSACC=f0f3 DSLIM=ffffffff
ES=0053 ESACC=f0f3 ESLIM=ffffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********
CS:EIP=005b:1ffb9e92 CSACC=f0df CSLIM=ffffffff
SS:ESP=0053:0014ffec SSACC=f0f3 SSLIM=ffffffff
EBP=0015002c FLG=00010202
DOSCALL1.DLL 0002:0000a4ec
I'll try a re-boot...FF has eaten up a boat-load of memory...so maybe that's not helping?
-
Are people not using a cmd file to start vlc? Here I use,
set BEGINLIBPATH=K:\vlc2\usr\local\lib;%BEGINLIBPATH%
vlc %1 %2 %3
which is located in K:\vlc2\usr\local\bin.
-
Are people not using a cmd file to start vlc? Here I use,
set BEGINLIBPATH=K:\vlc2\usr\local\lib;%BEGINLIBPATH%
vlc %1 %2 %3
which is located in K:\vlc2\usr\local\bin.
Thanks Dave for the cmd file. Works great.
-
Are people not using a cmd file to start vlc? Here I use,
set BEGINLIBPATH=K:\vlc2\usr\local\lib;%BEGINLIBPATH%
vlc %1 %2 %3
which is located in K:\vlc2\usr\local\bin.
I don't use any cmd file. I do put the vlc lib directory on the LIBPATH entry, and VLC runs fine.
To get sound, I select K Audio interface audio output and DART. To get video under Panorama, I select Video Mode=DIVE.
-
Are people not using a cmd file to start vlc? Here I use,
set BEGINLIBPATH=K:\vlc2\usr\local\lib;%BEGINLIBPATH%
vlc %1 %2 %3
which is located in K:\vlc2\usr\local\bin.
Yup, you bet I am:
SET BEGINLIBPATH=G:\apps\multimedia\vlc2\usr\local\lib;%BEGINLIBPATH%
G:\apps\multimedia\vlc2\usr\local\bin\vlc.exe %1
For my part, this became a FF issue...once the browser was down and memory released VLC was OK.
-
Dave is correct it is a memory allocation issue.
-
The QT dlls could be marked to load high, but then run into the zombie memory hole kernel bug unless something keeps them loaded.
-
The QT dlls could be marked to load high, but then run into the zombie memory hole kernel bug unless something keeps them loaded.
Makes me wonder if the OS4 programmers were able to overcome the zombie memory hole kernel bug.
-
The QT dlls could be marked to load high, but then run into the zombie memory hole kernel bug unless something keeps them loaded.
Makes me wonder if the OS4 programmers were able to overcome the zombie memory hole kernel bug.
They said so. Easy enough to test with Theseus.
-
The QT dlls could be marked to load high, but then run into the zombie memory hole kernel bug unless something keeps them loaded.
Hi Dave
Pls explain what do you mean by "zombie memory hole kernel bug" ?
-
Mark some DLLs such as xul.dll to load code high. open and close the app, Thunderbird in this example.
use Theseus to look at the shared memory summery, there will be a zombie hole the same size as xul.dll. Repeat and more holes appear.
Here's a screenshot, after closing TB and unloading the DLLs, 2 lines below the brwscmp entry there's still 0x03A13000 allocated, which is how much TB's xul.dll allocated. repeat and eventually the shared high memory area will be exhausted. There's other holes for the same reason.
Workaround is mozturbo to keep the DLLs loaded
-
Mark some DLLs such as xul.dll to load code high. open and close the app, Thunderbird in this example. use Theseus to look at the shared memory summery, there will be a zombie hole the same size as xul.dll.
Tnx Dave
Makes me wonder if the OS4 programmers were able to overcome the zombie memory hole kernel bug.
Hi David
This bug was fixed in OS/4 kernel long ago.