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 [ 04 | March | 2002 ]

<< Previous Message <<


Date: Mon, 4 Mar 2002 23:57:09 PST7
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Re: RSJ Lines

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

In <0GSH00FWAK3QTN@mta5.snfc21.pbi.net>, on 03/04/02
at 09:48 PM, sshapiro@ucsd.edu (Sandy Shapiro) said:

>Yes (as long as I don't have lockcdr.flt enabled).

OK, this is how this part is supposed to work.

>Yes, that is exactly what happens (as long as lockcdr.flt is enabled).

Of course, it should happen even if lockcdr.flt is not loaded.

Where's your reference to:

BASEDEV=OS2ASPI.DMD /ALL

>BASEDEV=RSJIDECD.FLT

REM the above out. You should not needed it and it just confuses the
issue.

>DEVICE=F:\CDWFS\RSJSCSI.SYS
>IFS=F:\CDWFS\CDWFS.IFS

These appear to be standard

>RUN=F:\CDWFS\CDWFSD.EXE -p "H:/TEMP" -c20000 -b2048 -t2 -i3 -s0

This is fine although I find it odd that they use a forward slash.
However, it should work.

>BASEDEV=LOCKCDR.FLT

This we want to REM out.

>Here is the Attach object:

This looks fine although it look more like a settings folder than what I
expected. Like I said, I don't have RSJ installed.

What you might want to do is read up on cdattach. It's a command line
version of the Attach button. Perhaps you will produce a more
understandable error message.

FWIW, I detest error messages like:

The system cannot find the device specified

because they provide not help in knowing what failed. What system is the
message referring to and what is the device name it's looking for.

One other thing to check. Since you have two CD drives, you have to tell
RSJ which one is the CD writer. With the filter loaded this is not needed
because a WORM drive does not look like a CD reader. Without the filter,
you have to tell RSJ because the CD writer looks just like a CD reader.

Steven

--
---------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.31a #10183 Warp4/FP15/14.085_W4
www.scoug.com irc.webbnet.org #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
"rollin@scoug.com".

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


<< Previous Message <<

Return to [ 04 | March | 2002 ]



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.