On Fri, 16 May 2014, John Wilson wrote:
From: Cory Smelosky <b4 at gewt.net>
=op onl
Received packet:
ONLINE END
UNIT=1
UNIT SIZE=1048778
What is the unit for that?
Blocks.
512-byte?
So 512/522.
John Wilson
D Bit
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Thu, 15 May 2014, John Wilson wrote:
a blank line after each "g" (go) command to make the program check for
response packets. "op gus" (with "unit n" and "g") does a "get unit status"
command if you want more details about the drive. "quit" halts (then 173000G
or CNTRL/BOOT or whatever, to reboot).
John Wilson
D Bit
=op onl
Received packet:
ONLINE END
UNIT=1
UNIT SIZE=1048778
What is the unit for that?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 05/16/2014 05:27 PM, Paul_Koning at Dell.com wrote:
First I need to find the exact size of the drive so I can set
an RAUSER to it. I can then install RSTS/E *IF* I can get SIMH
to boot and install from the RSTS/E V10.1 tape (which I can't
get it to do).
You mean you have a real drive, and you want to copy it to a
disk image file and configure that as an RA file of
user-specified size? That will work fine. RSTS can handle disks
of any size up to a limit (the RP07 is somewhat below that limit,
I d have to dig a bit to find the actual number). If you can
just dd the disk to a file, that file should serve.
Alternatively, you can always use a larger disk so long as you
don t cross a power of two. RSTS addresses disks by disk
clusters which are 16 bit numbers, and the file system layout
starts from a given disk cluster size. So if you have a pack
with 70k sectors, you can drop it into another pack of 90k
sectors but not in one of 130k sectors because that one has a
DCS double that of the original.
Are you certain that this is the only limitation? I've had the
crash-on-boot problems when they were off by quite a bit less than
a power of two. Since I found that problem the hard way, I always
make images (via simh "rauser=<n>") using the exact size of the
target physical disk.
Certainly matching the size is good. But I m pretty sure that what I
described is accurate.
I just did an experiment, with a couple of different disk images. I
don t see startup crashes and there should not be any. (Well, not
unless you mean a failure to start due to a fatal error .)
That's exactly what I mean. ;) Perhaps not the best terminology.
RSTS accepts a disk with mismatched container size so long as the
disk clustersize is unchanged and the SATT.SYS file is the correct
length. Actually, the latter condition is sufficient (it implies the
first). SATT.SYS size is container size divided by pack cluster size
(a parameter set when the pack was initialized), rounded up to an
integer.
I guess it was borderline when I tripped over it, then. That seems
odd because it wasn't just a "once in awhile" thing, it was EVERY time.
But I can certainly see it being bad luck. Now, though, I just find
out the target disk size and make my images exactly the same size, which
I'd do anyway because I'm anal about stuff like that. ;)
If you want to manipulate, or check, RSTS disk images, a useful
utility is rstsflx which you can find at
svn://akdesign.dyndns.org/flx/trunk
That sounds really handy; I will check it out, thanks!
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On Fri, 16 May 2014, Paul_Koning at Dell.com wrote:
RSTS accepts a disk with mismatched container size so long as the disk clustersize is unchanged and the SATT.SYS file is the correct length. Actually, the latter condition is sufficient (it implies the first). SATT.SYS size is container size divided by pack cluster size (a parameter set when the pack was initialized), rounded up to an integer.
It tells me the clustersize is not (some multiple of 2)
I thought RSTS would accept a disk so long as the DCS is right but with wrong SATT if mounted read-only. That turns out to be incorrect, it insists on a good SATT even if it has no need for one (as in the read-only case). I suspect that s a leftover from the days before read-only mode was introduced.
If you want to manipulate, or check, RSTS disk images, a useful utility is rstsflx which you can find at svn://akdesign.dyndns.org/flx/trunk
I'm limited by the disk space on the RT-11 disk and what I can transfer quickly with kermit (unles someone has a DECnet stack)
paul
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On May 15, 2014, at 5:44 PM, Dave McGuire <mcguire at neurotica.com> wrote:
On 05/15/2014 05:28 PM, Paul_Koning at Dell.com wrote:
First I need to find the exact size of the drive so I can set an
RAUSER to it. I can then install RSTS/E *IF* I can get SIMH to
boot and install from the RSTS/E V10.1 tape (which I can't get it
to do).
You mean you have a real drive, and you want to copy it to a disk
image file and configure that as an RA file of user-specified size?
That will work fine. RSTS can handle disks of any size up to a limit
(the RP07 is somewhat below that limit, I d have to dig a bit to find
the actual number). If you can just dd the disk to a file, that file
should serve.
Alternatively, you can always use a larger disk so long as you don t
cross a power of two. RSTS addresses disks by disk clusters which
are 16 bit numbers, and the file system layout starts from a given
disk cluster size. So if you have a pack with 70k sectors, you can
drop it into another pack of 90k sectors but not in one of 130k
sectors because that one has a DCS double that of the original.
Are you certain that this is the only limitation? I've had the
crash-on-boot problems when they were off by quite a bit less than a
power of two. Since I found that problem the hard way, I always make
images (via simh "rauser=<n>") using the exact size of the target
physical disk.
Certainly matching the size is good. But I m pretty sure that what I described is accurate.
I just did an experiment, with a couple of different disk images. I don t see startup crashes and there should not be any. (Well, not unless you mean a failure to start due to a fatal error .)
RSTS accepts a disk with mismatched container size so long as the disk clustersize is unchanged and the SATT.SYS file is the correct length. Actually, the latter condition is sufficient (it implies the first). SATT.SYS size is container size divided by pack cluster size (a parameter set when the pack was initialized), rounded up to an integer.
I thought RSTS would accept a disk so long as the DCS is right but with wrong SATT if mounted read-only. That turns out to be incorrect, it insists on a good SATT even if it has no need for one (as in the read-only case). I suspect that s a leftover from the days before read-only mode was introduced.
If you want to manipulate, or check, RSTS disk images, a useful utility is rstsflx which you can find at svn://akdesign.dyndns.org/flx/trunk
paul
El 15/05/2014, a les 23.48, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> va escriure:
I'm thinking about a simh bug. SIMH v39 boots from that tape mounting it under tq0:
The bug has been fixed by Mark in the HEAD version of the github repository. Now the RSTS/E install tape image can be booted using a TQ device.
PDP-11 simulator V4.0-0 Beta git commit id: c0f9c2e8
boot-tq.ini-2> set cpu 11/73
boot-tq.ini-3> set cpu 4m
Disabling RK
Disabling HK
Disabling TM
boot-tq.ini-4> set tq enable
boot-tq.ini-5> set tq0 lock
boot-tq.ini-6> att tq0 rstse_v10_1_install_sep10_1992.tap
boot-tq.ini-7> boot tq0
Performing limited hardware scan.
RSTS V10.1 (MU0) INIT V10.1-0L
Today's date?
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On Thu, 15 May 2014, John Wilson wrote:
I took a wild guess hoping the drive was partitioned in to 4 equal drives of ~400-500M. I am currently copying my 435M disk at 38.4kbaud.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
From: <Paul_Koning at Dell.com>
Hm... disks have controller-specific boot blocks, but I thought tapes were
universal.
Yeah, the RSTS generic tape boot is quite a nice piece of black magic!
(And, not to beat a dead horse, but E11 likes it fine on all four tape
types and can mount raw real SCSI drives too, with the size you say.)
From: Cory Smelosky <b4 at gewt.net>
I need the /physical/ drive size! Different systems give me different
sizes.
If you've got it on a real PDP-11, you can try my DUTEST program (from
RT-11, or if you have some other way to load it stand-alone and start it
at 1000, it doesn't actually need an OS):
http://www.dbit.com/pub/pdp11/rt11/dutest.mac
It's a reverse-engineering tool (from when I was working on MSCP/TMSCP)
so the command set is pretty low-level, but this sequence should get you
the MSCP controller's idea of the unit size:
.RUN DUTEST
DUTEST by John Wilson <wilson at dbit.com>
Copyright (C) 1997-1999 by Digby's Bitpile, Inc. All rights reserved.
=init
Returned values: DI Step 1 bits 7:0=000 (documented as 000)
Port type = 0, reserved step 3 bits 10:8 = 0, model = 006, FW version = 02
=op scc
=g
=
Received packet:
SCC END
FLAGS=100000
Message credits: 8
=op onl
=unit 0
=g
=
Received packet:
ONLINE END
UNIT=0
UNIT SIZE=204800
Message credits: 8
=
"=" is the prompt. Change "unit 0" to the actual MSCP unit. And enter
a blank line after each "g" (go) command to make the program check for
response packets. "op gus" (with "unit n" and "g") does a "get unit status"
command if you want more details about the drive. "quit" halts (then 173000G
or CNTRL/BOOT or whatever, to reboot).
John Wilson
D Bit
On 05/15/2014 05:48 PM, Cory Smelosky wrote:
I need the /physical/ drive size! Different systems give me different
sizes.
This, of course, should not happen. The host should query the drive
for its size, in blocks...I don't know why a given host OS would give
you different numbers.
It is listed as 2G...the MicroVAX 3100 I wrote it with claims it's ~570M
If it's an early MicroVAX-3100, and you're frobbing that drive via its
ROM-based monitor, that code is limited to 21-bit block numbers. Later
machines use 32-bit block numbers.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
