can't burn stacked bin

[psyolent]

yeah. thought that was driver only though for win10.
i have 6.38 of the software. finds the thing just fine no issues. well sometimes ... is mostly good.

[psyolent]

right. its only writing 16KB. even though i stack the bins ; and the file is 64KB, when you read the chip in HxD it only gets to 00001FF00 --> after that, 00002000 is dead. all 'FF' or 'y' in ASCII

[Dylan]

Just looked on my laptop I'm running 6.37. Found a VN memcal here I just put it in the eraser. Send me your BIN un stacked and I'll try and burn it.

[psyolent]

Dylan, its AFUA ; download/file.php?id=113

[Dylan]

Well that was interesting. I upgraded Windows a few days ago. Had to re install the USB driver so then decided to upgrade to 6.38.
I burnt the linked file to a 128k VN memcal. Ill attach the read back it verifies with HxD ok.

If you want it PM your address and Ill send it off Monday.

[psyolent]

ya. pretty sure these chips are fakes. all fucked.

[vn5000]

Are you using the usb lead gq4x came with , ive had similar problems with cheap shit usb leads
Does the chip id ok

[The1]

can you ID the chip? can be bad contact

[antus]

Sounds most likely to be bad chips. Hard to find good ones these days. The bad ones ive seen do exactly as describe, fast and slow patches on the chip then fail readback. Drivers etc tend to be all or nothing, not this type of failure. Electronic erase chips tend to erase reliably, unlike the uv erase style chips which can take more work (longer) and a couple of attempts to finally erase the stubborn bits.

[Dylan]

The one I burnt was an intel 128k eprom. First intel I've come across.