Tim Malone, MCSE               (805) 445-4847              tim@3tcm.net

Over 30 years of managed expertise in computer technology                        INDEX

 

I was first introduced to Novell Netware when I worked at a company called Management Systems Corporation in Salt Lake City in 1983.  Netware had just been announced and MSC was one of the first companies to begin selling it.  Netware had previously been called Sharenet.

 

I first began installing and supporting LANs and Novell Netware in 1984 when I worked for ACS Computer Systems in Montclair CA.  The owner had several law firms as clients.  We installed ARCNet topology in those early days.

 

I had first worked with ARCNet back in 1980 when I worked as a system operator and programmer for the City of Hope National Medical Center in Duarte CA.  I programmed for them in Basic on DataPoint equipment.

 

So I became familiar with LAN technology and architecture early in my career through my work with this forerunner topology, which is very rarely known or used anymore.  I think I first worked with original Netware (before 2.0) when I was configuring it in 1984.

 

In 1985 I worked for an early pioneer in the software distribution industry called Softeam.  I joined the company as the director of training but soon moved into marketing when I proposed and created the Softeam Journal, a monthly newspaper for the computer reseller.

 

As the editor of the paper, I was able to fly around the country and interview some of the early movers and shakers in the industry.  On one trip, my photographer and I spent considerable time in Provo interviewing Ray Noorda, the President of Novell.

 

While at Softeam I advised the technical staff on the finer points of implementing their first LAN and assisted in setting up the server running Netware 2.0.  It was a large LAN and ran between two buildings.  We learned a lot about repeaters and active hubs.

 

I was heavily involved in sales over the next few years so I sold and installed a few more network installations, most of them for small offices.  As a sales manager I hired and trained others to sell and install networks as well (2.11, 2.12 & 3.0).

 

In 1990 I decided to slow down from the hectic world of sales and joined a publishing firm called Price Books and Forms in Azusa CA.  I spent nearly five years with the company as the system administrator of their AS/400 and their Netware 3.1 LAN, which ran on Token-Ring to integrate easier with the AS/400.  Only problem was that their AS/400 accounting system didn’t fit their way of business.  They needed a subscription-based system and what they had on the AS/400 was DAS – Distribution accounting system.  It had no way to track renewals.

 

So I wrote a complete multi-user subscription tracking system in Clipper 5.02 so that everyone on the Novell network could access it.  While it was being developed, I used Support/400 to download the accounting files from the AS/400 every night and wrote scripts to automatically import them into the dBASE files that Clipper accessed on the Network.  It included a complete A/R and G/L system to get complete financials at the touch of a button.  No need for closing.  Everything was posted immediately and always available for summarizing in the P & L statement.

 

In 1995, I moved back into the tech support arena as the tech support manager and network administrator for Brandon International, a small manufacturing company with five locations.  I designed and installed their LAN and WAN from the ground up using Netware 4.1 servers throughout.

 

I last worked with Netware in February of 2001 while at Carson Industries in Glendora.  I kept the old Novell 3.2 server running as a backup for as long as I was there even though we switched to NT networking in 1999.

 

 

Summary: I sold, installed, worked with or supported Netware products for over fifteen years.  I am most comfortable with Netware 3.x and 4.x.  Netware has lost almost all market-share to Microsoft so I have not kept up with Novell technology lately.

 

This online resume can be reached at http://www.3tcm.net or http://3tcm.dock.net