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 [ 03 | January | 2002 ]

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


Date: Thu, 3 Jan 2002 18:06:49 PST7
From: Harry Chris Motin <hmotin@attglobal.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Re: Device driver

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.
=====================================================

Harry Chris Motin wrote:
>
> Steven,
>
> Thanks for your help. Please excuse the "seemingly dumb" questions. I
> downloaded a larger set of the zip files (basically all of the "OS/2
> host" files, the "All hosts" files and all of the platform specific
> target files for C, C++ and Fortran77).
>
> OK. In your reply to me I understand about the command file, which adds
> to some of the command variable settings via replacable parameters. I
> can do that! But I do not understand the following:
>
> 1. You have reference to a toolkit, residing on D:\. What toolkit is
> this? Is it the IBM device drivers kit?
>
> 2. Also, you state: "To use Watcom, run this before running your app".
> Yes, run the command file. But, before running what app??
>
> Thanks.
> HCM
> _______________________________________________________________________________________________
>
> Steven Levine wrote:
> >
> > =====================================================
> > 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.
> > =====================================================
> >
> > In <3C349308.21C26279@attglobal.net>, on 01/03/02
> > at 12:21 PM, Harry Chris Motin said:
> >
> > >I need a little help at the OpenWatcom website. At that site you can
> > >download 2 *.exe files, which are the C/C++ developer and the Fortran77
> > >developer. The first one is ~46MB in size and the other is ~34MB. There
> > >are also a bunch of *.zip files for C/C++ and Fortran77, that you can
> > >download as an alternative.
> >
> > What I did was download the .zip's I wanted. A much smaller download.
> > Here's my work list:
> >
> > Core files required by all versions
> > -----------------------------------
> >
> > * core_all - Core binaries (All hosts)
> > * core_binp - Core binaries (OS/2 host)
> >
> > * c_binp - C compiler (OS/2 host)
> >
> > * clib_hdr - C runtime library header files
> > * clib_a16 - C runtime libraries (16-bit all targets)
> > * clib_o16 - C runtime libraries (16-bit OS/2)
> > clib_d16 - C runtime libraries (16-bit DOS)
> > * clib_a32 - C runtime libraries (32-bit all targets)
> > * clib_o32 - C runtime libraries (32-bit OS/2)
> > clib_d32 - C runtime libraries (32-bit DOS)
> >
> > All C++ components require the C compiler & library ZIP's
> > ---------------------------------------------------------
> >
> > cpp_binp - C++ compiler (OS/2 host)
> >
> > cpplib_hdr - C++ runtime library header files
> > cpplib_a16 - C++ runtime libraries (16-bit all targets)
> > cpplib_o16 - C++ runtime libraries (16-bit OS/2)
> > cpplib_a32 - C++ runtime libraries (32-bit all targets)
> > cpplib_o32 - C++ runtime libraries (32-bit OS/2)
> >
> > * dbg_all - Debugger, profiler (All hosts)
> > * dbg_binp - Debugger, profiler (OS/2 host)
> >
> > * ide_all - IDE, editor, browser (All hosts)
> > * ide_binp - IDE, editor, browser (OS/2 host)
> >
> > samples - Sample code
> >
> > Manifest for all help files
> > ---------------------------
> >
> > * core_hlp_os2 - Core help files (OS/2 host)
> >
> > * c_hlp_os2 - C compiler & library help files (OS/2 host)
> >
> > cpp_hlp_os2 - C++ compiler & library help files (OS/2 host)
> >
> > * dbg_hlp_os2 - Debugger, profiler help files (OS/2 host)
> >
> > * ide_hlp_os2 - IDE, editor, browser help files (OS/2 host)
> >
> > All you need is the all host and os/2 host stuff for C. These happen to
> > be * for historical reasons. :-)
> >
> > >hours and the connection went dead. So ..., I later downloaded all the
> >
> > You need to use an FTP client that will resume download. :-) wget is a
> > fine choice.
> >
> > >*.zip files and unzipped them into a common directory, preserving all the
> > >subdirectory structure. My problem is that I do not see how to install
> > >C/C++ and Fortran77 as a working system, using the unzipped files. There
> >
> > I wouldn't bother with F77 unless you are going to use it. Just unzip the
> > files I've marked
> >
> > >does not seem to be an installer and there are no installation
> > >instructions. Anyone had any experience with setting up C/C++, using the
> > >*.zip files????
> >
> > Who me?
> >
> > After you unzip the files, create a .cmd file like:
> >
> > SET WATCOM=D:\WATCOM
> > SET TOOLKIT=D:\TOOLKIT
> > SET PATH=%WATCOM%\BINP;%WATCOM%\BINW;%PATH%
> > SET INCLUDE=%WATCOM%\H;%TOOLKIT%\H
> > SET EDPATH=%WATCOM%\EDDAT
> > SET HELP=%WATCOM%\BINP\HELP;%HELP%
> > SET BOOKSHELF=%WATCOM%\BINP\HELP;%BOOKSHELF%
> > SET BEGINLIBPATH=%WATCOM%\BINP\DLL
> > SET LIB=%TOOLKIT%\LIB;%WATCOM%\LIB386\OS2;%WATCOM%\LIB386;
> >
> > To use Watcom, run this before running your app. Of course, you can
> > always update config.sys. I've got too many compilers to be able to too
> > that cleanly, so I've get similar files for each compiler other than VAC
> > 3.08. This one is in config.sys because it got there first. :-)
> >
> > If you want C++, unzip them too. This .cmd file should be OK for C++.
> >
> > >Any suggestions with the *.zip files and/or the 2 executable files would
> > >be appreciated. Thanks.
> >
> > You might not like the .exe's. They require and WinXX installer.
> >
> > Steven
> >
> > --
> > ----------------------------------------------------------------
> > "Steven Levine" MR2/ICE 2.30a #10183 Warp4/FP15
> > www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
> > ----------------------------------------------------------------
> >
> > =====================================================
> >
> > 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".
> >
> > =====================================================

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

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 [ 03 | January | 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.