xboxscene.org forums

Pages: 1 [2] 3 4 5

Author Topic: Problem With Dev System  (Read 691 times)

Agent ME

  • Archived User
  • Full Member
  • *
  • Posts: 149
Problem With Dev System
« Reply #15 on: November 09, 2005, 06:12:00 PM »
Argh...

So... is a debug kit's HD unlocked? I'm wondering if I can put it in my chipped xbox and FTP to it, like put on EvoX.

Or is it locked?
Logged

haza55

  • Archived User
  • Newbie
  • *
  • Posts: 49
Problem With Dev System
« Reply #16 on: November 09, 2005, 11:53:00 PM »
do u have a router if so turn on ur xbox and see wat ips are being used by ur xboxs mac address
and dev kit do read burnt dvds but make sure u have a debug xbe on that disc
Logged

haza55

  • Archived User
  • Newbie
  • *
  • Posts: 49
Problem With Dev System
« Reply #17 on: November 09, 2005, 11:55:00 PM »
debug kits where made to run like a retail xbox so i would say it might unless its a dev kit
Logged

haza55

  • Archived User
  • Newbie
  • *
  • Posts: 49
Problem With Dev System
« Reply #18 on: November 09, 2005, 11:56:00 PM »
can u take some photos of it including the case and both sides of the motherboard
Logged

bucko

  • Recovered User
  • Hero Member
  • *
  • Posts: 4255
Problem With Dev System
« Reply #19 on: November 10, 2005, 02:49:00 AM »
Ignore the bios bit on this, but this might be of help setting up XDK.

http://www.hydras-wo...oxretailtodebug
Logged

Pikkon

  • Archived User
  • Sr. Member
  • *
  • Posts: 410
Problem With Dev System
« Reply #20 on: November 10, 2005, 03:43:00 AM »
QUOTE(bucko @ Nov 10 2005, 09:56 AM)
Ignore the bios bit on this, but this might be of help setting up XDK.
Logged

Agent ME

  • Archived User
  • Full Member
  • *
  • Posts: 149
Problem With Dev System
« Reply #21 on: November 10, 2005, 08:33:00 PM »
If you want photos look at the ebay link. Even an inside pic. Can't see specifics to clearly, like writing on a chip, but you can count whats there and tell there's an LPC pin-header.

So... is there like something in an xbe that's easily changeable that defines if it is runnable on retail/modded xboxs or devkit xboxs? And this program deXBE changes it so devkits can read it? And I saw a program "ParchHeader" that said it'd make devkit xbes to retail/modded xbes? Am I correct on my thinking?

Also, with Quake2x (port of quake2) (Available off xbins at XBOX > GAMES > Quake2xBeta3) there's two xbe's. default_devkit.xbe default_retail.xbe. My modded retail xbox (with X3 BIOS) will load either one. What's the difference? Is the default_devkit for use on dev kit xboxs?

I'll try the thing Pikkon just mentioned.

PS: It says my Avalaunch (Avalaunch v0.49.1 (build 62)) is already for debug. That normal?
Logged

Agent ME

  • Archived User
  • Full Member
  • *
  • Posts: 149
Problem With Dev System
« Reply #22 on: November 10, 2005, 09:10:00 PM »
Ok, this comp doesn't have a dvd burner (I only have cheap burnable CD's that are known for xbox's unability to read them, and burnable DVDs which I hope that work). Let me try burning this on other comp.

Otherwise I'll need to rush to store to reburnable CD...

So if I get Avalaunch running on dev kit, I can FTP over debug kit files right?
Logged

Agent ME

  • Archived User
  • Full Member
  • *
  • Posts: 149
Problem With Dev System
« Reply #23 on: November 10, 2005, 09:46:00 PM »
OMFG L33TZ0RS!

I burned the Avalaunch disc and put it in... its running!

I got FTP connection - full access to all drives. Resembles an unmodded xbox. Not even a E/devkit folder. Definetely a sort of retail restore done.

Just Avalaunch just being Avalaunch, it locks up every 30 seconds... Maybe I should try burning EvoX or UnleashX (with debug fix obviously).
Logged

Paintballpsyco2369

  • Archived User
  • Jr. Member
  • *
  • Posts: 65
Problem With Dev System
« Reply #24 on: November 11, 2005, 12:41:00 AM »
A Development Xbox has a USB port on the back for a keyboard or mouse; it also has a Serial Port for Kernel debugging. Also on the Dev unit, there is a port similar to a Scusi port. It has a extra circuit board on the inside, slightly different cable (internally) 128 mg ram, and the software on the hard drive. A debug is basically a normal xbox, with a pin header already installed on the LPC bus, it has 128 mg ram as well, as a blanked EEPROM. Plus the Debug has a see through green case that says debug on the front, and the Den unit has a clear case with development kit on the front. Also on the Dev unit, the lid sits higher than on the on retail, or debug xboxs to accommodate the "extra stuff". Other than that the software that runs them if basically the same, just you can use more parts of it on the Development unit, such as the Kernel debugging, emulating, and the mouse and keyboard. The Development units are more for software developing, and the Debugs are more for testing, and other things. I hope this helps answer your question.
Logged

haza55

  • Archived User
  • Newbie
  • *
  • Posts: 49
Problem With Dev System
« Reply #25 on: November 11, 2005, 01:02:00 AM »
If any of u have seen the halo 2 doco u see the devolpers and usally they have 3 to 4 xboxs each one devkit which are the more expensize kits and 2 or 3 debug consoles and they have usb keyboards that plug into the xbox usb ports at the front.

man just burn a recovory disc, place in ur xbox and on ur pc run the recovery wizard.
Logged

Pikkon

  • Archived User
  • Sr. Member
  • *
  • Posts: 410
Problem With Dev System
« Reply #26 on: November 11, 2005, 03:53:00 AM »
QUOTE(Paintballpsyco2369 @ Nov 11 2005, 07:48 AM)
A Development Xbox has a USB port on the back for a keyboard or mouse; it also has a Serial Port for Kernel debugging. Also on the Dev unit, there is a port similar to a Scusi port. It has a extra circuit board on the inside, slightly different cable (internally) 128 mg ram, and the software on the hard drive. A debug is basically a normal xbox, with a pin header already installed on the LPC bus, it has 128 mg ram as well, as a blanked EEPROM. Plus the Debug has a see through green case that says debug on the front, and the Den unit has a clear case with development kit on the front. Also on the Dev unit, the lid sits higher than on the on retail, or debug xboxs to accommodate the "extra stuff". Other than that the software that runs them if basically the same, just you can use more parts of it on the Development unit, such as the Kernel debugging, emulating, and the mouse and keyboard. The Development units are more for software developing, and the Debugs are more for testing, and other things. I hope this helps answer your question.
Logged

Agent ME

  • Archived User
  • Full Member
  • *
  • Posts: 149
Problem With Dev System
« Reply #27 on: November 11, 2005, 12:24:00 PM »
As far as I can tell, debug kits are just newer versions of the dev kits. They're about the same, just one has a BIOS flasher, and DVD emulator. Which don't have too much need for.

I would burn a Recovery disk... if I had an .iso.

Anyways, here's some more info after using Avalaunch -

Version is DVT4/5, RAM 64.00 MB?! (Hopefully an error, or something to do with running from disk, or that the extra devkit stuff isn't installed to initialize it, maybe the extra 64 is "hidden" from most apps and solely for the debug stuff, I don't know. Can someone with a debug kit use Avalaunch and tell me what theirs says?)

Also I FTP'ed UnleashX to apps folder, but if I launched it it would go to MS Dash and say dirty disk. I could have sworn I fixed it in deXBE for debug...
Logged

haza55

  • Archived User
  • Newbie
  • *
  • Posts: 49
Problem With Dev System
« Reply #28 on: November 11, 2005, 06:10:00 PM »
how many ram chips u got check top and bottom of the motherboard + what is there serial numbers
Logged

haza55

  • Archived User
  • Newbie
  • *
  • Posts: 49
Problem With Dev System
« Reply #29 on: November 11, 2005, 06:12:00 PM »
I would kill for a dev or a debug kit
or 2 version 1 or 1.1 xbox mb so i can rip the ram chips of one and put them on the other
i have 2 xboxs only if i could programme in c++ i can only program in c#
Logged
Pages: 1 [2] 3 4 5
« previous next »