This is probably not the rigth forum but I will ask anyway..
I have an old application that runs on a HP DL380G3 w2k server. I think the
cpu runs too quick and I would like to know if there is a way to decreas the
cpu speed.

Regards
Henrik

Probably able to "underclock" the FSB in the BIOS. Read your manual or
Contact HP.

Maximus wrote:

> This is probably not the rigth forum but I will ask anyway..
> I have an old application that runs on a HP DL380G3 w2k server. I think the
> cpu runs too quick and I would like to know if there is a way to decreas the
> cpu speed.
>
> Regards
> Henrik
>

While you're checking the manual, look for motherboard jumper settings
as well.

Depending on the undescribed problem symptoms, CPU speed may not be the
problem, of course.

Bob I wrote:
> Probably able to "underclock" the FSB in the BIOS. Read your manual or
> Contact HP.
>
> Maximus wrote:
>
>> This is probably not the rigth forum but I will ask anyway..
>> I have an old application that runs on a HP DL380G3 w2k server. I
>> think the cpu runs too quick and I would like to know if there is a
>> way to decreas the cpu speed.
>> Regards Henrik
>>
>

On Thu, 9 Dec 2004 01:57:02 -0800, "Maximus"
<(E-Mail Removed)> wrote:

>This is probably not the rigth forum but I will ask anyway..
>I have an old application that runs on a HP DL380G3 w2k server. I think the
>cpu runs too quick and I would like to know if there is a way to decreas the
>cpu speed.
>
>Regards
>Henrik

Depending on the applications compiling language, there might be
routines that correct speed sensitive problems. Do you write the code
and compile this program inhouse or was this a purchased app. If
purchased can you identify the app's name and if the provider still
supports it. You didn't say if it was a DOS or Win3.x, Win95, or
newer. There is compatibility features in Windows2000 that can be set.
Is the app crashing occasionally or all the time.

I would rather think about CPU instructions and program code. The CPU speed
dependancy sounds nonsense.

On Thu, 23 Dec 2004 13:38:40 -0500, "Jetro" <(E-Mail Removed)>
wrote:

>I would rather think about CPU instructions and program code. The CPU speed
>dependancy sounds nonsense.
>

Not so, In the DOS days and also early Windows, the system interrupts
behaved differently. A case in point would be the handling of
temporary filenames. The way that DOS made up a temporary filename bit
the dust when processors got so fast (50mhz+) that asking for two
tempory files caused an error because the system returned the same
filename for two or more consecutive files. Can't happen. Then there
were further problems with certain languages failing in systems with
processors above about 300mhz. So there are many older programs that
have big problems. Usually people have moved on to newer programs or
there are updates that solve the problems.

I remember all major computer technology leaps for the last 20 years.
Examples with IRQs handling, DOS, and certain (programming) languages just
prove my point with regard to internal CPU processing and antiquated
inefficient program code which both aren't related to CPU speed. I would
compare this problem with the elders on the road: they can keep their speed
just below 30 mph and cannot turn sharp no matter what they drive either
tricycle or Porche. If they would drive faster and make an accident - will
you blame Porche (CPU) for its speed or driver (OS and other programs) for
his slackness?