• Old SPARC hardware

    From Foggy@21:1/5 to All on Wed Dec 28 11:19:58 2016
    Hi all,

    I picked up a bunch of old Sparc hardware a few weeks ago. A SPARC 5, a SPARC 20 and an Ultra 2.

    None of them will boot a Solaris kernel. Tried Solaris 2.6 and 2.7.

    All of them report "The IDPROM contents are invalid" or similar. Is that the common cause of them not booting?

    cheers!
    ih

    The ULTRA2 does this:
    {0} ok boot cdrom
    Boot device: /sbus/SUNW,fas@e,8800000/sd@6,0:f File and args:
    Loading ufs-file-system package 1.4 04 Aug 1995 13:02:54.
    FCode UFS Reader 1.11 97/07/10 16:19:15.
    Redirected to slice: 1
    Loading: /platform/SUNW,Ultra-2/ufsboot
    Loading: /platform/sun4u/ufsboot
    Warning: IDprom checksum error.
    SunOS Release 5.7 Version Generic_106541-08 [UNIX(R) System V Release 4.0] Copyright (c) 1983-1999, Sun Microsystems, Inc.
    Invalid format code in IDprom.
    [gets no further]

    The SPARC5 just gets this far:
    ok boot cdrom
    Boot device: /iommu/sbus/espdma@5,8400000/esp@5,8800000/sd@6,0:d File and args:
    [nothing more]


    The SPARC 20 does this:
    <#0> ok boot cdrom
    Boot device: /iommu/sbus/espdma@f,400000/esp@f,800000/sd@6,0:d File and args: Warning: IDprom checksum error.
    Using default machine type Sun4m/60
    SunOS Release 5.6 Version Generic_105181-05 [UNIX(R) System V Release 4.0] Copyright (c) 1983-1997, Sun Microsystems, Inc.
    Invalid format code in IDprom.
    WARNING: Time-of-day chip had incorrect date; check and reset.
    Configuring devices...
    BAD TRAP: type=9 rp=fbe1cd74 addr=b5bc4000 mmu_fsr=126 rw=1
    BAD TRAP occurred in module "esp" due to an illegal access to a user address. sched: Data fault
    kernel read fault at addr=0xb5bc4000, pme=0x0
    MMU sfsr=126: Invalid Address on supv data fetch at level 1
    pte addr = 0xf59852d4, level = 1
    pid=0, pc=0xf5af3d40, sp=0xfbe1cdc0, psr=0x404004c6, context=0
    g1-g7: 40000, f026de48, f0287af4, 0, 0, 1, fbe1ce80
    Begin traceback... sp = fbe1cdc0
    Called from f0043240, fp=fbe1ce20, args=f5bc7558 f5afcdb4 f5afbff8 f5bc7558 0 0 Called from f00711f4, fp=fbe01d60, args=0 40400ae1 0 404000e1 0 0
    End traceback...
    panic: Data fault
    syncing file systems... [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1
    ] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [ 1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1]
    21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 [1] 21 cannot sync -- giving up
    rebooting...
    ā–’esetting ...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Doug McIntyre@21:1/5 to Foggy on Wed Dec 28 14:19:47 2016
    Foggy <ihardcas@gmail.com> writes:
    I picked up a bunch of old Sparc hardware a few weeks ago. A SPARC 5, a SPA= >RC 20 and an Ultra 2.

    None of them will boot a Solaris kernel. Tried Solaris 2.6 and 2.7.

    All of them report "The IDPROM contents are invalid" or similar. Is that th= >e common cause of them not booting?

    Hmm, I remember a bad IDPROM still letting you boot the systems, but
    you'll for sure have issues talking out on the Network (since the MAC
    address is stored in the IDPROM chip).

    I suspect the main reason your SS20 doesn't boot is from bad memory
    though. Couldn't tell you about the others.

    It looks like the Sun NVRAM HostID FAQ hosted on Squirrel.com now
    sells Swimware, but there are plenty of places to go for information
    contained within that FAQ, as well as many other projects to make a
    new one.

    So, I wouldn't discount it to being just the IDPROM chip battery going
    bad (which all SPARC systems up until the Nextra's or so when they
    switched to EEPROM cards) have a problem with. But probably other
    issues. But the IDPROM chips will definately have problems for you
    with the RTC and speaking on the Network if you do get these working otherwise.

    http://www.lib.ru/TXT/faqsunnvram.txt



    --
    Doug McIntyre
    doug@themcintyres.us

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Volker Borchert@21:1/5 to Doug McIntyre on Wed Dec 28 22:42:55 2016
    Doug McIntyre wrote:

    I suspect the main reason your SS20 doesn't boot is from bad memory
    though.

    Or grilled CPU. Some SuperSPARC and HyperSPARC have a reputation
    of running really hot, particularly when used in pairs and/or
    if/when the fans fail, and in my experience, they do. sunhelp.org
    used to have a "Rough Guide To MBus modules" that showed the
    critical combinations.

    To the OP: Check and if necessary replace the fans. Try to find a
    replacement MBus CPU, preferably the slowest, therefore requiring
    least cooling, type compatible with the SS20. Try with as little
    memory as possible. 64, maybe even 32 MB should do for 5.6 or 5.7.
    Once installed, 5.7 will run on sun4m with as little as 24 MB,
    maybe even less. But the installer insists on having some more.
    Remove all SBus cards, unplug the keyboard and hook up a terminal
    or emulator to ttya using 9600@8N1.

    --

    "I'm a doctor, not a mechanic." Dr Leonard McCoy <mccoy@ncc1701.starfleet.fed> "I'm a mechanic, not a doctor." Volker Borchert <v_borchert@despammed.com>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DoN. Nichols@21:1/5 to Foggy on Thu Dec 29 01:23:34 2016
    On 2016-12-28, Foggy <ihardcas@gmail.com> wrote:
    Hi all,

    I picked up a bunch of old Sparc hardware a few weeks ago. A SPARC 5,
    a SPARC 20 and an Ultra 2.

    None of them will boot a Solaris kernel. Tried Solaris 2.6 and 2.7.

    O.K. First off, I believe that all of the Ultra SPARCs require
    at least Solaris 8 or 9.

    All of them report "The IDPROM contents are invalid" or similar. Is
    that the common cause of them not booting?

    It is a common problem with older Sun systems. The IDPROM is a combination of a CMOS RAM, a TOD clock, and a coin cell -- all potted
    together. The two most important things in there are the HOSTID and the
    MAC address, though having the time is useful, too.

    The important part of the HOSTID is the starting part, which
    identifies what family of system you have -- thus defining where to look
    for various things which may be needed to complete the boot.

    There are instructions on the net for how to repair the NVRAM
    (surgery to allow you to connect a coin cell in place of the exhausted
    one in the chip package. Of course, this won't restore the data which
    was in the chip. You look up the HOSTID range based on what system you
    have, fill in the rest of the HOSTID with something a bit below making
    that part all 9s. This is done by keying in a special FORTH program
    into the OPENBOOT and running that to give access to the HOSTID and MAC
    areas of the ROM. (Details are on the net somewhere.) For the MAC
    address, one trick is to get an old net card made for a PC, take the MAC address from it, and crush the ROM from the card so there is never a duplication of the MAC address. :-)

    The only SPARC machines which I know of (from before the ones
    like the later UltraSPARC based ones) which don't have this problem
    were the Solbourne 4000 series, which had the HOSTID and the MAC address
    in a small ROM chip, and a coin cell holder to power the TOD clock. (No,
    They were not made by Sun, but were nice fast versions similar to the
    SS2.

    Solaris 2.6 should work well on the SS-20- and the SS-5, if it
    is complete enough with memory. Note that the SS-20 has both normal
    memory slots and ones for expansion memory for the framebuffer in the
    system. It will run without the additional framebufer memory, but not
    without the normal memory.

    IIRC, the SS-20 can support two CPUs (or four with some dual
    ones by ROSS which I ran for a while.

    The SS-5 came with at least three CPU speeds, with the fastest
    one having a postage-stamp sized fan (1" square) on top of the heat
    sink. I had one fail, and replaced the fan and it was happy again. I
    also had to replace the fan for a Ultra-1, which if I remember correctly
    would just get far enough to boot from the install CD-ROM before putting
    up an "overheating --- shutting down" warning.

    Do you have an old printed copy of the _Field Engineer's
    Handbook_, which has details about the various systems, including HOSTID
    ranges and the like -- and which RAM slots to populate first.


    Oh yes - also best to start with the keyboard and framebuffer unplugged, and set the EEPROM values to use the serial port (ttya) as a console. That way, not being able to work the framebuffer won't be a
    problem.

    And -- try running the diagonstics from the OpenBOOT PROM, which
    may find some of the problems.

    Do any of these have internal CD_ROM drives? If using an
    external one, it should be set to SCSI-ID 6 for all of these systems.

    Good Luck,
    DoN.
    --
    Remove oil spill source from e-mail
    Email: <BPdnicholsBP@d-and-d.com> | (KV4PH) Voice (all times): (703) 938-4564
    (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
    --- Black Holes are where God is dividing by zero ---

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Drazen Kacar@21:1/5 to DoN. Nichols on Thu Dec 29 20:50:51 2016
    DoN. Nichols wrote:
    On 2016-12-28, Foggy <ihardcas@gmail.com> wrote:
    Hi all,

    I picked up a bunch of old Sparc hardware a few weeks ago. A SPARC 5,
    a SPARC 20 and an Ultra 2.

    None of them will boot a Solaris kernel. Tried Solaris 2.6 and 2.7.

    O.K. First off, I believe that all of the Ultra SPARCs require
    at least Solaris 8 or 9.

    2.5.1 was the first release with UltraSPARC support, IIRC.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DoN. Nichols@21:1/5 to Drazen Kacar on Fri Dec 30 02:52:30 2016
    On 2016-12-29, Drazen Kacar <dave@fly.srk.fer.hr> wrote:
    DoN. Nichols wrote:
    On 2016-12-28, Foggy <ihardcas@gmail.com> wrote:
    Hi all,

    I picked up a bunch of old Sparc hardware a few weeks ago. A SPARC 5,
    a SPARC 20 and an Ultra 2.

    None of them will boot a Solaris kernel. Tried Solaris 2.6 and 2.7.

    O.K. First off, I believe that all of the Ultra SPARCs require
    at least Solaris 8 or 9.

    2.5.1 was the first release with UltraSPARC support, IIRC.

    My error, then.

    Now -- I have a couple of SS-5 boxen which I would like to be
    able to run Solaris 10 on. :-) (No expectations, however.)

    Enjoy,
    DoN.

    --
    Remove oil spill source from e-mail
    Email: <BPdnicholsBP@d-and-d.com> | (KV4PH) Voice (all times): (703) 938-4564
    (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
    --- Black Holes are where God is dividing by zero ---

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Casper H.S. Dik@21:1/5 to Drazen Kacar on Sat Dec 31 11:55:35 2016
    Drazen Kacar <dave@fly.srk.fer.hr> writes:

    DoN. Nichols wrote:
    On 2016-12-28, Foggy <ihardcas@gmail.com> wrote:
    Hi all,

    I picked up a bunch of old Sparc hardware a few weeks ago. A SPARC 5,
    a SPARC 20 and an Ultra 2.

    None of them will boot a Solaris kernel. Tried Solaris 2.6 and 2.7.

    O.K. First off, I believe that all of the Ultra SPARCs require
    at least Solaris 8 or 9.

    2.5.1 was the first release with UltraSPARC support, IIRC.

    Support for the first UltraSPARC systems was added in Solaris 2.5.
    (the Ultra 2 required 2.5.1).

    Casper

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Casper H.S. Dik@21:1/5 to Foggy on Sat Dec 31 11:53:13 2016
    Foggy <ihardcas@gmail.com> writes:

    I picked up a bunch of old Sparc hardware a few weeks ago. A SPARC 5,
    a SPARC 20 and an Ultra 2.

    None of them will boot a Solaris kernel. Tried Solaris 2.6 and 2.7.

    I think Solaris 8 should support SPARC 5 & 20 too and the Ultra 2
    should work even on later releases (depending on the actual
    CPU)

    All of them report "The IDPROM contents are invalid" or similar.
    Is that the common cause of them not booting?

    That could be the case as it is using the Hostid and the platform
    name to load the proper kernel modules.

    Casper

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Casper H.S. Dik@21:1/5 to DoN. Nichols on Sat Dec 31 11:57:08 2016
    "DoN. Nichols" <BPdnicholsBP@d-and-d.com> writes:

    On 2016-12-29, Drazen Kacar <dave@fly.srk.fer.hr> wrote:
    DoN. Nichols wrote:
    On 2016-12-28, Foggy <ihardcas@gmail.com> wrote:
    Hi all,

    I picked up a bunch of old Sparc hardware a few weeks ago. A SPARC 5,
    a SPARC 20 and an Ultra 2.

    None of them will boot a Solaris kernel. Tried Solaris 2.6 and 2.7.

    O.K. First off, I believe that all of the Ultra SPARCs require
    at least Solaris 8 or 9.

    2.5.1 was the first release with UltraSPARC support, IIRC.

    My error, then.

    Now -- I have a couple of SS-5 boxen which I would like to be
    able to run Solaris 10 on. :-) (No expectations, however.)

    Not possible. Sun4m (SS5, SS10, SS20) was dropped in Solaris 10
    when the 32 bit kernel was dropped for SPARC.

    Casper

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael Moeller@21:1/5 to All on Sat Dec 31 14:23:07 2016
    Am 12/28/2016 08:19 PM, schrieb Foggy:
    Hi all,

    I picked up a bunch of old Sparc hardware a few weeks ago. A SPARC 5, a SPARC 20 and an Ultra 2.

    None of them will boot a Solaris kernel. Tried Solaris 2.6 and 2.7.

    All of them report "The IDPROM contents are invalid" or similar. Is that the common cause of them not booting?

    cheers!
    ih

    Regarding the SS5 and SS20 (according to Mark Hendersons 'Sun NVRAM
    Hostid FAQ') you can try the following procedure. I have done this
    successfully several times. Power up the machine and press Stop-A.

    At the "ok" prompt execute the following (08:00:20:e3:e4:e5 is an
    example of the machines ethernet address)

    set-defaults
    setenv diag-switch? false
    8 0 20 E3 E4 E5 H1H2H3 mkpl

    Then press Control-D followed by a Control-R. If mkpl does NOT print a copyright notice, then it changed the IDPROM. You should make sure by
    looking at the idprom after using mkpl by executing the .idprom command.

    In case this fails, you can replace the NVRAM and redo the above
    procedure. I don't know about the Ultra, but M48T08-150PC1 chips from
    Mouser Electronics work with SS5 and SS20.


    Michael

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DoN. Nichols@21:1/5 to Dik on Sun Jan 1 03:05:18 2017
    On 2016-12-31, Casper H.S Dik <Casper.Dik@OrSPaMcle.COM> wrote:
    "DoN. Nichols" <BPdnicholsBP@d-and-d.com> writes:

    On 2016-12-29, Drazen Kacar <dave@fly.srk.fer.hr> wrote:
    DoN. Nichols wrote:

    [ ... ]

    Now -- I have a couple of SS-5 boxen which I would like to be
    able to run Solaris 10 on. :-) (No expectations, however.)

    Not possible. Sun4m (SS5, SS10, SS20) was dropped in Solaris 10
    when the 32 bit kernel was dropped for SPARC.

    As I said -- "No expectations, however". Not with that far a reach-back. :-)

    But this suggests that Solaris 9 should still work.
    Interesting. I've got it, but installed on nothing at present.

    Of course, my oldest Sun box (long retired, now) is a Sun 1/120 (MC68010 CPU) -- no chance for anything even semi-recent to work there.
    :-)

    Thanks for the reply, anyway. Always glad to hear from you as
    the best source of info on Sun equipment. And glad to see that you are
    still here.

    Happy New Year,
    DoN.

    --
    Remove oil spill source from e-mail
    Email: <BPdnicholsBP@d-and-d.com> | (KV4PH) Voice (all times): (703) 938-4564
    (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
    --- Black Holes are where God is dividing by zero ---

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Casper H.S. Dik@21:1/5 to Michael Moeller on Mon Jan 2 07:05:13 2017
    Michael Moeller <mmoel@t-online.de> writes:

    Am 12/28/2016 08:19 PM, schrieb Foggy:
    Hi all,

    I picked up a bunch of old Sparc hardware a few weeks ago. A SPARC 5, a SPARC 20 and an Ultra 2.

    None of them will boot a Solaris kernel. Tried Solaris 2.6 and 2.7.

    All of them report "The IDPROM contents are invalid" or similar. Is that the common cause of them not booting?

    cheers!
    ih

    Regarding the SS5 and SS20 (according to Mark Hendersons 'Sun NVRAM
    Hostid FAQ') you can try the following procedure. I have done this >successfully several times. Power up the machine and press Stop-A.

    At the "ok" prompt execute the following (08:00:20:e3:e4:e5 is an
    example of the machines ethernet address)

    I think the proper mac addrss should also listed in the label
    of the system.

    Casper

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mike Causer@21:1/5 to DoN. Nichols on Sat Jan 28 17:11:50 2017
    On 1 Jan 2017 03:05:18 GMT
    "DoN. Nichols" <BPdnicholsBP@d-and-d.com> wrote:

    Of course, my oldest Sun box (long retired, now) is a Sun
    1/120 (MC68010 CPU) -- no chance for anything even semi-recent to
    work there. :-)

    A 2/120 or a 1U ? I believe that some versions of NetBSD can run on the
    2/120 which might be fairly recent. My old 2/120 in ComputerVision
    casing still has the last SunOs I put on it in the 1980s, and its
    current owner & I plan to see if it will fire up later this year.

    BTW do you have any spares for it? Could do with more memory to run
    the CADCAM programs that are on there. (CIS Medusa for CADCAM
    aficionados.)


    Mike

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DoN. Nichols@21:1/5 to Mike Causer on Sun Jan 29 03:04:08 2017
    On 2017-01-28, Mike Causer <m.r.causer@goglemail.com> wrote:
    On 1 Jan 2017 03:05:18 GMT
    "DoN. Nichols" <BPdnicholsBP@d-and-d.com> wrote:

    Of course, my oldest Sun box (long retired, now) is a Sun
    1/120 (MC68010 CPU) -- no chance for anything even semi-recent to
    work there. :-)

    A 2/120 or a 1U ?

    2/120 -- on casters -- deskside cabinet. Intel Multibus cage
    inside. Sun2 arcitecture. As I got it -- with a SCSI interfaced drive
    inside, and a rather early QIC tape drive for loading the OS. (Not
    compatible with the later ones, which each typically will handle the
    current density and the pervious density as read-only, and all my other
    drives are too new to even read that drive's tapes.

    I believe that some versions of NetBSD can run on the 2/120 which might be fairly recent.

    Hmm ... depends on how sparse a memory it can run in. My AT&T
    Unix-PCs (3B1 and 7300) have a maximum physical and virtual memory of
    4 MB, and I don't think that any of the linux or BSD flavors currently available will run on that little space. (Both use the Motorla MC68010
    CPU, the first one of the 68k family which could support virtual memory,
    thanks to having the ability to cache the registers when an instruction
    fails on no memory, so the OS could map in the memory needed and restart
    the instruction.

    My old 2/120 in ComputerVision
    casing

    Computervison? That does not ring a bell for me. The case
    which I have is wide enough to hold the Multibus card cage with the
    backplane connectors to the right, and the left side of the case somes
    off to allow service.

    BTW -- A warning for anyone who did not know this, or who did and forgot
    it over the years. The tape drive uses the same power connector as the
    SCSI drive (which may have been MFM or ESID with a SCSI card), but the
    disk and interface cards use the typical 5V and 12V, while the cartridge
    tape drive uses 5V and 24V (or was it 28V?) Anyway -- don't swap those connectors. :-)

    It was my first Sun, ans was old at the time I got it.

    still has the last SunOs I put on it in the 1980s, and its
    current owner & I plan to see if it will fire up later this year.

    Good luck with that.

    BTW do you have any spares for it? Could do with more memory to run
    the CADCAM programs that are on there. (CIS Medusa for CADCAM
    aficionados.)

    I'm trying to remember what the max memory was for that system.
    The CPU could address up to a maximum of 16 MB, and I think that the
    memory map in there topped out at either 4 MB or 8 MB -- a bit thin for
    CAD/CAM work. What flavor of G-code do the available post-processors
    produce from it? (That is -- for what machines and controllers?) Are
    they flexible enough so they could be modified to output for LinuxCNC
    (used to be EMC from NIST -- Extensible Machiine Controller -- before
    someone else claimed ownership of the EMC name. :-)

    I don't think that I have ans spares which would fit, unless I
    stole them from the (also MultiBus) COSMOS CMS-16 which ran a Unisoft
    port of v7 unix on a MC68000 (too old to run a virtual memory unix, just
    plain swapping. :-) That one had two PLESSEY RAM cards in it with ECC
    built in. One of them failed, and it turned out to be a delay line
    which produced the different strobe timing (row and column) for the RAM
    chips. :-)

    Enjoy,
    DoN.

    --
    Remove oil spill source from e-mail
    Email: <BPdnicholsBP@d-and-d.com> | (KV4PH) Voice (all times): (703) 938-4564
    (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
    --- Black Holes are where God is dividing by zero ---

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mike Causer@21:1/5 to DoN. Nichols on Sun Jan 29 19:16:19 2017
    On 29 Jan 2017 03:04:08 GMT
    "DoN. Nichols" <BPdnicholsBP@d-and-d.com> wrote:

    2/120 -- on casters -- deskside cabinet. Intel Multibus cage
    inside. Sun2 arcitecture. As I got it -- with a SCSI interfaced
    drive inside, and a rather early QIC tape drive for loading the OS.

    QIC-4 IIRC. I could transfer stuff between work Suns & home on tape
    until I had a Sparc1+ on my desk. Upgrading at home to a 3/50 then 3/60
    with QIC-24 tape drives sorted that out.


    My old 2/120 in ComputerVision casing

    Computervison? That does not ring a bell for me.

    Computervision, a CADCAM company in Boston, licensed the Sun-2 and then
    -3 for their various product lines. I don't think they ever got CADDS
    to run on the -2 but we got our Medusa line to work satisfactorily so
    when CV announced the new hardware that is what I demonstrated. Even
    better on the -3 of course. The CPU board in mine is a Sun one and the
    other boards are standard Multibus from several vendors. I think that
    only the casing is different because it has many serial ports which Sun
    would not have needed but CV did. So apart from the sheet-metal all CV
    did was assemble it.


    I'm trying to remember what the max memory was for that
    system. The CPU could address up to a maximum of 16 MB, and I think
    that the memory map in there topped out at either 4 MB or 8 MB -- a
    bit thin for CAD/CAM work.

    I had 7 x 1 MB boards in mine which were replaced by a single 2 MB board
    after it left my hands. Taking out the Sky floating-point board would have allowed 8 MB -- but been a retrograde step for my purposes.



    What flavor of G-code do the available
    post-processors produce from it? (That is -- for what machines and controllers?) Are they flexible enough so they could be modified to
    output for LinuxCNC (used to be EMC from NIST -- Extensible Machiine Controller -- before someone else claimed ownership of the EMC
    name. :-)

    It's a 1986 version (because it has the best user interface -- guess
    what I worked on...) I don't think it could drive anything at all in
    2017.


    I don't think that I have ans spares which would fit, unless I
    stole them from the (also MultiBus) COSMOS CMS-16 which ran a Unisoft
    port of v7 unix on a MC68000 (too old to run a virtual memory unix,
    just plain swapping. :-)

    Ahhhh, the museum also has a machine with Unisoft V7 on the Lark discs.
    That's a Unix I haven't used so perhaps I could come back to you with
    some questions later. There are also several Sun-3 Multibus systems we
    have already robbed for spare Multibus cards, so another tour with
    screwdriver in hand is called for. Sparcs they have counted in
    dozens...
    ... and some original EDSAC components ;-)



    Mike

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DoN. Nichols@21:1/5 to Mike Causer on Mon Jan 30 05:12:07 2017
    On 2017-01-29, Mike Causer <m.r.causer@goglemail.com> wrote:
    On 29 Jan 2017 03:04:08 GMT
    "DoN. Nichols" <BPdnicholsBP@d-and-d.com> wrote:

    2/120 -- on casters -- deskside cabinet. Intel Multibus cage
    inside. Sun2 architecture. As I got it -- with a SCSI interfaced
    drive inside, and a rather early QIC tape drive for loading the OS.

    QIC-4 IIRC. I could transfer stuff between work Suns & home on tape
    until I had a Sparc1+ on my desk. Upgrading at home to a 3/50 then 3/60
    with QIC-24 tape drives sorted that out.

    O.K. Of course, the drives kept getting higher density. IIRC,
    the SUN-3 machines were 60 MB, and the early SPARC drives were 150 MB.
    (Then the Exabyte drives came along. :-)

    My old 2/120 in ComputerVision casing

    Computervison? That does not ring a bell for me.

    Computervision, a CADCAM company in Boston, licensed the Sun-2 and then
    -3 for their various product lines. I don't think they ever got CADDS
    to run on the -2 but we got our Medusa line to work satisfactorily so
    when CV announced the new hardware that is what I demonstrated. Even
    better on the -3 of course. The CPU board in mine is a Sun one and the
    other boards are standard Multibus from several vendors. I think that
    only the casing is different because it has many serial ports which Sun
    would not have needed but CV did. So apart from the sheet-metal all CV
    did was assemble it.

    O.K. Sort of reminds me of the first I heard of Silicon
    Graphics. They (at that time) advertised/claimed "The fastest graphics
    under the Sun" -- as they made fast high-resolution framebuffers for the
    Suns of the time. I knew about it because they came to the lab to demo
    their gear -- and were using a fancy CAD system to do so. I have no
    idea whether there was anything CAM on it, as that was before I
    experienced my first CNC hardware -- a Bridgeport clone running Anilam's
    CNC conversion.

    I'm trying to remember what the max memory was for that
    system. The CPU could address up to a maximum of 16 MB, and I think
    that the memory map in there topped out at either 4 MB or 8 MB -- a
    bit thin for CAD/CAM work.

    I had 7 x 1 MB boards in mine which were replaced by a single 2 MB board after it left my hands. Taking out the Sky floating-point board would have allowed 8 MB -- but been a retrograde step for my purposes.

    O.K. The 8 MB sounds right then. I guess the 4MB came from my
    memory of the 3B1/7300 systems with the same CPU chip. (But a SysVr2
    version with BSD and SysVr4 additions. :-)

    What flavor of G-code do the available
    post-processors produce from it? (That is -- for what machines and
    controllers?) Are they flexible enough so they could be modified to
    output for LinuxCNC (used to be EMC from NIST -- Extensible Machiine
    Controller -- before someone else claimed ownership of the EMC
    name. :-)

    It's a 1986 version (because it has the best user interface -- guess
    what I worked on...) I don't think it could drive anything at all in
    2017.

    Well ... I've been converting an old Bridgeport BOSS-3 mill
    (apparently BOSS-1 and BOSS-2 never escaped the factory), and I think
    that it was from 1977 or so, so it might have worked.

    I don't think that I have any spares which would fit, unless I stole
    them from the (also MultiBus) COSMOS CMS-16/UNX which ran a Unisoft port
    of v7 unix on a MC68000 (too old to run a virtual memory unix, just
    plain swapping. :-)

    Ahhhh, the museum also has a machine with Unisoft V7 on the Lark
    discs. That's a Unix I haven't used so perhaps I could come back to
    you with some questions later.

    O.K. It was a very slow OS -- on the 8 MHz MC-68000 (compared
    to the 10 Mhz in the 3B1/7300 and the Sun-2/120). I at about the same
    time got a Tektronix 6130 (National Semiconductor 16032 CPU IIRC) which
    had an open guest account but which would not turn on until I found a
    hidden fuse buried in the power supply. It came with no known
    passwords, and had been used as a training tool. I was able to get the
    hash of the root password (before the days of /etc/shadow) and wrote a
    program to run just a single salt on the hashing of trial passwords from
    all three systems -- the AT&T 7300/3B1, the COSMOS CMS-16/UNX, and the
    TEK 6300 itself. I combined the three /etc/dict/word files to improve
    my chances. (And I discovered that the loader would work because the
    library was scrambled. I had to copy it into the guest home directory,
    re-hash it (I forget the term that was used, but BSD needed it whenever
    the library was modified, and this was a BSD 4.2). Anyway, the 3B1/7300
    ran the fastest, the Tek 6300 a bit slower, and the Unisoft v7 in the
    COSMOS CMS-16/UNX was deadly slow. (Granted it was 8 MHZ 68000 instead
    of 10 MHz 68010, so it should be a bit slower anyway, but not *that*
    slow.) I eventually figured out why. This was a port of v7 unix from
    the PDP-11. Well ... examining some assembly language output from the compilers, I discovered that the COSMOS CMS-16/UNX with its v7 port was treating the MC 68000 as a PDP-11. If the PDP-11 didn't have the
    instructions, they were not used. (The only exceptions were the LNK and
    ULINK instructions for building and destroying the stack for
    subroutines. The real killer was array indexing. It calculated the
    offsets into the index one part at a time, while the AT&T
    UnixPC/7300/3B1 used the instruction in the MC-68010 where you could do
    a two-dimensional array by simply putting size of an object in one
    register, X and Y dimensions of the array in two other registers, and X
    and Y address in two more, and then calling a single instruction. Zap,
    the offset to get what you want.

    I didn't bother digging any deeper to see what else they were
    doing the slow way.

    But -- I did learn a lot about unix from that system. It was my
    first personal unix box (bought at a hamfest) and I eventually had it
    running two Fujitsu SMD interface 84 MB 8" drives. (I was limited to
    the few drives for which drivers were already compiled into the kernel.)
    No .o files for re-compiling the kernel with that one. Maybe you have
    it.

    Another pain was that the offset from GMT time was compiled into
    the kernel, with no easy way to change it. I finally discovered where
    it hid in the kernel, and did a change on a running kernel (after saving
    a copy of the old one to be safe). It also was just about the time of
    the change of DST dates, so even after I moved it to the proper coast,
    it was still wrong near the beginning and end of DST period. :-) I did
    get the sources for the system which is still used, and compiled that
    for programs which *I* wrote, but I didn't have the sources to
    re-compile a lot of the regular programs which came with the system,
    including cron. :-)

    There are also several Sun-3 Multibus systems we
    have already robbed for spare Multibus cards, so another tour with screwdriver in hand is called for. Sparcs they have counted in
    dozens...
    ... and some original EDSAC components ;-)

    Good Luck,
    DoN.

    --
    Remove oil spill source from e-mail
    Email: <BPdnicholsBP@d-and-d.com> | (KV4PH) Voice (all times): (703) 938-4564
    (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
    --- Black Holes are where God is dividing by zero ---

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From m. thompson@21:1/5 to DoN. Nichols on Mon Jan 30 04:49:22 2017
    On Monday, January 30, 2017 at 12:13:06 AM UTC-5, DoN. Nichols wrote:
    On 2017-01-29, Mike Causer <m.r.causer@goglemail.com> wrote:
    On 29 Jan 2017 03:04:08 GMT
    "DoN. Nichols" <BPdnicholsBP@d-and-d.com> wrote:

    2/120 -- on casters -- deskside cabinet. Intel Multibus cage
    inside. Sun2 architecture. As I got it -- with a SCSI interfaced
    drive inside, and a rather early QIC tape drive for loading the OS.

    QIC-4 IIRC. I could transfer stuff between work Suns & home on tape
    until I had a Sparc1+ on my desk. Upgrading at home to a 3/50 then 3/60 with QIC-24 tape drives sorted that out.

    O.K. Of course, the drives kept getting higher density. IIRC,
    the SUN-3 machines were 60 MB, and the early SPARC drives were 150 MB.
    (Then the Exabyte drives came along. :-)

    My old 2/120 in ComputerVision casing

    Computervison? That does not ring a bell for me.

    Computervision, a CADCAM company in Boston, licensed the Sun-2 and then
    -3 for their various product lines. I don't think they ever got CADDS
    to run on the -2 but we got our Medusa line to work satisfactorily so
    when CV announced the new hardware that is what I demonstrated. Even better on the -3 of course. The CPU board in mine is a Sun one and the other boards are standard Multibus from several vendors. I think that
    only the casing is different because it has many serial ports which Sun would not have needed but CV did. So apart from the sheet-metal all CV
    did was assemble it.

    O.K. Sort of reminds me of the first I heard of Silicon
    Graphics. They (at that time) advertised/claimed "The fastest graphics
    under the Sun" -- as they made fast high-resolution framebuffers for the
    Suns of the time. I knew about it because they came to the lab to demo
    their gear -- and were using a fancy CAD system to do so. I have no
    idea whether there was anything CAM on it, as that was before I
    experienced my first CNC hardware -- a Bridgeport clone running Anilam's
    CNC conversion.

    I'm trying to remember what the max memory was for that
    system. The CPU could address up to a maximum of 16 MB, and I think
    that the memory map in there topped out at either 4 MB or 8 MB -- a
    bit thin for CAD/CAM work.

    I had 7 x 1 MB boards in mine which were replaced by a single 2 MB board after it left my hands. Taking out the Sky floating-point board would have allowed 8 MB -- but been a retrograde step for my purposes.

    O.K. The 8 MB sounds right then. I guess the 4MB came from my
    memory of the 3B1/7300 systems with the same CPU chip. (But a SysVr2
    version with BSD and SysVr4 additions. :-)

    What flavor of G-code do the available
    post-processors produce from it? (That is -- for what machines and
    controllers?) Are they flexible enough so they could be modified to
    output for LinuxCNC (used to be EMC from NIST -- Extensible Machiine
    Controller -- before someone else claimed ownership of the EMC
    name. :-)

    It's a 1986 version (because it has the best user interface -- guess
    what I worked on...) I don't think it could drive anything at all in
    2017.

    Well ... I've been converting an old Bridgeport BOSS-3 mill
    (apparently BOSS-1 and BOSS-2 never escaped the factory), and I think
    that it was from 1977 or so, so it might have worked.

    I don't think that I have any spares which would fit, unless I stole
    them from the (also MultiBus) COSMOS CMS-16/UNX which ran a Unisoft port >> of v7 unix on a MC68000 (too old to run a virtual memory unix, just
    plain swapping. :-)

    Ahhhh, the museum also has a machine with Unisoft V7 on the Lark
    discs. That's a Unix I haven't used so perhaps I could come back to
    you with some questions later.

    O.K. It was a very slow OS -- on the 8 MHz MC-68000 (compared
    to the 10 Mhz in the 3B1/7300 and the Sun-2/120). I at about the same
    time got a Tektronix 6130 (National Semiconductor 16032 CPU IIRC) which
    had an open guest account but which would not turn on until I found a
    hidden fuse buried in the power supply. It came with no known
    passwords, and had been used as a training tool. I was able to get the
    hash of the root password (before the days of /etc/shadow) and wrote a program to run just a single salt on the hashing of trial passwords from
    all three systems -- the AT&T 7300/3B1, the COSMOS CMS-16/UNX, and the
    TEK 6300 itself. I combined the three /etc/dict/word files to improve
    my chances. (And I discovered that theĀ loader would work because the library was scrambled. I had to copy it into the guest home directory, re-hash it (I forget the term that was used, but BSD needed it whenever
    the library was modified, and this was a BSD 4.2). Anyway, the 3B1/7300
    ran the fastest, the Tek 6300 a bit slower, and the Unisoft v7 in the
    COSMOS CMS-16/UNX was deadly slow. (Granted it was 8 MHZ 68000 instead
    of 10 MHz 68010, so it should be a bit slower anyway, but not *that*
    slow.) I eventually figured out why. This was a port of v7 unix from
    the PDP-11. Well ... examining some assembly language output from the compilers, I discovered that the COSMOS CMS-16/UNX with its v7 port was treating the MC 68000 as a PDP-11. If the PDP-11 didn't have the instructions, they were not used. (The only exceptions were the LNK and
    ULINK instructions for building and destroying the stack for
    subroutines. The real killer was array indexing. It calculated the
    offsets into the index one part at a time, while the AT&T
    UnixPC/7300/3B1 used the instruction in the MC-68010 where you could do
    a two-dimensional array by simply putting size of an object in one
    register, X and Y dimensions of the array in two other registers, and X
    and Y address in two more, and then calling a single instruction. Zap,
    the offset to get what you want.

    I didn't bother digging any deeper to see what else they were
    doing the slow way.

    But -- I did learn a lot about unix from that system. It was my
    first personal unix box (bought at a hamfest) and I eventually had it
    running two Fujitsu SMD interface 84 MB 8" drives. (I was limited to
    the few drives for which drivers were already compiled into the kernel.)
    No .o files for re-compiling the kernel with that one. Maybe you have
    it.

    Another pain was that the offset from GMT time was compiled into
    the kernel, with no easy way to change it. I finally discovered where
    it hid in the kernel, and did a change on a running kernel (after saving
    a copy of the old one to be safe). It also was just about the time of
    the change of DST dates, so even after I moved it to the proper coast,
    it was still wrong near the beginning and end of DST period. :-) I did
    get the sources for the system which is still used, and compiled that
    for programs which *I* wrote, but I didn't have the sources to
    re-compile a lot of the regular programs which came with the system, including cron. :-)

    There are also several Sun-3 Multibus systems we have already robbed for spare Multibus cards, so another tour with screwdriver in hand is called for. Sparcs they have counted in
    dozens...
    ... and some original EDSAC components ;-)

    Good Luck,
    DoN.

    --
    Remove oil spill source from e-mail
    Email: <BPdnicholsBP@d-and-d.com> | (KV4PH) Voice (all times): (703) 938-4564
    (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
    --- Black Holes are where God is dividing by zero ---

    My 2/120 has two 80MB ESDI drives on a SCSI adapter behind the 20 MB tape drive and an external cabinet containing two Hitachi 124 MB 10" SMD disks. I helped debug the NetBSD port and the TME 2/120 emulator on this system. I also have a 2/50 and a 2/75
    that will net boot from the 2/120.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DoN. Nichols@21:1/5 to m. thompson on Tue Jan 31 04:44:53 2017
    On 2017-01-30, m. thompson <michael.99.thompson@gmail.com> wrote:

    [ ... ]

    My 2/120 has two 80MB ESDI drives on a SCSI adapter behind the 20 MB
    tape drive and an external cabinet containing two Hitachi 124 MB 10" SMD disks. I helped debug the NetBSD port and the TME 2/120 emulator on this system. I also have a 2/50 and a 2/75 that will net boot from the 2/120.

    Sounds like a pretty good example of the machine.

    Was the framebuffer a B&W or color to start with -- before the
    fancy one for the CAD/CAM system.

    Enjoy,
    DoN.

    --
    Remove oil spill source from e-mail
    Email: <BPdnicholsBP@d-and-d.com> | (KV4PH) Voice (all times): (703) 938-4564
    (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
    --- Black Holes are where God is dividing by zero ---

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From m. thompson@21:1/5 to DoN. Nichols on Tue Jan 31 17:02:07 2017
    On Monday, January 30, 2017 at 11:42:22 PM UTC-5, DoN. Nichols wrote:
    On 2017-01-30, m. thompson <michael.99.thompson@gmail.com> wrote:

    [ ... ]

    My 2/120 has two 80MB ESDI drives on a SCSI adapter behind the 20 MB
    tape drive and an external cabinet containing two Hitachi 124 MB 10" SMD disks. I helped debug the NetBSD port and the TME 2/120 emulator on this system. I also have a 2/50 and a 2/75 that will net boot from the 2/120.

    Sounds like a pretty good example of the machine.

    Was the framebuffer a B&W or color to start with -- before the
    fancy one for the CAD/CAM system.

    Enjoy,
    DoN.

    --
    Remove oil spill source from e-mail
    Email: <BPdnicholsBP@d-and-d.com> | (KV4PH) Voice (all times): (703) 938-4564
    (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
    --- Black Holes are where God is dividing by zero ---

    Mine still has the B&W framebuffer. I have a color framebuffer but have never installed it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DoN. Nichols@21:1/5 to m. thompson on Wed Feb 1 05:03:29 2017
    On 2017-02-01, m. thompson <michael.99.thompson@gmail.com> wrote:
    On Monday, January 30, 2017 at 11:42:22 PM UTC-5, DoN. Nichols wrote:
    On 2017-01-30, m. thompson <michael.99.thompson@gmail.com> wrote:

    [ ... ]

    My 2/120 has two 80MB ESDI drives on a SCSI adapter behind the 20 MB
    tape drive and an external cabinet containing two Hitachi 124 MB 10" SMD >> > disks. I helped debug the NetBSD port and the TME 2/120 emulator on this >> > system. I also have a 2/50 and a 2/75 that will net boot from the 2/120. >>
    Sounds like a pretty good example of the machine.

    Was the framebuffer a B&W or color to start with -- before the
    fancy one for the CAD/CAM system.

    I think that I do to -- somewhere -- but finding it is a bit
    tricky. :-)

    Ever had to deal with the "high resolution" B&W monitors for the
    Sun-3 family? My experience is that they take something like a half
    hour of warmup to get bright enough to see. :-)

    Enjoy,
    DoN.

    --
    Remove oil spill source from e-mail
    Email: <BPdnicholsBP@d-and-d.com> | (KV4PH) Voice (all times): (703) 938-4564
    (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
    --- Black Holes are where God is dividing by zero ---

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul E Coad@21:1/5 to m. thompson on Wed Feb 1 18:29:04 2017
    m. thompson <michael.99.thompson@gmail.com> wrote:

    [snip]
    My 2/120 has two 80MB ESDI drives on a SCSI adapter behind the 20 MB tape drive and an external cabinet containing two Hitachi 124 MB 10" SMD disks. I helped debug the NetBSD port and the TME 2/120 emulator on this system. I also have a 2/50 and a 2/75
    that will net boot from the 2/120.

    Can you provide some details on the 2/75? I can't find any references to
    it online. Is this a custom setup with a 2/50 cpu board in a 3/75 case?

    Thanks,

    --paul

    My is valid coad sonic net
    address not use: at dot

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From YTC#1@21:1/5 to Casper H.S. Dik on Fri Feb 3 09:59:09 2017
    On 12/31/16 11:53 AM, Casper H.S. Dik wrote:
    Foggy <ihardcas@gmail.com> writes:

    I picked up a bunch of old Sparc hardware a few weeks ago. A SPARC 5,
    a SPARC 20 and an Ultra 2.

    None of them will boot a Solaris kernel. Tried Solaris 2.6 and 2.7.

    I think Solaris 8 should support SPARC 5 & 20 too and the Ultra 2
    should work even on later releases (depending on the actual
    CPU)

    For S10, >200Mhz IIRC ?


    All of them report "The IDPROM contents are invalid" or similar.
    Is that the common cause of them not booting?

    That could be the case as it is using the Hostid and the platform
    name to load the proper kernel modules.

    Casper




    --
    Bruce Porter
    "The internet is a huge and diverse community but mainly friendly" http://ytc1.blogspot.co.uk/
    There *is* an alternative! http://www.openoffice.org/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Casper H.S. Dik@21:1/5 to bdp@ytc1-spambin.co.uk on Fri Feb 3 10:36:07 2017
    YTC#1 <bdp@ytc1-spambin.co.uk> writes:

    On 12/31/16 11:53 AM, Casper H.S. Dik wrote:
    Foggy <ihardcas@gmail.com> writes:

    I picked up a bunch of old Sparc hardware a few weeks ago. A SPARC 5,
    a SPARC 20 and an Ultra 2.

    None of them will boot a Solaris kernel. Tried Solaris 2.6 and 2.7.

    I think Solaris 8 should support SPARC 5 & 20 too and the Ultra 2
    should work even on later releases (depending on the actual
    CPU)

    For S10, >200Mhz IIRC ?

    I think all sun4m are supported; perhaps the amount of memory
    is more critical. 200MHz S10? I think the SuperSPARCs never
    went further than 90MHz. HyperSPARC went to 200MHz but that
    was after market (not sure it was supported in S10s?

    Casper

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From YTC#1@21:1/5 to Casper H.S. Dik on Fri Feb 3 11:27:25 2017
    On 02/ 3/17 10:36 AM, Casper H.S. Dik wrote:
    YTC#1 <bdp@ytc1-spambin.co.uk> writes:

    On 12/31/16 11:53 AM, Casper H.S. Dik wrote:
    Foggy <ihardcas@gmail.com> writes:

    I picked up a bunch of old Sparc hardware a few weeks ago. A SPARC 5,
    a SPARC 20 and an Ultra 2.

    None of them will boot a Solaris kernel. Tried Solaris 2.6 and 2.7.

    I think Solaris 8 should support SPARC 5 & 20 too and the Ultra 2
    should work even on later releases (depending on the actual
    CPU)

    For S10, >200Mhz IIRC ?

    I think all sun4m are supported; perhaps the amount of memory
    is more critical. 200MHz S10? I think the SuperSPARCs never

    No, but the Ultra 2 should work http://docs.oracle.com/cd/E19253-01/817-0544/webstart-96/index.html

    Depending on the CPU speed.
    I remember a tweak that was dropped out way to get the lab Ultra2s to
    run S10 :-)

    went further than 90MHz. HyperSPARC went to 200MHz but that
    HyperSPARC. That brings back memories, had that in some SS20s (googles),
    yep 200Mhz... and aha, taken over by Fuji

    was after market (not sure it was supported in S10s?

    Casper




    --
    Bruce Porter
    "The internet is a huge and diverse community but mainly friendly" http://ytc1.blogspot.co.uk/
    There *is* an alternative! http://www.openoffice.org/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Miod Vallat@21:1/5 to All on Tue Feb 14 19:00:13 2017
    I think all sun4m are supported; perhaps the amount of memory
    is more critical. 200MHz S10? I think the SuperSPARCs never
    went further than 90MHz. HyperSPARC went to 200MHz but that
    was after market (not sure it was supported in S10s?

    With a recent enough PROM, you can run a 200MHz HyperSPARC in an SS10,
    but due to MBus clock limitations on the SS10 motherboard, the
    processors will only run at 180MHz.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)