Re: [Simh] Standalone boot on vax8600?
Finally had a few minutes to look at this. Congratulations, Henry. You actually found a bug in simh. Fix attached. Mark, could you please commit this? Also, I noticed a bunch of warnings from some printf in pdp11_dmc.c, which I did not do anything about. I grabbed the code from today, so I suspect you or someone else will fix those soon anyway. Johnny On 2014-07-13 07:18, Johnny Billquist wrote: On 2014-07-13 05:01, Henry Bent wrote: Here you go: http://occs.cs.oberlin.edu/~hbent/vaxultrix/boot.gz Thanks. I'll see if I have some time to look at it today. Johnny -Henry On 12 July 2014 22:57, Johnny Billquist b...@softjar.se mailto:b...@softjar.se wrote: On 2014-07-13 04:52, Henry Bent wrote: Sure, I'll work on getting an Ultrix image in a usable state so that I can upload it. Actually, thinking about it, it should be enough with just the boot file that you are using. Johnny -Henry On 12 July 2014 22:50, Johnny Billquist b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se wrote: On 2014-07-13 04:19, Henry Bent wrote: Cool, thanks. I figured out what's going on. The standalone programs are running, they just aren't displaying any input or output after the first character is printed. So if I do this: -- sim load -o boot 0 sim run 2 -- and then blindly type ra(0,0)vmunix, it boots! [...] Hmm hmm. I suspect I might know what is going on there. I'd have to test and play around some to verify, though. The console I/O on the 86x0 machines are a bit special, and I wouldn't be surprised if there were some issues in simh related to that. Mark, can we get some trace of all reads and writes to the registers related to the console? (There are four logical devices addressed on the 86x0 machines through the same CSRs.) Henry, if you could get such information logged, we could probably fix this pretty fast. Or else if you could just provide me with the files, I could test this myself as well. I don't have an old Ultrix image around, though. Johnny -- Ultrix V2.2 System #2: Wed Nov 18 01:14:13 EST 1987 real mem = 8388608 avail mem = 6888448 using 34 buffers containing 278528 bytes of memory VAX 8600, serial no. 1234, hardware level = 7 IO adapter 0 at address 0x2008 is an SBI adapter uba0 at address 0x20006000 uda0 at uba0 uq0 at uda0 csr 172150 vec 774, ipl 15 ra0 at uq0 slave 0 de0 at uba0 csr 174510 vec 120, ipl 15 mba0 at address 0x20012000 ht0 at mba0 drive 0 tu0 at ht0 slave 0 boot device not found root device? -- And I can then interact with the console, characters are displayed normally, etc. -Henry On 12 July 2014 19:33, Mark Pizzolato - Info Comm m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com wrote: On Thursday, July 10, 2014 at 5:23 PM, Mark Pizzolato wrote: On Jul 10, 2014 2:02 PM, Johnny Billquist b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se wrote: On 2014-07-11 01:08, Mark Pizzolato - Info Comm wrote: On Thursday, July 10, 2014 at 3:13 PM, Cory Smelosky wrote: On Thu, 10 Jul 2014, Henry Bent wrote: Well, that at least did something different. sim boot rq0 /r5:8 Loading boot code from vmb.exe %BOOT-F-Unexpected Exceptio The 8600 simulator always seems to cut off the last character of its messages, I wonder if that's in any
Re: [Simh] Standalone boot on vax8600?
Cool, thanks. I figured out what's going on. The standalone programs are running, they just aren't displaying any input or output after the first character is printed. So if I do this: -- sim load -o boot 0 sim run 2 -- and then blindly type ra(0,0)vmunix, it boots! -- Ultrix V2.2 System #2: Wed Nov 18 01:14:13 EST 1987 real mem = 8388608 avail mem = 6888448 using 34 buffers containing 278528 bytes of memory VAX 8600, serial no. 1234, hardware level = 7 IO adapter 0 at address 0x2008 is an SBI adapter uba0 at address 0x20006000 uda0 at uba0 uq0 at uda0 csr 172150 vec 774, ipl 15 ra0 at uq0 slave 0 de0 at uba0 csr 174510 vec 120, ipl 15 mba0 at address 0x20012000 ht0 at mba0 drive 0 tu0 at ht0 slave 0 boot device not found root device? -- And I can then interact with the console, characters are displayed normally, etc. -Henry On 12 July 2014 19:33, Mark Pizzolato - Info Comm m...@infocomm.com wrote: On Thursday, July 10, 2014 at 5:23 PM, Mark Pizzolato wrote: On Jul 10, 2014 2:02 PM, Johnny Billquist b...@softjar.se wrote: On 2014-07-11 01:08, Mark Pizzolato - Info Comm wrote: On Thursday, July 10, 2014 at 3:13 PM, Cory Smelosky wrote: On Thu, 10 Jul 2014, Henry Bent wrote: Well, that at least did something different. sim boot rq0 /r5:8 Loading boot code from vmb.exe %BOOT-F-Unexpected Exceptio The 8600 simulator always seems to cut off the last character of its messages, I wonder if that's in any way related to the other console problems. 780, 750, and 730 have the same issue...along with not actually booting from the console RL, floppy, et al. The last character output in a message just prior to executing a HALT instruction is not surprising since the simulator implements a delay (as a number of instructions executed) from when the data is put in the output register prior to generating the completion interrupt/status. The halt instruction gets executed before the delay number of instructions have completed. Even if that was 'fixed', nothing operational would change. The reason the message has been generated will still exist. The latest github code will no longer drop the last character output just prior to executing a HALT instruction which returns to the sim prompt. Like I said above, nothing else changes though. - Mark ___ 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
Re: [Simh] Standalone boot on vax8600?
On 2014-07-13 04:19, Henry Bent wrote: Cool, thanks. I figured out what's going on. The standalone programs are running, they just aren't displaying any input or output after the first character is printed. So if I do this: -- sim load -o boot 0 sim run 2 -- and then blindly type ra(0,0)vmunix, it boots! [...] Hmm hmm. I suspect I might know what is going on there. I'd have to test and play around some to verify, though. The console I/O on the 86x0 machines are a bit special, and I wouldn't be surprised if there were some issues in simh related to that. Mark, can we get some trace of all reads and writes to the registers related to the console? (There are four logical devices addressed on the 86x0 machines through the same CSRs.) Henry, if you could get such information logged, we could probably fix this pretty fast. Or else if you could just provide me with the files, I could test this myself as well. I don't have an old Ultrix image around, though. Johnny -- Ultrix V2.2 System #2: Wed Nov 18 01:14:13 EST 1987 real mem = 8388608 avail mem = 6888448 using 34 buffers containing 278528 bytes of memory VAX 8600, serial no. 1234, hardware level = 7 IO adapter 0 at address 0x2008 is an SBI adapter uba0 at address 0x20006000 uda0 at uba0 uq0 at uda0 csr 172150 vec 774, ipl 15 ra0 at uq0 slave 0 de0 at uba0 csr 174510 vec 120, ipl 15 mba0 at address 0x20012000 ht0 at mba0 drive 0 tu0 at ht0 slave 0 boot device not found root device? -- And I can then interact with the console, characters are displayed normally, etc. -Henry On 12 July 2014 19:33, Mark Pizzolato - Info Comm m...@infocomm.com mailto:m...@infocomm.com wrote: On Thursday, July 10, 2014 at 5:23 PM, Mark Pizzolato wrote: On Jul 10, 2014 2:02 PM, Johnny Billquist b...@softjar.se mailto:b...@softjar.se wrote: On 2014-07-11 01:08, Mark Pizzolato - Info Comm wrote: On Thursday, July 10, 2014 at 3:13 PM, Cory Smelosky wrote: On Thu, 10 Jul 2014, Henry Bent wrote: Well, that at least did something different. sim boot rq0 /r5:8 Loading boot code from vmb.exe %BOOT-F-Unexpected Exceptio The 8600 simulator always seems to cut off the last character of its messages, I wonder if that's in any way related to the other console problems. 780, 750, and 730 have the same issue...along with not actually booting from the console RL, floppy, et al. The last character output in a message just prior to executing a HALT instruction is not surprising since the simulator implements a delay (as a number of instructions executed) from when the data is put in the output register prior to generating the completion interrupt/status. The halt instruction gets executed before the delay number of instructions have completed. Even if that was 'fixed', nothing operational would change. The reason the message has been generated will still exist. The latest github code will no longer drop the last character output just prior to executing a HALT instruction which returns to the sim prompt. Like I said above, nothing else changes though. - Mark ___ Simh mailing list Simh@trailing-edge.com mailto:Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh -- Johnny Billquist || I'm on a bus || on a psychedelic trip email: b...@softjar.se || Reading murder books pdp is alive! || tryin' to stay hip - B. Idol ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] Standalone boot on vax8600?
Sure, I'll work on getting an Ultrix image in a usable state so that I can upload it. -Henry On 12 July 2014 22:50, Johnny Billquist b...@softjar.se wrote: On 2014-07-13 04:19, Henry Bent wrote: Cool, thanks. I figured out what's going on. The standalone programs are running, they just aren't displaying any input or output after the first character is printed. So if I do this: -- sim load -o boot 0 sim run 2 -- and then blindly type ra(0,0)vmunix, it boots! [...] Hmm hmm. I suspect I might know what is going on there. I'd have to test and play around some to verify, though. The console I/O on the 86x0 machines are a bit special, and I wouldn't be surprised if there were some issues in simh related to that. Mark, can we get some trace of all reads and writes to the registers related to the console? (There are four logical devices addressed on the 86x0 machines through the same CSRs.) Henry, if you could get such information logged, we could probably fix this pretty fast. Or else if you could just provide me with the files, I could test this myself as well. I don't have an old Ultrix image around, though. Johnny -- Ultrix V2.2 System #2: Wed Nov 18 01:14:13 EST 1987 real mem = 8388608 avail mem = 6888448 using 34 buffers containing 278528 bytes of memory VAX 8600, serial no. 1234, hardware level = 7 IO adapter 0 at address 0x2008 is an SBI adapter uba0 at address 0x20006000 uda0 at uba0 uq0 at uda0 csr 172150 vec 774, ipl 15 ra0 at uq0 slave 0 de0 at uba0 csr 174510 vec 120, ipl 15 mba0 at address 0x20012000 ht0 at mba0 drive 0 tu0 at ht0 slave 0 boot device not found root device? -- And I can then interact with the console, characters are displayed normally, etc. -Henry On 12 July 2014 19:33, Mark Pizzolato - Info Comm m...@infocomm.com mailto:m...@infocomm.com wrote: On Thursday, July 10, 2014 at 5:23 PM, Mark Pizzolato wrote: On Jul 10, 2014 2:02 PM, Johnny Billquist b...@softjar.se mailto:b...@softjar.se wrote: On 2014-07-11 01:08, Mark Pizzolato - Info Comm wrote: On Thursday, July 10, 2014 at 3:13 PM, Cory Smelosky wrote: On Thu, 10 Jul 2014, Henry Bent wrote: Well, that at least did something different. sim boot rq0 /r5:8 Loading boot code from vmb.exe %BOOT-F-Unexpected Exceptio The 8600 simulator always seems to cut off the last character of its messages, I wonder if that's in any way related to the other console problems. 780, 750, and 730 have the same issue...along with not actually booting from the console RL, floppy, et al. The last character output in a message just prior to executing a HALT instruction is not surprising since the simulator implements a delay (as a number of instructions executed) from when the data is put in the output register prior to generating the completion interrupt/status. The halt instruction gets executed before the delay number of instructions have completed. Even if that was 'fixed', nothing operational would change. The reason the message has been generated will still exist. The latest github code will no longer drop the last character output just prior to executing a HALT instruction which returns to the sim prompt. Like I said above, nothing else changes though. - Mark ___ Simh mailing list Simh@trailing-edge.com mailto:Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh -- Johnny Billquist || I'm on a bus || on a psychedelic trip email: b...@softjar.se || Reading murder books pdp is alive! || tryin' to stay hip - B. Idol ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] Standalone boot on vax8600?
On 2014-07-13 04:52, Henry Bent wrote: Sure, I'll work on getting an Ultrix image in a usable state so that I can upload it. Actually, thinking about it, it should be enough with just the boot file that you are using. Johnny -Henry On 12 July 2014 22:50, Johnny Billquist b...@softjar.se mailto:b...@softjar.se wrote: On 2014-07-13 04:19, Henry Bent wrote: Cool, thanks. I figured out what's going on. The standalone programs are running, they just aren't displaying any input or output after the first character is printed. So if I do this: -- sim load -o boot 0 sim run 2 -- and then blindly type ra(0,0)vmunix, it boots! [...] Hmm hmm. I suspect I might know what is going on there. I'd have to test and play around some to verify, though. The console I/O on the 86x0 machines are a bit special, and I wouldn't be surprised if there were some issues in simh related to that. Mark, can we get some trace of all reads and writes to the registers related to the console? (There are four logical devices addressed on the 86x0 machines through the same CSRs.) Henry, if you could get such information logged, we could probably fix this pretty fast. Or else if you could just provide me with the files, I could test this myself as well. I don't have an old Ultrix image around, though. Johnny -- Ultrix V2.2 System #2: Wed Nov 18 01:14:13 EST 1987 real mem = 8388608 avail mem = 6888448 using 34 buffers containing 278528 bytes of memory VAX 8600, serial no. 1234, hardware level = 7 IO adapter 0 at address 0x2008 is an SBI adapter uba0 at address 0x20006000 uda0 at uba0 uq0 at uda0 csr 172150 vec 774, ipl 15 ra0 at uq0 slave 0 de0 at uba0 csr 174510 vec 120, ipl 15 mba0 at address 0x20012000 ht0 at mba0 drive 0 tu0 at ht0 slave 0 boot device not found root device? -- And I can then interact with the console, characters are displayed normally, etc. -Henry On 12 July 2014 19:33, Mark Pizzolato - Info Comm m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com wrote: On Thursday, July 10, 2014 at 5:23 PM, Mark Pizzolato wrote: On Jul 10, 2014 2:02 PM, Johnny Billquist b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se wrote: On 2014-07-11 01:08, Mark Pizzolato - Info Comm wrote: On Thursday, July 10, 2014 at 3:13 PM, Cory Smelosky wrote: On Thu, 10 Jul 2014, Henry Bent wrote: Well, that at least did something different. sim boot rq0 /r5:8 Loading boot code from vmb.exe %BOOT-F-Unexpected Exceptio The 8600 simulator always seems to cut off the last character of its messages, I wonder if that's in any way related to the other console problems. 780, 750, and 730 have the same issue...along with not actually booting from the console RL, floppy, et al. The last character output in a message just prior to executing a HALT instruction is not surprising since the simulator implements a delay (as a number of instructions executed) from when the data is put in the output register prior to generating the completion interrupt/status. The halt instruction gets executed before the delay number of instructions have completed. Even if that was 'fixed', nothing operational would change. The reason the message has been generated will still exist. The latest github code will no longer drop the last character output just prior to executing a HALT instruction which returns to the sim prompt. Like I said above, nothing else changes though. - Mark _ Simh mailing list Simh@trailing-edge.com mailto:Simh@trailing-edge.com mailto:Simh@trailing-edge.com mailto:Simh@trailing-edge.com__ http://mailman.trailing-edge.__com/mailman/listinfo/simh http://mailman.trailing-edge.com/mailman/listinfo/simh -- Johnny Billquist || I'm on a bus || on a psychedelic trip
Re: [Simh] Standalone boot on vax8600?
Here you go: http://occs.cs.oberlin.edu/~hbent/vaxultrix/boot.gz -Henry On 12 July 2014 22:57, Johnny Billquist b...@softjar.se wrote: On 2014-07-13 04:52, Henry Bent wrote: Sure, I'll work on getting an Ultrix image in a usable state so that I can upload it. Actually, thinking about it, it should be enough with just the boot file that you are using. Johnny -Henry On 12 July 2014 22:50, Johnny Billquist b...@softjar.se mailto:b...@softjar.se wrote: On 2014-07-13 04:19, Henry Bent wrote: Cool, thanks. I figured out what's going on. The standalone programs are running, they just aren't displaying any input or output after the first character is printed. So if I do this: -- sim load -o boot 0 sim run 2 -- and then blindly type ra(0,0)vmunix, it boots! [...] Hmm hmm. I suspect I might know what is going on there. I'd have to test and play around some to verify, though. The console I/O on the 86x0 machines are a bit special, and I wouldn't be surprised if there were some issues in simh related to that. Mark, can we get some trace of all reads and writes to the registers related to the console? (There are four logical devices addressed on the 86x0 machines through the same CSRs.) Henry, if you could get such information logged, we could probably fix this pretty fast. Or else if you could just provide me with the files, I could test this myself as well. I don't have an old Ultrix image around, though. Johnny -- Ultrix V2.2 System #2: Wed Nov 18 01:14:13 EST 1987 real mem = 8388608 avail mem = 6888448 using 34 buffers containing 278528 bytes of memory VAX 8600, serial no. 1234, hardware level = 7 IO adapter 0 at address 0x2008 is an SBI adapter uba0 at address 0x20006000 uda0 at uba0 uq0 at uda0 csr 172150 vec 774, ipl 15 ra0 at uq0 slave 0 de0 at uba0 csr 174510 vec 120, ipl 15 mba0 at address 0x20012000 ht0 at mba0 drive 0 tu0 at ht0 slave 0 boot device not found root device? -- And I can then interact with the console, characters are displayed normally, etc. -Henry On 12 July 2014 19:33, Mark Pizzolato - Info Comm m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com wrote: On Thursday, July 10, 2014 at 5:23 PM, Mark Pizzolato wrote: On Jul 10, 2014 2:02 PM, Johnny Billquist b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se wrote: On 2014-07-11 01:08, Mark Pizzolato - Info Comm wrote: On Thursday, July 10, 2014 at 3:13 PM, Cory Smelosky wrote: On Thu, 10 Jul 2014, Henry Bent wrote: Well, that at least did something different. sim boot rq0 /r5:8 Loading boot code from vmb.exe %BOOT-F-Unexpected Exceptio The 8600 simulator always seems to cut off the last character of its messages, I wonder if that's in any way related to the other console problems. 780, 750, and 730 have the same issue...along with not actually booting from the console RL, floppy, et al. The last character output in a message just prior to executing a HALT instruction is not surprising since the simulator implements a delay (as a number of instructions executed) from when the data is put in the output register prior to generating the completion interrupt/status. The halt instruction gets executed before the delay number of instructions have completed. Even if that was 'fixed', nothing operational would change. The reason the message has been generated will still exist. The latest github code will no longer drop the last character output just prior to executing a HALT instruction which returns to the sim prompt. Like I said above, nothing else changes though. - Mark _ Simh mailing list Simh@trailing-edge.com mailto:Simh@trailing-edge.com mailto:Simh@trailing-edge.com mailto:Simh@trailing-edge.com__
Re: [Simh] Standalone boot on vax8600?
On 2014-07-13 05:01, Henry Bent wrote: Here you go: http://occs.cs.oberlin.edu/~hbent/vaxultrix/boot.gz Thanks. I'll see if I have some time to look at it today. Johnny -Henry On 12 July 2014 22:57, Johnny Billquist b...@softjar.se mailto:b...@softjar.se wrote: On 2014-07-13 04:52, Henry Bent wrote: Sure, I'll work on getting an Ultrix image in a usable state so that I can upload it. Actually, thinking about it, it should be enough with just the boot file that you are using. Johnny -Henry On 12 July 2014 22:50, Johnny Billquist b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se wrote: On 2014-07-13 04:19, Henry Bent wrote: Cool, thanks. I figured out what's going on. The standalone programs are running, they just aren't displaying any input or output after the first character is printed. So if I do this: -- sim load -o boot 0 sim run 2 -- and then blindly type ra(0,0)vmunix, it boots! [...] Hmm hmm. I suspect I might know what is going on there. I'd have to test and play around some to verify, though. The console I/O on the 86x0 machines are a bit special, and I wouldn't be surprised if there were some issues in simh related to that. Mark, can we get some trace of all reads and writes to the registers related to the console? (There are four logical devices addressed on the 86x0 machines through the same CSRs.) Henry, if you could get such information logged, we could probably fix this pretty fast. Or else if you could just provide me with the files, I could test this myself as well. I don't have an old Ultrix image around, though. Johnny -- Ultrix V2.2 System #2: Wed Nov 18 01:14:13 EST 1987 real mem = 8388608 avail mem = 6888448 using 34 buffers containing 278528 bytes of memory VAX 8600, serial no. 1234, hardware level = 7 IO adapter 0 at address 0x2008 is an SBI adapter uba0 at address 0x20006000 uda0 at uba0 uq0 at uda0 csr 172150 vec 774, ipl 15 ra0 at uq0 slave 0 de0 at uba0 csr 174510 vec 120, ipl 15 mba0 at address 0x20012000 ht0 at mba0 drive 0 tu0 at ht0 slave 0 boot device not found root device? -- And I can then interact with the console, characters are displayed normally, etc. -Henry On 12 July 2014 19:33, Mark Pizzolato - Info Comm m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com mailto:m...@infocomm.com wrote: On Thursday, July 10, 2014 at 5:23 PM, Mark Pizzolato wrote: On Jul 10, 2014 2:02 PM, Johnny Billquist b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se mailto:b...@softjar.se wrote: On 2014-07-11 01:08, Mark Pizzolato - Info Comm wrote: On Thursday, July 10, 2014 at 3:13 PM, Cory Smelosky wrote: On Thu, 10 Jul 2014, Henry Bent wrote: Well, that at least did something different. sim boot rq0 /r5:8 Loading boot code from vmb.exe %BOOT-F-Unexpected Exceptio The 8600 simulator always seems to cut off the last character of its messages, I wonder if that's in any way related to the other console problems. 780, 750, and 730 have the same issue...along with not actually booting from the console RL, floppy, et al. The last
Re: [Simh] Standalone boot on vax8600?
On Thu, 10 Jul 2014, Henry Bent wrote: Well, that at least did something different. sim boot rq0 /r5:8 Loading boot code from vmb.exe %BOOT-F-Unexpected Exceptio The 8600 simulator always seems to cut off the last character of its messages, I wonder if that's in any way related to the other console problems. 780, 750, and 730 have the same issue...along with not actually booting from the console RL, floppy, et al. I tried the standalone boot on the other VAX sims (microvax 1, 2, 3900, and rtvax1000) and they are all able to load the booter and take console input (I didn't actually try booting). This seems to point to there being a problem with the console on the 8600. Any tips for where I should look to narrow down where the problem might be? -Henry -- Cory Smelosky http://gewt.net Personal stuff http://gimme-sympathy.org Projects ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] Standalone boot on vax8600?
On 2014-07-11 01:08, Mark Pizzolato - Info Comm wrote: On Thursday, July 10, 2014 at 3:13 PM, Cory Smelosky wrote: On Thu, 10 Jul 2014, Henry Bent wrote: Well, that at least did something different. sim boot rq0 /r5:8 Loading boot code from vmb.exe %BOOT-F-Unexpected Exceptio The 8600 simulator always seems to cut off the last character of its messages, I wonder if that's in any way related to the other console problems. 780, 750, and 730 have the same issue...along with not actually booting from the console RL, floppy, et al. The last character output in a message just prior to executing a HALT instruction is not surprising since the simulator implements a delay (as a number of instructions executed) from when the data is put in the output register prior to generating the completion interrupt/status. The halt instruction gets executed before the delay number of instructions have completed. Even if that was 'fixed', nothing operational would change. The reason the message has been generated will still exist. As for direct support for booting an OS from the console media, the 8600 supports BOOT CS /R5:xx to boot from the console RL02. Other than that, VMB.EXE is actually performing the boot operation and I think that when I checked VMB didn't know how to boot from console floppies on a 780, but it can boot from the console TU58 on both the 730 and 750 (BOOT TD /R5:xx). Well, I used to boot NetBSD on my 8650 by direct booting without VMB, Here is the COM file: ! ! Load 'boot.' and boot NetBSD. ! ! 'ra' MSCP drive type boot to multi user mode ! ! SET SNAP ON ! Enable ERROR_HALT snapshots SET FBOX OFF! System will turn on Fbox INIT! SRM processor init UNJAM ! UNJAM SBIA's and enable master sbia interrupts INIT/PAMM ! INIT physical address memory map DEPOSIT CSWP 8 ! Turn off the cache - System will enable cache !DEPOSIT R10 9 ! 'ra' MSCP drive type - uba0 - drive 0 !DEPOSIT R11 0 ! Software boot flags (multi user mode) DEP R0 11 DEP R1 20006000 DEP R2 2013f468 DEP R3 F! Unit number DEP R4 0 LOAD/START:0 BOOT. ! Load 'boot.' at memory location 0 START 60! Start 'boot.' at the address 60 But note, that is not not through VMB, so any discussions about R5 previously is not relevant here. Also, the start address is very much depending on the actual image loaded. Johnny -- Johnny Billquist || I'm on a bus || on a psychedelic trip email: b...@softjar.se || Reading murder books pdp is alive! || tryin' to stay hip - B. Idol ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] Standalone boot on vax8600?
On Jul 10, 2014 2:02 PM, Johnny Billquist b...@softjar.se wrote: On 2014-07-11 01:08, Mark Pizzolato - Info Comm wrote: On Thursday, July 10, 2014 at 3:13 PM, Cory Smelosky wrote: On Thu, 10 Jul 2014, Henry Bent wrote: Well, that at least did something different. sim boot rq0 /r5:8 Loading boot code from vmb.exe %BOOT-F-Unexpected Exceptio The 8600 simulator always seems to cut off the last character of its messages, I wonder if that's in any way related to the other console problems. 780, 750, and 730 have the same issue...along with not actually booting from the console RL, floppy, et al. The last character output in a message just prior to executing a HALT instruction is not surprising since the simulator implements a delay (as a number of instructions executed) from when the data is put in the output register prior to generating the completion interrupt/status. The halt instruction gets executed before the delay number of instructions have completed. Even if that was 'fixed', nothing operational would change. The reason the message has been generated will still exist. As for direct support for booting an OS from the console media, the 8600 supports BOOT CS /R5:xx to boot from the console RL02. Other than that, VMB.EXE is actually performing the boot operation and I think that when I checked VMB didn't know how to boot from console floppies on a 780, but it can boot from the console TU58 on both the 730 and 750 (BOOT TD /R5:xx). Well, I used to boot NetBSD on my 8650 by direct booting without VMB, Here is the COM file: ! ! Load 'boot.' and boot NetBSD. ! ! 'ra' MSCP drive type boot to multi user mode ! ! SET SNAP ON ! Enable ERROR_HALT snapshots SET FBOX OFF! System will turn on Fbox INIT! SRM processor init UNJAM ! UNJAM SBIA's and enable master sbia interrupts INIT/PAMM ! INIT physical address memory map DEPOSIT CSWP 8 ! Turn off the cache - System will enable cache !DEPOSIT R10 9 ! 'ra' MSCP drive type - uba0 - drive 0 !DEPOSIT R11 0 ! Software boot flags (multi user mode) DEP R0 11 DEP R1 20006000 DEP R2 2013f468 DEP R3 F! Unit number DEP R4 0 LOAD/START:0 BOOT. ! Load 'boot.' at memory location 0 START 60! Start 'boot.' at the address 60 But note, that is not not through VMB, so any discussions about R5 previously is not relevant here. Also, the start address is very much depending on the actual image loaded. All of these things can still be done with the simh VAX simulators. The default BOOT command operations setup and use VMB since that was the most common operation across 'most' deployed systems. What is done within the BOOT command is very much what Johnny's COM file does (init register values as need, load and start VMB). - Mark ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] Standalone boot on vax8600?
I got a console RL02 image from Quasijarus - the only one I could find easily - but I'm not sure what I'm supposed to do with it. All I get is this: -- sim boot cs /r5:8 Loading boot code from vmb.exe Please remove the volume from the console device. Insert the first standalone system volume and enter YES when ready: -- But that's neither here nor there at this point. The 8600 doesn't seem to be able to run any standalone utilities - they all print one character to the console and then stop. For example, copy and format: sim load -o copy 0 sim run 2 F sim load -o format 0 sim run 2 D While on any other vax simulator, I get: sim load -o copy 0 sim run 2 From: sim load -o format 0 sim run 2 Disk format/check utility Enable debugging (0=none, 1=bse, 2=ecc, 3=bse+ecc)? I haven't done any real testing of the qbus vax sims, I just verified that they could load and run standalone utilities. -Henry On 10 July 2014 19:08, Mark Pizzolato - Info Comm m...@infocomm.com wrote: On Thursday, July 10, 2014 at 3:13 PM, Cory Smelosky wrote: On Thu, 10 Jul 2014, Henry Bent wrote: Well, that at least did something different. sim boot rq0 /r5:8 Loading boot code from vmb.exe %BOOT-F-Unexpected Exceptio The 8600 simulator always seems to cut off the last character of its messages, I wonder if that's in any way related to the other console problems. 780, 750, and 730 have the same issue...along with not actually booting from the console RL, floppy, et al. The last character output in a message just prior to executing a HALT instruction is not surprising since the simulator implements a delay (as a number of instructions executed) from when the data is put in the output register prior to generating the completion interrupt/status. The halt instruction gets executed before the delay number of instructions have completed. Even if that was 'fixed', nothing operational would change. The reason the message has been generated will still exist. As for direct support for booting an OS from the console media, the 8600 supports BOOT CS /R5:xx to boot from the console RL02. Other than that, VMB.EXE is actually performing the boot operation and I think that when I checked VMB didn't know how to boot from console floppies on a 780, but it can boot from the console TU58 on both the 730 and 750 (BOOT TD /R5:xx). I tried the standalone boot on the other VAX sims (microvax 1, 2, 3900, and rtvax1000) and they are all able to load the booter and take console input (I didn't actually try booting). This seems to point to there being a problem with the console on the 8600. Any tips for where I should look to narrow down where the problem might be? What media have you tested with on the other (qbus) VAX simulators? - Mark ___ 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
Re: [Simh] Standalone boot on vax8600?
Might these umfinished operations cause problems? Unflushed disk buffers during shutdown for example. Original message From Mark Pizzolato - Info Comm m...@infocomm.com Date: 07/10/2014 5:08 PM (GMT-07:00) To Cory Smelosky b...@gewt.net,Simh s...@alohasunset.com Cc simh@trailing-edge.com Subject Re: [Simh] Standalone boot on vax8600? On Thursday, July 10, 2014 at 3:13 PM, Cory Smelosky wrote: On Thu, 10 Jul 2014, Henry Bent wrote: Well, that at least did something different. sim boot rq0 /r5:8 Loading boot code from vmb.exe %BOOT-F-Unexpected Exceptio The 8600 simulator always seems to cut off the last character of its messages, I wonder if that's in any way related to the other console problems. 780, 750, and 730 have the same issue...along with not actually booting from the console RL, floppy, et al. The last character output in a message just prior to executing a HALT instruction is not surprising since the simulator implements a delay (as a number of instructions executed) from when the data is put in the output register prior to generating the completion interrupt/status. The halt instruction gets executed before the delay number of instructions have completed. Even if that was 'fixed', nothing operational would change. The reason the message has been generated will still exist. As for direct support for booting an OS from the console media, the 8600 supports BOOT CS /R5:xx to boot from the console RL02. Other than that, VMB.EXE is actually performing the boot operation and I think that when I checked VMB didn't know how to boot from console floppies on a 780, but it can boot from the console TU58 on both the 730 and 750 (BOOT TD /R5:xx). I tried the standalone boot on the other VAX sims (microvax 1, 2, 3900, and rtvax1000) and they are all able to load the booter and take console input (I didn't actually try booting). This seems to point to there being a problem with the console on the 8600. Any tips for where I should look to narrow down where the problem might be? What media have you tested with on the other (qbus) VAX simulators? - Mark ___ 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
Re: [Simh] Standalone boot on vax8600?
On 2014-07-11 02:22, Mark Pizzolato - Info Comm wrote: On Jul 10, 2014 2:02 PM, Johnny Billquist b...@softjar.se wrote: On 2014-07-11 01:08, Mark Pizzolato - Info Comm wrote: On Thursday, July 10, 2014 at 3:13 PM, Cory Smelosky wrote: On Thu, 10 Jul 2014, Henry Bent wrote: Well, that at least did something different. sim boot rq0 /r5:8 Loading boot code from vmb.exe %BOOT-F-Unexpected Exceptio The 8600 simulator always seems to cut off the last character of its messages, I wonder if that's in any way related to the other console problems. 780, 750, and 730 have the same issue...along with not actually booting from the console RL, floppy, et al. The last character output in a message just prior to executing a HALT instruction is not surprising since the simulator implements a delay (as a number of instructions executed) from when the data is put in the output register prior to generating the completion interrupt/status. The halt instruction gets executed before the delay number of instructions have completed. Even if that was 'fixed', nothing operational would change. The reason the message has been generated will still exist. As for direct support for booting an OS from the console media, the 8600 supports BOOT CS /R5:xx to boot from the console RL02. Other than that, VMB.EXE is actually performing the boot operation and I think that when I checked VMB didn't know how to boot from console floppies on a 780, but it can boot from the console TU58 on both the 730 and 750 (BOOT TD /R5:xx). Well, I used to boot NetBSD on my 8650 by direct booting without VMB, Here is the COM file: ! ! Load 'boot.' and boot NetBSD. ! ! 'ra' MSCP drive type boot to multi user mode ! ! SET SNAP ON ! Enable ERROR_HALT snapshots SET FBOX OFF! System will turn on Fbox INIT! SRM processor init UNJAM ! UNJAM SBIA's and enable master sbia interrupts INIT/PAMM ! INIT physical address memory map DEPOSIT CSWP 8 ! Turn off the cache - System will enable cache !DEPOSIT R10 9 ! 'ra' MSCP drive type - uba0 - drive 0 !DEPOSIT R11 0 ! Software boot flags (multi user mode) DEP R0 11 DEP R1 20006000 DEP R2 2013f468 DEP R3 F! Unit number DEP R4 0 LOAD/START:0 BOOT. ! Load 'boot.' at memory location 0 START 60! Start 'boot.' at the address 60 But note, that is not not through VMB, so any discussions about R5 previously is not relevant here. Also, the start address is very much depending on the actual image loaded. All of these things can still be done with the simh VAX simulators. The default BOOT command operations setup and use VMB since that was the most common operation across 'most' deployed systems. What is done within the BOOT command is very much what Johnny's COM file does (init register values as need, load and start VMB). For completeness sake then, here is the command files to boot VMS and NetBSD, using VMB as well. (VMS, booting an RA disk over CI) -- ! ! Version: 001.000 ! ! CI PORT BOOT COMMAND FILE - CIBOO.COM ! ! This CI port boot command file is set up to boot from a CI ! device; for example, a HSC based disk. ! ! It assumes the CI780 is on SBIA #0, the TR level of the CI780 ! is set to 14, the HSC node number is set to 15 and the disk's ! unit number is 0. ! ! If any of these assumptions are not true for your configuration, ! you may still use this command file by entering the BOOT/NOSTART ! console command and then altering the appropriate register values ! when the console command prompt reappears. Use the console ! command SHOW BOOT.HLP/ASCII to get more information on how to ! use the BOOT/NOSTART command and R5 boot options. ! ! ! Operating System Disk:CI DEVICE ! ! SET SNAP ON ! Enable ERROR_HALT snapshots SET FBOX OFF! VMS will turn on Fbox INIT! SRM processor init UNJAM ! UNJAM SBIAs, Enable Master SBI interrupts DEPOSIT CSWP 8 ! Turn off the cache (VMS turns the cache on) ! DEPOSIT R0 20 ! Device Type is CI780 DEPOSIT R1 E! SBIA #0; TR number of the CI780 is 14 DEPOSIT R2 3! HSC port number 15 DEPOSIT R3 4! Unit number to boot from (in HEX) DEPOSIT R4 0! Logical block number to boot from if R5 bit 3 is set ! Use R5 for optional boot control flags DEPOSIT R5 0! Boot to multiuser. FIND/MEMORY ! Locate a 64KB chunk of good memory EXAMINE SP ! Display load address LOAD/START:@ VMB! Load VMB 200 bytes above the start of the good block START @ ! Start VMB at the load address And NetBSD, booting from an RA
Re: [Simh] Standalone boot on vax8600?
On 2014-07-11 02:41, Henry Bent wrote: I got a console RL02 image from Quasijarus - the only one I could find easily - but I'm not sure what I'm supposed to do with it. All I get is this: -- sim boot cs /r5:8 Loading boot code from vmb.exe Please remove the volume from the console device. Insert the first standalone system volume and enter YES when ready: -- That is expected. If you actually do this, you are expected to actually have the *system* on an RL02, that you will be booting from. As the normal console pack have all the diagnostics, boot images, microcode, and so on, there is no other system on that pack. This means that you are expected to replace the console pack at this point with another RL02 which contains some kind of a system. For normal VMS installations, this is how you initially install VMS. The second RL02 will contain STABACKIT, which is the standalone backup system. That is in turn used to restore from tapes to some actual other drive you have on the system, thus creating a bootable system disk. Unless you really are installing VMS from scratch, this is probably not something you want to do, or is what you thought you were doing. You probably want to boot from some actual disk you have, such as an RA disk attached to the machine. See my other mail about boot command files for the 86x0 machines. Oh, and I have never used Quasijaurus, so for that specific topic I can't offer any help. So you have a real physical 86x0 machine? Nice! Ping me off list, if you want to talk some more about it. Johnny But that's neither here nor there at this point. The 8600 doesn't seem to be able to run any standalone utilities - they all print one character to the console and then stop. For example, copy and format: sim load -o copy 0 sim run 2 F sim load -o format 0 sim run 2 D While on any other vax simulator, I get: sim load -o copy 0 sim run 2 From: sim load -o format 0 sim run 2 Disk format/check utility Enable debugging (0=none, 1=bse, 2=ecc, 3=bse+ecc)? I haven't done any real testing of the qbus vax sims, I just verified that they could load and run standalone utilities. -Henry On 10 July 2014 19:08, Mark Pizzolato - Info Comm m...@infocomm.com mailto:m...@infocomm.com wrote: On Thursday, July 10, 2014 at 3:13 PM, Cory Smelosky wrote: On Thu, 10 Jul 2014, Henry Bent wrote: Well, that at least did something different. sim boot rq0 /r5:8 Loading boot code from vmb.exe %BOOT-F-Unexpected Exceptio The 8600 simulator always seems to cut off the last character of its messages, I wonder if that's in any way related to the other console problems. 780, 750, and 730 have the same issue...along with not actually booting from the console RL, floppy, et al. The last character output in a message just prior to executing a HALT instruction is not surprising since the simulator implements a delay (as a number of instructions executed) from when the data is put in the output register prior to generating the completion interrupt/status. The halt instruction gets executed before the delay number of instructions have completed. Even if that was 'fixed', nothing operational would change. The reason the message has been generated will still exist. As for direct support for booting an OS from the console media, the 8600 supports BOOT CS /R5:xx to boot from the console RL02. Other than that, VMB.EXE is actually performing the boot operation and I think that when I checked VMB didn't know how to boot from console floppies on a 780, but it can boot from the console TU58 on both the 730 and 750 (BOOT TD /R5:xx). I tried the standalone boot on the other VAX sims (microvax 1, 2, 3900, and rtvax1000) and they are all able to load the booter and take console input (I didn't actually try booting). This seems to point to there being a problem with the console on the 8600. Any tips for where I should look to narrow down where the problem might be? What media have you tested with on the other (qbus) VAX simulators? - Mark ___ Simh mailing list Simh@trailing-edge.com mailto: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 -- Johnny Billquist || I'm on a bus || on a psychedelic trip email: b...@softjar.se || Reading murder books pdp is alive! || tryin' to stay hip - B. Idol ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] Standalone boot on vax8600?
On 2014-07-08 01:50, Henry Bent wrote: How are standalone programs loaded and run on the 8600? On the 7x0 I can do load -o boot 0 and run 2 and that will run a standalone boot. When I do that in the 8600 sim I get a newline and then the program just loops forever. Alternately, does anyone know the right way to load bootblocks on an ra disk in Ultrix 1 or 2 so that I can boot off of the disk directly? Everything I've tried just ends up giving a %BOOT-F-Unable to locate BOOT fil message from vmb.exe. VMB needs to have R5 set to specific values to boot Ultrix. If I remember right, bit 3 (0x8) needs to be set in R5 in order for VMB to just load the boot block from the device and start executing that instead of trying to look for specific files inside a Files-11 filesystem. But on a rel 86x0, you can also load other binaries from the console device, and just start them. For old versions of Ultrix, I seem to remember that this is what they did, before VMB gained the capability to boot from a boot block. Johnny ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] Standalone boot on vax8600?
On 08/07/2014 12:50, Johnny Billquist wrote: On 2014-07-08 01:50, Henry Bent wrote: How are standalone programs loaded and run on the 8600? On the 7x0 I can do load -o boot 0 and run 2 and that will run a standalone boot. When I do that in the 8600 sim I get a newline and then the program just loops forever. Alternately, does anyone know the right way to load bootblocks on an ra disk in Ultrix 1 or 2 so that I can boot off of the disk directly? Everything I've tried just ends up giving a %BOOT-F-Unable to locate BOOT fil message from vmb.exe. VMB needs to have R5 set to specific values to boot Ultrix. If I remember right, bit 3 (0x8) needs to be set in R5 in order for VMB to just load the boot block from the device and start executing that instead of trying to look for specific files inside a Files-11 filesystem. But on a rel 86x0, you can also load other binaries from the console device, and just start them. For old versions of Ultrix, I seem to remember that this is what they did, before VMB gained the capability to boot from a boot block. The value 8 is correct for R5. To boot this in simh use: sim b rq0 /r5:8 On a side note I think this flag is not required on later VAX system such as the MicroVAX II. The ROM code seems to work out what to do. 'load -o' is supported on the VAX 8600 so I suspect there is another issue. It could be a problem with the console device as I think someone has previously mentioned that there are some issues with my implementation (unless this been fixed now?) Matt ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] Standalone boot on vax8600?
On 2014-07-09 02:31, Matt Burke wrote: On 08/07/2014 12:50, Johnny Billquist wrote: On 2014-07-08 01:50, Henry Bent wrote: How are standalone programs loaded and run on the 8600? On the 7x0 I can do load -o boot 0 and run 2 and that will run a standalone boot. When I do that in the 8600 sim I get a newline and then the program just loops forever. Alternately, does anyone know the right way to load bootblocks on an ra disk in Ultrix 1 or 2 so that I can boot off of the disk directly? Everything I've tried just ends up giving a %BOOT-F-Unable to locate BOOT fil message from vmb.exe. VMB needs to have R5 set to specific values to boot Ultrix. If I remember right, bit 3 (0x8) needs to be set in R5 in order for VMB to just load the boot block from the device and start executing that instead of trying to look for specific files inside a Files-11 filesystem. But on a rel 86x0, you can also load other binaries from the console device, and just start them. For old versions of Ultrix, I seem to remember that this is what they did, before VMB gained the capability to boot from a boot block. The value 8 is correct for R5. To boot this in simh use: sim b rq0 /r5:8 On a side note I think this flag is not required on later VAX system such as the MicroVAX II. The ROM code seems to work out what to do. 'load -o' is supported on the VAX 8600 so I suspect there is another issue. It could be a problem with the console device as I think someone has previously mentioned that there are some issues with my implementation (unless this been fixed now?) I have played some with the simh 86x0 implementation, but I don't think I've checked much about the console device. But I don't think that should matter. Once you've loaded the binary from the console device, the console device isn't used any more on the real machine. Older versions of NetBSD used to boot that way, and you just loaded the boot file from the RL02, and started. And I seem to remember that it was started at address 2. But that of course depends on the boot image... And the boot image in turn knows how to read an FFS file system, and continued to load /vmunix from there (or whatever name for the kernel it was looking for). Johnny -- Johnny Billquist || I'm on a bus || on a psychedelic trip email: b...@softjar.se || Reading murder books pdp is alive! || tryin' to stay hip - B. Idol ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
