Hello all again,

Thanks very much for help with my problems. I am sorry it has taken so
long to respond, but I have been trying out your suggestions.

The first problem, the length of time to stop D3 was completely solved
by a restore, it now takes just over a minute.

The second problem remains. The machine is stand alone, so I am only
allowed one user (and only need one user) and when the one user can
sign on there are no performance problems. BUT, when I close down the
system (using D3tray), D3 appears to stop normally: the next morning
when I start D3 again using D3tray, it appears to start normally, but
when I try to logon it does not let me saying that "too many users are
logged on". If I then try to stop D3 the D3tray flashes for ever i.e.
it does not stop. I have found a way round this by 1) ending D3vme
(Task Manager - end process), 2) copying a saved version of the D3
folder to the D3 folder, 3) doing a restore, which, when it has
finished, brings up the logon prompt, 4) sign on to SYSPROG and
shutdown, which finishes normally 5) D3tray will now bring up the
system and I can work normally and D3tray appears to stop D3 normally:
until tomorrow morning when again I get "too many users" again. .

I have done nothing about the third question! Ross Ferris suggested

"So, you change the name of your "one and only" MDS server computer
.....
was this reflected with a change to the D3 config? (nor sure if this is
necessary) "

but I do not know how to do that. Is it possible that the change of
computer name could have caused the problem?

I have asked that the computer name be reverted to the old one, but
that involve lots of red tape, and any way I don't realy want to be
beaten.

Thanks again for any help,

All the best,

Chris Potts

Chris - excuse me in advance, but on our D3 system, I must logto dm, then
issue a shutdown command. Then when the service stops, I can shutdown or
reboot windows.
Am I missing something here?
Tom

"chrisjpotts" <chrisjpotts (AT) orobanche (DOT) co.uk> wrote

Tom Phillips wrote:
Hello Tom,

I think that that is what D3tray does, but with the advantage that
widows cannot be shutdown without first shutting D3, but it would be
interesting to see if doing it your way makes any difference. The
system is twenty miles away, so I will have to wait to try it.

How do you start your D3 after you have started widows?


Thanks for your help,

All the best,

Chris Potts

Chris - the D3 service is setup to start when the system boots.
Tom.

"chrisjpotts" <chrisjpotts (AT) orobanche (DOT) co.uk> wrote

Tom Phillips wrote:

Hello again Tom,

Thanks, when your mail arrived I was away doing just that, and the
problem is solved.

I downloaded a version of D3tray, a much newer one than the one I have
used for years, and it must have been that which was not correctly
shutting down D3. Anyway all is well now, my system comes up OK and
shuts down again OK. The user does a filesave before finishing each
night which I execute from a Databasic program, and all I have done is
execute a shutdown after the save in the same program. All is fine,
and nothing to do with changing the computer name, which is another
bonus. I have consigned D3tray to the recycle bin.

Thanks again for your and everyone else's help, my three problems are
solved.

All the best,

Chris Potts

Chris:

Do not use D3Tray to shut down D3. Shut down D3 from inside D3, at TCL.
It's best to log into the "DM" account and enter "SHUTDOWN". This will
properly shutdown D3 and disconnect from the VME.

D3Tray has not been updated for quite a number of years and shouldn't be
used in this capacity.

Hope this helps.

Bill

"chrisjpotts" <chrisjpotts (AT) orobanche (DOT) co.uk> wrote

Bill H wrote:
Thanks Bill,

That is how I have set it up, and all seems to be well now.

All the best,

Chris Potts