The collected works of Axatax_ - Page 2

I'd actually consider that, but as mentioned my power supply doesn't currently work.


Are there any available schematics for this PSU?
Does your machine have intact skins?
We don't have any support of antialiasing in our hardware, cairo and xrender have to calculate this on your main cpu. I am quite sure your Matrox Millennium can do this in hardware.


I'd be shocked as the Millennium I is 1995/6 vintage HW (the M II came out around 97 IIRC).

I guess VPro isn't much younger -- still, I'd be surprised if the M I can support proper AA (I'm skeptical if this card can do line AA let alone point).

I used to have the specs for this card, as I worked with David Dawes on the original XF86 server for the Millennium I and II while @ Sun. This was right around the time Glide came to Linux, and I moved onto this ( http://openut.sourceforge.net/docs.php ). I'm the "Jeffrey" guy. :) Anyhow, nobody was doing AA in any Linux GUI @ the time (either in the font or widget set). I'll give you the benefit of the doubt though.
Just an update on this, and sorry for jurking you guyz around :? . I just haven't had the time I had back in Jan. That said, I'm *really* going to try to get something out by the end of the weekend, and I have been working on this diligently.

I'm not going to make any performance claims, but I'm going to post up a youtube video of the current player in action. Maybe there will be some surprises. :D
would also like to see this added to the Nekoware collection. It's a great piece of software. So please don't give up on it.


I haven't given up -- but I *really* want to get the Mplayer 1.1.1 out the door. I've promised this for like eight months. S*it -- I'd love to do a new XMAME/MESS package, and I'd also like to get an Ardour port out (and I actually have some semi-working code for the later, as well as Jack, if you don't care about VST plugins).

Sh*it -- maybe we sould make some kind of Nekoware crowd funding thing... I dunno. I'd quit my job in a heartbeat to hack away on IRIX stuff. How cool would an IRIX port of Snes9X be with gamepad support? Samus doing TAS runs on your Octane? << -- I think that would qualify as death and ascension to heaven. Just MHO. :evil:
A little late, but you have my endorsement for -current, with some very minor caveats:

First, this Firefox is an improvement over the previous releases as it does not exhibit the ~hourly crashes I would routinely experience with the previous build. As for speed, I haven't conducted any specific testing, although it certainly isn't a regression by any means.

Now -- (and if I sound overly critical, it's because I feel this is a top-tier package and this really needs to be in -current and in top shape).

The zlib is not versioned properly. Just my opinion, but zlib is not bleeding edge SW, so each new package that someone builds with zlib really doesn't need a *new* zlib, and it doesn't need to *require* the latest zlib. If this zlib goes into -current this way, it's going to muck up pretty much the whole distribution. I have a permanent workaround for this and libpng (which is another chronic offender) with RLD_LIST kung-fu, but this really needs to be fixed, and maybe there should be some guidance in the build Wiki about these issues. Every drop for a big program sends a new zlib that screws everything else up. Maybe if there's not a new security issues with zlib, we should lock this library in and just leave it alone unless it's necessary to upgrade.

The .ftr/.fti files were not installed into the "local" path under /usr/lib/filetype which seems to be the de-facto standard for basically anything else not originating from SGI (and the rest of Nekoware, AFAIK). This Firefox seems to also use a different #tag than the previous version. I had to troubleshoot blank FIrefox icons after installation.

Last nit-pick, the default installation choice for items such as dist files/patches/and release notes were not applied consistently between all the updated libraries for this Firefox.

All in all, good job on a *very* important package (hell, it's the best effort we currently have on IRIX for a web browser).
I suspect the OP uses a Dual channel, not a real dual-head configuration. In dual channel mode there is one continuous desktop so the dialog windows appear in the middle of it - right where the desktop splits. Lame, Just another reason why I'm getting rid of my DCD.


The DCD issue is very annoying, is an X extension/architectural issue, and could be addressed in theory by means of an X11 proxy at the expense of direct-rendering (ie. you have to suck it up and use work-arounds/app defaults).
You guys are a regular education! Thanks for the info I'll give it a try as soon as I get to the homestead. The lone Octane we still have here at work doesn't have Illustrator installed...


I think after IRIX 6.5.22 you have to use the Adobe-provided DPS from the Illustrator CD.
I had/have one of those SGI spreadsheets that have a Discrete configuration Octane (dual 600/DM2/DCD, etc.) at right around US $190,000. This is from SGI for the hardware only, this was not from Discrete and did not include Flame.

Hmmm... Ferrari or Octane...

Decisions...
I would also like to see that modern Mplayer port finished. I wonder how well an Octane would handle MP4 video?. I would also be willing to donate some money to see updated software. Imagine the possibilities.


The MPlayer is comming, but I won't give any time lines anymore as I've done this twice and other life issues get in the way. Suffice it to say, I'm still alive and working on this and there will be improvements with MP4, and MPlayer across-the-board.

The Mplayer 1.1.1 in my FTP has good _compatibility_ with MP4 but the performance isn't quite there yet. The performance is coming -- just don't expect 1080p x264 on even the best Octane.
SGI moved to x.org from whatever they were using somewhere in the 6.5 series. I'll bet that's why DPS was sh*tcanned -- it's just not part of x.org.
ftp.nekochan.net is prompting for a PW and won't accept anon connections. Anything change on this front?
This is due to dependency issues with unmaintained packages.

The way I work around this, is to compile the necessary missing lib, and install the missing lib into somewhere like /usr/local/lib/compat, and add this path to your library path.

This is probably the best you can do for packages with an absconded maintainer.

Anyhow, play neko-nethackfe. I know it works, it's organic and non-GMO, and it's more fun than all that FPS junk... :)
OK, here's the deal (and my opinion) on MAME/MESS stuff --

The port is not difficult. It's pretty straight-forward, and I think I did it over the course of two days (it's really just dealing with GCC-isms and the macros used by the newer versions of this compiler). The issue is, building the damn thing takes about two days on my 2x600 Octane. That's the fastest SGI I have. Somebody with an awesome Origin could probably crunch through this in a few hours.

Now, here's the opinion part --

You may not *want* the latest MAME/MESS. I don't fully understand their development cycle, or how they hash the ROMs, but all of this seems to be in a state of constant flux (ie. - running a random ROM set will usually result in fail. Somewhere along the line, they changed either the expected ROM format or the hash values of the ROMs.)

Now, I have a great version of 0.88, working on my Octane. This is an "older" version of this software. It's newer than anything on Neko besides the 0.149, but it works better, doesn't suffer from the Neogeo/SEGA arcade endianess issues, and works perfectly with any ROMs I've thrown at it. I have the OpenGL renderer working like the 0.149 port, and the MESS port works, too (ie. you can play NES games on your SGI). It doesn't leave me wanting for a newer version, for now -- it runs like it's supposed to.

The 0.88 version is somewhat important, but I don't want to disrespect Neko's ToS for this forum. You can read between the lines on this.

If this is of interest, I can package this up for Nekoware. Just let me know -- and please do so in a day or so. I'm not always near my SGI's now.
WTH. I'm packing it up now and sending it to /incomming.

Enjoy, and send feedback. I think you'll like this version better than the 0,149. Compatibility with ROMs in the wild are much better with this version.
OK,

It's actually 0.94, not 0.88...

It's in /incomming now. If you guys like it, I'll do a proper Nekoware tardist.

But you have to let me know.!!! Please communicate!!!
Just make sure you're using ROMs for the 88-94 series of MAME.

I'm pretty sure you'll be tickled pink by this version. :)
gijoe77,

Thank you for the feedback!! It's definitely 0.94.

It _started_ as 0.78, and I had to patch it up incrementally so I could re-use the work I did on the OpenGL renderer in later versions. I couldn't locate any complete source archive for the versions I wanted to work with.

If something is reporting 0.78, then I missed something (probably minor) somewhere.

What specifically is reporting 0.78.x? Is this messing up your front-end?
Thanks !!!

What HW are you running on? Traditionally, the hangup on the *MAME stuff has been in the graphics renderer. The SDL and X targets are in the archive in order to provide comedic relief for the bored. We finally have an awesome OGL renderer, and now this project really shines on SGI. :)

I'll look into these games today. Try running without the front-end and see if anything changes.

BTW: Which vector games exhibit issues?
I have the version string fixed. When I do the tardist, it will report 0.94 across the board.
Just let me know what vector and 3D games aren't working right.
Cool. I'm looking into this now.
zn won't work, as the driver (as it stands) can't emulate the protected BIOS of the HW.

That and the Virtua Fighter stuff aren't really IRIX porting issues - they're unfinished MAME drivers in the version we have. This is kind of the nature of MAME.

If you know what MAME version these systems began working, that would be very helpful. :)
FYI - The CosmoPlayer 2.1.1 plugin from the 2006 Application CD works with Mozilla also. Just use the .so from the plugin32 directory.
The OpenGL renderer is a heavily modified back-port from a pretty recent version of MAME.

If you can identify which MAME versions the various broken games started to work, I can look at this.
This is really a complex issue, and why we don't have an "awesome" version of MAME (although I think this one is the best, but I'm biased :) )

As was observed, my 0.149 port was really not too hot on compatibility. The problems were really issues with upstream MAME.

---

When you look at the development time line of MAME, you can sometimes have years of garbage (ie. the NES emulation in MESS was broken for *ten years* from late 2003 until somewhere around 2013 -- yes, NES emulation).

Certain versions are considered "islands of stability".

Don't get hung up on the latest and greatest. This project (MESS/MAME) is really a developer's playground. Once in awhile, a really good version, all around, comes out of this project, and that's where we should focus our efforts on in terms of a polished Neko release.

I'm cool with trying to back-port certain important drivers to the version we have working here.

Just understand, there's a reason this software has version numbers which have never exceeded 0 (zero). As a packager, you have to put a stick in the ground at some point, and focus on your platform, rather than the existential project in question.
I gave it a shot on my r5k o2, and it seg faulted on cps1 and cps2 games


The binary is compiled for IP27/R12K.
Check the permissions on the two executables. They were set funny when I extracted the archive.
gijoe77,

Can you try this -- specifically, if there is improvement WRT to the non-working systems... This is based on a *much* newer MAME.
OK, so I can't attach, probably due to the file size -- Will send to /incomming.
Thank you for helping out with this!! -- Just one thing, when you mention systems (ie. cps*), please state which game failed.
On the MPlayer/MIPS mailing list, we have a 4x1GHz Tezro decoding "IMAX: Journey into Amazing Caves [Blu-ray]", somewhat imperfectly. Nobody really thought you could watch DVDs on an Octane, either...

If there was only 25 hours in a day...
Yeah, the 1.1.1 Mplayer has sync issues. This was just a "test" build of something newer than what we had. I wanted to see if others could re-produce my results (ie. run the binary), and if I had the ability to actually do the port. You can run 480p H.264 on a top-of-the-line Octane with this version (with sync issues).

SGI MIPS is "officially" supported on MPlayer now and that's where my changes go, so if you want the latest and greatest, you have to go to Mplayer SVN.

Just be warned, Mplayer in its entirety is in 1000 pieces right now, so any official release, SGI or otherwise, is a ways off.

When things stabilize, I'll do another release. I haven't given up - there's upstream issues that need to clear out before we have something worthwhile to package up. I think the "re-spin" of the 1.0.4 I did is pretty darn good - just don't expect miracles.

EDIT: -- WRT to the 1.0.4. - I don't think there's a DVD this won't play now, either with AC3 or DTS. If you find a problem child, let me know, but I don't think that'll happen. I'm pretty confident I nicked *all* the DVD-related issues...
And by the way, does the Irix version of CosmoPlayer support stereoscopy?


Yes, it does.
Probably should move this to an Mplayer thread...
Guys -- the Mplayer stuff is really another thread.

Please LMK if this MESS/MAME is cool, and I'll do a proper Neko package. (I think it hits the mark 10000% - but I'd like some feedback outside of one forum member).

The -06 version doesn't incorporate my OpenGL work - I'm just trying to assess games compatibility.
If only I could twist your arm into looking into adding a working cps3 driver!


You don't need to ;) . You just need to identify which version of MAME the CPS3 stuff started shining.

I'm totally cool with trying to back port known-working and important drivers. I think this is a better strategy @ this time than trying to chase the latest MAME on SGI. We have a really good, working base right now. You do the research, and I'll attempt the port.
Here's the deal with MPlayer --

The version in the /beta directory is absolutely boss on 480i and below. Physical DVD media now works 100%, AFAIK (nobody has reported any disc that doesn't play, yet). DTS works in this version, which was completely absent in the prior version (think the "white noise barrage" during the LOTR 2nd disk changeout...)

The 1.1.1 version can deal with 480p x.264 on a *really* good Octane, sometimes with sync issues, and probably more-or-less correct on an Origin w/graphics or Tezro.

The SVN version of MPlayer is **much** better, but is in a state of flux, so it will take sometime before a proper package appears here (although anyone is welcome to build their own).
I can't test on an MXE or an O2's or an Indy's or anything else than VPro (that's all I have), and I suspect an MXE isn't going to deal with x.264 @ > 480p, ever. Sorry. And if it can, it won't be from me. It will require someone with a much bigger brain than I have.
There is commonality in the OGL renderers. I don't have an MXE, and I target VPRO -- See my response in the MPlayer thread (regarding the 1.1.1 renderer).

The OGL stuff works like **nobody's business** in this MAME and the MPlayer 1.1.1. :) I think this port really pushes boundaries and the state-of-the-art (as much as you can on a ~10 year old platform). It's the best the SGI platform has ever seen WRT to these type of software (ie. games and "trivial stuff"). The MPlayer 1.1.1 in /beta, and this MAME version are really the best we've ever had on Nekoware (period!!). It's gonna get better, but stuff doesn't happen overnight.