SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 15 | July | 2002 ]

<< Previous Message << >> Next Message >>


Date: Mon, 15 Jul 2002 12:14:33 PST7
From: "J. R. Fox" <jr_fox@pacbell.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: VACP | Mozilla | Java 1.31

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Some loosely related questions:

I'm about to install Mozilla into ECS, and wanted to scout out any
"gotchas" ahead of time.

1) The new release of BZIP2 mentioned on the VOICE list says you need
some VACP runtime or library to use it. (A similar case to EMX ?)
I'm not sure why anyone might need BZIP (or RAR for that matter), when
we have the well-ingrained standards of PKZIP and InfoZip, but this
left me wondering. The Mozilla build all seem to have VACP as part of
their archive's long filenames. I had thought this only referred to
how they were compiled, and a quick skim of the docs did not turn up
mention of a need for outside modules, but I just wanted to be sure.

2) Wayne asked if there was a reason to prefer Mozilla 1.0 over 1.1a,
and I'd like to see that answer too. I would like to have Mozilla
co-exist with the already installed 4.61, and perhaps just "adopt" its
profiles & preferences. If there is some Skin or option to have
Mozilla look / act more like 4.61 in its UI (except for 4.61 crashes,
of course !), I'd probably like to enable it.

3) I've been looking over the Java 1.31 docs. The part about Known
Limitations if it is the default Java -- certain app.s will fail,
including LVMGUI and some TCP/IP stuff -- bothers me. I notice that
my ECS install placed Java 131 first in Libpath, but not at all in
Path or Classpath. So maybe I should just leave that alone ? If I
can still use 131 for Mozilla somehow (?), that would be fine.

4) I wasn't sure if the default install of ECS placed Java 131 and the
4.3 TCP stack in with the os, but a Syslevel report lists them, so
they must be there. Their presence may not be the same thing as their
being active or the default, though ?

5) I would want to install whatever plug-ins I had for 4.61 that
Mozilla can use.

Jordan

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 15 | July | 2002 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.