[duchamp]

I have had some requests for this, so here it goes from my notes. I only patched Flint 8.3.4 because that was what I had a available, I think. Flame 8.3.4 should work the same, I guess. Possibly Flame 9. This is not an elegant patch, and could be refined, but my O2 is down atm. Flame 7 was about the same speed as Effect 7, just with more features. Flint 8.3.4 was noticeably slower at playback of the same footage on O2 compared to Effect/Flame 7.1. Just uploaded Flame 834 to the ftp.

Flame 7 OCT to run on O2/CRM
Offset of flame 7 binary
7d4498 
Replace 1080015d with 24040004
7d4a48
Replace 1040001b with 00 00 00 00 (patch CPU error) 
7d4a68
Zero out: 8f 84 81 ec 24 84 60 50 0c 59 e1 28 24 84 00 20 8f 99 f6 c8 00 40 20 25 0c 59 da d8 df a5 00 08

Flint 8.3.4 OCT to run on O2/CRM
9df0b4
Replace 10 c5 01 49 with 24 04 00 04
9df610
Replace 10 40 00 1b with 00 00 00 00 (patch CPU error) 
9df630
Zero out: 10 24 84 46 38 0c 7a a9 d0 24 84 00 20 8f 99 f3 70 00 40 20 25 0c 77 fc f0 df a5 00 08

---

Or try this simpler version
Flame 7
Offset
7d4498
Change 1080015d to 1580015d
7d4a48
Change 1040001b to 1580015d
7d4a60
Change 10400009 to 15400009

Flint 8.3.4
Offset 9df0b4
Change 10 c5 01 49 to 15 c5 01 49
Offset 9df610
Change 10 40 00 1b to 15 40 00 1b
Offset 9df630
Change 10 24 84 46 to 15 24 84 46

[gijoe77]

if you or someone with the skillset could write up a little how-to guide on how you were able to determine where to look and modify (was it just tracing through it in a dissembler like IDA pro or was it running it with some debugger or some other tool), that would be awesome too - I got plenty of IRIX software/plugins I need to crack/modify/explore

[duchamp]

It's a combination of Ida Pro and either TotalView debugger or CVD debugger for irix. IDA Pro takes you quite far. Find the main and license checkout function in ida, and then just step through and set relevant breakpoints in the debugger. Change some jumps which look relevant, and see which error messages you get. If you have a valid license (but locked to one machine) you can usually quickly see where the program needs to go with and without license. However most irix programs are not that difficult and based on the same flexlm 6.1 or similar.  Basically you find the lc_checkout function and patch it so it always goes to OK. Newer software had more complicated schemes, e.g. XSI 3, but fortunately most Irix software is from long before anyone expected such advanced tools as Ida Pro.

[gijoe77]

thanks, I followed along in IDA pro and patched flame 7.0 - its working on the o2 I saw the "GraphicsInit(void)" section and "dlGetCpuType(void)" sections, so made perfect sense.

I'm not too sure how to follow along with a debugger? Can you give me a real dummy's summary for stepping along in a debugger? (does TotalView need a license? I know CVD does, but I think we have that one covered)

---

funny thing I just learned also - flame 7.0 works with O2 video!  it worked with this in the init.cfg:

Code:

Video            O2Video, Serial1

It seems 8.3.4 wants a stonefs so I can't really tell with it (yet), I don't have any external storage handy atm. I didn't really have much luck getting Flame 8.3.4 running tho, I couldn't get past the CRIME error, here is what I edited

Code:

A749B4
10 c5 01 49     to     15 c5 01 49

A74F10
10 40 00 1b     to     15 40 00 1b

A74F28
10 40 00 09     to     15 40 00 09

I also tried, but it didn't help

Code:

a749c4
10 c7 01 26     to      24 04 00 04

I can provide the flame 8.3.4 Oct binary, or the entire install file if needed