I've neither heard of nor tried the cleanup utility from the DBA CD, so I'm not actually sure what it does.  Did you try to remove Pervasive using the Add/Remove Programs function in Windows' control panel?  If not, and it's still listed, give that a shot.  If all else fails, what I like to do is just rebuild the machine, reinstall Windows and rest of your software - just backup your files first!  HTH  

to respond #2: Yes still thinks it's there
to respond #1: Hope I dont have to do this

We did this several times. The clean utility does not remove all the registry entries for Pervasive SQL because after reboot, when attempting a clean install, the installer says that a copy of Pervasive SQL exists on the machine and only gives the option to repair or remove the existing installation. But there is no existing installation because the PVSW folder and common registry entries have already  been deleted by the clean utility.

No need to rebuild your machine
 
use Registry Mechanic. It will clean up your "bad" register entries.
 
https://www.pctools.com/registry-mechanic/
 
ciao,
 
Kelloggs

Funny... you could have had the machine fixed by now if you would have just counted your losses and rebuilt the machine as in my original response.  What does it take - two, maybe three hours tops depending on processor speed and the amount of installation software?  Seriously, there is nothing to be afraid of in performing the task, and if you are at all, just hire a professional - that's what they're there for.  Good luck!  

Sorry David, I generally agree with Dan. And a network person can do a workstation, including configuration and file reloads, generally in 3 hours. If there are a LOT of apps, maybe 5 at the outside. And if users are trained to use the MS Office "Save My Settings" wizrard and save everything to an .ops file, then one of the more onerous chores (re-storing the Office programs the way that user likes them) can also be a 5 second task of restoring from that .ops file.
 
Now assuming that Vicki is on a Server, then that is NOT a 3 hour task even for a REALLY good pro, with every install CD sitting beside the server. It IS an all day process even for a pro. But, as I said, if things like this are happening, then it points to a server install that has become unstable. And therefore should be re-built.

Well said, Lorne. However, you know what they say about assumptions...    Two key questions have not been asked or answered yet - whether it is a workstation or server that is having the (un)install problem - and what was the reason for performing the (un)install in the first place?  Then again, they are irrelevant, as the problem still exists and must be resolved regardless.
 
Yes, servers do take a bit more time to setup, but that all depends on what you are running and how much you need to configure as well. I had upgraded our server last year starting with new raw components, put them together, installed and configured the software. Was nice to have a fresh start on a much faster machine.
 
Anyway, if you go forward with the rebuild, I would recommend creating a Ghost image when you're done, and save yourself some time in the event this happens again.  Don't know if any of this is any help to you Vicki, but again, best of luck to you.