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 [ 21 | September | 2002 ]

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


Date: Sat, 21 Sep 2002 13:45:44 PST7
From: Harry Chris Motin <hmotin@attglobal.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: system stop

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

Hi Butch,

I use RSJ version 4.04. I previously used RSJ version 3.61. Therefore, I
may be able to help you.

Before, we begin just a note of caution: with OS/2 ALWAYS, ALWAYS make a
backup of AT LEAST your destop files, OS2.INI, OS2SYS.INI and CONFIG.SYS
files before you install anything. In fact, you would be completely
safe, if you first made a full and complete backup of your system. That
way, you can always back out of a faulty/problematic install. It's the
safest way on OS/2, because the integration of different programs into
the OS varies a
lot with each program. Some are really good, some are OK, some are
problematical.

The RSJ install places some drivers on your hard drive and modifies your
CONFIG.SYS to install these drivers at bootup, which run RSJ and your
CD-R/CD-RW unit. That's all. Sometimes RSJ does not support all
CD-R/CD-RW units right out of the box. RSJ trys to auto detect you
hardware upon bootup, but sometimes fails, or perhaps auto detects
incorrectly. I suspect the latter is what is happening to you, and
because it detects incorrectly, it locks up your system. You can
E-Mail RSJ Software and tell them what CD-R/CD-RW unit you have. Usually
they can E-Mail back a configuration file with instructions for
installing on your system and that will take care of the problem.

OK. What I recommend for now is to back out of the RSJ driver
installation on bootup by REM'ing out all lines in your CONFIG.SYS file
that pertain the the RSJ drivers. You need to find all the lines added
by RSJ. And actually, to be certain, it would be better if you could
just temporarily substitute a previous CONFIG.SYS file, the latest one
before your RSJ install.

Either by REM'ing lines in your CONFIG.SYS or by going to an earlier
one, temporarily get rid of the RSJ driver installation at bootup.

Next, tell me what version of RSJ you have. Also, tell me what
CD-R/CD-RW unit you have. Find out if it directly supported by RSJ If it
is, you will see it listed, by make and model, in the CDDRV.INF file,
located in the CDWFS installation directory. Open this file in an
ordinary text file editor to read it.

If your unit is not listed in the file, that's probably your problem.
You will have to E-Mail RSJ software at "support@rsj.de". Tell them your
problem and that your unit is not listed in the CDDRV.INF file. As I
said, they will E-Mail you a replacement file with instructions. You may
have to call RSJ to hurry them along. They were slow (for me) in
answering the mail. After around 4 days of no response, I called them
and got prompt action that worked the first time.

HCM
______________________________________________________________________________

Butch Langel wrote:
>
> =====================================================
> 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 Fri, 20 Sep 2002 23:33:16 PST7
> "Info2SYNass.NET" wrote:
>
> > =====================================================
> > 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.
> > =====================================================
> >
> > Hi Butch,
> > please excuse me for my intervention:
> > I assume not RSJ has corrupted your CONFIG.SYS ;-)
> > Your re-re-installation, perhaps before reading and studying
> > the manual may have "corrupted" your CONFiG.SYS ;-(
> >
> > I never had the problem like you described but the problem of RSJ
> > not
> > recognizing the CD-RW is known because the correct settings in
> > the, again,
> > CONFIG.SYS seem to be very important but also somewhat tricky and
> > I also
> > was struggling with this ;-)
> >
> > Be insured that I do not want to offend you or anybody ...
> > ... but sometimes I cannot express better or smoother with my
> > Swiss-German-English. Please excuse me ;-(
> >
> > Regards, svobi
> >
> >
> > svobi,
> No problem. No offense taken. You are correct in every way.
>
> Butch
> >
> >
> >
> >
> >
> > eyeleica@lvcm.com on 21.09.2002 08.09.31
> > Please respond to scoug-help@scoug.com
> > To: SCOUG-help@scoug.com
> > cc:
> > Subject: SCOUG-Help: system stop
> >
> > With the help of Sector at the os/2 irq tonight, I was able to
> > get the system going. He suggested I uninstall RSJ cd-w program
> > and reinstall it. I read the manual and looked for a way to
> > uninstall, but couldn't find one. I then made a mistake and just
> > reinstalled RSJ again and rebooted. Upon reboot, I again got
> > system lock with previous errors. So, I am back at square one.
> >
> > Not only has RSJ corrupted my config.sys file, but it doesn't
> > recognize my cd-r.
> >
> >
> >
> >
> > ************************************************************
> > *** >>> Say NO to HTML in Mail and News <<< ***
> > *** ++++++++++++++++++++++++++++++++++++++++++++++++ ***
> > *** >>> AGAINST TERROR +++ AGAINST WAR <<< ***
> > ************************************************************
> >
> > =====================================================
> >
> > 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".
> >
> > =====================================================
> >
> >
>
> =====================================================
>
> 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".
>
> =====================================================

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

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 [ 21 | September | 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.