Well should i PM Andreas or just wait to see if he has time to check this out, hopefully he has time to support this wonderful hack.

I have just worked out my problem i think, im still testing it, but wanted to write down what i had done before i continue

i deleted in the uninstaller.php everywhere were it said

$DB_site->query

it was online 56 9* 114 116 etc and that alloud me to run the installer fine

now i get this message

You have completed all the automated steps of the Uninstaller.

Proceed with the rest of the modifications, described in the Uninstallations Instructions.

What are these?

I am not sure if this solves your problem. What you did, with that, is that you removed all the database changes that the uninstaller was supposed to do.

Here are the rest of the instructions


Uninstallation Instructions
===========================

Even though an Uninstaller is supplied in the zip file, there is a lot of manual work to remove this hack from your system, mainly because of the number of files and templates changed.

The Uninstaller does the following tasks:

- Remove all new templates that AWS has put into your system.
- Remove all database tables used by AWS, as well as the columns used by AWS in the standard tables.
- Remove all phrases and settings added by AWS.

What the Uninstaller does not do:

- Bring back the standard php files, to the condition they were before you applied this hack.
- Bring back the standard templates, to the condition they were before you applied this hack.

In order to remove this hack from your vB, first upload the uninstaller.php file to your admincp directory of your server and upload the install_warn directory inside your forum's root directory. Then point your browser to:

http://your.forumsite.com/admincp/uninstaller.php

Follow the steps to the end.

Please note that depending on the version you are trying to uninstall, the script might not complete all the programmed tasks. For example, if you are trying to uninstall a version which does not include all the columns in the user table, that the script tries to remove, you will get an error message. If this happens, please contact me through the hack's thread for help.

After the Uninstaller has finished its chores, you have to manually change all the templates and .php files. To do that, open the Installation instructions text file, go to STEP 2 and reverse all edits.


Gentlemen, please be careful. These instructions were for AWS 3.4.x, I am not sure if they are the same for AWS 3.5.

And yes, I would suggest someone PMs Andreas and see if he plans to work on this hack or not.

woot i just worked out how to fix the error i was getting, and so many b4 me.

I dont think what i did above, did anything lol, however i just realised that in adminphp if you edit the file settings and delete everything that has to do with the warning system then that will allow me to install the product no problem at all.

so far so good, i will update with my progress.

i now have everything working, this has been the hardest hack that I have had to install, and with the most problems, but after doing a lot of trial and error, and doing lots of backups. everything is working.

But it was well worth the effort because this hack should be standard in vbulletin IMHO.

I've checked the settings and nothing there to indicate that a user should be banned for a 2 point warning.

What is your Warnings Number Limit?

Warning Points Limit: 10
Warnings Number Limit: 20

Did you repeat that test and verified that a user gets banned with only two points?

When someone is Perm Banned, it puts them in the usergroup I specified, however it does not use that usergroups default title name, instead it just says Permanently Banned on their posts. How do I change this? Ive searched phrases and cant find a way to change it to match what that usergroup really says.

Can anyone answer my question? bump.