🚀 go-pugleaf

: Auke Bruinsma <air2@dds.nl> wrote:

>When the splash screen appears the harddisk is makking some noise
>but after a few seconds the noise stops and the system hangs!!

Jeff Overcash has prepared this information:

Make sure you are not running in 16 colors.  This is a Win98 bug (and a
bug that usually also stops the BDE Administrator in the Control Panel
from running).  You need to be using at least a 256 colours or more.  Here
is the standard answer for this question:

In all probability, this is a video driver bug.  What follows is the
standard list of fixes; unfortunately several of them are not applicable
under NT.

That's an indication that your video driver has a bug.  This is a bug in
how the driver is handling the ImageList API.  When building an image list
through the API, the driver starts the image in internal memory.  When the
list gets to a certain size it must switch to main memory to finish
building the TImageList.  This is when the freeze happens.  There is very
little Borland can do as this is a driver bug. This has traditionally hit
the S3 drivers.

Please try these work-arounds:

1) Get the latest driver (www.s3.com or your vendor if your vendor's
driver doesn't work, try the generic S3 driver as they tend to be more
compliant with the system specifications)

2) Start the IDE with the -ns switch

3) Under the [display] section of the SYSTEM.INI file add the following
line

    BusThrottle=1 (reboot afterwards)

4) Reduce the hardware acceleration for the card.

5) Reboot in safe mode and start BCB.  Goto the properties of the
component palette and hide all the controls that you rarely use. This will
reduce the size of the imagelist that is getting built and might get you
under the threshold.

6) Play with colour depth/resolution;  1024x768 in 16 bit color seems to
be the worst thing.

7) Get the latest DirectX drivers. 

Additionally, BCB4 cannot run in Windows 98 under 16 colour mode.  You
must be at least at 256 colors.

PS: If "BusThrottle" works for you, this is by far the best solution.  All
it does is instruct the driver that it must give a little time slice to
the OS so there is very little impact on performance (so far no one has
reported back to me that they can even tell a difference between using and
not using the "BusThrottle" setting except that Delphi runs).
Unfortunately not all drivers respect this setting.

-- 
 * Post to the right group - http://www.borland.com/newsgroups/
   * Do not cross- or multipost 
     * Research at http://www.mers.com/searchsite.html

Stefan Hoffmeister - http://www.econos.de/
(TeamB - http://www.teamb.com/)