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 | September | 2005 ]

>> Next Message >>


Date: Fri, 23 Sep 2005 23:12:56 PDT7
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Ethernet IRQ and SPCIIRQ related questions

In <20050918191530.WQTI12165.mta10.adelphia.net@[192.168.1.99]>, on
09/18/05
at 12:15 PM, "Michael Rakijas" said:

Hi,

I've surfaced for a while from my private projects.

>Hmm. I don't know what happen - must have gotten a little careless with
>my piping.

No problem. Now you get to install pci.exe a bit more carefully and try
again. It appears that either you neglected to install pcidevs.txt where
pci.exe could find it or the file is corrupted. This file is required so
that pci.exe can translate the vendor and device codes to something useful
to humans.

>probe1.log contains the output of: pci -S
>probe2.log contains the output of: pci -P -T -B -D -R
>probe3.log contains the output of: show_pir
>probe4.log contains the output of: show_lnk
>probe5.log contains the output of: rmview /irq

FWIW, I find it easier to keep track of which file is which when I use
mnemonic names like

pci_s.out
pci_btbdr.out
show_pir.out
show_lnk.out
rmview_irq.out

I use .out rather than .txt to avoid overwriting readme files named like
appname.txt.

Regards,

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.67 #10183 Warp4.something/14.100c_W4
www.scoug.com irc.fyrelizard.com #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
"postmaster@scoug.com".

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


>> Next Message >>

Return to [ 23 | September | 2005 ]



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.