Re: ...dos that mean..

[Holm Tiffe <holm%freibergnet.de@localhost>]

Holm Tiffe wrote:

> Holm Tiffe wrote:
> 
> > Jochen Kunz wrote:
> > 
> > > On Tue, 29 Jan 2013 09:52:06 +0100
> > > Holm Tiffe <holm%freibergnet.de@localhost> wrote:
> > > 
> > > > Think I have a /90 not a /90A... are the files correct for this?
> > > Yes. /90 and /90A are mostly identical. The /90A has a higher clock
> > > speed.
> > 
> > Ahh, ok. Maybe I can tune it a little? :-)
> > > 
> > > > Are there different Versions?
> > > Yes. I have version 1.3. You can MOP moot the cougar.sys file to
> > > perform the update.
> > > -- 
> > > 
> > > 
> > > \end{Jochen}
> > > 
> > > \ref{http://www.unixag-kl.fh-kl.de/~jkunz/}
> > 
> > Yes, read that and have the neccessary infrastructure running anyways.
> > But...I want to wait until at least the build process of the tools is
> > done...
> > GROFF_COMMAND_PREFIX='';  export GROFF_COMMAND_PREFIX;
> > GROFF_BIN_PATH=`echo /usr/src/tools/groff/obj/build/src/roff/groff
> > /usr/src/tools/groff/obj/build/src/roff/troff
> > /usr/src/tools/groff/obj/build/src/preproc/pic
> > /usr/src/tools/groff/obj/build/src/preproc/eqn
> > /usr/src/tools/groff/obj/build/src/preproc/tbl
> > /usr/src/tools/groff/obj/build/src/preproc/grn
> > /usr/src/tools/groff/obj/build/src/preproc/refer
> > /usr/src/tools/groff/obj/build/src/preproc/soelim
> > /usr/src/tools/groff/obj/build/src/preproc/html
> > /usr/src/tools/groff/obj/build/src/devices/grops
> > /usr/src/tools/groff/obj/build/src/devices/grohtml | sed -e 's|  *|:|g'`;
> > export GROFF_BIN_PATH;  sed -e "s;@VERSION@;1.19.2;"
> > /usr/src/gnu/dist/groff/doc/pic.ms  |
> > /usr/src/tools/groff/obj/build/src/roff/groff/groff
> > -M/usr/src/tools/groff/obj/build/tmac
> > -M/usr/src/tools/groff/../../gnu/dist/groff/tmac
> > -F/usr/src/tools/groff/obj/build/font
> > -F/usr/src/tools/groff/../../gnu/dist/groff/font -Upet -ww -Tps -ms -mwww 
> > >pic.ps
> > 
> > Currently that hing seems to be somewhere in groffand you wote that this
> > can last for weeks :-)
> > 
> > Regards,
> > 
> > Holm
> 
> 
> In the meantime the compilation of the tools is done so I've tried to boot
> that cougar.sys with b/100 ez and entering cougar.sys..nope.
> The FreeBSD mopd I've using is to stupid to boot elf or VAX binaries
> trying to port the netbsd mopd now... (argl...) 
> 
> Regards,
> 
> Holm
> 
> 


Ok guys, I've finally managed to netboot that cougar.sys file,
for sure it is newer than the firmware that was previously on the ROMS.
I now have a somewhat "nicer" sound on boot  ( :-| )and the bootmessage
is now:

49-A V1.4-0D0-V4.4   71 MHZ
08-00-2B-3C-1C-DB
64MB
                                       

OK

>>>

The 71 Mhz display is new.
The Problem with the mopd is, that it seems that it doesn't support
the download of afrom the VAX rom requested bootfile with a name.
renaming that cougar.sys to 08002b3c1cdb.SYS and b eza0 has done the trick,
B/100 ez and entering a filename doesn't work at all, thinks it's not
implemented, even in the netbsd mopd.


                        ****CAUTION****

--- EXECUTING THIS PROGRAM WILL CHANGE YOUR CURRENT ROM ---


Do you really want to continue [Y/N] ? : Y


 DO NOT TOUCH THE HALT BUTTON!

 DOING SO WILL RESULT IN LOSS OF OPERABLE STATE!

 The program will take at most several minutes.

 led codes display info 

 0111 0***          -   in process of programming FEPROM to 0's

 1000 0***          -   in process of programming FEPROM to 1's

 1001 0***          -   in process of programming new ROM image


 DO NOT TOUCH THE HALT BUTTON, OR YOU WILL DAMAGE THE CPU MODULE     !!!!


 !!!! THE SYSTEM WILL THEN DO A POWERUP RESTART and HALT at the console
!!!!



ÿªUþ
 
KA49-A V1.4-0D0-V4.4   71 MHZ
08-00-2B-3C-1C-DB
64MB

...
                                       
So far soo good.
The good news is, that it boots now every time w/o any problem the netbsd
netboot loader from the ethernet, like the rtVAx and the DECserver 300 also
do.
It also is booting the netbsd from dka0 flawlessly like before.

Want to hear the bad news?

It doesn't boot from dka100 like before.
IT DOESN'T BOOT FROM DKA1 ANYMORE!


>>> b dka100

 
?06 HLT INST
  PC= 00002AD6 PSL= 041F0000

>>> b dka1

 
%VMB-F-ERR, PC = 00001350
%VMB-I-STS, R0 = 00000908
?06 HLT INST
  PC= 00001693 PSL= 041F0000

>>> sh dev

  VMS/VMB      ADDR      DEVTYPE    NUMBYTES     RM/FX    WP    DEVNAM REV
  -------      ----      -------    --------     -----    --    ------ ---
  EZA0         08-00-2B-3C-1C-DB
  DKA0         A/0/0     DISK         4.29GB      FX            RZ29L-A 0814
  DKA100       A/1/0     DISK         4.22GB      FX            DCAS-34 S63A
 ..HostID..    A/6       INITR



I can netboot netbsd and mount sd1a,d,e, the fs's are clean, same when I boot 
from
sda0, all files are ok.

What the heck... it seems that I'm running circles around that dammned
VAXen... no end...


BTW: From my point off view the DCAS34330 is a good and trusty disk
(have more), but I had problems with the Emulex UC07 and UC08 on the PDP11.
Maybe that's related? Differences in the SCSI-slang? Has anyone sucessfully
working such a disk on a VS4000?


Changes the address from the DCAS to 0:

>>> sh dev

  VMS/VMB      ADDR      DEVTYPE    NUMBYTES     RM/FX    WP    DEVNAM
REV
  -------      ----      -------    --------     -----    --    ------
---
  EZA0         08-00-2B-3C-1C-DB
  DKA100       A/1/0     DISK         4.22GB      FX            DCAS-34
S63A
 ..HostID..    A/6       INITR



>>> b dka0

 
%VMB-F-ERR, PC = 00001350
%VMB-I-STS, R0 = 000001A4
?06 HLT INST
  PC= 00001693 PSL= 041F0000

>>> 

It's really not that easy..

Who had the 1.3 firmware?



Regards,

Holm
-- 
      Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, 
     Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583
  www.tsht.de, info%tsht.de@localhost, Fax +49 3731 74200, Mobil: 0172 8790 741