So I have an MSV11-QC (the 4gb Q Bus memory board) that has a failed
bit. On an 11/73 it throws the following error:
Expected data = 125252 (1010 1010 1010 1010
Bad data = 121252 (1010 0010 1010 1010)
Address = 10015140
Which puts the error in the top 2mb (1mw), bit 4000. No biggie,
consulting the matrix at:
Shows this to be bank 4, bit 4000 or E85.
Cut out E85, popped the board in (to double check before replacing) and
I see this:
Expected data = 125252
Bad data = 121252
Address = 02015140
Ooops. That would be decimal 531,040 which puts it in bank 1? Which
should be E88, where did I go wrong here?
Or is the table for the MSV11-Q only valid for the 64k ones and not the
256k ones? If so the bits may be right, but the banks are different.
Anyone want to cross-check this or my maths?
PS: Sorry if duplicates are getting sent to the list. I'm retiring
cz(a)alembic.crystel.com and replacing it with cz(a)beaker.crystel.com. If
the list manager could update my email I would appreciate!
I think you have the essence of a solution, using the Unix filter paradigm at user or driver level.
Your desire to retain the original file format(s) is very sensible, it is always best to record "raw" data - for the greatest fidelity.
The ISO 7-layer model provides a paradigm for data transport/storage formats and derived (presentation) formats.
Good luck with the weather
From: ben [mailto:firstname.lastname@example.org]
Sent: 01 January 2023 14:27
To: Martin Bishop <mjd.bishop(a)emeritus-solutions.com>; General Discussion: On-Topic and Off-Topic Posts <cctalk(a)classiccmp.org>
Subject: Re: [cctalk] Re: How to print old files.
On 2023-01-01 6:53 a.m., Martin Bishop wrote:
> Folks - wishing all a Good New Year
> The first ingredient must be a printer with a a suitable font table, in these times of soft fonts that should be a given or tractable.
> The second element is to convert to and use an MCS / multibyte character representation - which can differentiate _ ^ and the desired arrow marks.
> To do this you could:
> - load the file into an editor, save it in MCS format, perform the
> necessary substitutions (two global replaces)
> - write a program / script to achieve the same effect, read char and convert/translate to MCS octets.
> Note. It is just possible you will find a font with the arrows in the upper 128 glyphs of 8 bit "ascii", in which case you can skip the MCS conversion.
A filter of some kind is needed.
With the rise of emulators for old machines,I can see text being written with terminal emulation of the orginal i/o devices, but that leaves printing or tranfering text files a problem.
JOE could have a REAL - big iron 67, SAM runs windows 2000, TOM has a micro VAX. Every thing gets dumped to the cloud.
One must keep data as files, none of this crappy mess that this modern 'buy a app' to print,or read.
How does one share binary and paper tape/cards as files?
PS: Back to inventing big iron 67.
tag line: Cloud computing delayed to to bad weather, server is under 3 feet of snow.