Setup a "DINA" VM Network. Send files from PC to SGI INDY for N64 DEV!
Setup a "DINA" VM Network. Send files from PC to SGI INDY for N64 DEV!
Hi All,
I began the Process of setting up a Network connection between my PC and my SGI Indy in order to share files across the different file systems. This was primarily for some of my N64 related development. I set out to do this using the popular "DINA" VM image. So here is what I've done so far.

I made some sweet progress lately, and managed to get the PC laptop running the DINA VM.
I primarily followed some of the info laid out here from these links below to get DINA up and running:

after reading through the lot, I managed to get DINA  communicating over the network, to my INDY that is  running the IRIX v5.3 OS.

[Image: SGI_Ultra64_DEV_Board_Repair_000.JPG]

This was a bit of a pain to get the network running with IRIX 5.3. Most of the tutorials out there recommended using IRIX 6.5. So you'll notice alot of the documentation out there refers to this version.  Now for me, I was not performing the so called "Netboot" install.  I had already installed the IRIX OS using the SGI CD's. This was strictly for the need of establishing a Network connection from the INDY to a Windows PC so I can transfer IRIX software .tar files I had downloaded with my PC, over to the INDY while it was up and running.

So I had DINA up and running on my Laptop, I used the "Oracle Virtual Box" VM to load the DINA hard drive image.

[Image: IRIX_V53_DINA_NETWORK_72.jpg]

Now, just to make note...when you are assigning IP address's...
#1: The PC running the DINA VM, set its Ethernet card/Port to an IP of something like
#2: The DINA session in Oracle VirtualBox, make sure to select the "Bridged Network" mode in settings before booting the DINA image.
#3: Then bootup the DINA VM and go into the "Option #3 menu:  "Configuring the DINA IP address."
(If you find that the DINA image will not boot, or it crashes...try installing the Virtual Box and DINA image on a different PC or Laptop)

#4: Next, set the DINA session to its own unique IP address like
Make sure it is different compared to the one used by the Laptop or PC that is running the VM.

This is the whole reason you are using the "Bridged Network" mode in the VM. One IP address for the Laptop, and one IP address for the DINA VM....both will be using the same Ethernet card/Port on the Laptop running the VM.  I initially had the DINA VM set to the same IP address as the Laptop, and this did not work.

#5: Next, have the Subnet IP address range from Start to like Start IP: IP:

On the SGI INDY machine side...
Because I was running IRIX V5.3...some of the network settings have to be set by editing particular system files . As an example to set the Default Gateway for the network, there is no access to set this within the OS GUI for IRIX v5.3. You have to go in and edit one of the system files. (That being: /etc/rc2.d/S30network)


Once you set the specified variable in the code file, and re-save it, then the system will use these values for the network. The same goes for DNS server names. Specifics on these settings for IRIX 5.3 I found on this site here below:

Make sure to connect the Laptop running the DINA VM, the SGI INDY, and any other Windows PC's you want on this network....interface them together using a Network "HUB" and they should all be a part of the same subnet. So IP address's of
(NOTE:  If you use a Router....make sure to shut off the DHCP this will conflict with DINA is a DHCP service as well.)

[Image: IRIX_V53_DINA_NETWORK_74.jpg]

Once I had all these settings and hardware connections in place, I managed to gain access to the shared files and folder from the DINA drive image. (IRIX, FILES, and the NEKOWARE files.) As shown below:

DINA files access, over the network with another interfaced PC..........and also with my INDY running IRIX 5.3. [Image: biggrin.png] [Image: cool.png]

To access the DINA VM files with a PC on the network, simply click the windows Start button and select the "RUN" option.
in the run command entry space type the IP address for the DINA VM with the preceding back slashes, as shown below:    


[Image: IRIX_V53_DINA_NETWORK_53.jpg]

Now to get the SGI INDY to detect DINA, not only did I have to change the IRIX system files for the network settings, but I had to use the IRIX software program called "NFS Mount Manager".  This is accessed under: "TOOLCHEST > SYSTEM > NFS MOUNT MANAGER" menu.  You can review it's setup here at the link below under the "Overview of the NFS Mount Manager" heading.

Once I had all the settings in place, I was able to detect and share files across the INDY, to the DINA drive, and also to other PC's on the network. This will allow me to easily transfer files between the two, regardless of the different file systems.   [Image: biggrin.png]  

Here below are the settings I entered on the SGI INDY within the NFS Mount manager:

[Image: IRIX_V53_DINA_NETWORK_64.jpg]

Then once the Folders were Mounted, I had full access to the DINA files and other files from my PC's.
To avoid having to Mount the folders into NFS after each boot, there is a process for performing "AUTOMOUNT" at bootup. This I have yet to implement.
For some details on this, check out the link below:

IRIX 5.2 and 5.3

IRIX 6.5  (autoFS, Automatic Mounter)

[Image: IRIX_V53_DINA_NETWORK_68.jpg]

The really cool part about getting this DINA network that users who are simply wanting to use an INDY for nostalgic reasons...and just want to write and develop their N64 homebrew code on an can do just that with this setup. Once you compile the N64 ROM... you can easily use the DINA network to transfer the files over to a PC. Then feed the ROM over to your 64Drive Flashcart via USB.

If you wanted to get really could code a sweet script to automate the entire flow. This is really cool for those N64 Homebrew users who own an INDY, but don't actually own one of the rare Ultra64 GPIO dev boards.
This is the next best thing....and you get to use a sweet Vintage SGI machine to write your N64 code!!
Pretty  Sweet!   [Image: cool.png]

So now I'm off to install the rest of the required software packages for the N64 development environment.
Once I have that all installed and hopefully running, I'll report back with some further details and will probably have some questions too.

Cheers! Folks,
(This post was last modified: 04-20-2019, 08:38 PM by Gerry_MAN.)
N64 Hardware Fanatic

Posts: 17
Threads: 3
Joined: Aug 2018
Website Find Reply
04-20-2019, 08:30 PM

Forum Jump:

Users browsing this thread: 1 Guest(s)