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.
I just booted it up and tried it to get the real message. Here's what I'm
doing -
Hardware boot DL0. This boots the "real" RSX; when it gets to the MCR
prompt, I say "BOO [6,54]BRUSYS".
BRUSYS boots normally, and asks the "first device/second device" stuff.
FWIW, I say "DL0" and "MS0".
Hit enter and get the ">" prompt.
At this point, I enter "TIM 09:45 7-may-85" and it says
TIM -- 2
Not "error 2" (sorry, I misremembered that part); just "2" ...
Typing BRU, BAD or INI all produce
MCR -- 1
Curiously, entering just "TIM" with no argument actually works (although it
produces a bogus date/time).
I've never seen messages like this either; I'm hoping they mean something
to somebody.
Thanks,
Bob
On 2013-05-07 18:48, Cory Smelosky wrote:
On Tue, 7 May 2013, Johnny Billquist wrote:
On 2013-05-07 18:35, Cory Smelosky wrote:
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.
Every time I've had a problem with any of these, it has been the power
supply. Got any hints on what breaks?
In the case of mine the fans failed which resulted in rubber around
inductors melting and having other components fail due to the heat.
Seems like similar has happened to people around the internet.
http://osx.dev.gimme-sympathy.org/users/b4/weblog/6b8a6/images/0e170.JPG#32…
I actually have ones with no fans...
(I also noticed that MIM tried booting a DS200 for quite a while and failing, with the same "Line communication error" results. Same transciever?)
Johnny
On 2013-05-07 18:45, Johnny Billquist wrote:
On 2013-05-07 18:41, Bob Armstrong wrote:
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).
Those numbers would be helpful, but it sounds really weird that it would
not work just fine...
Give me the numbers, and maybe we can figure out what the errors are,
and go from there.
A full transcript would be even better. ;-)
(Although I should probably also point out that you do not need to copy the file anywhere to use it. What it booted from is rather irrelevant. But then again, I could also be totally wrong...)
Johnny
On Tue, 7 May 2013, Johnny Billquist wrote:
On 2013-05-07 18:35, Cory Smelosky wrote:
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.
Every time I've had a problem with any of these, it has been the power
supply. Got any hints on what breaks?
In the case of mine the fans failed which resulted in rubber around inductors melting and having other components fail due to the heat. Seems like similar has happened to people around the internet.
http://osx.dev.gimme-sympathy.org/users/b4/weblog/6b8a6/images/0e170.JPG#32…
Johnny
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On 2013-05-07 18:41, Bob Armstrong wrote:
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.
Ok.
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).
Those numbers would be helpful, but it sounds really weird that it would not work just fine...
Give me the numbers, and maybe we can figure out what the errors are, and go from there.
Johnny
On 2013-05-07 18:35, Cory Smelosky wrote:
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.
Every time I've had a problem with any of these, it has been the power supply. Got any hints on what breaks?
Johnny
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.
