From: "Glenn Meadows" 

Yea, that's going to be a tricky one, getting the image of the old box into
a new box and running, then upgrading it to Win2K.

We'll have to plot that one a bit more, and yea, the thought has been
rumbling around in my brain that we need to do that sometime this summer, I
would think.

The key, is getting the new hardware under the running system.

--

Glenn M.
"Geo"  wrote in message
news:4252067d$1{at}w3.nls.net...
> "Glenn Meadows"  wrote in message
> news:4251b843{at}w3.nls.net...
>> For me to visit my other one, I go to Cleveland, and then out to Georges'
>> place.....or call George...
>
> Speaking of which, bout time to upgrade that box? I was thinking I could
> image the drive and you could download the image file to bring it back on
> a
> new machine, then upgrade that machine to W2K? If we did that all we'd
> have
> to do to go live would be to copy the message database and other files via
> tape backup when you were ready to put it into service.
>
> As for the blue screen problem, has that machine always had that problem
> or
> did it start after you added some new piece of hardware? It's either an
> interrupt sharing issue or a failing hard drive (or cable or controller
> but
> most likely a drive) or, and this one is a stretch but I've seen it, a
> dead
> cpu fan.
>
> Geo.
>
>

--- BBBS/NT v4.01 Flag-5