Retrospectors,
I had an error this morning that I have never seen before. There
was a dialog box in front of the Retrospect window that said the
following...
Trouble in Retrospect:
Internal Consistency Check Failed:
Assertion Check at "elem.c-811"
When I clicked quit, Retrospect was st
> And for my rant. I have all the manuals of Retrospect going back to
> version 2 and I have three servers so this makes a few manuals on my
> bookshelf. Why can't Dantz label their manuals with the current
> version? All the manuals do not have version numbers for the app. The
> way I figure the
>Here's the reason: we want to minimize waste.
>
>If we printed a version number on the manuals, we'd have to toss the whole lot
>every time we did an update.
Well actually no. You can make a Manual for version 4 and not worry
about the minor updates like 4.1, 4.2, etc. Just create new manuals
I just want to say that the new driver update has made my backup machine
running Retrospect much more stable.
I used to have a 102 error at least once a week. Now, no more 102's!
Thanks Dantz!
--
Nick Scalise
[EMAIL PROTECTED]
--
--
To
Starting with 4.2, the version number is on the manual's binding.
Craig didn't mention this because I don't think he has a manual to look
at...I think he must have an illegal copy of the software. ;-)
Eric Ullman
Dantz Development
--
> From: Travis Morgan <[EMAIL PROTECTED]>
> Reply-To
At 6:10 PM -0800 on 8/1/00, Daniel O'Donnell wrote:
>Retrospect sees the client on the network (not logged in), but when
>I try to log in the client, the application errors out with -1028,
>client not on network.
I had a similar with a couple of PC's a while ago - i finally fixed
this by uni
