[Simh] Problems Booting VAX Emulation on Raspberry Pi

[Rob Jarratt]

Ah, so if the problem indicates a problem with the system disk then that
explains things better. I think I know where to look now because the system
disk is actually on a different machine and accessed using CIFS, so there is
a problem in that area. I took it to be a problem with the vmb.exe file.

 

Thanks

 

Rob

 

From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing-edge.com]
On Behalf Of Mark Pizzolato - Info Comm
Sent: 08 September 2012 13:17
To: r.jarratt at computer.org; simh at trailing-edge.com
Subject: Re: [Simh] Problems Booting VAX Emulation on Raspberry Pi

 

Hi Rob,

 

You don't show much detail about what your vax780.ini file looks like.

 

The "%BOOT-F-Unable to locate BOOT file" message is being issued by the code
from vmb.exe.  This would suggest to me that the disk image you are trying
to boot from has somehow gotten corrupted.  I'd pull that image off the
raspberry to an environment where you have a working simulator and attach
the disk image as an additional disk on that simulator and use then look
around at the details of the contents.

 

Good Luck.

 

-          Mark

 

From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing-edge.com]
On Behalf Of Rob Jarratt
Sent: Saturday, September 08, 2012 2:03 AM
To: simh at trailing-edge.com
Subject: [Simh] Problems Booting VAX Emulation on Raspberry Pi

 

I have had the 780 emulation running on my Raspberry Pi for some time now.
Recently I have had intermittent problems with vmb.exe, the problem seems to
have become permanent now though. I have re-copied vmb.exe to the machine
but the problem persists. Here is the log:

pi at raspberrypi:~$ sudo ./vax780

VAX780 simulator V3.9-0

libpcap version 1.1.1

Eth: opened OS device eth0

Debug output to "STDOUT"

Loading boot code from vmb.exe

%BOOT-F-Unable to locate BOOT filesim> q

Goodbye

Eth: closed eth0

Debug output disabled

The error about being unable to locate the BOOT file happens about 40
seconds after the "Loading boot code from vmb.exe" message.

Any ideas?

Regards

Rob

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20120908/7d623a04/attachment-0002.html>