• Please review our updated Terms and Rules here

My research about graphics of the Pro

SVTK$ does something completely different.
Thank you. However I tried SVTK$ under RSX-11M+ v4.6 and P/OS v3.2 and it doesn't work. :( I used the next short code.
Code:
.mcall svtk$,exit$s
.psect code,i,rw
start: svtk$ vt,0
       exit$s
vt:  .word 0
.end start
Maybe I missed something. Any other help would be greatly appreciated.
 

Attachments

  • e1.png
    e1.png
    10.2 KB · Views: 4
RTFM
Code:
>DIR


Directory DU1:[SST]
2023-12-05 20:31

V4.MAC;1            1.         2023-12-05 20:31
V4.OBJ;1            1.         2023-12-05 20:31
MICROS.DIR;1        1.         2023-12-05 20:30
V4.TSK;1            4.      C  2023-12-05 20:31
TMP.LST;1           2.         2023-12-05 20:31
TMP.MAP;1           3.         2023-12-05 20:31

Total of 12./12. blocks in 6. files

>TYP V4.MAC
        .TITLE  V3
        .MCALL  SVTK$S, QIOW$S, EXIT$S
START:
        SVTK$S  #SSTT, #1
        TST     @#1
        EXIT$S
V4:
        RTI
SSTT:
        .WORD   V4
        .END    START
>RUN V4
>
 
Hi Andrew
Thanks for your questions.

Why? I don't know this. I just set the video mode partially there.

I don't use this but I suspect that it is rather BIS than MOV.

IMHO you need this if the natural delay might be too short for the op to complete.

It seems RSX-11 doesn't have means to catch trap 4. :( This makes my video card slot detection routine for RT-11 useless for P/OS. :( Maybe P/OS has another means... But, anyway .TRPSET has no usability for the further video ops. IIRC instead of the check of register 4 we can somehow use an interrupt. IMHO it is not very useful.
 
Lessee....I forget who's running which PRO machine in these discussions - but the PRO350, being 11/23ish in nature, doesn't trap on odd addresses. If it doesn't trap, SVTK isn't going to notice it. PRO380, being J11ish, does trap on odd addresses, so SVTK should catch the trap.
 
If the address is odd - no, there will be no interruption; if there is no response from the bus

there will be.
Ah s,orrry, I was thinking of the odd address line

TST @#1

in the example you posted a couple notes back.
 
I was thinking of the odd address line

TST @#1

in the example you posted a couple notes back.
This was just a demonstration of passing a V4 interrupt to a user task. Although, given the features of the F11 processor, it was probably worth choosing the option with - no reply from the bus.

In any case, both scenarios will work.
 
This was just a demonstration of passing a V4 interrupt to a user task. Although, given the features of the F11 processor, it was probably worth choosing the option with - no reply from the bus.

In any case, both scenarios will work.
For some value of works....one scenario (PRO350 or 11/23) works without ever triggering the thing you were trying to demonstrate....the code at V4 doesn't get executed.
 
For some value of works....one scenario (PRO350 or 11/23) works without ever triggering the thing you were trying to demonstrate
The question was that it was not possible to get SVTK$ to work in principle:
However I tried SVTK$ under RSX-11M+ v4.6 and P/OS v3.2 and it doesn't work.
and not - it works on the Pro380, but not on the Pro350 - and the answer was - no, everything works.

Also, if you look at the code for which it was necessary to handle the interrupt at М4, you can see that we are talking about a timeout on the bus - not odd address interrupt.

If the question was that it works on the Pro380 and doesn’t work on the Pro350, then the answer would be appropriate.

SVTK$ works for both scenarios. It does not have one entry point for the vector 4 interrupt and another for the bus no response interrupt.
 
Last edited:
For the hard drive, I first purchased a used ST-225 and it failed within a week. I then tried the PortaOne DREM (https://www.drem.info/), which uses an SD card and has an FPGA that you can use for FGPA development outside of its HD and floppy replacement function. It initially did not support my original 20 MB HD, but PortaOne has fantastic support and they modified the firmware. I eventually upgraded to the 67MB disk. There are two really nice features that I use. First, I can snapshot my entire disk at any time and I can make drives of different sizes. Like I said, I started with the original 20MB drive and then explored that largest drive the PRO can support, which is 67 MB. I have multiple copies of disks with different software and different OSs. If I screw up one, I simply delete the disk file and copy one from my library. No more installing systems via a stack of floppies and setting configurations. Second, the SD card is readable by any laptop and it is how I move files between my PRO, the Windows/Linux systems and the Internet. There was one hiccup with the DREM that was related to the HDD controller that we did not quite solve. I have two controllers. One has a ceramic processor and in order for the system to boot, I have to power up the DREM first. The other HDD controller with the plastic processor package is fine having them power up together, like a normal PC. So I swapped cards and boot from the HDD controller with the plastic package.
Interesting. I'm having no luck at all with a DREM on my Pro350. Any image that I put on it will boot and run properly exactly once. A shutdown or power cycle of the main system corrupts something and it will never boot again. I've tried with a separate power supply and no improvement. I've reported the issue to Oleksandr at PortaOne, but he is without a working Pro at this point. In the interim I switched over to a Gesswein mfmemu and things seem fine there.
 
My Pro is also upgraded to ST-225 .Yes I have the BCC-03 color cable. I have an Extron multi-sync video adapter. When my first VR-201 monitor went south I hooked the BCC-03 up to my Pro to try to get the grayscale signal to display on VGA through the Extron. No luck there. Any advice is appreciated.
I've been succesfully using an Extron RGB-HDMI 300A with my Pro 350 to display grayscale output. It handles sync-on-green transparently. What issues are you seeing?
 
RTFM
Code:
>DIR


Directory DU1:[SST]
2023-12-05 20:31

V4.MAC;1            1.         2023-12-05 20:31
V4.OBJ;1            1.         2023-12-05 20:31
MICROS.DIR;1        1.         2023-12-05 20:30
V4.TSK;1            4.      C  2023-12-05 20:31
TMP.LST;1           2.         2023-12-05 20:31
TMP.MAP;1           3.         2023-12-05 20:31

Total of 12./12. blocks in 6. files

>TYP V4.MAC
        .TITLE  V3
        .MCALL  SVTK$S, QIOW$S, EXIT$S
START:
        SVTK$S  #SSTT, #1
        TST     @#1
        EXIT$S
V4:
        RTI
SSTT:
        .WORD   V4
        .END    START
>RUN V4
>
Thank you. Your code works. So I could finish my program (P/OS) that lists the slot identifications. Maybe the Mandelbrot for P/OS will be made soon.
 
I've been successfully using an Extron RGB-HDMI 300A with my Pro 350 to display grayscale output. It handles sync-on-green transparently. What issues are you seeing?
From a DEC Pro 350 with monochrome, I used a BCC03 to BNC/VGA to Extron. The Extron did not display the monochrome image.
 
Mandelbrot for P/OS is ready.
Please help me to get results from real hardware. Just run the program in the benchmark mode two times with NOCALC=0 and NOCALC=1. For the Pro-380, set PRO380=1 and TWORSETS=1.
BTW P/OS gives only 16 KB for a privileged program. On the RT-11 we have about 32. And the LAND game is only available for RT-11...
 
Mandelbrot for P/OS is ready.
Please help me to get results from real hardware. Just run the program in the benchmark mode two times with NOCALC=0 and NOCALC=1. For the Pro-380, set PRO380=1 and TWORSETS=1.
BTW P/OS gives only 16 KB for a privileged program. On the RT-11 we have about 32. And the LAND game is only available for RT-11...
No luck on this yet. I typed it in, checked the code, ran it. It creates something in a second but the graphics is not displayed correctly. After quitting, characters are not displayed correctly. Don't know how to reset to correct text mode, have to reboot.
 
Back
Top