While I'm new to speak up here, I've been watching for a while. I've also
used the name "MightyFrame" on groups, although that email address is not
registered with this list.
A few months back, I published a page decoding QIC-24 format.
http://mightyframe.blogspot.com/2015/08/qic-24-tape-data-bl
015 at 4:49 AM, Lawrence Wilkinson
wrote:
> On 15/11/15 11:15, Microtech Dart wrote:
>
> (snip)
>> "The cyclical redundancy check (CRC) shall consist of two bytes,
>> calculated
>> over the 512 bytes of interchange data, and the 4-byte block address,
>> *starting
cumenting things then specifying the CRC polynomial and
> the init value as all-ones should be sufficient.
>
> The corresponding init parameter of reveng is "-i ".
>
> On 15/11/15 23:52, Microtech Dart wrote:
>
>> Lawrence, Dwight & Chuck...thank you!
>&
http://terrysrubberrollers.com/
Terry has rebuilt about a dozen rollers for me over the past 2 years.
You'll need to remove the roller and send it in to him with a money order
(he doesn't take checks or credit cards), but he'll do a fantastic job for
about $40-50 per roller.
Not cheap, but worth
I've encountered a new challenge with the CRC now, it's from the data
blocks written by the Kennedy 6450/6455 Tape Drive.
The below message is to the creator of CRC_RevEng about this topic, but
since several here have been so helpful to me on understanding CRCs (and
Chuck, you referred me to CRC_R
I don't know about the materials, but I can say that his work has been so
good, that I never even thought to even ask about a warranty.
His email addresses are at the bottom of his very 90s looking website, and
he usually replies within a day.
On Tue, Nov 17, 2015 at 10:24 AM, Ali wrote:
> >
Thanks for the feedback here, Andreas, very good question.
Actually, I was suspecting that I was running into the maximum length of
the command line at least with Windows, and possibly with Linux, even
though it displayed the full message in the terminal window.
This is why I wanted to do the you
init parameter of reveng is "-i ".
>
> On 15/11/15 23:52, Microtech Dart wrote:
>
>> Lawrence, Dwight & Chuck...thank you!
>>
>> The revelation that I can append 84CF to the 512-byte data block and the
>> 4-byte block address, is golden, and t
Hi, all. It's been a while since I've discussed anything here. We've made
a lot of progress re-constructing a couple of Point 4 machines (as much as
one can without the actual hardware), yet still need some help from a few
knowledgeable folks in this 35+ year old OS. It was built on the DG Nova
Thanks for sharing that, Ian! Your story is exactly what I was hoping to
gather here.
Does our dissection of the LU0 make any sense to you?
On Sun, May 8, 2016 at 3:54 PM, Ian S. King wrote:
> On Sun, May 8, 2016 at 1:31 AM, Microtech Dart
> wrote:
>
> > Hi, all. It'
Ian, could you reply with a link to what you refer to as IRIS 68k hardware?
This catches my attention, and I just want to make certain that this isn't
related to what I've been working on.
Maybe it's just a coincidence, because I've been restoring an IRIS OS (from
Point 4), and independently, the
Bill, I hope that you can snap a few pictures with your phone to show us.
This is quite the mystery device.
On Sat, Jul 2, 2016 at 8:56 PM, Bill Sudbrink
wrote:
> No, I don't think so. I'm pretty sure that the paper
> tape on this thing is for output, probably printed or
> marked in some way be
Interesting story (well maybe for some). For any of you who have followed
my projects, here is some context:
It is one and the same company who used both the Point 4 IRIS systems and
the Convergent Technologies MightyFrame systems that I have spent the last
3 years reconstructing and restoring. So
Yes!
These are the octal-value asci characters, as far as I understand, for the
Point 4 IRIS system. That's for identifying the Televideo connection!
It's probably purely anecdotal, but back in the day, the address of this
local computer servicer/reseller was:
FUTURE DIMENSIONS,INC.
847 N. HOLL
14 matches
Mail list logo
