When I moved back to Ottawa in April 1976 to take a job at Carelton University’s Computer Center, I was already fascinated at the prospect of actually owning a computer. There were a very few computer “kits” on the market already, including the Altair and Imsai.
Having no significant expenses, I decided to splurge and purchase the IMSAI 8080 — and have the kit assembled for me at extra cost. Although called the “8080” after the Intel processor, a newer processor called the “Z80” had recently emerged and was not only compatible, but much more powerful. Of course I ordered mine to be built using the Z80.
Initially this was a personal experiment. I was interested to see what these new “personal” computers could amount to. Admittedly, although I saw great potential, I felt that their time had not yet arrived.
My system consisted of the processor, a whopping 40KB of memory, a single floppy disk drive, a CRT monitor (made for security systems) and a keyboard (which was not enclosed in a case, just the raw circuit board on a piece of bubble-wrap.
Programming was done either in machine code by entering steps via the front panel switches, or using a very simple BASIC programming language that was then available.
Although I didn’t do much with it other than experiment, I did write a demo calendar program that displayed a month calendar on the screen for any year… and the demo could be run so that the months progressed automatically. I offered the program to the store that I purchased the computer from, and they actually had it running in their window for a while!
One day I got a call from the Ottawa Citizen newspaper asking if they could send up a team to interview me. Seems they wanted to do a story on this new “home computer” phenomenon, and the store told them that I had one of the most powerful systems in the city!
The photos are not of my actual system which sadly I junked when we moved to Chicago in 1993, but they are of the exact system I had. The original newspaper article is also below.
The photo of the only remaining original memory card from that system IS real. That board measures about 10″ wide and 1/4″ thick and contains 16 KB (16,000 bytes) storage. Contrast that to today’s fingertip-sized micro-SD cards in your phones… As an example I gave to my classes: It would take 1 million of these cards to match the capacity of a 16 GB micro-SD. Placed end-to-end, those cards would stretch about 144 MILES. Stacked, they could make a pile almost 4 MILES high! Not to mention that these 16KB cards cost about $100 each, so 1 million cards would cost $100 million!
And today 16GB is a very small SD card, with capacities approaching the TERABYTE range!
Memory card provided only 16KB Ottawa Citizen article Jan 5, 1978
Having dabbled for a few years in the fledgling micro-computer field, I decided to see if I could turn my knowledge into some sort of business, advising companies in ways to use these new micro systems to help with some basic business tasks. Of course this was very part-time, as I was working for Litton Systems those years.
Remember, there were no computer graphics yet… so I picked the name MicroDyamics, and created a logo using Lettraset (rub-on letters and lines). Then I printed a business card. I still have samples of the last two iterations of these cards: the first showing our Carling Avenue apartment address in Ottawa, then a second version at our York Hill Blvd. address in Thornhill (Toronto).
Although I did approach and speak to a few small businesses, I don’t believe anyone took me up on my suggestions. It was simply too early to turn this into a business. But I had fun creating the name and designing the logo. Years later I was approached by some firm in Vancouver asking permission to use the name MicroDynamics (which I had registered in Canada). Since I had no plans for it, I said OK. (The concept of selling URL’s — which didn’t exist yet — wasn’t applicable, and I didn’t ask for any compensation since they planned to use a different name if I said no.)
Small ad run in the Ottawa Journal December 28, 1979
Shortly after moving to Toronto I took a job at Litton Systems Canada (LSL) — a division of Litton Industries. This division was primarily tasked with producing guidance systems, and at one point most of the commercial airline guidance systems in the US and Canada came from LSL.
My position was in a section called Test Equipment Engineering. They were responsible for making sure that all pieces of test equipment used in manufacturing were precisely in spec and accounted for. There were literally thousands of items that were considered “test equipment” — anything from a sophisticated electronic device down to a screwdriver, and also the software that ran any automated tests. Our task was to track every item, recall it according to its schedule, have it tested in a lab, and then update the records and return it to use. Our customers (many contracts were from the US pentagon and other countries) required such records be kept accurately.
When I started there, they had a rudimentary program based on old hierarchical database technology, but they wanted to modernize and improve the system. I was in charge of the migration to Unix-based computers (Hewlett-Packard HP-UX) and a relational database (Informix). I was instrumental in selecting the computer model and other related hardware, doing most of the database programming, and managing a few other workers.
The system pumped out printed forms for each item that was due for calibration, then these forms went to the calibration labs where engineers would retrieve the physical devices (each had a serial number tag). After they were calibrated (tested against standards), the forms were filled in and the devices were returned to use. Some devices required calibration only every few months, while others called for weekly or bi-weekly testing.
I was also responsible for our department’s computer terminal installations and re-locations. In those days, workers had a terminal on their desks, not a computer. The terminals were connected using a COAX cable, and communicated directly to the UNIX computer. One of the attached photos shows the COAX cable tap that was used to connect an individual terminal to the coaxial network line.
Another project that LSL worked on was the first “heads-up” display for the Apache helicopter. Although I wasn’t an engineer, someone offered me a tiny role just for fun: The system had some control buttons with a novel LCD backing that could change icons depending on its function. I was given the opportunity to design one of the LCD icons! I don’t recall what it was, nor do I know if it was ever actually used in production, but it was something of a thrill.
The Litton job (which I kept for 12 years until we left Toronto), was my introduction to UNIX, Hewlett-Packard, and relational databases.
Litton System Canada keychain souvenirCoax tap connector
In late 1984 Hewlett Packard released its first entry into the fledgling PC market — only about a year after the original IBM PC was released. It was a fascinating device, light years ahead of anything else on the market. Here are a few reasons why:
Number one is that this machine had a TOUCHSCREEN interface! In 1984! Now it wasn’t like today’s sensitive touchscreens; this was a crude array of crisscrossing infrared light beans in front of the screen that would sense your finger position when it broke the beams… but still, way ahead of its time on a personal device!
All other PCs of that era had an integrated disc drive, meaning that you could get different storage capacity only by buying a different model device. The HP150 chose a smarter path: The computer was integrated with the monitor, but storage was a separate unit connected via an HP-IB cable. This allowed for all sorts of configurations simply by swapping or adding storage units.
In a feat that I don’t think was ever repeated, HP used space in the top of the display unit to house an (optional) thermal printer!
Being privy to the internal technical documents, I discovered that — even though no color PC monitor yet existed — the operating system had all the support calls and routines to drive a color monitor! Clearly the engineers felt that color monitors would be a consumer demand, and in the hopes that HP’s software would survive, they planned for it.
Leveraging HP’s long standing as an engineering company, the device was wonderfully serviceable, with easy access and a number of modular, replaceable components.
Finally, even though the device was powered by MS-DOS, HP built their own user-friendly interface on top of it (much like Microsoft did with Windows years later, albeit much simpler.) This was called P.A.M. (Personal Applications Manger), and it presented all loaded applications as a table of boxes — like the icons on today’s cellphones! To launch a program you simply touched the appropriate box.
Understanding that HP’s target market was corporations more than personal users, the engineers made sure that the device could function as a full-featured computer terminal connected to the corporate mainframe or mini computers. This was a brilliant move that encouraged many companies to purchase the HP150 line.
I was blown away by the concept and the execution. Unfortunately for HP, where they were brilliant in engineering , they were very poor in marketing. Although MS-DOS based, the system was NOT compatible with the IBM PC, and the same programs could not run on it unless they were modified (much like IOS/Android apps are not interchangeable). Personally, I believe that had they engaged the right marketing talent, they had a chance to blow away the IBM PC market. But their marketing failed to promote some of the main advantages that I outlined above, and so within a few years the HP150 line had to be abandoned.
In any case, I was excited about the possibilities that I saw in 1984, and decided that I wanted to try my hand at becoming one of their software creators. I chose an application that (1) I had some familiarity with, (2) was understandable and useful to most corporations, and (3) that adapted very well to the touch interface. (Unfortunately, I was so convinced that this was the future, that I designed my program such that it REQUIRED the use of touch). The application I chose was calendar management (setting, moving, deleting, notating appointments on a calendar and finding available time slots across multiple calendars, etc.
In order to become a certified HP software development company (and get huge equipment discounts and access to internal technical information) I had to write up a detailed plan and submit it to HP. I was successful, and received their approval.
So I purchased the original HP150 (a couple of years later they came out with the 150B) along with all the “trimmings” — hard disc drive unit, double floppy drive unit, internal printer, etc. and got to work on the detailed design and programming. Most was written in Fortran since there was a Fortran compiler available.
Since I did not have financial backing, I did everything myself: Program design, coding, testing, writing a user manual, all aspects of product packaging, designing and producing a marketing flyer, publishing ads, creating sales incentives, and doing sales!
Just as an example, the packaging alone required seven vendors: (1) a box, (2) a foam liner, (3) a plastic diskette box to hold the required 3 discs, (4) a die-cutter to cut a hole in the foam liner to hold the diskette box, (5) a commercial printer to print and bind the user manual, and to print a box wrapper, (6) assembly of all the components in the box (discs, manual, warranty card, feedback postcard), and (7) shrink wrapping of the final packaged product.
I will let the attached documents speak to the actual program capabilities. Although laughable by 2020-era applications, this was unmatched for its time. It sold in very small numbers — probably several dozen total — but in more than 4 countries! I gained experience working with computer stores, various corporations (a branch of General Electric in Texas comes to mind; also a couple of hospitals and doctors.) By the time it came to market in mid-1986, the HP150 had already lost way too much ground to the IMB PC, and within 2 years had to be discontinued by HP. So my market was doomed from the start because the program REQUIRED the HP150 PC.
I’ve attached the marketing flyer, the full user manual (produced on my own text printer and a small HP graphics plotter that I also purchased), a magazine review and some ads that I placed. I was particularly pleased when the reviewer heaped praise on my user manual, because I personally hated the way most program manuals of the day were impossible for an average user to understand or use effectively. I also pulled out the actual computer (which I still have, in pristine condition) a few years back and found it to still work perfectly — and have attached a couple of photos and a short video clip showing the touch function.
Also attached is the cover of a user guide for a second application that I didn’t write, but marketed for another software author. This was a very simple program that allowed the creation of signs/banners created on a character printer by converting the words to huge sideways characters. I used this to print all of the kids’ birthday banners (one attached.)
To this day, I value all of the vast experience I gained from this project. Although it cost me a lot of money, I would not trade that experience for anything. This could not be obtained in any school.
Cover feature, Byte magazine Testing the system after it had been packed away for 30 years, still working!
The touchscreen interface from 1984Example of banner created using Wideways-150
Sometime in 1988 Litton decided to move our section to a different building. Prior to that, all of our computing equipment was in a crowded room that was not properly designed as a computer room. When they told us about the plans, they also allowed for us to design and implement a properly-outfitted computer room, since our systems were by this time deemed essential to the business.
The task of designing the computer room was given to me. This included the layout, placement of equipment, cabling requirements and design, and some hardware selection. It was, for me, something new and challenging — but I enjoyed doing it.
When the room was finally ready and all cables pre-installed, I was asked if I could manage to get the systems back up within 3 days after the move. I readily agreed, but because of all my pre-planning and careful labeling of all cables, we were back up and running in 24 hours!
I found a video that I took shortly after the room was put in service, and added some descriptive narration. (I noticed afterwards that I stated it was around 1985, but I saw a date stamp later in the video that showed 1989. Assuming the camera date was set correctly, this was likely 1989.)
Although we really liked our little house in Thornhill, the exterior grounds needed work. Without any experience in such things, I decided to take it on myself.
No YouTube videos in those days, but I read lots of articles on how to properly work with brick pavers.
I carefully planned out a front stoop and staircase, a walkway to the sidewalk, and a walled-in garden alongside the garage. I figure as long as I was embarking on such a project I might as well address the backyard as well, so I designed a patio and a swing set.
Digging out the old sod proved too difficult for me, so I hired our housekeeper’s husband to do that part. But the rest I did myself!
I had the brick pavers and wall retainers delivered, along with crushed limestone as a base, and some railway ties to frame the patio. Rented a machine to tamp down the limestone base, and a brick table saw to cut the pavers. It was a huge job, but I pulled it off. To this day I don’t know how.
I found some “before and after” photos that I took of the front, some shots of the patio, and a video that I took during the construction.
Remarkably, when I visited in 2021, the front walkway and steps still looked perfect!
After the collapse of the HP150 computer line, I decided to try my hand at consulting. At Litton Systems I had gained much expertise in UNIX and the Hewlett-Packard Unix (HP-UX) server line. I had also developed some good contacts at HP both from my software development venture and from dealing with the local HP sales reps for Litton.
I decided to recycle the (already-incorporated) Soft-Touch name as a consulting venture specializing in HP Unix systems. I initially got a couple of referrals from my HP sales rep, and slowly built up a few customer contracts. I don’t recall all of the company names, but Black & McDonald Electrical, and Four Seasons Hotels were two of them. There was also at least one real estate developer. I probably had only about 4-6 clients at its peak, before we decided to relocate to Chicago.
The way it worked was that I helped in some cases as these companies installed or switched to HP servers, and also was their “on-call” technical support if they had problems. I set up backup systems for them, and also helped them with communications and networking.
A very notable event was when I got a call from the head office of Four Seasons Hotels (in Toronto). They were opening their first hotel in Chicago, and their local IT guy was not too comfortable with the HP systems. An HP sales rep referred them to me. After meeting with them at the head office, they arranged to send me to Chicago to assist with configuring the system after the installation. Although it only required a couple of days onsite, I did get put up in a nice brand new Four Seasons hotel room! Afterwards I assisted the local staff by phone as required.
A friend that I knew from Chabad contacted me to try to interest me in a multi-level marketing opportunity. At the time I had zero interest in it as a business, but agreed to try the product mostly to help him out.
The product was a 75-year old recipe of botanicals in a liquid form that many people claimed did amazing things for them, especially in terms of increased energy and oxygen levels. I figured there was no harm in trying it.
After just a few days using this black liquid concoction (called Matol in Canada, where it was made, and marketed under the name “Km” in the US), I found that I did in fact feel a rush of energy. This made me want to know more about it, so I attended some local meetings and got hold of all their marketing materials.
Short story is that I was sufficiently impressed to want to try my hand with it — not so much as a business, but to let others know about this amazing natural product. Over several months I attended a few training seminars, read lots of materials (including videos of the inventor), and got a number of people to try the product. A few even signed up to attempt it as a business once they too felt a positive response to taking it. One fellow even told me that it cured the frequent migraines that he had had all his life!
When we moved to Chicago in 1992 I continued with this on a very part-time basis for a while. I wasn’t really too interested in it as a business, but a few people did sign up to try it, and several people reported amazing results with the product. I continued very casually until I landed my job at Abbott. Once working full-time I really didn’t have the time or interest to pursue it. I did, however keep taking the product myself for many years.
Although multi-level businesses were not really my thing, I found that I learned a lot of valuable marketing and personal business ideas from their trainings. They had a different way of looking at things, because in MLM, the more successful you make those recruits under you, the more successful you become. This is in contrast to most corporate managers who are usually more interested only in getting the best value from their subordinates for the least investment.
I leveraged those ideas (and others) as I got more into management roles, because I believed this was the best way to manage. When I hired people in various specific technical roles, I chose people who knew those areas better than I did. I might have had a greater over-all view of the technical and business situation, but I wanted those working for me to each be experts in their narrower field. Much later, as I read management books, I discovered that this was considered the essence of good management. I have MLM philosophies to thank for putting me on that “best practice” management path.
Sometime around 1991 I was put in touch with a guy in Chicago who had developed an innovative product and was looking for people to help market it. Being in Canada, it was an opportunity to have my own territory if I was interested.
First it is necessary to understand that at this time small portable cellphones didn’t exist for the general public. The only cellular options were built-in car phones, and something called a “bag phone”, which was a fairly bulky and heavy cellphone-and-batteries in a bag.
The product was basically a car phone built into a rugged aluminum briefcase. The large required batteries were under a false bottom in the briefcase, and a charging connector was on the outside of the case. A small metal antenna was mounted on the top of the case, as were some status lights and switches.
So basically this was like a super large and heavy bag phone. Where it differed greatly was that it came with a computer terminal that attached in the case on velcro strips and could communicate through the cellphone. Also available was a portable fax machine that could attach to the same velcro (in place of the terminal).
The target market for the fax machine were professions such as lawyers, real-estate salespeople, etc — anyone who in those days relied heavily on FAX communications. The terminal market was hoped to include all sorts of areas that could use a rugged and portable computer terminal connection — like for example on a construction site, law enforcement, etc.
I liked the concept even if I was unsure if it would take off. So I got a unit (including both the terminal and the fax machine), and tried my hand at marketing it. Again, I re-used the Soft-Touch name. I recall that I did bring it to several businesses for a demonstration, but although they were all impressed, none turned into sales.
One interesting story: Shortly after getting my own unit, I received a support call from the Four Seasons hotel in Chicago. They were experiencing a computer problem and it was affecting their operations so it was considered urgent. Having given them my “cellphone” number, they contacted me on this device. I was driving on the 401 highway in Toronto at the time.
When they heard that I was driving, they figured that they would not be able to have my help until I got to my destination but I told them I would try. I pulled off onto the shoulder of the highway and used the computer terminal to access their system in Chicago via the built-in cellphone. I found and corrected the problem in about 10 minutes, then called them back to let them know. They were astounded! No one else had the capability in those years to do that while on the road.
As innovative as the system was, it was probably a bit ahead of its time. In any case, small portable cellphones were commercially available within about a year, so this went nowhere. Once again, I showed my tendency to jump into something that was a bit too innovative for its time.
The attached photos show the terminal, and also a couple of construction site photos that I took for potential marketing purposes.
In 1992 we decided to move from Toronto to Chicago. After 12 years at Litton, this was a major change in my career. After taking a few months to settle in Chicago, I turned to job searching. I found an ad for a consulting position at Abbott Labs headquarters in north Chicago, and easily landed that temporary position.
Turned out that one Abbott division was trying to move from legacy mainframe computing to HP Unix-based systems to save money. After a few months working at Abbott, they offered to make me full-time and I accepted.
The division I worked for was called Clinical Services, and was responsible for gathering, analyzing and reporting on all the clinical trials data for new pharmaceutical products. Of course, my role was as an HP Unix expert, figuring out the hardware, software and design best suited to meet the division processing requirements. The work was interesting, and looked to be a 3-year project to get all the users and applications moved to Unix.
The Abbot Park location was beautiful, very much like a university campus, with multiple buildings in a large park-like setting. Many of the people I interacted with also reminded me of a university environment, since they were PhD medical researchers.
Working at Abbott gave me a deep insight into the trials and tribulations of pharmaceutical research. Although these companies charge what seems like crazy prices for new drugs, and they do make huge profits, then also take huge risks. A small anecdote that made me more sympathetic to this: There was a research scientist that I became friendly with. I’d pass his office a couple of times a week and often stop for a brief chat. He was always at his computer with all sorts of molecular models displayed. One day as I passed I saw him sitting in front of a blank screen. I asked why and he told me that after 5 years researching a promising new drug, he had just proven it to be ineffective! His last 5 years was for nothing, as he said “I’m back to the drawing board.”
I was also blown away by the requirement to print literally 3-5 CARTONS of paper reports about each drug trial — and the FDA required 3 copies, so that could be up to 15 cartons! I had to set up a room with multiple high-speed printers and design a method to organize the print queues to optimize print times while keeping reports organized.
I was two years into this 3-year project when I was spirited away by a local headhunter that I knew. We had already showed solid success by moving more than half of the users and applications to Unix, with the costs being less that a single year of support costs on the mainframe. Moreover, turn around times were faster, so everyone was happy. This headhunter described a new venture within a large company that desperately needed HP Unix expertise, and I had the perfect reputation. The company was Mercer, described in a separate post.
