[Previous Page ] [Main Documentation Page ] [Next Page]

Installation

Prerequisites

  1. Win98, WinMe, NT 4, Win2k
  2. VB6 OR (required list of DLLs)
  3. Access 97 or 2000 (for editing tables)

Compilation from source (optional)

Without downloading the binaries, to compile MidWatch for the first time in a working copy of the CVS tree, You should build in this order.
  1. Get the source from the CVS Repository
  2. Open midwatch\common\CommonGroup.vbg
    you will get an error that Logger.ocx could not be opened, answer no to "continue loading project". This error is caused by the test bed project CommonTest.vbp. You don't need it now.
  3. Make Wutils.dll.
  4. Make Logger.ocx.
  5. close CommonGroup.vbg
    (next time you open CommonGroup, CommonTest should not give you the error.)
  6. open midwatch\engine\EngineGroup.vbg
  7. make project group.

Install steps

  1. Compile from source (explained in previous section), or download the binaries.
  2. manually use regsvr32 to register SCMCprj.dll, Wutils.dll, and Logger.ocx.
  3. copy required DLLs (listed in prerequisites section) to c:\windows\system directory (or c:\winnt\system32, as appropriate)

Configuration

Wow, this is actually a more complicated issue that I haven't really put much thought into. Much of it is centered on the SignalBridge (the web reporting) and if you don't get it right, well you just won't have any reports, but your builds should still go through. If you can hack HTML and have some casual familiarity with your web sever (note I did not insist that you use IIS :) you should be able to figure out where to copy the images directory and allow MidWatch write privilages to the website.

A lot of the set up will be in putting the right data into the Access tables. There is no real good UI for this which is another area begging for a voluntier. I believe that for MidWatch to be shrink wrappable, one essential spec is that the user will never have any need to edit the tables by hand all of this must be done by the UI where the data can also be validated to protect other functions of MidWatch.

Ah, lets see, what other vauge, semi-usefull clues can I write here?

oh, I welcome questions via e-mail. You may send them directly to me, but I would prefer that you join the midwatch-1mc mail list and post questions there. This project is desperate for activity, and I could use some posts on the midwatch-1mc!

I got some new hardware.

On August 1st, 2000, I started loading MidWatch 0.1.33 on a new machine called GETTYSBURG.

I had installed MidWatch step by step as you would to document how to get it to work.

My notes are already in the maillist, join it! read it! comment on it!

Thanks to Dave Smith for re-writing this page and cutting out most of the BS I had written. His point to me: if it is an install page, get right to the install steps.

"Continuos improvement beats postponed perfection."  We'll get there!

[Previous Page ] [Main Documentation Page ] [Next Page]