Further to recent communications on this topic (for which many thanks to those persons) and some thinking I have a potential/possible reason that I would like comments on.
My thinking goes that if in the virtualisation setup I have the "disk" is not responding quickly enough for the RL driver in SimH then maybe it will return a buffer of zeros. Now even if I am on the right track for this, it leaves some questions (in no particular order): a) others have reported being able to use SimH 4.0 under virtualisation with no issues although not with RSX11M. So why would I be different? b) I would have thought that the driver for RL especially as it is emulating hardware would not "timeout" so quickly. c) If it did timeout, why have I not seen an error message? Maybe I need to look somewhere else ... hmm. And the obvious statement that I am completely wrong and it is something I have configured incorrectly either in the virtualisation environment (except it gives same error under both Virtual Box and VMware Workstation) or in SimH. Phil ----- Original Message ----- From: Mike Stramba <mikestra...@gmail.com> Reply-To: <mikestra...@gmail.com> To: Phil Fisher <phil.fis...@peejayeff.co.uk> Cc: <simh@trailing-edge.com> Sent: 22/03/2018 21:04:56 Subject: Re: [Simh] Problem booting RSX11M on pdp11 (halt at loc 0) ________________________________________________________________________________ Phil, I assume this is the site ? : http://home.earthlink.net/~n1be/pdp11/PDP11.html I'm downloading it now will try it on my Win7 laptop. Have tried / been successful running it on a "native" O.S (not under VmWare or VirtualBox ?) I.e is the point to try to get it running under VmWare / Vbox .. or just it running period ? ;) Mike On 3/22/18, Phil Fisher <phil.fis...@peejayeff.co.uk> wrote: > > I have checked up some information and found the following. (if anyone wants > to see the INI file or the disk image I can send that directly as a 7zip > file). > > Looking at the dump of the disk file it looks like a valid boot block > although (as below from offset 0): > > 0000000 000240 000406 000000 002467 000000 000000 000000 000000 > > 0000010 012704 001000 ... > > suggesting a code start of: > > NOP > BR 1$ > .word 0 > .word 02467 > .word 0 > .word 0 > .word 0 > .word 0 > 1$: MOV #1000,R4 > ... > > all values in octal. > > So to me this looks at least sensible. Alas I cannot recall what the old > RK05 boot block looked like for comparison as I was at one time VERY > familiar with that. > > So my thoughts are that BOOT is broken somehow or I have majorly screwed up > the INI file. > > Phil > -- > Phil J Fisher phil.fis...@peejayeff.co.uk > _____________________________________________________ > Email and any attachments sent are scanned by McAfee > Anti-Virus but integrity cannot be guaranteed. > _____________________________________________________ > > _______________________________________________ > Simh mailing list > Simh@trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh _______________________________________________ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
