#PAR backup!
>> Actually, the recent uploads ARE beta versions and we who use them are the
beta testers. <<
Disagree. A proper beta program has at least three things:
1) A list of known bugs — so the testers don't spend time tracking down bugs
that are already known. (If DPS has one, nobody I know of has seen it)
2) A method of tracking bugs and bug reports. (DPS won't take a bug report
over the phone: "If you have a REPEATABLE case, you can FAX it in, and MAYBE
we'll look at it")
3) A staff committed to FIXING the bugs and working CLOSELY with the BETA
testers. (DPS has the annoying habit of attributing any problem to "a DOS
problem, etc." — whatever it is, it's never THEIR bug)
Before I started rooting around up here I made the mistake of trying to get
some help from DPS about backup problems. I was flatly told that all the
backup problems that had been reported had been traced to "incompatibilities"
in various hardware configurations, etc.. — I come up here and find out that
was a BOLD FACED LIE! The "frame >896" problem was being hotly debated. So
far I haven't found anyone who is DIRECTLY backing up a PAR drive to tape and
directly restoring it — the work-around is tape to DOS to PAR.
I started contacting DPS in with backup problems in May, and they still don't
appear to have taken OWNERSHIP of the problem!
I LITERALLY BEGGED dps to LET me work with them to resolve the backup problem.
I was told that "We have over a THOUSAND units in the field, we're JUST TOO
BUSY to do that… send us a FAX" (FAX THIS you arrogant BA$|_rd!) I've
participated in Microsoft beta tests with over 5,000 beta testers — they
weren't too busy to work out a problem with MAJOR implications for the end
users. Or maybe DPS doesn't think backup problems are worth their precious
time?
Don't misunderstand, I think the PAR hardware is wonderful, Gus Grubba did a
wonderful job with the drivers, its just the tech support that bites.
Ahh. I feel better now! (flame off)
Cal