can't burn stacked bin

[psyolent]

Hey

Fired up the GQ-4X today to burn a manual vn v8 bin for him. I stacked it using TP no issues, reads up OK in HxD
I am continually embraced by fail :



Write failed, Address=0x009800, Buffer=0x26 Device=0x04

Chip is a Winbond W27C512-45Z.

Tried it a heap of times. Tried different chips. Still embraced by the fail boat.

Any ideas please? Bad chip(s)?

[Dylan]

You said VN V8, Is it 12P (256k) or an old VN BIN (128k) ?

[yoda69]

That error is normally caused by a poor erase.
Try doing just an Erase followed by a Blank Check.
Sounds like bad chips or poor contact to the ZIF

[psyolent]

dylan. original 128K bin

yoda. if i do quickly a read, erase, blank check, write. i've got it to do it. it gets to 10% slows, then, gets to 60% and hammers. like the old buffer underrun in the old CD burning days, remember that shit.
i then go back and re-read it and compare in HxD - and they are not identical.
there are a heap of 'y' in the ascii fields.

ps: i am using win10 here. just wondering ....

[yoda69]

Try changing the write speed from +2 to 0 and see if that helps.
I've also tried double write on some chips as well.
Seems strange to have it slow down and speed up, if you're running Win10 would assume computer isn't ancient.

[Dylan]

Out of interest are you stacking it 4 times? Apart from that I'm out. Id try another memcal?
I can send you one if needed might even have a 128k one here. If not I have a few EEPROM's here.

[psyolent]

yoda. yeah tried that too mate.
ok: re double write.....though as it fails you try to write again and it says to GTFO
i know.....nah i5-760 previous gen.
tried on wifes win7 laptop. same deal
dylan yah, stack x 4 using TP............16KB 64KB 16KB
i on my 2nd chip here. might take u up on that buddy

[Dylan]

Hit me up if you need to. Also I installed an update long time ago on Windows 10. Although it was working before hand anyway.

[psyolent]

dylan - re: update ---> what was it do you know?

[Dylan]

Was from there website. When you fire up there program it says checking fir updates but doesn't find any. Now that I think about it it wasn't working on Win 10 first up.