Thought I would try Avalaunch.
I have font exploit. Boots up using Phoenix Loader 1.2 with 4977 BFM BIOS.
Got Avalaunch 0.47 (haven't tried repack yet... maybe that fix?).
I can run Avalaunch from Evox and BoxPlorer with no problems.
When I try to run it from drive E: on system startup with custom 4977BFM BIOS (E:\avalaunch\default.xbe) it does not work and I just get a black screen.
I have tried XBMP with custom 4977BFM BIOS same way and it works (ie. E:\XBMP\default.xbe). I did this just to make sure my BIOS editing technique is correct.
FYI, I created different BIOS with Xbtool which load different things.
I will try later flashing a new BIOS on my X2 Pro and see if Avalaunch boots.
So far I think it could be a bug in Avalaunch, bug in Phoenix, or Avalaunch didn't like where I loaded it from when loaded as a dash ?
This post has been edited by IntestineMan: Jul 28 2003, 04:42 PM