<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:media="http://search.yahoo.com/mrss/"><channel><title><![CDATA[Symbolics LISP Engineering]]></title><description><![CDATA[one cons leads to another]]></description><link>https://symbolics.lisp.engineer/</link><generator>Ghost 0.9</generator><lastBuildDate>Sun, 14 Sep 2025 16:19:18 GMT</lastBuildDate><atom:link href="https://symbolics.lisp.engineer/rss/" rel="self" type="application/rss+xml"/><ttl>60</ttl><item><title><![CDATA[Symbolics LAN - Overview]]></title><description><![CDATA[<p>Over the past two weeks, I set up a small Symbolics LAN, and thought I would share some of the process and findings. I will write a post about each item, but the topics already concluded cover:</p>

<ul>
<li>Performance challenges of the Merlin Ethernet under load, and modern 10Base5 to 10BaseT</li></ul>]]></description><link>https://symbolics.lisp.engineer/symbolics-lan-overview/</link><guid isPermaLink="false">58b50770-070f-4f5b-afbd-0f856e7c3b28</guid><category><![CDATA[genera]]></category><category><![CDATA[symbolics]]></category><category><![CDATA[lan]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Sun, 09 May 2021 21:34:56 GMT</pubDate><media:content url="https://symbolics.lisp.engineer/content/images/2021/05/IMG_20210506_163257.jpg" medium="image"/><content:encoded><![CDATA[<img src="https://symbolics.lisp.engineer/content/images/2021/05/IMG_20210506_163257.jpg" alt="Symbolics LAN - Overview"><p>Over the past two weeks, I set up a small Symbolics LAN, and thought I would share some of the process and findings. I will write a post about each item, but the topics already concluded cover:</p>

<ul>
<li>Performance challenges of the Merlin Ethernet under load, and modern 10Base5 to 10BaseT transceivers</li>
<li>An improvement to the stability of my first XL1201 which I was unstable, some five years ago</li>
<li>Y2k problems with the <code>QFILE</code> protocol under Chaosnet, and a "hotfix" to Genera's <code>QFILE</code> client to bypass them (this is deprecated, but was fun to try out)</li>
<li>IP subnets and routing under Symbolics Namespaces</li>
<li>Setting up the three Symbolics XL computers as a small LAN with a Linux NFS server</li>
</ul>

<p>Later, I hope to cover some more topics, including:</p>

<ul>
<li>Adding MacIvories, NXP and other computers to the LAN</li>
<li>Bridging this Symbolics LAN with others over WAN</li>
</ul>

<p>In turn, I hope to explore and share some of the features of the new (to me) XL1200 with Framethrower that was provided by David Schmidt.</p>

<p>I also hope to show my colleagues at work some of the joys and advantages of the Symbolics model of building software, as compared to our current way of building services (e.g., Java/Spring Boot) and clients (e.g., TypeScript/Vue.js/Stencil).</p>

<p>The LAN currently consists of:</p>

<ul>
<li><code>XENON</code>, XL1201, Chaos 1200 &amp; IP 192.168.5.92</li>
<li><code>COBALT</code>, XL1201, Chaos 1202 &amp; IP 192.168.5.94</li>
<li><code>IRON</code>, XL1200, Chaos 1204 &amp; IP 192.168.5.95</li>
<li><code>IGW</code>, Edgerouter Pro, IP 192.168.5.1/24 and 192.168.1.1/22</li>
<li><code>BORON</code>, Intel NUC &amp; Ubuntu, IP 192.168.1.97</li>
</ul>

<p>The 192.168.5.0/24 segment is separate from the rest of my LAN and solely for vintage computers. No DHCP runs there, and all the broadcast traffic modern computers send out doesn't cross.</p>]]></content:encoded></item><item><title><![CDATA[Symbolics XL LAN Challenges]]></title><description><![CDATA[<p>I recently set up a LAN of my three XL Symbolics machines at home. The XL1201 which was having stability issues has been largely stabilized (thanks to help from David Schmidt). I will post more about this LAN soon, but I thought I would mention an interesting problem.</p>

<p>The machines</p>]]></description><link>https://symbolics.lisp.engineer/symbolics-xl-lan-challenges/</link><guid isPermaLink="false">cd8ca79d-c86f-47b3-8de1-39bc5ede7631</guid><category><![CDATA[xl1201]]></category><category><![CDATA[screenshot]]></category><category><![CDATA[genera]]></category><category><![CDATA[symbolics]]></category><category><![CDATA[crash]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Wed, 05 May 2021 22:26:17 GMT</pubDate><content:encoded><![CDATA[<p>I recently set up a LAN of my three XL Symbolics machines at home. The XL1201 which was having stability issues has been largely stabilized (thanks to help from David Schmidt). I will post more about this LAN soon, but I thought I would mention an interesting problem.</p>

<p>The machines connect to the LAN via an AUI to 10BaseT transceiver, to my core LAN which is a mixed 10G/1G LAN. The core router is a Ubiquiti EdgeRouter Pro which is attached to UNMS, their central management tool. When I connected these machines to the LAN, I was getting Merlin (the name of the CPU board) Ethernet errors on occasion, and eventually the computer would crash. I put the Symbolics computers on a separate segment connected only to a small Netgear switch and the EdgeRouter, but the computers kept crashing.</p>

<p>Eventually I ran a Wireshark on there, and noticed every 5 minutes or so a huge ARP request flood, asking every IP address 8 to 12 times for its MAC. I finally diagnosed this as part of the UNMS discovery protocol to find devices on the network. Once I added my new Symbolics segment to its "do not discover" blacklist, the network has become stable again. I guess feeding 8,000 ARPs into an ancient Ethernet communications chip is not good for stability.</p>

<p>More to come.</p>

<p><img src="https://symbolics.lisp.engineer/static/df/SymbolicsEthernetERROR20210504_153541.jpg" alt="Screenshot with Ethernet Error"></p>]]></content:encoded></item><item><title><![CDATA[Aiband, a Clojure Unity Roguelike]]></title><description><![CDATA[<p>I've decided to participate in <a href="https://itch.io/jam/procjam">ProcJam 2016</a> this year.</p>

<p>For a change of pace, I'm building a small roguelike in Clojure with a Unity3D front-end. This is an interesting challenge as Clojure allows for (even strives for) purity, but doesn't have a well-integrated, easy to use state monad and related</p>]]></description><link>https://symbolics.lisp.engineer/aiband-a-clojure-unity-roguelike/</link><guid isPermaLink="false">fef1d317-f931-4bc4-8c42-f11c7f90aeed</guid><category><![CDATA[clojure]]></category><category><![CDATA[unity3d]]></category><category><![CDATA[procjam]]></category><category><![CDATA[roguelike]]></category><category><![CDATA[aiband]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Wed, 09 Nov 2016 19:30:24 GMT</pubDate><media:content url="https://symbolics.lisp.engineer/content/images/2016/11/Screen-Shot-2016-11-09-at-1-53-26-PM.png" medium="image"/><content:encoded><![CDATA[<img src="https://symbolics.lisp.engineer/content/images/2016/11/Screen-Shot-2016-11-09-at-1-53-26-PM.png" alt="Aiband, a Clojure Unity Roguelike"><p>I've decided to participate in <a href="https://itch.io/jam/procjam">ProcJam 2016</a> this year.</p>

<p>For a change of pace, I'm building a small roguelike in Clojure with a Unity3D front-end. This is an interesting challenge as Clojure allows for (even strives for) purity, but doesn't have a well-integrated, easy to use state monad and related syntax like Haskell, making it hard to use (for example) random numbers purely.</p>

<p>So, I'm making an almost-pure version, with the impurities of the random numbers "allowed," for now. I may explore writing/refactoring my code to allow for the use of Clojure's threading macros.</p>

<p>The source code and more details are <a href="https://github.com/LispEngineer/aiband">available in my GitHub</a> if you want to follow along.</p>]]></content:encoded></item><item><title><![CDATA[CLIM on Genera 8.3 [Updated]]]></title><description><![CDATA[<p>In preparation of doing some actual software engineering on Genera, I decided to take a look at the CLIM implementation on my MacIvory III Genera 8.3.</p>

<p>There are a few steps to do first:</p>

<ul>
<li><code>Load System CLIM</code>: This will take a while. It loads a lot of files and</li></ul>]]></description><link>https://symbolics.lisp.engineer/clim-on-genera-8-3/</link><guid isPermaLink="false">22b95e4a-edaf-4ddf-924a-7c11f2dcc607</guid><category><![CDATA[genera]]></category><category><![CDATA[symbolics]]></category><category><![CDATA[macivory]]></category><category><![CDATA[clim]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Sun, 28 Aug 2016 18:55:07 GMT</pubDate><media:content url="https://symbolics.lisp.engineer/content/images/2016/08/IMG_3458-copy-2.JPG" medium="image"/><content:encoded><![CDATA[<img src="https://symbolics.lisp.engineer/content/images/2016/08/IMG_3458-copy-2.JPG" alt="CLIM on Genera 8.3 [Updated]"><p>In preparation of doing some actual software engineering on Genera, I decided to take a look at the CLIM implementation on my MacIvory III Genera 8.3.</p>

<p>There are a few steps to do first:</p>

<ul>
<li><code>Load System CLIM</code>: This will take a while. It loads a lot of files and several subsystems, including:
<ul><li><code>Loading system CLIM version 66</code></li>
<li><code>Initializing subsystem CLIM Utilities</code></li>
<li><code>Initializing subsystem CLIM Silica</code></li>
<li><code>Initializing subsystem CLIM Standalone</code></li>
<li><code>Initializing system CLIM version 66</code></li>
<li><code>Loading patches for system CLIM version 66</code></li>
<li><code>Patches for CLIM (Current version is 66.3):</code></li></ul></li>
<li>If you attempt to use CLIM at this point, however, it won't work because there is no driver (in my parlance only, I'm not sure the official term). The example code will fail: <code>Error: Cannot find port type: :GENERA</code></li>
<li><code>Load System Genera-CLIM</code> will install the remaining parts</li>
</ul>

<p>This whole process takes probably 15+ minutes of compiling and crunching, so you might want to save the world and restart after this (although I didn't do this yet).</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/08/Screen-Shot-2016-08-28-at-1-25-50-PM.png" alt="CLIM on Genera 8.3 [Updated]">
<img src="https://symbolics.lisp.engineer/content/images/2016/08/Screen-Shot-2016-08-28-at-1-34-18-PM.png" alt="CLIM on Genera 8.3 [Updated]">
<img src="https://symbolics.lisp.engineer/content/images/2016/08/Screen-Shot-2016-08-28-at-1-38-15-PM.png" alt="CLIM on Genera 8.3 [Updated]">
<img src="https://symbolics.lisp.engineer/content/images/2016/08/Screen-Shot-2016-08-28-at-1-38-22-PM.png" alt="CLIM on Genera 8.3 [Updated]">
<img src="https://symbolics.lisp.engineer/content/images/2016/08/Screen-Shot-2016-08-28-at-1-42-27-PM.png" alt="CLIM on Genera 8.3 [Updated]"></p>

<p>Oddly enough, at this point, I figured I'd read the CLIM documentation online in the <code>Document Examiner</code>, but alas, it doesn't seem to have it there even if I ask it to show candidates.</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/08/Screen-Shot-2016-08-28-at-2-13-19-PM.png" alt="CLIM on Genera 8.3 [Updated]"></p>

<p>Anyway, as usual, <a href="http://bitsavers.informatik.uni-stuttgart.de/pdf/symbolics/software/genera_8/Common_Lisp_Interface_Manager__CLIM__Release_2.0.pdf">Bitsavers has the docs</a> so I decided to follow along with the tutorial to run the <code>puzzle-1.lisp</code> example. (Reproduced at the end.)</p>

<p>To back up one step, let me mention how I have my development environment set up. I have the MacIvory III configured in a Mac Quadra 950 running Mac OS 8 with a <a href="http://lowendmac.com/video/thunder2gx.html">SuperMac Thunder II GX</a> running on a Dell 2007FP LCD, but unfortunately only running at 1360x1024 (since I don't have a monitor which can do 1600x1200 at 75Hz on VGA). I couldn't get my second Ethernet card to work (due to a bug in the Genera Ethernet control panel under Mac OS 8) so when Genera is running, the Mac is not on the LAN.</p>

<p>I run Genera, and leave it and the Mac running, but I turn off the monitors and lock the Mac's keyboard/mouse. Then I Telnet into Genera, <code>Start X Screen</code> twice to my iMac, and then <code>Halt Remote Terminal</code> (which ends the Telnet session). In the X screen, I use my <a href="https://github.com/LispEngineer/genera-src/blob/master/x11/xquartz-87-enh.lisp">Tenkeyless Enhanced</a> keyboard layout with my <a href="https://github.com/LispEngineer/genera-src/tree/master/wasd">custom WASD keyboard</a>.</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/08/IMG_3455-1-copy.JPG" alt="CLIM on Genera 8.3 [Updated]"></p>

<p>Back to CLIM. When I first ran the demo:</p>

<pre><code class="language-lisp">(setq fp1 (make-application-frame 'fifteen-puzzle-1
        :left 200 :right 400 :top 150 :bottom 350))
(run-frame-top-level fp1)
</code></pre>

<p>By selecting this and hitting <code>c-sh-E</code> in Zmacs, nothing happened, although Zmacs kept telling me it was executing the CLIM program. I couldn't figure it out. Furthermore, I couldn't get my nicely mapped <code>ABORT</code> button to do anything, nor <code>c-ABORT</code>. (It took me a while to remember to do <code>c-m-ABORT</code> which worked.) Turns out I had to tell System Preferences in the Mac (OS X.11) to unmap <code>^F8</code> from "Move focus to the status menus."</p>

<p>Anyway, I abort and restart the program a few times, both from Zmacs and a Lisp Listener (<code>(clim:run-frame-top-level clim-user::fp1)</code>). Finally I power on the MacIvory screen running Genera and, voila, the puzzle window is running on the console.</p>

<p>Well, needless to say, I may have to not use CLIM to do my Genera development, because I need (well, want) everything to work over an X screen.</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/08/IMG_3458-copy.JPG" alt="CLIM on Genera 8.3 [Updated]"></p>

<h1 id="documentationupdated">Documentation [Updated]</h1>

<p>I searched and found that the CLIM documentation was indeed on my filesystem, at <code>ARGON:&gt;sys&gt;doc&gt;clim&gt;</code>. I tried <code>Read Private Document</code> on the various <code>.sab</code> files, but nothing would show up in <code>Document Examiner.</code></p>

<p>In there was an attractive looking LISP file, <code>clim-doc.lisp</code>, that had lots of interesting references to documentation. So I <code>Load File</code>d it, but no luck.</p>

<p>Then I typed <code>Load System</code> and <code>COMPLETE</code> and, voila, <code>CLIM Documentation</code> showed up as an available system to load. Actually, it showed up twice (not sure why). I loaded it, and boom, I had my documentation.</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/08/Screen-Shot-2016-08-28-at-3-42-43-PM.png" alt="CLIM on Genera 8.3 [Updated]">
<img src="https://symbolics.lisp.engineer/content/images/2016/08/Screen-Shot-2016-08-28-at-3-43-06-PM.png" alt="CLIM on Genera 8.3 [Updated]"></p>

<h1 id="todos">TODOs</h1>

<ul>
<li>Figure out how to get CLIM to run over CLX, which can be loaded using <code>Load System CLX-CLIM</code></li>
</ul>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/08/Screen-Shot-2016-08-28-at-2-41-28-PM.png" alt="CLIM on Genera 8.3 [Updated]"></p>

<h1 id="puzzle1source">Puzzle-1 Source</h1>

<pre><code class="language-lisp">;;; -*- Mode: Lisp; Syntax: ANSI-Common-Lisp; Package: CLIM-USER; Base: 10; Lowercase: Yes -*-
;;;&gt;
;;;&gt; *****************************************************************************************
;;;&gt; ** (c) Copyright 1993 Symbolics, Inc.  All rights reserved.
;;;&gt; ** Portions of font library Copyright (c) 1984 Bitstream, Inc.  All Rights Reserved.
;;;&gt;
;;;&gt;    The software, data, and information contained herein are proprietary 
;;;&gt; to, and comprise valuable trade secrets of, Symbolics, Inc., which intends 
;;;&gt; to keep such software, data, and information confidential and to preserve 
;;;&gt; them as trade secrets.  They are given in confidence by Symbolics pursuant 
;;;&gt; to a written license agreement, and may be used, copied, transmitted, and 
;;;&gt; stored only in accordance with the terms of such license.
;;;&gt; 
;;;&gt; Symbolics, Symbolics 3600, Symbolics 3670 (R), Symbolics 3675 (R), Symbolics
;;;&gt; 3630, Symbolics 3640, Symbolics 3645 (R), Symbolics 3650 (R), Symbolics 3653,
;;;&gt; Symbolics 3620 (R), Symbolics 3610 (R), Symbolics Common Lisp (R),
;;;&gt; Symbolics-Lisp (R), Zetalisp (R), Genera (R), Open Genera, Virtual Lisp Machine,
;;;&gt; VLM, Wheels (R), Dynamic Windows (R), SmartStore (R), Semanticue (R), Frame-Up (R),
;;;&gt; Firewall (R), Document Examiner (R), Delivery Document Examiner, Ivory, MacIvory,
;;;&gt; MacIvory model 1, MacIvory model 2, MacIvory model 3, XL400, XL1200, XL1201,
;;;&gt; Symbolics UX400S, Symbolics UX1200S, NXP1000, Symbolics C, Symbolics Pascal (R),
;;;&gt; Symbolics Prolog, Symbolics Fortran (R), CLOE (R), CLOE Application Generator,
;;;&gt; CLOE Developer, CLOE Runtime, Common Lisp Developer, Symbolics Concordia, Joshua,
;;;&gt; Statice (R), and Minima are trademarks of Symbolics, Inc.
;;;&gt; 
;;;&gt; RESTRICTED RIGHTS LEGEND
;;;&gt;    Use, duplication, and disclosure by the Government are subject to restrictions 
;;;&gt; as set forth in subdivision (c)(1)(ii) of the Rights in Technical Data and Computer 
;;;&gt; Software Clause at DFAR 52.227-7013.
;;;&gt; 
;;;&gt;      Symbolics, Inc.
;;;&gt;      6 Concord Farms
;;;&gt;      555 Virginia Road
;;;&gt;      Concord, Massachusetts 01742-2727
;;;&gt;      United States of America
;;;&gt;      508-287-1000
;;;&gt;
;;;&gt; *****************************************************************************************
;;;&gt;

(define-application-frame fifteen-puzzle-1 ()
    ((pieces :initform (make-array '(4 4) :initial-contents '((1 2 3 4)
                                  (5 6 7 8)
                                  (9 10 11 12)
                                  (13 14 15 0)))))
  (:menu-bar nil)
  (:panes
    (display :application
         :text-style '(:fix :bold :very-large)
         :display-function 'draw-the-display
         :scroll-bars nil)
    (menu :command-menu))
  (:layouts
    (main 
      (vertically () display menu))))

;;; this draws the entire display

(defmethod draw-the-display ((application fifteen-puzzle-1) stream)
  (with-slots (pieces) application
    (dotimes (y 4)
      (dotimes (x 4)
    (let ((piece (aref pieces y x)))
      (if (zerop piece)
          (format stream "   ")
          (format stream "~2D " piece))))
      (terpri stream))))

;;; useful macrology - the body will be run with x and y bound to
;;; the coordinates of the empty cell

(defmacro find-empty-piece-and-do ((y x) &amp;body body)
  `(block find-empty-piece
     (dotimes (,y 4)
       (dotimes (,x 4)
     (when (zerop (aref pieces ,y ,x))
       ,@body
       (return-from find-empty-piece))))))

(define-fifteen-puzzle-1-command (down :menu t) ()
  (with-slots (pieces) *application-frame*
    (find-empty-piece-and-do (y x)
      (if (not (zerop y))
      (rotatef (aref pieces y x) (aref pieces (- y 1) x))))))

(define-fifteen-puzzle-1-command (up :menu t) ()
  (with-slots (pieces) *application-frame*
    (find-empty-piece-and-do (y x)
      (if (not (= y 3))
      (rotatef (aref pieces y x) (aref pieces (+ y 1) x))))))

(define-fifteen-puzzle-1-command (left :menu t) ()
  (with-slots (pieces) *application-frame*
    (find-empty-piece-and-do (y x)
      (if (not (= x 3))
      (rotatef (aref pieces y x) (aref pieces y (+ x 1)))))))

(define-fifteen-puzzle-1-command (right :menu t) ()
  (with-slots (pieces) *application-frame*
    (find-empty-piece-and-do (y x)
      (if (not (zerop x))
      (rotatef (aref pieces y x) (aref pieces y (- x 1)))))))

#||
()
(setq fp1 (make-application-frame 'fifteen-puzzle-1
        :left 200 :right 400 :top 150 :bottom 350))
(run-frame-top-level fp1)
||#
</code></pre>]]></content:encoded></item><item><title><![CDATA[Ivory CPU Heatsink and Instability]]></title><description><![CDATA[<p>One of the theories about the instability of my Symbolics XL1200 is that the CPU has no heatsink and so it is suffering from thermal problems after a while. (15-30-ish minutes)</p>

<p><a href="http://symbolics-dks.com/">David K. Schmidt</a> was kind enough to send me an old heatsink. It's 38x38x5 mm and has 11 fins</p>]]></description><link>https://symbolics.lisp.engineer/ivory-cpu-heatsink-and-instability/</link><guid isPermaLink="false">2a59a999-6d7a-4396-b216-c3e9a4f2955e</guid><category><![CDATA[symbolics]]></category><category><![CDATA[xl1201]]></category><category><![CDATA[repair]]></category><category><![CDATA[heatsink]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Sat, 06 Aug 2016 14:13:58 GMT</pubDate><media:content url="https://symbolics.lisp.engineer/content/images/2016/08/IMG_2172-copy-1.JPG" medium="image"/><content:encoded><![CDATA[<img src="https://symbolics.lisp.engineer/content/images/2016/08/IMG_2172-copy-1.JPG" alt="Ivory CPU Heatsink and Instability"><p>One of the theories about the instability of my Symbolics XL1200 is that the CPU has no heatsink and so it is suffering from thermal problems after a while. (15-30-ish minutes)</p>

<p><a href="http://symbolics-dks.com/">David K. Schmidt</a> was kind enough to send me an old heatsink. It's 38x38x5 mm and has 11 fins on it, as you'll see on the pictures; slightly smaller than the Ivory CPU itself.</p>

<p>First I cleaned the old epoxy from the heatsink using acetone, which was surprisingly easy to do.</p>

<p>After removing the Merlin II card, I cleaned the top of the Ivory CPU and the bottom of the heatsink with a small 70% Isopropol Alcohol medical swab.</p>

<p>I removed the Ivory CPU and cleaned the socket pins with CRC Contact cleaner and brushed on a small amount of Deoxit D5 on the pins of the Ivory CPU.</p>

<p>Using a minimal amount of <a href="http://www.arcticsilver.com/arctic_silver_thermal_adhesive.htm">Arctic Silver Thermal Adhesive</a> on just the golden "chip" part of the top of the Ivory CPU, I then stuck the chip and heatsink together. I then put the top of the Deoxit D5 bottle on top of the heatsink, and then a 3.5" SCSI hard drive on top of it to apply pressure. After an hour, I removed the hard drive and Deoxit cap, and left the whole setup to cure overnight.</p>

<p>In the morning, I cranked up the air conditioner and reinstalled the Merlin II.</p>

<p>Unfortunately, this does not seem to have solved the problem. Using the system for about 23 minutes has now produced some weird errors, including:</p>

<pre><code>--&gt; The scheduler's data structures are locked, using the cold load stream &lt;--

Error: The generic function PROCESS-ACTIVE-P was applied to the argument #&lt;DPT-CALL-INDIRECT-PREFETCH 22005600001&gt;.  
       The argument was not of the correct type.
       The function is implemented by the flavor PROCESS:PROCESS.

(FLAVOR:METHOD TV:SCREEN-GET-WHO-LINE-PROCESS TV:GENERIC-WHO-LINE-SCREEN-MIXIN)
  Arg 0 (SYS:SELF-MAPPING-TABLE): #&lt;Map to flavor TV:GENERIC-WHO-LINE-SCREEN-MIXIN 20012145454&gt;
  Arg1 (SELF): #&lt;WHO-LINE-SCREEN Who Line Screen 20006200000 exposed&gt;
...
</code></pre>

<p>Then, eventually within a few minutes it just gave random errors, like:</p>

<pre><code>Lisp stopped itself  
Error trap 10000006612 not in emulator mode ...  
</code></pre>

<p>So, it appears thermal stress on the Ivory CPU isn't the problem, <em>or</em> that the thermal stress is too great for that small heatsink to keep up with.</p>

<p><em>Sigh.</em></p>

<p>Next step is to clean and reseat all the chips on the I/O board, in a few weeks.</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/08/IMG_2144-copy.JPG" alt="Ivory CPU Heatsink and Instability">
<img src="https://symbolics.lisp.engineer/content/images/2016/08/IMG_2167-copy.JPG" alt="Ivory CPU Heatsink and Instability">
<img src="https://symbolics.lisp.engineer/content/images/2016/08/IMG_2172-copy.JPG" alt="Ivory CPU Heatsink and Instability">
<img src="https://symbolics.lisp.engineer/content/images/2016/08/IMG_2177-copy.JPG" alt="Ivory CPU Heatsink and Instability">
<img src="https://symbolics.lisp.engineer/content/images/2016/08/IMG_2185-copy.JPG" alt="Ivory CPU Heatsink and Instability">
<img src="https://symbolics.lisp.engineer/content/images/2016/08/IMG_2180-copy.JPG" alt="Ivory CPU Heatsink and Instability">
<img src="https://symbolics.lisp.engineer/content/images/2016/08/IMG_2194-copy.JPG" alt="Ivory CPU Heatsink and Instability"></p>]]></content:encoded></item><item><title><![CDATA[Telnet to MacIvory]]></title><description><![CDATA[<p>Just a quick note about how to enable telnet to your MacIvory III running Genera 8.3.</p>

<p>First, <code>Edit Object Site NAME</code> (obviously, use your <code>NAME</code> and not mine) in the <code>Namespace Editor</code> and add your network to the <code>Secure Subnets</code>. For example, for typical home networks you might add</p>]]></description><link>https://symbolics.lisp.engineer/telnet-to-macivory/</link><guid isPermaLink="false">61d54246-01a2-4d59-ae30-0c8e3d9b7caf</guid><category><![CDATA[symbolics]]></category><category><![CDATA[genera]]></category><category><![CDATA[macivory]]></category><category><![CDATA[telnet]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Fri, 29 Jul 2016 04:12:24 GMT</pubDate><content:encoded><![CDATA[<p>Just a quick note about how to enable telnet to your MacIvory III running Genera 8.3.</p>

<p>First, <code>Edit Object Site NAME</code> (obviously, use your <code>NAME</code> and not mine) in the <code>Namespace Editor</code> and add your network to the <code>Secure Subnets</code>. For example, for typical home networks you might add <code>INTERNET 192.168.1.0</code> or your office might be <code>INTERNET 10.0.0.0</code>. Save the object.</p>

<p>If you are logged in, it usually turns remote access off. This can be odd because you can telnet in when you first boot, but not as soon as you start doing anything on the local console. To turn remote access back on even when you're logged in, <code>(neti:remote-login-on)</code> is your command. (See <em>Networks</em> pages 13 and 21.)</p>

<p>Now you're able to <code>telnet</code> to your MacIvory, and then you can <code>Start X Screen</code> or whatever else you want to do.</p>

<pre><code>$ telnet 192.168.1.93
Trying 192.168.1.93...  
Connected to 192.168.1.93.  
Escape character is '^]'.

Symbolics System, FEP0:&gt;Inc-ADMIRAL2-XLib-Xquartz-1.ilod.1 (ADMIRAL2 Namespac!  
e &amp; :xquartz-87-tenkeyless keyboard)  
MacIvory model 3 Processor, 7.9M words Physical memory, 244.1M words Swapping!  
 space.
 Genera  8.3
Admiral2 ARGON

Type c-_ H for Help.  
Type Set Remote Terminal Options to set the terminal type.

Command:  
telnet&gt; Connection closed.  
</code></pre>]]></content:encoded></item><item><title><![CDATA[XL1201 Moment of Truth]]></title><description><![CDATA[<p>UPDATE: No joy. Still self-reboots.</p>

<p>So, I put the Merlin II card back into the XL1201, connected the power and console, and powered it up.</p>

<p>Nothing. Blank screen (which means the monitor was at least getting a signal) but no boot, nothing. I hit the reset button a few times</p>]]></description><link>https://symbolics.lisp.engineer/xl1201-moment-of-truth/</link><guid isPermaLink="false">58d4dae6-e60d-4cf1-98c6-e38e3c199d9e</guid><category><![CDATA[xl1201]]></category><category><![CDATA[symbolics]]></category><category><![CDATA[repair]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Sun, 24 Jul 2016 21:17:33 GMT</pubDate><content:encoded><![CDATA[<p>UPDATE: No joy. Still self-reboots.</p>

<p>So, I put the Merlin II card back into the XL1201, connected the power and console, and powered it up.</p>

<p>Nothing. Blank screen (which means the monitor was at least getting a signal) but no boot, nothing. I hit the reset button a few times and powered it off and on a few times, and tried to reseat the card. Not a thing.</p>

<p>So, removed the Merlin II and took a very close look at it, comparing my before pictures to everything, to make sure every chip was in the right place and every pin was in its slot.</p>

<p>Sure enough, I found exactly two chips inserted incorrectly - backward. Of course, they were the only two "vertical" chips, in locations FF1 and FF4. I removed, reversed and reseated them, and the XL1201 powered on and booted into Genera like a champ.</p>

<p>This was at 5:12PM. If I fixed things, it will still be running at, say, 5:42PM or even overnight. If I didn't, I would expect it to crash or reboot itself sometime between 5:27 and 5:32PM.</p>

<p>I guess we'll see...</p>

<h1 id="waitawhile">Wait a while...</h1>

<p>Well, it self-rebooted at 5:44PM. I guess I will do the same thing on the Merlin I/O board another weekend and we'll see what happens from there.</p>

<h1 id="nextsteps">Next Steps</h1>

<ul>
<li>Remove, clean, reseat all DIPs in the Merlin I/O card</li>
<li>Possibly remove, clean and reseat all PGA, PLCC and other challenging chips</li>
<li>Install a heat sink on Ivory CPU?</li>
</ul>

<p>If those things don't work, then:</p>

<ul>
<li>Replace broken capacitor on Merlin II CPU card</li>
<li>Replace all axial tantalum capacitors on the two boards and the backplane. Perhaps start with the backplane as it's small.</li>
</ul>]]></content:encoded></item><item><title><![CDATA[XL1201 Merlin II Chip Reseating]]></title><description><![CDATA[<p>UPDATE: I clipped and removed the broken capacitor. Replacing it will be the task of another day.</p>

<p>I spent two days removing, cleaning and reseating each DIP chip on the Symbolics XL1201 Merlin II Main (CPU) board. Earlier I <a href="https://symbolics.lisp.engineer/detailed-inspection-of-xl1201-merlin-ii-solder-side/">closely examined the solder side</a> of the board and found a</p>]]></description><link>https://symbolics.lisp.engineer/xl1201-merlin-ii-chip-reseating/</link><guid isPermaLink="false">e3a93f1c-269d-4204-abc5-25d0093ea86d</guid><category><![CDATA[symbolics]]></category><category><![CDATA[xl1201]]></category><category><![CDATA[pcb]]></category><category><![CDATA[repair]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Sun, 24 Jul 2016 19:48:20 GMT</pubDate><media:content url="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1733-copy-2.JPG" medium="image"/><content:encoded><![CDATA[<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1733-copy-2.JPG" alt="XL1201 Merlin II Chip Reseating"><p>UPDATE: I clipped and removed the broken capacitor. Replacing it will be the task of another day.</p>

<p>I spent two days removing, cleaning and reseating each DIP chip on the Symbolics XL1201 Merlin II Main (CPU) board. Earlier I <a href="https://symbolics.lisp.engineer/detailed-inspection-of-xl1201-merlin-ii-solder-side/">closely examined the solder side</a> of the board and found a few minor discrepancies. This time I also encountered three discrepancies:</p>

<ul>
<li>Bent pin on chip BB27 - unbent</li>
<li>Broken bypass cap next to chip GG7 - I clipped this one off entirely and will replace another day</li>
<li>One long bodge wire running along the entire top has come loose. This could get snagged on something and fall off.</li>
</ul>

<p>Additionally, I removed and resocketed the Weitek Floating Point co-processor without doing any cleaning. It looked sparkling clean.</p>

<p>While I was at it, I removed the metal gunk in the spare hole of BB12.</p>

<p>Finally, I examined the component-side of the bad-looking solder joint between CC25-26/DD25-26. It seems this was likely caused by the soldering of a bodge wire to this connection, on a resistor pack/network.</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/Photo-on-7-24-16-at-3-28-PM--2.jpg" alt="XL1201 Merlin II Chip Reseating"></p>

<p>Note that I did not remove the two other PGA chips on the board. One of them is almost certainly the Ivory. They are:</p>

<ul>
<li><code>VTC VIC068PGF4 9050 985 VIC ES</code>: Probably the VMEBus controller chip.</li>
<li><code>110730 USA 1XC9-0401 9051</code>: Probably the Ivory CPU, right in the center of the board.</li>
</ul>

<h1 id="discrepanciesdetailed">Discrepancies Detailed</h1>

<p>I found a broken capacitor between chip FF7 and GG7. Top label says "A5E104Z". <a href="https://octopart.com/search?q=A5E104Z">Octopart</a> shows a few places to get it, two of which seem to think it's a 0.1 uF 50V cap. One says "A5E104Z ARCO .1MFD-50VDC" and the other says "CAP CER DIP .1UF 50V 80-20% 7.5LS BULK". It's about 6.25mm wide, 2.5mm tall and the top is about 4mm off the circuit board. GG7 is a 74F00N which is a <a href="http://www.nxp.com/documents/data_sheet/74F00.pdf">Quad 2-input NAND</a> chip. It likely is a bypass capacitor for this chip, as almost every single chip has one immediately to its left.</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/Photo-on-7-24-16-at-12-43-PM--2.jpg" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Photo-on-7-24-16-at-12-40-PM--2.jpg" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Photo-on-7-24-16-at-12-44-PM.jpg" alt="XL1201 Merlin II Chip Reseating"></p>

<p>After moving the capacitor around, it was clearly broken all the way across.</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/Photo-on-7-24-16-at-3-29-PM.jpg" alt="XL1201 Merlin II Chip Reseating"></p>

<p>Additionally, I found one bent pin on chip BB27, which also is the only chip with an unusual label, "985-DS/N 582." I believe that this is the chip that contains the serial number, as the board has a sticker saying "S/N 582" as well as "582" hand-scratched into the board. The corresponding socket hole was also slightly marred. I very carefully unbent it and reinstalled it.</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/Photo-on-7-23-16-at-5-03-PM.jpg" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Photo-on-7-23-16-at-5-04-PM.jpg" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1737-copy.JPG" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1735-copy.JPG" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1733-copy.JPG" alt="XL1201 Merlin II Chip Reseating"></p>

<p>After-repair:</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1742-copy-2.JPG" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1749-copy.JPG" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1744-copy-2.JPG" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1752-copy-2.JPG" alt="XL1201 Merlin II Chip Reseating"></p>

<p>Finally, there are two places with no chip installed into a socket. One iS JJ30 silkscreened "WRPOST" and the other is KK30, silkscreened "AUX-TIMER". There are numerous jumper posts nearby which may enable these, though for what purpose I don't know. There are a total of about eight jumper blocks scattered around the board.</p>

<h1 id="procedure">Procedure</h1>

<ul>
<li>Photograph board with sufficient detail to ensure all chips can be replaced correctly</li>
<li>Remove each DIP chip, using <a href="https://www.amazon.com/gp/product/B00433SJB2/">Wiha Chip Lifter</a></li>
<li>Write down the chip location, the silkscreen written under the chip, and the label on the chip (if any)</li>
<li>Spray some <a href="https://www.amazon.com/gp/product/B00006LVEU">Deoxit D5</a> onto a Q-tip and wipe the chip's pins clean and set aside to dry</li>
<li>Spray some <a href="https://www.amazon.com/gp/product/B000BXKZVA">contact cleaner</a> into the chip socket, and agitate a bit with a toothbrush</li>
<li>Air-can dry the socket and, if necessary, the chip</li>
<li>Reinsert chip</li>
<li>Verify chip reinserted properly
<ul><li>Correct location</li>
<li>Correct orientation</li>
<li>All pins in their holes correctly</li></ul></li>
</ul>

<p>I replaced the Q-tip every 3-6 chips as it would become gray after a short time.</p>

<h1 id="chipsreseated">Chips Reseated</h1>

<ul>
<li>Position: Silkscreen: Chip Label</li>
<li>AA11: BC-BNK-BUS: 115932-A</li>
<li>AA12: BC-RFL-ADD: 115914-A</li>
<li>AA13: BC-OPER-GEN: 115915-A</li>
<li>AA16: BC-LCLK-G_N: 115958-A</li>
<li>AA18: (forgot to write down)</li>
<li>AA22: ID IMBU CT(R?)L: 115921-A</li>
<li>AA27: ID-DE-GATING: 115962-A</li>
<li>AA28: ID-STR-CTRL: 115963-A</li>
<li>BB11: BC-ADDR-PIPE: 115942-A (engraved)</li>
<li>BB17: BC-QUE-0: 115931-A</li>
<li>BB18: BC-QUE-1: 115930-A</li>
<li>BB19: BC-QUE-2: 115929-A</li>
<li>BB20: BC-QUE-CONT: 115928-A</li>
<li>BB21: BC-QUE-RFL: 115927-A</li>
<li>BB22: ID-INTERRUPT: 115920-A</li>
<li>BB24: CY7C291: 115982-D
<ul><li>BB24-28 are a different type of chip than all the rest, in a different package. Looks sort of like a KitKat, and harder to get back into the socket. See pictures.</li></ul></li>
<li>BB25: CY7C291: 115983-D</li>
<li>BB26: (forgot to write down)</li>
<li>BB27: CY7C291: 985-DS/N 582
<ul><li>This chip had its bottom right-most pin bent in and hence was probably not making solid contact.</li>
<li>I unbent the pin and reinserted into the socket. See pictures.</li></ul></li>
<li>BB28: CY7C291: 115986-D</li>
<li>BB30: ID-RESET: 115956-A</li>
<li>CC11: TC 5328 (no label)</li>
<li>CC12: TC 55328 (no label)</li>
<li>CC13: BD-RD-PIPE: 115935-A (engraved)</li>
<li>CC14: BC-DATA-SCH: 115941-A (engraved)</li>
<li>CC15: BC-WR-PIPE: 115957-A</li>
<li>CC16: BC-DATA-MON: 115937-A (engraved)</li>
<li>CC31: ID-ALATCH: 115964-A</li>
<li>DD7: MEM-WR-CTL: 115971-A</li>
<li>DD8: BANK-STATE: 115975-A</li>
<li>DD9: MEM-WR-CTL: 115971-A</li>
<li>DD10: MEM-RD-CTL:  115972-A</li>
<li>DD12: CACHE-STBS: 115951-A</li>
<li>DD13: TC55328 (no label)</li>
<li>DD14: TC55328 (no label)</li>
<li>DD16: BC-REQ-DEC: 115965-A (engraved)</li>
<li>DD18: BC-ADDR-CONT: 115944-A (engraved)</li>
<li>DD19: BC-QUE01-RDY: 115949-A (engraved)</li>
<li>DD20: BC-RD-ACK: 115961-C (engraved)</li>
<li>DD21: BC-2-RFL-RDY: 115948-A (engraved)</li>
<li>DD22: BC-ACK-GEN: 115947-A (engraved)</li>
<li>DD29: IM-DRIVE: 115955-B
<ul><li>Three separate bodge wires go to various pins of this chip's socket.</li></ul></li>
<li>EE16: CACHE-REFILL: 115946-A (engraved)</li>
<li>EE18: CACHE-CNTRL: 115945-A (engraved)</li>
<li>EE19: CACHE-REQ: 115926-A</li>
<li>EE22: MII-TIMEOUT: 115968-A</li>
<li>EE24: SHUFFLE: 115939-B</li>
<li>EE25: SHUFFLE: 115987-A</li>
<li>EE26: SHUFFLE: 115987-A</li>
<li>EE27: SHUFFLE: 115939-B</li>
<li>EE28: REQ-DECODE: 115966-A</li>
<li>EE29: V-REQ-ACK: 115992-A</li>
<li>FF1: MEM-STB: 115976-A (vertical)</li>
<li>FF4: MEM-STB: 115976-A (vertical)</li>
<li>FF7: MEM-ACK-BUF: 115973-B</li>
<li>FF8: MEM-REQ-CNT: 115970-A</li>
<li>FF9: MEM-RD-CTL: 115972-A</li>
<li>GG10: MEM-REQ-STATE: 115980-A</li>
<li>GG11: MEM-REQ-CTL: 115979-A</li>
<li>FF13: FPA-CLOCK: 115950-A (engraved)</li>
<li>FF22: IB-REQ-ACKED: 115953-A (engraved)</li>
<li>FF23: IB-CNTRL: 115960-A</li>
<li>FF24: POLLED-CNTRL: 115991-A</li>
<li>FF25: PLD-DECODE: 115943-A</li>
<li>FF27: V-ARBITOR: 115933-D (very faint)</li>
<li>FF28: ILB-CNTRL: 115934-C</li>
<li>FF29: SHUFFLE: 115987-A</li>
<li>FF30: SHUFFLE: 115939-B</li>
<li>GG15: IDT6178S: (no label)</li>
<li>GG16: IDT6178S: (no label)</li>
<li>GG17: IDT6178S: (no label)</li>
<li>GG18: IDT6178S: (no label)</li>
<li>GG19: IB-DECODE: 115952-A (engraved)</li>
<li>GG21: MII-REFRESH: 115969-A</li>
<li>GG23: REQ-DECODE: 115954-A</li>
<li>GG31: SHUFFLE: 115939-B</li>
<li>HH15: DT6178S: (no label)</li>
<li>HH16: DT6178S: (no label) </li>
<li>HH17: DT6178S: (no label)</li>
<li>HH18: DT6178S: (no label)</li>
<li>HH25: MEM-LTRL: 115950-A (engraved)</li>
<li>HH31: SHUFFLE: 115987-A</li>
<li>JJ15: MII-FP0-WR: 115916-B</li>
<li>JJ23: TRIGGER: 115924-B</li>
<li>JJ24: PARITY: 115925-A</li>
<li>JJ25: QUINT-MUX: 115981-A</li>
<li>JJ26: QUINT-MUX: 115981-A</li>
<li>JJ28: VME-DECODE: 115923-D</li>
<li>JJ30: WRPOST (no chip installed)</li>
<li>KK11: MII-FP0-RD: 115917-B</li>
<li>KK12: MII-TAG-CNTR: 115919-B</li>
<li>KK13: MII-FP1: 115918-B</li>
<li>KK14: MII-FPA-MISC: 115938-A (engraved)</li>
<li>KK31: AUX-TIMER (no chip installed)</li>
<li>Weitek FPA: Removed, inspected &amp; reinserted only (not cleaned)</li>
</ul>

<h1 id="additionalpictures">Additional Pictures</h1>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1704.JPG" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1776-copy.JPG" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1778-copy.JPG" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1775-copy.JPG" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1696.JPG" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1697.JPG" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1698.JPG" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1699.JPG" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1701.JPG" alt="XL1201 Merlin II Chip Reseating">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1700.JPG" alt="XL1201 Merlin II Chip Reseating"></p>]]></content:encoded></item><item><title><![CDATA[Detailed Inspection of XL1201 Merlin II Solder Side]]></title><description><![CDATA[<p>To see if I can isolate the cause of the XL1201 instability, I am going to physically inspect the two main cards with a loupe and flashlight. If I see anything suspect, I'll take a picture with a (cheap) USB microscope.</p>

<p>I am doing a detailed inspection of the solder</p>]]></description><link>https://symbolics.lisp.engineer/detailed-inspection-of-xl1201-merlin-ii-solder-side/</link><guid isPermaLink="false">97abf809-6359-4af6-834e-287f378a86f7</guid><category><![CDATA[symbolics]]></category><category><![CDATA[xl1201]]></category><category><![CDATA[pcb]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Sat, 23 Jul 2016 19:18:35 GMT</pubDate><media:content url="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1686-copy.JPG" medium="image"/><content:encoded><![CDATA[<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1686-copy.JPG" alt="Detailed Inspection of XL1201 Merlin II Solder Side"><p>To see if I can isolate the cause of the XL1201 instability, I am going to physically inspect the two main cards with a loupe and flashlight. If I see anything suspect, I'll take a picture with a (cheap) USB microscope.</p>

<p>I am doing a detailed inspection of the solder side of the Merlin II CPU card first.</p>

<p>Overview picture:</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1678-copy.JPG" alt="Detailed Inspection of XL1201 Merlin II Solder Side"></p>

<h1 id="discrepancies">Discrepancies</h1>

<p>There are only two that are concerning to me, but several others were found. The two of most concern are:</p>

<ul>
<li>Seemingly bad solder joint or problematic solder joint</li>
<li>Material in a empty socket hole - could it make shorts between the layers? Irrelevant?</li>
</ul>

<p>Material in a hole of empty socket BB12</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1679-copy.JPG" alt="Detailed Inspection of XL1201 Merlin II Solder Side">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1683-copy.JPG" alt="Detailed Inspection of XL1201 Merlin II Solder Side">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Photo-on-7-23-16-at-1-44-PM.jpg" alt="Detailed Inspection of XL1201 Merlin II Solder Side"></p>

<p>Bad-looking solder joint between CC25-26, DD-25-26</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/Photo-on-7-23-16-at-1-51-PM.jpg" alt="Detailed Inspection of XL1201 Merlin II Solder Side">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Photo-on-7-23-16-at-1-52-PM.jpg" alt="Detailed Inspection of XL1201 Merlin II Solder Side"></p>

<p>Black blemish near CD23</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/Photo-on-7-23-16-at-1-58-PM.jpg" alt="Detailed Inspection of XL1201 Merlin II Solder Side">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Photo-on-7-23-16-at-1-58-PM--2.jpg" alt="Detailed Inspection of XL1201 Merlin II Solder Side"></p>

<p>Poorly cut lead near EE25 but seems fine</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-23-at-2-49-26-PM.png" alt="Detailed Inspection of XL1201 Merlin II Solder Side"></p>

<p>FF11 - Slightly discolored joint</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-23-at-2-50-56-PM.png" alt="Detailed Inspection of XL1201 Merlin II Solder Side">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-23-at-2-51-16-PM.png" alt="Detailed Inspection of XL1201 Merlin II Solder Side"></p>

<p>FF30 - Black stuff near solder joint, seems to be just a bit of fabric?</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-23-at-2-51-53-PM.png" alt="Detailed Inspection of XL1201 Merlin II Solder Side"></p>]]></content:encoded></item><item><title><![CDATA[Enhanced X11 Keyboard]]></title><description><![CDATA[<p>Well, after living with the default keyboard mapping for Genera under X-Windows, I decided to make an optimized one for an 87-key ANSI layout. The design goals were:</p>

<ul>
<li>Utilize all the 16 top row keys efficiently, with most common functions in logical places</li>
<li>Utilize the 6-key quadrant for other common</li></ul>]]></description><link>https://symbolics.lisp.engineer/enhanced-x11-keyboard/</link><guid isPermaLink="false">afc32d3e-8c45-4cd2-9bee-82533d816da3</guid><category><![CDATA[symbolics]]></category><category><![CDATA[genera]]></category><category><![CDATA[keyboard]]></category><category><![CDATA[x11]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Wed, 20 Jul 2016 04:15:00 GMT</pubDate><media:content url="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-20-at-9-36-38-AM.png" medium="image"/><content:encoded><![CDATA[<img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-20-at-9-36-38-AM.png" alt="Enhanced X11 Keyboard"><p>Well, after living with the default keyboard mapping for Genera under X-Windows, I decided to make an optimized one for an 87-key ANSI layout. The design goals were:</p>

<ul>
<li>Utilize all the 16 top row keys efficiently, with most common functions in logical places</li>
<li>Utilize the 6-key quadrant for other common functions</li>
<li>Leave the arrow keys for cursor motion (because even though I have been using Emacs for at least 26 years I like my arrow keys)</li>
</ul>

<p>Some of the important things that these led me to were:</p>

<ul>
<li>The <code>esc</code> key is now Genera <code>SELECT</code>, as that is one of the most commonly used key somewhat analoguous to <code>Command-TAB</code> in macOS.</li>
<li>The <code>line</code> key is nice to have available for use in Zmacs to start a new line and auto-indent, so put that somewhere reasonably close. In fact, I thought about putting it where the backslash</li>
<li>Genera <code>Backspace</code> is not very useful (equivalent to <code>c-B</code>) so it gets demoted to a middle area and could even be entirely removed</li>
</ul>

<p>Some of the challenges were:</p>

<ul>
<li>Modifier keys in the bottom and second to bottom row are too few. I put the most common ones on the left side (<code>CONTROL</code>, <code>SUPER</code>, <code>META</code>) and the less common ones on the right side along with the two more common ones (<code>META</code>, <code>CONTROL</code>, <code>SYMBOL</code>, <code>HYPER</code>). Just in case someone doesn't have a Menu/Application key, I also mapped <code>SYMBOL</code> to <code>F5</code>, but didn't put a keycap on it. I had an "extra key" and wasn't sure what to put there, and this seemed the most useful thing.
<ul><li>The <code>SYMBOL</code> key (Menu/Application key) probably needs to be marked as a modifier in Xquartz. Right now it autorepeats, which is very annoying. I haven't tried fixing the problem though, since the key is so rarely used. (Mostly for ≣ and ⇄ (or is it ⇆).)</li></ul></li>
<li><code>SUSPEND</code>, <code>RESUME</code>, <code>ABORT</code> seem like they might be more safely put in <code>F13</code>, <code>F14</code>, and <code>F15</code> to prevent accidental keypresses. On the other hand, they're used so often during software development that they're easier to reach in the middle. So, they went into the middle and the shape keys into the upper right.</li>
<li><code>CAPS LOCK</code> and <code>MODE LOCK</code> don't seem to do much useful at all. Indeed, on my Mac I generally map <code>CAPS LOCK</code> to "noop" wasting a completely useful key. The Symbolics 3600 keyboard puts a backspace there. I tried that, but the big problem is that Xquartz or macOS always captures the <code>CAPS LOCK</code> to toggle caps lock, regardless of how you map the key in Xquartz or Genera.
<ul><li>One solution would be to remap the <code>CAPS LOCK</code> key to something else like <code>F16</code> using something like <a href="https://pqrs.org/osx/karabiner/">Karabiner</a> or <code>System Preferences</code>. The former works great but has to be installed everywhere. The latter only lets you map it to pre-existing modifiers. If it were mapped to <code>CONTROL</code> (or whatever), then we could put a <code>HYPER</code> on the left. But, <code>HYPER</code> just isn't used much, so... Whatever.</li></ul></li>
<li><code>LOCAL</code> seems to serve no purpose on MacIvory or on X11, so it's omitted. Same with <code>REPEAT</code>, although it is an interesting key for people without auto-repeat.</li>
<li><code>COMPLETE</code> is used frequently, but so is <code>CLEAR INPUT</code> (at least by me), so I wasn't sure which one belonged in the easily reached <code>F12</code>.</li>
<li><code>HELP</code> is also used frequently. It was a challenge to decide if it should stay in the <code>F12</code> spot or in the (previously) Mac standard spot.</li>
<li>GitHub doesn't work well with the character encoding of Genera. It considers those <code>.lisp</code> files with Genera characters (like ≣ and ⇄) to be binary and won't show them in listings.
<ul><li>I should really write an <code>iconv</code> plugin that will translate Unicode formats to the Genera format.</li>
<li>Another minor detail is that many Mac fonts seem to show the <a href="https://en.wikipedia.org/wiki/Triple_bar">≣ character</a> with four horizontal lines instead of three. There are also two similar Unicode code points for this sort of a character. (≡ and ≣)</li></ul></li>
</ul>

<p>So, with all that said, let me share the layout: (<a href="http://www.keyboard-layout-editor.com/#/gists/cd74f5906d3b62298d3169b808dd7ad0">Keyboard-Layout-Editor link</a>)</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/keyboard-layout.png" alt="Enhanced X11 Keyboard"></p>

<p>Additionally, I made a WASD Keyboards custom layout file (which the original is an <a href="https://inkscape.org/">Inkscape</a> SVG file, <a href="https://github.com/LispEngineer/genera-src/tree/master/wasd">sources located here</a>):</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-20-at-9-28-02-AM.png" alt="Enhanced X11 Keyboard"></p>

<p>Finally, of course, there is <a href="https://github.com/LispEngineer/genera-src/blob/master/x11/xquartz-87-enh.lisp"><code>xquartz-87-enh.lisp</code></a> <br>
in my <a href="https://github.com/LispEngineer/genera-src/tree/master/x11">GitHub Genera X11 Repository</a>. The X11 Repo <code>README.md</code> file has installation instructions.</p>

<p>When I get the custom keyboard from WASD, I'll post pictures here.</p>

<p>I welcome thoughts and feedback on this layout.</p>

<h1 id="generaview">Genera View</h1>

<p>Here is how this keyboard looks in Genera.</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-5-54-59-PM.png" alt="Enhanced X11 Keyboard">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-5-56-27-PM.png" alt="Enhanced X11 Keyboard">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-5-56-35-PM.png" alt="Enhanced X11 Keyboard">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-5-56-58-PM.png" alt="Enhanced X11 Keyboard"></p>

<h1 id="nextsteps">Next Steps</h1>

<p>I'm going to try to make a version of this layout for these keyboards that I also regularly use:</p>

<ul>
<li>MacBook Air/Pro laptop keyboard</li>
<li>Microsoft Sculpt keyboard</li>
</ul>

<p>I also have a USB Sun Type 3 keyboard that I may try to create an X mapping for, and a Sparcstation 20 with a Sun Type 5 keyboard. Finally, I may try to make a similar mapping for Linux.</p>]]></content:encoded></item><item><title><![CDATA[Reloading Translations Files]]></title><description><![CDATA[<p>Just a brief hint...</p>

<p>After you modify the file that has your translations (e.g., <code>sys.translations</code>), to make the new changes active, call <code>(load-patches)</code>. Per <em>Site Operations</em> guide, page 514, section <strong>Translations Files</strong>.</p>]]></description><link>https://symbolics.lisp.engineer/reloading-translations-files/</link><guid isPermaLink="false">df31337b-8a88-4e98-a741-6ce45fb43cb4</guid><category><![CDATA[genera]]></category><category><![CDATA[symbolics]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Mon, 18 Jul 2016 00:47:27 GMT</pubDate><content:encoded><![CDATA[<p>Just a brief hint...</p>

<p>After you modify the file that has your translations (e.g., <code>sys.translations</code>), to make the new changes active, call <code>(load-patches)</code>. Per <em>Site Operations</em> guide, page 514, section <strong>Translations Files</strong>.</p>]]></content:encoded></item><item><title><![CDATA[Genera Xquartz Keyboard]]></title><description><![CDATA[<p>It has taken some effort, but I finally created a reasonable (and close-to-default) keyboard layout and mapping for Genera for using a modern, 87-key "tenkeyless" keyboard under Xquartz. I became reasonably familiar (at a reading level) with Flavors and Genera's X implementation while reverse engineering all this stuff. I also</p>]]></description><link>https://symbolics.lisp.engineer/genera-xquartz-keyboard/</link><guid isPermaLink="false">dfd69d5f-aafa-486f-84cc-5806cba02ed2</guid><category><![CDATA[symbolics]]></category><category><![CDATA[macivory]]></category><category><![CDATA[x11]]></category><category><![CDATA[screenshot]]></category><category><![CDATA[keyboard]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Sun, 17 Jul 2016 19:42:01 GMT</pubDate><media:content url="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-2-53-19-PM-copy.png" medium="image"/><content:encoded><![CDATA[<img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-2-53-19-PM-copy.png" alt="Genera Xquartz Keyboard"><p>It has taken some effort, but I finally created a reasonable (and close-to-default) keyboard layout and mapping for Genera for using a modern, 87-key "tenkeyless" keyboard under Xquartz. I became reasonably familiar (at a reading level) with Flavors and Genera's X implementation while reverse engineering all this stuff. I also used the <code>apropos</code> function a lot, of course.</p>

<p>This layout stays very close to the default one provided by Genera while adding a few tweaks such as:</p>

<ul>
<li>Improved modifier mappings</li>
<li>Calling <code>RUBOUT</code> for <code>Backspace/Delete</code></li>
<li>Ability to use the <code>Keyboard Control</code> activity to further remap things visually</li>
</ul>

<p>I also created a <a href="https://github.com/LispEngineer/genera-src/blob/master/x11/xlib-patch.lisp">patch file</a> that will fix an X-Windows bug in Genera with a modern X server when it tries to set the modifier mappings. This will show up in the Genera herald so you know it's there.</p>

<p>The keyboard layout is called <code>:xquartz-87-tenkeyless</code> and nicely printed as <code>Xquartz 87-key Tenkeyless</code>. A <a href="http://www.keyboard-layout-editor.com/#/gists/1bdd2184b15cfed700133f1aeba23f1c">keyboard reference</a> is available.</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/keyboard-layout--5-.png" alt="Genera Xquartz Keyboard"></p>

<p>Xquartz must be configured with these three checkboxes set: (others are at your discretion)</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-3-03-50-PM.png" alt="Genera Xquartz Keyboard">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-3-03-53-PM.png" alt="Genera Xquartz Keyboard"></p>

<p>You need to allow remote connections, so be sure to do something like <code>xhost +</code> in your <code>xterm</code> window.</p>

<p>Furthermore, you should put the Genera fonts into your X11 font path <a href="https://symbolics.lisp.engineer/genera-x11-fonts-on-mac/">as described here</a> or things will look "wrong" and be less enjoyable.</p>

<p>One note: There seems to be only 6-key rollover when using the <code>Key Test</code> feature of <code>Keyboard Control</code>. I'm not sure if this is an Xquartz limitation or Genera limitation, or something else. Regardless, it's sufficient for our needs. (<code>Shift-hyper-meta-super-control-X</code> anyone? Can't add <code>symbol</code> in there... <pout>)</pout></p>

<h1 id="use">Use</h1>

<p>To use the keyboard layout in Genera:</p>

<ul>
<li>Download the <a href="https://github.com/LispEngineer/genera-src/blob/master/x11/xlib-patch.lisp">XLib patch file</a> and <a href="https://github.com/LispEngineer/genera-src/blob/master/x11/xquartz-87.lisp">Keyboard Mapping file</a> from <a href="https://github.com/LispEngineer/genera-src/tree/master/x11">my GitHub repo</a>
<ul><li>Warning: these contain non-ASCII/Unicode characters in them (Genera symbol characters)</li></ul></li>
<li><code>Load File xlib-patch.lisp</code></li>
<li><code>Load File xquartz-87.lisp</code></li>
<li><code>Save World ...</code> and update your boot file</li>
<li>Restart Genera</li>
<li>Start your Xquartz Server and configure as above</li>
<li><code>Start X Screen INTERNET|10.10.10.10 ...</code> on your host IP or hostname (if configured in your <code>Namespace</code>)</li>
<li><code>Show X Keyboard Mapping</code> will confirm that this mapping is in use by saying <code>The keyboard layout type is :XQUARTZ-87-TENKEYLESS.</code>
<ul><li>If not, see below</li></ul></li>
<li><code>Show Keyboard Layout</code> will show details on the layout</li>
<li><code>Select Activity Keyboard Control</code> will let you remap things further to your hearts content, then put on the kill ring the modifications for your <code>lismp-init.lisp</code> file.</li>
</ul>

<p>If your keyboard isn't working, it's probably because Genera couldn't match it. One thing to try is this:</p>

<pre><code>Command: sys:*consoles*  
(#&lt;X-SCREEN::X-CONSOLE NEON:0.0 0 (Genera on ARGON) 140001042&gt; #&lt;MTB:MAC-RPC-MAIN-CONSOLE 140005535&gt;)
Command: (xlib:display-vendor (x-screen::x-console-display (car sys:*consoles*)))  
"The X.Org Foundation"
11803000  
Command:  
</code></pre>

<p>Then, edit the <a href="https://github.com/LispEngineer/genera-src/blob/master/x11/xquartz-87.lisp"><code>xquartz-87.lisp</code></a> file to match, in the signature:</p>

<pre><code class="language-lisp">(x-screen:define-keyboard-signature :xquartz-87-tenkeyless
  (:keycode-offset 8
   :vendor-name "The X.Org Foundation"
   :vendor-version 11803000)
</code></pre>

<p>After that, check the keys against the output of your <code>xmodmap -pk</code> to make sure they match. If not, you'll have to edit almost everything else. (<code>xmodmap</code> will start with <code>...KeyCodes range from 8 to...</code> - that's where the <code>:keycode-offset</code> comes from.)</p>

<h2 id="forcingthekeyboardmappingtobeused">Forcing the Keyboard Mapping to Be Used</h2>

<p>UPDATE: I cobbled together the <code>Set X Keyboard Mapping</code> for Genera 8.3 from a few pieces I found on the Internet. Load <a href="https://github.com/LispEngineer/genera-src/blob/master/x11/set-x-kb-map.lisp"><code>set-x-kb-map.lisp</code></a> into your world (save it if you want the command permanently) and then you can say <code>Set X Keyboard Mapping [screen] Xquartz-87-Tenkeyless</code> and it will load this mapping.</p>

<h2 id="noteaboutf14andf15">Note about F14 and F15</h2>

<p>F14 and F15 are usually set to lower and raise brightness on the Mac. Disable this in System Preferences -> Keyboard -> Shortcuts -> Display</p>

<h1 id="nextsteps">Next Steps</h1>

<p>I'm going to make an improved layout that better utilizes the keys and puts the most frequently accessed ones closer to the home key. Having <code>SELECT</code> on the <code>esc</code> key is also nice (and familiar from using the MacIvory on the console). I'll share that here later.</p>

<h1 id="pictures">Pictures</h1>

<p>Here are some screenshots of the keyboard in use on my iMac from the MacIvory III.</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-2-28-26-PM.png" alt="Genera Xquartz Keyboard">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-2-53-19-PM.png" alt="Genera Xquartz Keyboard">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-2-53-25-PM.png" alt="Genera Xquartz Keyboard">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-2-54-27-PM.png" alt="Genera Xquartz Keyboard">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-2-57-21-PM.png" alt="Genera Xquartz Keyboard">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-3-37-34-PM.png" alt="Genera Xquartz Keyboard">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-2-57-37-PM.png" alt="Genera Xquartz Keyboard">
<img src="https://symbolics.lisp.engineer/content/images/2016/07/Screen-Shot-2016-07-17-at-4-18-27-PM.png" alt="Genera Xquartz Keyboard"></p>]]></content:encoded></item><item><title><![CDATA[XL1201 Stability Update]]></title><description><![CDATA[<p>In an effort to rule out the power supply causing the XL1201's instability, I sent it out for overhaul by <a href="http://www.powerclinicinc.com/">Power Clinic</a>. After reinstalling it, I booted the XL1201 and just let it sit in the <code>Document Examiner</code>.</p>

<p>Unfortunately, the computer decided to reboot itself after about 15-16 minutes. So,</p>]]></description><link>https://symbolics.lisp.engineer/xl1201-stability-update/</link><guid isPermaLink="false">aa88d2ed-2f1c-4c30-8e4b-3a1818afaa8a</guid><category><![CDATA[symbolics]]></category><category><![CDATA[xl1201]]></category><category><![CDATA[power]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Sat, 16 Jul 2016 15:47:51 GMT</pubDate><media:content url="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1476-copy.JPG" medium="image"/><content:encoded><![CDATA[<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1476-copy.JPG" alt="XL1201 Stability Update"><p>In an effort to rule out the power supply causing the XL1201's instability, I sent it out for overhaul by <a href="http://www.powerclinicinc.com/">Power Clinic</a>. After reinstalling it, I booted the XL1201 and just let it sit in the <code>Document Examiner</code>.</p>

<p>Unfortunately, the computer decided to reboot itself after about 15-16 minutes. So, the power supply would seem not to be the problem.</p>

<p>I will have to disassemble the XL1201 and give it a thorough examination to see if there are any obvious physical defects. If none are found, I will try to remove, clean, and reseat all socketed chips, and see if that helps.</p>

<p>I still have a feeling that the capacitors on the backplane and/or the two boards could be the problem, but at this point I just don't know. It worked fine for several weeks (including one or two days of overnight runs) before becoming unstable.</p>

<p>Power supply before picture:</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1388-copy-1.JPG" alt="XL1201 Stability Update"></p>

<p>Power supply after overhaul picture:</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1472-copy.JPG" alt="XL1201 Stability Update"></p>]]></content:encoded></item><item><title><![CDATA[MacIvory III Transplant]]></title><description><![CDATA[<p>Space is a premium in my little vintage computing paradise, so I had the bright idea of transplanting my MacIvory III from a desktop Quadra 650 to a tower Quadra 950 and clear some desktop space. <a href="http://symbolics-dks.com">David K. Schmidt</a> said this was a simple matter, and he was entirely correct.</p>]]></description><link>https://symbolics.lisp.engineer/macivory-iii-transplant/</link><guid isPermaLink="false">65435a76-48c0-44ec-a76e-c61c04f1a34a</guid><category><![CDATA[symbolics]]></category><category><![CDATA[macivory]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Thu, 14 Jul 2016 03:57:38 GMT</pubDate><media:content url="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1444.JPG" medium="image"/><content:encoded><![CDATA[<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1444.JPG" alt="MacIvory III Transplant"><p>Space is a premium in my little vintage computing paradise, so I had the bright idea of transplanting my MacIvory III from a desktop Quadra 650 to a tower Quadra 950 and clear some desktop space. <a href="http://symbolics-dks.com">David K. Schmidt</a> said this was a simple matter, and he was entirely correct. I effectively put the Quadra 650 hard drive and the MacIvory card into the 950, rebooted, and blam, it "just worked." (I actually put a clone of the Quadra 650 drive from 3 years ago in to test first.)</p>

<p>The Quadra 950 takes a long time to start up due to 256MB of RAM, and its fan is louder than the 650. However, it also has two Apple Ethernet devices on it (one with AAUI, one with Twisted Pair). This should be a good thing, but it turns out it isn't.</p>

<p>At boot time, you get a warning to select the Ethernet device for Genera to use. Unfortunately, as it turns out, there's a bug with the "MacIvory Control Panel" app and Mac OS 8. Apparently one work around for this is to boot into Mac OS 7, configure Ethernet through that control panel, and then boot back into Mac OS 8 and the MacIvory software will remember the setting. I don't have a way to do that that I know of, but I believe Apple distributes Mac OS 7 on their site for free.</p>

<p>I wonder where MacIvory software saves this setting. Maybe I can just manually edit that file.</p>

<p>I used the opportunity to take a picture of the MacIvory though. Enjoy!</p>

<p><img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1437-copy.JPG" alt="MacIvory III Transplant"></p>]]></content:encoded></item><item><title><![CDATA[Todd MAX-354-1252 Power Supply for XL1201]]></title><description><![CDATA[<p>So, I learned something about the Todd MAX-354-1252 power supply in the Symbolics XL1201 today that I thought I'd share. Not that I understand it, mind you.</p>

<p>The power supply has six trim pots. Four are obviously labeled for adjusting the four output voltages:</p>

<ul>
<li>5V at 50A</li>
<li>12V at 8A,</li></ul>]]></description><link>https://symbolics.lisp.engineer/todd-max-354-1252-power-supply-for-xl1201/</link><guid isPermaLink="false">2a5c3f0f-fcf3-4614-be6f-d06622b73912</guid><category><![CDATA[symbolics]]></category><category><![CDATA[xl1201]]></category><category><![CDATA[power]]></category><dc:creator><![CDATA[Douglas Fields]]></dc:creator><pubDate>Wed, 13 Jul 2016 23:28:33 GMT</pubDate><media:content url="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1389-copy.JPG" medium="image"/><content:encoded><![CDATA[<img src="https://symbolics.lisp.engineer/content/images/2016/07/IMG_1389-copy.JPG" alt="Todd MAX-354-1252 Power Supply for XL1201"><p>So, I learned something about the Todd MAX-354-1252 power supply in the Symbolics XL1201 today that I thought I'd share. Not that I understand it, mind you.</p>

<p>The power supply has six trim pots. Four are obviously labeled for adjusting the four output voltages:</p>

<ul>
<li>5V at 50A</li>
<li>12V at 8A, 12A peak</li>
<li>-12V at 2A</li>
<li>-5.2V at 10A (for ECL circuits)</li>
</ul>

<p>However, according to the expert engineers at <a href="http://www.powerclinicinc.com/">Power Clinic</a> "The two [remaining] trim pots in question are related to the front-end boost circuits. One is for operation frequency and the other is for boost fold. NEITHER should ever be adjusted."</p>

<p>As I understand it, switching power supplies work by switching the output voltage on and off extremely quickly (on the order of 100kHz) from the high input voltage, so obviously one of these tweaks that frequency. No idea what the "boost fold" is - but fortunately according to the engineers I never have to touch it.</p>]]></content:encoded></item></channel></rss>