Print

[Boke]

QUOTE(Monty1157 @ Oct 25 2006, 03:14 PM)

I've not seen what difference the 4.xb firmware would make to loading times, though I dread to think what Dead Rising would be like with a slower read speed. I'm enjoying the game, but I'm seeing more of the little red spinning loading graphic than I am of the game so far.

Maybe you should try the slower read speed then. Read errors might be the cause of the slow load times.

Dead Rising loads fast for me at the 2.4x - 4x speed. Usually in less than 2 turns of the loading graphic. Even the larger areas load in less than 4 turns.

[Monty1157]

QUOTE(Boke @ Oct 25 2006, 04:45 PM)

Maybe you should try the slower read speed then. Read errors might be the cause of the slow load times.

Dead Rising loads fast for me at the 2.4x - 4x speed. Usually in less than 2 turns of the loading graphic. Even the larger areas load in less than 4 turns.

It's not the speed of the loads that gets me. It's the amount. It was getting to the point last night that I was terrified to press a button in case it loaded. Again. (IMG:style_emoticons/default/biggrin.gif) I don't think there's a problem reading the discs. I've never had a skip, burp, stutter, or noisy load on any of the backups, and comparing them to the originals, they're running like for like. If there's a slowdown on loading something, then it's too small a difference for me to notice.

There's no problems on loading the first backup. Works flawlessly, as it does throughout the entire length of play, even after, say four or six hours. It's only on subsequent loads of other backups, even the backup I'd just used, that it has trouble finding the disc, and hits the Tray Open error. Putting in an original, and booting from that, to put it into the slower read mode (according to the 4.x release notes for the a version of the firmware release), doesn't help with the Open Tray error. Same thing happens. The only thing, barring the rubber band mod, to solve this issue is to let the console cool down for five minutes by turning it off. Not a biggie to me anyway. Allows me to go make a cuppa.

Come to think of it, I wonder if there's a way to use the overheated 360 to boil the water for the cuppa, thus transferring the heat to the water and cooling the console quicker? Hmmm....Kettlemod. Have to look into that. (IMG:style_emoticons/default/wink.gif)

QUOTE(mr-smith @ Oct 25 2006, 04:45 PM)

Don't tell me "dead rising" load times are worse than that of "PGR3"?? surely not??

I'm fed up waiting for pgr3 to load by the time the race starts!

Don't have PGR3. Race games aren't my thing. Sorry. (IMG:style_emoticons/default/sad.gif)

The best way I can explain it is the thought that I had when trying to play Dead Rising for the first time. Oh no, not another Final Fantasy VIII (Or was it IX? The last one on the PSX anyway). All I remember from that game was the horrendous load times between locations. Really annoying if you had to run from one location to another trying to figure out what to do next. After going through five locations you felt like crying it was that soul destroying. Sorry if peeps picked up what I meant incorrectly. (IMG:style_emoticons/default/smile.gif)

[0x13h]

This one of the best updates in the last months... (IMG:style_emoticons/default/wink.gif)

Very good work C43, you are the man!  (IMG:style_emoticons/default/torch.gif)

[fyr3wyr3]

its weird .. i lost my orig.bin but i still had my x40a.bin that had my key in it.  i renamed it to orig.bin and used make x42a.bin and took that x42a.bin and flashed my 360 that was at x4.0a  and it worked!! (knock on wood)  i didnt think it would cuz i thought u had to use ur actual orig.bin to make x42a.bin but evidently not.  hope it doesnt crap out on me later. any ideas tho to why it did?

[pablizzo]

Not that i know, purely my guess.

"Make xx.bin" looks for orig.bin, the looks for the key in the location it should be (regardless of hacked or stock FW) then patches it over to the new xx.bin. Since it only needs the key, it doesnt matter if the fw is hacked or not as long as it can read it, copy it over, and patch the other fw.

Sound correct in my head, but someone please put me in check if im wrong (IMG:style_emoticons/default/pop.gif)

[Monty1157]

You are correct! (IMG:style_emoticons/default/biggrin.gif)

[langnao]

QUOTE(pablizzo @ Oct 26 2006, 07:49 AM)

Not that i know, purely my guess.

"Make xx.bin" looks for orig.bin, the looks for the key in the location it should be (regardless of hacked or stock FW) then patches it over to the new xx.bin. Since it only needs the key, it doesnt matter if the fw is hacked or not as long as it can read it, copy it over, and patch the other fw.

Sound correct in my head, but someone please put me in check if im wrong (IMG:style_emoticons/default/pop.gif)

You are correct. It doesn't matter whatever it is original firmware or previous version of xtreme, what is does is just extracting the key and put it into the new firmware. Thus as long as the key is valid, it will work ...

[iPwn]

this is great! with the 4.0 series before 4.2, i had problems reading some certain backups, getting a dirty disk error, like PGR3, and DW5 EMPIRES, but this fixed it!!!?!?! i dont know why, but everything is just as good as 3.3 now for me!  (IMG:style_emoticons/default/smile.gif)

[Puma81]

Like someone said before. For SOME its not a heat issue for and for others it is the laser for getting the open tray. I myself have tested that my issue IS in deed 100% Heat releated. If I was to let my 360 heat up with the disk tray ejected with the backup still in the tray for a couple hours and go to play it I would get an open tray error. I would have to let that disk then chill inside the pre heated 360 for a while to get it to boot. The other way if I got impatient and didnt want to wait I ran the disk under hot a** water, whiped the water off and quickly popped it in the tray. Low and behold it booted. I've also tested with fans inside the case point at the Disk drive and this worked as well.

[ntloser]

QUOTE(Puma81 @ Oct 27 2006, 08:55 AM)

Like someone said before. For SOME its not a heat issue for and for others it is the laser for getting the open tray. I myself have tested that my issue IS in deed 100% Heat releated. If I was to let my 360 heat up with the disk tray ejected with the backup still in the tray for a couple hours and go to play it I would get an open tray error. I would have to let that disk then chill inside the pre heated 360 for a while to get it to boot. The other way if I got impatient and didnt want to wait I ran the disk under hot a** water, whiped the water off and quickly popped it in the tray. Low and behold it booted. I've also tested with fans inside the case point at the Disk drive and this worked as well.

Puma,

It is heat sensitive for some. For others it doesn't matter how cool they keep their box. However, the underlying issue is still the same.The laser has a harder time with the DL +R media and will try to read from the center of the disk.

 My first 360 had the open tray issue. If I removed the guts from the case and put large house fans on it, I would NOT get the open tray error. (I only tested this over a 3 day period.) The elastic fixed this and i was able to put my 360 back to gether and not worry about the open tray.

For others, the laser will try to read from center even if the drive is removed from the 360 and kept cool.

I was skeptical at first too but the results speak for themselves.

[Smooth Criminal]

mine is using 4.1a and about open tray problem I´ve notice this:

When I place the 360 verticaly, it has more probability to do not open the tray... need to be pressed a little to open...

when I place the 360 horizontally, it less probability to do not open the tray...


but in both cases it happened th open tray bug!!

[dslknight]

I don't know if anybody else has this issue, but if I power on my xbox and try to read an original disk it tries to read it but goes nowhere.  Then I try putting in a backup disk and it reads it right away and starts playing the game.  Once a backup disc is played, then for some reason the original discs can be read with no problems.  I tried flashing back to 4.1 and the original game disk read problems went away and I could read original discs from a cold start.  Flashing back to 4.2 I can't read original discs from a cold start. I have to put a backup disc in first which will then allow me to play originals.  Does this happen to any of you?  It's not that big a deal but I hate having to swap discs if I want to play an original.

[sga_MODZ]

Is there a guide on how to install/configure this?

[I'dkickurass@cod2]

A 4.2C firmware that reads everything fast always would be great, even 12X speed for original games. Just think how halo 2 would be like with faster rendering at 12X speed and there wouldn't be anymore slow load times with originals too. But it doesn't matter, the firmware is basicly perfect the way it is right now. I would really like those features, but if I don't see those features down the road then thats ok too.  Either way, I really appreciate what C4E has done for the hacking community. Where would we be with him.

[Oddish]

In the guide that comes with this release, there's nothing about how to put this drive in modeb or getting it to show up in Windows. I've only flashed Hitachi-LG drives before so I'd really like it if someone could point me in the direction of a _complete_ guide to flashing a Toshiba-Samsung (ms25). What do I have to do to get it in modeb and get it detected in Windows?