The collected works of Adrenaline - Page 3

Attached is a quick and dirty Win32 SDL/GL port, compiled with VC++ 2012 and SSE2 (Athlon64/P4 and above). I can recompile with SSE if need be.

I also went ahead and wrote a quick batch script to run all of the benchmarks in a row to save folks time.

Results from my AMD FX-8350 / CrossFired Radeon 6970s:
Code:
Running Default Benchmark (No Arguments)

running on Win32 (AMD Radeon HD 6900 Series) Tue May 28 19:43:13 2013
50 pixel triangles, 90 triangles/strip, 1 strips
vertex data: v3f
flat shading, zbuffer off, light off, texture off
test time: 3.000 secs.
geometry rate: 7864320000 triangles/sec
fill rate: 393216.000 Mpixels/sec

Running Benchmark with Area=12

running on Win32 (AMD Radeon HD 6900 Series) Tue May 28 19:43:13 2013
12 pixel triangles, 90 triangles/strip, 2 strips
vertex data: v3f
flat shading, zbuffer off, light off, texture off
test time: 3.000 secs.
geometry rate: 15728640000 triangles/sec
fill rate: 188743.680 Mpixels/sec

Running Benchmark with Area=100

running on Win32 (AMD Radeon HD 6900 Series) Tue May 28 19:43:14 2013
100 pixel triangles, 90 triangles/strip, 1 strips
vertex data: v3f
flat shading, zbuffer off, light off, texture off
test time: 3.000 secs.
geometry rate: 7864320000 triangles/sec
fill rate: 786432.000 Mpixels/sec

Running Benchmark with Area=1000

running on Win32 (AMD Radeon HD 6900 Series) Tue May 28 19:43:14 2013
1000 pixel triangles, 36 triangles/strip, 1 strips
vertex data: v3f
flat shading, zbuffer off, light off, texture off
test time: 2.000 secs.
geometry rate: 73728000 triangles/sec
fill rate: 73728.000 Mpixels/sec

Running Benchmark with Area=12 + Effects

running on Win32 (AMD Radeon HD 6900 Series) Tue May 28 19:43:14 2013
12 pixel triangles, 90 triangles/strip, 2 strips
vertex data: n3s t2s v3f
smooth shading, zbuffer off, light on, texture on
test time: 1.000 secs.
geometry rate: 11796480000 triangles/sec
fill rate: 141557.760 Mpixels/sec

Running Benchmark with Area=100 + Effects

running on Win32 (AMD Radeon HD 6900 Series) Tue May 28 19:43:15 2013
100 pixel triangles, 90 triangles/strip, 1 strips
vertex data: n3s t2s v3f
smooth shading, zbuffer off, light on, texture on
test time: 2.000 secs.
geometry rate: 5898240000 triangles/sec
fill rate: 589824.000 Mpixels/sec

Running Benchmark with Area=1000 + Effects

running on Win32 (AMD Radeon HD 6900 Series) Tue May 28 19:43:15 2013
1000 pixel triangles, 36 triangles/strip, 1 strips
vertex data: n3s t2s v3f
smooth shading, zbuffer off, light on, texture on
test time: 2.000 secs.
geometry rate: 73728000 triangles/sec
fill rate: 73728.000 Mpixels/sec

_________________
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 :O3x0: 2x700mhz R16k/4GB
Watched it Friday night with my wife - it was fun doing a Mystery Science Theater 3000 like commentary the entire time. The best part was the establishing and close up shots would show 4 feet of water, but most of the cutaway shots looked like a normal LA day (wasn't sure if that was an intentional Ed Wood like mistake or if they simply didn't pay close enough attention).
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
I can vouch for zuluchas - great guy, and can definitely imagine the need to reclaim some space in his living room :)

_________________
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 :O3x0: 2x700mhz R16k/4GB
hamei wrote:
$500 for an ugly, empty box.

Such a deal.


If it still had the Opterons/Dual Motherboards inside, $500 would be much more reasonable, but yeah $500 for an empty box is just silly.

_________________
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 :O3x0: 2x700mhz R16k/4GB
I've got some Samsung 2gb sticks on their way will post if they work or not.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
The craigslist link at the bottom -> http://baltimore.ebayclassifieds.com/co ... z2cJgWfv8f

Looks like he wants $28k.

If he'd part it out I'd make the ~3 hour drive down to him and could pick up some items if some folks wanted it. I just don't have much storage space in my town house.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
smj wrote: NOT WORKING
2GB: Micron MT36VDDF25672G-335D2 - PC2700R-25331-Z (PC2700R, DDR1, 333MHz, CL2.5, ECC, Registered)


Double checked the 8 sticks of these I have - they show up disabled upon boot in my Prism, resetting the errors/reseating doesn't do a thing.

So if someone needs/wants them - let me know, I have no use for them outside of my Altix 350s/Prism.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
BetXen wrote: I have lots of the following 2GB ram parts. All of them work perfectly:

Dataram DTP63692E A0: DDR 184pin PC2700 ECC Registered
Smart SME72564FD8C0CGSG: 184P-DDR-2GB-PC2700 ECC-REG


If the 24gb of Samsung I just bought don't work I may take you up on that.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
BetXen wrote: Unfortunately, I think that all of them are installed in my blades. Have to check if I have spares. Let me know.


They are due to come Thursday so I'll try them then and otherwise I'll just swing by smj's house this weekend and trade him some great Micron 2gb sticks :)
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
I think I am going to throw my hat in on buying and trying new dimms, these 12 sticks came up as disabled. Tried reseating and resetting to no avail.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
Lupin_the_3rd wrote: I use Handbrake and rip to .m4v format. It works really well. I have all 400+ of my DVD's stored like this now. Handbrake allows you to choose whether to rip the subtitles into a separate subtitles file, or whether to embed the subtitle text directly into the video. Ripping to a separate file allows your player to render the text, so you can choose the font, etc. But not all players support this. Embedding them into the video file ensures they work in every player.

My server is running CentOS with mdadm mirror of 2x 2TB drives. It is exporting via NFS to my player, a Raspberry Pi running OpenELEC / XBMC. This allows the server to live in the basement, so I don't hear noisy fans or hard drives in the living room.

The Keeper wrote: I can't figure out how to force HandBrake to encode the english subtitles in the MP4 files with some of the content, even though I selected "burn in". I don't even want to be presented with the option of enabling/disabling the subtitles, I want them unconditionally enabled.

A limitation that I'm finding with HandBrake is that with some of the content, I end up having to create separate MP4 files for each episode on a DVD, which is a bit of a nuisance.

I think the MKV files are supposed to have more robust subtitling features than M4V (MP4). You could give them a try and compare back to back.

I personally prefer having each episode as a separate file. 20 episodes = 20 files. Easier to manage that way, in my opinion, than trying to remember which episode is on which disc.

I do something similar, I use FreeNAS with 4 2TB drives in RAID 10. Handbrake at 1080p for Blurays and 480p for dvds with lossless audio. Uses a lot of space, but streaming to my Xbox 360 works out well.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
The big thing is to get one with an IO9/IO10 controller inside it. Those typically go for more than the expansion modules, though in recent months I was able to pick up a few spare IO9/IO10s for my Prism and A350s.

Another thing to note is the varying CPU speeds 1.3ghz to 1.6ghz (with some difference in cache mixed in there), if you care, the 1.6ghz models are a bit more rare, especially the 9mb cache versions. But they do tend to show up individually on eBay from time to time, and it is just a drop in.

As smi and I (among others) noted: http://forums.nekochan.net/viewtopic.php?f=3&t=16727949 , ram is very picky. So if you find one with > 2gb of ram, consider yourself lucky. I've got 60gb+ of 2gb dimms that aren't compatible.

They are fun with the SSI support, but I get a lot more out of playing with my O300s. In hindsight, having 12 A350s and a Prism is kind of silly :)
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
mia wrote: If you don't already have some altix-specific software to run on this, it's not worth it.
we use it for quicktransit.


Like BetXen said, if you have open source software and don't mind compiling yourself it's not that bad. It took a Saturday to get SVN built from source (along with the dependencies) along with a complete C++ build environment up and running with the Intel Compiler. But then again to each his (or her) own. Since retiring my ESXi server I needed a Linux box for work, so it filled that void.

There is something to be said about stuff simply not being ready to go from the opening of the box, the level of satisfaction with getting these machines up and running is well worth it in my opinion.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
vishnu wrote: When InfiniteReality first came out Hughes Aircraft used it to build F-16 fight trainers for Air Force use but I'm pretty sure there aren't any members here who have one of those with the complete virtual reality chamber to go with it...


At least on the Air Force base I was on, the F-16 simulator that pilots used on the base I could have sworn ran Falcon 3.0 on the latest and greatest Pentium (this was circa 1994).
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
guardian452 wrote: 2008.


How to get a good price is (a) know where to look (industrial/university surplus auctions, etc) , or (b) know somebody who wants to get rid of one.


I'm still hoping the Goddard NASA facility about 15 minutes from me has surplus SGI hardware.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
robespierre wrote: I can't even imagine how much hardware has been butchered by the "recapping" hysteria.
The Indy power supplies commonly fail, see the info here: http://www.nekochan.net/reputable/indytech.html


Not to bring up an old thread, but to say, had some similar issues to the poster with an Indy recently. Occasionally it wouldn't come on at all, leaving it unplugged for a few minutes usually did the trick. Did some work last night (did a fresh install), rebooted after the 6.5.22 upgrade and would not power on even after 30 minutes of leaving it unplugged.

The bigger question that I have is, anyone thinking 5-10 years down the road when these 20+ year old machines start having these problems regularly?
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
Finally had some time to swap the nodeboard for the 8mb cache variant - will post benchmark comparisons sometime soon.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
jimmer wrote: Erhmmm... you're thinking of grabbing a POWER box to explicitly run FreeBSD... or do you just need a box to run some service or to function as a daily driver workstation?

If to run FreeBSD... perhaps a recent-ish SPARC box? On the other hand, you could just also admit that desktop hardware is x86. Over. Out. Done. Dusted. Buy yourself some new x86 junk, restore your backups and immediately start putting pennies into the when-shit-happens-again fund.


I agree, while x86 is far from perfect, it does (like everything) fulfill a purpose.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
Stoo wrote: I'm not even sure there is much interest in Windows 10 period ;)


I actually prefer 8.1 - I put the Windows 10 Technical Preview on my Surface 3 pro last week and keep wanting to go back to the "Metro" Screen. The new "Start Menu" is trying to appease too many people. They should just offer "Classic" and "Metro" options.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
Those were the days, I remember my 12 year old self immediately after putting a Voodoo 1 (Diamond Monster 3D) into my Pentium and booting Quake II, I just sat in that opening corridor with the pistol watching the light from the blast go from the barrel down the hall and into the wall at the end, lighting up the room as it went. I'm sure others have similar recollections of the first time they launched a game with their newly acquired 3Dfx card.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
I hope they get better at making their SDKs better coincide with product launches (like the Band, still no where in sight). Though I do love the new universal app model, makes selling my boss on making a Windows Phone version mute since it's just a few tweaks of the UI here and there.

I hope to see more cool tech like this from them at BUILD in April.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
guardian452 wrote: It is currently on sale for $5 at GOG
http://www.gog.com/game/tesla_effect_a_ ... _adventure

I've never played a FMV before, but it looks really interesting and since the story features Tesla (looks like an operational Wardenclyffe in the trailer) it can't be that bad ;)

I've downloaded it already, as soon as I get home again I'll play it. Warning, it's close to 17GB with the patch and took about an hour to download :o


I'm remember playing Tex Murphy: Overseer back in the day, was a lot of fun. Kind of sad FMV or even partial-FMV games kind of died off. Loved the scenes in Wing Commander, Jedi Knight and Star Trek: Borg back in the 90s.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
I'll give this a shot in both a Prism and one of my Altix 350s - there are a bunch for $9.99 shipped on eBay right now.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
vishnu wrote: Having worked on several fairly large scale commercial development projects I can only say that in my humble opinion it is absolutely, unequivocally, 100 percent impossible to do so without a version control system. Back in the dark ages when we did all our development on SGIs we used CVS, now we use Clear Case. The main advantage to git over CVS is that it is much faster at merging large changesets. I don't know much about Mercurial or Subversion but I've always assumed they're basically the result of "not invented here" syndrome...


I'm still using SVN daily at work, though slowly moving towards TFS with Git for all new developments. Branching was always my sole annoyance in SVN, everything else works fine in my opinion.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
xiri wrote: Hi,

has anybody tested the ATI FireMV 2200 PCI on either Altix350 or Prism ?

Btw, there is actually a great offer to upgrade the Itanium2-cpu available on either Ebay or directly on their web-shop (2,49€ + shipping).
I do recommend the webshop (english/german) as it calculates the shipping cost correctly, Ebay does not.

http://www.ebay.de/itm/Intel-ITANIUM-2- ... 231486ebaa

https://www.servershop24.de/komponenten ... /a-103229/

If I remember correctly, the 1.6ghz 9mb L3-Madison was the fastest cpu for the Altix350 as the following release Montecito, which brought virtualization support to the IA-64, was not supported anymore.


My 2200 came in the mail yesterday, but I've been slammed at work. Should have time the following weekend to try it.

I swapped out my Prism's cpus for the 1.6ghz 9mb Itaniums. Not a whole lot of performance boost over the 1.6ghz 3mb versions.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
They do popup on eBay from time to time, I paid $600 for mine a few years back in not the greatest of condition, though it works great and is considerably quieter than a Tezro.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
TeamBlackFox wrote: 2. The, in my opinion, absurdity of using C# for anything... ( I have a problem with VM languages )


Really? You might have been out of the CLR world for a while, but you can pre-jit your application and with the relatively new .NET Native (came out a year ago), it compiles your C# code to machine code without any dependencies on the .NET framework.

You're entirely entitled to your opinion, but there is a time and place for everything.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
TeamBlackFox wrote: Indeed, thieves would have to be very aware of what I have to go after it.

Adrenaline wrote: Really? You might have been out of the CLR world for a while, but you can pre-jit your application and with the relatively new .NET Native (came out a year ago), it compiles your C# code to machine code without any dependencies on the .NET framework.


Well aware of this, I just don't care. Its in the same class as Java, but worse because Mono is a hopelessly broken piece of junk and the open sourced .NET doesn't run on FreeBSD or OpenSXCE, the two modern desktop OSes I use, unless you happen to use the aforementioned Mono. There'ls other complaints but moreso I've rarely heard of someone so into UNIX being a fan of an Microsoft-derived product (yes, everyone knows abotu Xenix, which is now defunct.)


The thing for me is the ability to do everything under the sun with C# - Mobile Apps for every platform, Web Services, backend services, quick tools etc.

It's evolved nicely since I started developing in it 8 years ago, between the task parallel library, asynchronous support and lamba expressions I couldn't be happier. Been diving into the C++/cli lately to do OpenCL work, which if you do it right you get the best of both worlds. You can write unmanaged C++ and only writing a few managed wrapper functions so you wouldn't need to do p/invoke calls all over your managed code. There is still an overhead when making calls between managed and unmanaged, but if you bulk load operations (i.e. send a collection of requests) to the unmanaged code you get a significant increase in speed over a managed code implementation.

I love my Silicon Graphics machines and I use either Linux or BSD daily (more so now that my masters program does everything in either), but at the end of the day, my C#/SQL Server skillset puts a roof over my head.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
armanox wrote:
TeamBlackFox wrote: Indeed, thieves would have to be very aware of what I have to go after it.

Adrenaline wrote: Really? You might have been out of the CLR world for a while, but you can pre-jit your application and with the relatively new .NET Native (came out a year ago), it compiles your C# code to machine code without any dependencies on the .NET framework.


Well aware of this, I just don't care. Its in the same class as Java, but worse because Mono is a hopelessly broken piece of junk and the open sourced .NET doesn't run on FreeBSD or OpenSXCE, the two modern desktop OSes I use, unless you happen to use the aforementioned Mono. There'ls other complaints but moreso I've rarely heard of someone so into UNIX being a fan of an Microsoft-derived product (yes, everyone knows abotu Xenix, which is now defunct.)


Last time I checked Mono was several versions behind Microsoft anyway...

I actually don't mind Java and C# as programming languages. My issue with C# is platform binding (despite being a portable language, it's not been ported and nobody really cares to), and Java is the amount of bad Java out there (and people doing things they were told not to do, which results in hard dependencies on certain java versions (at some point the com.sun packages started changing, probably to com.oracle, and they were never a core part of the language anyway, and people relied on them despite being told they probably should do that)


I use Mono for my Android and iOS development - everything I use is there (TPL, Async/Await, Immutable Collections, LinQ support etc.). I can share compiled code with a portable class library compiled in Visual Studio 2013 on my PC (set with the appropriate profile level to indicate I want to target Windows Phone, Android, iOS, Windows Store and .NET 4.5) which automatically filters out namespaces that aren't supported across those targeted platforms (a huge improvement over doing #define compiler flags in a shared code folder). And then take that dll and reference it in Xamarin Studio on my iMac or OpenSuse and compile iOS, console apps and Android apps with the Mono compiler.

It's not for everyone (yes it is weird a huge SGI/DEC/MIPS fan loves a Microsoft language), but I do like the versatility of the language. In my job I often jump through a bunch of different platforms throughout the day, whether it's web development, windows services or iOS development. It's nice that I don't need to switch mindsets to a different language 3-4 times a day.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
Similar feelings, but after having a Microsoft Band since November, at first I wasn't sold on it, but having the notifications for email, SMS, phone calls etc. is extremely useful. I couldn't imagine not having it at this point. Step counter, calorie counting, sleep tracking and Cortana integration are just icing on the cake.

It'll be interesting in the next year where the wearables market goes.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
foetz wrote:
Adrenaline wrote: It'll be interesting in the next year where the wearables market goes.

total surveillance of course. for corporations as well as intelligence services that stuff is golden and people even dig it. couldn't get much better for them :P


It has come up at work as a possible way of tracking along with the gps tracking that's already going on and then doing some trending analysis on heart rate, sleep patterns and then mapping it to work output. The only reason it hasn't come to fruition in this latest development cycle I'm wrapping up now is the lack of standardization in that market. The Mono framework makes it a bit more enjoyable to work in with C#, but it's not perfect.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
Don't get me wrong, it's not perfect. It took far too long for the SDK to become available (missed the window I dedicated to it, now I'm diving into Mobile VR). I'd like if there were statistics sync'd to the Microsoft Health app (available on all 3 platforms along with a neat web dashboard) would start generating trends and put them in a nice format to look at. Now that I can have access to the sensors via the SDK maybe I'll write an app for it to do what I want. Tough call where to focus nights/weekends at this point between VR, IoT, Cloud Architecture and Wearables (along with keeping current my web dev and mobile dev knowledge).
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
sgifanatic wrote:
GL1zdA wrote: This is so sad: http://www.digital.com/


I recently started reading "DEC is Dead, Long live DEC", but had to put that on hold as I got distracted with other things. Here's the URL if someone else is interested:

This thread is a good - if somewhat depressing - reminder that I need to finish that...


Seconded - I've been reading that off and on the last couple months (OpenGL ES 3.0 has taken priority lately), but it's a great read for the personal insights DEC employees gave.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
I've been wondering for a week or so now why Silicon Graphics chose the pizza box approach for the Indigo 2 and Indy? The Indy I get since it was a low cost machine going against other machines at the time (Sun's SPARCstation, NeXT's NeXTstation, PCs etc.). But the departure from the extremely stylized and iconic Indigo for it's successor I find extremely odd. Were people at the time wanting a more practical machine they could rest a 19" CRT on their workstation? Were the stands for the Indigo 2 meant to appeal to those who didn't want to do that? And then a few years later the O2 and Octane returned to the stylized approach.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
Couldn't imagine hauling a FW900. I had 19" iiyama visionmaster crt monitors back in the day and yes I hauled them to lan parties back in high school - nearly dropped them going up and down the stairs every other weekend.

I was just curious, especially for the folks on here who were actively using workstations back in 1992/1993, I was simply too young.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
sgifanatic wrote: I don't know the reasons why, but I would guess at atleast two:

First, the term pizza box was almost a category descriptor at the time, thanks to Sun. NeXT did the unconventional cube and then moved to the pizza box design also. I think Unix workstation vendors felt they needed a "pizza box" to be in the pizza box workstation business. This form factor, prior to xU-standardized rack mounted equipment, also allowed for greater density when placed in racks.

Second, the Indigo2 implemented EISA and since this bus originated in the PC world, the most convenient way to accommodate EISA card dimensions was to go for a PC style chassis form-factor. Which is roughly what the Indigo2 was.

And yes, placing the monitor on top of the desktop case could have been a third reason. It makes logical sense.


Great point about EISA, up until 1994 my house only had pizzabox style PCs (Tandy 1000, Packard Bell 386 etc.). Never thought about the transition point in the PC world to Towers - probably helped drive the return to non-pizzabox style with the O2 and Octane with both adopting PCI card support.

It's a shame there probably isn't much documentation on the initial Indigo 2 design meetings to read other possible approaches (maybe a larger Indigo style with the slide out boards like what would return in the O2/Octane). Or maybe keeping the Indy as the pizzabox and Indigo 2 as the more unique machine since it had a premium over the Indy.

I hope one day we get a book that dives into Silicon Graphics from their inception through to the Tezro and that interviews take place before people pass away or forget some of the more interesting product development and engineering notes that most people on here would find invaluable.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
kjaer wrote: I'd like to counter the idea that "pizza box" == "any desktop style enclosure". An Indigo2 is not a pizza box. The Tandy 1000 is not a pizza box. I'd argue that the Sun Ultra 1 isn't really a pizza box. Indy, sure.

The SPARCstation 1 really does resemble a pizza box in many ways. It was a novel package for a computer system, by 1989 standards.


I can see that, maybe a better description would be "Horizontal Desktop Enclosure" where some styling may be achieved like in the Indigo2, Indy, NeXTstation etc. but generally un-stylized and utilized in a horizontal fashion compared to the more tower/custom shapes of the Indigo/O2/Octane/Tezro/NeXTcube/G4 Cube/etc.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
uunix wrote: Reverse Psychology Sales Pitch Hamei?


Having owned both O300s and O350s - the 350s are definitely more temperamental.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
kramlq wrote: Seeing as the thread is already resurrected.... if any of the original posters are reading, there is a short paper on the Indigo2 design, but mostly from a thermal/airflow perspective:
http://s3.mentor.com/public_documents/s ... tation.pdf


Interesting thanks!

I wonder if the design from the marketing folks drove to ditch the unique Indigo design or the engineers decided it?
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL
Before diving into compiling it locally - anyone have git running on their machines? Tried the latest and 2 versions back from nekoware on my Tezro and am getting "Cannot Successfully map soname 'liblber-2.3.so.1'" errors when cloning.
:Indigo: 33mhz R3k/48mb/XS24 :Indy: 150mhz R4400/256mb/XL24 :Fuel: 600mhz R14kA/2gb/V10 Image 8x1.4ghz Itanium 2/8GB :O3x08R: 32x600mhz R14kA/24GB :Tezro: 4x700mhz R16k/8GB/V12/DCD/SAS/FC/DM5 (2x) :O3x0: 4x700mhz R16k/4GB :PrismDT: 2x1.6ghz 8mb/12gb/SAS/2xFGL