SCOUG-HELP Mailing List Archives

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

Date:	Thu, 27 Dec 2001 15:30:49 PST7
From:	"J. R. Fox" <jr_fox@pacbell.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Re: Your CD Writer under RSJ

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

Sandy wrote

> I have been using RSJ for years, I am up to version 3.60.
> With the DANI drivers, I can use my CD writer as a CD ROM drive.

I have a CD reader as well as a CD writer drive in my all-SCSI system (so, no DANI driver needed); the
writer doubles as a 2nd. CD reader, as necessary.

> Now, all of a sudden, when I boot up, there is no CD ROM drive. I can
> still attach the CD Writer.
>
> If I rem out: basedev=lockcdr.flt when I boot, then I can see my CD ROM
> drive.
>
> Of course, I then lose my CD Writer.

> This is a new problem. Something has changed, but I can't figure out what.
> Perhaps the lockcdr.flt driver got corrupted?

No, this is normal, per your setup with the RSJ software. You can have the recorder be seen as strictly a
writer, or as both . . . with it functioning as a writer while "Attached." (I seem to recall this has
something to do with the RSJ s/w operating the writer under Warp as if it were a WORM drive.) If you want
this "dual" functionality as your default, rather than the RSJ default, you must have the LOCKCDR.FLT
line REMmed OUT ! This is the way I have always chosen to have it. I'm not entirely sure why they chose to
default it the _other_ way, and their documentation does not call sufficient attention to this arrangement.

Peter replied:

> But try a deinstall and reinstall of RSJ. That will 1) refresh
> lockcdr.flt, 2) make sure your config.sys drivers are in the proper
> sequence, and 3) clear up any *.ini file entries that are out of whack.

Nope. Here's the deal -- and I was re-reminded of this in the course of having upgraded to ver. 3.55
recently, and then to ver. 3.61 even more recently, and twice. When you install or reinstall RSJ (as I had
to after my little fiasco with the Aggressive File Handles repair option of UniMaint), just about the only
thing it does to your CONFIG.SYS is to move the RSJ lines to a location of its own, a place other than the
one you may have chosen, and it **reinstates** an active LOCKCDR line, because that is the default. This
will take you back to Square One, yielding the "symptoms" noted by Sandy. Now, when I need to put a new RSJ
on, I first make a safety copy of CONFIG.SYS. After the fresh RSJ install, I delete the RSJ modified Config
and rename the copy I hid from it under the temporary name. And that should do it.

Jordan

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

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

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

Return to [ 27 | December | 2001 ]

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.