[Simh] RSTS/E v96 installation

Wed Mar 12 16:41:20 EDT 2008

After reading this thread I decided I would take a stab at install BP2 
as I have wanted to do for some time.  I guess it has been a very long 
time since I last touched a production RSTS/E system in 1985.  I spent 
about 1/2 hour trying to get the BP2_V2_7.tap file to install with no 
luck.  I could run a directory listing without any problem and I see the 
save sets but [0,1]INSTAL.COM is not happy with the install.  23 years 
ago I could probably have whipped it off easily enough but I have spent 
too much time since then at the C:\ , VMS $ and Bourne shell prompts.

When I have a little less on my plate I may take stab at it again.

Regards, Robert

Bill Heaton wrote:
> Hi Fausto,
>
> Sorry, I don't have a lot of experience with the layered products.  As  
> soon as I get the RSTS V9 Archive into reasonable shape, I'll be  
> heading in that direction.  There are several of the layered products  
> that I want to play with (again).  You may want to give the list more  
> information of what's happening and perhaps one of us will remember  
> something.
>
> If you get it working. Don't forget to generate a "How-to" so that  
> others can benefit!
>
> Regards, Bill
>
> On Mar 12, 2008, at 12:01 PM, Fausto Saporito wrote:
>
>   
>> Hello Bill, hello all,
>>
>> thanks for your replies.
>> If I understood well I need a separate installation tape for the
>> layered products, i.e. fortran77
>>
>> I found some of them in the trailing-edge ftp site, and I tried
>> several of them:
>>
>> 1) bb-k400f-bc_pdp_f77_rsts_v5_3_c1988.tap.bz2
>> 2) f77_v5_3.zip
>> 3) fortran-77_v5_4.zip
>>
>> the first two packages are in .bck format, and they don't have a CTL
>> file usable with RSTS/E BUILD command.
>> The last one has a .bck and .a saveset (remember me VMS saveset) and
>> no CTL file.
>>
>> All of them have a .COM installation procedure, but it fails. I
>> suppose that procedure (FRTRN77.COM) needs to be used within another
>> procedure/command.
>>
>> I found just one installation  document on bitsavers.org, but it
>> refers to a F77 installation under RSTS/E v7 and it uses only the
>> "BUILD" command.
>>
>> Do you have any suggestions about this kind of installation?
>>
>> thanks,
>> fausto
>>
>> Quoting Bill Heaton <wheaton at cryptocybernetics.com>:
>>
>>     
>>> Hi Fausto,
>>>
>>> I'm currently writing a How-To on sysgening RSTS/E V9.6 and can
>>> say that your on the right track.  I think that what's its saying  
>>> is that
>>> those tasks haven't changed.
>>>
>>> Using the TU tape drive is slightly easier.  Here's my config that  
>>> I'm
>>> using to successfully sysgen the system.  Once your up, use DB0:
>>> as your system device.  MM0: for the first tape, and MM1: for the
>>> second tape.
>>>
>>> BTW: for those that are wondering.  I have all the piece for my first
>>> release together.  Calling it the "RSTS V9 Archive".   Well over the
>>> 50% mark for getting it out to the world.  I'm still tuning the  
>>> sysgen.
>>>
>>> Regards, Bill
>>>
>>> rsts-sysgen.ini
>>> ============
>>>
>>> ; Disable devices, we'll enable what we need later
>>> set CR disable
>>> set DZ disable
>>> set HK disable
>>> set RK disable
>>> set RL disable
>>> set RP disable
>>> set RQ disable
>>> set RQB disable
>>> set RQC disable
>>> set RQD disable
>>> set RX disable
>>> set RY disable
>>> ;set TA disable
>>> set TC disable
>>> set TM disable
>>> set TS disable
>>> set TQ disable
>>> set TU disable
>>> set VH disable
>>> set XQ disable
>>> set XQB disable
>>> set XU disable
>>> set XUB disable
>>>
>>> echo PDP-11/93 with 4 meg of memory
>>> echo
>>> set cpu 11/93
>>> set cpu 4m
>>> set cpu cis
>>>
>>> set RP enable
>>> set RP0 RP04
>>> attach RP0 RSTS_V9.RP04
>>> echo RSTS_V9.RP04 mounted on RP0: (DB0:)
>>>
>>> set TU enable
>>> set TU0 locked
>>> set TU1 locked
>>> attach TU0 rsts_v9_6_install.tap
>>> attach TU1 rsts_v9_library.tap
>>> echo rsts_v9_6_install.tap mounted on TU0 (MM0:)
>>> echo rsts_v9_library.tap mounted on TU1 (MM1:)
>>>
>>> echo
>>> echo "boot tu" to boot tape
>>> echo "boot rp" to boot disk
>>>
>>>
>>>
>>> On Mar 12, 2008, at 11:06 AM, Fausto Saporito wrote:
>>>
>>>       
>>>> Hello all,
>>>>
>>>> I'm installing the RSTS/E v9.6, unfortunately I don't have the right
>>>> installation document, and I'm using that one related to RSTS/E 9.7
>>>>
>>>> During the installation I have the following request:
>>>>
>>>> Please mount the RSTS/E Library media and enter the
>>>> name and unit number of the device.
>>>> Valid device types are: 'MM', 'MS', 'MT', 'MU', 'DM' or 'DL'
>>>>
>>>> Library device? <_MU0:>
>>>>
>>>> What's this library media? I found in the trailing-edge ftp  
>>>> directory,
>>>> a rsts_v9_library.zip
>>>> Is this the correct file? Or is it too old?
>>>>
>>>> If I use it, I have the following:
>>>>
>>>> Restoring the System Startup files from the Library kit
>>>> Restoring the System Library package from the Library kit
>>>> File [1,2]LOGIN .TSK not replaced
>>>> File [1,2]LOGOUT.TSK not replaced
>>>> File [1,2]DIRECT.TSK not replaced
>>>> File [1,2]SYSTAT.TSK not replaced
>>>> File [1,2]FILCOM.TSK not replaced
>>>> File [1,2]ATPK  .TSK not replaced
>>>> File [1,2]SAVRES.SAV not replaced
>>>> File [1,2]TERMGR.TSK not replaced
>>>> File [1,2]RDRXXX.TSK not replaced
>>>> File [1,2]RDRIDS.TSK not replaced
>>>>
>>>> etc...
>>>>
>>>> Is it normal?
>>>>
>>>> After it, the installation seems to be fine, but F77, for example,  
>>>> is
>>>> not installed, even if I choiced to install it.
>>>>
>>>> thanks,
>>>> fausto
>>>> _______________________________________________
>>>> Simh mailing list
>>>> Simh at trailing-edge.com
>>>> http://mailman.trailing-edge.com/mailman/listinfo/simh
>>>>
>>>>         
>> _______________________________________________
>> Simh mailing list
>> Simh at trailing-edge.com
>> http://mailman.trailing-edge.com/mailman/listinfo/simh
>>
>>     
>
> _______________________________________________
> Simh mailing list
> Simh at trailing-edge.com
> http://mailman.trailing-edge.com/mailman/listinfo/simh
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20080312/a10efff8/attachment-0003.html>