27 May
2019
27 May
'19
6:58 a.m.
Hi
??? Whilst I wait to hear from Glen Slick who has got me this far
(Thanks Glen) I'll restate the problem.
1. I now have an old XP system with SIMH on it (PDP11.exe)
2.? I have created RD54.dsk containing RSTS/E
3. Attached to the system is a 2.1Gb SCSI drive via an adaptec 2940
controller
4. I need a tried and tested list of step by step instructions to put
RD54.dsk on the SCSI drive.
5. The drive will then be moved to a CQD-220A/TM SCSI controller on my
KDJ11-E based 11/93 and must boot.
6. Its just an image copy from one drive to another on the same system.
7. Nobody has come up with a tried and tested list of step by step
instructions yet.
Rod Smallwood
--
27 May
27 May
9:14 a.m.
Rod Smallwood via cctalk wrote:
Hi
??? Whilst I wait to hear from Glen Slick who has got me this far
(Thanks Glen) I'll restate the problem.
1. I now have an old XP system with SIMH on it (PDP11.exe)
2.? I have created RD54.dsk containing RSTS/E
3. Attached to the system is a 2.1Gb SCSI drive via an adaptec 2940
controller
4. I need a tried and tested list of step by step instructions to put
RD54.dsk on the SCSI drive.
5. The drive will then be moved to a CQD-220A/TM SCSI controller on my
KDJ11-E based 11/93 and must boot.
6. Its just an image copy from one drive to another on the same system.
7. Nobody has come up with a tried and tested list of step by step
instructions yet.
Rod Smallwood
I don't think that you have any chance to get that to work, since the
data structures on the floppy disk will be different to that needed
structure on the scsi disk. As far as I know the controllers put some
kind of partitioning information to the disks too...
I've installed different PDP11 Os'es from simh to the real
pdp11/(53,73,83) using simh's tape interface writing boot tapes.
I've converted the simh's tape file with my own utility to an qarter
inch tape connected to an Tandberg SLR5 to my FreeBSD box. as far as I
know in the meantime there exists an utility similar to mine that could
write out tapes from a tape file.
I've connected another SLR5 drive to the PDP11 box with an Emulex UC08,
Im sure that will work on the CQD220 too.
An Tandberg SLR5 and Tapes should be easy to et on ebay.
I've installed RT11, RSX11, XXDP and 2.11BSD this way.
Regards,
Holm
--
Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe,
Freiberger Stra?e 42, 09600 Obersch?na, USt-Id: DE253710583
info at tsht.de Fax +49 3731 74200 Tel +49 3731 74222 Mobil: 0172 8790 741
10:20 a.m.
On May 27, 2019, at 12:14 PM, Holm Tiffe via cctalk
<cctalk at classiccmp.org> wrote:
Rod Smallwood via cctalk wrote:
Floppy? I don't see that mentioned.
RSTS can handle image copies without trouble if the sizes match, or if destination is
slightly bigger.
Partitions -- there is no such thing on RSTS.
Writing disks is no problem if you have a program that can write raw block devies, and an
OS that lets you do this. Sufficiently old Windows can do this via the BIOS I/O
machinery; I've done it for RX50 floppies though not for hard drives (don't have
any).
RX50 floppies do have two complications: 10 sectors per track rather than the PC standard
9, and a sector layout with interleaving and track skew. It's not hard to deal with
this in software once you have the details reverse engineered. FLX does this, it's
how I've created PRO boot floppies on my PC.
paul
Hi
Whilst I wait to hear from Glen Slick who has got me this far
(Thanks Glen) I'll restate the problem.
1. I now have an old XP system with SIMH on it (PDP11.exe)
2. I have created RD54.dsk containing RSTS/E
3. Attached to the system is a 2.1Gb SCSI drive via an adaptec 2940
controller
4. I need a tried and tested list of step by step instructions to put
RD54.dsk on the SCSI drive.
5. The drive will then be moved to a CQD-220A/TM SCSI controller on my
KDJ11-E based 11/93 and must boot.
6. Its just an image copy from one drive to another on the same system.
7. Nobody has come up with a tried and tested list of step by step
instructions yet.
Rod Smallwood
I don't think that you have any chance to get that to work, since the
data structures on the floppy disk will be different to that needed
structure on the scsi disk. As far as I know the controllers put some
kind of partitioning information to the disks too... 
9:22 a.m.
On Mon, May 27, 2019 at 6:58 AM Rod Smallwood via cctalk
<cctalk at classiccmp.org> wrote:
Hi
Whilst I wait to hear from Glen Slick who has got me this far
(Thanks Glen) I'll restate the problem.
1. I now have an old XP system with SIMH on it (PDP11.exe)
2. I have created RD54.dsk containing RSTS/E
3. Attached to the system is a 2.1Gb SCSI drive via an adaptec 2940
controller
4. I need a tried and tested list of step by step instructions to put
RD54.dsk on the SCSI drive.
5. The drive will then be moved to a CQD-220A/TM SCSI controller on my
KDJ11-E based 11/93 and must boot.
6. Its just an image copy from one drive to another on the same system.
7. Nobody has come up with a tried and tested list of step by step
instructions yet.
OK, now that you have an RD54 disk image and a 2GB SCSI drive attached
to an Adaptec 2940 controller on a Windows XP system, the first thing
I would do is resize the capacity of the 2GB SCSI drive to match the
capacity of an RD54 drive.
To do that, I would download sg3_utils ( http://sg.danny.cz/sg/sg3_utils.html ).
Specifically I would download version 1.37 of the Windows binaries here:
http://sg.danny.cz/sg/p/sg3_utils-1.37exe.zip
The current version is 1.44, which I have not tried yet. The last time
I tried version 1.42 I had some issues so I went back to version 1.37
so that I what I suggest for now.
The RD54 disk image that was previously created has a block size of
311,200 and a byte size of 159,334,400.
The goal in this step is to resize the capacity of the SCSI drive so
that when it is attached to CMD CQD-220, the capacity of the drive as
reported through the MSCP interface will match that of the RD54 disk
image. What I have observed with the CMD CQD-220 controllers that I
have is that they report a capacity of 2 blocks smaller through the
MSCP interface than the SCSI drive reports. That is with the CMD
CQD-220 controller reset to default settings of a single unit for the
drive, not split into 2 or 4 units.
So the SCSI drive should report a capacity of 311,202 (311,200 + 2)
blocks in this case.
With the sg3_utils-1.37 binaries download and extracted on your
Windows XP system with the 2GB SCSI drive connected to the AHA-2940
controller, you could do this:
// Use sg_scan to see what drives are attached. In this example
physical drive "PD1" is the target drive. This will vary depending on
the configuration of your system. Find the physical drive name entry
that matches your target drive.
C:\sg3_utils-1.37>sg_scan
PD0 [C] HDS728040PLAT20 PF1OA21B
PD1 COMPAQPC DDRS-39130W S99C
CDROM0 [Z] TEAC CD-224E 1.7A
// Use sg_inq to send a SCSI Inquiry command to the physical drive to
verify that the vendor and product information seems correct for the
target drive. If you don't want to be making changes to the wrong
drive.
C:\sg3_utils-1.37>sg_inq pd1
standard INQUIRY:
PQual=0 Device_type=0 RMB=0 version=0x02 [SCSI-2]
[AERC=0] [TrmTsk=0] NormACA=0 HiSUP=0 Resp_data_format=2
SCCS=0 ACC=0 TPGS=0 3PC=0 Protect=0 [BQue=0]
EncServ=0 MultiP=0 [MChngr=0] [ACKREQQ=0] Addr16=0
[RelAdr=0] WBus16=1 Sync=1 Linked=1 [TranDis=0] CmdQue=1
[SPI: Clocking=0x0 QAS=0 IUS=0]
length=164 (0xa4) Peripheral device type: disk
Vendor identification: COMPAQPC
Product identification: DDRS-39130W
Product revision level: S99C
Unit serial number: REGA0360
// Use sg_readcap to send a SCSI Read Capacity command to the physical
drive. Make a note of the current number of blocks and write that down
in case you might want to return the drive to its native capacity
sometime later.
C:\sg3_utils-1.37>sg_readcap pd1
Read Capacity results:
Last logical block address=17773499 (0x10f33bb), Number of blocks=17773500
Logical block length=512 bytes
Hence:
Device size: 9100032000 bytes, 8678.47 MiB, 9.10003 GB
// Ok, now time to actually use sg_format --resize to change the
reported capacity of the drive. The --resize option does not do a low
level format of the drive. It uses a SCSI Mode Select command to
change the capacity of the drive as reported by a SCSI Read Capacity
command. Here the block count is 311,202 (311,200 + 2) blocks.
C:\sg3_utils-1.37>sg_format --count=311202 --resize --verbose pd1
inquiry cdb: 12 00 00 00 24 00
COMPAQPC DDRS-39130W S99C peripheral_type: disk [0x0]
PROTECT=0
mode sense (10) cdb: 5a 00 01 00 00 00 00 00 fc 00
mode sense (10): pass-through requested 252 bytes but got 28 bytes
Mode Sense (block descriptor) data, prior to changes:
Number of blocks=17773500 [0x10f33bc]
Block size=512 [0x200]
mode select (10) cdb: 55 11 00 00 00 00 00 00 1c 00
Resize operation seems to have been successful
// Use sg_readcap again to verify that the change took effect as
desired. The new disk size of 159,335,424 bytes is 1024 (2 blocks)
larger than the disk image size 159,334,400
C:\sg3_utils-1.37>sg_readcap pd1
Read Capacity results:
Last logical block address=311201 (0x4bfa1), Number of blocks=311202
Logical block length=512 bytes
Hence:
Device size: 159335424 bytes, 151.954 MiB, 0.159335 GB
// sg_format --resize has worked with the drives that I have tried. I
suppose that it is possible that some drives might not support this.
10:23 a.m.
On Mon, May 27, 2019 at 6:58 AM Rod Smallwood via cctalk
<cctalk at classiccmp.org> wrote:
Hi
Whilst I wait to hear from Glen Slick who has got me this far
(Thanks Glen) I'll restate the problem.
1. I now have an old XP system with SIMH on it (PDP11.exe)
2. I have created RD54.dsk containing RSTS/E
3. Attached to the system is a 2.1Gb SCSI drive via an adaptec 2940
controller
4. I need a tried and tested list of step by step instructions to put
RD54.dsk on the SCSI drive.
5. The drive will then be moved to a CQD-220A/TM SCSI controller on my
KDJ11-E based 11/93 and must boot.
6. Its just an image copy from one drive to another on the same system.
7. Nobody has come up with a tried and tested list of step by step
instructions yet.
After using sg3_utils sg_format to resize the capacity of the the SCSI
drive to match the size of the RD54 disk image, you can the use
something equivalent to 'dd' to copy the RD54 disk image to the SCSI
drive. On a Windows system I use a simple utility I wrote myself years
ago. I will send Rod a copy of that directly off list. Similar
utilities can be found online if you search around. I haven't found
any that I will recommend myself.
After the RD54 disk image has been copied to the physical SCSI drive
on your Windows system, move it over to the PDP-11/93 system with the
CMD CQD-220 controller. Use the CQD-220 firmware utilities to check
that the SCSI drive is recognized and configured as a single DU unit.
It might be a good idea to use the 'Z' configuration option to reset
the controller to the default settings. The output below was from a
CQD-220. The firmware on your CQD-220A may differ slightly with more
options, but it is the same general idea.
SCSI HOST ADAPTER UTILITY (REV. A8)
[ DISK ] : [ TAPE ]
1 = LOGICAL UNIT NUMBER OFFSET : 6 = LOGICAL UNIT NUMBER OFFSET
2 = FORMAT DRIVE : 7 = ADDITIONAL UTILITIES
3 = QUALIFY DRIVE :
4 = MANUALLY REPLACE BAD BLOCKS :
5 = ADDITIONAL UTILITIES :
SELECT OPTION ? 5
ADDITIONAL UTILITIES (REV. A8) SN = 9478
D = DISPLAY SCSI DEVICE & SETUP CONFIGURATION
S = SEND SCSI COMMAND TO THE DEVICE
T = TEST SCSI DEVICE
R = FORMAT RCT BLOCK
SELECT OPTION ? D
CURRENT CONFIGURATION :
DEV0: DU0 SCSI ID 0 LUN 0
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Write W/Verify OFF,
DEV1: DU1 SCSI ID 1 LUN 0
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Write W/Verify OFF,
DEV2: DU2 SCSI ID 2 LUN 0
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Write W/Verify OFF,
DEV3: DU3 SCSI ID 3 LUN 0
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Write W/Verify OFF,
DEV4: MU0 SCSI ID 4 LUN 0
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Buffer Mode ON,
DEV5: MU1 SCSI ID 5 LUN 0
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Buffer Mode ON,
DEV6: MU2 SCSI ID 6 LUN 0
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Buffer Mode ON,
DEV7 SCSI ID 7 HOST ADAPTER, SCSI Reset ON,Density Mode ON,
CHANGE CONFIGURATION ? (Y/N) Y
R = Toggle SCSI Reset, M = Toggle Density Mode
D = Toggle Disconnect, B = Toggle Buffer Mode (Tape only)
S = Toggle Sync/Async, W = Toggle Write w/Verify (Disk only)
C = Reconfigure Device, P = Toggle Prevent Medium Removal
T = Reset All Device Modes to Default
Z = Reset Controller to Default Configuration
SELECT OPTION ? Z
DEV0: DU0 SCSI ID 0 LUN 0
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Write W/Verify OFF,
DEV1: DU1 SCSI ID 1 LUN 0
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Write W/Verify OFF,
DEV2: DU2 SCSI ID 2 LUN 0
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Write W/Verify OFF,
DEV3: DU3 SCSI ID 3 LUN 0
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Write W/Verify OFF,
DEV4: MU0 SCSI ID 4 LUN 0
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Buffer Mode ON,
DEV5: MU1 SCSI ID 5 LUN 0
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Buffer Mode ON,
DEV6: MU2 SCSI ID 6 LUN 0
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Buffer Mode ON,
DEV7 SCSI ID 7 HOST ADAPTER, SCSI Reset ON,Density Mode ON,
CHANGE CONFIGURATION ? (Y/N) N
SCANNING SCSI DEVICES ATTACHED ...
DEV0: DU0 SCSI ID 0 LUN 0 COMPAQPCDDRS-39130W S99C
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Write W/Verify OFF,
DEV1: DU1 SCSI ID 1 LUN 0 OFFLINE
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Write W/Verify OFF,
DEV2: DU2 SCSI ID 2 LUN 0 OFFLINE
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Write W/Verify OFF,
DEV3: DU3 SCSI ID 3 LUN 0 OFFLINE
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Write W/Verify OFF,
DEV4: MU0 SCSI ID 4 LUN 0 OFFLINE
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Buffer Mode ON,
DEV5: MU1 SCSI ID 5 LUN 0 OFFLINE
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Buffer Mode ON,
DEV6: MU2 SCSI ID 6 LUN 0 OFFLINE
Disconnect ON,Sync Mode ON,Prevent Medium Removal ON,Buffer Mode ON,
DEV7 SCSI ID 7 HOST ADAPTER, SCSI Reset ON,Density Mode ON,
CHANGE CONFIGURATION ? (Y/N) N
Then boot from DU0, and if everything worked along the way it should
just work. Assuming it boots OK into RSTS/E 10.0, use the SHOW DISK
command to verify that the reported disk size is the expected 311200
blocks.
The output below is booting from the SCSI disk on a KDJ11-D 11/53.
9 8 7 6 5 4 3 2 1
Commands are Help, Boot, List, Map, Test and Wrap.
Type a command then press the RETURN key: BOOT DU0
DU0
RSTS V10.0-L RSTS (DU0) INIT V10.0-0L
Today's date? 19.5.27
Current time? 9:50
Start timesharing? <Yes>
Default memory allocation table shows MORE
memory than INIT detects on this machine.
Adjusting memory table.
Memory allocation table:
0K: 00000000 - 00503777 ( 81K) : EXEC
81K: 00504000 - 01547777 ( 137K) : USER
218K: 01550000 - 03777777 ( 294K) : XBUF
512K: 04000000 - 05777777 ( 256K) : USER
768K: 06000000 - 17757777 (1276K) : NXM
Memory available to RSTS/E is 768K words.
;9.05.27 09:50
Proceed with system startup? <YES>
Beginning RSTS/E system startup...
19.05.27 09:50 Installing monitor overlays
19.05.27 09:50 Mounting disks
19.05.27 09:50 Assigning logical names
19.05.27 09:50 Starting error logging
19.05.27 09:50 Setting system characteristics
27-May-19 09:50 AM Installing run-time systems and libraries
27-May-19 09:50 AM Starting Operator/Message Services
?Invalid time
?Undefined symbol
?Undefined symbol
>>>>>>>>>>>>>> OMS V10.0-K 27-May-19 09:50 AM
<<<<<<<<<<<<<<<
Message 4 from OMS,
user [1,2], Detached, job 3
Starting Operator/Message Services
27-May-19 09:50 AM Setting terminal characteristics
27-May-19 09:50 AM Defining system commands
27-May-19 09:50 AM Setting printer characteristics
27-May-19 09:50 AM Starting spoolers
*** From [1,2] on KB0: at 09:50 AM 27-May-19
** RSTS/E is on the air...
>>>>>>>>>>>>>> OMS V10.0-K 27-May-19 09:51 AM
<<<<<<<<<<<<<<<
Message 5 from user
[1,2] on _KB0:, job 2
The system startup is complete
RSTS V10.0-L 27-May-19 09:51 AM
User: 1,2
Password:
Jobs detached under this account:
Job What Size State Run-time RTS
1 ERRCPY 5K SR 15.7 ...RSX
3 OMS 9K SL 1.7 ...RSX
4 PBS... 18K SL 1.8 ...RSX
Job number to attach to?
Last interactive login on 27-May-19, 09:50 AM at KB0:
Last non-interactive login on 27-May-19, 09:50 AM
3 other users are logged in under this account
$ SHOW DISK
Disk Structure:
Dsk Open Size Free Clu Err Name Level Comments
DU0 22 311200 256560 82% 8 0 RSTS10 1.2 Pub, DLW
$ SHOW SYSTEM
System name: RSTS V10.0-L RSTS/E V10.0
Currently installed Monitor: RSTS
Swap Maximum: 66K
Date format: Alphabetic
Time format: AM_PM
Magtape label default: DOS
Magtape density default: 1600 BPI
Power fail restart delay: 300 seconds
Dynamic Region Limit: 0K words
Hangup: Delayed
Monitor Statistics: Disabled
Job limit: 63
Current jobs: 4
Password Prompting: Network and Dialup users
LAT Software: Not Installed Upon reboot: installed
FMS Software: Not Installed
Current Pseudo keyboards: 4
Answerback message: None
$ RUN SHUTUP
SHUTUP V10.0-K RSTS V10.0-L RSTS/E V10.0
09:51 AM 27-May-19 ######## Set-up Dialogue Phase ########
Type '^' to any query to backup one question
Allow Print/Batch Services jobs to complete <YES>?
Minutes until system shutdown (0-99) <5>?
Minutes until logins are disabled (0-4) <0>?
Shutdown with automatic RESTART <NO>?
09:51 AM 27-May-19 ######## Warning Message Phase ########
5 minute warning message sent
Further LOGINs are now disabled
3 minute warning message sent
2 minute warning message sent
1 minute warning message sent
09:56 AM 27-May-19 ######## Initial Job Killing Phase ########
09:56 AM 27-May-19 ######## Print/Batch Shutdown Phase ########
Print/Batch Services shutdown complete at 09:56 AM
09:56 AM 27-May-19 ######## OMS Shutdown Phase ########
>>>>>>>>>>>>>> OMS V10.0-K 27-May-19 09:56 AM
<<<<<<<<<<<<<<<
Message 6 from SHUTUP,
operator [1,2] on _KB0:, job 2
Operator/Message Services shutting down
Operator/Message Services shutdown complete at 09:56 AM
09:56 AM 27-May-19 ######## EVTLOG Shutdown Phase ########
09:56 AM 27-May-19 ######## ERRCPY Shutdown Phase ########
09:56 AM 27-May-19 ######## Remove RTS/RES LIB Phase ########
09:56 AM 27-May-19 ######## Log File Closing Phase ########
09:56 AM 27-May-19 ######## SWAP File Removal Phase ########
09:56 AM 27-May-19 ######## Disk DISMOUNT Phase ########
09:56 AM 27-May-19 ######## Final Shutdown Phase ########
Please wait for system to re-boot itself
RSTS V10.0-L RSTS (DU0) INIT V10.0-0L
;9.05.27 09:57
Start timesharing? <Yes> NO
Option: <Start> HARDWARE
HARDWR suboption? LIST
Name Address Vector Comments
TT0: 177560 060
RU0: 172150 P310 UDA50 Units: 0(RA80)
MU0: 174500 P314 TU81 Units: 0(TU81)
KL0: 176500 300
KW11L 177546 100 (Write-only)
Hertz = 50.
Other: FPU, 22-Bit, Data space, J11-D CPU
HARDWR suboption?
Option: <Start>
10:37 a.m.
On May 27, 2019, at 1:23 PM, Glen Slick via cctalk
<cctalk at classiccmp.org> wrote:
...
Then boot from DU0, and if everything worked along the way it should
just work. Assuming it boots OK into RSTS/E 10.0, use the SHOW DISK
command to verify that the reported disk size is the expected 311200
blocks.
Nice.
You can run the file system checker -- in INIT, to the "start timesharing"
prompt, answer "refresh", then <ret> for the system disk, and when asked
"Rebuild" say yes. It should complete with no complaints.
The output below is booting from the SCSI disk on a
KDJ11-D 11/53.
9 8 7 6 5 4 3 2 1
Commands are Help, Boot, List, Map, Test and Wrap.
Type a command then press the RETURN key: BOOT DU0
DU0
RSTS V10.0-L RSTS (DU0) INIT V10.0-0L
Today's date? 19.5.27
Current time? 9:50
...
;9.05.27 09:50
Hm, Y2K bug in that version?
Proceed with system startup? <YES>
Beginning RSTS/E system startup...
19.05.27 09:50 Installing monitor overlays
19.05.27 09:50 Mounting disks
19.05.27 09:50 Assigning logical names
19.05.27 09:50 Starting error logging
19.05.27 09:50 Setting system characteristics
27-May-19 09:50 AM Installing run-time systems and libraries
27-May-19 09:50 AM Starting Operator/Message Services
?Invalid time
?Undefined symbol
?Undefined symbol
This says there's some stuff in your start.com that RSTS is not happy with, but
it's not clear what that might be. It doesn't seem to cause any real problems.
paul
10:55 a.m.
On Mon, May 27, 2019 at 10:37 AM Paul Koning <paulkoning at comcast.net> wrote:
It was installed from the RSTS/E 10.0 tape image that recently
(2019-05-09) appeared on Bitsavers:
http://www.bitsavers.org/bits/DEC/pdp11/rsts/RSTS_V10.ZIP
I have installed from a RSTS/E 10.1 tape image in the past and I seem
to remember it being more Y2K friendly. I used the Bitsavers 10.0 tape
image as an example here because the 10.1 tape image source that I
previously used was not public at the time to provide a link.
Yeah, those messages bug me slightly and I should try to figure out
what they mean. I don't remember seeing those when I used a 10.1
install. I just wanted to get this example out there for Rod now, and
worry about clean up issues later.
Thanks.
RSTS V10.0-L RSTS (DU0) INIT V10.0-0L
Today's date? 19.5.27
Current time? 9:50
...
;9.05.27 09:50
Hm, Y2K bug in that version?
Proceed with
system startup? <YES>
Beginning RSTS/E system startup...
19.05.27 09:50 Installing monitor overlays
19.05.27 09:50 Mounting disks
19.05.27 09:50 Assigning logical names
19.05.27 09:50 Starting error logging
19.05.27 09:50 Setting system characteristics
27-May-19 09:50 AM Installing run-time systems and libraries
27-May-19 09:50 AM Starting Operator/Message Services
?Invalid time
?Undefined symbol
?Undefined symbol
This says there's some stuff in your start.com that RSTS is not happy with, but
it's not clear what that might be. It doesn't seem to cause any real problems.
11:15 a.m.
On Mon, May 27, 2019 at 10:37 AM Paul Koning <paulkoning at comcast.net> wrote:
It appears that the first two errors are related to a Y2K issue.
The third error appears to be related to "OMS$:REQLOG.OMS". I barely
know my way around RSTS/E and don't know what that might be without
further investigation.
Proceed with system startup? <YES>
Beginning RSTS/E system startup...
19.05.27 09:50 Installing monitor overlays
19.05.27 09:50 Mounting disks
19.05.27 09:50 Assigning logical names
19.05.27 09:50 Starting error logging
19.05.27 09:50 Setting system characteristics
27-May-19 09:50 AM Installing run-time systems and libraries
27-May-19 09:50 AM Starting Operator/Message Services
?Invalid time
?Undefined symbol
?Undefined symbol
This says there's some stuff in your start.com that RSTS is not happy with, but
it's not clear what that might be. It doesn't seem to cause any real problems.
From start.log:
$ ! *** Start Operator/Message Services ***
$ !
$ OMS_ON := FALSE
$ _write 0 f$time()+ " Starting Operator/Message Services"
27-May-19 11:04 AM Starting Operator/Message Services
$ Today = F$Left(F$CVTime(), 8)
$ Today = F$Left(F$CVTime(), 8)
?Invalid time
$ File = F$Left(Today, 2) + F$Mid(Today, 4, 2) + F$Right(Today, 7)
$ File = F$Left(Today, 2) + F$Mid(Today, 4, 2) + F$Right(Today, 7)
^
?Undefined symbol
$ _if F$Search("OMS$:REQLOG.OMS") .nes. "" Then -
Continue: _Rename/NoWarn OMS$:REQLOG.OMS 'File'
$ _if F$Search("OMS$:REQLOG.OMS") .nes. "" Then
_Rename/NoWarn
OMS$:REQLOG.OMS 'File'
^
?Undefined symbol
11:26 a.m.
On May 27, 2019, at 2:15 PM, Glen Slick via cctalk
<cctalk at classiccmp.org> wrote:
On Mon, May 27, 2019 at 10:37 AM Paul Koning <paulkoning at comcast.net> wrote:
It appears that the first two errors are related to a Y2K issue.
The third error appears to be related to "OMS$:REQLOG.OMS". I barely
know my way around RSTS/E and don't know what that might be without
further investigation.
From start.log:
$ ! *** Start Operator/Message Services ***
$ !
$ OMS_ON := FALSE
$ _write 0 f$time()+ " Starting Operator/Message Services"
27-May-19 11:04 AM Starting Operator/Message Services
$ Today = F$Left(F$CVTime(), 8)
$ Today = F$Left(F$CVTime(), 8)
?Invalid time
Looks like f$cvtime is failing, that's presumably a Y2K issue.
Proceed with system startup? <YES>
Beginning RSTS/E system startup...
19.05.27 09:50 Installing monitor overlays
19.05.27 09:50 Mounting disks
19.05.27 09:50 Assigning logical names
19.05.27 09:50 Starting error logging
19.05.27 09:50 Setting system characteristics
27-May-19 09:50 AM Installing run-time systems and libraries
27-May-19 09:50 AM Starting Operator/Message Services
?Invalid time
?Undefined symbol
?Undefined symbol
This says there's some stuff in your start.com that RSTS is not happy with, but
it's not clear what that might be. It doesn't seem to cause any real problems.
$ File = F$Left(Today, 2) + F$Mid(Today, 4, 2) +
F$Right(Today, 7)
$ File = F$Left(Today, 2) + F$Mid(Today, 4, 2) + F$Right(Today, 7)
^
?Undefined symbol
"today" is undefined because the previous line was supposed to define it but
failed.
$ _if F$Search("OMS$:REQLOG.OMS") .nes.
"" Then -
Continue: _Rename/NoWarn OMS$:REQLOG.OMS 'File'
$ _if F$Search("OMS$:REQLOG.OMS") .nes. "" Then
_Rename/NoWarn
OMS$:REQLOG.OMS 'File'
^
?Undefined symbol
"file" is undefined because the line that defined it got an error.
So it looks like an error cascade started with a Y2K bug. You might try starting with a
20th century date like 1999, I'd expect it to be clean then.
paul
11:37 a.m.
On Mon, May 27, 2019 at 11:26 AM Paul Koning <paulkoning at comcast.net> wrote:
Looks like f$cvtime is failing, that's presumably a Y2K issue.
Changing the date to 1999 before startup did resolve the issues.
RSTS V10.0-L RSTS (DU0) INIT V10.0-0L
;9.05.27 11:33
Start timesharing? <Yes> NO
Option: <Start> DATE
Today's date? <;9.05.27> 99.5.27
Current time? <11:34>
Option: <Start>
Disk is being rebuilt - wait ...
99.05.27 11:34
Proceed with system startup? <YES>
Beginning RSTS/E system startup...
99.05.27 11:34 Installing monitor overlays
99.05.27 11:34 Mounting disks
99.05.27 11:34 Assigning logical names
99.05.27 11:34 Starting error logging
99.05.27 11:34 Setting system characteristics
27-May-99 11:34 AM Installing run-time systems and libraries
27-May-99 11:34 AM Starting Operator/Message Services
$ File = F$Left(Today, 2) + F$Mid(Today, 4, 2) +
F$Right(Today, 7)
$ File = F$Left(Today, 2) + F$Mid(Today, 4, 2) + F$Right(Today, 7)
^
?Undefined symbol
"today" is undefined because the previous line was supposed to define it but
failed.
$ _if F$Search("OMS$:REQLOG.OMS") .nes.
"" Then -
Continue: _Rename/NoWarn OMS$:REQLOG.OMS 'File'
$ _if F$Search("OMS$:REQLOG.OMS") .nes. "" Then
_Rename/NoWarn
OMS$:REQLOG.OMS 'File'
^
?Undefined symbol
"file" is undefined because the line that defined it got an error.
So it looks like an error cascade started with a Y2K bug. You might try starting with a
20th century date like 1999, I'd expect it to be clean then.
paul
>>>>>>>>>>>>>> OMS V10.0-K 27-May-99 11:34 AM
<<<<<<<<<<<<<<<
Message 1 from OMS,
user [1,2], Detached, job 3
Starting Operator/Message Services
27-May-99 11:34 AM Setting terminal characteristics
27-May-99 11:34 AM Defining system commands
27-May-99 11:34 AM Setting printer characteristics
27-May-99 11:34 AM Starting spoolers
*** From [1,2] on KB0: at 11:34 AM 27-May-99
** RSTS/E is on the air...
>>>>>>>>>>>>>> OMS V10.0-K 27-May-99 11:34 AM
<<<<<<<<<<<<<<<
Message 2 from user
[1,2] on _KB0:, job 2
The system startup is complete
3:15 p.m.
On 5/27/19 9:58 AM, Rod Smallwood via cctalk wrote:
Hi
??? Whilst I wait to hear from Glen Slick who has got me this far
(Thanks Glen) I'll restate the problem.
1. I now have an old XP system with SIMH on it (PDP11.exe)
2.? I have created RD54.dsk containing RSTS/E
3. Attached to the system is a 2.1Gb SCSI drive via an adaptec 2940
controller
4. I need a tried and tested list of step by step instructions to put
RD54.dsk on the SCSI drive.
5. The drive will then be moved to a CQD-220A/TM SCSI controller on my
KDJ11-E based 11/93 and must boot.
6. Its just an image copy from one drive to another on the same system.
7. Nobody has come up with a tried and tested list of step by step
instructions yet.
Rod Smallwood
Depends on what you mean by tried and tested.
I told you to use Ersatz-11 and buld the image directly
on the SCSI drive. Ersatz-11 works fine under FreeDOS.
Disks are cheap so you just make a different disk for
your system. I have used this method to make RT-11, RSTS/E
and BSD-211 systems disks that successfully boot and run
on my 11/93 with the CQD-220A/TM controller.
You could probably boot your image under Ersatz-11 and then
copy it to the SCSI but the method above works just as well.
bill
1802
days inactive
1802
days old
10 comments
5 participants
participants (5)
-
bill.gunshannon＠hotmail.com -
glen.slick＠gmail.com -
holm＠freibergnet.de -
paulkoning＠comcast.net -
rodsmallwood52＠btinternet.com