The collected works of Obelix

I am sorry, but it is not a question of a buggy environmental monitor.
When my Fuel began flooding me with warning messages about the +5V line exceeding 5.5V, I checked the voltage with a precision voltmeter and found it was absolutely true.
The voltage kept increasing with time and now, after approx. 10 days, my Fuel no longer powers up: the +5V line exceeds 6V and the machine aborts the power-up and shuts down by itself.
In other words, the power supply is gone - and I *really* hope the voltage has not fried up any other part of the circuitry in the process.

Now, is there anyone knowing (a) how to repair it (this info is available for the PSU of the Indy...), or (b) where to get another?
The only supplier I know of asks 550 US$ from a new one - more than I paid for the whole thing.

By the way, I really love (loved?) my Fuel. Its build quality is not comparable to my Octane, but is anyway a good performer.

Thank you!
SAQ wrote: Basic thing to keep in mind: on most cheap SMPSUs (the Fuel's is probably in this category, all PC supplies are), the voltage regulation reference is taken from one line and the other supplies are expected to track along with it, which they do mostly. Are the other lines also off on voltage?


No, all warning messages always were about the +5V. Other voltages were within tolerances. Good point - maybe this can narrow the search...
schleusel wrote: The newer 460W Fuel PSU is an EPS12V (24+8 pin for "high end" PCs) model from Fortron Source (Sparkle) - that one to be precise: http://www.home2000.net/client/fspgroup ... enumber=23 ... Although i have no idea if they really use the stock model or even whether the pinout is the same..


It isn't.
The Fuel uses standard ATX-EPS connectors, but with different color codes and a completely different pin-out.
Installing a non-SGI PSU looks like a disaster waiting to happen...
Hi everybody!
Last weekend I tried to install e-uae on my Octane2-R12K/400-V6, IRIX 6.5.29, screen set at 1280x1024, 24 bpp. I used the kickstart and workbench of my old faithful A500, which worked perfectly on WinUAE.
All dependencies are there and the tardist file installed flawlessly. E-uae starts up correctly and allows me to set the ROM path and the virtual disks, then as soon as I depress the "Pause" button it invariably aborts with a useless (at least for me) message about X error messages being asynchronous. No other clues.
Anyone else experienced this problem?
Ah, reducing the screen depth to factory setting (i.e. pseudomap) is even worse - it actually prevents e-uae from running.

Thanks!