© 2026 Zoe. All rights reserved.
Zoe is a legal information platform. Always consult the Federal Register of Legislation for authoritative text.
[1999] VSC 290
Supreme Court of Victoria
1999-08-17
Hansen J.
Original judgment source is linked above.
Civic Transport Services Pty. Ltd. v Wacher Pty. Ltd.
CONTRACT - Computer software support agreement - Sale of business - Novation of support agreement - Assignment of obligations of provider under support agreement - Whether fresh agreement by purchaser to provide software support. CONTRACT - To install and test customised software on replacement computer - Continuing problems in use - Whether request for on-going work made under agreement to install and test or under software support agreement - Whether request made to and work done by vendor or purchaser of business. TORT - Duty of care - Loss of customised software - Purchaser of business - Duty to warn - Correct tape size for back-up - Retain copy of customised software - Contributory negligence - Volenti non fit injuria. ESTOPPEL - Anshun estoppel - Prior proceeding between vendor of business and present plaintiff for cost of installing and testing computer software - Present plaintiff now sues purchaser of business for damages for loss suffered following loss of software.
Carry is a special purpose integrated system for courier businesses. Carry automates the booking of jobs, placing orders with drivers, notification to drivers of bookings made as well as preparation of customer invoices and statements. Carry also has extensive reporting features, including a debtors system, which can be used to assist in the efficient management of a courier business. Carry also has built in administrative tools which allow even a novice user to perform required system administration tasks including back-up, archiving and storage of user data, creation of new system users, change of system date, start of day and end of day procedures. The user simply follows the screen prompts displayed by Carry to perform those functions.
With standard support users have access to our support team for advice on the use of the application systems listed on the front of this agreement. This advice may be provided by telephone, fax or dial-up connection to your computer. Investigation of program problems and their rectification via software change releases is also provided where the software is still classed as supportable (see Software Support section).
Advice on the use of the Unix Operating System and limited support in identifying hardware problems is also provided. Engineering support including software support for hardware problems and support for applications not covered by this agreement is only available on a time and expenses basis.
Conversion programs for file transfer from Superteam to 486
The reference to the Superteam is a reference to the Honeywell computer and the reference to the 486 is a reference to the ICL computer.
Costs of programming and systems support services to recreate Carry
Loss of profits and the opportunity to earn further profits in the period November, 1992 to December, 1996 being an amount between $1,892,492 and $3,760.219, of which the plaintiff claims
Salaries and wages of additional staff required to be employed by reason of the loss of Carry
Shannon says that he made a note of that message at the time however the note was not in evidence before me. Shannon says that he was then informed by Ms. Michelle Stocks, Civic's then office manager, that she had spoken to Cramey who had advised her that the message indicated a hardware problem and that ICL, the hardware supplier, should be contacted. Shannon says that following that conversation he telephoned Cramey to discuss the matter. During this conversation, Shannon says that Cramey told him that Civic's computer had run out of "inodes" and that the kernel of the UNIX operating system had to be reconfigured to provide more inodes.
[The error message] means that the file system /u (which contains the Carry software and data) on the hard disk of Civic's computer has run out of inodes and consequently no new files can be created in that file system on the hard disk. Unless or until the maximum allowable size of the inode list is increased by the system administrator (assuming it is not already at its absolute limit of 65488), or alternatively, some files are deleted from the file system, the message will reappear every time an attempt is made to create a new file in that file system.
The technical cause of the error message was in the opinion of the special referee as follows:
For each file in a Unix file system there is a record on disk called an inode (inode is a contraction of the term "index node"). The inode associated with any given file contains a description of the layout on disk of the data in that file and other information such as the type of the file, the file's owner, and access permissions. When a file is created, the operating system allocates a new inode to that file. When a file is erased, the operating system releases the inode that it allocated to the file when the file was created. The number of inodes available to each file system on a hard disk - and hence the maximum number of files that can reside in that file system - can be specified by the system administrator; otherwise it is set at a default value determined by the number of logical blocks allocated to the file system. When a process attempts to create a new file in a given file system, the operating system kernel tries to allocate an inode to the file being created. If the number of inodes already allocated within that file system is equal to the maximum size of the inode list for that system, the request to create a new file fails and the kernel returns an error code to the requesting process. In the present case, [the error message] indicates that a process (s5ialloc) has issued a request to the operating system kernel to allocate an inode for a new file within an EAFS file system /u (which contains the Carry programs and data), and the kernel, in attempting to satisfy the request, has found that there are no free inodes in the inode list of that file system; that is, the maximum size of the inode list, as currently configured, has already been reached. Since every file within a file system requires an entry in the inode list, the kernel's inability to create a new inode means that no new files can be created in /u.
I note that the message was recorded as such in Shannon's written notes of 6 November 1992.
NOTICE: clalloc - Out of space on EAFS dev hdl (1/42)
The special referee noted in his first report that no message signifying an "out of space" condition appears on the printed extracts of the system log which he had been given and nor was he able to find any such message in any documentation of SCO, the manufacturer of the particular version of Unix on Civic's ICL computer. Accordingly, the special referee substituted the following form of error message, as that was the form which he observed when a file system runs out of disk space:
[The error message] means that the file system /u on the hard disk of Civic's computer has no more space for the creation of new files or for the allocation of further disk blocks for expansion of existing files. Unless and until some files are deleted from the file system in order to free disk space, the message will reappear every time an attempt is made to write data to the disk within the file system.
...There is also an upper limit to the total disk space that all the files within a file system can occupy. This limit is set by the system administrator when the file system is created, using the mkfs command to specify the number of 512-byte blocks of disk to be allocated to the file system.
The [error message] indicates that a process (clalloc) has issued a request to the operating system kernel to allocate disk space for a new file or for the expansion of an existing file within the EAFS file system /u (which contains the Carry programs and data), and the kernel in attempting to satisfy the request, has found that there are no free blocks of disk space available to meet the request.
Not necessarily. There appears to be at least one rare set of circumstances under which an out-of-disk-space condition on /u file system (1/42) would not be recorded in the log file.
After discussing the circumstances in which this might occur, the special referee states:
Therefore, in my opinion, my tests of November 1996 do not support the contention that an out of disk space condition did not occur in that period. On the other hand, I have seen no evidence that an out of disk space condition did occur in that period.
Q Did you have a conversation with Mr Shannon about preparing the system for your arrival?
A. Yes it is our company policy that the customer take a full complete backup of our operating system and of their data and application prior to us even touching their machine.
Shannon denied that that was what Kwan had told him, saying:
..what he said was that I had to ring the applications supplier and instruct them that there was a request to do full system backup prior to his arrival.
Counsel for Wacher submits that no explanation has been given by Civic for not calling Kwan in this proceeding and that the inference should be drawn that his evidence would apparently not have assisted Civic's case.
I was then told to contact NBS and have them do a full system backup.
Despite this note, I have some hesitation in accepting Shannon's evidence in this regard. I find that Shannon was advised by Kwan to have a back-up done before his arrival and that Shannon, as it was his practice to do, contacted Cramey to assist him in having this done.
1. Place a tape in the tape drive and log-in as root;
find . -print | fgrep -v itc | cpio -ocv | dd of=/dev/tape00
Shannon says that Cramey told him to write down the instructions, which he says he did, and to read back the command line, which he says he did. The hand-written note is in evidence before me. Cramey then told Shannon to telephone him if there were any problems
Q. Then what happened in relation to the conversation that you were having with Mr Cramey?
A. As I stated Nick was delighted. I said to Nick, "We've got to get this back up. Nick - we then discussed-"
Counsel for Wacher put it to Shannon that "is indeed what you said to Nick Cramey on that occasion and as you indeed said it to the local court on that occasion?" to which Shannon replied:
Counsel for Wacher then referred Shannon to some further evidence that he gave under cross-examination. It is an important point and I think it is necessary to set out the passage of questioning in this proceeding in full:
Then turn to 999; that is answering questions from your own barrister. If you go to 999 you will see some cross-examination about it and do you see after the objection near the top of the page:
"In your conversations with Cramey, didn't he say words to you that indicated to you that he believed Mr Kwan was going to do the backup?- - - Not at all
So he thought you were going to do the backup?- - - I was doing the backup."
Yes. Now, on your own without assistance, is that correct?
That you were going to do the backup? - - -Mr Cramey knew that, yes.
But that was your intention, too, you were going to do the backup? - - - It was - no, Mr Cramey instructed me to do it. I was following instructions.
No at the time you understood you were doing the backup? - - - No I was doing the backup under instructions from Mr Cramey.
So when your barrister puts your position in that question that what was happening was that you were obtaining directions from Cramey for you to do the backup, that is wrong is it? - - - Bad choice of words.
Well, is it right or is it wrong? - - -Well, I wasn't obtaining directions, I was following directions.
Yes. You see, if you had wanted Cramey to do the backup, you could have asked him to do it via the modem connection, couldn't you? - - - At the outset I asked Mr Cramey to get a full system backup.
Answer my question, will you? Your understanding at the time was that if you wanted Mr Cramey to do a backup you could have got him to do it using the modem connection? - - - Not at the time,
Yes. Your understanding at the time - I will put it again - is that if you had wanted Mr Cramey to do the backup he could have done it directly through the modem connection. That was your understanding? - - - He could have done that, that is correct, yes.
But instead of getting him to do it, you asked him for directions so that you could do the backup yourself, didn't you? - - - No that is not correct.
Counsel for Wacher submits that there is no explanation for Shannon asking for the Unix commands if he wanted Wacher to do the back-up and that the truth is that Shannon was quite prepared to do the back-up himself, as he had used Unix commands before. Counsel submits further that if Shannon did initially ask for Nucleus to do a full system back-up, he must have changed his mind and instead asked Cramey for the Unix commands to do the back-up himself.
Shannon telephoned Cramey and told him of the error message. Shannon says that Cramey asked him what size tape drive the ICL computer had. As Shannon did not know, and he says on Cramey's suggestion, although his notes of 6 November do not indicate this, he looked at the documents which had been delivered with the computer and read from a document headed "DRS Peripheral Layout", the words "CMT 320/525" to which he says Cramey responded with words to the effect "that's it, the tape drive is a 525 meg.".
Shannon crossed out the "obs=512k" from the first command line in his notes and wrote the second command after his previous notes.
(i) the /itc directory and its subdirectories did not contain more than 525 megabytes of data;
(ii) the tape that was used had a capacity of 525 megabytes;
Did Wacher have a contractual relationship or owe Civic a duty of care from 14 October 1992?
the expression "Support Contracts" shall mean and include the interest of the Vendor in the maintenance and support contracts entered into by and between the Vendor or its predecessor with the various licencees of the Software more particularly referred to in the Third Schedule hereto.
As I mentioned above, Civic is referred to in the Third Schedule to the agreement as a software licensee who is a party to a Support Contract.
The Vendor warrants that it will duly perform and discharge its obligations under the Support Contracts up to date of completion whereafter performance and discharge of the obligations thereunder shall be the responsibility of the Purchaser.
By cl.4, the date of completion is the date of signing of the agreement which is 9 October 1992.
Fees paid or payable by licensees pursuant to Support Contracts which are referable in whole or in part to periods subsequent to the date of completion shall be apportioned between the parties on completion on a daily basis and adjusted accordingly provided that in the event that the effect of such adjustment shall be a debt due by the Vendor to the Purchaser the amount of such debt shall be set off against the unpaid balance of Purchase Price due from the Purchaser to the Vendor in accordance with Clause 3(e) hereof.
In relation to this clause, I note that on 27 September 1992, Civic paid Nucleus' invoice for $2,125, being the support fee for the period 1 October 1992 to 31 December 1992.
The Purchaser acknowledges that it has made its own enquiries in relation to the Support Contracts and has satisfied itself entirely as to the terms and conditions and the validity and enforceability thereof AND subject only to the provisions of Clause 11 and to the warranty of the Vendor in Clause 16 hereof the Purchaser acknowledges and agrees that on and from completion hereof the obligations of the Vendor to the several licensees thereunder shall be and become obligations of the Purchaser which the Purchaser hereby warrants and agrees fully and faithfully to carry out and perform AND subject as aforesaid the Purchaser hereby releases the Vendor from and indemnifies the Vendor against all actions claims and demands whatsoever touching on or arising under or in relation to the Support Contracts.
There will be a question of credit of Mr Shannon involved in that.
There is no question to try to maintain against such a strong tide that such notice was given.
Counsel for Wacher submits that Shannon's instructions to his lawyers to open the case on this footing were simply false and dishonest. I shall deal with this submission below when I come to deal with Shannon's evidence about the alleged novation.
The Vendor will discharge all debts and liabilities which have been incurred by the Vendor in respect of the Business and which have not been discharged at the time of completion and will keep the Purchaser indemnified in respect thereof.
Subject to the term[s] hereof, the Vendor shall be entitled to payment of all debts owing to the Business at the time of completion and the Purchaser will promptly account to the Vendor for all payments received by it in respect thereof.
The effect of this clause is that Nucleus was entitled to amounts payable to the business at the time of completion and subsequently paid. The amount payable by Civic under the 29 June 1992 agreement is an example of such an entitlement. At completion Civic had made no payment under that agreement. But Nucleus remained entitled to any such payment and thus was able to sue Civic in debt in reliance on the June agreement in the proceeding which it commenced in the Local Court of New South Wales on 3 December 1992.
The Vendor shall terminate the employment of all of its employees with effect from the date of completion and pay to each such employee the amount due to him or her for wages and holiday pay as at that date AND so far as the Vendor is concerned the Purchaser shall be at liberty to re-employ all or any of such employees.
The contents of this letter are consistent with the terms of cl. 20 of the agreement and the details in the termination pay advice for Cramey which states his commencement date as 12 October 1992 and termination date as 25 December 1992. Nevertheless, this does not mean that Nucleus was not run as an arm's length operation and using the name of Nucleus, as Whiteley states. Moreover, external indicia such as the continued use of Nucleus letterhead indicate that was the case.
We have much satisfaction in announcing that Nucleus Business Systems Pty Ltd has become a strategic part of the Wacher Group, Australia's longest established computer software company.
I find in fact that the former Nucleus employees became employees of Wacher from 12 October 1992 and that Whiteley became an employee at some time earlier than this, although the exact date is not clear. I should also record that I found Whiteley, regarding his evidence overall, to be an honest and reliable witness. In particular I preferred his evidence to that given by Shannon where there was conflict.
It is, I think, quite clear that neither at law nor in equity could the burden of a contract be shifted off the shoulders of a contractor on to those of another without the consent of the contractee. A debtor cannot relieve himself of his liability to his creditor by assigning the burden of the obligation to somebody else: this can only be brought about by the consent of all three, and involves release of the original debtor.
As I noted above, counsel for Civic, quite sensibly, abandoned the alternative plea of assignment in his closing address.
Reduced to its simplest form, a novation is merely a contract between three parties, the obligee, the original obligor, and the substituted obligor, the effect of which contract is that in consideration of the obligee releasing the original obligor from his obligation, the substituted obligor promises the obligee that he will assume responsibility for the performance of the obligation. Being, in essence, but a contract - albeit, perhaps, a special type of contract - a novation, to be effective in law, must exhibit the usual phenomena of contract, that is offer and acceptance, the fact of acceptance being communicated to the offeror unless communication has been expressly or impliedly dispensed with.
A purported novation will fail for want of consideration if the intention that the original obligor's obligations are to be extinguished is not made clear ( Lyth v Ault and Wood [1852] EngR 562; (1852) 7 Exch 669; 155 ER 117).
The Wacher Transport Division will continue to aggressively market the CARRY Transport Solution and, with access to further resources, give an even greater level of support. CARRY will continue to be enhanced to ensure that it meets your current and future requirements. . . All of our key experienced people remain with the company, including James Taylor, who will manage our Sales Operation. We retain our proud reputation of personal support . . . nothing whatsoever will change in that regard!
WACHER PTY LIMITED is delighted to have had the opportunity to acquire Nucleus Business Systems Pty Ltd. The acquisition is a strategic addition to our Transport Division.
The CARRY product will be a significant component of our Transport Division . . . We have appointed Mr. Vic Whiteley as Manager of our Transport Division. All Nucleus staff will be retained. Ongoing support arrangements remain unchanged.
I should note that counsel for Civic submits that insofar as the letters suggest that Wacher has acquired the company "Nucleus Business Systems Pty Ltd" they are misleading and wrong.
(f) Cramey failed to take any, or any sufficient, steps to ensure that magnetic tapes used by Shannon to make a back-up copy of Unix and the application systems (including Carry) were of sufficient size to contain a copy of all of Unix and the application systems (including Carry).
(g) Without any, or any sufficient, justification therefor Cramey wrongly assumed that the tapes used by Shannon to make a back-up copy of Unix and the application systems (including Carry) were of sufficient size to contain a copy of all of Unix and the application systems (including Carry).
(h) Cramey failed to advise Shannon properly, or at all, in respect to messages which were, or might be, displayed on Civic's computer during the back-up which would indicate that the magnetic tape was full such that the back-up copy would, or could be, incomplete.
All business computer systems need regular attention to be given to housekeeping operations such as backingup, removing redundant files, tuning the system for optimum performance, checking the integrity of files, and similar tasks. If no attention is paid to these tasks, then loss of data and an inefficient system, possibly an inoperable one, are inevitable. It is good practice to make one person responsible for performing or supervising these tasks, and such a person is usually designated the `System Administrator'. The fact that the SCO Unix System Administrator's Guide [1] is 744 pages long and the SCO System Administrator's Reference Manual [18] is 706 pages long strongly suggests that system administration is not a trivial task and that it cannot be left to take care of itself. Although most system administration tasks are not especially difficult, they are certainly not intuitive, particularly on a Unix system. There are vast opportunities for making disastrous mistakes. Consequently, a person carrying out a system administrator's tasks, whether or not she or he is formally designated as system administrator, must have adequate up-to-date information relating specifically to the version of Unix in use.
The answer seems to be - persons who are so closely and directly affected by my act that I ought reasonably to have them in contemplation as being so affected when I am directing my mind to the acts or omissions which are called in question.
Attention has been drawn to the fact that Lord Atkin's definition refers to a person affected "by my act", not my omission; see Sutherland Shire Council v Heyman [1985] HCA 41; [1984-1985] 157 CLR 424 at 477 - 478 per Brennan J, a case in which the High Court emphasised the distinction between causing something to happen and failing to prevent it from happening (see 443 - 446 per Gibbs CJ, 477 - 479 per Brennan J and 502 per Deane J). Deane J described the distinction as fundamental.
Civic Transport Services Pty Ltd
Wacher Pty Ltd [1999] VSC 290
(1981) 147 CLR 589
(1959) 101 CLR 298
(1976) 1 NSWLR 191
(1983) 1 IPR 315
(1970) 119 CLR 435
(1982) 160 CLR 1
(1984) 156 CLR 41