On May 20, 2014, at 8:33 AM, Cory Smelosky <b4 at gewt.net> wrote:
So:
Pack cluster size is not 1, 2, 4, 8, 16, 32 or 64.
PC=120324 PS=030344 OV=000006 M5=004000 M6=004200 SP=041240
R0=000026 R1=143161 R2=143161 R3=000000 R4=000000 R5=041350
The disk should be around ~512M. I created a 500M disk.
Disk? DU0
Pack ID? 0
Pack cluster size <16>?
MFD cluster size <16>?
SATT.SYS base <30530>?
Pre-extend directories <NO>?
PUB, PRI, or SYS <SYS>?
[1,1] cluster size <16>?
[1,2] cluster size <16>?
[1,1] and [1,2] account base <30530>?
Date last modified <YES>?
New files first <NO>?
Read-only <NO>?
Patterns <3>? 0
Erase Disk <YES>? YES
Proceed (Y or N)? Y
Unless the partitioning is written to the first block and not done through controller NVRAM...I can't see the reasoning.
Could you explain what you wanted to do, what steps you followed, and what exactly the trouble is?
If you feed a disk to RSTS that doesn t have a RSTS file system on it, it will get confused/annoyed. The error message you quoted is an example of what you would see.
Given an uninitialized disk, you use the disk initialization procedure (from INIT or online). The dialog you showed does that. After that procedure, you ll have a RSTS format disk.
Partitioning? RSTS doesn t have partitions. The whole physical drive is a single file system. It also doesn t depend on NVRAM (PDP11s traditionally have none).
Block 0 is the boot block (dummy not bootable boot block by default). Boot 1 is the superblock ( pack label ). For new (V9 or later) disks that points to the MFD (top level directory); for old disks (format 0.0) it is the first block of the [1,1] directory which doubles as MFD on that layout.
paul
El 20/05/2014, a les 15.25, Cory Smelosky <b4 at gewt.net> va escriure:
Going to fight RSTS/E first. I can succeed if I image with a VAX. ;)
Thanks! What kit did you use for 4.8 non-plus?
I've got several tape images named "decnet11something" around. I guess its the one named "decnet11m48", but I'm not completely sure about that.
And, yes, I'm a disaster.
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On Tue, 20 May 2014, Jordi Guillaumes i Pons wrote:
For creating a disk image...the drive is 1048617 blocks.
Do I use 1024 or 1000 to define 1M? Should I do 512M or 536M?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Tue, 20 May 2014, Jordi Guillaumes i Pons wrote:
El 20/05/2014, a les 15.14, Cory Smelosky <b4 at gewt.net> va escriure:
Unless you want to feel the pain (or the joy) of manually defining memory partitions, I'd suggest you to go PLUS :)
Can't! No Split I&D.
Ouch :)
I managed to decnetize a 4.8 (simulated) machine. Yell if you need help doing so (if you are planning to network it of course).
Going to fight RSTS/E first. I can succeed if I image with a VAX. ;)
Thanks! What kit did you use for 4.8 non-plus?
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 20/05/2014, a les 15.14, Cory Smelosky <b4 at gewt.net> va escriure:
Unless you want to feel the pain (or the joy) of manually defining memory partitions, I'd suggest you to go PLUS :)
Can't! No Split I&D.
Ouch :)
I managed to decnetize a 4.8 (simulated) machine. Yell if you need help doing so (if you are planning to network it of course).
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On Tue, 20 May 2014, Jordi Guillaumes i Pons wrote:
El 20/05/2014, a les 14.33, Cory Smelosky <b4 at gewt.net> va escriure:
Back to trying RSX-11M 4.8. That's 100M and doubtful it'll complain.
Unless you want to feel the pain (or the joy) of manually defining memory partitions, I'd suggest you to go PLUS :)
Can't! No Split I&D.
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 20/05/2014, a les 14.33, Cory Smelosky <b4 at gewt.net> va escriure:
Back to trying RSX-11M 4.8. That's 100M and doubtful it'll complain.
Unless you want to feel the pain (or the joy) of manually defining memory partitions, I'd suggest you to go PLUS :)
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
So:
Pack cluster size is not 1, 2, 4, 8, 16, 32 or 64.
PC=120324 PS=030344 OV=000006 M5=004000 M6=004200 SP=041240
R0=000026 R1=143161 R2=143161 R3=000000 R4=000000 R5=041350
The disk should be around ~512M. I created a 500M disk.
Disk? DU0
Pack ID? 0
Pack cluster size <16>?
MFD cluster size <16>?
SATT.SYS base <30530>?
Pre-extend directories <NO>?
PUB, PRI, or SYS <SYS>?
[1,1] cluster size <16>?
[1,2] cluster size <16>?
[1,1] and [1,2] account base <30530>?
Date last modified <YES>?
New files first <NO>?
Read-only <NO>?
Patterns <3>? 0
Erase Disk <YES>? YES
Proceed (Y or N)? Y
Unless the partitioning is written to the first block and not done through controller NVRAM...I can't see the reasoning.
Back to trying RSX-11M 4.8. That's 100M and doubtful it'll complain.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Mon, 19 May 2014, Jerome H. Fine wrote:
Since you are obviously using either V05.06 or V05.07
Yup. 5.07. It has Mentec branding!
(only the last two versions of RT-11 have the RT11ZM
Monitor), you can use the VRUN command to support
giving LINK all 64 KB of memory. Naturally, you
will probably need at least 256 KB of total physical
memory on even a PDP-11/23 (to run RT11XM as well as
to provide the needed extended memory to provide
LINK with the full 64 KB to run in) although 128 KB
might do in a pinch depending on which device you use
for the system device.
Thanks. I'll look in to VRUN.
NOTE that a PDP-11/23 does not have the IOPAGE MMU
registers to support RT11ZM (which you probably already
know or have found out).
Yup. ;)
Let me know if the VRUN command works. There are more
things to try if that does not work.
Will do. Currently stuck in standalone mkfs trying to write to a separate disk. Will head down and reset shortly.
If you insist on using RT11FB and that does not work,
then try RT11SB which may take less memory. If that
is insufficient, go back to an earlier version of RT-11
and try RT11SJ.
TSX+ has to be started from SB/SJ/FB iirc.
Otherwise, LINK has a few options to expand the Symbol
Table size. If you don't have access to the LINK chapter,
let me know and I can look it up.
Thanks!
It sounds like you are trying to LINK TSX-Plus which
does require a HUGE Symbol Table. If possible, have
only the system device driver loaded if not using RT11XM
(which will allow you to use VRUN which will use extended
memory, so low memory will not matter).
Otherwise, if you have a TSX-Plus configuration already
available, switch to that to perform your LINK.
Jerome Fine
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
>Cory Smelosky wrote:
Afternoon,
I have a quick RT-11 question hopefully someone can help with without me needing the skim the entire linker manual. ;)
Would ?LINK-F-Symbol table overflow be a result of monitor configuration constraints, memory constraints, or something else? I've linked TSX+ in SIMH fine so I have no idea why it's failing on the real 11/23. I think I had linked it under the ZM monitor in SIMH though...not XM.
Since you are obviously using either V05.06 or V05.07
(only the last two versions of RT-11 have the RT11ZM
Monitor), you can use the VRUN command to support
giving LINK all 64 KB of memory. Naturally, you
will probably need at least 256 KB of total physical
memory on even a PDP-11/23 (to run RT11XM as well as
to provide the needed extended memory to provide
LINK with the full 64 KB to run in) although 128 KB
might do in a pinch depending on which device you use
for the system device.
NOTE that a PDP-11/23 does not have the IOPAGE MMU
registers to support RT11ZM (which you probably already
know or have found out).
Let me know if the VRUN command works. There are more
things to try if that does not work.
If you insist on using RT11FB and that does not work,
then try RT11SB which may take less memory. If that
is insufficient, go back to an earlier version of RT-11
and try RT11SJ.
Otherwise, LINK has a few options to expand the Symbol
Table size. If you don't have access to the LINK chapter,
let me know and I can look it up.
It sounds like you are trying to LINK TSX-Plus which
does require a HUGE Symbol Table. If possible, have
only the system device driver loaded if not using RT11XM
(which will allow you to use VRUN which will use extended
memory, so low memory will not matter).
Otherwise, if you have a TSX-Plus configuration already
available, switch to that to perform your LINK.
Jerome Fine
