zap unwanted resurrection

Is there a convenient way to stop Zap from coming back after it is quit? Short of a reboot I can’t seem to get rid of it. It sets a shedload of system variables which keep it alive in the background. I have tried unsetting some of these but with limited success.
It is a problem when Zap grabs a file for which I have a personalised StrongED mode or it grabs an OLE editor request.
I can’t see an easy solution.

This is from long ago but Zap has a KillEditor tool which means it grabs, persistently, more than one might like. My first choice is StrongED but Zap can have other ideas.

This is my ZapUser.Config.!ZapBoot file which may help.

| !ZapBoot - executed when Zap is first seen by the filer
| $Id: !ZapBoot,feb,v 1.2 2001/12/13 18:49:50 ds Exp $

| Make Zap pirate previously claimed filetypes
| Obey ZapCode:Config.KillEditor

| Setup
Set Alias$ZapSet Set Alias$Zap%%0Type IfVarSet %%1Type_%%%%0 Then Else Set %%1Type_%%%%0 %%*2

| Claim file type(s) only if not yet claimed
ZapSet Run Alias$@Run Run ZapCode:ZapRunFile |%|%|*0

ZapRunType FFF

| Claim external edits only if not yet claimed
ZapSet Edit Alias$@Edit Run <Zap$Dir>.!Run

ZapEditType FFF

| Claim linked and embedded objects only if not yet claimed
| ZapSet OLE OLEServer$ -N Zap -R /<Zap$Dir>

|ZapOLEType FFD
| ZapOLEType FFF

It does what I want it to do, which is to keep StrongED as the primary Editor after itinerant use of Zap. HTH.

It does what I want it to do, which is to keep StrongED as the primary Editor after itinerant use of Zap. 

Thanks David, that is just the ticket.