Reasons
1. The WinISP has an incomplete user interface - No save option, although when loading a hex file sometimes it saye "File Written" !

2. The autobaud thing is just damn annoying ! If it didnt go into ISP mode, or I forgot to switch the RS232 box to the board, I have to wait until it goes to 110 baud ! to decide there is no chip to talk to.

3. No support on WinISP from philips, no source, they didn't write it.

4. Each time it runs, have to select chip type and oscillator, etc.

5. I wrote my own for at89s8252, which does have a very friendly user interface, which I will be using instead of WinISP. I think the time wasted waiting for the autobaud will more than make up for the development time.

6. No error correction protocol, etc. It's not sufficient for remote programming.

7. It can't even automatically erase the blocks of the chip that the code is using.

8. Even so, WinISP is still much better than the one SST made - SST's is atrocious, using radio buttons as pushbuttons, not allowing the remap bits to be set. But NEITHER one is as good as one made by someone (ME) who actually has to use the thing on a regular basis.

9. I am not bashing it altogether - I believe it is good enough for occasional use, or for programming the chip for the first time to get my own IAP code in there. But I want something better.