From Newsgroup: comp.sys.apple2

I've sometimes run into the occasional program that crashes or
malfunctions on an Apple //c or a Laser 128. So some time ago I had the
daft idea of trying to get the Enhanced //e ROM running on both.

Obviously, it's not quite as easy as just putting the right ROMs in the
right place, or there seems to be differences between how all 3 systems bankswitch the ROMs.

I know it's a stupid idea but it's something I would like to experiment
with.

-uso.
--- Synchronet 3.18b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.apple2

It sounds like you need a ROMX from theromexchange.com.
--- Synchronet 3.18b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.apple2

On Fri, 11 Jun 2021, qkumba wrote:

It sounds like you need a ROMX from theromexchange.com.

That actually seems to have nothing to do with what I'm trying to do. o.o

(Also, I use emulators to test my ideas.)

-uso.
--- Synchronet 3.18b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.apple2


On Thursday, June 10, 2021 at 7:36:35 PM UTC-6, Steve Nickolas wrote:

I've sometimes run into the occasional program that crashes or
malfunctions on an Apple //c or a Laser 128. So some time ago I had the
daft idea of trying to get the Enhanced //e ROM running on both.

Obviously, it's not quite as easy as just putting the right ROMs in the right place, or there seems to be differences between how all 3 systems bankswitch the ROMs.

I know it's a stupid idea but it's something I would like to experiment with.

You don't say if the programs that crash work on an enhanced IIe, or just regular IIe. That would probably mean usage of an unsupported opcode that doesn't work on enhanced machines.
I know the CALL -3100 command to enable graphics doesn't work on the Laser. Not sure about the IIc.
Are we talking all programs with graphics, the ones that crash that is? A list of the programs that don't work would be handy.
Although I understand where you are going. I had the same thought at one time to install a IIe ROM into my Laser for more compatibility.
Instead of changing the ROM though, probably an easier idea might be to install the enhanced ROM's software into the Laser or IIc's Auxilliary Language Card, set the soft switches that puts the Auxiliary memory in control and run the software from there. The only time it won't work is if the programs are booted from disk.
--- Synchronet 3.18b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.apple2

On Fri, 11 Jun 2021, I am Rob wrote:

You don't say if the programs that crash work on an enhanced IIe, or
just regular IIe. That would probably mean usage of an unsupported
opcode that doesn't work on enhanced machines.

I compared with an enhanced //e. I don't generally test stuff with the
1982 firmware.

I know the CALL -3100 command to enable graphics doesn't work on the
Laser. Not sure about the IIc.

CALL -3100 works on the //c, meaning it has to do with differences in the BASIC (as F3E4 is in BASIC space) rather than differences in the monitor.

Are we talking all programs with graphics, the ones that crash that is?
A list of the programs that don't work would be handy.

I haven't tested everything. I do know Cubit is one of the problem games
(and it has to do with using an illegal entry point, FB81, according to documentation in my replacement ][+ monitor).

Although I understand where you are going. I had the same thought at
one time to install a IIe ROM into my Laser for more compatibility.

I'm sure the thought wasn't uncommon among people who have used Lasers. (I first had the thought back in 1996.)

Instead of changing the ROM though, probably an easier idea might be to install the enhanced ROM's software into the Laser or IIc's Auxilliary Language Card, set the soft switches that puts the Auxiliary memory in control and run the software from there. The only time it won't work is
if the programs are booted from disk.

For Cubit, you can do that with the ][ or ][+ ROM.

-uso.
--- Synchronet 3.18b-Win32 NewsLink 1.113