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
El 15/05/2014, a les 23.41, Cory Smelosky <b4 at gewt.net> va escriure:
I need the /physical/ drive size! Different systems give me different sizes.
Oh, I think I'm starting to understand. Are you trying to use a raw device in simh? :)
That is COOL! :)
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
El 15/05/2014, a les 23.37, <Paul_Koning at Dell.com> <Paul_Koning at Dell.com> va escriure:
Hm... disks have controller-specific boot blocks, but I thought tapes were universal. Yes, the code says that showed up in V9.1. So I wonder why it would not work for you.
I'm thinking about a simh bug. SIMH v39 boots from that tape mounting it under tq0:
sim> att tq0 rstse_v10_1_install_sep10_1992.tap
sim> b tq0
Performing limited hardware scan.
RSTS V10.1 (MU0) INIT V10.1-0L
Today's date? 15-MAY-14
Current time? 23:41
Installing RSTS on a new system disk? <Yes>
15-May-14 11:41 PM
Disk?
I know Mark has fiddled a lot with the massbus drivers, so to find the "failed" commit will be a long task. I'm for it anyway... Reporting the bug as i'm writting this.
https://github.com/simh/simh/issues/139
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On Thu, 15 May 2014, Dave McGuire 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
I see from private email that you had started up the command interface
on your Qbus SCSI host adapter. Is there a "scan the bus" command or
something like that in there, that might tell you the drive size in
blocks, from the perspective of that controller? Alternatively, what I
do (as I mentioned in private mail) is to boot 2.11BSD from a different
device and look at the ra<n> probe messages for the device size.
It scans it...but it doesn't seem to list the size in blocks. :(
-Dave
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 05/15/2014 05:41 PM, Cory Smelosky wrote:
On Thu, 15 May 2014, Paul_Koning at Dell.com wrote:
On May 15, 2014, at 5:34 PM, Cory Smelosky <b4 at gewt.net> wrote:
On Thu, 15 May 2014, 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.
I want to copy an image to a real drive.
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.
The problem is I have NO IDEA just how big this drive is. Systems
tend to disagree about its size...I suppose I can sacrifice the RZ23
for this.
Find yourself a copy of my utility rstsflx and ask it to ident the
image. It will tell you the file system information. That will tell
you what sort of disk it can go onto.
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.
I see from private email that you had started up the command interface
on your Qbus SCSI host adapter. Is there a "scan the bus" command or
something like that in there, that might tell you the drive size in
blocks, from the perspective of that controller? Alternatively, what I
do (as I mentioned in private mail) is to boot 2.11BSD from a different
device and look at the ra<n> probe messages for the device size.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
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.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On Thu, 15 May 2014, Paul_Koning at Dell.com wrote:
On May 15, 2014, at 5:34 PM, Cory Smelosky <b4 at gewt.net> wrote:
On Thu, 15 May 2014, 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.
I want to copy an image to a real drive.
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.
The problem is I have NO IDEA just how big this drive is. Systems tend to disagree about its size...I suppose I can sacrifice the RZ23 for this.
Find yourself a copy of my utility rstsflx and ask it to ident the image. It will tell you the file system information. That will tell you what sort of disk it can go onto.
I need the /physical/ drive size! Different systems give me different sizes.
If it doesn t give the whole answer, ask some more and I ll dig deeper to find the things you need to look at. Oh yes, the first item would be the file size of file [0,1]satt.sys.
paul
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On May 15, 2014, at 5:34 PM, Cory Smelosky <b4 at gewt.net> wrote:
On Thu, 15 May 2014, 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.
I want to copy an image to a real drive.
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.
The problem is I have NO IDEA just how big this drive is. Systems tend to disagree about its size...I suppose I can sacrifice the RZ23 for this.
Find yourself a copy of my utility rstsflx and ask it to ident the image. It will tell you the file system information. That will tell you what sort of disk it can go onto.
If it doesn t give the whole answer, ask some more and I ll dig deeper to find the things you need to look at. Oh yes, the first item would be the file size of file [0,1]satt.sys.
paul
