[rescue] Unhappy MicroVAX II

Ian King IanK at vulcan.com
Thu Apr 18 00:28:06 CDT 2013

Thanks for rattling some dusty neuristors, ISTR the TOY battery has to be
good to boot.  There is a Radio Shack replacement battery for the
Panasonic cordless phone that is a nearly perfect fit: the right
connector, but the battery pack itself is just a tad to big for the clip
that holds down the original.  At least that's what I remember from my
4000/300.  -- Ian

On 4/17/13 6:29 PM, "Tom publix" <ittybittybytes at gmail.com> wrote:

>You probably need to change the little pack of batteries that are behind
>the console panel. They are needed to run the TOY clock but run down, they
>can cause weird thing to happen (besides not wanting to boot) I'm not sure
>what the voltage are on these things, but if you don't want to do it
>yourself, you can have one made  at my local Batteries etc.
>On Tue, Apr 16, 2013 at 12:00 PM, Ian Finder <ian.finder at gmail.com> wrote:
>> Nope, no hex display at all. Totally dark, even with all the other
>> cards removed. All ends of the cables were reseated and checked a lot.
>> There's still lights on the card edge; the green DC-OK led, and some red
>> ones.
>> But the hex display (and serial console) is totally a no show.
>> At MC6810's suggestion I'll check the voltages& scope the PSU when I get
>> home, but the LEDs on the front turn on and DC-GOOD is among them.
>> On Tue, Apr 16, 2013 at 10:25 AM, Mouse <mouse at rodents-montreal.org>
>> wrote:
>> > > [...]  Still nothin' on the hex display. :(
>> >
>> > Nothing at all?  As in, it's not even lit up?  That's definitely not
>> > right; no matter what the data lines are driven as you should get
>> > something displayed.  My first suspect there would be unplugged or
>> > mis-plugged cables or some such.  (Don't forget to check the cab kit
>> > end of the cable too, not just the CPU end.)
>> >
>> > I don't know the details, but it strikes me as at least possible that
>> > mis-plugged or loose cable could have the CPU thinking it's not CPU 0
>> > and it's thus holding itself in reset waiting for some other CPU to
>> > tell it to boot.
>> >
>> > Or if you mean it's just stuck showing F, that has a lot more possible
>> > failure modes - it's set to F at power-up and the second instruction
>> > executed from the ROMs sets it to E.
>> >
>> > /~\ The ASCII                             Mouse
>> > \ / Ribbon Campaign
>> >  X  Against HTML                mouse at rodents-montreal.org
>> > / \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B
>> > _______________________________________________
>> > rescue list - http://www.sunhelp.org/mailman/listinfo/rescue
>> >
>> --
>>    Ian Finder
>>    (206) 395-MIPS
>>    ian.finder at gmail.com
>> _______________________________________________
>> rescue list - http://www.sunhelp.org/mailman/listinfo/rescue
>rescue list - http://www.sunhelp.org/mailman/listinfo/rescue

More information about the rescue mailing list