Renderer creation error: HAL device not available for default adapter

After download and installation of PE I wanted to log in with the client
software of Project Entropia with the button “Launch PE”,
then however only the error message occured: Renderer creation error: HAL
DEVICE emergency available for default adapter.
My System:
Windows 2000 SP4 all Windows Updates
1024 MB RAM
AMD Sempron 2600+ CPU
ATI Radeon 9250 Grafic Adapter
ATI Driver 6525
Res. 1152x862 (32 bit)
A DirectX compat. Audiosystem
DirectX version 9.0c
9 GB free Harddisk
Internetconnection: DSL 1024kbit

and that should do! :rolleyes:

Thanks for support and best regards,

Tom

No offence mate, but you will get a lot more responses when writing in English, since the main language in here are Englis :slight_smile:

Good luck! :slight_smile:

Taxita :tongue2:

:slight_smile: After restarting my machine and trying to log in that error didn’t occur again!

:mad: But there is a new Problem: I’m allways loosing connection after some seconds and I’m forced to log in again.

:eek: Because its an other topic, I will start a new thread!

Thanks! Tom

Edit : Removed. :slight_smile:

time to warm up this old topic. I took the oldest one about this issue to show how old problems we still get and how to solve them without “professional MA support” =)

renderer error, HAL device, possible reason not enough memory etc. errors get resolved (in case of ATI cards at least) if you do not use the latest drivers as MA suggests. far from that, I had to use more than half a year old ones to get my freshly installed ndoze working with PE. and believe me, I’ve tried everything before that (vga and motherboard agp/gart driver, directx, PE reinstall, you name it).

so, if you have some uncertain error and can’t find the solution, run dxdiag and see if you can test direct3d and directdraw from there. if direct3d, which current PE seems to need desperately, fails then it’s simply vga driver mistake. cool that ATI has this site for old revision drivers, I was lucky to get it working after going back in driver history for 3-4 generations =)

yes, another thing people might try before all that is system restore which in some cases works like magic, but not always.

I couldn’t find any sticky topics for vga related error solving. if there is such, this might be of some value to insert in there…

J.

I’ve seen HAL problems before…whatever you do, don’t leave the spacecraft without your helmet. :wink:

t