You cannot set up a disk to boot BRUSYS from scratch.
Sorry, maybe I didn't make it clear but this ISN'T what I want to do. I'm
perfectly happy with booting the real RSX on DL0 (which works fine now) and
then saying "BOO [6,54]BRUSYS". That works great on DU0 - the BRUSYS boots,
asks the usual "enter the first device...", "enter the second device..."
dialog, and then you can run BAD, INI, BRU and I don't know what else.
But the copy of BRUSYS.SYS on DL0 doesn't work. You can boot it (using
BOO, just like above) and it'll ask for the first and second devices as
usual. But then once it's booted none of the tasks work - running INI, BAD,
BRU all produce MCR errors (it says "MCR - error nn"; I forget the exact
number, but I could boot it up again and see if you need to know).
Bob
On 2013-05-07 18:31, Sampsa Laine wrote:
Got the DS200 running, turns out it was a bad transceiver.
Cool.
Will try to get the 300 up if I can find a transceiver.
The 300 is better than the 200 in most ways.
Johnny
On 2013-05-07 18:23, Sampsa Laine wrote:
On 7 May 2013, at 18:22, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-05-07 18:18, Sampsa Laine wrote:
Do I need to reset this thing somehow?
All I'm getting is garbage, thinking the baud rate is wrong - it's connected to a VT420 on port 1, baud rate 9600
Has it booted, or is it still sitting in the boot loop? (You can see that on the display of the DS300, when it has booted, it do an animation loop on the display.)
The display just says "2"
That means it is in the process of booting. Downloading software.
4 is I think just waiting to boot, selftest passed.
3 means it has sent out a boot request
2 means it has recevied the initial handshaking from a boot server, and is downloading
1 is probably something like completed download
Before it has booted it prints things, normally on port 1, and I think at the fixed speed of 9600. Once it has booted, it all depends on the setup of the port, which is stored in nonvolatile ram.
How do I reset the NVRAM?
Hold in the button while applying power.
Johnny
"Brian Schenkenberger, VAXman-" <system at TMESIS.COM> writes:
Brian Hechinger <wonko at 4amlunch.net> writes:
I'm starting a new job. Part of that is being trained on their
application that I'll be supporting.
The training will be taking place in the office in London.
For all of you EU-ers who'll be in London, near London or within
reasonable travel distance to London the week of June 3rd contact me
off-list. I'd love the chance to meet up with people.
Brian, I won't be in London but I just took my friend to EWR last evening
so he could fly home to London. After he was made redundant in VISA's IT
dept a decade ago, he became a tour guide and is presently working in the
Royal Muse at Buckingham Palace. If you'd like a nice tour of the Palace
and, later, London's watering holes, I can fix you up with him.
Is this your first trip to London? .UK? Europe?
FYI, his name is Keith Waye. He's quoted in this brief article on the Royal
Wedding.
http://www.telegraph.co.uk/news/uknews/royal-wedding/8481190/Royal-Wedding-…>
Here is also some more information about him:
http://www.lulu.com/spotlight/doyousee
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
On Tue, 7 May 2013, Sampsa Laine wrote:
Got the DS200 running, turns out it was a bad transceiver.
Aww. I wanted another one to fix. ;)
Will try to get the 300 up if I can find a transceiver.
sampsa
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On Tue, 7 May 2013, Sampsa Laine wrote:
Anybody have this?
My DS200/MC has just bit the dust it seems.
Send the DS200 my way. I like fixing those.
sampsa
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On 2013-05-07 18:23, Bob Armstrong wrote:
BRUSYS is a standalone system that runs without any disk.
Yep, that's what I thought.
It has all the necessary tasks in order to install a distribution on a
disk.
This is a system that is only intended for when you boot from tape.
Well, that's one use. But you can also use it to backup or copy the
system disk too (e.g. a disk to disk transfer). That part is even
documented in the RSX manual.
Right, if you boot BRUSYS from a tape. If you actually booted from a disk, you'd use BRU on that disk for this instead.
If you copy BRUSYS.SYS to another disk, it should work just as well as from
the original disk.
Sounds good, but in practice it doesn't. Sorry...
Exactly what did you do for that to happen? It sounds more than strange.
So, whatever you did when you copied the file over to another disk was
probably
not doing what you thought you were doing.
UFD DL0:[6,54]
PIP DL0:[6,54]/CO=DU0:[6,54]*.*
Right. And then you do BOO DL:[6,54]BRUSYS, which should be just fine.
Any bootable disk is normally created by doing a build of a normal RSX
system,
copy all the files to the target disk, do a VMR on the target disk, boot
the
result, and then do a SAV /WB to dump the memory, and update the boot
block.
Yep, that's basically what I did to create the bootable RSX system on DL0
from DU0.
If you have any other suggestions, please let me know. I'd really like to
get S/A BRU working on DL0.
There are some very important details here.
If you take your normal system and copy it over (I'm not talking about BRUSYS now), you will run a VMR on your new disk, using your SYSVMR.CMD and a copy of RSX11M.TSK copied into a new RSX11M.SYS. SYSTEM.CMD will then install all partitions, device drivers and tasks needed to get the system bootable. However, SYSVMR installs stuff using the device names LB: and SY:, so before running VMR, you need to make sure these names points to your new disk, or else you will install all tasks from a different disk. This is perfectly acceptable in VMR point of view, but when you boot your new disk, the "other" disk, where all the images are, is not mounted, and thus they will all be removed at boot time, and nothing will work.
So, essentially, getting a new disk set up, based on a current disk.
UFD xx:[1,1]
UFD xx:[1,54]
PIP xx:[1,1]=oo:[1,1]*.*
PIP xx:[1,54]=oo:[1,54]*.*
PIP xx:[1,54]RSX11M.SYS/CO/NV/BL:1026.=xx:[1,54]RSX11M.TSK
ASN LB:=xx:
ASN SY:=xx:
SET /UIC=[1,54]
VMR @SYSVMR
BOO [1,54]
SAV /WB
There are probably details you need to polish, but this should give you a rough idea.
(For M+, you also want [3,54], and of course there are plenty of other stuff you might want to suck over.)
Johnny
On 2013-05-07 18:18, Sampsa Laine wrote:
Do I need to reset this thing somehow?
All I'm getting is garbage, thinking the baud rate is wrong - it's connected to a VT420 on port 1, baud rate 9600
Looking at logs on MIM, I can see a request from 08-00-2B-1B-DF-1D. However after some loading time, I get an error "Line communication error". No idea what that might mean.
Johnny
sampsa
On 7 May 2013, at 18:12, Sampsa Laine <sampsa at mac.com> wrote:
OK, I'll power it up and see what happens :)
On 7 May 2013, at 18:07, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-05-07 17:24, Sampsa Laine wrote:
Anybody have this?
My DS200/MC has just bit the dust it seems.
Yes, both V1 and V2. And MIM serves anyone connected with MOP if they request it.
Johnny
On 7 May 2013, at 18:22, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-05-07 18:18, Sampsa Laine wrote:
Do I need to reset this thing somehow?
All I'm getting is garbage, thinking the baud rate is wrong - it's connected to a VT420 on port 1, baud rate 9600
Has it booted, or is it still sitting in the boot loop? (You can see that on the display of the DS300, when it has booted, it do an animation loop on the display.)
The display just says "2"
Before it has booted it prints things, normally on port 1, and I think at the fixed speed of 9600. Once it has booted, it all depends on the setup of the port, which is stored in nonvolatile ram.
How do I reset the NVRAM?
