If you're having trouble with launching the 32-bit client (just guessing here, from your posting twice in ~13 hours about this)
, it would be a good idea to get 32-bit D3 working; using 64-bit should be an alternative for performance reasons, not because "it doesn't work at all with 32-bit." If you're getting crashes with 32-bit, your course of action at this time should be troubleshooting that (e.g. you post that D3 is crashing for you, not in one of the 2.4.3 threads, and then we ask for "Comptibility diagnostics" from ISBoxer's Help menu and try to help find what is causing the crash, and so on) and not asking when 64-bit support will be ready (... what if you just have the same problem after I post that 64-bit is working?)
centor wrote:When isboxer will be compatible with diablo 3 64 bit ?
Just as soon as I am able to track down the final bug that stops you from using Diablo 3 64-bit. Work is in progress.
Again, 2.4.3 introduced some pretty major changes to the client -- Direct3D 11 and 64-bit support. In addition, they use a new system during login (not mentioned in the patch notes because you wouldn't usually need to know) that happened to break Inner Space with D3 entirely.
It does take time to work through issues like this.