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 - Dariusz Piatkowski

Pages: 1 ... 64 65 [66] 67 68 ... 89
976
Hey TC,

...The system has 2 drives in it and OS/2 Warp v4 (14.062_W4) is installed on a SCSI drive. That drive has other OSes on it and Partition Magic's Boot Magic controls what boots...

I think Dave is right on the money, OS/2 is probably getting confused about the drives and what drive letters are being assigned to them.

Here is another suggestion, I think this should work since the functionality I am about to describe was introduced with Warp4. Using the LVM manager you will be able to assign a drive letter to a disk partition. Now, there have always been problems between OS/2 and other OSes, mostly Windows stuff, where the OS/2 assignments would occasionally get messed up. Still, on my machine I have a total of 3 drives, with multiple partitions each...regardless, my OS/2 boot partition is drive G:\, works without any problems. Once assigned, that letter never goes away from within OS/2...so if you flag a partition as C:\, it will remain that within OS/2.

Be carefull of course, the last thing you want to do is to completely lock yourself out...having a maintenance boot partition goes a long way to helping out with such issues though.

977
Applications / Re: File Open dialog not resizable?
« on: March 07, 2018, 06:15:49 pm »
Hi Eugene,

...2) File Open Container is activated by default in ArcaOS
and can be activated in eComStation 2.x http://en.os2.guru/projects/foc/?action=faq...

What about non eCS or AOS installs? In my case, a Warp 4.52 (CP2 over Warp4 + SMP) base OS?

I have the runtime installed (Win, Net & Base) but focdlg is nowhere to be found...is that a AOS thing maybe, or do I also need to install WPS, given that it contains the WPFolderEx class?

I like the functionality this offers, and as you use a lot of the FOD/FOC it certainly would make "life" easier!!!

978
I would second Roderick's suggestion...narrow things down to a single active CPU, go from there.

Depending on some of the remaining hardware drivers you may be seeing a lock early on (display showing stuff) but the root cause maybe something else.

As I experimented with getting SMP installed on my AMD Phenom II X6 I found that running more than 5 cores would result in the WPS blue-screen hang, but that was a somewhat well known issue with SNAP video drivers not being quite SMP ready.

For my part I am very curious how you work through this issue, please continue to post updates. The Ryzen CPU is my next upgrade, probably Ryzen2 actually, still some time left.

979
Applications / Re: File Open dialog not resizable?
« on: March 07, 2018, 12:23:40 am »
Doug,
Sorry no idea, but I'm curious which part of AOS provides the modified dialogue window?

Is this by any chance the set of modules from the ECO-runtime series?

980
Comments, Suggestions & Questions / Re: Censorship complaints
« on: February 26, 2018, 01:28:49 am »
Hmmm...what did I miss??? :o Or, if I had read it, and was not appalled, does that make me the next "marked man"? LOL

OK, seriously, I have no idea which thread caused this. But...Andreas can be to-the-point, and as someone who can do the same I account for that level of directness across various posts on our forum, and it certainly hold true for a number of individuals. It does not ruffle my feathers, and if anything does I state my point to let the person know.

I guess I am thinking that sure, it behooves us all to try to remain civil, but you can not demand the un-natural level of civility where the perhaps obvious "wrong" goes un-called out and we all politely pretend like it didn't happen. I would much rather see some angry words to trully understand a person's point of view, rather than assume things and be left at the mercy of my (perhaps?) flawed interpretation.

So given the nearly morbid level of OS/2 growth (let's face it, not like we have a wildfire going on here... ::)) should we not all just become a little more relaxed instead?

981
Thanks for the wealth of info Dave.

Alright, I've started going through the EMX stuff, find it a bit confusing though why we are still looking at EMX stuff given how old that specific port is in light of the fact that I thought we were moving towards gcc and the migration of the Linux GNU type stuff to our platform, and therefore the replication of how things are done there. So should it not all come down to : one or the other?

OK...more reading, maybe somewhere in there lies the answer.

Now, regarding the '-pthread' and -lpthread' options. So I was using the '-pthread' as the GCC option because by design once the compiler sees the thread support enabled it is supposed to pass that parameter to the linker, and as such, it effectively creates the '-lpthread' parameter. Maybe the problem is that in my output of the gcc run I do not actually find the '-lpthread' showing...???

Anways, OK, thank you again...off I go to do some more reading...lol

982
Networking / Re: RTL8211CL DRIVER
« on: February 25, 2018, 05:33:55 pm »
...I seem to recall a recent discussion about this... found it. Have a read https://www.os2world.com/forum/index.php/topic,1519.0.html...

Thanks Pete...yup, it was a great move to fix the SMP hang, but with the performance being so bad I found that it just did not work for me. Strangely the ticket I logged has simply gone un-answered (https://mantis.arcanoae.com/view.php?id=1505).

983
Programming / GCC - proper include files and libraries, what's the method?
« on: February 23, 2018, 03:24:12 am »
Alright..another installment on my "continuing mission to boldly go where with OS/2 coding where I have not gone before"...LOL, this time all about the CORRECT include files!!!

So I have the following on my machine (things that are specific to GCC):

1) RPM packages for:
- gcc.pentium4                                4.9.2.1-3.oc00           installed
- libgcc-fwd.pentium4                         4.9.2.1-3.oc00           installed
- libgcc1.pentium4                            4.9.2.1-3.oc00           installed
- pthread.i686                           20151229-21.oc00              installed
- pthread-devel.i686                     20151229-21.oc00              installed
- pthread-legacy.i686                    20151229-21.oc00              installed

2) OS/2 Warp Toolkit

3) IBMCPP 3.6.5

All of the above have their own include files. So given that I'm trying to learn how GCC itself is structured and what it actually uses on the local machine, I rule out #2 & #3 (gcc session has no visibility to these) I am struggling to understand why the very same include file (there are multiples) occur in several places, take stdio.h as an example.

Just in the RPM based \usr\ tree I find the following:

Code: [Select]
[G:\usr]dir stdio.h /s

Directory of G:\usr\include
10-26-14   2:17p     19624         124  stdio.h
        1 file(s)      19624 bytes used

Directory of G:\usr\include\c++\4.9.2\tr1
 2-01-15   2:07p      1209         124  stdio.h
        1 file(s)       1209 bytes used

Directory of G:\usr\lib\gcc\i386-pc-os2-emx\4.9.2\include\ssp
 2-01-15   2:08p      3473         124  stdio.h
        1 file(s)       3473 bytes used

Directory of G:\usr\lib\gcc\i386-pc-os2-emx\4.9.2\include-fixed
 2-01-15  12:34p     20124         124  stdio.h
        1 file(s)      20124 bytes used
Total files listed:
        4 file(s)         44430 bytes used
                   4100499 K bytes free

...what the heck? So why these multiple occurencies?

Also, I note that as RPM installed the pthread.i686 package (to support the -pthread gcc option) it put the pthread.h into \usr\include.

So that is Q1, the second issue might be related to this, not sure, and is as follows: attempting to compile thread enabled CPU benchmark causes my GCC session to fail with the following:

Code: [Select]
COLLECT_GCC=gcc
Target: i386-pc-os2-emx
Configured with: ../configure --prefix=/@unixroot/usr --with-sysroot=/@unixroot --enable-shared --enable-languages=c,c++ --enable-frame-pointer --with-gnu-as --disable-bootstrap --disable-multilib --disable-libstdcxx-pch --enable-threads
Thread model: os2
gcc version 4.9.2 (GCC)
COLLECT_GCC_OPTIONS='-v' '-o' 'CPUbench.exe' '-mtune=i386' '-march=i386'
 G:/usr/bin/../libexec/gcc/i386-pc-os2-emx/4.9.2/cc1 -quiet -v -iprefix G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/ cpubenchmark.c -quiet -dumpbase cpubenchmark.c -mtune=i386 -march=i386 -auxbase cpubenchmark -version -o G:\var\tmp/ccGyMGfL.s
GNU C (GCC) version 4.9.2 (i386-pc-os2-emx)
        compiled by GNU C version 4.7.3, GMP version 5.0.2, MPFR version 3.1.0,
MPC version 1.0.1
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
ignoring nonexistent directory "G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/../../../../i386-pc-os2-emx/include"
ignoring nonexistent directory "/@unixroot/usr/local/include"
ignoring nonexistent directory "G:/usr/lib/gcc/../../lib/gcc/i386-pc-os2-emx/4.9.2/../../../../i386-pc-os2-emx/include"
#include "..." search starts here:
#include <...> search starts here:
 G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/include
 G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/include-fixed
 G:/usr/lib/gcc/../../lib/gcc/i386-pc-os2-emx/4.9.2/include
 G:/usr/lib/gcc/../../lib/gcc/i386-pc-os2-emx/4.9.2/include-fixed
 /@unixroot/usr/include
End of search list.
GNU C (GCC) version 4.9.2 (i386-pc-os2-emx)
        compiled by GNU C version 4.7.3, GMP version 5.0.2, MPFR version 3.1.0,
MPC version 1.0.1
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Compiler executable checksum: 40cb22df062740f747e010b72b1ced6d
COLLECT_GCC_OPTIONS='-v' '-o' 'CPUbench.exe' '-mtune=i386' '-march=i386' as -v --traditional-format -o G:\var\tmp/ccWtYHda.o G:\var\tmp/ccGyMGfL.s
GNU assembler version 2.27 (i386-pc-os2-emx) using BFD version (GNU Binutils) 2.
27
COMPILER_PATH=G:/usr/bin/../libexec/gcc/i386-pc-os2-emx/4.9.2/;G:/usr/bin/../libexec/gcc/;G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/../../../../i386-pc-os2-emx/bin/
LIBRARY_PATH=G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/;G:/usr/bin/../lib/gcc/;G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/../../../;/@unixroot/usr/lib/
COLLECT_GCC_OPTIONS='-v' '-o' 'CPUbench.exe' '-mtune=i386' '-march=i386'
 ld.exe -o CPUbench.exe G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/../../../crt0.o -LG:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2 -LG:/usr/bin/../lib/gcc -LG:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/../../.. -L/@unixroot/usr/lib G:\var\tmp/ccWtYHda.o -lgcc_so_d -lc_alias -lc_dll -los2 -lgcc_so_d -lc_alias -lc_dll -los
2 -lgcc_so_d -lc_alias -lc_dll -los2 -lgcc_so_d -lc_alias -lc_dll -los2
G:\var\tmp/ccWtYHda.o: Undefined symbol _pthread_create referenced from text segment
G:\var\tmp/ccWtYHda.o: Undefined symbol _pthread_join referenced from text segment
G:\var\tmp/ccWtYHda.o: Undefined symbol _pthread_create referenced from text segment
G:\var\tmp/ccWtYHda.o: Undefined symbol _pthread_join referenced from text segment

...but since 'gcc -c' alone (so compile only) works that means it's the linker that's failing and most likely because the pthread libarary is missing?

That should not be the case since:

Code: [Select]
Directory of G:\usr\lib

12-29-15   9:06a     12424         124  pthread.a
12-29-15   9:06a      4052         124  pthread.dll
12-29-15   9:06a    299570         124  pthread_g.a
12-29-15   9:06a    301982         124  pthread_s.a
        4 file(s)     618028 bytes used

...clearly shows pthread.a and inspecting it I find the _pthread_create/join functions there:

Code: [Select]
IMPORT#37#58c81:
00000000 e _pthread_create
00000000 E _pthread_create=pthr01._pthread_create
...
IMPORT#33#458c8:
00000000 e _pthread_join
00000000 E _pthread_join=pthr01._pthread_join

So what am I missing?

984
Programming / Re: GCC configuration - runtime options...
« on: February 22, 2018, 03:52:44 am »
...Hmm, under cmd.exe, this seems to be fine
Code: [Select]
set GCCOPT="-march=i686" "-pipe" "O2"giving
Code: [Select]
COLLECT_GCC_OPTIONS='-march=i686' '-pipe' '-O2' '-v' '-o' 'hello.exe'

Yup, that did the trick...I did not think that just listing the individual flags with double-quotes around each one and no concatenation character of any sorts in-between would work...but heck, that is our answer! Thank you.

985
Programming / Re: GCC configuration - runtime options...
« on: February 22, 2018, 12:02:23 am »
...Try SET GCCOPT='march=i686 -O2 -pipe' (might need double quotes)...

It worked...sort of...seems that multiple flags actually cause a problem, here is what happens:

1) issue : SET GCCOPT="-march=i686 -O2 -pipe"
2) compile : gcc -v hello.c -o hello.exe
3) what comes back is :

Code: [Select]
Using built-in specs.
COLLECT_GCC=gcc
Target: i386-pc-os2-emx
Configured with: ../configure --prefix=/@unixroot/usr --with-sysroot=/@unixroot --enable-shared --enable-languages=c,c++ --enable-frame-pointer --with-gnu-as --disable-bootstrap --disable-multilib --disable-libstdcxx-pch --enable-threads
Thread model: os2
gcc version 4.9.2 (GCC)
COLLECT_GCC_OPTIONS='-march=i686 -O2 -pipe' '-v' '-o' 'hello.exe'
 G:/usr/bin/../libexec/gcc/i386-pc-os2-emx/4.9.2/cc1 -quiet -v -iprefix G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/ hello.c -quiet -dumpbase hello.c -march=i686 -O2 -pipe -auxbase hello -version -o G:\var\tmp/ccxiDPJ7.s
GNU C (GCC) version 4.9.2 (i386-pc-os2-emx)
        compiled by GNU C version 4.7.3, GMP version 5.0.2, MPFR version 3.1.0,
MPC version 1.0.1
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
ignoring nonexistent directory "G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/../../../../i386-pc-os2-emx/include"
ignoring nonexistent directory "/@unixroot/usr/local/include"
ignoring nonexistent directory "G:/usr/lib/gcc/../../lib/gcc/i386-pc-os2-emx/4.9.2/../../../../i386-pc-os2-emx/include"
#include "..." search starts here:
#include <...> search starts here:
 G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/include
 G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/include-fixed
 G:/usr/lib/gcc/../../lib/gcc/i386-pc-os2-emx/4.9.2/include
 G:/usr/lib/gcc/../../lib/gcc/i386-pc-os2-emx/4.9.2/include-fixed
 /@unixroot/usr/include
End of search list.
hello.c:1:0: error: bad value (i686 -O2 -pipe) for -march= switch
 // 'Hello World' example
 ^
GNU C (GCC) version 4.9.2 (i386-pc-os2-emx)
        compiled by GNU C version 4.7.3, GMP version 5.0.2, MPFR version 3.1.0,
MPC version 1.0.1
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096

So the error "hello.c:1:0: error: bad value (i686 -O2 -pipe) for -march= switch" implies that the whole GCCOPT is perceived to be a single value, you can confirm that since "COLLECT_GCC_OPTIONS='-march=i686 -O2 -pipe' '-v' '-o' 'hello.exe'" shows it as such as well.

I'll investigate passing multiple values next...in the bigger scheme of things this is probably not all that important given that the more complex stuff would be done through a makefile anyways. Still, this type of stuff teaching you a bunch about the innner-workings, so some value there anywayss.

986
Networking / Re: RTL8211CL DRIVER
« on: February 21, 2018, 11:09:02 pm »
Ben,

...Whether the driver package is "well worth the money" in another and different circumstance, is irrelevant, non-productive, and ignores the rest of what I wrote...I would like it if the topic of this thread were not shanghaied into a "let's all protect/sell the new branded OS/2" flavour please...

Whoah....c'mon man...you posted a question regarding the driver support for your NIC, what you got was actually a pretty good response as far as hands-on experience goes AND what your other options may be.

Quite frankly, in as small of a forum as we have here, you'd think someone like yourself who is being presented with various additional options (whatever these may be...heck, build your own driver with the 32-bit driver framework then???) would at least be inclined to say "thank you" in a slightly less "up yours" kind of a way...know what I mean???

No one is trying to steal your thread and convert it into a sales pitch for ANOS...but man, your take on the thread contributions sure make me feel like I wasted the time digging through my system to at least get you some additional info...heck, I hate to imagine what would have happened had I checked the AN NIC driver README for your specific NIC device ID, pretty good chance, by the sounds of it, that I'd be accused of getting commisions on the sales...LOL, yeah, seriously, that's how ridiculous it seems to me.

Anyways...good luck to you...

987
Networking / Re: RTL8211CL DRIVER
« on: February 21, 2018, 07:44:20 pm »
Quote
$50 US, ($75 Can)

Well, it is actually $49 US, which is somewhere near $63 CAD (plus exchange fees). It is also more than just one driver. Well worth the investment, if you want to use OS/2.

Quote
I was just wondering, does ANoae have an upgrade plan for old eCS users?

I don't think so. ArcaOS is based on a different version of OS/2, but the driver package applies to eCS, as well as older versions of OS/2, ArcaOS has it's own subscription package.

Doug makes an excellent point...I have purchased the $49 US Drivers subscription for the past 3 yrs...money well spent. If anything, consider that their last release of SNAP video drivers finally put to bed the nasty SMP bug...I only wish they could fix the poor performance so that I could actually retire the original SciTech SNAP drivers.

I believe that the upgrade process is something that AN team is going to look at in the future, but for right now, no specific plans and/or dates have been released.

988
Programming / Re: GCC configuration - runtime options...
« on: February 21, 2018, 05:01:31 am »
Hey Dave!

...Which part are you wondering about?...

Ahh...the dreaded '-mtune=i386' '-march=i386' options. Even when I set the CFLAGS at CLI (SET CFLAGS='-march=i686 -O2 -pipe') the gcc execution in that same session does not appear to pick these up...so is it that gcc on it's own does not actually use the env variable and that it's sole use is for the make utility?

...For extra fun, try
Code: [Select]
gcc -v -E hello.c -o hello.exeand look at hello.exe in a text editor. Then do the same by replacing the -E with -S.

Good stuff...I got there in a slightly different way, be executing the cpp pre-processor and then the as assembler. Still...good stuff, especially the pre-processor output, it does give you the final look at the complete source tree, or at least the fully resolved path to all your includes.

989
Programming / GCC configuration - runtime options...
« on: February 21, 2018, 03:22:04 am »
I have the RPM package of GCC 4.9.2 installed here.

As I experimented with the optimal settings for the NBench benchmark I tried quite a few different opimization flags. Well, I am not back to much simpler stuff...literally "Hello World!"...except that I am using the simple stuff to learn a lot more about the whole GNU toolset configuration on our platform.

So here is the question, given a simple compilation with the -v (verbose) option I get a dump of the built-in flags:

Code: [Select]
[G:\code\source\GCC]gcc -v hello.c -o hello.exe
Using built-in specs.
COLLECT_GCC=gcc
Target: i386-pc-os2-emx
Configured with: ../configure --prefix=/@unixroot/usr --with-sysroot=/@unixroot --enable-shared --enable-languages=c,c++ --enable-frame-pointer --with-gnu-as --disable-bootstrap --disable-multilib --disable-libstdcxx-pch --enable-threads
Thread model: os2
gcc version 4.9.2 (GCC)
COLLECT_GCC_OPTIONS='-v' '-o' 'hello.exe' '-mtune=i386' '-march=i386'
G:/usr/bin/../libexec/gcc/i386-pc-os2-emx/4.9.2/cc1 -quiet -v -iprefix G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/ hello.c -quiet -dumpbase hello.c -mtune=i386 -march=i386 -auxbase hello -version -o G:\var\tmp/cceQCIJv.s
GNU C (GCC) version 4.9.2 (i386-pc-os2-emx)
        compiled by GNU C version 4.7.3, GMP version 5.0.2, MPFR version 3.1.0,
MPC version 1.0.1
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
ignoring nonexistent directory "G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/../../../../i386-pc-os2-emx/include"
ignoring nonexistent directory "/@unixroot/usr/local/include"
ignoring nonexistent directory "G:/usr/lib/gcc/../../lib/gcc/i386-pc-os2-emx/4.9.2/../../../../i386-pc-os2-emx/include"
#include "..." search starts here:
#include <...> search starts here:
 G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/include
 G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/include-fixed
 G:/usr/lib/gcc/../../lib/gcc/i386-pc-os2-emx/4.9.2/include
 G:/usr/lib/gcc/../../lib/gcc/i386-pc-os2-emx/4.9.2/include-fixed
 /@unixroot/usr/include
End of search list.
GNU C (GCC) version 4.9.2 (i386-pc-os2-emx)
        compiled by GNU C version 4.7.3, GMP version 5.0.2, MPFR version 3.1.0,
MPC version 1.0.1
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Compiler executable checksum: 40cb22df062740f747e010b72b1ced6d
COLLECT_GCC_OPTIONS='-v' '-o' 'hello.exe' '-mtune=i386' '-march=i386'
 as -v --traditional-format -o G:\var\tmp/ccokR79z.o G:\var\tmp/cceQCIJv.s
GNU assembler version 2.27 (i386-pc-os2-emx) using BFD version (GNU Binutils) 2.27
COMPILER_PATH=G:/usr/bin/../libexec/gcc/i386-pc-os2-emx/4.9.2/;G:/usr/bin/../libexec/gcc/;G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/../../../../i386-pc-os2-emx/bin/
LIBRARY_PATH=G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/;G:/usr/bin/../lib/gcc/;G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/../../../;/@unixroot/usr/lib/
COLLECT_GCC_OPTIONS='-v' '-o' 'hello.exe' '-mtune=i386' '-march=i386'
 ld.exe -o hello.exe G:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/../../../crt0.o -LG:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2 -LG:/usr/bin/../lib/gcc -LG:/usr/bin/../lib/gcc/i386-pc-os2-emx/4.9.2/../../.. -L/@unixroot/usr/lib G:\var\tmp/ccokR79z.o -lgcc_so_d -lc_alias -lc_dll -los2 -lgcc_so_d -lc_alias -lc_dll -los2 -
lgcc_so_d -lc_alias -lc_dll -los2 -lgcc_so_d -lc_alias -lc_dll -los2

Now what I am trying to figure out is where the heck the seeded COLLECT_GCC_OPTIONS comes from? Heck, compiling for a i386 architecture, even in a very simple program is...well, appaling...LOL, c'mon...no setup today should be defaulting to this...!!!

990
Applications / Re: VLC problems - was Open Office 4.1
« on: February 21, 2018, 03:09:32 am »
Hi David,

...I found the problem with VLC3.  I had to add the its "lib" folder to the Libpath statement in the config.sys,  It now works as it should....

...but if you are starting VLC through it's program object you certainly do not need to add the path to the LIBPATH variable, you would only do that if you intend to start vlc from CL, and therefore you would also want to add it to the PATH as well.

What you have done is certainly not wrong, but a more flexible/safe way would be to create a vlc.cmd file in the VCL directory which modifies the LIBPATH for just the VLC session, that way the VLC install will not impact anything else on your system.

Here is what's in my vlc.cmd:

=== START ===
SET BEGINLIBPATH=G:\apps\multimedia\vlc2\usr\local\lib;%BEGINLIBPATH%
G:\apps\multimedia\vlc2\usr\local\bin\vlc.exe %1
=== STOP ===

...then my VLC program object simply points to the VLC.CMD script.

Pages: 1 ... 64 65 [66] 67 68 ... 89