Is it necessary to clean codespace on Rom 102 card?

[RockyM]

Probably a dumb question, but when you unlock the card, do you need to clean codespace on the card before writing bin and blocker? Or do you only clean codespace on the bin that will be written to the card?

[Gothmog]

Probably a dumb question, but when you unlock the card, do you need to clean codespace on the card before writing bin and blocker? Or do you only clean codespace on the bin that will be written to the card?

Uisng N2edit this is what I do:

- Unlock card
- Read card
- Clean CodeSpace
- Write cleaned code space back to card
- Check REV to make sure it is REV103 or 240
- Load new BIN
- Write to card
- Check REv to make sure it is the lastest
- Attempt to read card this should fail, due to the blocker

If you clean the code space but don't write back to the card than you might as well load and save your new BIN over what ever you had.

Anyway this is how I do it and I have seen arguements over this process on other boards. I think this is deemed the safest way. You always want to write a new BIN to a Virgin REV.

[RockyM]

Sounds right, but what is the reason behind cleaning codespace on the card? For example, if you're just changing tiers and blocker on the bin, then re-writing back to the card, do you really need to clean codespace on the card?

[Gothmog]

I normally use pre-made BINS. So the Blockers, tiers, and locals are good to go. If you build your own BIN from scratch I think it is still recommended to apply to a clean REV103.

I believe N2edit is going to write the full BIN to the card even if you are just making small changes. So you should probably follow the same process.