[Raion]

Upgraded to 256 meg I think you will find the system is perfectly useful. What type of CPU do you got there?

[colin_419]

I've got a MIPS R4400. When I was running IRIX 5.2, the system reported an R4400 @ 200MHz. My environment shows cpu frequency is set to 175 though, and now in IRIX 6.5.22 it is reporting the frequency as 175MHz. I might have to take a closer look at my CPU to know who made it. From what I read, Toshiba and others offered varying speeds. I didn't want to damage my CPU by turning it up the extra 25MHz to 200MHz.

I had such a blast last night exploring the demos on the machine. I played a few levels of DOOM, found the flipping screens demo that inspired Super Mario 64's menu, the flight simulator, all just so cool! I'm about to load it up with some developer tools and take a crack at writing some GL powered programs.

I also took a tour of the gallery here. The Album Pentium's Lair is so cool! I'll have to keep my eye out for some memory modules to upgrade my system. I take it coming across these modules might be a challenge, but I'll take a look here soon.

I'm starting my next job here soon as a software engineer at Nidec, and I was geeked when I saw Nidec on my power supply. Total coincidence haha

[Raion]

I did port a different version of Doom at one point and I might be able to redo that work if there's demand. The version of Doom included has no sound which is stupid in my opinion

[colin_419]

Oh that's cool! I was pretty bummed that I didn't hear E1M1 when it started. I've never played around with the DOOM source code but I'd love to check it out some time. I'm just about to transfer over all the N64 tools to my Indy. I've spent time doing GL 1.1 programming, but I'd really love to make something cool for the Indy or 64.

[Raion]

I ported chocolate Doom it compiles with mips pro with a few modifications to the source code. Can get the compiler from that download site that I sent you. As far as I can tell though zdoom won't actually compile so better stick to something like chocolate

[colin_419]

Thanks for the tips! I was reading some of the documentation here last night on using certain flags with the MIPS Pro compiler, citing that it was rather pedantic. Can't wait to get started and possibly share some things I've made for IRIX.

[Raion]

Let me know if you need any help. I've tried building a ton of stuff so I can tell you what's worth it and what isn't before you get started.

[vishnu]

If you're using MIPSPro, it's only compatible with the standard up to C99 - but Mips Inc. has assigned one of their professional programmers to the GCC project, so hopefully GCC will be able to do a much better job of compiling optimized code for Mips in the somewhat near future. EDIT: By the way, as I often point out, MIPSPro is available, with a working license, from my website:

smigt.org/m65

[robespierre]

There's no danger of damaging the CPU because its clock speed is not under software control. However, the code that reads the clock speed must know about all the possibilities to display the correct result, and it can be that the 175 MHz PM is too new for the system software you tried.

As an aside, I wouldn't try running a system below 5.3 on an Indy. There were some pretty severe performance problems in early 5.x releases, especially on the Indy, which was the subject of an infamous leaked memo.