killed my new computer!

Complex UV Layout in Maya

Over the last couple of years UV layout in Maya has changed for the better. In this course we're going to be taking a look at some of those changes as we UV map an entire character

Watch

# 1 24-11-2003 , 02:52 PM

Moderator
Join Date: Oct 2002

Location: London, UK

Posts: 2,800

damn it! can anyone help me with this? I just got my new computer up and running and windows was detecting it as a 1.88Ghz AMD when it was in fact a 2.17Ghz AMD. So I went to the bios and changed the clock mult to 14x (FSB of 166Mhz) giving 2.34Ghz and then it died. And I now cant get it to boot up and give me a picture or anything.... any ideas? I'm thinking that there might be a hardware lock out on the mobo and so maybe I can clear the cmos and see if that helps. But I'm running outta ideas....

help! please...

Alan

Technical Director - Framestore

Currently working on: Your Highness

IMDB

Quote

# 2 25-11-2003 , 07:23 AM

Registered User
Join Date: Jan 2003

Posts: 1,113

Warenty? If you built it your self... Dont do that again.

Armitrex Studios
Now open!!

Quote

# 3 25-11-2003 , 10:08 AM

Moderator
Join Date: Oct 2002

Location: London, UK

Posts: 2,800

woohoo it's ok! I reset the bios and it all stirred back into life user added image

the motherboard must have a hardware lockout to avoid burning out the chip user added image

oh happy days! user added image

Technical Director - Framestore

Currently working on: Your Highness

IMDB

Quote

# 4 25-11-2003 , 11:49 AM

Moderator
Join Date: Sep 2002

Location: London, UK

Posts: 3,198

Hehe, I know exactly how you must have felt when you pressed the power button and nothing happened. Glad you got it sorted out...

Kari
- My Website
- My IMDB

Do a lot, Fail a lot and Learn a lot!

Quote

# 5 25-11-2003 , 12:35 PM

Moderator
Join Date: Oct 2002

Location: London, UK

Posts: 2,800

no that was the worst thing, it would spin up the hard disks and everything would appear to start up but i was getting no picture and some diagnostic LED's on the case were telling me it was a CPU problem that's why I was panicking. I thought I'd blown the RAM and CPU (and everything else!!) but I got lucky this time! no more arsing around with the clock speed for me! user added image