<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>Quick test. Copy the tape into disk files using both drives, then compare the two files. If they come out the same, then it's something in backup. If they're different, you can look and see what bits are changed. If copy errors out on the team, then that's probably simpler to debug than backup.</div><div><br></div><div>Btw. Does anyone have a source for ds10l cup fans? I need to replace a very noisy onr.</div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Galaxy Tab® A</div></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Johnny Billquist <bqt@softjar.se> </div><div>Date: 11/5/17 5:19 PM (GMT-07:00) </div><div>To: Paul Koning <paulkoning@comcast.net> </div><div>Cc: simh@trailing-edge.com </div><div>Subject: Re: [Simh] Simh Digest, Vol 166, Issue 12 </div><div><br></div></div>On 2017-11-06 00:39, Paul Koning wrote:<br>> <br>> <br>>> On Nov 5, 2017, at 5:48 PM, Johnny Billquist <bqt@softjar.se> wrote:<br>>><br>>> Ah.<br>>><br>>> That sound like a simh problem. The tape file itself have one of a few different formats, none of them even keep any CRC (at least none of the ones I can think of right now).<br>>> The backing file storage just have the tape records. And obviously, since the same backing file storage is used on both emulated tape drives, there is obviously nothing wrong with the file.<br>>><br>>> Any CRC indication is purely made up in simh. And that is where you get the error indication. So I guess someone needs to dig into the emulation of the Massbus tape drives.<br>> <br>> Another possibility: VMS BACKUP has its own CRC in its data blocks, entirely separate from the tape drive hardware check codes. If BACKUP reports CRC errors, it's most likely talking about those. BACKUP also writes redundant blocks, so if only 1 out of N blocks is bad, the bad block can be reconstructed. Presumably, CRC errors reported by BACKUP are caused by flaws in the original material that was transcribed into SIMH tape images.<br><br>...in which case it should show up both using the TS11 and TE15. But it <br>only shows up in the TE16, which suggests that there is nothing wrong <br>with the contents of the actual tape image file.<br><br>Correct me if I'm thinking wrong somewhere here.<br><br> Johnny<br><br>-- <br>Johnny Billquist || "I'm on a bus<br> || on a psychedelic trip<br>email: bqt@softjar.se || Reading murder books<br>pdp is alive! || tryin' to stay hip" - B. Idol<br>_______________________________________________<br>Simh mailing list<br>Simh@trailing-edge.com<br>http://mailman.trailing-edge.com/mailman/listinfo/simh</body></html>