Print

[juan23]

yes it was with that, i am now trying everything i can to go back to the 4977 bios, however when i reformated my hdd i was getting 155 gig on the f drive, however when i do reboot xbox hangs and gives me error code(13) dash failure..crazy.  no now if trying a few diff things to go back to normal

[juan23]

i have tried everything to get that large hdd to bios to boot up, for some reason it will not boot on my box, maybe im doing something wrong when i make the bios, but splash screen and color come up, but no x2 shows up.  i even went back to the 4977 bios 1 meg size on an x2.2 lite +(test subject by the way)  and still no go

i load up xbtool, select the bios i want, make a 1meg file, then save to the name i create, then reflash chip, i am going to try an zero out the drive next and start completely fresh

[juan23]

im using hdd prepare, it reeds the extra large hdd till i have to reboot then it doesnt work any longer


is slayers the only one thats works correctly??

[qadmin]

2 questions:

Are there size limitations for this type of addressing?
What is the maximum size of a drive that could be used?

Thanks again to Paul and all!!

[qadmin]

Thanks Paul, for your quick response and continuing lessons!!

Keep up the great works!!!

-Q

[oz_paulb]

I was just taking a look at the EvoX (dashboard) code (to see if I could get it to handle a drive "G:" (partition7)).

I noticed that when they check to see if a drive exists, they do a raw sector read of the *hard coded* beginning sector of that partition, to see if there is a "FATX" at the beginning (to see if there is a valid filesystem there).

What this means is: it'll be difficult to move 'standard' partitions (C/E/X/Y/Z) to other areas of the drive (like above 137GB), because EvoX will be looking at the 'standard' location for those drives.  Also, moving the start of the F partition to anything higher/different could cause problems (EvoX may not find it).

I think this is just the initial check to see if it should bother 'mounting' the drive.  After that, it passes the partition #/drive letter to IoCreateSymbolicLink() (letting the kernel take care of everything else).

This also could mean that EvoX will have problems formatting drives that aren't at their 'standard' locations.  My experience says that this isn't the case - I formatted an F: drive that started above 137GB, and it didn't corrupt my 'old' F: drive.

So, just be careful when doing things with EvoX right now (formatting partitions/etc).

If I make progress, I may be releasing a patch to EvoX (since the developers don't seem to be supporting it any more).

- Paulb

[juan23]

my steps for faluire

i flash chip with ozx using the 4977 bios
boot up auto slayers v2.1 format lg hdd

shows 155 gig on f drive.

then load on evox, reboot, then wlla

no more files, all drives show zero again, x2 doesnt show up on boot up

any idea what is happening

[juan23]

by the way the error code i get after rebooting if i let it go long enough is (13) no dash can be launched

[oz_paulb]

QUOTE (oz_paulb @ Sep 3 2003, 04:21 AM)

QUOTE (juan23 @ Sep 3 2003, 04:08 AM) my steps for faluire i flash chip with ozx using the 4977 bios boot up auto slayers v2.1 format lg hdd shows 155 gig on f drive. then load on evox, reboot, then wlla no more files, all drives show zero again, x2 doesnt show up on boot up any idea what is happening I assume you're using a CD/DVD with Slayer's installer? After you format, what if you re-boot and leave the CD in the drive?  Does it still show 155GB free? Have you tried a different BIOS (I've done pretty thorough testing on EvoX D.6)? I don't remember if you mentioned it before: what is your hard drive manufacturer/model/etc? - Paulb

Another couple of things to try:

1. Use non-LBA48 bios, follow the same steps.  You won't have 155GB free on F:, but see if things work after rebooting

2. Use LBA48 bios, but tell it the option that says "partition6 uses up to 137gb / no partition7", and follow the same steps.  This should be identical to a non-LBA48 bios.

- Paulb

[juan23]

okay when i reboot leaving slayers in the dvd drive, it all goes back to zeros

i am using a maxtor 160 gig dimond max ultraplus 9 8meg cache 7200 rpm

havnt tried any evox d.6 bios, been using 4978.03, and 4977 bios, seems to be flashed fine, just not taking the large hdd patch, works fine on regular hdd

I have a 200 gig WD special edition i could try this on another day.

but maxtor is what i would prefer

[juan23]

should i maybe zero out this drive, and start from like a retail drive?

[KiLaHuRtZ]

I have to agree that EvoX is going down the shitter.  I currently use it, but I am thinking of switching to the XBMP as my main dashboard.  My question is since you have to map the drives in the config.xml file, could I just map drive "G"

<map>G:,Harddisk0Partition7</map>

and have it work?
Thanks Paul.

[goan_trance]

Hi Paul. Quick question re: using Xbtools.

I'm having a little trouble with it right now.

I loaded (clicked on "open") my *.bin file into xbtool, checked off the lba048 option, and chose "use rest of HD for partition 6".

I then clicked on "save as", and saved the file. When I tried opening the "revised" bios file in xbtools, at the top of the screen it said "unknown kernel" as opposed "bios 4976.02", and the lba048 options I had selected did not show up (the option was unmarked and that part of the window was greyed out).

What am I doing wrong?

I disregarded this, and tried to flash my chip with the "new" bios.bin file, and was unsuccessful...it gave me the following error:
"unflashable....bios error".

Kindly let me know how to rectify.

Thanks in advance for getting back to people quickly re: their questions.

Goan.

[oz_paulb]

QUOTE (KiLaHuRtZ @ Sep 3 2003, 05:25 AM)

I have to agree that EvoX is going down the shitter.  I currently use it, but I am thinking of switching to the XBMP as my main dashboard.  My question is since you have to map the drives in the config.xml file, could I just map drive "G" <map>G:,Harddisk0Partition7</map> and have it work? Thanks Paul.

I've never really messed with XBMP, so I don't know the answer to that.

If there's a place with "F:" and "partition6" in a .ini script somewhere, you should be able to create another one with "G:" and "partition7".

- Paulb

[oz_paulb]

QUOTE (goan_trance @ Sep 3 2003, 05:28 AM)

Hi Paul. Quick question re: using Xbtools. I'm having a little trouble with it right now. I loaded (clicked on "open") my *.bin file into xbtool, checked off the lba048 option, and chose "use rest of HD for partition 6". I then clicked on "save as", and saved the file. When I tried opening the "revised" bios file in xbtools, at the top of the screen it said "unknown kernel" as opposed "bios 4976.02", and the lba048 options I had selected did not show up (the option was unmarked and that part of the window was greyed out). What am I doing wrong? I disregarded this, and tried to flash my chip with the "new" bios.bin file, and was unsuccessful...it gave me the following error: "unflashable....bios error". Kindly let me know how to rectify. Thanks in advance for getting back to people quickly re: their questions. Goan.

To tell you the truth, I'm not an expert on Xbtool.  I've only used it recently, and for specific uses (just to do quick testing of the LBA48 patches).

I'd suggest you email the Xbtool author (xbtool at alltel.net).  He's also been checking into these forums, so he may be able to answer here.

- Paulb