Getting Flame 4 to run on Irix 5.3

Ginzanix

Member
Aug 28, 2019
52
92
18
Hi all!

I have almost finished a licensing patch for Flame 4.0.2 on Irix 5.3. This version is significant as the oldest Flame version which runs on R4000 cpus, on Irix 5.3, and the last to support pre-impact graphics. Actually it was made for the Onyx1 RealityEngine, but for some reason, there are functions in the binary which are specific for Indy XZ graphics (maybe leftover from Flint-testing?).

I have managed to pass the checks for RE-graphics, the MicroSentinel/UX dongle checks (Flame 4 does not have the later licensing), and patched the Stone hardware checks (any disk can be used for a Stone array - though Flame 4 can even use an ordinary disk). Now it hangs when setting up the framestore (both when Stone and file-based). I have done the patch using Mame/Indigo2 Irix 5.3, and my SGI O2 running Irix 6.5, so there may be hardware/emulation issues.

If someone could help me test this on original IRIX 5.3 hardware (Onyx1 would be perfect, but Indy/Indigo2 should work), I'd be grateful. I might be able to help with the media if you dont have it already (I own the orginal software disk, though no dongle unfortunately). Here is the patch for the flame_IRIX_5.3 binary:

Patch 0b60d8 10200040 to 14200040 to skip RealityEngine check.
Patch 0ca58c 304f0004 to 00000000 to enable Dongle debug, to print some interesting Dongle info (Dongle license contents)
Patch 0ca5cc 14800008 to 10800008 to skip INVALID DEVICE message
Patch 0ca5f0 8f99c9fc 0320f809 to 00000000 00000000 to avoid crash. Still DEVICE INVALID VERSION
Patch 441418 00001025 to 24020001 to enable all program licenses and get OK version. Still DEVICE ERROR
Patch 0ca640 0320f809 to 24020001 to skip check dongle mode, and set dongle mode to 01 (File) directly. Results in LICENSE NOT VALID FOR THIS MACHINE
Patch 440d30 00000000 to 24020001 to skip LICENSE NOT VALID FOR THIS MACHINE and startup Flame

You could just setup Flame with a file-based framestore, but if you want, here is a patch for Stone - possibly the old champro trick works even with this old version, though I didn't test it. Patch swr.o:

19C0 change 10400009 to 14400009 patch Stone lic check
1AA8 change 11200009 to 15200009 patch Stone lic check
1AD8 change 2401FFFF 1181000C to 24010004 1420000A patch Stone lic check
412C change 10400016 change to 14400016 patch check for STON+WIR label

For a filebased framestore, it seems you need to make a new file "/usr/lib/discreet/libioSA.cfg", with the text "-1", for some reason, or you will get "SharedArena" errors.

Let me know if it works!
 

kikems

Member
Jul 22, 2020
98
41
18
Spain
I'd try install in my Crimson Elan, but not works at first time, I need check installation y and try again. I'm not sure it works with Elan gfx board. Maybe someone with Indigo 2 can try it.
 
  • Like
Reactions: Ginzanix

Ginzanix

Member
Aug 28, 2019
52
92
18
I'd try install in my Crimson Elan, but not works at first time, I need check installation y and try again. I'm not sure it works with Elan gfx board. Maybe someone with Indigo 2 can try it.
Thanks for testing. Please post any error message you get, possibly I can fix it.
 

kikems

Member
Jul 22, 2020
98
41
18
Spain
Now I have Indigo2 in repair, when it works again, I'll try your Flame 4
 
Last edited:

kikems

Member
Jul 22, 2020
98
41
18
Spain
Finally I have my Indigo2 extreme graphics working again. I'd try to apply patch with patchfile executable but obtain "no valid license file".
This night I'll try reinstall and patch again.
I'd try with my Indy XL24bits but obtain corrupted graphics at startup flame, maybe with XZ works.
 
Last edited:

kikems

Member
Jul 22, 2020
98
41
18
Spain
Hi all!

I have almost finished a licensing patch for Flame 4.0.2 on Irix 5.3. This version is significant as the oldest Flame version which runs on R4000 cpus, on Irix 5.3, and the last to support pre-impact graphics. Actually it was made for the Onyx1 RealityEngine, but for some reason, there are functions in the binary which are specific for Indy XZ graphics (maybe leftover from Flint-testing?).

I have managed to pass the checks for RE-graphics, the MicroSentinel/UX dongle checks (Flame 4 does not have the later licensing), and patched the Stone hardware checks (any disk can be used for a Stone array - though Flame 4 can even use an ordinary disk). Now it hangs when setting up the framestore (both when Stone and file-based). I have done the patch using Mame/Indigo2 Irix 5.3, and my SGI O2 running Irix 6.5, so there may be hardware/emulation issues.

If someone could help me test this on original IRIX 5.3 hardware (Onyx1 would be perfect, but Indy/Indigo2 should work), I'd be grateful. I might be able to help with the media if you dont have it already (I own the orginal software disk, though no dongle unfortunately). Here is the patch for the flame_IRIX_5.3 binary:

Patch 0b60d8 10200040 to 14200040 to skip RealityEngine check.
Patch 0ca58c 304f0004 to 00000000 to enable Dongle debug, to print some interesting Dongle info (Dongle license contents)
Patch 0ca5cc 14800008 to 10800008 to skip INVALID DEVICE message
Patch 0ca5f0 8f99c9fc 0320f809 to 00000000 00000000 to avoid crash. Still DEVICE INVALID VERSION
Patch 441418 00001025 to 24020001 to enable all program licenses and get OK version. Still DEVICE ERROR
Patch 0ca640 0320f809 to 24020001 to skip check dongle mode, and set dongle mode to 01 (File) directly. Results in LICENSE NOT VALID FOR THIS MACHINE
Patch 440d30 00000000 to 24020001 to skip LICENSE NOT VALID FOR THIS MACHINE and startup Flame

You could just setup Flame with a file-based framestore, but if you want, here is a patch for Stone - possibly the old champro trick works even with this old version, though I didn't test it. Patch swr.o:

19C0 change 10400009 to 14400009 patch Stone lic check
1AA8 change 11200009 to 15200009 patch Stone lic check
1AD8 change 2401FFFF 1181000C to 24010004 1420000A patch Stone lic check
412C change 10400016 change to 14400016 patch check for STON+WIR label

For a filebased framestore, it seems you need to make a new file "/usr/lib/discreet/libioSA.cfg", with the text "-1", for some reason, or you will get "SharedArena" errors.

Let me know if it works!
I think can't understand how to apply "Patch 0ca5f0 8f99c9fc 0320f809 to 00000000 00000000 to avoid crash. Still DEVICE INVALID VERSION" with patchfile executable.
for example, if I need apply "Patch 0ca5cc 14800008 to 10800008 to skip INVALID DEVICE message" with patchfile I use:
./patchfile flame_IRIX_5.3 0x0ca5cc 0x10800008

but I not understand how to apply "Patch 0ca5f0 8f99c9fc 0320f809 to 00000000 00000000"
 

Ginzanix

Member
Aug 28, 2019
52
92
18
I think can't understand how to apply "Patch 0ca5f0 8f99c9fc 0320f809 to 00000000 00000000 to avoid crash. Still DEVICE INVALID VERSION" with patchfile executable.
for example, if I need apply "Patch 0ca5cc 14800008 to 10800008 to skip INVALID DEVICE message" with patchfile I use:
./patchfile flame_IRIX_5.3 0x0ca5cc 0x10800008

but I not understand how to apply "Patch 0ca5f0 8f99c9fc 0320f809 to 00000000 00000000"
Here is the updated patch with explanation

https://pastebin.com/qYR44LcZ

Seems to work in Mame/Indy, but I get some graphics errors - possibly due to emulation. Flame 4 actually has an "Indy"-mode, possibly leftover from Flint, with reference to XZ graphics, which I enable in the patch. Though I am not sure it completely removes the references to Onyx/RealityEngine. Let me know how it works!

indy-flame.png
 
  • Like
Reactions: kikems

kikems

Member
Jul 22, 2020
98
41
18
Spain
Now works in my Indigo 2 extreme gfx. I have some issues with paint module and render footage but I'm suppose it's because need some resource from Reality engine hardware. I need make more experiments with patches from Ginzanix like enable/disable Indy mode and similar things.
 

kikems

Member
Jul 22, 2020
98
41
18
Spain
After few test with Indigo2 extreme I think that Ginzanix made perfect fix for Flame4. The problem is that current flame 4 installation media is a Flame for RealityEngine hardware and not works good with other gfx systems.
Checking INSTALL SCRIPT I'm observe that it's an universal Installler for Flame4 and Flint4, first check if you have RE hardware, if it's available install some modules (like Paint) from Fire folder, if not detect RE hardware try to install equivalent modules but from Sparks folder ( the problem is taht these modules from Sparks folder it's not availables in the Flame ISO, I'm supose Sparks modules is for Flint ). Because these reasons some parts of Flame app not work properly without RE hardware.
I think that Ginzanix patch provide a full working and functional Flame4 for SGI computers with RealityEngine hardware, and it's very cool to preserve these historical software as working product for explore and enjoy. Other users without RE hardware ( using Ginzanix patch for skip RE checks ) can access to explore the software with limits and some not working features.

Here some pic examples with my Indigo2 extreme gfx. As you can see some images have corrupted rendered graphics because some modules try to use RE hardware, like paint screen only show white screen witout RE engine. Other modules like editing clips, import-export and few effects that only use CPU compute works perfect.
 

Attachments

Last edited:

kikems

Member
Jul 22, 2020
98
41
18
Spain
In the way to try to find a working version of Flame/Flint app for my Indigo2 extreme I'd try to install Flint 5.5 that works with my Octane 1 and O2 but not works with my Indigo2 because 5.5 need at least Solid Impact gfx system.

If someone have Flame4/Flint4 univeral CD ( I'm don't know if exist ), Flint 4 or flint 5.0 ( maybe 5.0 was the last version for pre-impact hardware ), please share. I'm sure that Ginzanix can help us to make it works for pre-impact systems.
 

kikems

Member
Jul 22, 2020
98
41
18
Spain
I can test Ginzanix Flame4 patch with Indy XZ and works like Indigo2, effects and options like paint that use graphic system show corrupted images, and cpu compute modules works. I think the patch really works if you have RE engine but for other systems with 3D engine but withtout hardware texture graphics like Extreme Graphics, Elan, XZ, etc... we need a Flint 4 patched version.
 

Ginzanix

Member
Aug 28, 2019
52
92
18
I can test Ginzanix Flame4 patch with Indy XZ and works like Indigo2, effects and options like paint that use graphic system show corrupted images, and cpu compute modules works. I think the patch really works if you have RE engine but for other systems with 3D engine but withtout hardware texture graphics like Extreme Graphics, Elan, XZ, etc... we need a Flint 4 patched version.
Hi kikems! Thanks for testing! Have you tried the new version 4.4.1I, which GIJoe posted? I think it may require Irix 6.2 and Impact graphics, but might also work on Indy. I can have a look.
 
  • Like
Reactions: kikems

kikems

Member
Jul 22, 2020
98
41
18
Spain
I'd test Flint 4.4.1i to install with my Indy XZ and run without ask for any additional hardware, of course I not have license and can't use it, but app start without hardware errors or alerts.
I think this flint can run for old gfx systems without texture hardware like Indigo 2 extreme, impact, Indy XL or Elan systems. It's for Irix 5.3.
 

kikems

Member
Jul 22, 2020
98
41
18
Spain
Finally with help of Ginzanix and GiJoe I can install and run licensed Flint4 with Indy XZ and works without any error or hardware alerts . Paint module and other effects that show corrupted images with Flame4 now works in Flint ( Flint is the small brother of Flame and require hardware with less specs ).

Some areas of app works too slow but works, maybe because I need more ram in my Indy, recomended ram for Flint is 256 Mb and I have only 128 Mb. I think Flint was never certified for Indy only for Indigo2 or up.

Now I need test with other SGI without texture hardware like Extreme graphics and Elan.
This version was cetified for Irix 5.3 but work with Irix 6.2 too ( you need coment 2 lines in INSTALL script for IRIX 6.x ).

It's awesome that after 30 years we can rescue this historical apps in working order to get the oportunity to explore and learn more about intial VFX apps for film and TV industries with help of IRIX retro comunity.
 

Attachments

Last edited:
  • Like
Reactions: Elf and Linux-RISC

kikems

Member
Jul 22, 2020
98
41
18
Spain
Just out of curiosity last night I loaded Flint4 on the Indy XL and as I imagined it doesn't work well without Z buffer hardware. The app initializes and apparently works, but some modules like paint and composer hang the app, yopu need at least Indy XZ. You can explore the app and it's possible use editing tools and some fx but the app it's not fully working.
Flame4 patched version it just doesn't start on Indy XL.
 

Ginzanix

Member
Aug 28, 2019
52
92
18
Just out of curiosity last night I loaded Flint4 on the Indy XL and as I imagined it doesn't work well without Z buffer hardware. The app initializes and apparently works, but some modules like paint and composer hang the app, yopu need at least Indy XZ. You can explore the app and it's possible use editing tools and some fx but the app it's not fully working.
Flame4 patched version it just doesn't start on Indy XL.
Thanks for testing again! I tried Flint 4.4.1I with MAME, which emulates XL graphics, and also got errors. I noted this quote from discreet.com (via archive.org), though I forgot where:

"Given the differences in hardware architecture between the Extreme/XZ and the Impact, many new features can not be implemented in a commercially viable way on the Extreme/XZ platform. Concretely, this means that FLINT 4.0.3 is the final version of FLINT software available on Indigo2 Extreme/XZ. Discreet Logic will continue to provide support for FLINT 4.0.3."

So, it is not surprising if experience errors (or slow performance) with Flint 4.4.1I, because it really expects there to be a Indigo2 with High or Max Impact/texture memory. But, possibly they didn't remove the support for XZ/Extreme graphics completely.
 
  • Like
Reactions: kikems

kikems

Member
Jul 22, 2020
98
41
18
Spain
Thanks for testing again! I tried Flint 4.4.1I with MAME, which emulates XL graphics, and also got errors. I noted this quote from discreet.com (via archive.org), though I forgot where:

"Given the differences in hardware architecture between the Extreme/XZ and the Impact, many new features can not be implemented in a commercially viable way on the Extreme/XZ platform. Concretely, this means that FLINT 4.0.3 is the final version of FLINT software available on Indigo2 Extreme/XZ. Discreet Logic will continue to provide support for FLINT 4.0.3."

So, it is not surprising if experience errors (or slow performance) with Flint 4.4.1I, because it really expects there to be a Indigo2 with High or Max Impact/texture memory. But, possibly they didn't remove the support for XZ/Extreme graphics completely.
Very interesting info, in that case I hope we soon or later find Flint 4.0.x iso to patch for our old XZ/Extreme systems, for now this Flint 4.4.1i is the oldest version we have working for Indigo2 Impact and Irix 5.3 or 6.2.
 
Last edited:

About us

  • Silicon Graphics User Group (SGUG) is a community for users, developers, and admirers of Silicon Graphics (SGI) products. We aim to be a friendly hobbyist community for discussing all aspects of SGIs, including use, software development, the IRIX Operating System, and troubleshooting, as well as facilitating hardware exchange.

User Menu