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 [ 04 | July | 2002 ]

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


Date: Thu, 4 Jul 2002 07:11:13 PST7
From: Harry Chris Motin <hmotin@attglobal.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Basic Help

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

Butch,

You are welcome! OK, so now you know about the "setcopyfromfloppy". It
should be:

SET COPYFROMFLOPPY=1

I am not sure why you have that in the CONFIG.SYS file of your up and
running and installed OS/2. I do not have it in mine. Please look in the
CONFIG.SYS file of your installed system and confirm that you have it.
This is the file that resides in the root directory (C:\CONFIG.SYS). I
looked up the usage of that SET statement in a database for the OS/2
CONFIG.SYS file. It says the following:

=1 or ON

If OS/2 should install updated drivers during an installation from the
Installation disks and not from CD this statement must reside in the
config.sys on Installationdisk 1

The above is an exact copy from that database. As it states, its used
for installing the OS. It is not used on up and running OS/2.

You can delete that line from your C:\CONFIG.SYS file.

I have a couple of comments for you:

1. You might try installing the SciTech video display driver as the
first update of your system to the correct drivers. If you do this, you
will have a much better video display and it will be easier to work with
your system for the other changes. I use the SciTech driver on my system
(I use an ATI video adapter card). If you have problems with the SciTech
driver, I can help you.

You should not have any problems with the SciTech driver, however. I
found the installation easy and straight forward. To install the SciTech
driver, you have to change your system back to VGA video mode first.
That's pretty ugly. Some of your icons will probably be off your desktop
and inaccessible.

2. You asked about the OS/2 desktop (GUI) and why it isn't more
popular. This desktop came into its final version in OS/2 Warp 4, which
was delivered to the public circa 1993-1994 - well before the release of
Windows 95. Prior to that the desktop GUI was in pretty much its final
form with the release of OS/2 2.1 and OS/2 Warp 3 (circa 1992-1993).
Warp 4 just added refinements to the OS.

IBM did not have much success convincing developers to write software
for the OS, or convincing PC makers to preload the OS on machines. Some
of the problem was IBM marketing ineptness. However, a verrry
significant part of the problem was Microsoft, behind the scenes (I kept
up with developments in the antitrust trial). Apparently, Microsoft
threatened everyone not to develop for OS/2 or preload on PC. They had
exclusivity contracts to enforce it. If you developed or preloaded OS/2,
you could not get a contract to develop for Windows (or preload it).
Since Microsoft was the 600 lb gorilla (a majority of people were going
to buy Microsoft anyway), everyone fell in line. IBM continued to
develop OS/2, but the public did not have much faith in their
commitment. It turns out that Microsoft was putting the screws to IBM
behind the scenes. Evidence from the trial states that Microsoft plainly
told IBM that they would hold them at a disadvantage, relative to
Windows products, as long as they (IBM) continued to compete with them.
Microsoft did the following to IBM:

A. Microsoft claimed that IBM owed them more money for IBM's use of
Windows 3.0 and 3.1 in OS/2. They held off any Windows 95 licensing with
IBM until the results of Microsoft's audit were settled

B. After IBM settled the audit (gave them more money) Microsoft
dragged its feet in cooperating with IBM on IBM/Lotus development of
Windows products (Microsoft insists that Windows products from other
developers be tested by Microsoft and receive the Microsoft seal of
approval). Microsoft would take months to examine and approve IBM/Lotus
products for Windows.

C. IBM was the last computer manufacturer to receive a license to
preload Windows on their machines. IBM received the Windows 95 license
15 minutes before the public release of 95. Microsoft also charged IBM
the highest license fee.

3. As you read the OS/2 tutorial, one of the most basic operations with
the desktop GUI (OS/2 calls it the WorkPlace Shell, or WPS) is the
movement and manipulation of icons. You can do three things: 1.) copy
files; 2.) move files; 3.) create shadows of files. Please note the
following:

A. To make copy of a file, highlight its icon, using the left mouse
button (LMB). Then, press the CONTROL key and drag the icon, using the
right mouse button (RMB) to where you want to copy it. As you drag it
you will notice that the original icon stays where you found it, but
that you are dragging a "faded" copy under the RMB. This is your
indication that you are indeed going to make a copy. To complete this
operation release the RMB where you want the copy, then release the
CONTROL key.

B. To move a file, highlight its icon, using the LMB. Then, drag it to
where you want to move it, using the RMB. While you are dragging it, the
original icon will remain in place and the dragged icon, under your RMB,
will be in full display (not faded). Release the RMB where you want to
move the file.

C. To make a shadow of a file (Microsoft calls the same thing a
"shortcut") highlight the file's icon with the LMB. Press the SHIFT and
CONTROL keys together. Then, using the RMB drag the icon to where you
want to create the shadow. You will see a "string" created and tied to
the original icon and the icon under your RMB. This is your indicator of
the shadow creation operation. Release the RMB, then release the SHIFT
and CONTROL keys.

The above are the standard ways of creating copies, moves and shadows.
In a few instances, however, they are modified. For example, making a
shadow is the standard operation for a file that is in a folder on the
hard drive (not on the desktop), but for which you create something on
your desktop. Therefore, if the file is in a hard drive folder, using
the RMB, only, creates a shadow (you see the string attached to the
icons as you do the operation). It does not create a move. Try it. Go to
your "Drive C" folder and find the icon of a file somewhere on your hard
drive. For example, use the C:\CONFIG.SYS file icon. If you RMB this
file from C: to the desktop (don't release the RMB), you will see the
attached string, indicating a shadow creation operation.

HCM
______________________________________________________________________________

Butch Langel 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.
> =====================================================
>
> Nice people at Scoug Help, I have only one word to express myself tonight:
> WOW !
> I reinstalled the system and was successful. There were some errors prior
> to booting that necessitated pressing the enter button to continue, but this
> time indeed the system continued to boot and success.
> Interestingly, the first error message indicated the statement
> "setcopyfromfloppy" on line one of the config.sys file was not recognized
> and ignored.
> I must still install drivers for soundcard, video, printer , ethernet, and
> cd-r.
>
> I am going to try to spend some time going thru the os2 tutorial to
> familiarize myself with the system. It isn't anything like I've seen. This
> is the first time I've seen it live. The gui is very impressive. I can't
> understand why it isn't more popular. Why did IBM decide not to support the
> system?
> The WarpUP 15 cd has been ordered. I am sure I will be asking for
> assistance when I start installing drivers and upgrades.
>
> Again, thank you for your support and kindness. It is surely appreciated.
>
> Butch Langel
>
> =====================================================
>
> 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 [ 04 | 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.