Various comments on V4.2.1.0 client for windows

In my so far futile quest to find a relatively wart-less *SM client
version, I've come to the latest and greatest V4.2.1.0.  While great
improvements have been made, I find (in the windows case) ...

1. The return code problem. Already documented on this list.

2. Unable to backup Win2000. My "supported" VM 3.1.2.90 server is unable to
backup the registry/systemobject. At a time when WinXP is about to debut,
my inability to backup Win2000 without "manual" Ms backups of the registry,
is something I wish Tivoli would consider a bug or something necessary of
correction.

(Backup REG gives ANS1943E; backup Systemobject gives ANS1924E)

3. The default language for the download .EXE file is Chinese.  I have a
couple of students that probably appreciated this, but a hundred others
scrolled to "English".  To view the dialog box I'm referring to, see

      ftp://wts.unet.maine.edu/ADSM/_Dumb/

4. On (my 1st) Win2000 install, the LNKs for the GUI backup are strange or
broken (both desktop and off START button). The icon in the executable is
OK.  To view the icon I'm referring to, see

      ftp://wts.unet.maine.edu/ADSM/_Dumb/

5. APAR IC29552 "Active file not found" with some strange characters in
file names, was corrected in 4.1.2, with a DB correction program
TSMCLEAN.EXE provided to correct an infected *SM database. When I used it,
TSMCLEAN just terminates with a programming error. Perhaps my "supported"
3.1.2.90 server is confusing TSMCLEAN?

6. It's unclear why the installer leaves 77MB in "tsm_images". Is this
required for the Win Control Panel "repair", "modify" and "uninstall"
functions?  If not, I want my 77MB back; it really matters on those 1 and 2
G NT machines I still have in abundance.

7. The setup wizards are by far the best ever. However, I've watched
(cringed) as some of my client users run the backup wizard, then go back to
run the schedule wizard (causing the backup wizard to run again). More a
nit than a wart. :-)

8. The audit trail for backup and restore are still miserably and
conspicuously poor/absent. DSMERROR.LOG contains the appropriate
information, as does DSMSCHED.LOG, but ad hoc backups and all restores have
no ability to write an audit trail.  I "want" a DSMSCHED-type log that is
on by default for ad hoc backups and all restores (please).

9. Include/Exclude. "Boo!" to whomever implemented the exclude.dir.  If you
scan recent postings on ADSM-L, you'll be really confused. Trailing slash
or not, "..." or not, drive/system indicator needed or used or not,
trailing splat (*) OK or not.   I would guess the rules require no trailing
"/" and/or "*", and require a filespace component, but I don't "know".

"Cheers" to a recent poster that pointed out one can test an
include/exclude list against existing files via little red "x" found in the
"Actions",  "Backup" tree view. Cool. (And cheers to the doc writers that
put lots of include/exclude examples in the online doc available with the
client download.

10. If this were a top-ten list, I'd have put something here.  Maybe you
have your own "favorite" wart?

V5 will be perfect ... I know it will.

cheers, wayne