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

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


Date: Fri, 17 Mar 2006 18:07:52 PST8
From: sshapiro@ucsd.edu (Sandy Shapiro)
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Startup problem

I have about six items in my startup folder, and just recently I have
started getting error messages during bootup. For example, it might be
Pmfax that gives the error message or it might be Manyclip, or it might be
dhpstart (which does not give a message -- it just hangs).

The message is usually a Sys2020 -- "could not demand load the
applications's segment -- see Sys193". Sys193 says: "cannot be run in an
OS/2 session."

I don't know why this should start happening all of a sudden after years
of no problems.

What has changed recently? Well, for one thing, I replaced my SCSI CD
burner with an EIDE DVD burner. That seems to work OK. The error messages
started, however, while I was playing around with Daniatapi.flt.
Specificaly, I added parameters to the command to see if I could get the
drive to be recognized after boot up.

What I mean is that if RSJ is not loaded, the drive is seen after boot up.
If RSJ is loaded, the drive is seen only after it is "attached" by RSJ.
Dani says both will work if you add the parameter:

Daniatapi.flt /A:x /U:x /RSJ

I tried all combinations of 0 and 1 for the A and U parameters (ie: /A:1
/U:0) etc. But none worked. It was while testing this that the error
messages started to occur. I have now gone back to the plain daniatapi.flt
command without any parameters, but the error messages keep occurring
(which is why I think it may be just a coincidence).

I also wonder if my hard drive, which is old, may be starting to act up. I
don't have the SMART technology available with this mother board.

I would appreciate any suggestions for troubleshooting this.

Thanks,
Sandy

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

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 [ 17 | 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.