Latest Threads

Forum Statistics
  • Forum posts:8,421
  • Forum threads:1,239
  • Members:620
  • Latest member:Spooky

Posted by: stormy
05-30-2019, 05:21 PM
Forum: Beginners' Questions/Tips
- Replies (2)

Just wondering how to save my desktop gamma, the default 1.3 is way too high and need to lower it to 1. I can change it in the display settings but how can I save this upon every reboot? When going to save settings I'm not sure where or what file name to use.


Print this item

Posted by: kaigan
05-30-2019, 04:53 PM
Forum: Hardware/Triage/Repair
- Replies (10)

The MAME emulation team is in serious need of additional Indy ROM images! Please don't re-flash your original EPROM without first confirming its version and reading out a copy of it with a programmer to be submitted to the collection. They currently have images B4, B6, and B10. All others are needed for archival. If your ROM version is not one of these, please get in touch with the MAME team.

There are two ways to get the ROM file, depending on if the EPROM has been removed from the system already or not. If it hasn't, see dexter1's post below mine for an easy way to dump the ROM from the console. If the chip is out of the system, instructions on reading and saving your ROM image with an EPROM programmer are in Addendum 1 on my second post.

Need an upgraded EPROM but don't want to go through the whole process? Send me a PM. I have a small supply of pre-programmed chips that I can provide for $5+shipping.

I recently upgraded the PROM in my Indy in order to support R5000 processors. This is a fairly straightforward process, but it is possible to make mistakes. If you attempt the instructions presented below, please be sure you read and understand them fully before proceeding. While I'm happy to provide assistance on the process, I can't be held responsible if you break something on your Indy while trying the upgrade.

Required Equipment

  • An EPROM programmer. I personally like the TL866ii Plus. They're available on Amazon or eBay, usually for around $45-$60 USD. Other models will likely work, but may involve different methods. This tutorial's instructions are explicitly for this programmer. Previous models in the TL866 series should also work.
  • A 27C4096-120 (or faster) EPROM. eBay sellers usually have them for $2-$3 USD each, but may only sell in batches of 5 or more.
  • The updated ROM image for the Indy. Although this is available on the Internet with some searching, that version will not work with the TL866ii Plus without modification. (We'll discuss why that ROM image doesn't work below.) Instead, I recommend using the prepared ROM in the attachments.
  • Basic tools and other supplies, including a Phillips screwdriver, a socket driver or pliers, and opaque tape to cover the EPROM window.

Optional Equipment

  • An R5000-series CPU module, as that's the main reason to perform this upgrade.
  • A UV EPROM eraser. I bought a cheap model from Amazon. I recommend this, as it will be the only way other than flashing multiple chips to correct any mistakes you may make in the flashing process.
  • An IC removal tool. This isn't strictly necessary, but it helps for removing the existing EPROM from the Indy. You can also use a flathead screwdriver, but I don't recommend it. It's very easy to break something and IC removal tools are inexpensive.
  • High-percentage isopropyl alcohol. This is only really needed if you're re-using an EPROM that's already had a sticker on it, or if you made a mistake and need to erase the chip. Cleaning the window with alcohol lets more UV through and speeds up the erasure process.

Required Software

  • Drivers (for Windows) and flash software for the TL866ii Plus, available on AutoElectric's web site here:
  • For Linux and MacOS systems, Wine. FOSS software does exist for the TL866-series of programmers, but I still recommend running the Windows application via Wine at this time. If you're using the software through Wine, you'll also need the setupapi.dll file available here: Some tweaks may be required for MacOS. Unfortunately, I'm currently unable to test the software on a Mac.

Let's Program an EPROM!

  1. Download and extract the software and drivers for the TL866ii Plus from the link above. Install the software and approve the driver installation when prompted.

  2. Insert your 27C4096-120 or equivalent EPROM into the programmer. Be sure to match the notch in the chip with the direction indicated on the programmer when inserting the chip. Then, lower the lever to lock the chip into place. Finally, plug the programmer into your computer via USB.
    [Image: 26n6oWx.jpg]

  3. Load the software. On first boot, you may receive a message stating that the programmer firmware is out of date.
    [Image: 47bdYbX.png]

    If you see this, after closing the prompt, select "Tools -> Reflash Firmware". You'll receive a dialog box that looks like the one below. Select "Reflash" and wait for the process to complete. At this point, close the dialog box and the software. You can then reload it.

  4. With the programmer firmware up to date, you'll be greeted with the main window upon closing the software.
    [Image: UfkbpjK.png]

  5. Click on the large button below the words "Select IC" in the top left of the main window. This will open a dialog box allowing you to select the type of chip being used in the programmer. Depending on the manufacturer of your particular EPROM, you may be able to find their variant of the 27C4096 in the list of vendors and names. If not, I recommend just selecting the AMD version, the AM27C4096 @DIP40. The specific model is only relevant for a check that we'll disable in the next step. The image will still burn properly. One you have the chip selected, click "Select".
    [Image: XTusWpr.png]

  6. In the bottom left of the main programmer window, uncheck the checkbox labeled "Check ID". This will allow the programmer to read, write, and verify data on the chip even if it isn't an exact match to the manufacturer. The rest of the settings can be left at their defaults.
    [Image: IPgi1L1.png]

  7. At this point, we need to make sure that the EPROM is blank before we program it. To do this, in the main programmer window, go to "Device -> Blank Check". Click the "Blank" button to begin. If the chip is not blank, you will see a message like the one below. In this case, you will need to use a UV EPROM eraser or select an alternate chip to program.
    [Image: CQz5zKB.png]

    If the chip is blank, you will instead see a window resembling the one below. At this point, you can select "Cancel" to exit the dialog.
    [Image: iullF95.png]

  8. We're almost ready to program the EPROM! Extract the indy_rom_011.tar.gz file from the attachment, which should be named indy_rom_011.bin. Then, in the programmer window, select "File -> Open" and select the .bin ROM file you just extracted. A new dialog box resembling the one below will appear. Leave all settings at their defaults.
    [Image: V3ItcAA.png]

  9. In case you didn't obtain the file from the attachments below (and, ideally, just for good measure), we should make sure that the data is correct before we burn the EPROM. Using the scrollbar on the right side of the main programmer window, scroll down and look at the "ASCII" column. Eventually, you should find readable text, like the example below.
    [Image: 8B4NR7Z.png]

    If, instead, the text appears to be jumbled, like in the example below, then the ROM file you have needs to be byte swapped in order to work with this programmer. Byte-swapping the Indy ROM file is currently outside the focus of this tutorial, but instructions will likely be included at a later date.
    [Image: ocIZISW.png]

  10. With this done, go to "Device -> Program". A dialog box like the following one will appear. Upon clicking the "Program" button, the device will begin the programming process. This will take a few minutes. Upon completion, a verification pass will be run. You should receive messages like the ones below indicated successful programming and verification. Once complete, you can click "Cancel" to close the dialog box.
    [Image: JJfoTrQ.png]

  11. At this point, you can close the programmer software and disconnect the programmer device from your computer's USB port. Then, raise the lever to allow the removal of your newly-burned EPROM.

  12. In order to preserve the data burned to the EPROM, a sticker or piece of opaque tape should be placed over the window on the top of the EPROM. This prevents any potential strong UV light from erasing the data on the chip. While this isn't generally much of a concern unless you're burning EPROMs out in the sun or shining bright lights inside your Indy, it's still best practice.

    Note: the chip in the image below is the original, re-flashed EPROM from my Indy. The 27C4096 is a newer, equivalent EPROM to this one.
    [Image: RcYqHc5.jpg]

Installing the EPROM in Your Indy

  1. Now that we have an actual EPROM burned, it needs to be installed into the Indy. To start, remove the cover from the top of your Indy. This can be done by applying a small amount of downward pressure on the black clip on the back of the Indy, while applying forward pressure on the blue tab on the cover. The cover will slide forward, revealing internals similar to the ones below.

    Note: my Indy has a SCSI2SDv6 installed in the top left. Yours will likely have a SCSI hard drive and sled in its place.
    [Image: osdt5nm.jpg]

  2. In order to install the new EPROM, the graphics board (in the bottom left) will need to be removed. This will vary depending on the model of graphics board installed in your Indy. In the case of this 24-bit module, two of the long standoffs and one screw need to be removed. Also, the two lugs on the sides of the 13W3 connector also need to be removed. With the board out of the way, the EPROM below is revealed, just beneath the two graphics board connectors. I've left the EPROM window clear in this example picture for better illustration. In a stock Indy, this will be covered by a white or yellow label indicating the EPROM version.
    [Image: of9dNt9.jpg]

  3. Using an IC extractor tool, carefully wedge each end of the tool underneath one of the short sides of the EPROM. Gently pull up until the chip is unseated from its socket.

  4. With the stock EPROM removed, the socket below is ready to accept the newly-burned chip. Again, be sure to align the notch in the chip with the notch in the socket when inserting the new EPROM. If you install it backwards, it's possible that damage to either the EPROM or the motherboard could occur. On my Indy, the notch on the socket is toward the inside of the board. However, be sure to verify this on your own board.
    [Image: 15CdiRT.jpg]

  5. With the new EPROM in place, you can reverse the disassembly steps to reinstall the graphics board and close the Indy. Plug it in, and if all goes well, the light will turn green and you'll hear the lovely startup chime!

  6. To confirm the upgrade to the PROM, you can halt the boot process and enter the Command Monitor. Type the version command. You should receive the following result: PROM Monitor SGI Version 5.3 Rev B10 R4X00/R5000 IP24 Feb 12, 1996 (BE)
... and that's the installation! If you run into any issues during the process, or have any questions, please post them below. I'll try to help out with issues as best as I can.

Print this item

Posted by: praetor
05-30-2019, 03:21 AM
Forum: Development/Porting
- Replies (5)

Howdy y'all

I was wondering if any of you knew anything about the Pascal compiler that SGI had. It's not in the latest MIPSPro, and I'm not sure if it's in the MIPSPro or if it's part of the IDO, which would kinda suck.

Any info anyone can provide would be apprecaited!  Big Grin

Print this item

Posted by: cj_reha
05-30-2019, 03:08 AM
Forum: Hardware/Triage/Repair
- Replies (1)

Hello all -

I recently acquired an Indy R5000 for a pretty good price at the VCF East convention earlier this May; however, when I tested it, both red and green power lights lit up for a second or so before the protection circuit seemingly kicked in, the system turned off, and a foul smell started filling the room. I assumed this was a power supply issue, but after opening it, I discovered it has a Sony unit installed - these supplies are considered quite reliable.

Tonight I finally pulled it apart to do a more in-depth diagnosis, and discovered a fried tantalum capacitor on the bottom of the motherboard, labeled as C602 by the reference designator. The cap is unfortunately so baked that I can't discern what its value is, and the capacitors nearby are all different values and sizes. Would anyone happen to have a bare Indy logic board laying around? I'd love to figure out what the value is and see if I can get the Indy to work again.


Update: got the value! A very generous Indy owner sent a photo via Discord. The value appears to be 20v 4.7uF...solved!

Print this item

Posted by: Dylanear
05-30-2019, 01:51 AM
Forum: Hardware/Triage/Repair
- Replies (7)

I'm curious if anyone has any really old SGI hardware booting and running? Personal Iris perhaps? Old twin tower Iris 4D systems? 

What's the oldest hardware anyone on here is running?? 

I wonder if there's any 3000 series running anywhere in the world? Surely not any 1000 or 2000 series terminals? I'd kill to see a 3130 running Alias 1.0 on MEX again!

Print this item

Posted by: Krokodil
05-29-2019, 09:04 PM
Forum: SGI Discussion
- Replies (12)

Here's my Octane II named Algogulf. I got it about 3 years ago from a guy in Surrey BC, apparently from a studio named Rainmaker Entertainment. It cost me about $600 USD or about $800 CDN at the time. Would've been a bit cheaper, but I believe there was a bit of a bidding war with some other guy on Ebay.

The specs of it are: Dual 600MHZ R12000 CPU, 2.5 GB RAM, 137GB SCSI HDD, V12 Graphics card, DCD module, card cage with a fiber optic NIC and a couple of other things that I'm not sure what they are, one of them might be something to due with FibreChannel and in the XIO slots something that might be a VBOB and something XMenet. I'd say it's pretty loaded and I'm proud to have it. Lol. That "TURBO" logo came with it.

[Image: gk2hGE4.jpg]

[Image: sBISQQ4.jpg]

Print this item

Posted by: chulofiasco
05-29-2019, 07:03 PM
Forum: IRIX/Software
- Replies (4)

I've got an Indigo2 and a Mac MIDI interface.

How can i configure the second serial port to function for MIDI, and what midi utilities should I find under IRIX 6.5?

Any help would be appreciated. 

Thanks !

Print this item

Posted by: Raion
05-29-2019, 03:12 PM
Forum: Site Discussion
- Replies (18)

We lost a little bit of ourselves. Not a day goes by where I don't think about that place. May 20th 2018 will forever be a day in my memory. 

I guess it's a perfect time to detail my experience, and exposure, into SGI:

I was 19 years old and working for a company called InMotion in Virginia Beach. I met a curious guy there with a bright red workstation and a small light blue slab at his desk. His name was Will, but he was known on as "thebulbguy". He was their Tier 3 Network Engineer, and I became fast friends with him. He began telling me about these "SGI" computers. At the time I was into Amigas and old PowerPC macs, so he had my attention. 

I then found two Personal Iris 4D/35s local in Chesapeake. I went and grabbed them, and was completely at a loss with what to do with them. I signed up on Nekochan, and well, learned I had pretty much useless machines for major enthusiast work. So I gave them to Will, and he used them for parts for his personal irises. 

I later grabbed an octane and became super active in 2014, and despite an emotional meltdown that had nothing to do with the site and everything to do with negative, shitty people I lived with in 2015, I was a regular user up until the day it died. I wasn't ever really interested in the 3D graphics. I was always interested in the OS itself, and its uniqueness. I even daily drove IRIX for about 2 months on a dual 300MHz Octane. 

I never saw myself as willing to take up the mantle, tbh, that Pete had left behind. This site's original purpose was a smaller alternative discussion that allowed for sales of commercial software, something Nekochan never allowed. 

Then all of us were blindsided by Peter's sudden decision to shut down. I don't know all of the facts, but I do know he had been troubled by running the site for some years, his interests have drifted to other microcomputers. And as of late we had a lot of controversy on the site, too, with users throwing around insults at each other constantly, people trying to "expose" us on /r/conspiracy etc. Nobody knows how this must have weighed on Peter's mind. 

It's been hard, but we've bounced back. We recently surpassed 600 forum members. This is all a good thing. 

Eventually, I hope to start offering more services and have more things people look for from a community like this. Make it the best we can be.

Print this item

Posted by: stormy
05-26-2019, 06:10 PM
Forum: Beginners' Questions/Tips
- Replies (8)

Hey guys,

I've been trawling the internet to try and find answers but everything I try doesn't work, so I'll ask here! It might be a quirk of Irix. I can mount the folder but it is read only, I just get 'permission denied' when trying to write from my Linux machine.

I am trying to:
* Share /Desktop/Downloads on my Octane via NFS
* Mount the SGI /Desktop/Downloads on my Arch Linux machine
The IP of my Linux:
The IP of my SGI:

Here is my /etc/exports for Irix:
/Desktop/Downloads -rw=

Here is my /etc/fstab for Linux:   /mnt/sgi   nfs   defaults,rw,timeo=900,retrans=5,_netdev    0 0

When accessing /mnt/sgi on my Linux machine, the contents do show up, but I cannot write or make files/folders. When checking permissions they say root/root in the terminal.

showmount -e
Export list for
/export/opt/       (everyone)
/Desktop/Downloads (everyone)
^ when checking with the showmount command on Linux

Any ideas out there? Thanks Smile

Print this item

Posted by: stormy
05-26-2019, 12:49 PM
Forum: Beginners' Questions/Tips
- Replies (1)

Hey guys,

My octane seems to have a weird gamma bug where sometimes the login prompt will load with very bright washed out gamma, when logging in this stays the same on the desktop. To fix it I just log out and back in again a few times until it goes back to normal. 

Any thoughts?


Print this item