SCOUG-HELP Mailing List Archives
Return to [ 25 |
April |
2003 ]
<< Previous Message <<
=====================================================
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.
=====================================================
I finally tried to install RSJ tonight without Daniella's back door. It
hung the boot.
After reading some of the SCOUG board emails between you and others, I
added the info necessary to identify my CD-RW drive to the
BASEDEVICE=LOCKCDR.FLT line. That took care of the hang, but the boot
still stopped with the statement that rsjscsi.sys was not installed in
G:\CDWFS (my location for RSJ) and that the line
DEVICE=G:\CDWFS\RSJSCSI.SYS was being ignored. Booting resumed when I hit
enter.
But the file is in that directory. So I don't understand what is going
on.
Maybe the problem is my cddrv.inf file. It is 15425 bytes and is dated
3-12-02, 11:29:06. If the one you received from RSJ is newer, will you
please send me a copy.
Or, if you think my problem is something else, please tell me what it is.
Thank you.
Jack
In <200304152003.3659918.8@scoug.com>, on 04/15/2003
at 08:03 PM, "Harry Motin" said:
>Jack,
>Did you ever get RSJ installed? Did you install Daniela's "backdoor" for
>RSJ? HCM
>On Tue, 15 Apr 2003 19:32:40 PDT, jack.huffman@worldnet.att.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.
>>=====================================================
>>
>>In , on 04/15/2003
>> at 04:47 PM, "Steven Levine" said:
>>
>>
>>>In <200304151500.3934043.6@scoug.com>, on 04/15/03
>>> at 03:00 PM, jack.huffman@worldnet.att.net said:
>>
>>>>11-APR-03 00:07:24 [id=8000] Backup for set 'BABKUP1' started. 11-APR-03
>>>>00:07:32 [id=0200] [rc1=0002 rc2=0000] [OS/2 API error code = 3 (x0003)]
>>>>An unexpected device error has occurred. Please collect all relevant
>>>>information and contact technical support for further assistance.
>>>>11-APR-03 00:08:02 [id=8003] Total active time for operation : 0:00.
>>>>11-APR-03 00:08:02 [id=8004] Total idle time for operation : 0:38.
>>>>11-APR-03 00:08:02 [id=8005] Total elapsed time for operation : 0:38.
>>>>11-APR-03 00:08:02 [id=8007] Processed 0.0 MB in 0 files. 11-APR-03
>>>>00:08:02 [id=8400] Backup aborted.
>>
>>>>BABKUP1 set looks like this:
>>
>>>A couple of things. Make sure you have applied all the patches to v3.0,
>>>just to be safe.
>>
>>>Since you are backing up to hard disk, you need to limit each container
>>>(i.e. backup.dat) to 2GB. I suspect you are exceeding this. Use the
>>>estimate options to see if this is the case. If so, just create multiple
>>>backup set and keep each the container below 2GB.
>>
>>>>I emailed this info to tech support but have not heard anything from
>>>>them. Since they usually reply promptly, I guess they are overloaded or
>>>>stumped.
>>
>>>They might be a bit busy with support for the new version. v3.0 has been
>>>out of support for a while, but they probably will reply eventually.
>>
>>>Steven
>>
>>Steven,
>>
>>Hooray and thanks a million! BAII worked. After 13 years of never
>>backing up, I did a zip backup last October and will make a full backup
>>now so I can run DFsee. Lousing up the hard drive as I did and your
>>strictures about backing up took hold.
>>
>>Since there were only 1.2 megs of files in all the drives, upgrading to v.
>>3.00a did the trick.
>>
>>I am curious about these three entried in the backup set.
>>
>>[ExcPatt_1]
>> FileSpec = *\swapper.dat
>> Recursive = On
>> HideFromUser = On
>>
>>[ExcPatt_2]
>> FileSpec = *\ea data. sf
>> Recursive = On
>> HideFromUser = On
>>
>>[ExcPatt_3]
>> FileSpec = *\wp data. sf
>> Recursive = On
>> HideFromUser = On
>>
>>It looks like the ea's and whatever is in wp data. sf was not copied.
>>Does Warp 4 create them when the files are restored?
>>
>>I plan to check the restore option by backing up one partition and
>>restoring it with a write over everything instruction and then verify that
>>the number of bytes before backup and after restore are the same. Is that
>>an adequate test? Is it enough to check the byte totals before and after
>>on ZTreeBold or is there a better way to make that check?
>>
>>Thanks again.
>>
>>Jack
>>
>>-----------------------------------------------------------
>>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".
>>
>>=====================================================
>>
>>
>=====================================================
>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 <<
Return to [ 25 |
April |
2003 ]
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.
|