As far as I remember, this inability to start CB were never related to those new drivers, but the "Disc-Control"-Function.
Originally Posted by kevstah2004
You say it, as if it were a proven fact that it is CBs embedded "ELF-Launcher", which is causing this "inability to start", while I rather think it has to do with the system-initialisation (and CBs inability to cope with that) and "environment" CB is running in.
try it with v4.30 it's a problem with Codebreaker's elf launcher and there's nothing the uLE dev's can do to fix that since they don't reprogram Codebreaker
PS2 V7/DMS3 V2 (FW:2.4b7); Seagate Baracuda 200GB
PS2 V7/CC1.0 (FW:34 hacked v2 BM:2.1.6); Maxtor DiamondMAX9 PLUS 160GB
PS2 SCPH-30004R; NoMod+NoLaser
3xSony MC 8MB
MAX/Datel 16MB with Boot-CD
Custom FMCB 1.8b+ Beta-Build, my AIO 0.5, Sony&xRhino-Linux