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 [ 23 | April | 2006 ]

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


Date: Sun, 23 Apr 2006 17:06:00 PST8
From: Zdenek Jizba <jizba@verizon.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: detecting hard disk

Content Type: text/plain

Steven Levine wrote:

>In <444B82F1.10507@verizon.net>, on 04/23/06
> at 06:38 AM, Zdenek Jizba said:
>
>
>
....(prior text removed)...

>Odd. I usually get a blinking cursor at the end of the press enter
>message. Were you referring to the other multicolored blinking?
>
>
with reference to pressing enter. I guess that I was not very clear. After
the message:" DHCPSTRT: DHCP client did not get parameters. DHCPSTRT
continuing to try in background Press enter to continue" I DID press enter.
At that point the whole screen lit up with some 20 colored lines and
each line
containing blocks of color junk (as best as I can describe). The height
of the
lines was such that there was no intervening blank space between them,
and the
whole screen was blinking.

>>So what is NIC recognition problem (issue?) and how can it be fixed? More
>>to the point why do I have such problems?
>>
>>
>
>You probably have such problems because you bought the motherboard without
>checking if the on board NIC had known, working OS/2 drivers. As a long
>time OS/2 user, you should know that OS/2 does not support everything that
>is manufactured. The problem itself easy enough to fix once it is fully
>understood. Take a glance a Sheridan's thread, which is a classic case.
>
>
>
As a computer user as opposed to one who deals with the inner workings
of hardware
I must say that I was not aware that some components may not be readily
supported by
OS/2. When I went to MWAVE to order the tower, I had one of the
technicials select
the components that I wanted (80GB hard disk, CD-RW read/writer,
diskette drive
internal modem, a motherboard with good but not necesarily fastest chips
and NO
windows) on the only condition of having a long time warranty and the
whole to
cost less than $1000 (actually quite less).

>Regards,
>
>Steven
>
>
>
Denny Jizba

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

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
"postmaster@scoug.com".

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


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

Return to [ 23 | April | 2006 ]



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.