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 [ 05 | May | 2004 ]

>> Next Message >>


Date: Wed, 5 May 2004 01:42:11 PDT7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: netbind

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

Mark Abramowitz wrote:
>
> Any suggestions as to what to do to track the problem down?

On my system I added echo statements to MPTSTART.CMD and
SETUP.CMD (called by MPTSTART.CMD) so I can monitor what's
going on during bootup. Both are in \MPTN\BIN\.

You can also execute echos from CONFIG.SYS by calling
CMD.EXE. Here ya go:

CALL=G:\OS2\CMD.EXE /C ECHO HELLO, WORLD

There's also a device driver named DELAY.SYS you can use
to monitor where in the boot process you are. Examples:

DEVICE=DELAY.SYS :00 Beginning of DEVICE=*.SYS driver loading.
DEVICE=DELAY.SYS :00 End of DEVICE=*.SYS driver loading.

I think it's on Hobbes as DELAYD.

ECHOing from a BASEDEV is a problem -- my understanding
is that the boot process queues all BASEDEV messages and
displays them en masse when BASEDEV processing is completed,
thus you can't see where you are in the BASEDEV loading
process if something isn't working.

- Peter

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

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

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


>> Next Message >>

Return to [ 05 | May | 2004 ]



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.