Shouldn't be. Whilst some PAL/GAL chips have a dedicated OE input the ATF22V10C isn't one of them. As far as I can tell from the datasheet pin 13 is just a regular input. The Lattice GAL22V10 certainly does it that way.

I'd point out that another thread here is discussing similar issues with the ATF22V10C/TL866II+ combo.

If you have access to another GAL programmer I'd be interested in the results.

Pull-up and pull-down resistors don't seem to have an effect.

Changing the device name to p22v10 doesn't seem to have an effect.
I tried using GALasm instead of WinCupl, and that didn't seem to have an effect either.

Thanks for the link. I skimmed that thread before I began having my problem. I need to go back and read it again more carefully. Just glancing at it now, it looks like he may be having the exact same problem I am. His BOOTUP_OE signal is assigned to pin 13.
Unfortunately I only have the one programmer and Atmel chips. I have one Lattice PALCE22V10Q, which is not on the TL866II+ supported devices list, and all of my attempts to program it so far have failed.

I've access to the VP-290 programmer, and I've built a quick and dirty test board to check the output file from WinCUPL.

It appears to work as expected using a stock ATF22V10C-15.

The 2 Blue LEDs are connected to the A and B inputs on pins 13 and 14. The green ones to the regular outputs, and the red ones to the inverse, fed from pins 20 to 23.

The CPU board is a Grant Searle 7 chip 6502 design with an extra chip select decodes so that I can POKE 32768,x to set the LEDs. The LED's are configured to sink current so they're on when the output is low .

Martin,
Thank you for taking the time to test this. It looks like the VP-290 correctly programs the ATF22V10C.
FYI, this thread got off-topic from the original post. I think this thread seems better suited to continuing the discussion of problems programming the ATF22V10C using the TL866II+ programmer.