Your message dated: Fri, 05 Apr 2019 19:07:34 -0400
Sorry, for the confusion regarding half words and file formats... I don't
where the half-words came from...
Anyway, I am now able to spend time working on this to figure out where
I went wrong.
FYI, There is a document that has some
Phil,
The terms originated in the IBM 360 “principles of operation” book which I have
here for the model 67. To wit: “instructions operate on units called
halfword (2 bytes), fullword(4 bytes), doubleword (8 bytes), quad word (16
bytes). FWIW The IBM ‘storage block’ was 2048 bytes
On 2019-04-06 00:33, Phil Budne wrote:
Johnny Billquist wrote:
In DEC terminology those are words.
It goes: byte, word, longword, quadword, octaword. (8, 16, 32, 64, 128
bits.)
Halfword is something that I first saw on Motorola 68K, but maybe it's
been used elsewhere as well. But it feels
Johnny Billquist wrote:
> In DEC terminology those are words.
> It goes: byte, word, longword, quadword, octaword. (8, 16, 32, 64, 128
> bits.)
> Halfword is something that I first saw on Motorola 68K, but maybe it's
> been used elsewhere as well. But it feels wrong to use that terminology
>
On 2019-04-05 03:41, Ron Young wrote:
For each line there is a 2 byte length, 2 byte line number followed by the data
bytes... One more thing is that each line is halfword aligned with padded null
bytes.
In DEC terminology those are words.
It goes: byte, word, longword, quadword, octaword.
Matt Burke has implemented the QDSS VCB02 Dragon colour graphics device in his
side branch of SimH, as a VAXstation II. I’ve tried a prototype and it seems to
work well, up to the limits of VS2 memory limits etc.
I believe he intends to merge it into mainstream SimH in due course, as his
time
Thanks, I'll try that. A little bit later because the host server is a
production one.
n.b.: This story is the following of the one with performances on
OpenVMS Itanium. The performance on the windows server is about 5 times
better, so. My first idea was "we can do everything with 2 OpenVMS
