parhelia and garbled BIOS

[lecter]

Thanx guys, but that is just the form i'm talking about... the "Submit" button takes me to an IE error page, it doesn't work...does it work for you? E-mail would be so much better, if only I could find an address...

[Greebe]

Have you tried something other than IE?

[lecter]

Microsoft OLE DB Provider for SQL Server error '80040e57'

String or binary data would be truncated.

/forms/complaint.asp, line 236


That was the message with Opera.

[lecter]

Originally posted by Greebe
Matrox cannot fix another manufactures BIOS problems. What this means is for all who have this problem to contact the manufacture of their MB and complain... this leverage will push them to fix it.

From the Parhelia review on TomsHardware
Another problem is the display of VESA graphics under DOS. Parhelia cannot display VESA graphics that are not 100% compatible, for example, in a high-resolution BIOS of a motherboard. Matrox will be offering an additional BIOS to remedy this problem.

Well what do you know, it wasn't ASUS's fault after all! I hope they fix this.

[Pace]

You believe Tom over Mike?

[lecter]

Hey, I think Tom is a goddamn liar when it comes to benchmarks...but I also believe what I see and I am not the only one having this problem...when one mobo with high-res bios makes trouble, it's very probably the mobo's fault...when this happens in more than 1 system, with different mobo's and in which the common component is the vidcard, I blame the vidcard...why does this not seem logical to you?

[Greebe]

lecter, the quote I posted is an official responce from Matrox and will be posted by them shortly addressing this issue for all to see. If you don't believe me then fine, but claiming Tom is correct and Matrox is wrong really puts you in a special corner. You know the one where the fool is wearing a dunce hat. Care to put money on it or continue putting your foot in your mouth?

[DGhost]

lector, reread Tom's quote...

Parhelia cannot display VESA graphics that are not 100% compatible, for example, in a high-resolution BIOS of a motherboard

so they are sticking to standards instead of being lax? i think the industry needs more of this, as lax standards have resulted in really really bad mistakes and problems sometimes...

[testjoe]

Here's a groundbreaking idea...

How about everybody stop going ON and ON about the garbled fullscreen boot-up logo and just go into the motherboard's bios and TURN OFF the god damn full screen logo? Did this issue really require two pages worth of thread?

Full screen logos are for retards anyway, that buy their PC's at circuit city, the kind that would get scared and faint from "all those numbers and stuff" .... What person considering a Parhelia WOULDN'T want to see boot up diagnostics in favor of the fullscreen graphic ?

Joe T.

[Greebe]

How about everybody stop going ON and ON about the garbled fullscreen boot-up logo and just go into the motherboard's bios and TURN OFF the god damn full screen logo? Did this issue really require two pages worth of thread?

If that's what it takes then YES. Any thread can be as many posts as neccessary to either answer all aspects of the question at hand or pound it into whoever's head that just doesn't get it. Either way I've seen far worse and makes no difference to me.

[beng3000]

Well, the problem I was having was that the BIOS itself was garbled and unusable. It was with an older Dell computer. I have since switched the Parhelia to a newer AMD based computer and have no problems at all.

[Pace]

One argues with me, but one does not use context.

I, therefore, ignore contextless letters and punctuation

[lecter]

I agree with testjoe about the usability of the bootlogo, it's really a minor quirk, but I don't like the response it has been getting-basically Matrox is blaming the mobo makers when it seems to me it is their fault...DGhost, think about it, if a game or a 3D app is poorly coded and does not conform to quality standards (and let's face it, this applies to nearly all games) then it is Matrox's right not to run it? How about compatibility? Is that too much to ask from a modern computer component?

[Wombat]

Yes, you are asking too much. Why have standards if you expect everyone to tolerate all the "special exceptions" that could pop up because somebody felt like it?

[Greebe]

Exactly Rob. With the cut throat price competitiveness of today most manufactures and software companies either poorly implement hardware or code to keep support costs down. Now that may seem to be an oxymoron, but when all that most customers look at is the price and nothing more or are mislead in some manner as to lead you to believe that all is fine until after the fact what do you end up with?.. either a POS that goes to the trash bin or a migraine that you must patiently wait til the problems are resolved. If they would take a bit of pride in what they do and tell their marketing depts to take a flippin hike then we would all be in a better position to make choices and not gamble at every turn.