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

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


Date: Wed, 25 Sep 2002 21:48:51 PST7
From: jack.huffman@worldnet.att.net
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: frequent WPS archiving suggested

=====================================================
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 <1032970059-0-Info@SYNass.NET>, on 09/25/2002
at 02:26 AM, "Info2SYNass.NET" said:

>=====================================================
>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 Harry, Hi Butch, Hi everbody
>Butch's struggling with RSJ shows once more again the importance of
>a very frequent WPS archiving and the command ARCINST ;-)

>With these frequent archives we will have a chance to restore back to
>a well working environment if anything wents wrong ;-))

>It has been so helpful in sooo many times for me that I cannot repeat
>enough to do so ;-)))

>But do not forget to adjust your OS2.KEY file to your personal needs ...
>... otherwise you will be disappointed ;-(

>To anybody with an OS2.KEY file containing these few lines only:

>KEYFILE:OS2.INI
>KEYFILE:OS2SYS.INI
>KEYFILE:C:\CONFIG.SYS
>KEYFILE:C:\STARTUP.CMD
>KEYFILE:C:\AUTOEXEC.BAT
>KEYFILE:C:\OS2INIT.CMD

>Your archiving task will not be done properly !!!
>Do ask for more instructions from your collegues ;-))

>Kind regards, svobi

svobi,

What files do you add to the list above?

FIA for the info.

Jack Huffman

>hmotin@attglobal.net on 25.09.2002 03.45.03
>Please respond to scoug-help@scoug.com
>To: scoug-help@scoug.com
>cc:
>Subject: SCOUG-Help: uninstall of RSJ cd writer program

>I hope the conversation between you and RSJ was sufficiently illuminating
>to both parties, so that they gave you the correct, complete and full
>instructions for editing the CONFIG.SYS. It would be a
>shame, if you edited it and it resulted in a lock up again upon rebooting
>your system. I presume that you have to edit it, then reboot
>in order to THEN activate the "Uninstall" bar on the RSJ
>Installer.
>Right??

>If that is the case, you would be wise to make a copy of your CONFIG.SYS
>right now, because it works right now and provides you a
>fault-free boot
>up. Therefore, if anything bad happens after editing the
>CONFIG.SYS and
>rebooting on the edited file, you can switch back to the good and working
>CONFIG.SYS.

>You can use either of the following 2 text editors (ASCII file editors)
>to edit the CONFIG.SYS: 1.) the OS/2 System Editor
>(...\OS2\E.EXE); or
>2.) the OS/2 Enhanced Editor (do a search for EPM.EXE for the OS/2
>Enhanced Editor exe file. I believe it's located in the ....\OS2\APPS\
>directory (I could be wrong here))

>HCM
>__________________________________________________________________
>____________

>eyeleica@lvcm.com wrote:
>>
>> I've contacted RSJ and they have been quite responsive to my
>questions.
>> They suggested to uninstall first but to do that I have to
>learn to use a
>> text editor to edit config.sys and some other files. Prior to
>editing or
>> part of editing, I must copy the old config.sys (the one with
>RSJ entries)
>> over the current config.sys and then call the installer. The
>uninstall
>> button should be available then. After the uninstall is
>complete, they
>> recommend to install the software, and change config.sys line
>> BASEDEV=LOCKDR.FLT to BASEDEV=LOCKCDR.FLt -n-i:"PLEXTOR CD-R
>> PX-W1610". Then replace the file c:\cdwfs\cddrv.inf with one
>they sent
>> me via zip attachment.
>>
>> After doing that, I reboot and everything should be functional.
> I will do
>> when I can use an editor. You see, I am just at the laying
>prone looking
>> up stage. Crawling will follow.
>>
>> Thanks for the advice. I intend on using RSJ. It looks great.
> My
>> concern is sometimes programs try to do more than necessary and
>become
>> problematic rather than helpful. I had major problems with
>Adaptec CD
>> Record, but when I went to Clone CD, which is a pretty basic
>copy system,
>> no problems.
>>
>> Butch
>>
>> In <3D9053DA.71B07348@attglobal.net>, on 09/24/2002
>> at 08:55 AM, Harry Chris Motin said:
>>
>> >Butch,
>> >Steven is right about the possibility of RSJ installing some
>drivers on
>> >your system, and you should check, just as he suggested.
>However, I
>> >presume that you are using the latest version of RSJ, or
>perhaps the one
>> >just before that. I believe the latest version is 4.04. The
>one before
>> >that was 3.61. I used both versions and (I think) RSJ had
>fixed that
>> >problem by then. Anyway, I had no problems of that sort.
>>
>> >However, you should check, eventually. Since your system now
>boots, it's
>> >less of a priority (I would think! - (that's just my
>thoughts)).
>>
>> >Have you made any final decisions about RSJ? Are you going to
>find out if
>> >your hardware is directly supported? Have you contacted RSJ
>Software,
>> >yet?
>>
>> >If you decide to use RSJ, I can instruct you (later) about
>using
>> >Daniela's drivers to "see" your CD-R/CD-RW unit without having
>to attach
>> >it through the RSJ software. In other words, without this back
>door
>> >through Daniela's drivers, you cannot see or use your
>CD-R/CD-RW unit,
>> >except through the RSJ software. And therefore, you have to
>bring up the
>> >software and "attach" the unit to use it for anything at all.
>Sometimes,
>> >however, you just want to use your unit as a regular CD-ROM
>device, to
>> >read CD-ROM's, not to write them. Without Daniela's back door
>this is not
>> >possible.
>>
>> >Using the back door you will have a new drive icon for the
>unit on you
>> >desktop. The drive letter will be your next alphabet letter.
>Then, if you
>> >want to use the CD unit to write to CD's, you attach it with
>RSJ. Another
>> >drive icon will appear on your desktop. The alphabet letter
>will be "Z",
>> >unless you have changed it to something else in the RSJ
>configuration. If
>> >you open up both drive icons, they will show the exactly the
>same files
>> >and directories.
>>
>> >And of course, now you can use all of the RSJ software
>facilities to
>> >write to CD's and make CD labels, etc.
>>
>> >HCM
>>
>>_________________________________________________________________
>___________
>>
>> >Steven Levine wrote:
>> >>
>> >> In <3D8DCF3E.E993F41E@attglobal.net>, on 09/22/02
>> >> at 06:12 AM, Harry Chris Motin
>said:
>> >>
>> >> >it that do not apply to your unit. There is a chance that
>your RSJ
>> >> >installation replaced some of your previous IDE drivers
>(Steven's idea).
>> >> >I doubt that.
>> >>
>> >> There's always a doubting Harry out there somewhere. :-)
>Take a gander
>> >> at:
>> >>
>> >> http://www.rsj.de/stage/de/cdwriter/chgos2.asp
>> >>
>> >> and note the fix done for v3.51.
>> >>
>> >> >However, we should test it out by comparing your existing
>> >> >CONFIG.SYS to a previous one.
>> >>
>> >> Better to check file dates. IIRC RSJ installed the driver
>to a
>> >> non-standard location, either root or \os2, so check
>everywhere. Also,
>> >> since the driver is a BASEDEV, there's no path to check in
>config.sys.
>> >>
>> >> Steven
>> >>
>> >> --
>> >>
>------------------------------------------------------------------
>---
>> >> "Steven Levine" MR2/ICE 2.31a
>#10183 Warp4/FP15/14.085_W4
>> >> www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
>> >>
>------------------------------------------------------------------
>---

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

>=====================================================

--
-----------------------------------------------------------
jack.huffman@worldnet.att.net
-----------------------------------------------------------

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

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