xboxscene.org forums

Author Topic: Dev. System Question  (Read 90 times)

old engineer

  • Archived User
  • Full Member
  • *
  • Posts: 155
Dev. System Question
« on: October 26, 2005, 10:23:00 AM »

Are you serious, or just having a laugh?
Logged

Tp21

  • Archived User
  • Jr. Member
  • *
  • Posts: 58
Dev. System Question
« Reply #1 on: October 26, 2005, 12:14:00 PM »

tongue.gif) ... it's just the bios that's diffrent and extra ram...
if you want 2 extra usb ports + serial you could just use the chip from an PC-motherboard... (forgot the name, all the external things are connected to it (mouse,keyboard,usb,serial,parralel) if you have an relative new motherboard (PC) it's connected too the LPC bus.
you could just "Reconnect" it in the xbox
Logged

fghjj

  • Archived User
  • Sr. Member
  • *
  • Posts: 288
Dev. System Question
« Reply #2 on: October 26, 2005, 04:39:00 PM »

I too find the startpost confusing. You want to take an Xbox, do lots of research and finally resolder it into an XDK, all that to make a long nose at MS? Are you aware that:

-You can buy XDK's for a few 100 of $ of eBay once in a while.

-If you mod you box (softmod chip or tsop), download the XDK-software from your favorite war3z trade place, you can start development right away? You don't need anymore hardware modifications.

-You really don't need a DVD emulator, unless you plan to make a 4.7 GB sized program and distribute it globally on DVD (and get sued by MS).

-You don't even need 128 MB, unless you intend to develop a program that will rock the Xbox world like XBMC?

-You really really really don't need to bother with MCPX, parallel ports, serial ports, megabits per second or DVD cables.
Logged

Pikkon

  • Archived User
  • Sr. Member
  • *
  • Posts: 410
Dev. System Question
« Reply #3 on: October 26, 2005, 04:59:00 PM »

The MCPX chip on a dev/debug kit is a X2,X3 is for retail.
The eeprom on a dev/debug kit is not blank.It contains
information.I used to own both of them so I know from
experience.But all in all just buy a real XDK or a Debug Kit.

Logged

Agent ME

  • Archived User
  • Full Member
  • *
  • Posts: 149
Dev. System Question
« Reply #4 on: November 01, 2005, 08:30:00 PM »

Yeah, I don't think the EEPROM is blank - I saw a pic somewhere on the net of a very very old XDK dash on a real XDK xbox. (Trust me, it was an old version - the menu options weren't spaced out very much, and no icons for the games in the main launcher screen) In the settings window, there was something for EEPROM signature, and it wasn't blank, so there must been an EEPROM, especially if they even bothered to have that in the settings window.

(But the person who had this was retarded - You could see the XDK wasn't on a network and the guy obviously doesn't know how to take in-game 100% quality pics)

And about the extra 64 mb RAM, you'll only need that if you want to play / make games that are very memory intensive, like Halo1 and 2.

And don't XDK's also have a faster CPU? On a retail-converted-to-XDK-without-the-extra-CPU/RAM, the video tool is very laggy and doesn't even pick up sound. But it obviously works better on a real XDK - it would kinda defeat its purpose if it didn't.
Logged

Pikkon

  • Archived User
  • Sr. Member
  • *
  • Posts: 410
Dev. System Question
« Reply #5 on: November 02, 2005, 06:36:00 AM »

The CPU on a retail and dev/debug kit is the same.
And yes on a dev/debug kit you can record videos
and take screen shots.And your framerate will be fine
as the dev box's have 128 ram.Or just upgrade a
retail xbox from 64 to 128 ram.
Logged

Brouhaha

  • Archived User
  • Full Member
  • *
  • Posts: 213
Dev. System Question
« Reply #6 on: November 02, 2005, 01:02:00 PM »

QUOTE(Ecrofirt @ Nov 2 2005, 01:52 PM)
So it's a ram issue that's causing my framerate to dip so much when I use the movie tool? My game only uses 8MB of physical memory, so I'm suprised by this.
Logged

atomiX

  • Archived User
  • Sr. Member
  • *
  • Posts: 492
Dev. System Question
« Reply #7 on: November 04, 2005, 07:40:00 AM »

wink.gif
Logged