Well, maybe no more than two, I would guess. The patent he assigned to Canopy Group was filed March of 2002.

Now he is encouraging Linux kernel engineers to "dump the FS's and NUMA" in order to be "nearly there for being squeaky clean" and to "show a good faith effort to limit SCO's claims". Some heavy duty FUD, which has been met with derision and disdain. His offer of money for anyone willing to let him get rid of the GPL on Linux code has been modified:

"On a side note, the GPL buyout previously offered has been modified. We will be contacting individual contributors and negotiating with each copyright holder for the code we wish to convert on a case by case basis."

In one message, he makes reference to a lawsuit Novell won against him, and that caught my attention, naturally. The name of the case, assuming it is the same individual, turns out to be Novell v. Timpanogos Research Group, Inc., and in his 1998 ruling, the judge mentions a Merkey-Microsoft connection. Note especially paragraph 158, where the judge highlights Mr. Merkey's signing off his emails to Microsoft "Your Loyal Servant". He was trying to do some business with Microsoft at the time. The judge had a few descriptive words for Mr. Merkey, as you will note particularly in paragraph 123 - 125 of the Findings of Fact:

123. Major testified that even though he has such a close business relationship with Merkey, he has to filter what Merkey says to find the truth, he is unable to control Merkey, Merkey is able to create his own reality which may have no basis in fact, and Merkey is prone to exaggeration.

124. In fact, however, Merkey is not just prone to exaggeration, he also is and can be deceptive, not only to his adversaries, but also to his own partners, his business associates and to the court. He deliberately describes his own, separate reality.

125. Major acknowledges that Merkey does not see boundaries; that if he feels strongly or wants to do something, he does it.

It's a case that gets cited in articles about inevitable disclosure, a controversial legal doctrine, which you can read about here, if you'd like to know more about the concept. The case was finally settled, as you can read in this press release.

I was sure you'd find the case of interest, especially if you are a kernel developer. Here is the ruling.

*******************************

IN THE FOURTH JUDICIAL DISTRICT COURT
UTAH COUNTY, STATE OF UTAH

_______________________________________

Novell Inc.,

Plaintiff,

vs.

Timpanogos Research Group Inc.,

Defendants.

_____________________________________

CASE NO. 970400339

DATED: January 30, 1998

RULING

Anthony W. Schofield, Judge

____________________________________

This matter is before the court on plaintiff's motion for a preliminary injunction. Evidence was taken in several sessions spread over many months, with hearings on May 5, 1997, July 9, 1997, October 6-9, 1997, November 3-5, 1997 and December 15-16, 1997. In addition, the court received numerous affidavits and received certain testimony by deposition.

Gordon Roberts, Michael Larson, Elizabeth Blattner and David Bennion of Parsons, Behle and Latimer have represented Novell. In the beginning Alan Sullivan and Bryan Benevento of VanCott, Bagley, Cornwall & McCarthy represented Timpanogos Research Group, Inc. formerly known as Wolf Mountain Group, Inc. (for clarity throughout this ruling, I will refer to the defendant corporation as "TRG") and all of the individual defendants. Subsequently Ronald Katz, Gary Benton and Wendy Addiss of Coudert Brothers appeared as co-counsel for all of the defendants. Thereafter VanCott withdrew. Following that withdrawal, Coudert Brothers, and W. Andrew McCullough and Randy Lish of McCullough, Jones & Ivins have represented TRG; Andrew McCullough and Randy Lish have represented defendants Darren Major and Larry Angus; and defendant Jeff Merkey has appeared pro se. ¹

Having considered the evidence introduced in the evidentiary hearing and the arguments of counsel, I now issue this ruling granting to Novell a preliminary injunction.

FINDINGS OF FACT

I find that the following facts have been proven by a preponderance of the evidence:

1. Novell is a corporation engaged in computer software development and sales.

2. For a long time prior to March 1997, defendants Merkey, Major and Angus were employees of Novell.

3. Major was employed by Novell from 1984 through 1995. In 1995 he left Novell and went to work at Cheyenne, Inc.

4. While employed by Cheyenne, for much of 1996 Major worked at Novell in the Wolf Mountain group through a partnering arrangement between Cheyenne and Novell.

5. On January 1, 1997, Major left Cheyenne and returned to full-time employment at Novell, working on the Wolf Mountain project.

6. Immediately prior to the happening of the events of March and April 1997, Merkey was a chief scientist at Novell and was the software engineer in charge of Novell's Wolf Mountain project, which was engaged in the development of a clustering initiative.

7. Immediately prior to the happening of the events of March and April 1997, Major was a software engineer working for Merkey in Novell's Wolf Mountain project.

8. Immediately prior to the happening of the events of March and April 1997, Angus was working for Merkey in Novell's Wolf Mountain project.

9. At the time of his initial hire by Novell in 1993, Merkey signed an Agreement Respecting Trade Secrets, Inventions, Copyrights and Patents (Ex. 101).

10. The agreement provided that during his employment he would have possession or access to materials which contained trade secrets, confidential technical or business information of Novell and that he agreed not to use any such information for himself or others and not to disclose any such information at any time during or after employment by Novell.

11. Major signed a similar agreement containing the same terms on February 9, 1988 (Ex. 80).

12. Angus signed a similar agreement containing the same terms on December 4, 1987 (Ex. 181).

13. In consequence of his decision to become reemployed by Novell on January 1, 1997, Major signed an Intellectual Property Agreement dated December 30, 1996 (Ex. 83).

14. In the agreement Major agreed that any breach by him of the agreement will result in "variable, and continuing damage to [Novell], for which there is no adequate remedy at law, and [Novell] will be entitled to injunctive relief. . . ."

15. This agreement contained provisions preventing his use or disclosure to others of Novell's proprietary information.

16. On January 3, 1997, Major signed an Individual Confirmation Form (Novell) by which he agreed that Novell had classified the Wolf Mountain project as top secret and that he would not disclose any Wolf Mountain information to any other person, party, or agency within Novell or outside Novell without the express written consent of a Novell Authorized Business Development Authority (Ex. 84).

17. On June 26, 1996, Angus also signed an Individual Confirmation Form (Ex. 17, 182).

18. Novell's Wolf Mountain project was engaged in developing computer clustering.

19. Clustering is the ability to physically connect multiple, independent computers ("nodes") together and for the multiple computers to work together as if one giant computer. The effect is to create a computer system which may have the computing capacity and power of a large main frame computer but to assemble it with off-the- shelf PC computers. It is expected this would provide significant computer power at a greatly reduced cost and with readily replaceable and upgradeable PC computers.

20. Because Novell is or has been the leader in computer networking, where many computers are hooked together to a common server, able to communicate together and share common application systems; clustering seemed to many at Novell as a logical next step for it to take.

21. Novell began its Wolf Mountain clustering project in March 1995.

22. The goal of the Wolf Mountain group was to develop a clustering software package either as a stand alone product for sale by Novell or to be incorporated by it into its NetWare network operating system product.

23. From the inception of the Wolf Mountain project, Merkey was the chief scientist and the head engineer working on this project.

24. From its birth until October 1996, the Wolf Mountain project was under the direction of Dr. Glen Ricart, the Chief Technology Officer at Novell. In October 1996, it was placed in a newly formed division, the Scalable Server Division, under the direction of Vic Langford.

25. Throughout all of this time Merkey remained the chief scientist on the project.

26. By late fall 1996, Merkey envisioned Wolf Mountain as a stand alone operating system to replace the operating system used by Novell in its NetWare and IntranetWare products.

27. From its inception the Wolf Mountain project had been housed at the Orem campus of Novell while the long established group which developed Novell's NetWare product (hereafter the "core operating group") was housed at the Provo campus.

28. During all of this time, Merkey felt that the Wolf Mountain group was treated much like a stepchild by the core operating group. He endured this because he felt that Wolf Mountain constituted the first significant innovation at Novell in a long time and constituted a potential product which would return Novell to major importance in the computer industry.

29. Part of Merkey's ability to deal with what he felt to be second class treatment of the Wolf Mountain group by Novell was the personal support he felt directly from Novell's presidents.

30. At the time that the Wolf Mountain project was begun, Bob Frankenburg was president of Novell. Then, for a time, Joseph Marengi served as president of Novell.

31. While Marengi was president he had close contact with Merkey and assured Merkey of continued support by Novell of the Wolf Mountain project.

32. In December 1996, Novell did an internal roll-out of its Wolf Mountain technology. This roll-out was for the purpose of disclosing within Novell the nature of the proposed technology so that it could be evaluated by other computer engineers at Novell.

33. While Merkey and his team felt the roll-out went generally well, they received criticism from the core operating group at Novell.

34. This criticism was as much evidence of the infighting between the Wolf Mountain group and the core operating group as it was a bona fide critique of the Wolf Mountain project.

35. After the internal roll-out the level of internal criticism of Wolf Mountain increased.

36. In early 1997, the Scalable Server Division was placed under the management of Denise Gibson, who also managed the core operating group.

37. Merkey felt that placing Wolf Mountain under common management with the core operating group was a significant blow, if not the death knell for Wolf Mountain as a separate, distinguishable product to be offered by Novell. He doubted that with both the core operating group and Wolf Mountain under the direction of Gibson, Novell would ever be able to regain its position in the computer industry.

38. In early 1997, when Merkey realized that Novell was not going to proceed with the Wolf Mountain project in the manner which he wished, he began to devise a plan to take the Wolf Mountain project out of Novell.

39. Initially, Merkey sought to take Wolf Mountain from Novell in an amicable fashion, by agreement with Novell that a new spin out company would be formed.

40. He did this by lobbying Marengi for a spin out of the Wolf Mountain group into a separate, stand alone corporation, owned by Novell.

41. Marengi entertained these suggestions because he claimed to still believe in the Wolf Mountain technologies and the Wolf Mountain project.

42. Marengi discussed with Novell's counsel the possibility of creating a spin out company for Wolf Mountain.

43. There is a kernel of truth in Merkey's claim that he discussed the Wolf Mountain spin out with senior Novell executives.

44. What is missing is Novell's agreement. Though both discussed the issue with Merkey, neither Marengi, who was president of Novell until early April 1997, nor Eric Schmidt, who was president thereafter, approved the spin out.

45. Major had no independent knowledge of Merkey's discussions with Novell executives concerning the spin out. Rather, he relied on Merkey for any understanding which he had of those discussions.

46. By March 7, 1997, Merkey was so frustrated with Gibson's supervision that he and Major each tendered resignations from Novell.

47. Major believed that the Wolf Mountain project was an industry leading processing system and he did not understand why Novell did not openly and vigorously embrace the new technology. Rather, he believed that Novell was shooting arrows at them rather than encouraging the new technology.

48. When he resigned, Merkey told Stevenson he felt his dreams of building an industry leading information processing system could be best accomplished outside of Novell.

49. Each year in the spring Novell hosts a gathering of computer scientists, experts and industry analysts in a symposium called Brainshare.

50. The purpose of Brainshare is to advise Novell's partners, other software engineers who want their programs to work in harmony with Novell's Net Ware operating system and anyone else interested in Novell's business what products it anticipates developing and shipping in the immediate future.

51. Although Gibson initially scotched the idea of featuring Wolf Mountain at Brainshare, Merkey lobbied hard for Novell to prominently display its Wolf Mountain technologies at Brainshare.

52. Novell accepted Merkey's urgings. As he had been the chief scientist on Wolf Mountain, Novell persuaded him to return to that position, which he did around March 10, 1997.

53. Upon his return to the Wolf Mountain project, Merkey told the Wolf Mountain team that he returned, that the status of Wolf Mountain as a separate division was undecided until after Brainshare, that Major was pursuing an outside venture, and that it was time for the Wolf Mountain group to perform ("For now, let's get a kick-ass demo for Brainshare and show the world that Novell isn't Braindead anymore." Ex. 99)

54. Brainshare was held during the week of March 24, 1997, at which time Merkey made a number of presentations in which he touted the Wolf Mountain technology. Also at Brainshare Novell demonstrated a 12-node computer cluster, giving clear credibility to the claim that Wolf Mountain was a well-developed, functioning set of technologies.

55. Major, however, never returned to employment with Novell.

56. Despite Merkey's desires, a spin out corporation never was created by Novell.

57. When a spin out was not forthcoming, in mid-March Merkey asked Novell if he could form a new company to engage in various software development interests.

58. Novell agreed that he could form such a corporation but asked that he coordinate with Novell's lawyers so that Novell's intellectual property rights would be preserved.

59. On March 18, 1997, Novell and Merkey and Major entered into an agreement by which Merkey and Major were allowed to form a new corporation for the purpose of engaging in software development (Ex. 8).

60. One condition of the March 18 agreement is that Merkey and Major would respect Novell's intellectual property rights.

61. In the March 18 agreement Merkey and Major also agreed that if the new corporation developed products which compete with Novell products, they would obtain required licenses for any of Novell technologies.

62. Merkey personally agreed that, since he still was an employee of Novell, he would comply with the existing Novell employee confidentiality procedures.

63. David Stevenson, Merkey's direct superior and one of Novell's primary witnesses in this proceeding, even invested $500 in the new company.

64. Stevenson invested in this company on the express assurance from Merkey that the company had the blessing of Novell's management.

65. This new company originally was named Wolf Mountain Group, Inc. Later, after this action was begun, it changed its name to Timpanogos Research Group, Inc.

66. Merkey, Major and Stevenson were the original investors in TRG.

67. Prior to April 17, 1997, Merkey transmitted to John Balciunas, via e-mail, a copy of a document entitled Tapestry for NT Architecture Overview (Ex. 26). This document originally was prepared by Merkey on a Novell computer server.

68. Also, in a draft press release issued by TRG on or about March 31, 1997, at a time that Merkey still was an employee of Novell, TRG announced plans to develop a product named Tapestry with the feature set described in the Wolf Mountain Architectural Overview (Ex. 49).

69. The Tapestry document is virtually identical to a document prepared by Merkey while at Novell entitled Scalable Server Division Wolf Mountain Architecture Overview (Ex. 10).

70. A close comparison of the two documents reveals that virtually the entire text of the Tapestry document has been lifted verbatim from the Novell Wolf Mountain Architecture Overview document. A few names and acronyms have been changed, but nothing else.

71. The Tapestry document is not the work of Merkey at TRG, but is the work of Novell which Merkey copied whole cloth.

72. In an internal e-mail at Microsoft Balciunas noted on April 4, 1997, that it would take a couple of weeks for Microsoft to work out positioning of the Wolf Mountain software. From the face of the e-mail it is obvious he was in contact with Merkey (Ex. 51).

73. On April 7, 1997, Merkey sent Jim Allchin at Microsoft an e-mail concerning the creation of Wolf Mountain Group, Inc., indicating that Marengi had approved a patent cross license between Novell and Wolf Mountain Group and inviting Microsoft to buy a 30% ownership interest in Wolf Mountain Group, Inc.

74. In an internal e-mail at Microsoft, Balciunas noted that Merkey was scheduled to meet with him on April 17, 1997, and that Balciunas had a copy of Merkey's architectural overview of his product (Ex. 54).

75. On April 16, 1997, Merkey met with Schmidt in a lengthy meeting in Schmidt's office. At Merkey's request, Major joined part of that meeting.

76. During this meeting Merkey advised Schmidt that he was proceeding forward with his company and that he planned to meet with Microsoft officials the next day to discuss areas where Microsoft and TRG could work together.

77. As Merkey was still an employee of Novell, Schmidt told Merkey that he would prefer that the meeting with Microsoft not take place, that if he went he did not go with Novell's approval or authorization, and that he should respect Novell's proprietary and confidential information.

78. At the conclusion of the meeting between Merkey, Major and Schmidt, Schmidt asked that Merkey and Major take no further action with respect to TRG for two weeks. Major committed that they would not.

79. With Schmidt's admonition still ringing in their ears, on April 17, 1997, Merkey and Major met with John Balciunas and other employees of Microsoft at Microsoft's offices in Redmond, Washington.

80. Merkey told Balciunas that he had created the Tapestry document after he was authorized by Novell to form a new company. Balciunas understood this to be March 18, 1997.

81. Merkey told Balciunas that the Tapestry document had been prepared "starting from 'a clean piece of paper' ".

82. Merkey advised Microsoft that he and Major were filing for 14 patents and that he was negotiating a patent cross-license agreement with Novell.

83. Similarly, in a letter dated April 3, 1997, from Major to David Bradford, Novell's general counsel, Major urged Novell to enter into patent cross-license agreements with TRG (Ex. 86).

84. During their meetings with Microsoft, Merkey spent two hours describing the Tapestry technology and he explained how Novell had invested $15 million in their new company. All aspects of this presentation were essentially dishonest as the technology was Novell's Wolf Mountain technology not TRG's and Novell had not invested any money in the new company.

85. Though Major is portrayed in this litigation as an honest individual who has an eccentric and exaggerating partner, in fact, by his quiet during the Microsoft meeting, Major was a direct participant in the dishonesty.

86. In their meetings with Marty Albert the very next day, directly contrary to what they told Microsoft the day before, Merkey and Major told Albert that Novell had not made any investment in the new company. They looked to Albert to be their financier.

87. While Merkey asserts that the April 18-19, 1997 meeting was his first with Albert on the subject, that seems highly unlikely as, by the end of a meeting which Merkey asserts was brief and no technical information was disclosed, Albert had agreed to invest several million dollars in the new venture, hardly the prudence which would be expected from a successful businessman.

88. Following Merkey's meeting with Balciunas on April 17, 1997, Merkey sent Balciunas an e-mail dated April 19, 1997, in which he advised that TRG was focusing on Tapestry and would have a product available for Microsoft to review in its laboratory by late July and would be shipping by December (Ex. 57).

89. As he had just met with Balciunas and Balciunas had a copy of the Tapestry architectural overview, it is clear Merkey was saying that he was going to build essentially the same product he had been developing while at Novell.

90. Prior to leaving Novell Merkey told several Novell employees that he had intentionally under documented his work so that it would be in his head and not Novell's. Some quote him as also saying that when he left Novell he would take with him "the crown jewels", which they interpret to be the most sensitive technologies developed in Wolf Mountain.

91. Having spent considerable time in trial and error experimentation at Novell, Merkey and Major acquired negative knowledge while becoming intimate with what worked and did not work in the process of developing technology. From their experience at Novell, Merkey and Major knew where their starting point was and could thereby avoid "false paths" and "blind alleys" in developing any products for TRG.

92. This negative knowledge learned at Novell allowed Merkey and Major to cut corners in designing the Tapestry product for TRG. Because as Merkey stated, much of the information about Wolf Mountain was in his head, Merkey was able to save considerable time in testing and design research that was required at Novell.

93. Because Merkey and Major announced the Tapestry for Microsoft Windows NT product so soon after their resignation from Novell, it is clear they used the negative knowledge learned at Novell.

94. Merkey also told Balciunas that "all of the information was 'in his head' " and that he hadn't written anything down in years.

95. In an interview published in Lantimes magazine on May 12, 1997, less than a month after he left Novell, Merkey stated that TRG's product, Tapestry for Microsoft Windows NT, was "fairly far along."

96. In that same interview he stated that:

One of the biggest problems is, when we were doing Wolf Mountain at Novell, we were running real quick and just cranking code out. None of the intellectual property is documented. None of the patents have been filed. The only place the knowledge exists is inside [my head] and [Major's]. None of it has been written down. In terms of Novell attempting to sue us for intellectual property, I'm not sure they know what to sue us for.

97. This interview was given at a time that Merkey was technically still an employee of Novell as he resigned by a letter dated April 20, 1997, but to be effective two weeks later, on May 4, 1997.

98. On April 20, 1997, the date of his second resignation from Novell, Merkey sent an e-mail to the members of the Scalable Server Division/Wolf Mountain team at Novell in which he advised them that he and Major had acquired funding for TRG and that the new company was hiring.

99. On April 23, 1997, Merkey told Balciunas in an e-mail that he was on track for delivery of the Tapestry product by December 1997 (Ex. 59).

100. In the April 23, 1997 e-mail Merkey told Balciunas that 70 senior architects and developers at Novell had resigned to join TRG. While TRG did hire some former Novell employees, it only hired a handful, not the 70 to which he alluded (Ex. 59).

101. In that same e-mail Merkey told Balciunas that TRG had "captured clustering mindshare, and shifted it to WolfPack and Windows NT."

102. This only could have meant that he was claiming to have taken the clustering initiative from Novell's Wolf Mountain group to TRG for use by Microsoft which had a clustering initiative called "Wolfpack."

103. In a news story on the internet in a service entitled Info World Electric News dated April 28, 1997, Merkey is quoted as claiming to have taken 70 Novell employees with him when he left Novell (Ex. 142).

104. In that story Merkey describes his Tapestry product as software which works in conjunction with Microsoft's Wolfpack to strengthen scalability and would enable the formation of heterogeneous clusters of Intel-based servers running Windows NT, Intranet Ware, and Unix (Ex. 142).

105. For a company in which Merkey had been employed for only a week and Major only a month, it is inconceivable that TRG had any product other than the alleged Tapestry product which Merkey described to Microsoft by peddling it a slightly edited copy of the Wolf Mountain architectural overview which he prepared while at Novell.

106. On April 29, 1997, the court issued a writ of replevin authorizing the constable to search the residences of Merkey, Major and Angus, to retrieve Novell documentation and computer equipment located at the residences.

107. At the time that the constables searched his home, Major had a copy of the following confidential Wolf Mountain documents at his home: (I) Clustered Network Operating System (this is the body of the patent application filed with the U.S. Government); (ii) Product Proposal for Wolf Mountain; (iii) Novell Corporate Architecture--Wolf Mountain Summit Summary Review; (iv) Wolf Mountain NDA briefing with META Group; and (v) Wolf Mountain: An Invited Analysis/Report. (Ex. 47). Other than item (I), each of these documents bore a legend that it was confidential. Each contained extended analysis and detailed information about the Wolf Mountain technologies

108. While the search was on at Major's home, Major contacted Merkey by cell phone and advised him of the search. At that time Merkey was at Angus' garage working on computer equipment for TRG.

109. Though he has complained bitterly about the trauma inflicted upon his children by the search, Merkey was not present at his home when his home was searched and has no first hand knowledge of what happened then.

110. Merkey was aware that he was being looked for and that the Novell computers in his possession were being sought pursuant to the writ of replevin.

111. At the time that the constables searched his home, Merkey had a copy of the following confidential Wolf Mountain documents at his home: (I) Wolf Mountain: An Invited Analysis/Report; (ii) Wolf Mountain Architecture Overview-Draft-; (iii) IDC Commercial Systems & Servers--Short Report for Novell--Beyond Netware; (iv) Novell Corporate Architecture--Wolf Mountain Summit Summary Review; (iv) Novell Project 2000 Hand-Outs; (v) Novell Project 2000 Technical Information; (vi) IDC Systems Research--Proprietary Novell Report: Strategic Assessment of Wolf Mountain's Market Space; and (vii) Wolf Mountain Architecture Overview. Other than items (iii and vi), each of these documents bore a legend that it was confidential or a Novell company secret. Each contained extended analysis and detailed information about the Wolf Mountain technologies

112. Merkey explained at hearing that after learning that the constables had searched his home, he did not return to his home until he had returned the laptop computer (which later was discovered to have a smashed hard drive). This contradicts other testimony where he said the laptop was at his home by the docking station when the constables searched his home.

113. Late in the evening of April 29, 1997, Merkey returned a laptop computer to Novell. Upon inspection Novell discovered that the hard drive in the computer was smashed. That same computer and hard drive were offered as an exhibit and the court has personally inspected the computer.

114. The hard drive of the laptop is a modular unit, easily removable from the computer.

115. At trial the hard drive was removed and inspected by the court. It had the appearance of having been smashed with several blows from a hard object like a hammer.

116. Merkey has offered no less than four different explanations of how the hard drive came to be smashed, pointing most of the blame to his children.

117. One of his explanations is that he was so angry at the replevin that he threw the computer at Novell's door when he returned it. This explanation does not fly (like the computer allegedly did) for neither the computer carrying case nor the laptop bear any evidence of physical abuse or damage, though the hard drive, which ordinarily is mounted within the plastic shell of the computer, clearly has been smashed.

118. Even if documents are deleted from a hard drive, experts often can retrieve material which has been deleted from a hard drive. As an expert in computer science, Merkey knew this.

119. The only sure way to prevent recovery of deleted material from a hard drive is to physically damage the hard drive. That is what happened here.

120. The fact that he returned the hard drive damaged while the rest of the computer appears in good shape demonstrates that Merkey intended to prevent the retrieval of any information from the hard drive.

121. That he would tell different and conflicting stories of how the hard drive came to be damaged demonstrates Merkey did not want the truth of how it came to be damaged known.

122. In their operation of TRG, Merkey and Major act much as partners.

123. Major testified that even though he has such a close business relationship with Merkey, he has to filter what Merkey says to find the truth, he is unable to control Merkey, Merkey is able to create his own reality which may have no basis in fact, and Merkey is prone to exaggeration.

124. In fact, however, Merkey is not just prone to exaggeration, he also is and can be deceptive, not only to his adversaries, but also to his own partners, his business associates and to the court. He deliberately describes his own, separate reality.

125. Major acknowledges that Merkey does not see boundaries; that if he feels strongly or wants to do something, he does it.

126. Major has tried to distance his concept of where TRG is going from public statements and other actions taken by Merkey which demonstrate a contrary direction.

127. All the while that Major made these attempts he was president of TRG.

128. For example, Major disavowed the business plan which Merkey prepared in September 1997.

129. In a letter from Merkey to Albert on September 12, 1997, Merkey asserted that the "Utah Judicial Commission contacted me Thursday, and relayed that they had reviewed Judge Schofield in Court over video camera, and have initiated an investigation relative to the Court session of September 8, 1997." (Ex. 107).

130. While it may be possible that the Utah Judicial Commission (Conduct Commission?) contacted Merkey, that commission has not obtained a copy of any video of the court session of September 8, 1997. That hearing was court-reported and the only video made was made in accord with Rule 4-201(2)(C), Utah Code of Judicial Administration, for the purpose of the judge's private notes. No copy of that sole copy has been viewed by anyone other than the court. In short, this statement is another example of Merkey's penchant for self-serving, separate reality, dishonesty.

131. While it is human nature for each of us to put our own spin on events which we observe -- indeed the heart of most auto accident cases is the different perceptions of eye-witnesses -- Merkey nonetheless regularly exaggerates or lies in his comments to others about events happening around him. It is as though he is creating his own separate reality. For example, his e-mail message to Balciunas of June 12, 1997, contains several clear misstatements or fabrications of what transpired in court (Ex. 72)

132. Merkey also was dishonest in a number of the e-mail messages which he sent to Balciunas, either exaggerating or deliberately falsifying factual assertions which he made in those e-mails.

133. There is an acknowledged tendency in the industry for software development companies to float deliberately false or exaggerated statements of prospective product offerings, a practice called "vaporware."

134. Merkey now alleges that all of his early commitments to Microsoft, which unquestionably were based upon pirated Novell technologies and information, were just vaporware.

135. Given his penchant for creating a separate reality and for deliberate misrepresentation, I find Merkey's claim that he was simply floating vaporware unreliable. Rather, he wanted to have the benefit of both worlds -- his world actually working on a clustering model based upon the Novell architecture -- but also a world in which he could claim that he was not using or misappropriating Novell confidential technical information.

136. Major also is not always truthful.

137. Major resigned on March 7, 1997 and out processed on March 20, 1997. At the time that he resigned he knew that at out processing he would be required to return to Novell all of the Novell documents he had in his possession.

138. Notwithstanding this understanding, during the two weeks after he resigned and before out processing, Major received a copy of the Wolf Mountain product proposal which was last edited on March 16, 1997. As such it only could have been obtained by him on or after March 16, 1997.

139. Even though he had received a copy of the product proposal within four days of his out processing, Major did not return it to Novell at out processing. He claimed at court to have forgotten that he received it. This explanation does not wash. He is too bright to have forgotten receipt of such an important document just four days prior to out processing.

140. This action by Major evidences an intent to hide from Novell his real purpose with respect to the document. He had no intent to return it. Nor did he even return it when the constables searched his home. Rather, his copy was returned by him through counsel a week or two later.

141. On April 23, 1997, Angus out processed after terminating his employment with Novell. At that time he certified that he had no Novell property at his home or in his possession (Ex. 184).

142. This certification was inaccurate as he had a notebook in which he recorded, among other things, notes of problem areas encountered by the Wolf Mountain team in its development and implementation of the Wolf Mountain technology (Ex. 183).

143. I do not accept Angus' assertion that he simply had forgotten that he had his notebook at home. It was far too sensitive a document and the times were far too charged to accept his claim of forgetfulness.

144. While I find that Merkey and Major are not fully trustworthy, they claim that neither is Novell. They assert that Novell acted out of improper motivations.

145. The decision by Novell to put the Scalable Server Division under the direction of Denise Gibson is a management decision which does not reflect any bias or antipathy toward Merkey, Major or the Wolf Mountain team.

146. Merkey asserts that he did not fit in at Novell because he had a different ethnic or religious background than most of the Novell workers. This claim was not supported by any meaningful evidence.

147. Merkey asserts that Gibson had a vendetta against him.

148. The record supports a conclusion that Gibson and Merkey did not get along and that Merkey chaffed while under Gibson's supervision as he felt that being placed under her supervision was the death knell for Wolf Mountain as a project.

149. During the hearing Novell introduced Exhibit 13 which purports to be a memo to Merkey from Vic Langford, the supervisor of the Scalable Server Division. Novell acknowledges that the memo was prepared for Langford's signature but that Langford declined to sign it. Defendants assert this demonstrates dishonesty on the part of Novell. Though each of our business practices sometimes are subject to question, Novell was generally forthright in how it reacted to Merkey and Major and their actions. Certainly Novell was angered at Merkey and spent tremendous sums of money pursuing this litigation against him. But I do not accept the wrongful motives which defendants attribute to Novell.

150. At a court hearing on May 6, 1997, TRG was criticized for using the name Tapestry, which Novell claimed it had used internally in its Wolf Mountain project. As a result Merkey gave the TRG product a new name: "Replevin" which the press release noted was Latin for "to search". In fact, however, with the new name selected and announced just a week after a writ of replevin had been served upon him and Major, the only fair conclusion is that he chose this new name as a direct affront to Novell.

151. In a press release dated May 8, 1997, TRG announced that it was developing "a 32/64 bit, massively scalable, clustered, fault tolerant, journaled meta-directory storage and access technology for Windows NT, Unix and other industry platforms." (Ex. 63).

152. Primary among the other platforms spoken of by TRG is Novell's NetWare and IntranetWare products.

153. This press release was issued only two weeks or so after Merkey left Novell and contains the same feature set which he designed and described in both the Novell Wolf Mountain Architectural Overview and his pirated Tapestry for Windows NT Architectural Overview. Given the extremely short time since he left Novell and the fact he had already pirated the Novell architectural overview, it is clear Merkey was building upon information, designs, and architecture which he developed at Novell and which belonged to Novell.

154. In an e-mail from Merkey to Balciunas dated May 10. 1997, Merkey asserted that the "court stuff" has only delayed their development of a product by a couple of weeks. He asserted they were still on track to deploy a product by the first or second quarter of 1998 (Ex. 64).

155. On May 15, 1997, Merkey sent an e-mail to Sharon Fisher, a journalist covering the computer industry, asking that she provide a copy of the "technical document" which he gave to her and other press folks at Brainshare. He told her he had been given permission by the court to use anything that was in the public domain and wanted to obtain a copy to prove that it was given to the press and now was in the public domain (Ex. 164).

156. In an internal e-mail at Microsoft, Microsoft noted that Merkey was going to provide a draft press release which differentiated between TRG's Tapestry product and the Wolf Mountain technology developed by Novell (Ex. 56).

157. Merkey never provided such a differentiation to Microsoft (nor, so far as the court is aware, to anyone else).

158. The depth of Merkey's shift in feelings -- an antipathy for Novell and a commitment to Microsoft -- is reflected in a variety of e-mail messages to Microsoft sent shortly after he left Novell in which he signs off as "Your Loyal Servant."

159. A computer operating system is the computer program which directs and controls the interface between computer hardware and any application programs such as word processors, accounting and spread sheet programs and internet browsers. Operating systems also are known generically as "platforms".

160. Novell's NetWare program is an operating system as is Microsoft's Windows NT and the Unix operating system.

161. One of the design goals of Wolf Mountain was to create a single system image, with fault tolerance.

162. In the development of the Wolf Mountain technologies at Novell, Merkey and Major intended platform independence or neutrality, meaning that in the design of the Wolf Mountain technologies, Merkey and Major intended that the Wolf Mountain clustering program run on or be compatible with any of the three major operating systems just described.

163. The architecture of the Wolf Mountain project includes platform independence.

164. At the time Merkey and Major left Novell they had not completed the intended platform independence. No source code had been written which would allow the Wolf Mountain program to run on the Microsoft NT or Unix platforms. Rather, the only source code which had been written was for the Wolf Mountain program on the Novell NetWare platform.

165. At the time that Merkey and Major left Novell the source code for the Wolf Mountain project was not complete, though, as Dr. Head noted, the Novell Wolf Mountain code consisted of over 20,000 files containing 600 million bytes, or the equivalent of 150,000 singly-spaced typewritten sheets, the height of a five-story building.

166. There are three primary computer languages; machine language which usually consists of O's and 1's and is machine readable; assembly language which is specific to a particular machine or computer processor; and a high level language, which is the language most application programs are written in, including Algol, Fortran, Basic, C and C++.

167. C and C++ are not fully compatible.

168. All of the TRG code was written in C++, which is the most advanced of the current high-level languages.

169. Novell's NetWare program is written in an assembly language while the Novell Wolf Mountain code is written in C.

170. Because TRG's code is written in C++ while Novell's Wolf Mountain code is written in C and the two are not fully compatible, Dr. Head asserts that TRG could not have copied or used any of Novell's Wolf Mountain confidential information.

171. This conclusion is not correct. Even though TRG appears not to have actually used any Wolf Mountain code, it has used the Wolf Mountain architecture, structure and design.

172. The Wolf Mountain project consists of the combination of many disparate technologies, the majority of which are in the public domain or are derivatives of well-known, public domain concepts.

173. Even though the Wolf Mountain project was built primarily of known, public domain concepts, the manner in which Novell assembled and combined those technologies is unique.

174. The Wolf Mountain technologies have independent value. First, Novell spent enormous sums of money developing these technologies and second, the technologies are sufficiently developed that significant parts are relatively portable, such as the UFOD and the CICP.

175. Novell always took reasonable steps to protect its trade secrets and confidential technical information.

176. First, it required each employee to sign a confidentiality and non-disclosure agreement, agreeing that the trade secrets are confidential and belonged to Novell.

177. Second, Novell required that its technologies generally be kept on campus in a secure environment. Defendants make much of the fact that Novell allowed members of the Wolf Mountain team to take back up copies of the Wolf Mountain source code and documentation home for safekeeping, there is no evidence that any of these actions ever jeopardized the security and confidentiality of those documents. There is no credible evidence that Novell did not take reasonable steps to preserve its trade secrets.

178. Third, Novell established rules and procedures concerning the public disclosure of its trade secrets. For example, Novell decided in advance what information could be publicly disclosed at Brainshare.

179. At Brainshare, when Merkey distributed a copy of the Wolf Mountain architectural overview, his superiors including Dave Stevenson attempted to retrieve any such copies and reprimanded Merkey for making unauthorized disclosures. Merkey acknowledged his action was inappropriate.

180. Merkey cannot claim information is in the public domain if he made unauthorized disclosure of that information.

181. One of the primary components of the Wolf Mountain project was the unified file object directory (UFOD). Major was the principal author of this technology.

182. The function of the UFOD is to provide a system of directory services and file management, routing and data storage services.

183. UFOD largely is built upon known technologies.

184. Any computer program designed to accomplish what the UFOD was designed to accomplish would have common parts and technologies, including memory caching, disk caching and a hierarchical storage manager and would use well known techniques such as disk mirroring, segmenting, scatter-gather and mini-volumes as the primary unit of data storage, caching, replication and distribution.

185. Though these are public domain technologies and concepts, how Novell used and combined these well known component parts is unique.

186. Major conceded that the UFOD was largely unique and likely was a trade secret.

187. The UFOD technology has independent value because to a large extent it is portable.

188. Another key component of the Wolf Mountain technology is the cluster interconnect protocol (CICP).

189. The function of the CICP is to provide a communications subsystem so that the various computers in the cluster can communicate and function together.

190. The CICP also is based upon well known, public domain technologies.

191. How Novell used, combined and applied these well known concepts is unique.

192. Before he left Novell, Merkey frequently asserted that the Wolf Mountain technologies were unique and needed protection. For example, he told Eric Gardanier, a patent attorney hired by Novell to help it patent the Wolf Mountain technologies, that Microsoft would have to get its hands on the Wolf Mountain technology.

193. In an e-mail dated June 25, 1997, from Merkey to Balciunas, Merkey said that at that time he was developing a program like the CICP, which would have "identical functionality, and multi-fabric clustering capability." (Ex 71).

194. It is clear that from the time he left Novell until at least the date of this e-mail that Merkey was building upon the Tapestry architecture, claiming it as his own, even though he had pirated that architecture from Novell.

195. Merkey repeatedly told Balciunas that he was "working on the stuff that they said they were going to be working on since the beginning of April." Again this can only have been the Tapestry based document, which is based upon the pirated technology.

196. These actions by Merkey and Major are in violation of the terms of the temporary restraining order previously issued by the court.

197. The basic structure of the Wolf Mountain technology and of the UFOD and CICP each are unique and of great value to Novell. They represent a significant investment by it in the development of a new technology.

198. Because the manner in which the technologies were assembled and combined is unique, because they have independent value and because they have been protected by reasonable efforts to maintain their confidential status, the manner of combination is a trade secret.

199. Major concedes that the implementation of the CICP protocol is a Novell trade secret.

200. Major agreed that the method of journaling which he implemented in UFOD is a Novell trade secret.

201. Major agreed that the process of containing the history of an object within itself (self journaling) is unique to Novell.

202. Major agreed that the format of how information is stored that is the object description used in UFOD is a Novell trade secret.

203. Major agreed that the message format that UFOD used to communicate between nodes is a Novell trade secret.

204. Major agreed that the implementation of the cache system in UFOD was a Novell trade secret.

205. Major agreed that there are aspects of the kernel developed by Merkey at Wolf Mountain at Novell which are trade secrets.

206. Major agreed that the implementation of the memory management system at Wolf Mountain is proprietary to Novell.

207. Major agreed that some of the marketing strategies which Novell had for the Wolf Mountain project are trade secrets.

208. Under examination by Merkey, Major agreed that the CICP wire protocol and the UFOD message protocol each were Novell trade secrets.

209. Novell has a trade secret claim to its Wolf Mountain architecture, the UFOD and CICP.

210. I believe Novell may have trade secrets in its Wolf Mountain technology other than the grand scheme, the UFOD and the CICP. In this hearing, however, other than the secrets set forth above, it did not carry its burden of proving just what those other technologies are.

211. As a result it is not entitled to protection by preliminary injunction of any other trade secrets.

212. Novell has long been a major player in the computer communications industry.

213. In order to preserve a leading role in any aspect of the computer software industry, a company such as Novell must remain forward thinking and innovative.

214. In the development of its Wolf Mountain technologies, Novell was both forward thinking and innovative. What it now wishes is to protect and preserve that effort.

215. At the outset of this litigation it appeared that the Wolf Mountain technology had the potential to be the next paradigm in the computer communications field. Merkey said as much in his in-fighting while at Novel and he said as much in his presentations at Brainshare.

216. Certainly Novell has not proceeded to develop Wolf Mountain in that way.

217. In an article in PCWEEK Magazine dated July 7, 1997, Denise Gibson is quoted as saying: "You will never see Wolf Mountain as Wolf Mountain. It will be rolled into other products." (Ex. 152).

218. While Novell has not chosen to use the Wolf Mountain technologies in the fashion which Merkey and Major anticipated and desired, it is using aspects of these technologies in other areas.

219. Merkey repeatedly asserted while at Novell that Novell had a two year head start over the competition in developing clustering technology.

220. Even though Novell has chosen not to develop a stand alone Wolf Mountain product, it nonetheless is using Wolf Mountain technologies and is entitled to protect those technologies which it developed.

221. Novell's business is to develop and market computer software in the highly competitive field described above.

222. One of the principal assets which Novell has is its trade secrets and confidential technical information.

223. Novell protects this asset by requiring all of its employees to sign confidentiality and non-disclosure agreements as set forth above.

224. In this case two senior scientists left Novell, taking with them some of Novell's trade secrets and other confidential information.

225. If these employees are permitted to take these secrets with impunity, Novell will be at the mercy of its other employees who may wish to take other of Novell's trade secrets and confidential technical information and enter into competing businesses. Such a result is wholly unacceptable to Novell and places it at tremendous risk in the marketplace, a risk which money damages cannot remedy.

226. Defendants assert that they will be harmed if Novell is entitled to an injunction protecting its trade secrets and confidential technical information. In fact, however, they have no legal claim to any of this information. Not having a legal claim to such information, they cannot demonstrate a greater harm than Novell will suffer if the requested injunction is not granted.

227. TRG is developing three products, Replevin 4.0, Replevin 5.0 and MAN 1.0.

228. Each of these three products is based upon and naturally flows from the Tapestry architecture which Merkey pirated from Novell.

229. The Wolf Mountain group at Novell was building products that perform many of the same functions and operate much like the TRG products.

230. Novell had not developed a product quite like MAN 1.0, but the Wolf Mountain architectural overview contemplated just such a product.

231. Having observed the actions and reactions of the parties from the date this case was filed through months of hearings, having observed them testify in court and seeing what it is that they told Microsoft they would do and what they now claim to be doing, and having received extensive evidence in this matter, I am convinced that defendants have used Novell technology in developing their Repelvin and MAN products.

232. At no time has TRG had any authorization from Novell to use any of the Novell technology.

233. I am further convinced that but for the interposition of this lawsuit, defendants would be well on the way to a product even more closely resembling the Wolf Mountain product which Novell demonstrated at Brainshare.

234. While TRG's Replevin and MAN products, at least in part, are based upon the Novell Wolf Mountain architecture, the actual coding of these products was done independent of Novell. The structure is Novell's but the coding and full implementation were done by TRG.

235. TRG's Replevin and MAN products are designed to work in harmony with Microsoft's NT platform.

236. As a result, many of the component parts included in the UFOD and the CICP are redundant as Microsoft has several analogous technologies.

237. Further, Novell is not now even building a product directly based upon this same technology.

238. As a result, Novell will not need a long lasting preliminary injunction.

239. Because of the great fluidity in the industry, because Novell is not even using the technologies in a stand alone product and because TRG's Replevin and MAN products do not require many of the component technologies which were contained in the UFOD and in CICP, Novell will be adequately protected if defendants are restrained from any use of the Novell technologies for a period of nine months from the entry of this ruling.

240. The existing temporary restraining order has prevented TRG from moving vigorously forward because other companies are reluctant to enter into partnering or other relationships until the litigation is complete.

241. Because of the existing temporary restraining order both Merkey and Major have been significantly distracted from the work of TRG as they have had to deal with the existing litigation. TRG's business has been slowed by this mental resource drain.

ANALYSIS AND RULING

Based upon the foregoing findings, I now enter this ruling.

Having first obtained a temporary restraining order, which order has been in place during the evidentiary hearing on the motion for preliminary injunction, Novell now seeks a preliminary injunction. It asserts a persisting harm if defendants are allowed to continue in the business of clustering software development.

Rule 65A(e) sets the standard for issuance of a preliminary injunction:

A restraining order or preliminary injunction may issue only upon a showing by the applicant that:
(1) The applicant will suffer irreparable harm unless the order or injunction issues;
(2) The threatened injury to the applicant outweighs whatever damage the proposed order or injunction may cause the party restrained or enjoined;
(3) The order or injunction, if issued, would not be adverse to the public interest; and
(4) There is a substantial likelihood that the applicant will prevail on the merits of the underlying claim, or the case presents serious issues on the merits which should be the subject of further litigation.

As to each of these issues, Novell has the burden of proof. Said another way, unless Novell provides proof by a preponderance of the evidence on each of these four requirements, it may not receive the preliminary injunction which it seeks. I treat each of these issues separately.

Irreparable harm.

I. Merkey, Major and Angus breached their contractual obligations to Novell.

At the time that Merkey, Major and Angus left Novell, each was subject to certain contractual covenants of confidentiality. By way of illustration, Merkey signed an "Agreement Respecting Trade Secrets, Inventions, Copyrights, and Patents" which provides that as a Novell employee he may have access to "material embodying trade secrets or confidential technical or business information of" Novell. With respect to any such information, he agreed that as an employee or former employee, he will not "use any such information or material for himself or others" or "disclose or publish any trade secret or confidential technical or business information or material" of Novell.

Not only are Merkey, Major and Angus subject to contractual obligations preventing their use or disclosure of Novell's trade secrets, when Novell agreed to allow Merkey and Major to form a new software development company, Merkey and Major covenanted that they would not compete with Novell, or if they did so they would first enter into an agreement with Novell concerning the use of Novell's intellectual property.

Notwithstanding these duties not to use for themselves nor to disclose to others Novell's confidential technical information, the record establishes that Merkey and Major each have violated their agreements with Novell.

By late 1996 Merkey was excited with the significant progress in the development of a new product for Novell, a product that he believed would help Novell retain its position as an industry leader in the computer communications software business and which would replace Novell's existing network products, NetWare and IntranetWare. Though he was officed at the Orem campus and the Wolf Mountain group was regularly treated by the core operating group as a step-child, Merkey believed that Wolf Mountain technologies represented Novell's future.

Then, in early 1997, by Merkey's account, Novell betrayed both him and Novell's own future by placing the Scalable Server Division under the direction of Denise Gibson, who had stewardship over the core operating group and had a personal antipathy for Merkey. To Merkey this was the death knell for the Wolf Mountain project. Against this backdrop, Merkey hatched a plan in his creative and very fertile mind. He would convince Novell to form a separate company to continue with the development of the Wolf Mountain technologies. To that end he had a number of discussions with a variety of Novell executives, particularly Joe Marengi, Novell's president. While Novell discussed the possibility, it never decided to form such a spin-out as a done deal. In late March, while still an employee of Novell, he sent to Microsoft, Novell's largest competitor, a copy of a document which he labeled "Tapestry for NT Architecture Overview", telling Microsoft he had created this document in the new company in a clean room environment. This story was patently false. With several small exceptions centering around names and acronyms, the Tapestry document is a verbatim pirate from a document Merkey wrote while at Novell entitled "Wolf Mountain Architectural Overview".

On April 17, 1997, while an employee of Novell and against the advice of Novell's president, Eric Schmidt, Merkey and Major met with representatives of Microsoft. During that meeting Merkey and Major advised that the technology contained in the Tapestry document which he asserted had been created by TRG independent of Novell, was ready for "immediate assimilation" by Microsoft.

Merkey assured Microsoft then, and regularly thereafter, that a finished product would not be long in the making. From April until early fall 1997, though he kept pushing the delivery date back blaming problems like this litigation, Merkey never claimed development of a product other than his proposed tapestry based product, a product built on the architecture which he pirated from Novell. ²

The day after meeting with Microsoft, Merkey and Major met with a potential investor, Marty Albert. Again, they disclosed to him their business proposal for TRG. By the end of their two day meeting with Albert, he had agreed to finance the new company and had been elected chairman of the board.

With a straight face Merkey and Major each assert that they never disclosed or used any confidential technical information belonging to Novell. Simply put, this is not honest. It is beyond any reasonable dispute that they disclosed Novell's confidential technical information to Microsoft and they disclosed some of it to Albert.

In addition to disclosing to third parties, Merkey and Major obviously intended to use Novell's confidential technical information for themselves. Within days of Merkey's leaving Novell, TRG published a description on its web site of its intended product development. The feature set is identical to the feature set which Novell disclosed at Brainshare.

At Brainshare the Wolf Mountain technologies worked. Novell demonstrated a 12-node clustered system that performed just the way Merkey had advertised. This technology was well developed. But for the interposition of this lawsuit I have no doubt Merkey and Major would have moved quickly to fully implement the Wolf Mountain technology which Merkey explained at Brainshare, of which he was the principal architect, and which he considered his personal baby. He even bragged to the press and to other Novell employees that he had under-documented the technology so that Novell would not know what he had, and that if Novell sued him, it would not even know what to sue for. He took and intended to use Novell's technology for his own use. ³

Each of the foregoing actions -- and others which can be found in the record -- is a direct violation of defendants' contractual obligations with Novell.

Novell spent large sums of money developing its Wolf Mountain technologies. Merkey and Major intended to use and disclose these technologies to others at their discretion, an action completely at odds with their contractual obligations. And they did so with an obvious malice. Because they are in breach of their contractual obligations they should be prevented from continuing to use themselves or from disclosing to others the technologies which Novell spent so much time and effort developing.

That such a restraint is appropriate is established by Envirotech Corp. v. Callahan, 872 P.2d 487 (Utah App. 1994) where the court of appeals noted that even absent a written employment contract, a fiduciary duty exists preventing an employee, upon termination, from disclosing confidential information of the former employer. If such a fiduciary duty exists without a contract, certainly a contractual provision preventing a former employee from using or disclosing confidential technical information also should be upheld. This conclusion is consistent with the other Utah appellate rulings touching on the duties of former employees to their former employers: J & K Computer Systems, Inc. v. Parrish, 642 P.2d 732 (Utah 1982); and Microbiological Research Corp. v. Muna, 625 P.2d 690 (Utah 1981). ⁴ Defendants' actions are both a breach of their contractual obligations and a breach of their fiduciary duties to their former employer.

Further, there is no other meaningful or effective remedy for Merkey's and Major's breaches of their contractual obligations to Novell. Money damages may provide some relief, but the only truly effectual relief available in this case is the requested restraint.

Closely related to Merkey's and Major's breaches is the fact that TRG has been created by Merkey and Major for the express purpose of developing these technologies. They now assert they are building for the Microsoft NT platform. So what? Merkey was the author of Wolf Mountain and committed that it would be platform neutral, meaning that it would function both on Novell's NetWare operating system as well as Microsoft's NT operating system and the Unix operating system. True no source code may have been written by Novell to accomplish all of these architectural goals and platform neutrality had not been accomplished, but Novell expected and intended that its Wolf Mountain products would be platform neutral. Had Merkey remained at Novell platform neutrality would be far closer by now, if not a reality. TRG cannot now complete the development for the NT platform which Novell started without impinging on the confidential technical information which Novell developed in its Wolf Mountain project.

Merkey was the chief scientist on Novell's Wolf Mountain project and Major was a senior scientist. Having Left Novell and not bound by a non-competition agreement, they can compete. But not by taking the Novell project, renaming it, and continuing to work on it. Though they now claim that is not what they are doing, all of their early press and web site announcements indicate that is exactly what they were doing. Even Merkey's draft of a business plan for TRG, prepared in September 1997, almost six months after they left and after they had been subject to the temporary restraining order for many months, establishes that they intend to continue on the same course which they had been following while at Novell. That Major, the president of TRG, disclaims the draft business plan is irrelevant. Merkey, the admitted genius behind Wolf Mountain and the one person whom Major admits he cannot control, intends to continue just where Novell had been going. For these reasons, any restraint against Merkey and Major also should apply to their new company, TRG.

Finally, as to Angus; I find he also breached his contracts with Novell as he failed to return to Novell confidential proprietary information when he left Novell. He admits as much. He likewise should be restrained from using any Novell confidential technical information in any work which he does, whether with TRG or some other employer.

II. Merkey and Major took Novell trade secrets with them to TRG. Many days of hearing were consumed in closed-door sessions while the parties addressed Novell's claim that defendants misappropriated Novell's trade secrets. As I noted in an earlier ruling in this case, the Utah Supreme Court has held that:

The threshold issue in every [trade secret] case is whether, in fact, there is a trade secret to be misappropriated. The secret is of value only so long as it remains a secret. The burden is upon the plaintiff to prove its existence as a secret, and there is no presumption in his favor.

Microbiological Research Corp. v. Muna, 625 P.2d 690, 696 (Utah 1981).

Here, Novell bears the burden of establishing that any of the information which defendant took or used is a trade secret. To resolve that issue the parties relied upon the definition of trade secret contained in Utah Code Ann. ¶13-24(2)4:

"Trade secret" means information, including a formula, pattern, compilation, program, device, method, technique, or process, that:
(a) derives independent economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by, other persons who can obtain economic value from its disclosure or use; and
(b) is the subject of efforts that are reasonable under the circumstances to maintain its secrecy.

In the analysis here I also rely upon this statutory definition of trade secret. Further, the court not only has authority to restrain actual misappropriation of trade secrets, but also threatened misappropriation. ⁵ Novell argues that while it has proven actual misappropriation, at a minimum it certainly has established threatened misappropriation.

The parties each offered an expert witness on whether any information allegedly taken or used by defendants constitutes a Novell trade secret. ⁶ Novell called Dr. Evan Ivie, a retired BYU computer science professor with a thorough computer science background and hands-on experience in an early clustering related project. Defendants called Dr. Sabin Head, an independent computer consultant from Sunnyvale, California, who has a broad base of expertise in computer software development. The court had the opportunity to listen carefully to each and I base my conclusions in this case on their testimony and my own observations and conclusions as to their credibility.

In an earlier ruling in this case I noted, as the Utah Supreme Court stated in Muna:

[A] unique combination of generally known elements or steps can qualify as a trade secret, if it represents a valuable contribution attributable to the independent efforts of the one claiming to have conceived it. The combination must differ materially from other methods revealed by the prior art.

Muna, 625 P.2d at 696.

Defendants assert that much of the technology which they are using in their new projects and efforts can be found in the public domain and therefore is not protectable as a trade secret. To a fair extent this is correct. Further, defendants also note that on leaving Novell they had a right to take with them their general knowledge of the computer industry, gained over a lifetime of study and work in that industry. Again, they are correct. ⁷ Yet, as noted by Muna, even if Novell was using generally known technologies in its Wolf Mountain project, a unique combination of those public domain elements can qualify as a trade secret.

At the direction of the court Novell submitted an exhibit which it asserts contains the trade secrets which defendants have misappropriated (Ex. 112). After asserting that each of the trade secrets identified in Exhibit 112 is a Novell trade secret, Dr. Ivie endured a merciless cross examination. Thereafter Dr. Head testified that none of the matters which Dr. Ivie identified as trade secrets in fact were. Rather, he concluded that Novell only had one protectable trade secret: the overall scheme or manner of organization of the various parts which it was incorporating into its Wolf Mountain technology.

I accept Dr. Heads' analysis that Novell's grand scheme Wolf Mountain is a trade secret. Unfortunately for defendants, this analysis supports a far broader conclusion than Dr. Head may have intended.

Defendants argued over and over again that Novell had the burden of proving what its trade secrets were but failed to meet that burden. ⁸ Defendants reminded the court several times that I continued the hearing so that Novell could more fully identify and list its trade secrets. Defendants are entitled to know what it is they cannot use. This argument is not without merit.

The technology at issue in this case is so complex and of such a high level of sophistication that it defies description by a computer layman. That problem not only stymies the court, it clearly effected Novell's counsel's ability to introduce helpful evidence to the court. What is clear is that the Wolf Mountain technology, best described and identified in the Wolf Mountain Architectural Overview, is made of myriad separate elements. A goodly portion of those elements are based upon well known, public domain concepts. But how Novell adapted, implemented, integrated and applied those public domain concepts is proprietary. To some extent Novell established that it had developed new and different technologies, but to an extent it also failed.

As I have explained above, in late March or early April, Merkey gave to Microsoft the Wolf Mountain architecture which he was developing at Novell, having renamed it Tapestry. Novell had spent millions of dollars and almost two years of research and development before Merkey pirated this technology. While Dr. Head did not say so, Novell convincingly established that the Wolf Mountain architecture is the grand scheme or unique combination of which Dr. Head testified. Major also conceded that this architecture, at least as set forth in the Wolf Mountain Architectural Overview, is Novell's confidential information. What he fails to add, however, is that Merkey pirated that architecture in his Tapestry effort.

When Merkey disclosed this architecture he not only violated his confidentiality agreements with Novell, he trafficked upon the trade secrets of Novell. And thereafter he claimed in web site statements and to the media that he was building a product based upon the same Tapestry architecture. Merkey violated Novell's trade secret rights in its unique combination represented by the Wolf Mountain architecture. Novell is irreparably harmed by this disclosure.

This same analysis also supports a finding that the UFOD and CICP are Novell trade secrets. Even Dr. Head concedes that one of the most significant innovations in the Wolf Mountain technology is the Unified File Object Directory (UFOD). Major was the principal architect of this portion of the technology. UFOD provides integrated directory services, file services and data storage. And, interestingly, UFOD largely is built upon known technologies, many of which are close relatives to main frame storage models used by IBM in its main frame systems. Any computer program seeking to accomplish what the UFOD was designed to accomplish would have common parts: memory caching, disk caching, a hierarchical storage manager, and would use well known techniques such as disk mirroring, segmenting, scatter- gather, and mini-volumes as the primary unit of data storage, caching, replication and distribution. Dr. Head asserted that all of these component parts are well known in the industry. At the same time, however, I accept Dr. Ivie's analysis that in its form, UFOD is a unique combination of mostly known technologies which, under Muna, qualifies for trade secret status and protection. Major himself conceded that UFOD was unique and proprietary to Novell. While Novell did not really explain all of the nuts and bolts of the UFOD, it is composed of many parts which Major conceded were trade secrets, such as how it was designed to do self journaling, the memory management system and the UFOD message format protocol. Each of these are protectable. And it is clear that the bulk of TRG's present effort is directed at an NT based implementation of a storage manager like that which Major built in the UFOD. TRG thus is using, at least indirectly the Novell UFOD work product.

Similarly, I find that the Cluster Interconnect Protocol (CICP) deserves separate mention. The purpose of the CICP is to provide a computer communications subsystem for the various computers functioning together as a cluster. The CICP is built of many common parts. But how Novell built its CICP, how it arranged these mostly public domain concepts and technologies, is a unique and protectable secret. Under Merkey's examination Major admitted that the CICP wire protocol is a trade secret.

Novell wants me to restrain defendants from using its trade secrets. I don't fault the request, but I struggle to make an identification sufficient that I can issue a restraint. I am persuaded that it is likely Novell has other trade secrets within UFOD, CICP and other elements of the Wolf Mountain technologies. But at this point I stumble. Though I spent considerable effort digging through the huge body of information which was introduced at trial, I have been unable fully to understand and to catalogue the rest of Novell's alleged trade secrets. To that degree Novell has failed in meeting its burden. Perhaps not because, as defendants claim, no trade secrets exist, but because the matters are so complex and technologically numbing that they escape comprehension by the court. ⁹ Nonetheless, what the court cannot understand and segregate into identifiable bundles, it cannot restrain defendants from using. I deny the remainder of Novell's trade secret claims.

The threatened harm to Novell outweighs the potential damage to defendants.

Novell brought this action believing defendants breached their contractual obligations when they took from Novell confidential technical information and trade secrets. Novell has sustained that burden and has established that defendants have no legal entitlement to this information and trade secrets and that defendants have misappropriated Novell technologies.

The computer industry is highly competitive and dynamic. Today's industry leaders must be forward thinking and innovative if they are to retain their niche in the industry. To that end Novell expended millions of dollars in developing its Wolf Mountain technologies. While it is true that even to date Novell has not developed a stand alone, Wolf Mountain-based product, it now is beginning to implement aspects and technologies developed in the Wolf Mountain project into its other products. ¹⁰ Novell will suffer significant loss if defendants are allowed to take and use these technologies with impunity.

First, there is a point to be made with its own employees. Novell is able to succeed in the software development business by requiring its computer software engineers to respect Novell's ownership of its confidential technical information and trade secrets. Now, if Novell accedes to Merkey and Major without objection, former senior computer scientists who took and are using its technical information, Novell's other employees will presume that with impunity, they may take and use for themselves the trade secrets and confidential technical information which Novell has spent millions and millions of dollars developing. This is a damage which money alone never can remedy.

Second, the computer industry is extremely competitive and dynamic. A company either must be progressive and innovative or it will soon find itself on the scrap heap. At Brainshare Merkey touted the Wolf Mountain technologies as the next generation of computer communication software. In other settings he asserted that Novell had a two year head start on any of the competition in this new, exciting technology. Now Merkey complains that Novell is not building a stand- alone, Wolf Mountain-based project and thus its confidential information need not be protected.

While it appears true that Novell has not implemented such a product, it is using the Wolf Mountain technologies in other ways in its existing products and likely will continue to do so as it upgrades and replaces its existing technologies. It will suffer damage if Merkey and Major are allowed to continue to use and build upon the two year lead which Novell has gained.

While Novell will suffer great harm if defendants are allowed to use the confidential information which they wrongfully took from Novell, where defendants have no legal claim to Novell's technologies and proprietary information, they are hard pressed to claim that they should be permitted to use that which they unlawfully took from Novell. Because they do not have a legal basis to use Novell's confidential information, the threat to Novell if defendants use this information and technology clearly outweighs any risk to defendants. See Autoski11 v. National Educ. Support Sys., Inc., 994 F.2d 1476, 1498 (10th Cir. 1993).

The proposed injunction is not adverse to the public interest.

As demonstrated by Utah's adoption of the Uniform Trade Secrets Act, Utah Code Ann. ¶ 13-24-3, et seq., public policy supports the development of new technologies by authorizing injunctive protection of trade secrets. Defendants have no claim that the proposed injunction would be adverse to the public interest.

Novell has a substantial likelihood of prevailing on the merits.

Novell has presented a compelling case that defendants misappropriated trade secrets, violated their contractual obligations of confidentiality, and breached their fiduciary duties to their former employer. Defendants have demonstrated a predatory intent and a deliberate strategy to claim and use as their own, technologies which they developed while at Novell. To a large extent their actions have been in bad faith. While counsel claimed in argument that Merkey was "crying out in pain", in fact, he was a predator seeking to bamboozle Novell into letting him leave with technologies which Novell spent millions of dollars developing. While Novell yet has a judicial education project ahead of it before it will fully persuade the court concerning all of its alleged trade secrets, it has more than amply demonstrated defendants' breaches and misappropriations. It has a substantial likelihood of prevailing on the merits of many of its claims.

Doctrine of inevitable disclosure.

Finally, a word about the doctrine of inevitable disclosure which Novell urges that I adopt but defendants just as vigorously urge that I reject.

The doctrine of inevitable disclosure is based upon the notion that sometimes a departing employee may have such extensive knowledge of and experience with the former employer's trade secrets that, given the employee's new job function, it is inevitable that he will use or encroach upon the former employer's trade secrets. The use of this doctrine negates any requirement to find an actual or threatened misappropriation.

No Utah appellate court has considered, and thus no Utah appellate court has either adopted or rejected the application of this doctrine. I treat the matter as a case of first impression.

In 1989 Utah adopted the Utah Uniform Trade Secret Act. ¹¹ Section 13- 24-3 of the Act provides that "actual or threatened misappropriations may be enjoined". Further, Rule 65A of the Utah Rules of Civil Procedure, which establishes the requirements for a preliminary injunction, also speaks of a "threatened injury". In short, both the Act and Rule 65A allow injunctive relief whether a misappropriation actually occurs or only is threatened. The doctrine of inevitability is used to show that the probability of a threatened injury or misappropriation is so high that it becomes "inevitable." It is not, therefore, a separate basis for action, but rather is used to establish the existence of a threat of misappropriation.

Like many other states, Utah his adopted the Uniform Trade Secret Act. Many of the states which have done so also have applied the doctrine of inevitable disclosure in cases in which there is a question of whether there is a threatened misappropriation.¹²

In PepsiCo, Inc. v. Redmond, 54 F.3d 1262, 1269 (7th Cir. 1995) the Seventh Circuit found that a former employee could be enjoined from working in a specific field of work if the "new employment will inevitably lead him to rely on the [former employer's] trade secrets." The Court found that the "threatened misappropriation" provision of the Uniform Trade Secret Act was bolstered by the use of the doctrine of inevitable disclosure.

The federal district court of Minnesota, applying both California and Minnesota law, stated that if a former employee retained trade secret documents from a former employer, an inference of intent to use such information was found, evidencing a "high degree of probability of inevitable disclosure." ¹³ In the recent case of DoubleClick Inc. v. Henderson, 11/12/97 NYLJ 26 (col.5), the court noted that:

Injunctive relief may issue where a former employer's new job function will inevitable lead her to rely on trade secrets belonging to a former employer. In Lumex Inc. v. Highsmith (919 F. Supp. 624 [EDNY]) the court granted an injunction preventing a management representative from working with a competitor of plaintiff. The court held that the former employee would likely disclose plaintiff's trade secrets "to aid his new employer and his own future. . . . [Defendant] was privy to the top secret Cybex product, business and financial information. He cannot eradicate these secrets from his mind." (Id. at 631; PepsiCo, Inc. v. Redmond, 54 F.3d 1262, 1269 [ 35 USPQ2d 1010 ].) In the instant case it appears to the court that the defendants will inevitably use DoubleClick's trade secrets. Like the executive in Lumex, the centrality of Henderson and Dickey in DoubleClick's operations makes it unlikely that they could "eradicate [DoubleClick's] secrets from [their] mind." (Lumex, supra, 919 F. Supp. at 631.) Moreover, the actual use of DoubleClick's trade secrets described above, and other actions discussed below, demonstrate defendants' cavalier attitude toward their duties to their former employer. This gives rise to a reasonable inference that they would use DoubleClick's confidential information against it.

Though no Utah court has resolved whether the doctrine of inevitable disclosure should apply in Utah, this case is an excellent example of why it should.

First, Merkey and Major were two of the principle inventors of Novell's Wolf Mountain technologies. Prior to leaving Novell each acknowledged that the Wolf Mountain technologies were of great value to Novell and had the potential to represent a paradigm shift in computer communications technology.

Through their long and intimate experience on the Wolf Mountain project Merkey and Major learned two important classes of information: what worked and what didn't. ¹⁴ While it is one thing for them to claim they will not use Novell's trade secrets, it is inconceivable to believe that if they are designing a product similar to Wolf Mountain that they ever would start down any of the blind alleys that they already know won't work. No one is going to spend money trying that which they already know will end in failure. At least as to negative knowledge, it is inevitable that Merkey and Major will not use any of the negative knowledge which they learned while at Novell and that negative knowledge gives them a considerable head start or competitive advantage as they develop competing products for the market. They should not be allowed this profit at the expense of their contractual and fiduciary obligations not to use knowledge gained while at Novell.

The pattern of conduct engaged in by Merkey and Major is telling as well.

Even before he left Novell Merkey pirated Novell's technology and shipped a copy to Microsoft. Within days of his resignation but before his actual termination date, Merkey was telling Microsoft that he was nearly ready for Microsoft's assimilation of the Tapestry (pirated) technology. With that kind of conduct overshadowing their every action, and where they have openly and regularly acknowledged that they were building upon the Tapestry architecture, it is inevitable that they will use or disclose the Novell technology. Frankly, they have essentially admitted to doing so.

Second, Doubleclick also provides a basis for the application of the doctrine because it so closely parallels the present case.

I have found that Merkey, Major, and Angus each retained trade secret documents or confidential technical information belonging to Novell after their termination of employment. Further, Merkey himself stated in a LanTimes article: "None of the intellectual property is documented. None of the patents have been filed. The only place the knowledge exists is inside [my head] and [Darren's]. None of it has been written down." Because Merkey and Major were the chief engineers of the Wolf Mountain project, their intimate acquaintance with Novell trade secrets makes it highly probable that they will disclose or use Novell's trade secrets. The fact that to a large extent the Wolf Mountain technology exists primarily in their heads further reinforces that they will inevitably use or disclose Novell's trade secrets.

Another reason stated by the court in Doubleclick for adopting the doctrine of inevitable disclosure was the cavalier attitude of defendants Henderson and Dickey towards their former employer. The court stated that this attitude "gives rise to a reasonable inference that [Henderson and Dickey] would use DoubleClick's confidential information against it." This case presents a similar circumstance. At the least, Merkey's attitude towards Novell can be characterized as "cavalier." I have chosen the adjective "predatory" which the facts of this case amply support. Although counsel argued eloquently in closing arguments that Merkey was not cavalier, but rather was "crying out in pain," the evidence establishes that Merkey intended to take from Novell its trade secret and confidential technical information and use it for himself. With such an intent, it is inevitable that he would use information gained through his employment with Novell for his own profit.

If I invoke the doctrine I may treat the foregoing actions of defendants' as creating an inference that they intended to use Novell's confidential technical information -- that their use of the information is inevitable. Such a conclusion is entirely appropriate in this case. In my mind there is no question that there is a high probability that defendants will use or disclose Novell's trade secrets. I am fully satisfied that but for the interposition of this lawsuit, they already would have made good on their intent to capitalize on the technologies which they wrongfully took from Novell. ¹⁵

An injunction is an appropriate remedy.

Given the factual findings and my conclusion on the legal application of those facts, I am convinced that Novell has met the requirements for entry of a preliminary injunction in this matter, meaning an injunction which will control the parties as they proceed through the remaining phases of this lawsuit. What remains is to define the scope and breadth of the injunction.

I have found that it is inevitable that defendants will traffic upon Novell's trade secrets and confidential technical information unless they are restrained from being in the same business Novell is in. By this I mean, if defendants are involved in the development of clustering technologies; file management, directory, storage and routing systems; or cluster interconnect communications systems; they will inevitably use Novell's intellectual property. That I will not allow.

Yet, by design defendants were not bound not to compete. As former employees they are free to go to work for any of Novell's competitors or to found a competing business themselves. ¹⁶ All they cannot do is benefit from their knowledge of Novell's intellectual property. Further, they need to be able to support themselves and their families and their expertise is in computer software development. Keeping them from software development would be like prohibiting counsel from practicing law. What else are they to do?

The answer for the lawyer is that he or she could leave a law firm and still have opportunities for employment in governmental or corporate law offices. Similarly, there are computer software developers who are busy in the industry but are not deeply involved in clustering; in file management, directory, routing and storage systems; or in cluster interconnect communications systems. That is where these men will need to go. True Major convincingly explained that his knowledge base is in file management and storage systems. But the facts of this case are just too compelling. Defendants cannot be allowed to remain in the same field as Novell's Wolf Mountain project without inevitably encroaching on the knowledge which they gained in a fiduciary capacity while at Novell.

Finally, I am not prepared to make this injunction permanent. It must have an end. This is a fluid industry, with new developments coming at lighting speed. The delay of only several months to a year may consign a project to second or third class status. Thus, while an injunction is altogether appropriate, it should not last forever.

When they first established TRG, defendants asserted that within nine months they would have a product on the market. A considerable time has passed since then as we have worked through the legal steps giving rise to this ruling and they keep pushing back the date upon which they will have a product ready, in large part because of the serious mental and resource drain which this litigation has created. They still are nearly as far away from shipping a product now as they claimed in May 1997. Given the fluidity of the industry and of Novell's place in the market, a restraint of nine months from the entry of this ruling is appropriate. ¹⁷ I therefore conclude that for nine more months defendants must be restrained from using any of Novell's trade secrets or confidential technical information and from engaging in any software development in the areas of clustering; file management, directory, storage and routing systems; or clustering interconnect communications system. If during that time they seek employment with any new employer, they must advise that new employer of the restrictions contained in this ruling and injunction. But because the marketplace changes so rapidly, this preliminary injunction will expire nine months after the entry of this ruling and defendants will be free to reenter any of the areas as to which this restraint is issued. By then Novell will have had a year and a half of restraint upon defendants within which Novell can develop, perfect and capitalize upon its Wolf Mountain technologies. Given the degree of completion which was evident at Brainshare, when a 12-node cluster operated, that is an appropriate and ample time for it to bring its technologies to fruition.

Pursuant to Rule 4-504, Utah Code of Judicial Administration, Novell's counsel is directed to prepare an appropriate order.

Dated this 30 day of January, 1998.

BY THE COURT:

_____[signature]_____
ANTHONY W> SCHOFIELD, JUDGE

[Seal of the Court]

¹ I express sincere appreciation to able counsel in this case who exemplified in their skill and demeanor in court what is right and good about the legal profession. Their diligence and even their occasional humor and sarcasm were remarkable.

² At the same time he was telling Microsoft of his proposed Tapestry document, Merkey also told the world the same thing by announcements placed on the TRG website, announcements which clearly described just the kind of work which he was doing while at Novell and which he simply intended to continue doing at TRG.

³The whole brouhaha about the laptop computer also demonstrates Merkey's malicious intent. When he returned the laptop the hard drive was smashed beyond use. Bits of the hard drive itself were falling from the broken hard drive case when inspected by the court. The only reasonable inference from Merkey's actions is that he knew that even if he deleted the information from the hard drive, a skilled computer expert could reconstruct what had been stored there. To prevent Novell seeing that he had stored important Novell confidential technical information, he smashed the hard drive beyond use.

⁴ In an early, preliminary ruling in this case I noted that defendants are not bound by any non-competition agreements with Novell. They have a right to compete with Novell, and they can compete with the "in-your-face" attitude which they repeatedly demonstrated throughout these proceedings. That still is a correct statement of their rights. But their right to compete is limited by their contractual obligations not to use for themselves or disclose to others any of Novell's confidential technical information. They have breached those obligations. Any competition built upon or arising out of that breach must be restrained.

⁵ Utah Code Ann. ¶ 13-24-3.

⁶ Anyone studying this analysis need know that I do not pretend to be a computer wunderkind. While I use a computer on a daily basis and can make my way around a good many programs with reasonable facility, I have undertaken my study of the trade secret issue as one versed in the social sciences, not computer science. Nonetheless, I have been greatly aided in this study by the significant assistance which the two experts brought to the table. Each has extensive experience in the computer sciences and from them I learned sufficient to understand most of the issues needed to address the legal issues before the court.

⁷ " [u]pon termination of his employment, an employee has the prerogative to use his general knowledge, experience, memory and skill, however gained, provided he does not use, disclose, or impinge upon any of the secret processes or business secrets of his former employer. Muna, supra, at 697.

⁸ For a moment let me address three of defendants' primary defenses to Novell's trade secret claims.

First, defendants claim that neither the UFOD or CICP is a trade secret because they are not fully documented in code. To be protectable, a trade secret need not be fully complete in either development or documentation. If that were so no computer company would be safe from employee pirating as the trade secrets would not be protectable until a final product is complete. This is not reasonable policy nor is it the law.

Second, defendants claim that neither UFOD or CICP is a trade secret because neither has independent value. This argument is simply wrong. True, neither is or was intended to be a stand alone product. In an analysis that became less and less persuasive the longer he persisted in its explication, Dr. Head asserted that component parts of a software program cannot be a trade secret. The argument makes no sense in the real world in which both Novell and TRG are working and competing. The component parts do have independent value and can be readily transferred to other programs and uses, often with minimal reworking.

Third, defendants assert that Novell did not protect its trade secrets because it disclosed these secrets at Brainshare and Compaq's Innovate conference or did not take reasonable efforts to protect their secrecy. This is not correct. It is true that without authorization Merkey distributed copies of the Wolf Mountain architectural overview at Brainshare. He cannot violate Novell's rules on what he was allowed to distribute and thereafter claim that Novell disclosed the trade secrets so they no longer qualify for trade secret protection. That is exactly what he did in this case. I am persuaded Novell's protective steps were reasonable under the circumstances.

⁹ Having spent many days in hearing and then studying the claims of Novell and its expert, I suppose I am too obtuse to understand what was presented. Early on defendants asked that I appoint a special master to assist the court in understanding the technology. Novell objected. Maybe Novell would have been better served in this case had I made such an appointment.

¹⁰ Early on in this case, consistent with Merkey's own excited pronouncements, Novell convinced this court that Wolf Mountain represented a new paradigm shift in computer communication technology. Instead of a server hosting many computers in a networking model, the many computers can be interconnected not only to accomplish what networking did, but to provide significantly enhanced computing power. Novell now has abandoned that plan and paradigm shift. Obviously it has a business plan which gives direction to its actions. While I understand and can explain why it may have done so, it seems just a little ironic that Novell has spent so much money in pursing the protection of technologies that to a large extent it has chosen not to use.

¹¹ Utah Code Ann. Sections 13-24-1 et seq.

¹² Illinois, PepsiCo, Inc. v. Redmond, 54 F.3d 1262 (7th Cir. 1995); Iowa, Uncle B's Bakery, Inc. v. O'Rourke, 920 F. Supp. 1405 (N.D. Iowa 1996); Arkansas, Southwestern Energy Co. v. Eickenhorst, 955 F. Supp. 1078 (W.D. Ark. 1997); Minnesota and California, Surgidev Corp. v. Eye Technology, Inc., 648 F. Supp. 661 (D. Minn. 1986). Furthermore, states which have not adopted the Act also have applied the doctrine of inevitable disclosure. New York, Integrated Cash Mgmt. Serv., Inc. v. Digital Transactions, Inc., 732 F. Supp. 370 (S.D.N.Y. 1989); New Jersey, National Starch & Chem. Corp. v. Parker Chem. Corp., 530 A.2d 31 (N.J. Super. Ct. 1987); Texas, Williams v. Compressor Engineering Corp., 704 S.W.2d 469 (Tex. Civ. App. 1986); Pennsylvania, Air Products and Chem. Inc. v. Johnson, 442 A.2d 1114 (Pa. Super. Ct. 1982); Ohio, Emery Indus., Inc. v. Cottier, 202 U.S.P.Q. 829 (S.D. Ohio 1978); Delaware, American Totalisator Sys., Inc. v. Automatic Totalisators (USA) Ltd., 1978 WL 4479 (Del. Ch. 1978); Michigan, Allis-Chalmers Mfg. Co. v. Continental Aviation and Engineering Corp., 255 F. Supp. 645 (E.D. Mich. 1966); Florida, Fountain v. Hudson Cush-N-Foam, 122 So.2d 232 (Fla. App. Ct. 1960).

¹³ Surgidev Corp. v. Eye Technology, Inc., 648 F. Supp. 661, 695 (D. Minn. 1986).

¹⁴ This latter class is referred to throughout these proceedings as negative knowledge. It represents the many, many times when, in the course of their software development, Merkey and the other software engineers considered an approach to a problem, tried it and discovered it didn't work. With considerable regularity they would start down such a blind alley, only to reach a dead end and have to start over. This negative knowledge was gained at considerable expense to Novell.

¹⁵ I am aware Novell believes that defendants are using and capitalizing upon Novell's technologies. What I intend is to prevent any further success by defendants in that scheme.

¹⁶ As noted elsewhere, this last opportunity is limited by the terms of the March 18, 1997 agreement between Merkey, Major and Novell. Yet even that agreement cannot be deemed to have an unlimited duration.

¹⁷ This is a strong and seemingly harsh result. After hearing the evidence in this case I engaged in a private debate, seeking to find an equitable result that would be more toward the middle of the road, maybe one that would provide a sufficient foundation for settlement of this tremendously costly disagreement. Heavens knows these parties all need to put this matter behind them and move on to matters which develop income rather than drain resources. But as I studied the evidence I have been drawn inexorably to these conclusions. Harsh though they may seem, in honest sincerity I am convinced they are appropriate.