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 [ 15 | June | 2004 ]

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


Date: Tue, 15 Jun 2004 19:09:08 PDT7
From: "Harry Motin" <hmotin@sbcglobal.net >
Reply-To: scoug-help@scoug.com
To: < "scoug-help@scoug.com" > scoug-help@scoug.com >
Subject: SCOUG-Help: Re: OS2CDROM + RSJ a No-Go

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

On Tue, 15 Jun 2004 12:27:11 PDT7, J. R. Fox wrote:

>If you have any further ideas, I'd be glad to hear them.

Yes, I do.

>Both of these versions yielded a functional OS2CDROM. Neither of them yielded a
>functional
>RSJ. I can read a cd, but when I try to attach it for RSJ purposes (which involves their
>WORM
>drive sleight-of-hand), I get the error "The System is Unable to Find the Specified
>Device" --
>or words to that effect.

The fact that you can use your new unit as a CDROM unit indicates to me that RSJ
REALLY is not recognizing your unit at bootup and doing the proper things. If it was
doing what it was supposed to, you would not be able you use your new drive as a
CDROM unit, when booting with the CD_NO.CFG_TRY_THIS_FIRST file. That
CONFIG.SYS was designed to use RSJ just exactly as you would under a fresh RSJ
install (that is, no Daniela's back door). Therefore, the problem is RSJ reading and
ID'ing your unit at boot up.

I had that problem with my Yahama unit. I suggest you do what I did. I E-Mailed the RSJ
folks and explained the problem. They informed me that their software did not
recognize my unit. They told me how to edit my cddrv.inf file to get RSJ to recognize it at
boot. After that everything else was gravy.

In summary, E-Mail RSJ. But first, you've got to set up your RSJ installation just like RSJ
originally intended it. I suggest that you uninstall it and then reinstall it. But after that do
not fool around with it. If it does not work after a fresh reinstall, E-Mail RSJ with your
information.
HCM

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

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 << >> Next Message >>

Return to [ 15 | June | 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.