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 [ 02 | June | 2003 ]

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


Date: Mon, 2 Jun 2003 05:51:42 PDT7
From: "Harry Motin" <hmotin@sbcglobal.net >
Reply-To: scoug-help@scoug.com
To: "Info 4 SYNass" <Info@SYNass.NET > ,
Subject: SCOUG-Help: Re: Wayne's ide... IMPORTANT

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

On Mon, 2 Jun 2003 00:03:29 PDT7, Info 4 SYNass wrote:

>I noticed that CONFIG.SYS & SNOOP.LST has REMmed SCSI entries !?
>Could this cause this result that Wayne cannot see his SCSI drive now
>???

No, it could not do that. The SNOOP.LST is for registering hardware to the Hardware
Manager and making it known to OS/2. You can run your system without the
SNOOP.LST file. In my case a bad snoop Adaptec SCSI file associated with a line in
the SNOOP.LST caused my system to trap everytime I tried to run the Hardware
Manager in Full Hardware Detection mode. I had to disable the offending line.

Steven later communicated to me that he had Wayne not use his SCSI system at that
particular point. That is, the SCSI adapter driver was not active in Wayne's
CONFIG.SYS at that particular time. Hence, FDISK could not see the SCSI drive

HCM

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

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 [ 02 | June | 2003 ]



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.