Jiglu: glidos: Discussion: Glidos 1.38 and AMD

My processor is an AMD Athlon xp 2000+ (1.66 GHz) and a compatible EPoX motherboard. Is Glidos 1.38 known to have problems with either of these pieces of hardware?

The pc keeps crashing a lot when I'm using the Glidos server.

Also:

My sound card is a Creative Soundblaster Live series card (Live 100, I think).

Video card is an nVidia GeForce 6600 (has built-in 256MB RAM). I think this card is a 32-bit. I'm not sure.

Also have a 1.0GB stick of RAM.

I think that's enough RAM for most games.

Oh, yes. My AV program is by Computer Associates. Also known as eTrust Security Suite. I was wondering if anyone out there has a lot of conflicts with this or any other particular AV program. This one causes a lot of problems with my big games if I don't disable it. And I think it may be interfering even when I DO disable it.

Perhaps someone out there has had these same problems and might know a solution.

Thank You.

Lynn Perry <...> said:
My processor is an AMD Athlon xp 2000+ (1.66 GHz) and a compatible EPoX
motherboard. Is Glidos 1.38 known to have problems with either of these
pieces of hardware?
The pc keeps crashing a lot when I'm using the Glidos server.

No known conflicts. My best guess would be that your system has inadequate cooling and it's overheating. Glidos would show this up because it tends to run the CPU at 100%. The old 2000+ Athlons did tend to run hot.

If you've had the system for a while, it's good to open the case, and vacuum out the CPU cooler; they often get clogged with dust.

Also, I can recommend Orthos for testing your system's stability: http://sp2004.fre3.com/beta/orthos_exe_20060420.cab. Any problems, this will pick it up.

Paul Gardiner <...> said:
Lynn Perry <...> said:
My processor is an AMD Athlon xp 2000+ (1.66 GHz) and a compatible EPoX
motherboard. Is Glidos 1.38 known to have problems with either of these
pieces of hardware?
The pc keeps crashing a lot when I'm using the Glidos server.
No known conflicts. My best guess would be that your system has inadequate cooling and it's overheating. Glidos would show this up because it tends to run the CPU at 100%. The old 2000+ Athlons did tend to run hot.
If you've had the system for a while, it's good to open the case, and vacuum out the CPU cooler; they often get clogged with dust.
Also, I can recommend Orthos for testing your system's stability: http://sp2004.fre3.com/beta/orthos_exe_20060420.cab. Any problems, this will pick it up.

I installed the orthos application and ran it. I tried each item on the list for one minute each (except "Custom"...I don't have any idea what the terms mean).

The end result with the "Gromacs" thing was over 10000 iterations without failure.

One minute on each of the other items showed 0 errors, 0 warnings.

Also:

This is a single processor, not a dual.

But in the PC case there are twin cooling fans (lighted with little blue lights...right purty looking).

Also:

At computer startup, there is a black screen with white lettering that shows a number of things at the bottom of the screen, including CPU temperature.

Is there any particular maximum temp I need to watch out for there?

P.S.: I'm 58 years old and they didn't teach this computer stuff when I was a school kid. And I didn't even know how to turn one of these things on until I was about 49. So I'm definitely not a computer whiz.

:(

Lynn Perry <...> said:
I installed the orthos application and ran it. I tried each item on the
list for one minute each (except "Custom"...I don't have any idea what
the terms mean).
The end result with the "Gromacs" thing was over 10000 iterations
without failure.
One minute on each of the other items showed 0 errors, 0 warnings.

Ah right. The thing to do is run on the default setting (Blend I think it is), and leave it for 4 hours or so.

Paul Gardiner <...> said:
Lynn Perry <...> said:
I installed the orthos application and ran it. I tried each item on the
list for one minute each (except "Custom"...I don't have any idea what
the terms mean).
The end result with the "Gromacs" thing was over 10000 iterations
without failure.
One minute on each of the other items showed 0 errors, 0 warnings.
Ah right. The thing to do is run on the default setting (Blend I think it is), and leave it for 4 hours or so.

A short time after this, I tried running Orthos while running TR1. I let the game run for over 30 minutes and started getting an intermittent beep from the pc.

I quit the game and found the Orthos had stopped and turned red. It showed some kind of error message, suggesting possible hardware failure and told me to check the readme text. But I couldn't find any readme text file in the Orthos package.

Is that where it's supposed to be?

Lynn

Hi Paul,

This is a shot in the dark... any plans to support The 7th Guest? It's a great game and spread in millions of copies as it was the first game on CD and was bundled with God knows how many computers. I loved it and still have a lot of images of it in my head and it would be great to relive it again.

Kind regards,

Stefan

Lynn Perry <...> said:
A short time after this, I tried running Orthos while running TR1. I let
the game run for over 30 minutes and started getting an intermittent
beep from the pc.
I quit the game and found the Orthos had stopped and turned red. It
showed some kind of error message, suggesting possible hardware failure
and told me to check the readme text. But I couldn't find any readme
text file in the Orthos package.
Is that where it's supposed to be?

That's how Orthos shows up problems, yes. And the beeping is your motherboard warning you of overheating.

But are you saying you get this only if running TR1 and Orthos together? Orthos should be able to show up problems all on its own. It would be strange (and interesting) if this happened only when running the two together.

Altogether, this is more evidence of perhaps your CPU cooler being clogged with dust.

Stefan Stefan <...> said:
Re: Glidos 1.38 and AMDHi Paul,
This is a shot in the dark... any plans to support The 7th Guest? It's a great game and spread in millions of copies as it was the first game on CD and was bundled with God knows how many computers. I loved it and still have a lot of images of it in my head and it would be great to relive it again.
Kind regards,
Stefan

Were you thinking Glidos or VDos32? I can't remember that using Glide. What happens when you try running it under Windows directly?

Paul Gardiner <...> said:
Stefan Stefan <...> said:
Re: Glidos 1.38 and AMDHi Paul,
This is a shot in the dark… any plans to support The 7th Guest? It's a great game and spread in millions of copies as it was the first game on CD and was bundled with God knows how many computers. I loved it and still have a lot of images of it in my head and it would be great to relive it again.
Kind regards,
Stefan
Were you thinking Glidos or VDos32? I can't remember that using Glide. What happens when you try running it under Windows directly?

I had The 7th Guest a few years ago, but gave it to a relative. I ran it under Windows XP. It seemed to work okay with Windows.

Solo.

:)

Paul Gardiner <...> said:
Lynn Perry <...> said:
A short time after this, I tried running Orthos while running TR1. I let
the game run for over 30 minutes and started getting an intermittent
beep from the pc.
I quit the game and found the Orthos had stopped and turned red. It
showed some kind of error message, suggesting possible hardware failure
and told me to check the readme text. But I couldn't find any readme
text file in the Orthos package.
Is that where it's supposed to be?
That's how Orthos shows up problems, yes. And the beeping is your motherboard warning you of overheating.
But are you saying you get this only if running TR1 and Orthos together? Orthos should be able to show up problems all on its own. It would be strange (and interesting) if this happened only when running the two together.
Altogether, this is more evidence of perhaps your CPU cooler being clogged with dust.

Yes. The problem only showed when I ran both together. But I'll get the fans checked for dust asap. Thanks Paul.

Solo.

:)

Lynn Perry <...> said:
Paul Gardiner <...> said:
Lynn Perry <...> said:
A short time after this, I tried running Orthos while running TR1. I let
the game run for over 30 minutes and started getting an intermittent
beep from the pc.
I quit the game and found the Orthos had stopped and turned red. It
showed some kind of error message, suggesting possible hardware failure
and told me to check the readme text. But I couldn't find any readme
text file in the Orthos package.
Is that where it's supposed to be?
That's how Orthos shows up problems, yes. And the beeping is your motherboard warning you of overheating.
But are you saying you get this only if running TR1 and Orthos together? Orthos should be able to show up problems all on its own. It would be strange (and interesting) if this happened only when running the two together.
Altogether, this is more evidence of perhaps your CPU cooler being clogged with dust.
Yes. The problem only showed when I ran both together. But I'll get the fans checked for dust asap. Thanks Paul.
Solo.
:)

My brotherinlaw used his canned air to blow out the outer fans. We didn't open the case to do the cpu fan. I don't know how to open the case. I tried, but couldn't seem to get all the screws to come out. Anyway, blowing out whatever dust in the other fans didn't do any good. It still crashes frequently (restarting the pc in the process). And on the white-on-black screen at startup, it still shows at the bottom the cpu temp at about 109-113 degrees F. after one of these crashes.

At this point in time the display will show the chassis temp at about 97 to 100 degrees F. (whatever it means by "chassis")...?

CPU fan will show speed of about 4963 rpm.

I have no idea what all this means.

I wish someone would invent a miniature refrigerated air conditioner to place near the air intake vent on this pc...:(

that's about 40-45 degrees C which is not really that hot for a modern CPU. Mine regularly runs at 55 C

----- Original Message ----
From: Lynn Perry <...>
To: glidos <...>
Sent: Friday, 3 August, 2007 6:10:45 PM
Subject: Re: [glidos] Glidos 1.38 and AMD

Lynn Perry <...> said:
Paul Gardiner <...> said:
Lynn Perry <...> said:
A short time after this, I tried running Orthos while running TR1. I let
the game run for over 30 minutes and started getting an intermittent
beep from the pc.
I quit the game and found the Orthos had stopped and turned red. It
showed some kind of error message, suggesting possible hardware failure
and told me to check the readme text. But I couldn't find any readme
text file in the Orthos package.
Is that where it's supposed to be?
That's how Orthos shows up problems, yes. And the beeping is your motherboard warning you of overheating.
But are you saying you get this only if running TR1 and Orthos together? Orthos should be able to show up problems all on its own. It would be strange (and interesting) if this happened only when running the two together.
Altogether, this is more evidence of perhaps your CPU cooler being clogged with dust.
Yes. The problem only showed when I ran both together. But I'll get the fans checked for dust asap. Thanks Paul.
Solo.
:)

My brotherinlaw used his canned air to blow out the outer fans. We didn't open the case to do the cpu fan. I don't know how to open the case. I tried, but couldn't seem to get all the screws to come out. Anyway, blowing out whatever dust in the other fans didn't do any good. It still crashes frequently (restarting the pc in the process). And on the white-on-black screen at startup, it still shows at the bottom the cpu temp at about 109-113 degrees F. after one of these crashes.

At this point in time the display will show the chassis temp at about 97 to 100 degrees F. (whatever it means by "chassis")...?

CPU fan will show speed of about 4963 rpm.

I have no idea what all this means.

I wish someone would invent a miniature refrigerated air conditioner to place near the air intake vent on this pc...:(

Lynn Perry wrote:
My brotherinlaw used his canned air to blow out the outer fans. We
didn't open the case to do the cpu fan. I don't know how to open the
case. I tried, but couldn't seem to get all the screws to come out.

Its the CPU fan that gets clogged, and its also the one that is important.

Anyway, blowing out whatever dust in the other fans didn't do any good.
It still crashes frequently (restarting the pc in the process). And on
the white-on-black screen at startup, it still shows at the bottom the
cpu temp at about 109–113 degrees F. after one of these crashes.
At this point in time the display will show the chassis temp at about 97
to 100 degrees F. (whatever it means by "chassis")...?

Hmmm. Provided that's really Fahrenheit then that's not high at all. Maybe heat isn't the problem, although you did say that sometimes
you'd get warning beeps, which is something motherboards are often
set up to do when overheated.

CPU fan will show speed of about 4963 rpm.

That's certainly fast enough. I should imagine that's quite
noisy.

I don't really know what to suggest now. Its all a bit
strange.

Paul

As you know, warning beeps come in certain patterns depending on the error, so it's worth noting the sequences and looking them up from another PC...

Beep Code: Description of Problem:

No Beeps Short, No power, Bad CPU/MB, Loose Peripherals
One Beep Everything is normal and Computer POSTed fine
Two Beeps POST/CMOS Error
One Long Beep, One Short Beep Motherboard Problem
One Long Beep, Two Short Beeps Video Problem
One Long Beep, Three Short Beeps Video Problem
Three Long Beeps Keyboard Error
Repeated Long Beeps Memory Error
Continuous Hi-Lo Beeps CPU Overheating

...where POST = Power On Self Test

I suggest Lynn also looks in the Windows event viewer, as there may be pertinent information there which could help identify the source of her problems - temperature is obviously not the case here.

Right-click 'My Computer', Manage, then expand Event Viewer and look in the Application and System sections. If you then right-click and select 'Properties' on the severe log files (red ones), you will see more detail about the error encountered. From there you may link to a potential resolution on Microsoft's website

Lynn, if you live close to Oxford, I would be happy to come and take a look for you for free. I usually charge £40 per hour, but friends/family and local Tomb Raider fanatics (whom I regard as friends anyway) get free service, though I may ask you to put a Guinness or two in the fridge in case I suddenly get really thirsty!

Regards

Richard

globox globox <...> said:
Paul As you know, warning beeps come in certain patterns depending on the error, so it's worth noting the sequences and looking them up from another PC... Beep Code: Description of Problem: No Beeps Short, No power, Bad CPU/MB, Loose Peripherals One Beep Everything is normal and Computer POSTed fine Two Beeps POST/CMOS Error One Long Beep, One Short Beep Motherboard Problem One Long Beep, Two Short Beeps Video Problem One Long Beep, Three Short Beeps Video Problem Three Long Beeps Keyboard Error Repeated Long Beeps Memory Error Continuous Hi-Lo Beeps CPU Overheating ...where POST = Power On Self Test I suggest Lynn also looks in the Windows event viewer, as there may be pertinent information there which could help identify the source of her problems - temperature is obviously not the case here. Right-click 'My Computer', Manage, then expand Event Viewer and look in the Application and System sections. If you then right-click and select 'Properties' on the severe log files (red ones), you will see more detail about the error encountered. From there you may link to a potential resolution on Microsoft's website Lynn, if you live close to Oxford, I would be happy to come and take a look for you for free. I usually charge £40 per hour, but friends/family and local Tomb Raider fanatics (whom I regard as friends anyway) get free service, though I may ask you to put a Guinness or two in the fridge in case I suddenly get really thirsty! Regards Richard Paul Gardiner wrote: div.kinomi { background-color: white; min-width: 680px; overflow: hidden; width: 100%; font-family: "Trebuchet MS", Helvetica, Swiss, Arial, Geneva, sans-serif; } div.kinomi .attachments { background-color: #f0f0ff; margin: 0 0 12px; padding: 4px; } div.kinomi .attachments table { margin: 0; } div.kinomi .attachments td { padding: 0 0 0 16px; vertical-align: top; } div.kinomi .buttons { border-top: 1px solid #284580; padding: 8px 0 0; } div.kinomi .buttons a { background: ButtonFace; color: ButtonText; border: 1px solid; border-color: ButtonHighlight ButtonShadow ButtonShadow ButtonHighlight; font-size: 85%; text-decoration: none; margin: 0 8px 0 0; padding: 2px 8px; } div.kinomi .footer { clear: both; color: #606060; font-size: 80%; font-style: italic; border-top: 1px solid #a0a0a0; padding: 2px 0 0; } div.kinomi .message img { border: none; display: block; margin: 0 0 12px; } div.kinomi .part { margin: 0 0 12px; } div.kinomi .part a.contact, div.kinomi .part a.event, div.kinomi .part a.suggestedTag { text-decoration: none; } div.kinomi .part a.contact:hover, div.kinomi .part a.event:hover, div.kinomi .part a.suggestedTag:hover { text-decoration: underline; } div.kinomi .part blockquote { color: #404040; margin: 2px 0 8px 16px; padding-left: 8px; border-left: 1px solid #a0a0ff; } div.kinomi .part h1 { font-size: 140%; margin: 16px 0 8px; } div.kinomi .part h2 { font-size: 130%; margin: 16px 0 8px; } div.kinomi .part h3 { font-size: 120%; margin: 12px 0 8px; } div.kinomi .part h4 { font-size: 110%; margin: 12px 0 8px; } div.kinomi .part h5 { font-size: 100%; margin: 8px 0 8px; } div.kinomi .part img { border: none; display: block; margin: 0 0 12px; } div.kinomi .part ol, div.kinomi .part ul { margin: 8px 0 8px 40px; padding: 0; } div.kinomi .part p { margin: 0 0 8px; } div.kinomi .poll { background-color: #e0e0ff; padding: 8px; margin: 0 0 12px; } div.kinomi .poll p.choice { margin: 2px 0 2px 24px; } div.kinomi .poll p.info { margin: 6px 0 12px; } div.kinomi .embedded { margin-left: 40px; } div.kinomi .embedded h2.subject { background-color: #284580; color: white; font-size: 100%; margin: 24px 0 4px; padding: 0 2px; } div.kinomi .embedded table.authorDate { font-size: 90%; font-style: italic; margin: 0 0 4px; width: 100%; } div.kinomi .embedded td.author { padding: 0; text-align: left; } div.kinomi .embedded td.date { padding: 0; text-align: right; } div.kinomi .attachments h3, div.kinomi .poll h3 { font-size: 100%; margin: 0 0 2px; } div.kinomi .recipients {font-size: 80%; font-style: italic; margin: 0 0 12px; } div.kinomi .adverts { background-color: #f0f0f0; margin: 24px 0 0; padding: 8px; } div.kinomi .adverts .advert { margin: 0 0 10px; } div.kinomi .adverts .title { color: #ff0000; font-size: 80% } div.kinomi .adverts .description { color: #000000; font-size: 70% } div.kinomi .adverts a { font-size: 80% } div.kinomi .links { font-size: 70%; margin: 12px 0 0; } div.kinomi .related { background-color: #f0f0ff; font-size: 85%; padding: 8px; margin: 0 0 0 16px; } div.kinomi .related h3 { font-size: 100%; margin: 0 0 8px; } div.kinomi .related h4 { font-size: 100%; font-weight: normal; margin: 4px 0 0; } div.kinomi .related ul { margin: 2px 0 12px 24px; padding: 0;} div.kinomi .related .detail { font-style: italic; } div.kinomi .visit { background-color: #f0f0ff; font-size: 85%; font-weight: bold; margin: 0 0 12px 16px; padding: 8px; } div.kinomi .main { float: left; margin: 0 0 16px; width: 74.9%; } div.kinomi .part .main { float: none; width: auto; } div.kinomi .right { float: left; margin: 0 0 16px; width: 24.9%; } div.kinomi .right a { text-decoration: none; } div.kinomi .right a:hover { text-decoration: underline; } Lynn Perry wrote: My brotherinlaw used his canned air to blow out the outer fans. We didn't open the case to do the cpu fan. I don't know how to open the case. I tried, but couldn't seem to get all the screws to come out. Its the CPU fan that gets clogged, and its also the one that is important. Anyway, blowing out whatever dust in the other fans didn't do any good. It still crashes frequently (restarting the pc in the process). And on the white-on-black screen at startup, it still shows at the bottom the cpu temp at about 109â€“113 degrees F. after one of these crashes. At this point in time the display will show the chassis temp at about 97 to 100 degrees F. (whatever it means by "chassis")...? Hmmm. Provided that's really Fahrenheit then that's not high at all. Maybe heat isn't the problem, although you did say that sometimes you'd get warning beeps, which is something motherboards are often set up to do when overheated. CPU fan will show speed of about 4963 rpm. That's certainly fast enough. I should imagine that's quite noisy. I don't really know what to suggest now. Its all a bit strange. www.jiglu.com – making communities, smarter

The intermittent beep I heard occurred every several seconds. I can only describe it as a beep. Whether it would be called long or short I'm not sure.

Also I forgot to mention that sometimes the cpu fan speed varies after one of these crash events. e.g., 4963 rpm one time and 5113 rpm the next time.

The fans do make some sound, but they don't seem all that noisy to me.

After your message I did look in the event viewer. Most of it means nothing to me. There were several red x-ed items. One or two "fault bucket" items. One or two that seemed to be related to the internet connection. And several claiming "application error"...mostly related to glidos. It still didn't tell me exactly WHAT happened...:(

Um...they might sell Guinness at a local private club or at the package store in the next county...but I usually don't go over to the next county...and I never go to the private clubs. :) (grin).

Also...is Oxford north or south of Fort Worth?...Iffen it's up north in Yankeeland, ah ain't goin' there. :)) <=== big cheezy grin.

Solo.

you're not in the UK right near to Paul and myself then?

Lynn Perry <...> wrote:

globox globox <...> said:
Paul As you know, warning beeps come in certain patterns depending on the error, so it's worth noting the sequences and looking them up from another PC... Beep Code: Description of Problem: No Beeps Short, No power, Bad CPU/MB, Loose Peripherals One Beep Everything is normal and Computer POSTed fine Two Beeps POST/CMOS Error One Long Beep, One Short Beep Motherboard Problem One Long Beep, Two Short Beeps Video Problem One Long Beep, Three Short Beeps Video Problem Three Long Beeps Keyboard Error Repeated Long Beeps Memory Error Continuous Hi-Lo Beeps CPU Overheating ...where POST = Power On Self Test I suggest Lynn also looks in the Windows event viewer, as there may be pertinent information there which could help identify the source of her problems - temperature is obviously not the case here. Right-click 'My Computer', Manage, then expand Event Viewer and look in the Application and System sections. If you then right-click and select 'Properties' on the severe log files (red ones), you will see more detail about the error encountered. From there you may link to a potential resolution on Microsoft's website Lynn, if you live close to Oxford, I would be happy to come and take a look for you for free. I usually charge Â£40 per hour, but friends/family and local Tomb Raider fanatics (whom I regard as friends anyway) get free service, though I may ask you to put a Guinness or two in the fridge in case I suddenly get really thirsty! Regards Richard Paul Gardiner wrote: div.kinomi { background-color: white; min-width: 680px; overflow: hidden; width: 100%; font-family: "Trebuchet MS", Helvetica, Swiss, Arial, Geneva, sans-serif; } div.kinomi .attachments { background-color: #f0f0ff; margin: 0 0 12px; padding: 4px; } div.kinomi .attachments table { margin: 0; } div.kinomi .attachments td { padding: 0 0 0 16px; vertical-align: top; } div.kinomi .buttons { border-top: 1px solid #284580; padding: 8px 0 0; } div.kinomi .buttons a { background: ButtonFace; color: ButtonText; border: 1px solid; border-color: ButtonHighlight ButtonShadow ButtonShadow ButtonHighlight; font-size: 85%; text-decoration: none; margin: 0 8px 0 0; padding: 2px 8px; } div.kinomi .footer { clear: both; color: #606060; font-size: 80%; font-style: italic; border-top: 1px solid #a0a0a0; padding: 2px 0 0; } div.kinomi .message img { border: none; display: block; margin: 0 0 12px; } div.kinomi .part { margin: 0 0 12px; } div.kinomi .part a.contact, div.kinomi .part a.event, div.kinomi .part a.suggestedTag { text-decoration: none; } div.kinomi .part a.contact:hover, div.kinomi .part a.event:hover, div.kinomi .part a.suggestedTag:hover { text-decoration: underline; } div.kinomi .part blockquote { color: #404040; margin: 2px 0 8px 16px; padding-left: 8px; border-left: 1px solid #a0a0ff; } div.kinomi .part h1 { font-size: 140%; margin: 16px 0 8px; } div.kinomi .part h2 { font-size: 130%; margin: 16px 0 8px; } div.kinomi .part h3 { font-size: 120%; margin: 12px 0 8px; } div.kinomi .part h4 { font-size: 110%; margin: 12px 0 8px; } div.kinomi .part h5 { font-size: 100%; margin: 8px 0 8px; } div.kinomi .part img { border: none; display: block; margin: 0 0 12px; } div.kinomi .part ol, div.kinomi .part ul { margin: 8px 0 8px 40px; padding: 0; } div.kinomi .part p { margin: 0 0 8px; } div.kinomi .poll { background-color: #e0e0ff; padding: 8px; margin: 0 0 12px; } div.kinomi .poll p.choice { margin: 2px 0 2px 24px; } div.kinomi .poll p.info { margin: 6px 0 12px; } div.kinomi .embedded { margin-left: 40px; } div.kinomi .embedded h2.subject { background-color: #284580; color: white; font-size: 100%; margin: 24px 0 4px; padding: 0 2px; } div.kinomi .embedded table.authorDate { font-size: 90%; font-style: italic; margin: 0 0 4px; width: 100%; } div.kinomi .embedded td.author { padding: 0; text-align: left; } div.kinomi .embedded td.date { padding: 0; text-align: right; } div.kinomi .attachments h3, div.kinomi .poll h3 { font-size: 100%; margin: 0 0 2px; } div.kinomi .recipients {font-size: 80%; font-style: italic; margin: 0 0 12px; } div.kinomi .adverts { background-color: #f0f0f0; margin: 24px 0 0; padding: 8px; } div.kinomi .adverts .advert { margin: 0 0 10px; } div.kinomi .adverts .title { color: #ff0000; font-size: 80% } div.kinomi .adverts .description { color: #000000; font-size: 70% } div.kinomi .adverts a { font-size: 80% } div.kinomi .links { font-size: 70%; margin: 12px 0 0; } div.kinomi .related { background-color: #f0f0ff; font-size: 85%; padding: 8px; margin: 0 0 0 16px; } div.kinomi .related h3 { font-size: 100%; margin: 0 0 8px; } div.kinomi .related h4 { font-size: 100%; font-weight: normal; margin: 4px 0 0; } div.kinomi .related ul { margin: 2px 0 12px 24px; padding: 0;} div.kinomi .related .detail { font-style: italic; } div.kinomi .visit { background-color: #f0f0ff; font-size: 85%; font-weight: bold; margin: 0 0 12px 16px; padding: 8px; } div.kinomi .main { float: left; margin: 0 0 16px; width: 74.9%; } div.kinomi .part .main { float: none; width: auto; } div.kinomi .right { float: left; margin: 0 0 16px; width: 24.9%; } div.kinomi .right a { text-decoration: none; } div.kinomi .right a:hover { text-decoration: underline; } Lynn Perry wrote: My brotherinlaw used his canned air to blow out the outer fans. We didn't open the case to do the cpu fan. I don't know how to open the case. I tried, but couldn't seem to get all the screws to come out. Its the CPU fan that gets clogged, and its also the one that is important. Anyway, blowing out whatever dust in the other fans didn't do any good. It still crashes frequently (restarting the pc in the process). And on the white-on-black screen at startup, it still shows at the bottom the cpu temp at about 109Ã¢â‚¬â€œ113 degrees F. after one of these crashes. At this point in time the display will show the chassis temp at about 97 to 100 degrees F. (whatever it means by "chassis")...? Hmmm. Provided that's really Fahrenheit then that's not high at all. Maybe heat isn't the problem, although you did say that sometimes you'd get warning beeps, which is something motherboards are often set up to do when overheated. CPU fan will show speed of about 4963 rpm. That's certainly fast enough. I should imagine that's quite noisy. I don't really know what to suggest now. Its all a bit strange. www.jiglu.com â€“ making communities, smarter
The intermittent beep I heard occurred every several seconds. I can only describe it as a beep. Whether it would be called long or short I'm not sure.
Also I forgot to mention that sometimes the cpu fan speed varies after one of these crash events. e.g., 4963 rpm one timeÂ and 5113 rpm the next time.
The fans do make some sound, but they don't seem all that noisy to me.
After your message I did look in the event viewer. Most of it means nothing to me. There were several red x-ed items. One or two "fault bucket" items. One or two that seemed to be related to the internet connection. And several claiming "application error"...mostly related to glidos. It still didn't tell me exactly WHAT happened...:(
Um...they might sell Guinness at a local private club or at the package store in the next county...but I usually don't go over to the next county...and I never go to the private clubs. :) (grin).
Also...is Oxford north or south of Fort Worth?...Iffen it's up north in Yankeeland, ah ain't goin' there. :)) <=== big cheezy grin.
Solo.
www.jiglu.com – making communities, smarter

globox wrote:
Paul
As you know, warning beeps come in certain patterns depending on the
error, so it's worth noting the sequences and looking them up from
another PC...
Beep Code: Description of Problem:
No Beeps Short, No power, Bad CPU/MB, Loose Peripherals
One Beep Everything is normal and Computer POSTed fine
Two Beeps POST/CMOS Error
One Long Beep, One Short Beep Motherboard Problem
One Long Beep, Two Short Beeps Video Problem
One Long Beep, Three Short Beeps Video Problem
Three Long Beeps Keyboard Error
Repeated Long Beeps Memory Error
Continuous Hi-Lo Beeps CPU Overheating
...where POST = Power On Self Test

I knew some motherboards did this sort of thing, but I didn't
know there were any standard use of beeps across the
different makes of motherboard. Very interesting.

Come to think of it, it might be worth trying running Glidos in DirectX, rather than OpenGL. You can get to the setting via the "Adjust..." button.

Paul Gardiner <...> said:
Come to think of it, it might be worth trying running Glidos in DirectX, rather than OpenGL. You can get to the setting via the "Adjust…" button.

Well...okay. I can try that. But why do I want to try it?

globox globox <...> said:
you're not in the UK right near to Paul and myself then? Lynn Perry wrote: div.kinomi { background-color: white; min-width: 680px; overflow: hidden; width: 100%; font-family: "Trebuchet MS", Helvetica, Swiss, Arial, Geneva, sans-serif; } div.kinomi .attachments { background-color: #f0f0ff; margin: 0 0 12px; padding: 4px; } div.kinomi .attachments table { margin: 0; } div.kinomi .attachments td { padding: 0 0 0 16px; vertical-align: top; } div.kinomi .buttons { border-top: 1px solid #284580; padding: 8px 0 0; } div.kinomi .buttons a { background: ButtonFace; color: ButtonText; border: 1px solid; border-color: ButtonHighlight ButtonShadow ButtonShadow ButtonHighlight; font-size: 85%; text-decoration: none; margin: 0 8px 0 0; padding: 2px 8px; } div.kinomi .footer { clear: both; color: #606060; font-size: 80%; font-style: italic; border-top: 1px solid #a0a0a0; padding: 2px 0 0; } div.kinomi .message img { border: none; display: block; margin: 0 0 12px; } div.kinomi .part { margin: 0 0 12px; } div.kinomi .part a.contact, div.kinomi .part a.event, div.kinomi .part a.suggestedTag { text-decoration: none; } div.kinomi .part a.contact:hover, div.kinomi .part a.event:hover, div.kinomi .part a.suggestedTag:hover { text-decoration: underline; } div.kinomi .part blockquote { color: #404040; margin: 2px 0 8px 16px; padding-left: 8px; border-left: 1px solid #a0a0ff; } div.kinomi .part h1 { font-size: 140%; margin: 16px 0 8px; } div.kinomi .part h2 { font-size: 130%; margin: 16px 0 8px; } div.kinomi .part h3 { font-size: 120%; margin: 12px 0 8px; } div.kinomi .part h4 { font-size: 110%; margin: 12px 0 8px; } div.kinomi .part h5 { font-size: 100%; margin: 8px 0 8px; } div.kinomi .part img { border: none; display: block; margin: 0 0 12px; } div.kinomi .part ol, div.kinomi .part ul { margin: 8px 0 8px 40px; padding: 0; } div.kinomi .part p { margin: 0 0 8px; } div.kinomi .poll { background-color: #e0e0ff; padding: 8px; margin: 0 0 12px; } div.kinomi .poll p.choice { margin: 2px 0 2px 24px; } div.kinomi .poll p.info { margin: 6px 0 12px; } div.kinomi .embedded { margin-left: 40px; } div.kinomi .embedded h2.subject { background-color: #284580; color: white; font-size: 100%; margin: 24px 0 4px; padding: 0 2px; } div.kinomi .embedded table.authorDate { font-size: 90%; font-style: italic; margin: 0 0 4px; width: 100%; } div.kinomi .embedded td.author { padding: 0; text-align: left; } div.kinomi .embedded td.date { padding: 0; text-align: right; } div.kinomi .attachments h3, div.kinomi .poll h3 { font-size: 100%; margin: 0 0 2px; } div.kinomi .recipients {font-size: 80%; font-style: italic; margin: 0 0 12px; } div.kinomi .adverts { background-color: #f0f0f0; margin: 24px 0 0; padding: 8px; } div.kinomi .adverts .advert { margin: 0 0 10px; } div.kinomi .adverts .title { color: #ff0000; font-size: 80% } div.kinomi .adverts .description { color: #000000; font-size: 70% } div.kinomi .adverts a { font-size: 80% } div.kinomi .links { font-size: 70%; margin: 12px 0 0; } div.kinomi .related { background-color: #f0f0ff; font-size: 85%; padding: 8px; margin: 0 0 0 16px; } div.kinomi .related h3 { font-size: 100%; margin: 0 0 8px; } div.kinomi .related h4 { font-size: 100%; font-weight: normal; margin: 4px 0 0; } div.kinomi .related ul { margin: 2px 0 12px 24px; padding: 0;} div.kinomi .related .detail { font-style: italic; } div.kinomi .visit { background-color: #f0f0ff; font-size: 85%; font-weight: bold; margin: 0 0 12px 16px; padding: 8px; } div.kinomi .main { float: left; margin: 0 0 16px; width: 74.9%; } div.kinomi .part .main { float: none; width: auto; } div.kinomi .right { float: left; margin: 0 0 16px; width: 24.9%; } div.kinomi .right a { text-decoration: none; } div.kinomi .right a:hover { text-decoration: underline; } globox globox said: Paul As you know, warning beeps come in certain patterns depending on the error, so it's worth noting the sequences and looking them up from another PC... Beep Code: Description of Problem: No Beeps Short, No power, Bad CPU/MB, Loose Peripherals One Beep Everything is normal and Computer POSTed fine Two Beeps POST/CMOS Error One Long Beep, One Short Beep Motherboard Problem One Long Beep, Two Short Beeps Video Problem One Long Beep, Three Short Beeps Video Problem Three Long Beeps Keyboard Error Repeated Long Beeps Memory Error Continuous Hi-Lo Beeps CPU Overheating ...where POST = Power On Self Test I suggest Lynn also looks in the Windows event viewer, as there may be pertinent information there which could help identify the source of her problems - temperature is obviously not the case here. Right-click 'My Computer', Manage, then expand Event Viewer and look in the Application and System sections. If you then right-click and select 'Properties' on the severe log files (red ones), you will see more detail about the error encountered. From there you may link to a potential resolution on Microsoft's website Lynn, if you live close to Oxford, I would be happy to come and take a look for you for free. I usually charge Â£40 per hour, but friends/family and local Tomb Raider fanatics (whom I regard as friends anyway) get free service, though I may ask you to put a Guinness or two in the fridge in case I suddenly get really thirsty! Regards Richard Paul Gardiner wrote: div.kinomi { background-color: white; min-width: 680px; overflow: hidden; width: 100%; font-family: "Trebuchet MS", Helvetica, Swiss, Arial, Geneva, sans-serif; } div.kinomi .attachments { background-color: #f0f0ff; margin: 0 0 12px; padding: 4px; } div.kinomi .attachments table { margin: 0; } div.kinomi .attachments td { padding: 0 0 0 16px; vertical-align: top; } div.kinomi .buttons { border-top: 1px solid #284580; padding: 8px 0 0; } div.kinomi .buttons a { background: ButtonFace; color: ButtonText; border: 1px solid; border-color: ButtonHighlight ButtonShadow ButtonShadow ButtonHighlight; font-size: 85%; text-decoration: none; margin: 0 8px 0 0; padding: 2px 8px; } div.kinomi .footer { clear: both; color: #606060; font-size: 80%; font-style: italic; border-top: 1px solid #a0a0a0; padding: 2px 0 0; } div.kinomi .message img { border: none; display: block; margin: 0 0 12px; } div.kinomi .part { margin: 0 0 12px; } div.kinomi .part a.contact, div.kinomi .part a.event, div.kinomi .part a.suggestedTag { text-decoration: none; } div.kinomi .part a.contact:hover, div.kinomi .part a.event:hover, div.kinomi .part a.suggestedTag:hover { text-decoration: underline; } div.kinomi .part blockquote { color: #404040; margin: 2px 0 8px 16px; padding-left: 8px; border-left: 1px solid #a0a0ff; } div.kinomi .part h1 { font-size: 140%; margin: 16px 0 8px; } div.kinomi .part h2 { font-size: 130%; margin: 16px 0 8px; } div.kinomi .part h3 { font-size: 120%; margin: 12px 0 8px; } div.kinomi .part h4 { font-size: 110%; margin: 12px 0 8px; } div.kinomi .part h5 { font-size: 100%; margin: 8px 0 8px; } div.kinomi .part img { border: none; display: block; margin: 0 0 12px; } div.kinomi .part ol, div.kinomi .part ul { margin: 8px 0 8px 40px; padding: 0; } div.kinomi .part p { margin: 0 0 8px; } div.kinomi .poll { background-color: #e0e0ff; padding: 8px; margin: 0 0 12px; } div.kinomi .poll p.choice { margin: 2px 0 2px 24px; } div.kinomi .poll p.info { margin: 6px 0 12px; } div.kinomi .embedded { margin-left: 40px; } div.kinomi .embedded h2.subject { background-color: #284580; color: white; font-size: 100%; margin: 24px 0 4px; padding: 0 2px; } div.kinomi .embedded table.authorDate { font-size: 90%; font-style: italic; margin: 0 0 4px; width: 100%; } div.kinomi .embedded td.author { padding: 0; text-align: left; } div.kinomi .embedded td.date { padding: 0; text-align: right; } div.kinomi .attachments h3, div.kinomi .poll h3 { font-size: 100%; margin: 0 0 2px; } div.kinomi .recipients {font-size: 80%; font-style: italic; margin: 0 0 12px; } div.kinomi .adverts { background-color: #f0f0f0; margin: 24px 0 0; padding: 8px; } div.kinomi .adverts .advert { margin: 0 0 10px; } div.kinomi .adverts .title { color: #ff0000; font-size: 80% } div.kinomi .adverts .description { color: #000000; font-size: 70% } div.kinomi .adverts a { font-size: 80% } div.kinomi .links { font-size: 70%; margin: 12px 0 0; } div.kinomi .related { background-color: #f0f0ff; font-size: 85%; padding: 8px; margin: 0 0 0 16px; } div.kinomi .related h3 { font-size: 100%; margin: 0 0 8px; } div.kinomi .related h4 { font-size: 100%; font-weight: normal; margin: 4px 0 0; } div.kinomi .related ul { margin: 2px 0 12px 24px; padding: 0;} div.kinomi .related .detail { font-style: italic; } div.kinomi .visit { background-color: #f0f0ff; font-size: 85%; font-weight: bold; margin: 0 0 12px 16px; padding: 8px; } div.kinomi .main { float: left; margin: 0 0 16px; width: 74.9%; } div.kinomi .part .main { float: none; width: auto; } div.kinomi .right { float: left; margin: 0 0 16px; width: 24.9%; } div.kinomi .right a { text-decoration: none; } div.kinomi .right a:hover { text-decoration: underline; } Lynn Perry wrote: My brotherinlaw used his canned air to blow out the outer fans. We didn't open the case to do the cpu fan. I don't know how to open the case. I tried, but couldn't seem to get all the screws to come out. Its the CPU fan that gets clogged, and its also the one that is important. Anyway, blowing out whatever dust in the other fans didn't do any good. It still crashes frequently (restarting the pc in the process). And on the white-on-black screen at startup, it still shows at the bottom the cpu temp at about 109Ã¢â‚¬â€œ113 degrees F. after one of these crashes. At this point in time the display will show the chassis temp at about 97 to 100 degrees F. (whatever it means by "chassis")...? Hmmm. Provided that's really Fahrenheit then that's not high at all. Maybe heat isn't the problem, although you did say that sometimes you'd get warning beeps, which is something motherboards are often set up to do when overheated. CPU fan will show speed of about 4963 rpm. That's certainly fast enough. I should imagine that's quite noisy. I don't really know what to suggest now. Its all a bit strange. www.jiglu.com â€“ making communities, smarter The intermittent beep I heard occurred every several seconds. I can only describe it as a beep. Whether it would be called long or short I'm not sure. Also I forgot to mention that sometimes the cpu fan speed varies after one of these crash events. e.g., 4963 rpm one timeÂ and 5113 rpm the next time. The fans do make some sound, but they don't seem all that noisy to me. After your message I did look in the event viewer. Most of it means nothing to me. There were several red x-ed items. One or two "fault bucket" items. One or two that seemed to be related to the internet connection. And several claiming "application error"...mostly related to glidos. It still didn't tell me exactly WHAT happened...:( Um...they might sell Guinness at a local private club or at the package store in the next county...but I usually don't go over to the next county...and I never go to the private clubs. :) (grin). Also...is Oxford north or south of Fort Worth?...Iffen it's up north in Yankeeland, ah ain't goin' there. :)) <=== big cheezy grin. Solo. www.jiglu.com – making communities, smarter

Richard: Uh...no...There's a great big puddle 'a water atwixt us.

Solo. :D