SGI: Development

I just bought an Octane 2 and am very new to Irix but I'm learning.

first, thank you to everyone that's worked at getting a modern browser up and running on Irix/SGI. It's been 30 years since I used Unix and it's coming back, albeit slowly. I love the machine and am learning to love the OS as well.

My Octane had Mozilla 1.x.x that did work and was stable. It was relatively fast and really didn't have many issues when I used it. I just updated to FF 3.0.19 and have it running. I'm having some issues that are outside my knowledge with the OS and, as much as I hate to post, I really could use some help. 3.0.19 is running slow and erratic. I have areas that turn black when the cursor moves over them and data input boxes that will black out when I try to type something in. The browser is very slow as well. I assume I have either a conflict or outdated supporting file somewhere but, like I mentioned, I'm not up to speed at that level to fix it. I am a fast learner though.

If anyone has run into this and can offer up some help I'd appreciate it. My goal was to wipe the OS (which I just did) and install FF to use and get familiar with. This is the last piece of that puzzle and then I'll be doing more work at learning more about IRIS so I'm eager to fix this issue. Please keep in mind that I'm a base level newby.

Thanks so much!

Have you set the xserver to use 24-bit color? http://www.nekochan.net/wiki/True_Color

Changing the color depth didn't work but fixpath did.

I assume I did this correctly... I uncompressed the neko_fixpath.tar.gz file that was on the desktop then dragged it onto the firefox icon. I guess that since I'm not getting these blacked out areas that it went as it was suppose to.

Vladio wrote: I assume I did this correctly... I uncompressed the neko_fixpath.tar.gz file that was on the desktop then dragged it onto the firefox icon. I guess that since I'm not getting these blacked out areas that it went as it was suppose to.

Umm, yes, well ... errr ... I don't think so.

I'm pretty sure that neko_fixpath is a script to automate adding nekoware to your path. If nekoware comes first, then the /usr/nekoware apps and libraries get used (if they exist) in preference to the older Irix ones. Most of nekoware will need this to function. You could do the same thing by hand if you want, neko_fixpath is just a handy way to accomplish that.

Not sure what you actually did, but I don't think it will have the effect you want

It's interesting that you saw a change tho. I wonder what fireflop did with that script ? Or fireflop never saw it, Irix tried to open flopsy with that script as an argument and the script accidentally got run as a side-effect ? Any of you script-masters out there have an idea ?

It's interesting that you saw a change tho. I wonder what fireflop did with that script ? Or fireflop never saw it, Irix tried to open flopsy with that script as an argument and the script accidentally got run as a side-effect ? Any of you script-masters out there have an idea ?

Too scary for me to even try, who wrote neko_fixpath? There should at least be a few comment lines at the top of the script that says what it's supposed to do. And anyway, if all it's supposed to do is put /usr/bin/nekoware at the top of your path, you can do that with a single line in your ~/.profile:

it's actually /usr/nekoware/bin but either way a good idea to set your env vars yourself instead of having any script mess with them

foetz wrote: it's actually /usr/nekoware/bin but either way a good idea to set your env vars yourself instead of having any script mess with them

Yup that was a typo, I meant /usr/nekoware/bin ...

haha you shall be forgiven

foetz wrote: haha you shall be forgiven

After making amends. 50 pushups, pledge !

I installed Firefox3 from Nekoware/stable using nekosync on my 'new' Octane/SSI (fresh install of 6.5.16 then patch 5086 then update to 6.5.22). On start I get:


Firefox2, on which I'm typing this, is running flawlessly.