Jump to content


  • Content Count

  • Joined

  • Last visited

  • Medals

Posts posted by Horus

  1. Again, with 1.12, there is aliasing or cracking visible between the LOD levels, but different to what happens with 1.11b, it seems here to be just visible on the sea mesh. Furthermore, when i move my player, the loading/streaming of the textures take much longer than with 1.09b or even 1.08, and then results in a black screen later. So first i've got untextured models loaded and then, when it started texturing, the screen went black. It did not crash, it just gave a black screen, and when i've killed the process, the Desktop switched down to 4 bit. A proper restart solved that oO.

    The cracking/alisiaing effect is visible through black lines on the outer edges of the nearest and the next LOD level on the sea mesh. I've provided shots and a little movie in the 1.11b troubleshooting thread to show how it looks like.

    Same problem here and for the 1 time i have ''CreateIndexBuffer failed'' error banghead.gif

  2. I think this is very important fix for server machines. More info:

    <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">List: openbsd-misc

    Subject: Intel Core 2

    From: Theo de Raadt <deraadt () cvs ! openbsd ! org>

    Date: 2007-06-27 17:08:16

    Message-ID: 200706271708.l5RH8GkK024621 () cvs ! openbsd ! org

    [Download message RAW]

    Various developers are busy implimenting workarounds for serious bugs

    in Intel's Core 2 cpu.

    These processors are buggy as hell, and some of these bugs don't just

    cause development/debugging problems, but will *ASSUREDLY* be

    exploitable from userland code.

    As is typical, BIOS vendors will be very late providing workarounds /

    fixes for these processors bugs. Some bugs are unfixable and cannot

    be worked around. Intel only provides detailed fixes to BIOS vendors

    and large operating system groups. Open Source operating systems are

    largely left in the cold.

    Full (current) errata from Intel:


    - We bet there are many more errata not yet announced -- every month

    this file gets larger.

    - Intel understates the impact of these erraata very significantly.

    Almost all operating systems will run into these bugs.

    - Basically the MMU simply does not operate as specified/implimented

    in previous generations of x86 hardware. It is not just buggy, but

    Intel has gone further and defined "new ways to handle page tables"

    (see page 58).

    - Some of these bugs are along the lines of "buffer overflow"; where

    a write-protect or non-execute bit for a page table entry is ignored.

    Others are floating point instruction non-coherencies, or memory

    corruptions -- outside of the range of permitted writing for the

    process -- running common instruction sequences.

    - All of this is just unbelievable to many of us.

    An easier summary document for some people to read:


    Note that some errata like AI65, AI79, AI43, AI39, AI90, AI99 scare

    the hell out of us. Some of these are things that cannot be fixed in

    running code, and some are things that every operating system will do

    until about mid-2008, because that is how the MMU has always been

    managed on all generations of Intel/AMD/whoeverelse hardware. Now

    Intel is telling people to manage the MMU's TLB flushes in a new and

    different way. Yet even if we do so, some of the errata listed are

    unaffected by doing so.

    As I said before, hiding in this list are 20-30 bugs that cannot be

    worked around by operating systems, and will be potentially

    exploitable. I would bet a lot of money that at least 2-3 of them


    For instance, AI90 is exploitable on some operating systems (but not

    OpenBSD running default binaries).

    At this time, I cannot recommend purchase of any machines based on the

    Intel Core 2 until these issues are dealt with (which I suspect will

    take more than a year). Intel must be come more transparent.

    (While here, I would like to say that AMD is becoming less helpful day

    by day towards open source operating systems too, perhaps because

    their serious errata lists are growing rapidly too).

  3. <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">A COUPLE OF WEEKS ago, we heard that Dell was dealing with a certain situation considering Intel dual-core MCW and quad-core KC architecture, and that the company was releasing urgent BIOS and microcode versions for its line up....

    Read more

  4. I have same problem with my A4Tech X-750BF mouse banghead.gif On their website FAQ i found this

    <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">Q: I have an A4 Tech 5-button mouse, it works properly in common applications, however, the 4th and 5th button do not work with some special games, why?

    A: Some games do not support these two additional buttons, if your game does not support these two buttons and did not provide option in the game configuration panel, both of them will not function properly. The best way to solve this problem is consult with your game company to get an updated version.

    Suma plz can you fix that confused_o.gif THX

  5. ..As soon as Securom confirms the fix and provides us with new executables we're going to provide new official hotfix and updated patches using the updated executables.

    Same response from Atari

    <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">...I am happy to report that SecuRom has identified the problem and that they are working on a hotfix that will fix this issue. They just passed a copy of the fix to the developer and then the developer (after they test it, etc.) will pass it to Atari US and we will release it on atarisupport.com

    We will also be re-releasing the 1.08 patch with the fix installed in it already shortly after.

    I will notify everyone once we have released the hotfix, it should come very soon...


    Atari, Inc.

    Digital Downloads and E-Commerce Producer

  6. So I take it j_f_oko and me are the only ones this hotfix didn't work for? Anyone else have problems with the 7.5 hotfix out there?

    Maybe u need turn off WHQL certification...start>control panel>system>hardware>driver signing...select 'Ignore - Install the software..' and tick the 'Make this action the system default' box. welcome.gif