[Simh] Problem with I1620 - Monitor I Operating System

[Michael Short]

During the load of the MON1 there is a three sector write which crosses a
cylinder boundary. If the Cyl O'vflw is set to program the load should
complete.

On Wednesday, March 22, 2017, Sancho Villa, Roberto <rsancho at indra.es>
wrote:

> Hi
>
>
>
> I’m trying the SimH I1620 and faced some problems.
>
> I’m installing Monitor I System, the Operating System.
>
>
>
> I’ve been searching the maillist for help and found your email “Problem
> with I1620”, that suggest you already done it
>
>
>
> What happens to me is that the normal installs generates a CYLINDER
> OVERFLOW error. If I comment out the overflow checks in sim code, then
> installation goes on. I’m using the current GitHub code. Did you get this
> behavior?
>
>
>
> Best regards
>
> Roberto
>
>
>
> BTW: Monitor I is little known and deserves a better place in OS timeline.
>
> As I could see, IBM 1620 Monitor I -> IBM 1130 DMS -> IBM System/3 SCP ->
> IBM System/32 … -> OS/400
>
> The three first ones available for SimH J
>
>
>
> ------------------------------
>
> Este correo electrónico y, en su caso, cualquier fichero anexo al mismo,
> contiene información de carácter confidencial exclusivamente dirigida a su
> destinatario o destinatarios. Si no es vd. el destinatario indicado, queda
> notificado que la lectura, utilización, divulgación y/o copia sin
> autorización está prohibida en virtud de la legislación vigente. En el caso
> de haber recibido este correo electrónico por error, se ruega notificar
> inmediatamente esta circunstancia mediante reenvío a la dirección
> electrónica del remitente.
> Evite imprimir este mensaje si no es estrictamente necesario.
>
> This email and any file attached to it (when applicable) contain(s)
> confidential information that is exclusively addressed to its recipient(s).
> If you are not the indicated recipient, you are informed that reading,
> using, disseminating and/or copying it without authorisation is forbidden
> in accordance with the legislation in effect. If you have received this
> email by mistake, please immediately notify the sender of the situation by
> resending it to their email address.
> Avoid printing this message if it is not absolutely necessary.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20170322/60b8ca5a/attachment.html>