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.
If the replacement disk is a fair amount larger, clean ( disk rebuild ) which is RSTS fsck may complain that the free cluster bitmap file is too small. That won t prevent reading but it will make the disk read-only.
It gives an initialisation error about it being > a power of 2.
paul
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
El 15/05/2014, a les 23.25, Cory Smelosky <b4 at gewt.net> va escriure:
On Thu, 15 May 2014, Jordi Guillaumes i Pons wrote:
El 15/05/2014, a les 23.22, Cory Smelosky <b4 at gewt.net> va escriure:
sim> b tq
TQ I/O error: Undefined error: 0
I/O error, PC: 157456 (TST 157520)
Use a TS device, and don't forget to set it to read-locked.
Ahhh. That does it. Thanks!
Great!
Now for the disk issue, I'm using an RP04 connected to RP0. It shows as "DB0:" in RSTS, and it has plenty of space for the OS, even being of "just" 84MB:
$ show disk
Disk Structure:
Dsk Open Size Free Clu Err Name Level Comments
DB0 22 171796 124272 72% 4 0 RSTS11 1.2 Pub, DLW
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On May 15, 2014, at 5:14 PM, Cory Smelosky <b4 at gewt.net> wrote:
On Thu, 15 May 2014, Jordi Guillaumes i Pons wrote:
El 15/05/2014, a les 5.15, Cory Smelosky <b4 at gewt.net> va escriure:
The RZ25 didn't have the disk to copy the image I had ready.
Thankfully...it failed (apparently something went short as it being plugged in makes the VAX /fail to power on/) so I can use my 526M drive!
Hi Cory,
I'm perhaps a little bit late catching this train, but... what was the original problem you are trying to solve using this kind of hardware sorcery? Your first post mentioned something along you being unable to install RSTS/E under simh from tape... could you be more specific? I have a running RSTS/E installation which I built from an install tape, and perhaps I could help you to fix the initial problem which triggered all this disk size/connection/style thing...
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.
If the replacement disk is a fair amount larger, clean ( disk rebuild ) which is RSTS fsck may complain that the free cluster bitmap file is too small. That won t prevent reading but it will make the disk read-only.
paul
On Thu, 15 May 2014, Jordi Guillaumes i Pons wrote:
El 15/05/2014, a les 23.22, Cory Smelosky <b4 at gewt.net> va escriure:
sim> b tq
TQ I/O error: Undefined error: 0
I/O error, PC: 157456 (TST 157520)
Use a TS device, and don't forget to set it to read-locked.
Ahhh. That does it. Thanks!
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
El 15/05/2014, a les 23.22, Cory Smelosky <b4 at gewt.net> va escriure:
sim> b tq
TQ I/O error: Undefined error: 0
I/O error, PC: 157456 (TST 157520)
Use a TS device, and don't forget to set it to read-locked.
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On Thu, 15 May 2014, Dave McGuire wrote:
On 05/15/2014 05:14 PM, Cory Smelosky 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).
I can assist with that later tonight, unless Jordi can help sooner.
You know the tape needs to be write-locked for a RSTS/E install, right?
Yeah.
local: rstse_v10_1_install_sep10_1992.tap.bz2 remote: rstse_v10_1_install_sep10_1992.tap.bz2
200 EPRT command successful. Consider using EPSV.
150 Opening BINARY mode data connection for rstse_v10_1_install_sep10_1992.tap.bz2 (9704614 bytes).
100% |**********************************************************************************************************************************| 9477 KiB 303.66 KiB/s 00:00 ETA
226 Transfer complete.
9704614 bytes received in 00:31 (303.12 KiB/s)
ftp> qui
221 Goodbye.
melanie:~ b4$ bunzip2 rstse_v10_1_install_sep10_1992.tap.bz2
melanie:~ b4$ ~/simh/BIN/pdp11
PDP-11 simulator V4.0-0 Beta git commit id: 746e5ab8
sim> at -r tq rstse_v10_1_install_sep10_1992.tap
TQ: unit is read only
sim> set cpu 11/23
sim> set cpu 1m
Disabling RK
Disabling HK
Disabling TM
sim> b tq
TQ I/O error: Undefined error: 0
I/O error, PC: 157456 (TST 157520)
-Dave
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
El 15/05/2014, a les 23.14, Cory Smelosky <b4 at gewt.net> va escriure:
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).
Are you getting weird "invalid block size" messages?
If so, check:
- Your CPU type is 11/73 (I'm pretty sure other options will work, but not, for instance, 11/70)
- Make sure you have set your tape drive to READ ONLY (set TS0 LOCK)
- Use the TS device.
I'm right now repeating the install to check it just works. Looking at the monitor building progress bar ...
It worked
Memory available to RSTS/E is 2044K words.
Re-creating CRASH.SYS file with minimum size of 1316 blocks
4 devices disabled
Proceed with system startup? <YES>
Beginning RSTS/E system startup...
15-May-14 11:20 PM Installing monitor overlays
15-May-14 11:20 PM Mounting disks
15-May-14 11:20 PM Assigning logical names
15-May-14 11:20 PM Starting error logging
15-May-14 11:20 PM Setting system characteristics
15-May-14 11:20 PM Installing run-time systems and libraries
15-May-14 11:20 PM Starting Operator/Message Services
OMS V10.1-A 15-May-14 11:20 PM <<<<<<<<<<<<<<<
Message 1 from OMS, user [1,2], Detached, job 3
Starting Operator/Message Services
15-May-14 11:20 PM Setting terminal characteristics
15-May-14 11:20 PM Defining system commands
15-May-14 11:20 PM Setting printer characteristics
15-May-14 11:20 PM Starting spoolers
*** From [1,2] "[ 1, 2]" on KB0: at 11:20 PM 15-May-14
** RSTS/E is on the air...
OMS V10.1-A 15-May-14 11:20 PM <<<<<<<<<<<<<<<
Message 2 from user [1,2] on _KB0:, job 2
The system startup is complete
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On 05/15/2014 05:14 PM, Cory Smelosky 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).
I can assist with that later tonight, unless Jordi can help sooner.
You know the tape needs to be write-locked for a RSTS/E install, right?
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On Thu, 15 May 2014, Jordi Guillaumes i Pons wrote:
El 15/05/2014, a les 5.15, Cory Smelosky <b4 at gewt.net> va escriure:
The RZ25 didn't have the disk to copy the image I had ready.
Thankfully...it failed (apparently something went short as it being plugged in makes the VAX /fail to power on/) so I can use my 526M drive!
Hi Cory,
I'm perhaps a little bit late catching this train, but... what was the original problem you are trying to solve using this kind of hardware sorcery? Your first post mentioned something along you being unable to install RSTS/E under simh from tape... could you be more specific? I have a running RSTS/E installation which I built from an install tape, and perhaps I could help you to fix the initial problem which triggered all this disk size/connection/style thing...
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).
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
El 15/05/2014, a les 5.15, Cory Smelosky <b4 at gewt.net> va escriure:
The RZ25 didn't have the disk to copy the image I had ready.
Thankfully...it failed (apparently something went short as it being plugged in makes the VAX /fail to power on/) so I can use my 526M drive!
Hi Cory,
I'm perhaps a little bit late catching this train, but... what was the original problem you are trying to solve using this kind of hardware sorcery? Your first post mentioned something along you being unable to install RSTS/E under simh from tape... could you be more specific? I have a running RSTS/E installation which I built from an install tape, and perhaps I could help you to fix the initial problem which triggered all this disk size/connection/style thing...
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
