|
mvickers03
|
 |
« Reply #560 on: May 23, 2006, 05:06:57 PM » |
|
I burned a few with booktype dvd-dl all of them ar coasters
If you are buying a burner i would recommend a pioneer 110d that, allready has booktype enabled for dl disks
Also i use a neat little program from lite-on to tell me what the booktype of a disk is search for it on google BookType135.zip
i know opther programs do it aswell but this one is amazingly simple
|
|
|
|
« Last Edit: May 23, 2006, 05:11:41 PM by mvickers03 »
|
Logged
|
|
|
|
|
Orion Pax
|
|
« Reply #561 on: May 23, 2006, 05:20:15 PM » |
|
|
|
|
|
|
Logged
|
|
|
|
|
Orion Pax
|
|
« Reply #562 on: May 23, 2006, 06:26:30 PM » |
|
It sure as hell did burn as dvd-rom. Sweet. Oh and the forum wouldnt let me edit my last post.  |
|
|
|
|
Logged
|
|
|
|
|
john
|
|
« Reply #563 on: May 23, 2006, 06:43:12 PM » |
|
would 6 speed burning make the game load any faster? I burn at 2.4 and ive been getting s0ome glitching during movies and some audio glitching suring intense action
|
|
|
|
|
Logged
|
|
|
|
C-S-B
Newbie
Posts: 5
|
|
« Reply #564 on: May 23, 2006, 06:55:24 PM » |
|
would 6 speed burning make the game load any faster? I burn at 2.4 and ive been getting s0ome glitching during movies and some audio glitching suring intense action
It's been said that 2.4 is the optimum speed - No slower or faster. If you have jumpy movies, it might be your media. |
|
|
|
|
Logged
|
|
|
|
|
bunghoolio
|
|
« Reply #565 on: May 23, 2006, 07:14:37 PM » |
|
Here are my findings:
Used Pioneer 110D with rpc1 1.39 firmware
Iomega DL disc made X360 TS drive very noisy on game playback.
Verbatim DL discs worked perfect!
Burn at 2.4x
|
|
|
|
|
Logged
|
|
|
|
|
Orion Pax
|
|
« Reply #566 on: May 23, 2006, 07:33:31 PM » |
|
I used NEC ND 3450B with RPC II Firmware 103c
burned at 2.4x
verbatim DL disc, cant see any noticible slow down.
|
|
|
|
|
Logged
|
|
|
|
|
bunghoolio
|
|
« Reply #567 on: May 23, 2006, 08:17:26 PM » |
|
Why is xtrm.bin patched using kdx 1.5 + f360 proper patch different to manually patching TS drive key with Hex Workshop? Here is what I found: Using Hex WS. I MANUALLY entered every digit of my TS drive key into xtrm.bin using goto command 4000-4200. Saved it as key1.bin Flashed my drive - 9/9 backups worked perfect!  Using PPFomatic3 I patched xtrm.bin with xtremeproper.ppf (f360) Used KDX1_5 to xtract my key from orig.bin. Then opened the patched xtrm.bin and pasted the key into KDX. Saved it as kdxkey.bin Ran a file compare in Hex WS and found that kdxkey.bin is slightly different to key1.bin. Key1.bin works perfect. I didn't tyr kdxkey.bin. Here is the section that is different: working key1.bin $4008 FFFFFFFFFFFFFFFFFFFFFFFFFF02EEEEEEEEBBBBBBFFFFFFFFFFFFFFFFFFFFFFFFFF0311111111FFFFFFFFFFFFFFFFFF kdxkey.bin $4008 FFFFFFFFFFFFFFFFFFFFFFFFFF02EEEEEEEED6B1E92D62E1A58BA1F43C34372473B4FFFFFFFFFFFFFFFFFFFFFFFFFFFF This is from $4008-$4020 Can anyone tell me what is going on. I would like to use KDX1.5 because it takes alot less time to patch TS drive key. But am sceptical it will work properly because there are differences between the two files I have edited. |
|
|
|
« Last Edit: May 23, 2006, 08:19:38 PM by bunghoolio »
|
Logged
|
|
|
|
|
Orion Pax
|
|
« Reply #568 on: May 23, 2006, 08:56:33 PM » |
|
If you have allready made the patched firmware then your fine. what is the problem? You said it worked 100% with key1.bin. Use it. I just manually copied from 4000 HEX to 4200 HEX. Copy and paste......make sure not to insert. I noticed a difference too. My key (according to KDX) started at 401A. and ended at 4029. Now if I used KDX there is some info from 4000 to 401A being left out of my original firmware. I was sceptical about leaving this info out. The xtreme.bin has it FF'd out in that area, so its missing it. I went ahead and manually copied from 4000-4200 (HEX.....if you use the goto command in hex workshop, make sure to change the offset type to HEX, there is a difference) and pasted it in the same position and it works fine.....but I have only done 1 backup so far. I am gonna try more on the weekend when kids are gone. Dont want to take up their pc and the 360 from them.
|
|
|
|
|
Logged
|
|
|
|
infringer
Newbie
Posts: 5
|
|
« Reply #569 on: May 23, 2006, 09:46:52 PM » |
|
hrmmm interesting seems to me the only thing holding people back from using other drives would be a flash utility that works or means of flashing and or a key data header of some sort to search for using a hex utility....
Hopefully that gets ironed out for the other users...
along with botched responses patched into the firmware of the drive.
sounds like headway has been made with the 360 no doubt good thing to see.
|
|
|
|
|
Logged
|
|
|
|
|
dpacro
|
|
« Reply #570 on: May 23, 2006, 10:32:00 PM » |
|
Hi , thx for the work.
first...ill give some infos about what i tried if you dont already know about a PCI sata Promise TX4 ... It doesnt detect the Samsung drive at all... so Dont waste your money and time trying with it.
Secondo... i used a Asus KBN-E motherboard with unboard sata controler from nforce3 ... Works very good #1.
troisiement ... my friend burned different games and they all boot perfectly even if some have the bit setted at DVD+R DL and DVD-ROM.... It doesnt seem to do any diffrence here... (memorex dvd+R DL used)
Voila...
|
|
|
|
|
Logged
|
|
|
|
|
Orion Pax
|
|
« Reply #571 on: May 24, 2006, 05:22:06 AM » |
|
I think your friends drive automatically sets dvd+r DL to dvd-rom. My kids dvd burner is automatically set to dvd-rom and you cant change it back. WHich is fine either way. at least I know ALL burns will work either way.
As far as SATA....i have no idea what chipset their pc has but it is onboard sata.
One thing to make sure....bios. My kids pc in the bios you have the option to TURN OFF the other SATA ports. In fact sata 1-3 (listed as 0 - 1 - 2 - 3) were off by default since only one drive was hooked up to it. I have to turn on SATA #1 for it to work. There was no automatic setting.
|
|
|
|
|
Logged
|
|
|
|
|
isoheppi
|
|
« Reply #572 on: May 24, 2006, 02:46:26 PM » |
|
Why is xtrm.bin patched using kdx 1.5 + f360 proper patch different to manually patching TS drive key with Hex Workshop? Here is what I found: Using Hex WS. I MANUALLY entered every digit of my TS drive key into xtrm.bin using goto command 4000-4200. Saved it as key1.bin Flashed my drive - 9/9 backups worked perfect! Using PPFomatic3 I patched xtrm.bin with xtremeproper.ppf (f360) Used KDX1_5 to xtract my key from orig.bin. Then opened the patched xtrm.bin and pasted the key into KDX. Saved it as kdxkey.bin Ran a file compare in Hex WS and found that kdxkey.bin is slightly different to key1.bin. Key1.bin works perfect. I didn't tyr kdxkey.bin. Here is the section that is different: working key1.bin $4008 FFFFFFFFFFFFFFFFFFFFFFFFFF02EEEEEEEEBBBBBBFFFFFFFFFFFFFFFFFFFFFFFFFF0311111111FFFFFFFFFFFFFFFFFF kdxkey.bin $4008 FFFFFFFFFFFFFFFFFFFFFFFFFF02EEEEEEEED6B1E92D62E1A58BA1F43C34372473B4FFFFFFFFFFFFFFFFFFFFFFFFFFFF This is from $4008-$4020 Can anyone tell me what is going on. I would like to use KDX1.5 because it takes alot less time to patch TS drive key. But am sceptical it will work properly because there are differences between the two files I have edited. bunghoolio, you propably read my posts about the same thinggie. well now itīs confirmed c-s-b was right in his reply I patched my firmware using the kdx patcher. originals and movies work fine. but i canīt get the backups work. I noticed when i opened the xtreme_proper firmware that between 4000 and 4200 is nothing but the key, and in my backup.bin (orig) there is much more. and in my kdx patched xtreme_proper.bin there is only the key. now if i would do the patching manually and copy all from 4000-4200 there would be much more info on the new patched xtreme_proper.bin .... so could this be my problem ? should i do a reflash with manually copied data to the xtreme_proper.bin  If originals are working, your key is in the correct location. The data surrounding it is dummy data, and unrequired. The problem you have is with your backup. i just did a reflash with manually edited firmware.......aaand well, my coasters are still coasters and the one working still worked. HAS ANYONE NOTICED HOW THE DRIVE KEEPS AWFULL NOISE PLAYING ORIGINALS but when i play my backups i have found out that the drive doesnīt make almoust no noise. wonder if that is due the DVD-ROM media flash....that would make sense. any commentīs on this ? |
|
|
|
|
Logged
|
|
|
|
|
letsmod
|
|
« Reply #573 on: May 24, 2006, 06:35:55 PM » |
|
I have not seen this so be gentle. Does DVD-R DL not work??
|
|
|
|
|
Logged
|
|
|
|
|
Orion Pax
|
|
« Reply #574 on: May 24, 2006, 07:33:42 PM » |
|
I have no idea....all mine are dvd+r dl....the ones I just ordered are just the same....
|
|
|
|
|
Logged
|
|
|
|
|
PS2MXBOX
|
|
« Reply #575 on: May 24, 2006, 07:41:26 PM » |
|
I have not seen this so be gentle. Does DVD-R DL not work??
I was curious about this too... I should look at the differences between DL +r and -r a little closer. But if someone would be willing to spend the $2 and test that would be appreciated as Ritek makes some nice injet printable -r DL discs. |
|
|
|
|
Logged
|
|
|
|
|
garyopa
|
|
« Reply #576 on: May 24, 2006, 07:47:17 PM » |
|
I tried the DVD-R dual-layer (not PLUS, the MINUS) by Ritek and they don't work.
Looking into the reasons, it looks like there is no BookType setting for DVD-R dual-layer,
and the Xtreme firmware looks at the media type to know if it is a Original or "backup",
and it looks like it only likes DVD-ROM (DVD+R dual), so the DVD-R (minus) dual will
not be pickup by the firmware as a backup.
|
|
|
|
|
Logged
|
|
|
|
|
PS2MXBOX
|
|
« Reply #577 on: May 24, 2006, 07:53:49 PM » |
|
I know this is getting a little off topic but I feel it's beneficial either way. Apparently some burners may not let you change the booktype for -r dl Well after reading some of the posts here, http://club.cdfreaks.com/showthread.php?t=137282 it seems you can't change the booktype for DVD-R DL to DVD-ROM so there goes $50 |
|
|
|
« Last Edit: May 24, 2006, 07:59:25 PM by PS2MXBOX »
|
Logged
|
|
|
|
|
bunghoolio
|
|
« Reply #578 on: May 24, 2006, 08:08:27 PM » |
|
Confirmed that xtrm.bin patched with xtrmproper.ppf and key written in with KDX1.5 WORKS PERFECT despite the differences I mentioned earlier. No need to manually enter TS drive key. Use patched xtrm.bin + xtrmproper.ppf + KDX 1.5. All good! |
|
|
|
|
Logged
|
|
|
|
|
latency
|
|
« Reply #579 on: May 24, 2006, 08:30:05 PM » |
|
Hi all. I grabed my dvd key and created modified bin. I flashed with both modified and xtrm0800 all banks updated and completed. When I boot into XP my boot screen freezes for a while and than loads. My SATA controller "can not start" according to Device Manager. I have an ABIT KV7 MB, VIA8237. What gives? Any ideas. I have read a few people on here say the same thing, but don't see any info on how they fixed it..if they did.
I have to have the SATA RAID BIOS enabled in order to get my OS to work on the SATA drives (one XP, one MCE). I also have XP on an IDE drive so I have played around with Enabling and Disabling SATA RAID BIOS and still have same results booting.
I also see where you need to set it to NAIVE/IDE or something to that affect. Where do you do this. It is not an option in bios nor in the OS.
Any suggestions?
|
|
|
|
« Last Edit: May 24, 2006, 08:34:07 PM by latency »
|
Logged
|
Gretchen Michelle
|
|
|
|
