29LV040 is a 4 megabit (512 KB) chip, so it's definitely conceivable that the ROM is actually bigger than 128 KB. (Does it really say 29LV0400? I can't find many references to that, but plenty to 29LV040)
In particular, this is probably the datasheet for the chip you have:
http://www.100y.com.tw/pdf_file/MX29LV040QC-70.pdf
or this:
http://www.zlgmcu.com/mxic/pdf/NOR_Flash_b/MX29LV040C_DS_EN.pdf
Weird that the Windows flasher is acting like it succeeds, not much I can really do in that case then. The only other thing I can think of is maybe we could patch the WeibeTech flasher to recognize that particular flash chip...flash chips generally always talk using the same JEDEC protocol, so it's kind of interesting that they limit it to only work with certain chips. You can read a manufacturer and a chip ID from most flash chips, so that might be what it's restricting itself based on.
In particular this chip identifies itself as manufacturer 0xC2 and device 0x4F.
In particular, this is probably the datasheet for the chip you have:
http://www.100y.com.tw/pdf_file/MX29LV040QC-70.pdf
or this:
http://www.zlgmcu.com/mxic/pdf/NOR_Flash_b/MX29LV040C_DS_EN.pdf
Weird that the Windows flasher is acting like it succeeds, not much I can really do in that case then. The only other thing I can think of is maybe we could patch the WeibeTech flasher to recognize that particular flash chip...flash chips generally always talk using the same JEDEC protocol, so it's kind of interesting that they limit it to only work with certain chips. You can read a manufacturer and a chip ID from most flash chips, so that might be what it's restricting itself based on.
In particular this chip identifies itself as manufacturer 0xC2 and device 0x4F.