xboxscene.org forums

Pages: 1 2 3 [4] 5

Author Topic: Evox M8 Release  (Read 664 times)

Diablov90

  • Archived User
  • Newbie
  • *
  • Posts: 22
Evox M8 Release
« Reply #45 on: July 07, 2004, 12:17:00 PM »
Where would the D0 point be?  Or is that the LFRAME? Also is the alternate D0 the same on all versions?
Logged

lookformeb

  • Archived User
  • Hero Member
  • *
  • Posts: 1442
Evox M8 Release
« Reply #46 on: July 07, 2004, 02:00:00 PM »
QUOTE (Diablov90 @ Jul 7 2004, 04:17 PM)
Where would the D0 point be?  Or is that the LFRAME? Also is the alternate D0 the same on all versions?

Look at the install guide for your chip.
Logged

Diablov90

  • Archived User
  • Newbie
  • *
  • Posts: 22
Evox M8 Release
« Reply #47 on: July 07, 2004, 04:21:00 PM »
But Xecuter doesnt have any diagrams on their site, since im installing a X2.3b lite on a 1.6.
Logged

xnice

  • Archived User
  • Newbie
  • *
  • Posts: 1
Evox M8 Release
« Reply #48 on: July 07, 2004, 06:09:00 PM »
I wonder if the tsop mod will work on 1.6's ever?
Logged

Diablov90

  • Archived User
  • Newbie
  • *
  • Posts: 22
Evox M8 Release
« Reply #49 on: July 07, 2004, 07:22:00 PM »
Whats the difference between the SmartXX diagram and the OzXodus diagram? I see only one wire that is different, but the rest is the same.
Logged

heydricas

  • Archived User
  • Newbie
  • *
  • Posts: 25
Evox M8 Release
« Reply #50 on: July 07, 2004, 07:29:00 PM »
rolleyes.gif Somebody knows if 1.6 have the Lframe in place ?????  ph34r.gif
Logged

Arakon

  • Archived User
  • Hero Member
  • *
  • Posts: 629
Evox M8 Release
« Reply #51 on: July 08, 2004, 12:52:00 AM »
considering that the 1.6 doesn't have a tsop in the first place, a "tsop mod" won't happen.
Logged

desertboy

  • Archived User
  • Hero Member
  • *
  • Posts: 523
Evox M8 Release
« Reply #52 on: July 08, 2004, 03:50:00 AM »
QUOTE (Arakon @ Jul 8 2004, 09:52 AM)
considering that the 1.6 doesn't have a tsop in the first place, a "tsop mod" won't happen.

There is a TSOP all because it's non flashable and incorporated into another chip it's still a TSOP.

It's not certain there's no reflashable TSOP it's only suspected only time will tell.

Logged

ToeFur

  • Archived User
  • Newbie
  • *
  • Posts: 9
Evox M8 Release
« Reply #53 on: July 08, 2004, 09:24:00 AM »
I'm having trouble opening the bios in x2bm.  I need the hash.  But I can't find it anywhere, and have no clue how to use md5sum.exe.
Logged

nyarrgh

  • Archived User
  • Jr. Member
  • *
  • Posts: 57
Evox M8 Release
« Reply #54 on: July 08, 2004, 09:44:00 AM »
Sorry in advance if this is a stupid question, and I HAVE read through the thread.


does the m8 bios support LBA48? and/or which type of LBA48 does it support?

Logged

heydricas

  • Archived User
  • Newbie
  • *
  • Posts: 25
Evox M8 Release
« Reply #55 on: July 08, 2004, 12:23:00 PM »
sad.gif
Logged

Exobex

  • Archived User
  • Hero Member
  • *
  • Posts: 1093
Evox M8 Release
« Reply #56 on: July 08, 2004, 12:41:00 PM »
QUOTE (nyarrgh @ Jul 8 2004, 05:44 PM)
Sorry in advance if this is a stupid question, and I HAVE read through the thread.


does the m8 bios support LBA48? and/or which type of LBA48 does it support?

<bumped to the top>
I have the same question.  I'm installing 160GB drives in many Xboxes now, so LBA48 support is essential.

I don't want to e-mail or PM Nightshd to ask about XBtool support, he's probably getting bombarded enough as it is!

For now I'll stick to M7, M8_16.bin will be handy when the 1.6 hits Wales, though.
Once XBtool gets updated (or LBA48 versions get released), I'll switch.  Might be tricky though, 1.0.22 can't even unpack the kernel!

BTW:-

CODE
ROM  = "EvoX M8",0xaa4d0820b932009090f780f0ee1d1b1c
ROM  = "EvoX M8 (1.6)",0xb6fe3d5cf9df635cbc4e48fbe2b469f1
Logged

heinrich

  • Archived User
  • Hero Member
  • *
  • Posts: 2274
Evox M8 Release
« Reply #57 on: July 08, 2004, 01:05:00 PM »
wink.gif


m8 does not support lba48
Logged

javi

  • Archived User
  • Newbie
  • *
  • Posts: 15
Evox M8 Release
« Reply #58 on: July 08, 2004, 04:16:00 PM »
wink.gif

heydricas: As far as i understood, you dont ground #lframe, you wire it to the modchip/flashrom #lframe pin.
(i'm not an LPC-expert, but that's what it read).
Logged

Exobex

  • Archived User
  • Hero Member
  • *
  • Posts: 1093
Evox M8 Release
« Reply #59 on: July 08, 2004, 11:19:00 PM »
QUOTE (javi @ Jul 9 2004, 12:16 AM)
hey Exobex, what do u think of Xyclops? Is it a flashable device? is there any new raincoat comming soon?  wink.gif

I won't know anything about Xyclops until I get a 1.6 machine to have a nose at.  However, indications so far are that it's not flashable, although there is one possibility that I can think of:-

The chip IS flashable
The chip does not respond to the usual "get manufacturer/device ID" commands, or
The chip has its manufacturer and device IDs set to 09, 00

Raincoat 0.6 or 0.7 would reject these (which it does to stop STOOOPID people adding a flash=0x0900,"Please kill my Xbox - pleeeeease",0x40000 line to their raincoat.conf file)
If it is indeed flashable, a newer raincoat would need an override function to allow flashing 0x09, 0x00 devices, unless the presence of a valid chip (and jumper points) can be determined by further reading of the BIOS from the chip.

In a nutshell: we'll see.

QUOTE

heydricas: As far as i understood, you dont ground #lframe, you wire it to the modchip/flashrom #lframe pin.
(i'm not an LPC-expert, but that's what it read).

As far as I can tell, you actually ground #LFRAME.  This knocks out the onboard BIOS chip (which needs it), but not the new-style LPC mod (which, thanks to M$'s earlier tinkering with the LPC bus, doesn't!).
M$'s method of stopping modchips has turned round and bitten them on the arse.
Logged
Pages: 1 2 3 [4] 5
« previous next »