Jump to content


Photo

Cannot Start Avalaunch Direct From Phoenix 1.2


  • Please log in to reply
3 replies to this topic

#1 IntestineMan

IntestineMan

    X-S Senior Member

  • Members
  • PipPip
  • 188 posts

Posted 28 July 2003 - 04:41 PM

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 ?

Edited by IntestineMan, 28 July 2003 - 04:42 PM.


#2 checa

checa

    X-S Young Member

  • Members
  • Pip
  • 42 posts

Posted 09 August 2003 - 08:01 AM

has anyone fixed this problem? I use the font exploit also and would like to use Avalaunch instead of Evox.

#3 KamelRed

KamelRed

    X-S Senior Member

  • Members
  • PipPip
  • 189 posts
  • Location:USA
  • Interests:Xbox 360 is my interest... =
  • Xbox Version:v1.0
  • 360 version:v3.0 (falcon)

Posted 10 August 2003 - 05:15 AM

Rename Avalaunch's default.xbe to evoxdash.xbe. Worked for me.

#4 checa

checa

    X-S Young Member

  • Members
  • Pip
  • 42 posts

Posted 11 August 2003 - 01:00 AM

cool, thanks for the help.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users