I am curious to know if anyone has experienced the "Registry problem"
pop-up screen from time to time on desktops running Win95?

As of last week, we were on MVS ADSM V2 level 12 server and several of our
Win95 clients occassionally experienced the "Registry problem".  This
sometimes caused the machine to freeze up and resulted in a reboot.  Other
times, users can ignore the message and go on without rebooting.  However,
in all occasions, the registry seems to be OK after each reboot (without
any corruption noticed!).  The contents of the message is as follows:

"Windows encountered an error accessing the system registry.  You should
restore the registry now and restart your computer.  If you ignore this
error and shut down your system, you may lose data.  Restoring the registry
will replace the faulty registry with a known good backup copy.  However,
this backup copy may not contain all the information recently added to your
system."
And the option give:  "Restore from Backup and Restart".....

Our users started to see the above message "from time to time" and the
messages  always associated with their scheduled backup time.  Of course,
this doesn't mean that the scheduler was the reason, since we started to
see the message during manual backup as well.

Because of the nature of the problem, and not being able to recreate it on
demand, so far it has been hard to determine whether ADSM is the reason!!!
I have opened a record with IBM and was advised to bring the server, as
well as the client code to the latest level to see whether or not the
problem will disappear.

Last weekend, 2/22, we have upgraded our MVS server to version 3 and
yesterday began to test the new version 3 Win95 client (IP21169S).  Looks
like the new client is not the answer.  Here's what we did:

Closed all applications.
Installed the new client (on top of the same directory path...the previous
dsm.opt remained in tact).  By the way, we used TCP/IP as our commmethod.
Initiated the GUI Admin client (everything looked OK, minimized it).
Initiated the GUI client backup (selected the backup option, and started to
backup one of the local drives.
 White (4) was running, we started another GUI client backup.  We selected
the backup option and started testing the "Find file(s) to backup" using
filter list....while this was going on, the "Registry problem" screen
popped up.  At this time, the initial backup screen appeared to be working
still.  We then click on the "Registry problem", and press the CNTL+ALT+DEL
keys.  The resulting screen showed the first item selected was NETBIOS?  At
this time, we noticed that if we minimized the screen which contained the
output from the filtered selection list (the result from the second GUI
backup client), it labeled was NETBIOS next to the ADSM backup logo.  A few
seconds after that, the machine was frozen and we had to reboot.
After the reboot, we attempted to recreate the problem without any
success!!!

To sum it up:
Since we've determined that the "Registry problem" pop-up screen appeared
when ADSM was the only running application, we've more reason to believe
that ADSM was the cause.
With the above in mind, has anyone seen anything like this?


Cookie Nguyen
ARCO
cnguyen AT mail.arco DOT com