Read error pages

[ssg]

I'm thinking of explaining read error codes in the wiki, however I'm not sure about the difference between a and b. Here's what I know:

read error a: signal dropped. means there was an unexpected cut in the data signal. that's why we usually get a when we suddenly stop the tape during loading.

read error b: signal not understood? usually due to head alignment or low quality magnetic signal on tape.

read error c: invalid file type?

read error d: block is too large to fit in the buffer. (given when you do a cat on large blocks)

are there any others? corrections are welcome.

[arnoldemu]

I'm thinking of explaining read error codes in the wiki, however I'm not sure about the difference between a and b. Here's what I know:

read error a: signal dropped. means there was an unexpected cut in the data signal. that's why we usually get a when we suddenly stop the tape during loading.

read error b: signal not understood? usually due to head alignment or low quality magnetic signal on tape.

read error c: invalid file type?

read error d: block is too large to fit in the buffer. (given when you do a cat on large blocks)

are there any others? corrections are welcome.

read error a is down to the timing of the signal, so the timing is too fast, or signal dropped.

read error b is checksum incorrect (so data read ok, but when checksum was calculated then compared to checksum on cassette, they were different).

read error d is block too large.

read error c seems to be used with "CAS CHECK". This is where you are comparing data in memory with data written to tape. So effectively a verify that data was written correctly.

[ssg]

Ok I added the initial version. Firmware disassembly excerpts could be added in the future to prove in which exact cases they are used.


http://cpcwiki.eu/index.php/Read_error_codes

[Gryzor]

Thanks for adding it

Tip: take a look at http://cpcwiki.eu/index.php/Special:WhatLinksHere/Read_error_codes : this shows that no other articles link to the one you created. While your effort is visible when someone searches for it, it's not easy to get there through other articles... so it'd be great to add links to it to any relevant pages you can think of - guides, troubleshooting, hardware even...

[Bryce]

I've added links from the two DIY tape sockets I did:

http://www.cpcwiki.eu/index.php/DIY_464_External_Audio_Socket

http://www.cpcwiki.eu/index.php/DIY_Plus_Tape_Socket

But it needs to get added to a main software / hardware page directory too.

Bryce.

[Gryzor]

Thanks mate!

As for the main soft/hard pages, hm, maybe it's not the best place... we're really lacking a 'troubleshooting' ueber-category I guess?

[Bryce]

At the moment, the only trouble-shooting is lumped in at the bottom of the DIY & Repair, but as most trouble shooting is hardware related, it's probably still the best place to have it, it just lacks in content?

Bryce.

[Gryzor]

You mean DIY&Repair? Probably... could even rename it to DIY&Troubleshooting, which somehow I feel also covers repairing...

[Bryce]

Nah, DIY & Repair is the better description, troubleshooting is just a step within the repair process, eg: A read error on the disc, Troubleshooting = Does the drive belt need to be replaced, Repair = The description of how one changes the belt.

The other option would be to put DIY in its own category and make a new Troubleshooting and repair category? But there's very little content at the moment to justify this.

Bryce.

[Gryzor]

Nah, you're right abot that.