t0nyt wrote: Wed Oct 16, 2024 6:28 pm
But when I load the v1.4 ROM image in Q-emuLator and try to run Pascal it complains the ROM isn't present or is the wrong version
How do you load the ROM?
In QEmulator -> QL Configuration you must load the Metacomco ROM as "Back ROM" and set it to "Active"
I tested with v1.8 - there is no message that the ROM is loaded, but programs ED (editor) and Pascal (compiler) work.
Yes, other than being v1.4 that’s exactly what I’m trying
The ROM image can sit in the Rom Port or Back image section in Qemulator. On power the ROM defines a command in S*BASIC this loads the ROM routines into memory. Check thd manual out on the QL Home Page,
If you want to use SMSQ/E use the EPROM_LOAD command to load tge ROM file, I generally use DEV or SUB to map a psuedo MDV device to the compiler or use MDI or FDI to use a MDV or FLP image.
The ROM image can sit in the Rom Port or Back image section in Qemulator. On power the ROM defines a command in S*BASIC this loads the ROM routines into memory. Check thd manual out on the QL Home Page,
As far as I can see, tested with v1.8:
- it works as Back ROM
- it does not work as Ext ROM
- there is no PRL command
- in v1.8 the command is: ROM
- if the ROM is loaded as Back ROM then programs Ed and Pascal work even if the command ROM is not issued. (the programs start without any error message - but I have not tried to actually compile anything)
The ROM image can sit in the Rom Port or Back image section in Qemulator. On power the ROM defines a command in S*BASIC this loads the ROM routines into memory. Check thd manual out on the QL Home Page,
As far as I can see, tested with v1.8:
- it works as Back ROM
- it does not work as Ext ROM
- there is no PRL command
- in v1.8 the command is: ROM
- if the ROM is loaded as Back ROM then programs Ed and Pascal work even if the command ROM is not issued. (the programs start without any error message - but I have not tried to actually compile anything)
Thanks Andrew
If I load v1.8 Rom then “ROM” works, but not with v1.4 Rom
I guess there may be a corruption in my v1.4 Rom or MDVs