OSX86 Fried my Processor/Motherboard? Need desperate help.

[stryder]

Well, if he did, in fact, corrupt the firmware... wouldn't it be an easy fix? You just stick a PCI card in the computer, boot off of that, and re-flash the firmware?

 

And, sorry, I had heard in the past that ATI never does any sort of flashing. I figured that applied to both Mac and Windows, so that's my bad and I'll admit that.

 

But it still definitely sounds like the mobo failed.

 

But the thing that interests me... Is that if the driver did in fact try to patch the video card... could it be possible that the flash did something to something else in the computer instead of hitting its target? I can see how that could conceivably make the motherboard fubar.

 

Once again, I apologize for my ignorance and I apologize if I came off as an {censored} in that post, it wasn't my intent.

 

I'll admit that I'm definitely still learning all of this and while I'm catching on fast, I was using information that I'd heard previously about ATI's stance about flashing the firmware.

 

Correct, if the video card was corrupted, then inserting another card would solve that problem. But it didn't. I agree with another poster, if it was rebooting like that, it possibly was something else (northbridge, etc.). That does sound plausible. Like I said before, though, adding the ATI driver from the PPC side to the equation adds possibilities nobody has tried or tested. There is really no way of knowing.

 

Unless someone wants to get adventurous and start updating drivers on various ATI cards in various setups to see what happens...

 

I JUST rebuilt a new machine, so I'm not stepping on any stones.

[Poi§on]

The fan on my CPU is fine (Everything was bought july 2005). My friend is testing the ram and the video card now. If those are fine and I'm gonna send back my motherboard for a replacement since it'd only b the cost of shipping. My motherboard is supposed to have a top hat flash that will reprogram the BIOS if it gets corrupted. But as i said it was missing in the shipment and I can't order the part singly from ECS. If I need to send the motherboar back hopefully it'll come with the top hat bios flasher this time. Heres what it looks like:

 

http://images.google.com/imgres?imgurl=htt...6lr%3D%26sa%3DG

 

If it still doesn't work after that, the only thing left is the processor which i think i can also get a replacement for free from work. Booting from any medium doesn't work. Like the one post said i can't even get the computer to display anything, let alone get to a point to boot from another media. AND ITS NOT THE POWER SUPPLY, there's been 3 post saying that. Read all the posts ppl.

[Poi§on]

The RAM and Video Card are working fine. Which leaves the Motherboard and CPU as the only possible items left that could be messed up. I'm gonna bet its the motherboard and send it back. I'm missing that part I want anyway so. Assuming it is the motherboard... What in OSX86 could have caused this? When the computer was restarting itself on its own right b4 this issue started every time the processor speed would get changed in the BIOS to something slower. I think OSX86 may have corrupted the BIOS personally. THat top hat flash item listed in my last post would have been perfect to fix this too. But what are all y'alls opinion on what might have happened?

[EtherealRemnant]

While I'm still doubtful on your BIOS being flashed by the ATI drivers, I'm starting to see some sense in that.

 

It could also have just been bad luck and a bad board.

 

Now the problem is that if you RMA that board through Newegg and its been flashed by OS X, I dunno how far you're gonna get on getting a replacement.

 

I am not experimental enough to download the ATI drivers and possibly fry MY board... so I don't think we'll know unless you try it and it does it again.

[domino]

Yes welcome to the PC world where everything may not be so Apple perfect. I have had many board, drives,and AGP crads RMA'ed becuase they were dead out of the box or just plain stop working in less than a month.

 

Anyone can say OSx86 could have had instructions that might have killed the board, but without definate proof and an O-scope, you might have just as well said that it static electricity or a bad ground might have done it. It would be nice to know though. Maybe as time passes, we'll start seeing bad drives and bad AGP cards poping up here and there.

[stryder]

Yes welcome to the PC world where everything may not be so Apple perfect. I have had many board, drives,and AGP crads RMA'ed becuase they were dead out of the box or just plain stop working in less than a month.

 

Anyone can say OSx86 could have had instructions that might have killed the board, but without definate proof and an O-scope, you might have just as well said that it static electricity or a bad ground might have done it. It would be nice to know though. Maybe as time passes, we'll start seeing bad drives and bad AGP cards poping up here and there.

 

I do know on the PowerPC side that OS X has always been very fussy with hardware. What I mean is that if you had memory that was 99.999999% functional, OS X would often crash the computer because of it. OS X is like that with almost everything.

 

When OS X 10.0 came out, there were lots of reports from people complaining of their machines rebooting, programs crashing, etc., and it was traced back to hardware that was just a little off, and off enough to cause OS X to be unhappy. Memory especially, but other things, too.

 

My Dual processor G4 Mac lost one of its processors, in OS X only. In OS 9 it was still there, but in OS X it said I had 1 processor. Had to return it to Apple for replacement (if I had paid it would have cost me like $1000 at the time).

 

I don't quite understand why OS X is like that. It just likes hardware that plays really nice, and avoids hardware that's so-so.

 

That said, if your computer was restarting and getting a lower CPU speed each time, I don't think OS X itself caused that. I have seen that before. Either the bios/motherboard thinks your processor is having problems, or your processor is having problems, and the bios was detecting it.

 

I know 3 people have said bad power supply, and you don't believe it, but it could be an intermittently bad power supply. That would definately cause the bios corruption and reboots you report. Bad RAM or a bad memory slot on the motherboard could cause those reboots, too. A PCI/PCI-X card that is a little loose could also cause that (same with memory that isn't 100% seated).

 

Intel processors are built pretty good, otherwise I would suggest that when you seated the CPU fan you may have damaged the processor. But that's unlikely with Intel (very VERY easy with an AMD, as the processor die sticks out and when you try and bend the fan housing over to "pin it down" you could "chip" or bend a corner on an AMD processor, rendering it faulty).

 

I'm not sure if the ATI drivers try to write to OpenFirmware or not, and I don't know what sort of support OS X x86 has for OpenFirmware, whether it traces it back to the bios or what. Like I said, that remains to be seen.

 

Let's hope if ATI drivers did do something, that more people don't screw up their machines by accident. If so, I hope they change their drivers to recognize the platform they're on and refuse to run.

[Poi§on]

I do know on the PowerPC side that OS X has always been very fussy with hardware. What I mean is that if you had memory that was 99.999999% functional, OS X would often crash the computer because of it. OS X is like that with almost everything.

 

When OS X 10.0 came out, there were lots of reports from people complaining of their machines rebooting, programs crashing, etc., and it was traced back to hardware that was just a little off, and off enough to cause OS X to be unhappy. Memory especially, but other things, too.

 

My Dual processor G4 Mac lost one of its processors, in OS X only. In OS 9 it was still there, but in OS X it said I had 1 processor. Had to return it to Apple for replacement (if I had paid it would have cost me like $1000 at the time).

 

I don't quite understand why OS X is like that. It just likes hardware that plays really nice, and avoids hardware that's so-so.

 

That said, if your computer was restarting and getting a lower CPU speed each time, I don't think OS X itself caused that. I have seen that before. Either the bios/motherboard thinks your processor is having problems, or your processor is having problems, and the bios was detecting it.

 

I know 3 people have said bad power supply, and you don't believe it, but it could be an intermittently bad power supply. That would definately cause the bios corruption and reboots you report. Bad RAM or a bad memory slot on the motherboard could cause those reboots, too. A PCI/PCI-X card that is a little loose could also cause that (same with memory that isn't 100% seated).

 

Intel processors are built pretty good, otherwise I would suggest that when you seated the CPU fan you may have damaged the processor. But that's unlikely with Intel (very VERY easy with an AMD, as the processor die sticks out and when you try and bend the fan housing over to "pin it down" you could "chip" or bend a corner on an AMD processor, rendering it faulty).

 

I'm not sure if the ATI drivers try to write to OpenFirmware or not, and I don't know what sort of support OS X x86 has for OpenFirmware, whether it traces it back to the bios or what. Like I said, that remains to be seen.

 

Let's hope if ATI drivers did do something, that more people don't screw up their machines by accident. If so, I hope they change their drivers to recognize the platform they're on and refuse to run.

 

There is no way it could be the power supply. I tried 2 different ones with the same result. And theres no way its the video card as it was working just fine in another machine same with the RAM. And I'm not a retard, I had the video card and CPU/Heatsink in nice and tight. You'd have to be a damn near idiot to not get a Socket T CPU heatsink on correctly. Mine snaps right in in seconds.

 

I think the main issue regardless if you all want to avoid it or not, is that the copy of OS X I installed has not worked all the bugs out of it. It may have been accessing registers that it shouldn't or who knows what. But this is understandable. It is a developers copy of the system and frankly I was shocked it even worked at all. I took a risk by installing it and lost with my setup. However, I'm not going to sit here and say "oh my hardware is faulty" when up until I installed this OSX86, everything was working great. All the equipment I have is 6 months old and near top of the line. I'm 99.9% sure the problem is something on the motherboard got corrupted due to the copy of OSX86 I used was on a system it wasn't designed to be run on. Much like putting a honda engine in a ford, it may start up but they'll probably be nuts and bolts flying everywhere once you drop the clutch... Because a honda engine was designed for a honda car!

 

I have a new copy of the latest build (1072) 10.4.2 OSX86 but I'm not gonna risk it on my top of the line system either. Maybe my older 2.4Ghz P4 Dell can get it to work. I'm definitely not going to risk this again on my speed machine until OSX86 is released to the public officially. Besides my Dual 2.5 G5 rockets OSX more than enough for me

[stryder]

There is no way it could be the power supply. I tried 2 different ones with the same result. And theres no way its the video card as it was working just fine in another machine same with the RAM. And I'm not a retard, I had the video card and CPU/Heatsink in nice and tight. You'd have to be a damn near idiot to not get a Socket T CPU heatsink on correctly. Mine snaps right in in seconds.

 

I think the main issue regardless if you all want to avoid it or not, is that the copy of OS X I installed has not worked all the bugs out of it. It may have been accessing registers that it shouldn't or who knows what. But this is understandable. It is a developers copy of the system and frankly I was shocked it even worked at all. I took a risk by installing it and lost with my setup. However, I'm not going to sit here and say "oh my hardware is faulty" when up until I installed this OSX86, everything was working great. All the equipment I have is 6 months old and near top of the line. I'm 99.9% sure the problem is something on the motherboard got corrupted due to the copy of OSX86 I used was on a system it wasn't designed to be run on. Much like putting a honda engine in a ford, it may start up but they'll probably be nuts and bolts flying everywhere once you drop the clutch... Because a honda engine was designed for a honda car!

 

I have a new copy of the latest build (1072) 10.4.2 OSX86 but I'm not gonna risk it on my top of the line system either. Maybe my older 2.4Ghz P4 Dell can get it to work. I'm definitely not going to risk this again on my speed machine until OSX86 is released to the public officially. Besides my Dual 2.5 G5 rockets OSX more than enough for me

 

I agree. I have a Socket T. They are a brainless install. I was referring to the fact that if it were an AMD that would be a possibility, and I know from the start it was an Intel. AMDs are susceptible to the type of damage I mention.

 

You are exactly right in acknowledging that this is a developer build, and as such may have accessed registers that fried the board. Very unlikely, but possible. My reference to the posibility of the ps being bad was that it is possible the ps went bad for a brief period of time, frying or corrupting things. That has happend to me. I had a ps fry my video card, and I don't know why... I swapped the ps for a new one, and when that one went, I tried the old "bad" one again, and it worked fine again. But I know my now "good" power supply fried my video card at one point. And it was rebooting and reporting different processor speeds with that one, too.

 

But like I've said repeatedly, there is no real way of knowing exactly what caused your machine to cease functioning. You are dealing with a developer version of OS X running on hardware that it was not meant to run on (a non-DTK), and you installed drivers from a PPC version. Lots and lots of variables there.

 

Maybe aliens abducted your machine during the night...

 

I'm done here, there's nothing more really to discuss right now, as it's mostly been said.

 

Over and out.

[EtherealRemnant]

Well, I got experimental and installed the latest OS X drivers from ATI.

 

They just don't run, don't detect an actual ATI card in ATI Displays. No issues otherwise so I don't think that is what caused it.

 

I have a Radeon 9800 Pro (with the XT core) and it didn't seem to do anything, it doesn't even try to load the extensions at boot.

 

Actually, checking my extensions folder, it didn't even install any, probably because of the aforementioned not finding the board.

[Fuzzlet]

Yeah I've tried installing ATI ppc drivers on my 9800 Pro, and... nothing happened.

 

Sometimes just freak things happen with no real conclusive evidence to a cause.

[ghw9132]

In my system a few years back i had an ECS K7VZA mobo and ATI Radeon video card. It had similar symptoms, rebooting etc. When windows would reboot, it would say it had recovered from a serious error and state the video card was at fault. I eventually found a certain combination of via 4in1 drivers and ATI drivers that would function together, stable. However I believe the automatic rebooting damaged the motherboard since after a while the only way it would boot is with extreme patience. -- push the power button, wait a few seconds to see if it will boot, hold power button to shut off, and repeat. Sometimes it took up to 5 minutes of f-cking with it before it would boot. Also, the radeon card i had i delibratlly attempted to flash it to work on the mac, unfortunatly it has a smaller flash rom and would not function properly. The Mac card could be reflashed to work in a pc.

[Poi§on]

Problem has now been fixed. Culprit: Motherboard. Luckily through newegg's screw up in attempt to credit me $25 for the replacement top hat flash part (which turns out you can't order seperately from ECS) I got $25 extra bucks along with buying a better, newer motherboard by ECS the PF5 with the top hat flash, support for dual core processors, and ddr2 667 for $30 cheaper. So basically I made $50 and got a better board because of this whole issue.

 

But now the question is why? I refuse to believe that this was a magical coincedence that the motherboard happened to go bad right after I installed OSX86 and OSX86 had nothing to do with it. The whole random rebooting thing right before it died is a clear clue that the copy of OSX86 I obtained was not compatible with my setup. What I believe happened is that OSX86 somehow manage to corrupt the boards BIOS. In any event be warned: If you attempt to run OSX86 be aware that the kind of problems I had may occur. And you may not be as fortunate to have bought your motherboard from newegg. This was the first time I've ever seen software destroy hardware.

 

Even though I got a newer OSX86 10.4.2 copy and the top hat flash for my new PF5 motherboard there is no way I'm gonna try it again. Not until it becomes retail at least. It isn't worth the hassle and risk. I got my dual 2.5 G5 for OSX anyway. Just woulda been nice to have another OSX machine rather than my all time hate Microsoft. So to all y'all good luck and have fun experimenting!

 

~Erik

[EtherealRemnant]

Sorry but I think your warning is quite far-fetched. Nobody else has reported any problems with OS X trashing their motherboard.

 

Why don't you get a REAL motherboard instead of cheap {censored}? I think your problem lies there, personally. *shrugs*

[arsenalsam7]

ditto on ECS being {censored}

you have 10.4.2?

how?

 

 

 

can a virus corrupt a bios chip?

[EtherealRemnant]

A virus that is coded properly could corrupt just about anything that is able to be corrupted. If you can flash it, you can make a virus to flash it in a negative way as well. Just a rule of thumb. If it can be done by one program, it can be done with another, which a virus clearly is a program.

[MitchBomcanhao]

Ok, I had my doubts before posting this, but...

 

my Acer TM371 laptop started giving me some monitor issues (image flipping between normal and dark/striped image), but it seems it only happened while using osx. It does seem unrelated to os x (maybe a faulty connection?), but who really knows? sadly i'm sending it over to ACER so they can check it out, and i really need my laptop...

 

backing up as I type

[Elv13]

ihad this problem too, i solved it. Unplug everything, remove the botherboard batterie. Wait 2 day, ung\plug everyting, and replog all, reconect the powersupply, boot into bios, restore default setting. reboot, delete osx partition (i am talking from it but next time i get this i delete it.

[Poi§on]

Sorry but I think your warning is quite far-fetched. Nobody else has reported any problems with OS X trashing their motherboard.

 

Why don't you get a REAL motherboard instead of cheap {censored}? I think your problem lies there, personally. *shrugs*

 

 

My ECS motherboard is not {censored}. I've built dozens of systems with ECS motherboards and they've all worked great. This motherboard has loads of features and runs fast and stable. It has the newest technology ICH7R, Dual core support, SATA2, DDR2, dual PCI-X x16 slots for 2 video cards, 1066FSB, etc. And it is the only motherboard I have seen that has a top hat flash for the bios in case you mess it up. So it must be {censored} huh?

 

http://www.newegg.com/Product/Product.asp?...N82E16813135199

 

I see people having more problems with ASUS motherboards than any. And my advice is not far fetched. Considering the copy I installed had a read me 20 pages long of all the hacks that were needed to even get it to install correctly there is considerable risk. Half the people on here have posts pertaining to problems that are unique to them 'that nobody else is having' so wtf is that supposed to mean? I suggest you get your {censored} straight before you start throwing insults about my system setup around. Just because my problem is rare or hasn't happened to someone else yet doesn't mean its not worthwhile to stress that there may be some risk.

 

ihad this problem too, i solved it. Unplug everything, remove the botherboard batterie. Wait 2 day, ung\plug everyting, and replog all, reconect the powersupply, boot into bios, restore default setting. reboot, delete osx partition (i am talking from it but next time i get this i delete it.

 

I tried that as well...no success.

[brianbwlim]

Do you still think OSX fried your computer???

 

Everyone posts topic when the problem persists even after proper remedy and rescue.

 

So, Does OSX fry again your new ECS motherboard???

 

If so, then you can be honored as a founder of HOTTEST NEWS of this year,

else you maybe better change or delete this postiing.

[Poi§on]

Do you still think OSX fried your computer???

 

Everyone posts topic when the problem persists even after proper remedy and rescue.

 

So, Does OSX fry again your new ECS motherboard???

 

If so, then you can be honored as a founder of HOTTEST NEWS of this year,

else you maybe better change or delete this postiing.

 

I'm not going to even try to reinstall it sorry. You all can believe me or not I don't really care. I'm not going through the possible hassle of dismantling my system again to prove a point. It may work for all I know, especially since I have a newer version now. I'm not trying to gain publicity here, I was just trying to get help on solving a problem. But now that the problem is solved everyone's pointing the finger at me like I don't know what I'm doing. Most everyone else's problems don't involving risking losing money by damaging equipment so its to their advantage to "post topic when the problem persists even after proper remedy and rescue". But I'll try and change the topic title to satisfy all these anal retentives out there. After all my guess is it didn't fry anything and just corrupted the BIOS. Whatever...If you all are going to continue posting on here why don't you put something useful rather than these jerkish comments. If you're that curious go buy a PF21 motherboard and install 10.4.1 on it and see what happens. I'm not making this {censored} up. I explained the circumstances of what happened and drew a logical conclusion if you are gonna say its cuz ECS is {censored} or make it sound like I'm just posting on here to gain attention then you can kiss my ass. Best of luck to you all who are actually using my post information rather than criticize it.

 

~P

[EtherealRemnant]

ECS boards are very well known to be craptastic.

 

That board that you sent me the link to has almost no reviews.

 

Go read reviews on other ECS boards. They are NOT known to be the most reliable boards.

 

Want a reliable board? Get an Intel board made by a real manufacturer. *shrugs*

 

Just the fact that it comes with the top hat flash should be a bit of a warning... Why in the HELL would you need a top hat flash for a board that is completely stable? Just some food for thought.

 

You can say whatever you like, I really couldn't care less, but I'm still betting its the fact that you chose a craptastic brand of a motherboard and that is why you had the issue.

 

In any case, I can't stand Intel processors and I stand behind AMD 101% so the point is moot in my case. I have very few problems with my OS X install. In fact, the only real problem I have is that I don't have hardware video and that I have to use the onboard sound because my Audigy 2 ZS isn't supported.

 

Everything that I know about computers and how they work, through my... Oh, 13 or 14 years of experience (I'm 21 and I BUILT my first computer at the age of 9)... tells me that you're just pissed off because some coincidence caused your {censored} board to blow. Cry me a river.

 

The bottom line is that even though that ECS board is 118 dollars, their previous incarnations of "quality" have left something to be wanted in a big way and I'll never trust an ECS board based on that fact.

 

Every board is going to have problems but I refuse to believe that OS X fried your motherboard until you come on here with some real proof. End of story. In all my years of computing, I've never ONCE had a board die on me other than from a lightning surge but I've seen many cheap boards take the plunge on others' computers. Its kind of ironic, since I have a "cheap" board in mine (Soltek K8AN2E-GR) and I've had less problems with it than with ANY other board I've ever used. You can stick a high price tag on {censored}. Just look at IBM DeskStar (loving known as the DeathStar) drives...

 

I sincerely hope that was just an isolated incident and that you're not just finding out what kind of quality you're getting with ECS but don't bomb on me like I'm someone who doesn't know {censored}. All of my experience on computers was totally personal and "just for fun" and I've got quite a bit of it. As an example, I've got Windows XP, SuSE 10.0, and Mac OS X all running on the same computer, with SuSE 10.0 and OS X on the same hard drive. And that's just an example.

 

I could understand if I came on here and was like "i dun no wat to do wit this disc... can u help me? i dont no cumputers..." but I didn't. Don't treat me like a common idiot because I can damn well assure you, I'm QUITE FAR from an idiot.

[brianbwlim]

Well

 

In the process of debugging for SW and/or HW,

Most effective way is rule out the part which can never(or seldom) happen.

 

And then try to find bugs in the rest of the parts.

-- looks somthing like binary search ---

 

Here, most important thing is what to rule out or not.

To do this, we need to have concrete data for the past history of error(or bug) debugging.

In other words, we have to rigorously confirm the cause of problem.

 

For your case::::

 

You just have one case of frying motherboard with OSX 10.4.1.

 

You just believe its because OSX have some magic code to burn out BIOS or something.

I can say "you are just believing" because you do not want to confirm it with your new mother board.

Here you rule out every other possbility that may arise from your old HW.

 

Never you can say it is because of OSX before you do have similar case with OSX 10.4.1 and new ECS mother board.

Only you can say that you just had a bad luck with OSX 10.4.1 and ECS motherboard.

 

And this kind of information can not be used as the concrete information for the Next debugging for someone who may have similar problem because you do not want to conform that fact with new ECS motherboard and just saying you had a bad luck but now OK with new board and OSX 10.4.2.

 

Nobody can be informed anything from your experience, but they can just have info that you once had a bad luck with ECS motherboard but now everything is OK. -- Not any more --

 

Something strange in your case is:

You do believe that OSX 10.4.1 has fried your computer, but you are dare to believe OSX 10.4.2 has no such problem.

 

What about if it happens within one month or 1 or 2 or 3 years,

Then what would you want to say?! It is because of OSX or HW or Dust or Electricity or Humidity Or.....

Or Would you say that you need OSX 10.4.X and new ECS motherborad to have another OK case.

[Poi§on]

ECS boards are very well known to be craptastic.

 

That board that you sent me the link to has almost no reviews.

 

Go read reviews on other ECS boards. They are NOT known to be the most reliable boards.

 

Want a reliable board? Get an Intel board made by a real manufacturer. *shrugs*

 

Just the fact that it comes with the top hat flash should be a bit of a warning... Why in the HELL would you need a top hat flash for a board that is completely stable? Just some food for thought.

 

You can say whatever you like, I really couldn't care less, but I'm still betting its the fact that you chose a craptastic brand of a motherboard and that is why you had the issue.

 

In any case, I can't stand Intel processors and I stand behind AMD 101% so the point is moot in my case. I have very few problems with my OS X install. In fact, the only real problem I have is that I don't have hardware video and that I have to use the onboard sound because my Audigy 2 ZS isn't supported.

 

Everything that I know about computers and how they work, through my... Oh, 13 or 14 years of experience (I'm 21 and I BUILT my first computer at the age of 9)... tells me that you're just pissed off because some coincidence caused your {censored} board to blow. Cry me a river.

 

The bottom line is that even though that ECS board is 118 dollars, their previous incarnations of "quality" have left something to be wanted in a big way and I'll never trust an ECS board based on that fact.

 

Every board is going to have problems but I refuse to believe that OS X fried your motherboard until you come on here with some real proof. End of story. In all my years of computing, I've never ONCE had a board die on me other than from a lightning surge but I've seen many cheap boards take the plunge on others' computers. Its kind of ironic, since I have a "cheap" board in mine (Soltek K8AN2E-GR) and I've had less problems with it than with ANY other board I've ever used. You can stick a high price tag on {censored}. Just look at IBM DeskStar (loving known as the DeathStar) drives...

 

I sincerely hope that was just an isolated incident and that you're not just finding out what kind of quality you're getting with ECS but don't bomb on me like I'm someone who doesn't know {censored}. All of my experience on computers was totally personal and "just for fun" and I've got quite a bit of it. As an example, I've got Windows XP, SuSE 10.0, and Mac OS X all running on the same computer, with SuSE 10.0 and OS X on the same hard drive. And that's just an example.

 

I could understand if I came on here and was like "i dun no wat to do wit this disc... can u help me? i dont no cumputers..." but I didn't. Don't treat me like a common idiot because I can damn well assure you, I'm QUITE FAR from an idiot.

 

First off, I wasn't going off of reviews on newegg. I was going off experience. Don't forget that I work at INTEL so by all means buy our motherboards. I just didn't want to spend double the money and the ECS motherboard I got fit all the features I needed.

 

So under your ideas all cars that come with spare tires mean that the tires it currently has will explode right? ECS includes a top hat flash for convience not because the BIOS chip goes bad. Its for all the stupid people that may flash it with the wrong BIOS or something similiar. Or in my case do something the board was not designed for.

 

In all my years of experience which I'm sorry to say is a lot longer than yours I've seen plenty of burnt up motherboards, power supplies, and processors from customers and not just from spilling coffee on it. Problems where brand new systems stop working and find out its faulty or incompatible equipment. Also don't forget I am a computer technician so I see every problem you can think of. So you can sit in your magical world of fantasy and believe that hardware never has problems unless its crappy or you can have a serious reality check.

 

I'm not pissed off at all about what happened. I am glad. Remember I made $50 and got a better board. The only thing I'm pissed about is jerks that are responding with comments like "ECS sucks" or acting as if I don't know what I'm doing rather than having an intelligent post on what probably happened physically. i.e. "I had a similar problem and it turned out that the copy of OSX86 was not compatible with SRS BIOS chips" or something along those lines. To me, your responses are like getting in an accident cuz you lose control racing and having someone walk up and say its because of the type of car your driving. {censored}.

 

If you want proof why don't you call newegg and inquire about it? Even if I did reinstall it and it had the same problem what proof would you have? You'd just say that ECS is {censored} and blame it on something else. As I said, If you want proof go buy a PF21 and try it yourself. It was running windows fine for almost a year and then I installed OSX86 and the next day it dies? But oh no its cuz ECS is {censored}, thats logical, even though it was working flawlessly until I installed OSX86 right? Gimme a break. Even if you thought ECS was a good brand and liked intel I'm sure you'd be skeptical about doing it after seeing the problem I had as most everyone else I've talked to about this has. That is unless you don't care about the possibility of losing time and money in which I'd have to say you are an idiot.

 

So you can brag about your multi op system machine and your 10 years of experience I don't really care. My senior project used an Altera Flex 10K with 70,000 gates and fifty 28 pin IC chips that I wired up myself along with half a dozen other components. My and anyone elses level of expertise in the area still doesn't change the fact of what happened.

 

I sincerely hope that if you post again you use your experience and expertise to come up with a more intelligent and logical explanation rather than ECS and intel are {censored}. You sound like those people that say apple is {censored} and base their opinion on seeing a mac classic they saw 10 years ago when you post things like that.

 

~P

[SixShot]

My ECS motherboard is not {censored}. I've built dozens of systems with ECS motherboards and they've all worked great.

 

Well, that's a matter of opinion and how the amount of ECS boards that you have worked with. The majority of the Slot-1/S370/Socket A motherboards that I have had to replace in the past outweighs the amount of Asus boards that I have had to replace, in a ratio of 5:1. I'm coming across more dead P4P series boards, but thats' for another story.

 

The K7S5A was the only Socket A that lived up to expectations. The VIA boards were nothing but grief, including that little pissant of a board called the K7S41GX being based of the SiS 741GX.

 

The only reason why ECS is getting better is because the top engineers from ABit and Asus jumped ship and went to ECS. They are finally starting to produce a semi decent board, the KN1. The PF21 is a mixed batch. And yes, all three manufacturers are under the same roof at HSING TECH.

 

So under your ideas all cars that come with spare tires mean that the tires it currently has will explode right?

 

Remember the Ford Ranger / Firestone tire recall?

 

Don't forget that I work at INTEL so by all means buy our motherboards.

 

You won't catch me buying them seeing that Intel bid on the lowest seller for capacitors and didn't choose Rubycon. Guess who Dell bought their 865 motherboards from? Do you want to know how many Optiplex GX270 motherboards I have to replace in a week?

[Poi§on]

Well

 

In the process of debugging for SW and/or HW,

Most effective way is rule out the part which can never(or seldom) happen.

 

And then try to find bugs in the rest of the parts.

-- looks somthing like binary search ---

 

Here, most important thing is what to rule out or not.

To do this, we need to have concrete data for the past history of error(or bug) debugging.

In other words, we have to rigorously confirm the cause of problem.

 

I don’t want to debug it. I wanted to fix it and I did that already. If you want to debug it go buy the exact same system I got now and try it. I’m not about to blow money away to debug it.

 

For your case::::

 

You just have one case of frying motherboard with OSX 10.4.1.

 

You just believe its because OSX have some magic code to burn out BIOS or something.

I can say "you are just believing" because you do not want to confirm it with your new mother board.

Here you rule out every other possbility that may arise from your old HW.

 

You don't need magical code to corrupt BIOS. And damn straight I'm just "believing". Why would I want to risk having this happen again to prove a point. I don't know where you get old hardware from. I have a 512MB X800XL video card, DDR2, a 3.2Ghz P4, and a 250GB HD all brand new? So whats old?

 

 

Never you can say it is because of OSX before you do have similar case with OSX 10.4.1 and new ECS mother board.

Only you can say that you just had a bad luck with OSX 10.4.1 and ECS motherboard.

 

You're right I did have bad luck with 10.4.1 and ECS motherboard. Thats what I've been trying to convey to everyone.

 

And this kind of information can not be used as the concrete information for the Next debugging for someone who may have similar problem because you do not want to conform that fact with new ECS motherboard and just saying you had a bad luck but now OK with new board and OSX 10.4.2.

 

You need to reread my previous posts. If you want to debug and confirm that it happens and lose money go ahead. I will not even mess with it for any reason.

 

Nobody can be informed anything from your experience, but they can just have info that you once had a bad luck with ECS motherboard but now everything is OK. -- Not any more –

 

I disagree. Everything is ok because I’m not reinstalling OSX86. People can still be informed about what happened. Why don’t you look up informed in the dictionary?

 

Something strange in your case is:

You do believe that OSX 10.4.1 has fried your computer, but you are dare to believe OSX 10.4.2 has no such problem.

 

And I never said OSx86 10.4.2 wouldn't have the same problem. I JUST SAID I WASN'T GOING TO RISK TRYING IT AGAIN EVEN WITH A NEWER SYSTEM THAT MAY HAVE FIXED WHATEVER ISSUE CAUSED THIS TO HAPPEN.

 

 

What about if it happens within one month or 1 or 2 or 3 years,

Then what would you want to say?! It is because of OSX or HW or Dust or Electricity or Humidity Or.....

Or Would you say that you need OSX 10.4.X and new ECS motherborad to have another OK case.

 

If it happened after a long time frame I would definitely NOT blame OSX86 as the culprit. DUH!?!