[legodude]

I'm having trouble getting the Galileo software installed
I did a fresh install of 6.5.22 from Reanimator using default options
I downloaded Galileo 6.5 from Ian's site:
http://sgidepot.co.uk/depot/

I try to install all of the packages:

Code:

i N  galileo.man.pages [d]             16+  Galileo Video Manual Pages
i N  galileo.man.relnotes [d]          16+  Galileo Video Release Notes
i N  galileo.sw.demos                1456+  Galileo Video Demo Software
i N  galileo.sw.diag                 5876+  Galileo Video Diagnostic Software
i N  galileo.sw.eoe [bd]              872+  Galileo Video Execution Software

But I run into conflicts:

Code:

galileo.sw.eoe (1274627333) is incompatible with eoe.sw.base (1289434520)

I feel I'm missing some basic Irix knowledge here.

You're going to need your overlay cds also and the /unbundled directory on the second overlay

Code:

Galileo video 1.1 (ev1): unit 0, revision 2.

Thanks for your help.


Is there an idiot's guide to installing software like this on Irix? I'm not sure I could have figured this out. Do I always have to add the overlay CDs when installing new packages?

[robespierre]

In general, you will need the overlay CDs for anything that requires the base CDs, because the overlays—as their name implies—supersede the base 6.5 set to provide the current version of the packages.

[legodude]

In general, you will need the overlay CDs for anything that requires the base CDs, because the overlays—as their name implies—supersede the base 6.5 set to provide the current version of the packages.

How do I figure out when I need base CDs? I assumed that installing Cosmo software would require the CDs to be loaded, but I tried without anything extra and was able to install the package.

[weblacky]

I can understand your confusion but you're possibly overthinking this. Don't confuse revisions with dependencies. For example in a normal Windows desktop machine you can certainly get an older driver that still claims to work with your operating system and install it but you'd rather have the latest driver to install it because you hope there's bug fixes or whatever, right?

As you seen the software manager isn't that intelligent it only knows that there are dependencies but it has no idea that newer versions of the driver or software are available unless you present additional repositories from the overlay CDs.

So think of the software manager complaining about dependencies as saying that you need to give it more files from your base disc set to satisfy the dependencies but the installation can still be broken or perhaps malfunction because there's in fact a newer driver that was supposed to be used all along. That newer driver only comes from the overlay CDs that match your operating system version, if they're updated at all.

So the software manager will tell you if you're missing pieces and you need to provide more discs. The overlays are there to update the versions of the software after you've satisfied all the dependencies. Normally you would do this all at once so that you would never install the old driver into a later operating system.

So the technique would be to present the original old driver disc, then present your base CDs to satisfy dependencies, then present your overlays to allow the software manager to detect upgrades to this entire scenario, to then allow it to install the latest revision when it actually goes to perform installation.

Does that generally clear things up?

[kshuff]

This cable, which I happen to have  

  

[legodude]

It does exist!

Any way that you would be willing to check the pinout?

[Gamefan]

I can understand your confusion but you're possibly overthinking this. Don't confuse revisions with dependencies. For example in a normal Windows desktop machine you can certainly get an older driver that still claims to work with your operating system and install it but you'd rather have the latest driver to install it because you hope there's bug fixes or whatever, right?

As you seen the software manager isn't that intelligent it only knows that there are dependencies but it has no idea that newer versions of the driver or software are available unless you present additional repositories from the overlay CDs.

So think of the software manager complaining about dependencies as saying that you need to give it more files from your base disc set to satisfy the dependencies but the installation can still be broken or perhaps malfunction because there's in fact a newer driver that was supposed to be used all along. That newer driver only comes from the overlay CDs that match your operating system version, if they're updated at all.

So the software manager will tell you if you're missing pieces and you need to provide more discs. The overlays are there to update the versions of the software after you've satisfied all the dependencies. Normally you would do this all at once so that you would never install the old driver into a later operating system.

So the technique would be to present the original old driver disc, then present your base CDs to satisfy dependencies, then present your overlays to allow the software manager to detect upgrades to this entire scenario, to then allow it to install the latest revision when it actually goes to perform installation.

Does that generally clear things up?

This clears up a lot for me! Thank you so much for this breakdown.

[legodude]

   

I got my 10pack of connectors. The quality is pretty good, and with the way the rows are offset, soldering won't be terrible. I'm going to try and whip up a pinout and then give it a go.

[weblacky]

If you could also post the part number and where you bought the connectors, that would be great!

Please keep us up to date on the pinout and your experiences on this topic.

[legodude]

I got the connectors from Aliexpres:
https://www.aliexpress.us/item/3256804348972809.html
I will likely have 4-6 spares when I am done that I am happy to drop in the mail.

Here is the pinout I came up with. It is not exactly how Ian describes it (at least how I read it) because looking into a male connector, the pin numbers snake back and forth (unlike a d-sub connector):

Top left pin 1 (looking into male connector)
1...15
30...16
31...45
60...46