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 [ 26 | March | 2006 ]

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


Date: Sun, 26 Mar 2006 09:59:05 PST8
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Network Not Working

In <20060326081939-51189-7@scoug.com>, on 03/26/06
at 08:19 AM, "Harry Motin" said:

>11063065 chipset drivers, identified by NICPak. Thank you Steven for
>pointing me to those drivers. Incidently, PCI.EXE listed the NIC as VIA
>VT6102 Rhine II, not VIA 11063065.

First thing is make sure you have the most recent version of NicPAK. If
you do have the most recent, I recommend you report the problem to Chuck.

> VIA VT6102 Rhine II Another OS/2 NDIS MAC driver ver.1.06 (200512-17)
> info: Set Power Management Status to D0 and/or clear PMESTS.

You need to ask the author what this means, or read the source code. ;-)
IIRC, the source is included.

> ioctl(SIOCAIFDDR): Invalid Arg
> E:\MPTN\BIN\VDOSCTL.EXE
> Press Enter to continue

I suspect may you have a extra route statement in setup.cmd. However, if
the vdosctl.exe is really failing to load, it's something on the MDOS side
that got a problem. Does ETC in \autoexec.bat point to the same place, as
ETC in \config.sys? If not, check the MDOS etc. directory for farkled
settings. FWIW, I point both ETCs to the same directory.

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.67 #10183 Warp/eCS/DIY/14.103a_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".

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


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

Return to [ 26 | March | 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.