[Simh] Panic while attempting to boot a NetBSD ISO

[Gregg Levine]

Hello!
Okay I've tried again to bring things up. This time remembering to
give it dua1: at the prompt instead of something else. It promptly
complained. I'll try one more time this time with the image in the
same directory as the boot script. I've also commented out the
firmware blob since you've commented that its already included.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."


On Sat, Feb 6, 2016 at 7:59 AM, Mark Pizzolato <Mark at infocomm.com> wrote:
> On Friday, February 5, 2016 at 10:07 PM, Gregg Levine wrote:
>> Hello!
>> That's just it Mark. They aren't empty ones. I've downloaded three
>> separate ISO images, 5.1.3 and then 5.1.4 and finally 5.1.5 and placed
>> them in their own directories.
>>
>>
>> You mean that the selection of what to create is bollixed? It was
>> supposed to create an empty disk image. Now what it says here: "RQ1:
>> creating new file", it was suppose to use RQ0 for that.
>> I suspect something is definitely wrong there.
>
> That was my point.  Meanwhile, Wilm Boerhout <wilm at boerhout.nl>
> points out the reason why the simulator halted (you tried to boot
> from DUAL instead of DUA1).  Given the 'RQ1L creating new file',
> you'll get a different failure message trying to boot from an empty disk.
>
> Looking ahead.  I said that your attempt to connect XQ to wlan would
> Probably be a problem when you get that far.  For NetBSD you're
> only interested in IP and none of the other DEC LAN protocols, so
> 'attach xq NAT:' will probably meet your needs.
>
>> Right now the computer is running Windows. The stuff for all of that
>> is on a different disk, and I'll need to switch back.
>
> All this stuff works on Windows also.  :-)
>
>
>> I'll report more when that is happening.
>> -----
>> Gregg C Levine gregg.drwho8 at gmail.com
>> "This signature fought the Time Wars, time and again."
>>
>>
>> On Sat, Feb 6, 2016 at 12:31 AM, Mark Pizzolato <Mark at infocomm.com>
>> wrote:
>> > On Friday, February 5, 2016 at 9:15 PM, Gregg Levine wrote:
>> >> Hello!
>> >> Okay here goes, I'm following these instructions:
>> >> https://www.netbsd.org/ports/vax/emulator-howto.html
>> >
>> > Well, the commands outlined at this link say:
>> >         load -r /usr/pkg/share/simh/ka655x.bin
>> >         set cpu 64m
>> >         set rq0 ra92
>> >         at rq0 netbsd.dsk
>> >         set rq1 cdrom
>> >         at rq1 /path/to/vaxcd.iso
>> >         at xq0 name-of-network-interface-on-host
>> >         boot cpu
>> >
>> >> And I'm getting this response:
>> >> MicroVAX 3900 simulator V4.0-0 Beta        git commit id: f03bae6c
>> >> sim> do netbsd-boot
>> >> RQ1: creating new file
>> >
>> > This message suggests that:
>> >         at rq1 /path/to/vaxcd.iso
>> > isn't actually pointing at the CDROM image, but has created a new empty
>> disk image file
>> >
>> >> libpcap version 1.4.0
>> >> Eth: opened OS device wlan0 - No description available
>> >
>> > OK so far, but I think you'll eventually have trouble using a Wireless Device.
>> That won't matter for now.
>> >
>> >> KA655-B V5.3, VMB 2.7
>> >> Performing normal system tests.
>> >> 40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
>> >> 24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
>> >> 08..07..06..05..04..03..
>> >> Tests completed.
>> >> >>>boot dual:
>> >> (BOOT/R5:0 DUAL
>> >>
>> >>
>> >>
>> >>   2..
>> >> ?41 DEVASSIGN, DUAL
>> >> HALT instruction, PC: 00000C1A (MOVL (R11),SP)
>> >> sim>
>> >
>> > Booting from an empty CDROM image isn't likely to get too far...
>> >
>> >> The script I wrote follows what it says on the site, except for the CD-ROM
>> >> file, and the network device, and the BIN file it needs.
>> >
>> > The "load -r ..." command isn't necessary anymore.  The ROM image is built
>> in to the binary, but what you did shouldn't be bad.
>> >
>> > - Mark
>