Post by: rmenhal on June 20, 2004, 10:36:00 AM
Summary of nkpatcher 8.1 features:
* Works with retail kernels 3944 - 5838
* Run unsigned code
* Partition 6 / F drive (up to 137 GB)
* Eject trick/fix with options:
- no reset on eject for hard drive loaded XBEs, with options:
* reset on eject CD/DVD loaded XBEs based on a flag in the XBE header
* always reset on eject CD/DVD loaded XBEs
- never reset on eject for either of hard drive or CD/DVD loaded XBEs
* In-Game Reset, with options:
- Boot to dashboard instead of the usual DVD-first-then-dashboard -sequence
- Full reboot mode resets to the X logo screen, works better with
e.g. Soul Calibur 2, but getting back to dashboard takes longer
- Selectable master port, only allow IGR from the game pad attached to the
user configured port number
* Xbox Live blocking, prevents Live aware games from connecting to the Live
service which would result in a ban
* Automatic or user selectable game region set
* Virtual C drive, use a 500 MB file, for example e:\shadowc\shadowc.img, as
a C drive instead of the real C drive
* Virtual CD/DVD drive, play games directly from ISO images on the hard drive.
Summary of those features mentioned in http://www.xbox-scene.com/bios_retail.html
* originals
* original imports
* unsigned code
* debug xbe
* backups
* disable Xlive, optional
* macrovision off
* no-patch hack
* no-patch hack2
* eject trick, optional
* eject fix, optional
* HDD swap
* F/E boot v1, optional
* change bootfile v1, optional
* IGR to dash b, optional
* IGR to game, optional
* disable IGR, optional
* Xbox v1.0 - v1.6b
Below is the original post (at the time of nkpatcher 4):
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Replacing the running kernel on Xboxes with kernel 5530 or higher doesn't work through the regular Phoenix BIOS Loader (PBL) and Bootable From Media (BFM) BIOS images - a fact of which owners of such boxes are painfully aware. Nkpatcher is proposed as a simple and temporary solution to the problem. The feature set is very limited and inferior to BIOSes such as Xecuter X2.
Currently nkpatcher has the following features:
* Runs unsigned code - no more signing everything with xbedump
* Support for F drive (hard disk size limited to about 137 GB = 2^37 bytes)
* Eject fix
The code section below contains the source code and a habibi-signed XBE for nkpatcher. Running this XBE patches the kernel in memory to make the aforementioned features come to life. After that nkpatcher executes C:\evoxdash.xbe which is the executable of your favorite dashboard. Where users of pre-5530 Xboxes would run PBL, nkpatcher can be used instead.
Although nkpatcher can be used with any dashboard/game-save exploit (remember to font-sign nkpatcher.xbe if you still use some of the old font exploits!), it is best used in conjunction with the Ultimate Dashboard Exploit (UDE). You should get the latest fonts and preferably use the specific font for 5530 (bert_ate_ernie-5530-01.xtf). Install UDE following the instructions in the UDE thread and then copy nkpatcher.xbe from the tarball below to E:\default.xbe. Remember to place the executable of your favorite dashboard to C:\evoxdash.xbe.
Nkpatcher actually supports also kernels 5101, 5530, 5713 and 5838. The code is based on the kernel 4034 patches used in Complex !Loader. Kernel 5713+ users won't be able to use any dashboard exploit such as UDE, but could use a game-save exploit if they wish.
EDIT: updated to nkpatcher4. Just a minor bug-fix (the kernel patches weren't changed and there are no new features.)
EDIT2: update to nkpatcher5. Added more patching. Now it also runs debug xbes. Games that didn't work with previous versions, may work now. The Complex !Loader patches for < 5101 kernels were scrapped and re-made similar to the >=5101 patches. Nkpatcher should now behave similarly with all kernels (3944, 4034, 4627, 4817, 5101, 5530, 5713, 5838). Nkpatcher4 (to be removed) is still included below, because I altered the patching code a lot and may have introduced silly bugs.
EDIT3: update to nkpatcher6 and removed nkpatcher4. No new features, only a minor fix to 5713 and 5838. Added a new compile-time option: by default, nkpatcher boots C:\evoxdash.xbe. If you compile nkpatcher with the command-line option -dNORMAL_BOOT_SEQ, nkpatcher boots D:\default.xbe first then the dash. Remember to sign the xbe after compiling.
EDIT4: nkpatcher7 is a rather big feature upgrade; nicer eject-trick, IGR and Live blocking.
EDIT 13/12/2004:
I proudly present nkpatcher 8.
It has these two novel features in addition to nkpatcher 7:* Virtual/shadow C drive. No hassle with fonts or trouble with dashboard updates as long as you loaded nkpatcher.
* Virtual CD/DVD drive. You can attach .iso files on the hard drive as game discs.
(I wanted to do this interesting stuff first.
Oz_paulb's LBA48 code will appear in nkpatcher 9.)Now too large to post here - see xbins!
This post has been edited by rmenhal: Dec 21 2004, 07:59 PM
Post by: mkjones on June 20, 2004, 02:01:00 PM
well done...
Post by: devz3ro on June 20, 2004, 08:56:00 PM
I also found with this the nkpatcher, Top spin starts to work, but when it starts to load the main menu, the xbox reboots (after TSOP up to 5530 + newest fonts without scraps.xtf <--- should it matter?)
.P.S. rmenhal, this does not boot DVDRs directly, (using K:5101 PBL does boot directly for some reason, possibly a jump / rest needed?) the xbox keeps rebooting with a backup inside. I guess you would need a backup to do any development on this issue
. This is not that important as you can just boot with the tray open then close once your desired Dashboard is completely loaded.Oh yes, forgot to add that this *does* work with the s-video cable, another plus over PBL 1.4.1
.-devz3ro
http://sh0x.tk/
Post by: anjilslaire on June 20, 2004, 09:06:00 PM
| QUOTE (devz3ro @ Jun 20 2004, 09:56 PM) |
| Post more about counterstrike and other games that did not work on PBL if anyone gets the chance to test it out. |
Strange. I've never had a problem running Counter-Strike with pbl. Morden's v3 worked perfectly with it. Granted, I haven't tried it with UDE, yet...
Post by: chimpanzee on June 20, 2004, 09:20:00 PM
Post by: devz3ro on June 20, 2004, 09:21:00 PM
Sorry, maybe it was another game. For some reason I recall reading that crimson skies and counterstrike did not work with PBL 1.4.1. Maybe it was another game, I'm way too tried to find out which one is correct. Please correct me if you do find out / know.
Thanks
-devz3ro
http://sh0x.tk/
This post has been edited by devz3ro: Jun 21 2004, 04:25 AM
Post by: devz3ro on June 20, 2004, 09:23:00 PM
| QUOTE (chimpanzee @ Jun 21 2004, 06:20 AM) |
| If it is launched from game hack, will the eject fix still work ? I read over the xbox-linux thread that once it is set(by the game), there is no way to revert it. |
ROE will be enabled, there is a bunch of threads explaining how and why. Our search is down, please stand by while we try and do our best to fix
.-devz3ro
http://sh0x.tk/
Post by: rmenhal on June 20, 2004, 10:26:00 PM
| QUOTE (devz3ro @ Jun 21 2004, 05:56 AM) |
| I also found with this the nkpatcher, Top spin starts to work, but when it starts to load the main menu, the xbox reboots (after TSOP up to 5530 + newest fonts without scraps.xtf <--- should it matter?) . |
Scraps.xtf doesn't matter if you use the 1974272-byte update.xbe. It doesn't matter with the 1914880-byte version either if UDE boots without it (but using it with that is advisable).
Currently nkpatcher doesn't do much more than skip the signature setting. Can you try signing your dashboard and the game and running without nkpatcher? If it works that way, then there's definately something wrong with nkpatcher.
| QUOTE |
| P.S. rmenhal, this does not boot DVDRs directly, (using K:5101 PBL does boot directly for some reason, possibly a jump / rest needed?) the xbox keeps rebooting with a backup inside. I guess you would need a backup to do any development on this issue . This is not that important as you can just boot with the tray open then close once your desired Dashboard is completely loaded. |
The kernel is patched while it's running - some clash with that, I guess.
| QUOTE |
| Oh yes, forgot to add that this *does* work with the s-video cable, another plus over PBL 1.4.1 |
Such problems could be fixed by commenting out all video output code from PBL and recompiling, though. If video code was added to nkpatcher, there might be similar problems.
Post by: devz3ro on June 20, 2004, 10:40:00 PM
| QUOTE (rmenhal @ Jun 21 2004, 07:26 AM) |
| Such problems could be fixed by commenting out all video output code from PBL and recompiling, though. If video code was added to nkpatcher, there might be similar problems. |
PBL 1.3.5i does support s-video, just the focus support isn't there (flicker until bios is loaded). Is it possible that Yoshi messed something up when adding the focus support? Or does s-video have to die in order for focus to live?
-devz3ro
http://sh0x.tk/
Post by: SeanicTheHedgehog on June 20, 2004, 10:57:00 PM
Post by: Australian Rat on June 21, 2004, 12:45:00 AM
I don't think the UDE was ever formally announced either... shouldn't that be mentioned so people using dangerous fonts know to switch?
Post by: brianforever on June 21, 2004, 01:12:00 AM
| QUOTE (devz3ro @ Jun 21 2004, 05:56 AM) |
| After reading rmenhal's post I decided to give Crimson Skies a try. Didn't work on PBL, so why not try it on this. After crossing fingers and hoping, to my suprise it actually does. Now I have not tried any missions or anything to see if it would freeze in the game or not so you guys will have to figure that out. Post more about counterstrike and other games that did not work on PBL if anyone gets the chance to test it out. I also found with this the nkpatcher, Top spin starts to work, but when it starts to load the main menu, the xbox reboots (after TSOP up to 5530 + newest fonts without scraps.xtf <--- should it matter?) .P.S. rmenhal, this does not boot DVDRs directly, (using K:5101 PBL does boot directly for some reason, possibly a jump / rest needed?) the xbox keeps rebooting with a backup inside. I guess you would need a backup to do any development on this issue . This is not that important as you can just boot with the tray open then close once your desired Dashboard is completely loaded.Oh yes, forgot to add that this *does* work with the s-video cable, another plus over PBL 1.4.1 .-devz3ro http://sh0x.tk/ |
Strange that you had probs using s-video with PBL 1.4.1 I m running 2 of my softmodded xboxes with the s-video & all my other friends have np with it too
& Also I ve Completed the 2 CSs with no problems at all & So far had never had a Problem with any Games running on PBL 1.4.1
Post by: devz3ro on June 21, 2004, 01:28:00 AM
| QUOTE (brianforever @ Jun 21 2004, 10:12 AM) |
| Strange that you had probs using s-video with PBL 1.4.1 I m running 2 of my softmodded xboxes with the s-video & all my other friends have np with it too & Also I ve Completed the 2 CSs with no problems at all & So far had never had a Problem with any Games running on PBL 1.4.1 |
Are you sure it was PBL 1.4.1 and not PBL 1.3.5i? There are lots of people on this board that have the same problem with s-video not being compatible with PBL 1.4.1 and crimson skies not working with it also.
Ex. http://forums.xbox-s...howtopic=184082
Ex. http://forums.xbox-s...howtopic=186277
Just like krayzie I did not encounter any problems without the s-video. I am using the Monster s-video btw.
-devz3ro
http://sh0x.tk/
Post by: krayzie on June 21, 2004, 08:50:00 AM
Post by: Angerwound on June 21, 2004, 08:55:00 AM
Post by: BluhDeBluh on June 21, 2004, 10:38:00 AM
Post by: krayzie on June 21, 2004, 10:51:00 AM
Post by: SeanicTheHedgehog on June 21, 2004, 01:47:00 PM
Post by: thekid1000 on June 21, 2004, 01:57:00 PM
does this mean that every dashboard and kernel is exploiable now , and can have a different bios ?
Post by: krayzie on June 21, 2004, 07:40:00 PM
No it doesn't mean every kernel and dash is exploitable now.
I'm sure you can use it with a gamesave and let it make you run unsigned code from the hd and No it will not fix the reset on eject problem.
Post by: Raebis on June 21, 2004, 09:50:00 PM
However, I do still have PBL on my system, and a link to in evox, for 7th partition support and when i need a bios loaded for whatever reason.
p.s.
I have an xbox with a focus encoder
PBL 1.4.1 does not work at all with svideo (ms advanced av pack)
PBL 1.4.1 does work beautifully with standard composite cable
pbl 1.3.5i works with svideo and composite but is garbled and makes my tv hurt
now my friend has a xbox with a conexant encoder (or whatever that company is called) and 1.4.1, 1.3.5i they all work with MonsterCable svideo and MonsterCable Component (480p mode only, he has a crappy EDTV)
hope anyone can get anything from that.
l8ah
Post by: ldots on June 22, 2004, 01:32:00 PM
Post by: SeanicTheHedgehog on June 23, 2004, 12:42:00 AM
Post by: Kanabis on June 23, 2004, 12:45:00 PM
Post by: gronne on June 23, 2004, 01:31:00 PM
Post by: afon on June 23, 2004, 09:23:00 PM
. I've got two chipped xboxs and a TSOP'ed xbox, so im no noob. I used a softmod when i didnt have the cash for a chip, and it worked great. Can I get an amen?
Post by: Kanabis on June 23, 2004, 11:49:00 PM
| QUOTE |
| How do you extract the tarball ? I copied it into notepad and changed extension but without success. winrar is telling me the archive is corrupted.Can someone post a link to the file ? |
Sounds like you didnt extract with winzip first and then extract again with winrar. Maybe re-check the instructions on the main UDE thread.
| QUOTE |
What's the biggest difference from running this on a 5530 and just running UDE normally on an earlier kernel? Is there any? |
Kernel 5530 has to use nkpatcher (at least for now). Other kernels can use either pbl or nkpatcher (or even both i believe). AFAIK thats the only thing.
Post by: Skynet on June 24, 2004, 04:45:00 AM
Post by: PedrosPad on June 24, 2004, 05:11:00 AM
| QUOTE (Skynet @ Jun 24 2004, 01:45 PM) |
| I'm still a little confused with nkpatcher and what it can/can't do. mkjones suggested that I could try it, but he said it prob wouldn't work. I posted in another thread about me having a 1.6 with K: 5838 D: 5659 will nkpatcher help me in any way? |
Short answer: no
(the longer answer is "Not yet" - so ultimately the answer is still no).
(Same goes for those with Kernel 5713)
Post by: ldots on June 24, 2004, 05:20:00 AM
) it would be worth a try. That way 5713 and 5838 owners could do a HDD upgrade (< 137Gb) and run unsigned apps and backups from a (big) HDD.
Post by: PedrosPad on June 24, 2004, 05:28:00 AM
| QUOTE (ldots @ Jun 24 2004, 02:20 PM) |
| Well he could run nkpatcher from a game save hack couldn't he? I know the patches for 5838 are untested, but assuming rmenhal got those right (something tells me he did ) it would be worth a try. That way 5713 and 5838 owners could do a HDD upgrade (< 137Gb) and run unsigned apps and backups from a (big) HDD. |
True. But I'd have thought that the largest group of users for softmods are those who don't want to open their XBOXs, such as to install a larger HDD for instance
.
Post by: ldots on June 24, 2004, 05:44:00 AM
If he just want to run some apps and emulators 5 Gb should be sufficient. The nkpatcher would still be very convienient as signature checks are disabled.
Post by: Spectracide on June 24, 2004, 06:44:00 AM
| QUOTE (ldots @ Jun 24 2004, 02:20 PM) |
| Well he could run nkpatcher from a game save hack couldn't he? I know the patches for 5838 are untested, but assuming rmenhal got those right (something tells me he did ) it would be worth a try. |
Someone do it!
Waiting is a bitch.
Post by: ldots on June 24, 2004, 06:51:00 AM
Then try the steps I briefly sketched on the previous page of this thread.
Post by: Spectracide on June 24, 2004, 07:24:00 AM
Post by: Spectracide on June 24, 2004, 07:34:00 AM
Get to the status window and type
/server irc.prison.net
And that should get you connected to EFnet.
Post by: Skynet on June 24, 2004, 07:41:00 AM
Post by: chimpanzee on June 25, 2004, 12:38:00 AM
Post by: krayzie on June 25, 2004, 08:03:00 AM
Post by: Siku on June 25, 2004, 11:25:00 AM
IGR would make it all the more sweeter
(Just a suggestion but like you said it's very limited so it's all good, It's kick ass as it is. It's done it's Job 
) Thanks Again.
Post by: krayzie on June 25, 2004, 09:58:00 PM
| QUOTE (Siku @ Jun 25 2004, 08:25 PM) |
| IGR would make it all the more sweeter (Just a suggestion but like you said it's very limited so it's all good, It's kick ass as it is. It's done it's Job ) Thanks Again. |
If you have evox as a dash you can use that IGR just fine.
Post by: denky on June 26, 2004, 04:50:00 PM
For your 4034 kernel the nkpatcher patches are from Complex Loader so it will be a good idea to test them out.
Some notes from cpx-ldr11.rar about their ROE hack:
| QUOTE |
| Issues: Disabling reset-on-eject can only be done from within a dashboard exploit, as described above. So while signing our loader to work with other exploits will work, you may not be able to disable reset-on-eject. ... .. Notices: .. ... Phoenix, thanks for patching our code into the XTF files, as you can see we're making good use of it! You might want to check our XTF to borrow our reset on eject hack too |
Post by: Flame2k on June 27, 2004, 01:55:00 AM
anyway, im having stupid problems with the code, could someone do me a really big favour and pm me the tarball?
thanks in advance
Post by: Flame2k on June 27, 2004, 04:23:00 AM
Post by: Spectracide on June 27, 2004, 07:11:00 AM
Awesome news. Just worked on my 5838.I'll get a few pics in a minute.
edit:
xbox system info
mechassault runs nkpatcher, nkpatcher runs evox on C: (installed beforehand)
running unsigned code (formally 21'd)
edit2:
it may be worth noting I used Action Replay and the AR memory card that came with it. no corruption here.
Post by: devz3ro on June 27, 2004, 07:25:00 AM
| QUOTE (Spectracide @ Jun 27 2004, 04:11 PM) |
| W00t! Awesome news. Just worked on my 5838. I'll get a few pics in a minute. |
How new is your 1.6?
EDIT:
Can you check your cache drives (x,y,z) to see if XMTAXBOX.XBE resides on any of them? This seems ideal for those with 1.6s and willing to hot swap out the hard drive for a bigger one. You would just have to load with a game like splinter cell (fastest of the 3 loading) and be on your way.
-devz3ro
http://sh0x.tk/
Post by: Spectracide on June 27, 2004, 07:37:00 AM
| QUOTE (devz3ro @ Jun 27 2004, 10:25 AM) |
| Can you check your cache drives (x,y,z) to see if XMTAXBOX.XBE resides on any of them? |
Not there. Just seeing stuff from other games.
Post by: Flame2k on June 27, 2004, 09:49:00 AM
thanx alot!great work.
nkpatcher
Post by: gronne on June 27, 2004, 01:30:00 PM
I might tell my brother he can buy a new xbox then.
/me awaits more news on this
Edit: Does it work as well as on other kernels that need NKpatcher?
Is it possible to continue the development on NKpatcher or is this as far as it can go?
Post by: brianforever on June 27, 2004, 04:41:00 PM
| QUOTE (gronne @ Jun 27 2004, 10:30 PM) |
| But I thought 5838 didn't work whatsoever yet. Does this mean it works on some and some not, or all? Suppose you can't tell because of lack of information, but this should be great news I reckon. Please explain what I've obviously have completely missed. I might tell my brother he can buy a new xbox then. /me awaits more news on this Edit: Does it work as well as on other kernels that need NKpatcher? Is it possible to continue the development on NKpatcher or is this as far as it can go? |
Lol dont u ever read his Post ?
Kernel 5713 & 5838 users won't be able to use any dashboard exploit such as UDE, but could use a game-save exploit.
So he is running his unsigned Apps & Games From his HardDDisk with Nkpatcher(e.g Xbmc from C:/ due also to ROE )
Post by: kennelbound on June 27, 2004, 07:21:00 PM
Post by: kennelbound on June 27, 2004, 07:36:00 PM
Post by: gronne on June 28, 2004, 01:41:00 AM
| QUOTE (brianforever @ Jun 28 2004, 01:41 AM) |
| Lol dont u ever read his Post ? Kernel 5713 & 5838 users won't be able to use any dashboard exploit such as UDE, but could use a game-save exploit. So he is running his unsigned Apps & Games From his HardDDisk with Nkpatcher(e.g Xbmc from C:/ due also to ROE ) |
I never meant you could use UDE either. But when you've installed NKpatcher you don't have to do the game-save hack every time, right? It should start right up like UDE does, I figure.
I know UDE and NKpatcher really is two different things, but will it be much more issues with NKpatcher? Does it lack many things UDE has?
Post by: PedrosPad on June 28, 2004, 02:43:00 AM
| QUOTE (gronne @ Jun 28 2004, 10:41 AM) |
| I know UDE and NKpatcher really is two different things, but will it be much more issues with NKpatcher? Does it lack many things UDE has? |
UDE is an exploit that allows habbi signed applications/XBEs to be executed (on Kernels < 5317).
NKPatcher is a habbi signed application that patches the kernel to remove some Kernel checks (on all known Kernels).
Therefore, you need an exploit in order to execute NKPatcher.
The only known exploit for K:5713+ is the game sav. - and, btw, ROE is already enabled by the time this executes
.Technically:
UDE changes the Kernel signature to habbi only.
NKPatcher patches the Kernel to :
* Disable the signature check entirely - no more signing everything with xbedump.
* Extend the Kernel based HDD partition table to support the F drive (hard disk size limited to about 137 GB = 2^37 bytes)
* Disable the code to set ROE, should an application try to set it. (If ROE is off, when NKPatcher executes, this patch ensures it stays off!, but, if ROE has been set, ahead of NKPatcher running, there is no way to unset it!)
Post by: Flame2k on June 28, 2004, 09:23:00 AM
im using it with ude so i wouldnt know
Post by: PedrosPad on June 28, 2004, 10:19:00 AM
| QUOTE (Flame2k @ Jun 28 2004, 06:23 PM) |
| one downside though, does it fix the reset on eject problem when using a gamesave exploit? |
Thought I'd just explained that
, but in summary...No
Post by: krayzie on June 28, 2004, 11:54:00 AM
Post by: brianforever on June 29, 2004, 12:58:00 AM
| QUOTE (krayzie @ Jun 28 2004, 08:54 PM) |
| Any of you guys think it is posible to hex the nkpatcher to run an xbe from the dvd drive instead of the evoxdash.xbe on C:? |
Yes its possible & easily done,
But Whats the Point in doing that when u need a Game Save exploit to boot it up (K:5713+)
& with ROE, Nothing would be able to run from D:/
Post by: krayzie on June 29, 2004, 06:02:00 AM
| QUOTE (brianforever @ Jun 29 2004, 09:58 AM) |
| Yes its possible & easily done, But Whats the Point in doing that when u need a Game Save exploit to boot it up (K:5713+) & with ROE, Nothing would be able to run from D:/ |
Please don't advise wether I need to do it or not as I have my own reasons on why to do it. I just want the correct path for the dvd drive's default.xbe to hex it in. I now have something like device\cdrom0;default.xbe but it isn't working.
Post by: The_Truth on June 29, 2004, 12:30:00 PM
)Edit: Wouldn't this completely prevent the ROE for gamesave exploits? no fonts needed!!!!!
Post by: PedrosPad on June 29, 2004, 12:43:00 PM
| QUOTE (The_Truth @ Jun 29 2004, 09:30 PM) |
| guys, nkpatcher could just make the easteregg exploit perfect!, run nkpatcher from easteregg exploit, (with hacked st.db if needed *im not sure*), then u run the gamesave exploit, and the only thing that's modified at all in the xbox is the easter egg executable! this would be the absolute safest way to softmod one yet,(if you dont mind alil bit of finger dancing ) Edit: Wouldn't this completely prevent the ROE for gamesave exploits? no fonts needed!!!!! |
The easter egg exploit works on the lastest Dashboard, that's true, but it doesn't work on the latest Kernels (5713 & 5838) that prevent the execution of pre-live Dashboards (and the easter egg exploit uses a pre-live Dashboard!).
If we're not talking about K:5713/5838 then there are already plenty of good exploits (the easter egg exploit can already launch PBL, etc).
Post by: E-Vix on June 29, 2004, 03:02:00 PM
| QUOTE |
xbestr db '\Device\Harddisk0\Partition2;evoxdash.xbe',0 |
Change this to whatever file you want to load. I changed mine into '\Device\Harddisk0\Partition1;apps\avalaunch\default.xbe' so it would automatically boot Avalaunch on my E drive.
Partition1 = E
Partition2 = C
Partition6 = F
Now download NASM at http://nasm.sourceforge.net. Put the three .asm files in the same directory as NASM, and from a dos box or linux shell enter the following command:
| QUOTE |
nasm -o nkpatcher.xbe nkpatcher.asm |
Ignore the errors about some spaces that have been converted and there you have it. Your own custom nkpatcher file.
You may be wondering what the benefit is over hex-editing the precompiled nkpatcher.xbe. Well, if you recompile it, you can enter much longer paths.
Post by: Spectracide on June 29, 2004, 03:21:00 PM
Post by: krayzie on June 29, 2004, 07:57:00 PM
| QUOTE (E-Vix @ Jun 30 2004, 12:02 AM) |
| Change this to whatever file you want to load. I changed mine into '\Device\Harddisk0\Partition1;apps\avalaunch\default.xbe' so it would automatically boot Avalaunch on my E drive. Partition1 = E Partition2 = C Partition6 = F |
is anyone happy to tell me how to boot an xbe of a dvd today? (I don't care if it's usefull or not). I just want the correct line to hex or edit in the asm. So far I've only come up with device\cdrom0;default.xbe but it doesn't work. I know it's just something simple but I just need to know.
*edit* nevermind got it to work allready
Post by: ldots on June 30, 2004, 03:27:00 AM
xbestr db '\Device\CdRom0;default.xbe',0
Post by: old engineer on July 01, 2004, 01:01:00 PM
Amazing that no one has made this into a mem card save package yet!!!!
TIA
Post by: E-Vix on July 01, 2004, 01:24:00 PM
| QUOTE (old engineer @ Jul 1 2004, 11:01 PM) |
| Right, keep reading all this but am still confused... I've got a K:5713 Xbox so I want to run say a 007 gamesave expliot >nkpatcher4>EvoX dash. My question is what executes nkpatcher4? Does it need renaming? I would like to install it to E: along with EvoX, I understand that I may need to hex edit nkpatcher4 to sort this, no worries. Idots gave a guide for doing this several pages back but I'm still confused as to whats going on with the file names!!!!!!! If I have a file called evoxdash.xbe in my game save, what should I call nkpatcher4.xbe? ...What executes it to work? I guess I'm missing the obvious here Amazing that no one has made this into a mem card save package yet!!!! TIA |
Normally the 007 savegame patch loads the default.xbe in the same directory as where the savegame patch is located (E:/UDATA/4541000d/000000000000/)
So the easyest way to do it is to rename nkpatcher.xbe to default.xbe and place it in the 007 savegame folder.
Now the default nkpatcher loads c:\evoxdash.xbe. If you don't want to load c:\evoxdash.xbe you either have to hex edit your nkpatcher, or follow my instructions a few posts back on how to edit and recompile the source.
Post by: old engineer on July 01, 2004, 01:32:00 PM
Post by: rmenhal on July 01, 2004, 04:14:00 PM
Post by: devz3ro on July 01, 2004, 09:15:00 PM
| QUOTE (rmenhal @ Jul 2 2004, 01:14 AM) |
| Nkpatcher5 is now available. It includes support for all kernels and does more patching, so games that didn't work with previous versions may work now. Actually I'd like to know if there are games that don't work with nkpatcher5, but work with EvoX M7. |
Amazing
It's funny how you implement all these features and the file size gets... smaller!!. I would believe the other way around. I guess it could be code cleanup etc. but anyways, excellent job. I did get a chance to try topspin (which did not work with nkpatcher4) and it now loads flawlessly
. My only complaint is the "reboot endlessly if a non-m$ signed default.xbe resides in d:". As I stated before, this really is no big deal as you can just boot with the cd tray open, but would be nice if it didn't . But then again, who is this more meant for? K:5530+ users who have to boot with the gamesave exploit? or us K:5101- users who can boot from the update.xbe?-devz3ro
http://sh0x.tk/
Post by: mkjones on July 02, 2004, 12:51:00 AM
| QUOTE (brianbtran @ Jul 2 2004, 08:18 AM) |
| i'm running kernel 5838. game save exploit is the only way. does that mean, i have to pop in the CD and click load everytime in order to boot to EVOX DASH? That sucks. what's the point of this nkpatcher then? please let me know. Thanks so much! |
So you can run apps from the HD without signing
games however will not work with the gamesave becuase of the eject problem Sorry, but im sure some day there will be an exploit for these new kernals..
Post by: Flame2k on July 02, 2004, 02:33:00 AM
| QUOTE |
| Amazing It's funny how you implement all these features and the file size gets... smaller!!. I would believe the other way around. I guess it could be code cleanup etc. but anyways, excellent job. I did get a chance to try topspin (which did not work with nkpatcher4) and it now loads flawlessly . My only complaint is the "reboot endlessly if a non-m$ signed default.xbe resides in d:". As I stated before, this really is no big deal as you can just boot with the cd tray open, but would be nice if it didn't . But then again, who is this more meant for? K:5530+ users who have to boot with the gamesave exploit? or us K:5101- users who can boot from the update.xbe? -devz3ro |
Its best for users that can downgrade the dash but cant use pbl, such as 5530, pbl doesnt work on 5530 but u can still downgrade to 4920 as im sure u know. therefore its a great pbl alternative for us lot
Post by: GJCD on July 02, 2004, 04:11:00 AM
Thank you rmenhal
Post by: Spectracide on July 02, 2004, 04:47:00 AM
| QUOTE (old engineer @ Jul 2 2004, 06:13 AM) |
| So I'm stumped, whats the trick to get this .xbe to execute?????? |
Run your MechAssault save with Evox. When you get FTP working, connect to your XBox and install Evox to your C: drive with Evox being evoxdash.xbe. That is what nkpatcher looks for.
Now take your Mechassault Save and open it on your computer. Remove default.xbe (and any other evox files if you wish) and put in nkpatcher.xbe (renamed to default.xbe). Now MechAssault with execute nkpatcher, and look for evoxdash.xbe on C: and run it.
Post by: mkjones on July 02, 2004, 05:00:00 AM
| QUOTE (brianbtran @ Jul 2 2004, 01:55 PM) |
| mkjones, one more quick question, what about running games stored on the hard drive. would that be okay? Thanks! |
I suppose so
as long as your dash is set up right..Remember however that not all games work with nkpatcher..
Post by: brianbtran on July 02, 2004, 05:05:00 AM
basically, 5838 is a useless xbox for now.
Post by: old engineer on July 02, 2004, 05:47:00 AM
| QUOTE (Spectracide @ Jul 2 2004, 01:47 PM) |
| Run your MechAssault save with Evox. When you get FTP working, connect to your XBox and install Evox to your C: drive with Evox being evoxdash.xbe. That is what nkpatcher looks for. Now take your Mechassault Save and open it on your computer. Remove default.xbe (and any other evox files if you wish) and put in nkpatcher.xbe (renamed to default.xbe). Now MechAssault with execute nkpatcher, and look for evoxdash.xbe on C: and run it. |
Tried this m8 still crunched out to error 21.
...Still, thanks for trying, anymore ideas appreciated.
Post by: pugnip on July 02, 2004, 07:17:00 AM
can anyone have any ideas?
Pugnip.
Post by: old engineer on July 02, 2004, 07:32:00 AM
Post by: krayzie on July 02, 2004, 07:35:00 AM
| QUOTE (pugnip @ Jul 2 2004, 04:17 PM) |
| I have a 5713 and running a gamesave exploit and the eject fix isn't working can anyone have any ideas? Pugnip. |
Yeah it's because the reset on eject stays present when running from a gamesave and can't be fixed. You can only play stuff of the hd.
Post by: pugnip on July 02, 2004, 07:50:00 AM
Pugnip.
Post by: krayzie on July 02, 2004, 08:14:00 AM
| QUOTE (pugnip @ Jul 2 2004, 04:50 PM) |
| Is there anyway to fix this? Pugnip. |
Can't you read?
Post by: Deciphile on July 02, 2004, 08:17:00 AM
nkpatcher5 runs on 5838.
Post by: devz3ro on July 02, 2004, 09:13:00 AM
I suggest the two of you start reading in the "GameSave Exploit" forum and learn how everything works before coming to this one. Most of us understand that ROE will *always* exist (with no fix ever) when you are using a gamesave exploit. Installing gamesave exploits with different *.xbes is not difficult at all. A quick explanation would be to go inside the gamesave folder, replace the xbe (usually in 000000000000) with the nkpatchers xbe and then place your favorite renamed to evoxdash.xbe dashboard in the root of your C drive. You may now execute unsigned xbes from your hard drive and not your dvd drive (Yes, you have to transfer whatever you want to execute via ftp to the xbox). Opening your dvd drive after you did all of the above will always cause the xbox to reboot.
-devz3ro
http://sh0x.tk/
Post by: old engineer on July 02, 2004, 09:35:00 AM
...I'm not a n00b, I know how to softmod, TSOP flash and chip. I understand UDE, I know the difference between a gamesave exploit and a dashboard exploit!!!!!!!!!!
...I muck around with this stuff all the time, I understand about Kernal versions and ROE etc, etc, etc.
The ONLY reason I asked for an explanation from someone who got this working is that I've done EVERYTHING that I consider correct but it still won't execute nkpatcher, it just goes to a error 21 screen!!!!!!!!
K = 5713
evoxdash.xbe is on C:
nkpatcher5.xbe is renamed default.xbe and resides in mech assault save folder in Udata on E:
Any clues!!!!!!!!!
Post by: Spectracide on July 02, 2004, 09:48:00 AM
Post by: Deciphile on July 02, 2004, 11:26:00 AM
I don't know if this helps since I'm running on 5838 but what I did was to:
1. Of course run the game save hack that came from easy pheonix loader . The one that defaults to MXM.
2. ftp'ed to xbox and transfered nkpatcher5 tarball contents to E:/ root
3. transfered all contents of the latest version of Evo-x (minus readmes and nfo's) folder to C:/ root
4. rebooted and ran gamesave hack again to go back to MXM dash.
5. went to dashboards folder and hit nkpatcher it then executed and put me into the evo-x dash which is where I wanted to be.
I tried hex editing the gamesave but it would frag everytime so I found this to be an alternative.
Post by: Deciphile on July 02, 2004, 11:36:00 AM
Post by: gronne on July 02, 2004, 02:17:00 PM
| QUOTE (brianbtran @ Jul 2 2004, 10:27 PM) |
| man this sucks for 5838 users. the gamesave exploit requires the original game. a backup does not even work. I rented 007 auf and have 4 more days to return. aaaaaaaahhhhhhhhhhhhhh! anyway that i can return the game and still can run the gamesave exploit hack? |
That goes for every xbox not hardware-modded out there. No matter what kernel you've got. And I reckon you can't run the gamesave-exploit without it, no.
Post by: devz3ro on July 02, 2004, 06:25:00 PM
| QUOTE (old engineer @ Jul 2 2004, 06:35 PM) |
| Yeah, thanks devz3ro, but your post don't help me m8 ...I'm not a n00b, I know how to softmod, TSOP flash and chip. I understand UDE, I know the difference between a gamesave exploit and a dashboard exploit!!!!!!!!!! ...I muck around with this stuff all the time, I understand about Kernal versions and ROE etc, etc, etc. The ONLY reason I asked for an explanation from someone who got this working is that I've done EVERYTHING that I consider correct but it still won't execute nkpatcher, it just goes to a error 21 screen!!!!!!!! K = 5713 evoxdash.xbe is on C: nkpatcher5.xbe is renamed default.xbe and resides in mech assault save folder in Udata on E: Any clues!!!!!!!!! |
My post was not directed towards just you.
Why not TSOP down to your desired bios if you know how? I started with the 5713 bios, TSOP'd down to 5530 and now have UDE working with the latest xbox live present (which I use without a switch). I can't speak for mech assault, even though I own all 3 gamesave exploit games. The latest nkpatcher *does* execute fine on 007 and splintercell (K:5713). If you say that you tried *everything* TSOP seems like your last resort, when in my eyes it should have been the first.
just my 2 cents
-devz3ro
http://sh0x.tk/
Post by: Deciphile on July 02, 2004, 07:48:00 PM
Bro go to gamestop or a place much like it and buy it used. I got MA for like 8 bucks. I've always had great luck at places like these. Never fret my friend there is always a solution when dealing with software and hardware. It definently is a must to have the original game when running gamesave hacks.
Post by: old engineer on July 04, 2004, 02:54:00 AM
Post by: rmenhal on July 04, 2004, 05:15:00 AM
| QUOTE (devz3ro @ Jul 2 2004, 06:15 AM) |
| My only complaint is the "reboot endlessly if a non-m$ signed default.xbe resides in d:". As I stated before, this really is no big deal as you can just boot with the cd tray open, but would be nice if it didn't |
I'll look into this sometime later. Does everyone have this problem, or with just some xbox/kernel combination?
| QUOTE |
| But then again, who is this more meant for? K:5530+ users who have to boot with the gamesave exploit? or us K:5101- users who can boot from the update.xbe? |
Mainly just 5530 and higher, though it should work just the same for all kernels. I think many do like X2 features such as IGR and Live login disabling (and maybe lba48), which aren't in nkpatcher, so anyone who can run PBL will probably want to.
Post by: rmenhal on July 04, 2004, 05:25:00 AM
| QUOTE (old engineer @ Jul 4 2004, 11:54 AM) |
| Well I tried Deciphile's idea of using MXM to exectute nkpatcher... ...No joy though |
What happened then?
Can you
1. sign C:\evoxdash.xbe with habibi and then execute it just fine via MXM?
2. if the above works, then leave the working C:\evoxdash.xbe there, and execute nkpatcher.xbe via the exact same way in MXM.
The only way I see nkpatcher5 itself causing an error 21, is that the kernel version doesn't match any of the supported kernels. In that case all patching is skipped and nkpatcher launches the dashboard (without patching, the dashboard is C:\xboxdash.xbe which is MS-signed.) So check that your kernel version is exactly 1.00.5713.01. It doesn't look like there are .02 or .03 kernels for any of 3944-5838 (Google).
Post by: krayzie on July 04, 2004, 06:05:00 AM
| QUOTE (rmenhal @ Jul 4 2004, 02:15 PM) |
| I'll look into this sometime later. Does everyone have this problem, or with just some xbox/kernel combination? |
I don't experience this at all. My dash loads just fine with a backup in the drive.
Post by: devz3ro on July 04, 2004, 08:42:00 AM
| QUOTE (rmenhal @ Jul 4 2004, 02:15 PM) |
| I'll look into this sometime later. Does everyone have this problem, or with just some xbox/kernel combination? |
I have the problem with K:5101 and K:5530. The way I have my box setup is to load the hexed THC dashboard (which direct boots games). This has to be what is causing the problem. My question is, why does PBL go directly to the game and this just reboot? Could be a feature in the x2 4983 bios, if I recall correctly d:\default.xbe is the first path it looks for (I think it was this when I took apart the non-encrypted 4981 bios a while ago). But anyways, thanks krayzie, something as simple as just changing the dash I honestly didn't even think of
.-devz3ro
http://sh0x.tk/
Post by: devz3ro on July 04, 2004, 10:35:00 AM
| QUOTE (rmenhal @ Jul 4 2004, 06:22 PM) |
| Yep, bioses boot d:\default.xbe first. I made nkpatcher5 boot dash, because those who wish to use it from a game save exploit wouldn't like nkpatcher booting back to the game. You can make nkpatcher boot dvd first, then dash, by commenting out the code from "launchdash:" to ".inf" and uncommenting the corresponding piece below it. Then compile and sign with habibi. |
Its cool, I have it loading evox, then evox autolaunchs the game (so no more reboots). Just had to replace that ugly looking default skin
-devz3ro
http://sh0x.tk/
Post by: PedrosPad on July 04, 2004, 11:10:00 PM
| QUOTE (Tomilius @ Jul 5 2004, 01:24 AM) |
| I guess the only thing that could be added now is IGR |
Doesn't EvolutionX already have it's own IGR? If you choose to use an inferior replacement Dashboard - hassle it's authors.
Post by: old engineer on July 05, 2004, 09:28:00 AM
Post by: Tsjibbe on July 05, 2004, 09:49:00 AM
| QUOTE (PedrosPad @ Jul 5 2004, 08:10 AM) |
| Doesn't EvolutionX already have it's own IGR? If you choose to use an inferior replacement Dashboard - hassle it's authors. |
I've been trying to get this IGR working in evolution-x. But it don't seem to work for me. Did anyone manage to get the igr working with nkpatcher in combination with evox?
Post by: krayzie on July 05, 2004, 09:51:00 AM
Post by: rmenhal on July 05, 2004, 10:08:00 AM
| QUOTE (Tsjibbe @ Jul 5 2004, 06:49 PM) |
| I've been trying to get this IGR working in evolution-x. But it don't seem to work for me. Did anyone manage to get the igr working with nkpatcher in combination with evox? |
It works. Make sure that TSR is set to normal (TSR_Type=1), IGR=Yes and the IGR-section in evox.ini has the button combination you expect.
Post by: Tsjibbe on July 05, 2004, 10:13:00 AM
Post by: Master Reefed on July 07, 2004, 08:58:00 AM
soo...uhh, whats the chance someone will compile this and put it in "the usual places"
cause I have a 5530 and am having a devil of a time, tryin to compile this code.
Post by: devz3ro on July 07, 2004, 11:10:00 AM
| QUOTE (Master Reefed @ Jul 7 2004, 05:58 PM) |
| soo...uhh, whats the chance someone will compile this and put it in "the usual places" cause I have a 5530 and am having a devil of a time, tryin to compile this code. |
no need to, if you decode the code in the first thread, the xbe is there already compiled and ready for use (yes it will work for your kernel).
-devz3ro
http://sh0x.tk/
Post by: krayzie on July 07, 2004, 11:13:00 AM
Post by: Master Reefed on July 07, 2004, 01:21:00 PM
Guess this box didnt have the extra space.
Very nice work!
Post by: devz3ro on July 08, 2004, 12:53:00 AM
) just because of the "PBL code fixes" that are now floating around. I am still using the nkpatcher and plan to for a while (love the 5kb file size & ultra fast boot).presently (just because I can):
K:5530
D:5960
originally:
K:5713
D:5659
As for a wma under / overflow, I have no understanding what-so-ever on that subject. I had a few ideas, but didn't want to look stupid by posting them if they were way off
Good luck with it though. Too bad evox released the m8, I wanted us to have the first 1.6 xbox booting and executing unsigned code without the xbox frying itself We'll get em next time'
-devz3ro
http://sh0x.tk/
Post by: Flame2k on July 08, 2004, 04:59:00 AM
| QUOTE |
| Nah, I think nkpatcher is done now. I guess the new PBL versions don't fix things for 5530+ kernels yet, but PBL can probably be fixed for them anyway. It's a tad too complex (heh) to include patching for multiple kernel versions. I guess nkpatcher is a viable option when extra features aren't desired, but when a 5530+ fixed PBL comes out I fully expect nkpatcher to be obsoleted very fast. |
Obsoleted? nar, possibly, but i know i will keep using it because i like it better than pbl.
also, it saves people from having to worry about eeprom and rc4 keys.
Post by: devz3ro on July 08, 2004, 12:36:00 PM
| QUOTE (rmenhal @ Jul 8 2004, 11:16 AM) |
| I think that's great. I wasn't planning on making or releasing a v1.6 bios. |
I didn't mean for you to release a 1.6 bios, I meant for us to find a bootstrap + nkpatcher to make it all work before m8 final was released. I should have worded it "The first *softmodded* box booting & executing unsigned code on a 1.6"
-devz3ro
http://sh0x.tk/
Post by: rmenhal on July 08, 2004, 08:20:00 PM
| QUOTE (knight_of_flowers @ Jul 9 2004, 01:22 AM) |
| any advice out there for a helpless soul??? |
Try signing both C:\evoxdash.xbe and nkpatcher.xbe with habibi, put them in place (nkpatcher wherever you want), and then try running each of them as an application from another dashboard in E:\PBL\p.x. What happens?
| QUOTE |
| By the way, I'm using the easy phoenix loader audio exploit which puts the PBL xbe as p.x in E:\PBL. Hence, I'm renaming nkpatcher.xbe to p.x also. Any issue with this? |
This should be ok.
Post by: old engineer on July 09, 2004, 12:22:00 AM
| QUOTE (rmenhal @ Jul 5 2004, 07:03 PM) |
| I doubt it. From your previous problem descriptions, it sounds like your problem is something else than nkpatcher. Did you get that habibi-signed C:\evoxdash.xbe to work properly (without nkpatcher)? |
Yep, I can run evoxdash.xbe, installed on C:, as an app from MXM once it's been -habibi signed, but I still can't run any version of nkpacher, or the FBL with the inbuilt nkpatcher.
...Still get dash error 21!!!
Strange
Post by: old engineer on July 09, 2004, 01:00:00 AM
...looks like the only think I can't get to run is nkpatcher.
Post by: rmenhal on July 09, 2004, 06:53:00 AM
| QUOTE (old engineer @ Jul 9 2004, 10:00 AM) |
| ...looks like the only think I can't get to run is nkpatcher. |
Can you try the following xbe to aid in debugging this? It'll change led color and possibly blink depending on how far code execution gets. Then it'll just go into infinite loop. How's the led?
It also writes your kernel version number into file E:\kversion.bin. Can you open it into a (hex) editor and paste the contents here?
| CODE |
| begin-base64 644 p.zip UEsDBBQAAAAIAGe26TDOrYVMuwUAAEgWAAAFABUAcC54YmVVVAkAAzL37kAy 9+5AVXgEAOgD6APtl39MU1cUx29bBBy6oliUyAYqTpyTUaWEqCA6KnXoLGPQ MvBXpa48f0Op3djIY8DMA5yYbVlQzCCoU7tFRMMeJRS0RtmcTuPCYJLhxM1i mfya+Iv27ZwWEjHof4vZ0tOce7+999zPPb3nJs1VLpXKkif/MUUfHfBZUtyK wNKjxxcsLR68/fHk4CV8WfKW1wOamv3CPFukEu+OQ/c65hlNrPzrN2Y+8G8N r7m7cl/A/MVzrT4qZamq+mxwW7FPc3j/rIn92XuKc75d+vsSr9YPE5fvla25 bAl7qbQsbqdPxsD+/fmB+dJz2e/NWcfuCFm3qG/vjO0Ly9PZqmtBG3M0ncJf y2fE0vs9uqbtSB6s+SDheMu9H3vvhidxN8eVHxA2y5gF+/TmzRu3X3yhb3Xb EeOlU5FNt6S/eWUZEupDs6VnJCvGTbCH+tULwr+ov3NukPUvPN0r3mmImXDx y6hK3ZypxX3i0sWVP/j59TCJuqOzPMuqKt3S1hHCI8SbEJkvIXqQl676Ltbz eDhK3hE4e0Os7UioL6rRDdcUQyx6GbhJvjnlqcFgbUP7PCvmeRlHCO0BzoE9 71z+i+aBjTePyNyJ815Bf0rgvDvfQF8FHtTezn8U9Upv0DLS6mtrVQzkrbrx JEdPVCSNqInuifEQrVqv/dd/hctc5jKXucxlLnOZy1zmsv+bdX4FTUlJiRje e/PAD4IfAjeAV4PngleAx/AIvQHcBLoLvA78Kjg8WmjkpMaodekb1Kmy9Rlp aemZm0JT5esztOna9G1b56Wqddv0aeszNSF6lfpZkeLUTTp1RiaoEFX6VjIb PhnwjiqSBENbMJAVUBQ5DpSmHDakCOVJBXK/UDxQHqisdjnTIZczf1LRmjII owhzi1JRAkqgoR0LkhQaeI9FJ3CiUJjO64pgrlPTqQh5EjefEy2Cod0xQcHU i5SncyQag85GiL+vwO3jcTg+Ph5nwuA79hGOiClDWfWMmtXgcPbC/PsQkBfF ExZ0g9iYl+MO8ibIofXcqOs5USBMyh8KAxvlMznOzgmnNwoDW4TTW4Rjhd8t c9OsnMgjkRohIcL8ED4hkWcccgtKn4koT6K84pAPUP7lgzJCAHKfCOVOlPG+ KGtQXnJIA0ilEnZ7lMyJgrAMzjSPPeXwzdbxlvdhbji5x5dahyu3YfTFxGov knhDQAO+l4teLriWJVRwokl4cI1af8bMuFM8BRTOH0aYdnFjLXEjpN+Q58VR fE7kiVvYK15zhk84j5XjkfM0dKR+atxBc+VKH1g3XgOtaRDOi9qR3H/QXEvw cit5sKopa5KkJnpLSq4kGL4aFINHOuEYieTt3hPdzrG4AwWfV2JskWQKtLmf lsE8x3E0k2Up+gRvZMF4tlpAa/nTmhhpT25UC2yu86APY2/X5PbyaXNlISSw O3Zw9mWGb8oHTXlhHqYFhDRqqgYwos2RaDO2ooeY7gVoFFQYxClMMrzVr4Lc I9hlq9IcUxqqzMfYkhKr3cB0m/MeuWu92DBk1cUCqyLilICeW1V4h+g6jQQq f+8GI73OJN5kcUwjxpiEJEVig4ovoFmtSUDXjhUIaMtPdo47P+YjG5/uP7TW 2kDZ+XT9nmQ+XZvyLp82XgHF3m8Q0HVlbhAcB0eweu2aFAfp3JgYyLbLCQyD mNpFCMwZBXgcgdkI7EUg2wjAKwh8aB8FWN0NMcoTADzcw6ctcx3Ai7eHgEYr AFctA+BU+E3GvaDYFihF3cI+CD76OLBheQ/uhqQlUBFLhw1Jq61DpDe7gNSO JAOSpkHDRpwEUjOS1o4gMQ4SbFOLtbWUOkgHhkmFSOpGEtbCKHaQoB51vv0Q LBpBSvobJ08D6a27MLnKQdrcPURSwD71dTIg7VoOJBso9vIZIHXAhbFcsD1O kiNJiSQtksaMIBl/hjEWr5klEyZGBfcg2IYhGcPgkhH2tP+RfwBQSwECFwMU AAAACABntukwzq2FTLsFAABIFgAABQANAAAAAAAAAAAApIEAAAAAcC54YmVV VAUAAzL37kBVeAAAUEsFBgAAAAABAAEAQAAAAPMFAAAAAA== ==== |
Post by: old engineer on July 09, 2004, 08:40:00 AM
LED went to a solid orange colour, screen stayed at 'loading', then locked up.
The following is kversion.bin that was generated:
....Q...
(0100 0000 5116 0100)
Hope this helps
Post by: mkjones on July 10, 2004, 06:29:00 AM
Post by: smegmahead on July 11, 2004, 01:56:00 PM
For myself I've put my knkpatcher6 directly too my game save hack of splintercell to load my xbox media center so i can run things from the network as i only have a 10gig original xbox drive.
if someone know how can i change my hard drive I will appreciate.
Post by: rmenhal on July 11, 2004, 05:11:00 PM
| QUOTE (smegmahead @ Jul 11 2004, 10:56 PM) |
| I've succefully run nkpatcher into my v1.6 xbox with a 5838 kernel, but i'd like to know how can i change my hard drive for a bigger one with the nkpatcher ??? For myself I've put my knkpatcher6 directly too my game save hack of splintercell to load my xbox media center so i can run things from the network as i only have a 10gig original xbox drive. if someone know how can i change my hard drive I will appreciate. |
The same way you would do it if you were running PBL. You need to check out some tutorials and ldots' xboxhdm.
Post by: old engineer on July 12, 2004, 08:40:00 AM
| QUOTE (rmenhal @ Jul 12 2004, 02:04 AM) |
| Well, everything seems to be in order so far. Have you tried running nkpatcher from evox dash (save game -> evoxdash -> nkpatcher -> C:\evoxdash.xbe, no other dashes in between)? |
Yeah, that was how I originally tried to launch it
...Gonna try 'metoopbl' now
Post by: rmenhal on July 19, 2004, 12:32:00 AM
| QUOTE (Error420 @ Jul 18 2004, 04:01 PM) |
| You guys make this nkpatcher compile thing sound so easy. I only have visual c++ standard edition so I gotta do some major searching to find c++ enterprise or higher. I've already downloaded like 300 or 400 megs trying to get all the files I need to compile a xbe. |
Sorry, but you don't need those files for nkpatcher.
You need Netwide Assembler: http://nasm.sourceforge.net/Post by: EthanHunt_IMF on July 19, 2004, 02:44:00 AM
| QUOTE (rmenhal @ Jul 11 2004, 08:14 PM) |
| The same way you would do it if you were running PBL. You need to check out some tutorials and ldots' xboxhdm. |
Anyone use Ldots xboxhdm with the eeprom.bin produced with evox backup option to calculate the new password? Config Magic doesn't work on v1.6 box (at least not the one i tried it on) and the eeprom.bin produced from evox's backup feature didn't work in liveinfo.
The work around is to copy the hdkey from the txt file evox produces and paste it into liveinfo (make sure you take out the spaces).
Post by: steinarne on July 21, 2004, 10:57:00 AM
Anyone who can help me?
PM me maybe?
I appreciate it
Post by: mkjones on September 28, 2004, 04:54:00 AM
Im trying to come up with a way to boot nkp from an apps menu so it then boots a game DVD from d:\defualt.xbe
Obviusly you would need to turn any auto boot features off in my dash.
I know this could be done in MXM, but I wanted to stay away from having to boot another dash just to do it.
Any ideas?
Do ya think if the boot path was changed to d:\defualt.xbe and you just stuck a game in and then it would boot fine?
Post by: krayzie on September 28, 2004, 08:50:00 AM
| QUOTE (mkjones @ Sep 28 2004, 12:57 PM) |
| Anyone help me out Im trying to come up with a way to boot nkp from an apps menu so it then boots a game DVD from d:\defualt.xbe Obviusly you would need to turn any auto boot features off in my dash. I know this could be done in MXM, but I wanted to stay away from having to boot another dash just to do it. Any ideas? Do ya think if the boot path was changed to d:\defualt.xbe and you just stuck a game in and then it would boot fine? |
I once did that to let unsigned games boot on a non-pbl/nkpatcher exploited xbox. So that it first boots the habibi signed nkpatcher default.xbe then boots to d:/game.xbe
Anyway you just have to edit the line "db '\Device\Harddisk0\Partition2;evoxdash.xbe" in the asm source to "db '\Device\Cdrom0;default.xbe" in your case. Note that nkpatcher does not work with hacked bfm bioses that might have been loaded.
Post by: rmenhal on October 30, 2004, 01:48:00 AM
| CODE |
;;; -------------------------------------------------------------------------- ;;; Configuration for nkpatcher ;;; -------------------------------------------------------------------------- ;;; Dashboard path %define DASHBOARD_PATH '\Device\Harddisk0\Partition2\evoxdash.xbe' ;;; Reset-on-eject behaviour: ;;; ;;; EJECT_FIX = Never reset on eject. ;;; CD_DVD_ALWAYS_ROE = Always reset on eject for CD/DVD loaded XBEs, never ;;; reset on eject for hard disk loaded XBEs. ;;; ;;; Default is to never reset on eject for hard disk loaded XBEs, but reset ;;; on eject CD/DVD loaded XBEs based on the ROE flag in the XBE header. ; %define EJECT_FIX ; %define CD_DVD_ALWAYS_ROE ;;; Automatic game region settings: ;;; ;;; GAME_REGION_AUTO = Set game region automatically based on the game region ;;; field in XBE header. Since the header may have several ;;; regions enabled there's a choice to be made. First ;;; tried is the game region from EEPROM, then the primary ;;; through tertiary regions below. ;;; GAME_REGION_IGNORE_REAL = Ignore the region stored in EEPROM and only ;;; use primary through tertiary regions below. ;;; ;;; Default is to use only the game region stored in the EEPROM and not ;;; change it. %define GAME_REGION_AUTO ; %define GAME_REGION_IGNORE_REAL %ifdef GAME_REGION_AUTO ;;; Game regions: ;;; ;;; 1 = North America ;;; 2 = Japan ;;; 4 = Rest of world %define GAME_REGION_PRIMARY 4 %define GAME_REGION_SECONDARY 1 %define GAME_REGION_TERTIARY 2 %endif; GAME_REGION_AUTO ;;; In-Game Reset settings: ;;; ;;; IGR = Enable IGR code ;;; ;;; Button combinations: ;;; * triggers+back+start ;;; * triggers+back+black ;;; * triggers+start+black ;;; ;;; IGR_TO_DASHBOARD = Reset to dashboard, not DVD. Changed button combos: ;;; * triggers+back+start to dashboard ;;; * triggers+back+black to dashboard ;;; * triggers+tart+black to first DVD, then dashboard ;;; ;;; IGR_FULL_REBOOT = Do a full reboot instead of the default quick reboot. ;;; Some games hang (Soul Calibur 2 during a match) with ;;; quick reboot. ;;; ;;; IGR_MASTER_PORT #port_number = Only allow IGR from pad port #port_number, ;;; where #port_number is 0-3 (0 the left-most ;;; port, 3 the right-most.) ;;; ;;; IGR is not enabled by default. %define IGR %define IGR_TO_DASHBOARD ; %define IGR_FULL_REBOOT ; %define IGR_MASTER_PORT 0 ;;; Xbox Live blocking: ;;; ;;; XBL_BLOCK = Enable blocking ;;; ;;; Blocking not enabled by default. %define XBL_BLOCK ;;; Patches inside INIT section (boot unlocked HDs etc.) ;;; ;;; INIT_SEC_PATCHES = enable ;;; ;;; Do NOT enable these for nkpatcher.xbe executed on the Xbox (will crash ;;; and/or weird behaviour.) ; %define INIT_SEC_PATCHES ;;; -------------------------------------------------------------------------- ;;; Configuration end ;;; -------------------------------------------------------------------------- |
Post by: PedrosPad on October 30, 2004, 12:45:00 PM
Post by: total_ass on October 30, 2004, 01:03:00 PM
Post by: PedrosPad on October 31, 2004, 03:26:00 PM
| QUOTE (rmenhal @ Oct 30 2004, 09:51 AM) |
| Nkpatcher7 (in the root post) is a big feature upgrade to nkpatcher6. |
Hi rmenhal,
Is there any feature of NASM you haven't managed to use in the release - lol
.(conditional compilation, macros, local labels, ...)
Post by: DaddyJ on October 31, 2004, 03:40:00 PM
Post by: zorxd on November 01, 2004, 04:38:00 PM
Post by: DaddyJ on November 01, 2004, 04:44:00 PM
lol
Post by: krayzie on November 10, 2004, 10:02:00 AM
| QUOTE (Dunny @ Nov 10 2004, 07:04 PM) |
| Is there anyway to have it load the dash before the dvd. |
yeah set the dash to not auto launch games
Post by: rmenhal on November 10, 2004, 10:20:00 AM
| QUOTE (Dunny @ Nov 10 2004, 07:12 PM) |
| so I imagine Nkpatcher loads from a dvd before the dash? |
Yes, that's the default with nkpatcher7 (was different in nkpatcher6). You need to recompile with BOOT_DASH_ONLY option:
nasm -dBOOT_DASH_ONLY -o nkpatcher.xbe xboxapp.asm
(and sign it with habibi).
Post by: Dunny on November 10, 2004, 10:26:00 AM
Post by: Dunny on November 10, 2004, 10:48:00 AM
| QUOTE |
| nkpatcher.asm:189: error: symbol `patchmedia.ntqvol` undefined nkpatcher.asm:189: error: symbol `patchmedia.ntqvol` undefined xboxapp.asm:205: error: phase error detected at end of assembly. |
Post by: rmenhal on November 10, 2004, 11:08:00 AM
| QUOTE (Dunny @ Nov 10 2004, 07:29 PM) |
| I went into xboxapp.asp and uncommented the below, ; %define BOOT_DASH_ONLY is it ok to do it like that? seems to work fine. great work on this btw, I was wrecking my head trying to boot PBL! |
Yes, that's good.
The EJECT_FIX option has a bug. The line 189 is:
| QUOTE |
setcalljmptarget edx, patchmedia, ntqvol, edi |
It should be wrapped like this:
| QUOTE |
| %ifndef EJECT_FIX setcalljmptarget edx, patchmedia, ntqvol, edi %endif |
But you won't have any use for this option anyway. As far as anybody knows, the hard reset on eject cannot be fixed (and you have that enabled because you're using a game save exploit.)
Post by: Dunny on November 10, 2004, 11:21:00 AM
Post by: myst on November 15, 2004, 12:11:00 PM
Post by: Brice123 on November 17, 2004, 02:44:00 PM
-Brice
Post by: Brice123 on November 17, 2004, 02:45:00 PM
| QUOTE (rmenhal @ Oct 30 2004, 09:51 AM) | ||
Nkpatcher7 (in the root post) is a big feature upgrade to nkpatcher6. Here's the sample (compile-time) configuration file from the release:
|
Hey guys, sorry if this is a noob question...but I need to fix the IGR on nkpatcher with this update. How (I heard you have to extract files with winrar and winzip) and where do I put this file on my xbox to fix the IGR problem? Is this more complicated than just a simple cut and paste of code into a evox.ini file, or for me, my config.xml. Thanks guys!
-Brice
Post by: lp2000 on November 17, 2004, 09:00:00 PM
Post by: keggerman on November 24, 2004, 02:01:00 AM
Chris
Post by: zorxd on December 12, 2004, 01:23:00 PM
however isn't 500Mb too big for a C partition?
Post by: DaddyJ on December 12, 2004, 01:27:00 PM
The C Partition is around 520 megs blank.
But nkpatcher is no where near that big.
Post by: jimmsta on December 12, 2004, 02:39:00 PM
Post by: DaddyJ on December 12, 2004, 03:12:00 PM
Post by: jimmsta on December 12, 2004, 04:05:00 PM
Post by: garyopa on December 12, 2004, 04:05:00 PM
Posted last night on the "news" page.
But not in this thread. Since "NO EDIT" button, I guess.
Post by: DaddyJ on December 12, 2004, 04:08:00 PM
Post by: rmenhal on December 12, 2004, 08:31:00 PM
PS. A fix will be released.
Post by: total_ass on December 13, 2004, 09:14:00 AM
you really should be a mod.
Post by: krayzie on December 13, 2004, 09:32:00 AM
Post by: total_ass on December 13, 2004, 09:51:00 AM
if so then we are finally protected from MS once and for all.
Post by: warpjavier on December 13, 2004, 11:23:00 AM
First of all, thanks to rmenhal for his work.
And a question, M$ is able to detect Nkpatcher running?. I mean, can I go live with Nkpatcher running?
Maybe is a stupid question, but I want to be sure.
Thanks
Post by: krayzie on December 13, 2004, 12:56:00 PM
Post by: total_ass on December 13, 2004, 12:59:00 PM
don't quote me on this in the future lol but i think we can safely say that MS cannot harm us anymore.
oops i bet i just jinxed it.
Post by: krayzie on December 13, 2004, 01:17:00 PM
Post by: total_ass on December 13, 2004, 01:21:00 PM
could nkpatcher actually be stored on the real C partition, then when the shadow drive is loaded up, then nkpatcher cannot be accessed. this means that MS cannot target NKpatcher.
screw read-only, we got a shield!!!!
Post by: RiceCake on December 13, 2004, 02:12:00 PM
Even if they can't see NKpatcher on C - they'll still ban you.
Besides you gotta store NKpatcher somewhere to run the damn thing, lol...
Post by: Cain on December 13, 2004, 05:46:00 PM
I'd like to have the shadow C: image on the C: partition, so the partition would just contain:
bert-generic.xtf
ernie.xtf
xboxdash.xbe
nkpatcher.xbe
default.xbe
shadowc.img
Is this going to cause a loop?
and does nkpatcher load the dash [%define DASHBOARD_PATH '\Device\Harddisk0\Partition2\default.xbe'] from the real partition or the image?
thanks.
Post by: krayzie on December 13, 2004, 10:20:00 PM
| QUOTE |
| Is this going to cause a loop? and does nkpatcher load the dash [%define DASHBOARD_PATH '\Device\Harddisk0\Partition2\default.xbe'] from the real partition or the image? |
I dunno for sure but I guerss it will go in some loop or hang something trying to load an image from a hidden partition.
And my nkpatcher boots to c:\evoxdash.xbe and not default.xbe but it loads it from the virtual C since it gets loaded after nkpatcher. So make sure not to delete that of the virtual C.
Post by: rmenhal on December 13, 2004, 10:51:00 PM
| QUOTE (Cain @ Dec 14 2004, 02:49 AM) |
| Is this going to cause a loop? and does nkpatcher load the dash [%define DASHBOARD_PATH '\Device\Harddisk0\Partition2\default.xbe'] from the real partition or the image? |
Currently, you can't have the image on the real C drive. It would be possible with some code additions, but of course the virtual C drive then needs to be smaller than 500 MB.
Like krayzie said, the hacked dash will get loaded from the image.
Post by: slrhsapple on December 13, 2004, 11:52:00 PM
. Thanks you. Have a nice holiday
Post by: total_ass on December 14, 2004, 12:17:00 AM
| QUOTE (RiceCake @ Dec 13 2004, 10:15 PM) |
| Uhh... Even if they can't see NKpatcher on C - they'll still ban you. Besides you gotta store NKpatcher somewhere to run the damn thing, lol... |
i wasn't trying to say that you will not get banned. even i know that any modifications to the bios at all will get you banned.
no what i was trying to say was that with the new Shadow C MS cannot kill our exploits anymore.
Post by: krayzie on December 14, 2004, 03:02:00 AM
Rmenhal has done it again.
Post by: BlackWar on December 14, 2004, 11:10:00 AM
Post by: chimpanzee on December 14, 2004, 11:20:00 AM
| QUOTE (krayzie @ Dec 14 2004, 12:05 PM) |
| Even though the whole softmod kill stuff is way to overated this virtual c feature is a great step in beating any way for m$ to harm our beloved xboxes. Normally it's just a cat and mouse game where we would have to beat any new security feature m$ has built into their system. Now we have taken 1 major step in front of them and it will not be easy for them to fix it and I doubt if they ever gonna try it. Rmenhal has done it again. |
While this feature is neat(no longer need to patch xboxdash.xbe), I believe the problem remains.
If nkpatcher is not in action(booting from retail games which may update xboxdash.xbe or going live), the problem would still be there as it is now(but the fonts hack may already prevent it).
If nkpatcher is in action, it blocks live anyway.
So the only new protection seems to be running games under nkpatcher that may either update xboxdash or in some case refers to c:\fonts.
Post by: total_ass on December 14, 2004, 11:22:00 AM
Post by: total_ass on December 14, 2004, 11:33:00 AM
Post by: krayzie on December 14, 2004, 11:53:00 AM
| QUOTE (chimpanzee @ Dec 14 2004, 08:23 PM) |
| While this feature is neat(no longer need to patch xboxdash.xbe), I believe the problem remains. If nkpatcher is not in action(booting from retail games which may update xboxdash.xbe or going live), the problem would still be there as it is now(but the fonts hack may already prevent it). If nkpatcher is in action, it blocks live anyway. So the only new protection seems to be running games under nkpatcher that may either update xboxdash or in some case refers to c:\fonts. |
Yeah well I wasn't saying it was a complete 100 % proof fix but it is a major step forwards. If you wanna play retail games just let nkpatcher boot first.
Post by: krayzie on December 14, 2004, 12:28:00 PM
| QUOTE (Cain @ Dec 14 2004, 09:29 PM) |
| How about using the clock loop issue to our advantage... get nkpatcher to corrupt the clock on every boot, games wouldnt load on boot, instead it would go straight to the dash (UXE -> Nkpatcher). Then there would be no way for MS to see the c: partition without hacking at their own BIOS, which I doubt they'd bother with. Just a thought. |
I actually thought of that too but it leaves you with an wrongly set clock every time.
Post by: PedrosPad on December 14, 2004, 01:03:00 PM
| QUOTE (Cain @ Dec 14 2004, 09:29 PM) |
| How about using the clock loop issue to our advantage... get nkpatcher to corrupt the clock on every boot, games wouldnt load on boot, instead it would go straight to the dash (UXE -> Nkpatcher). Then there would be no way for MS to see the c: partition without hacking at their own BIOS, which I doubt they'd bother with. Just a thought. |
Very cool thought
. I like the way your mind works . But krayzie's right it does have a big disadvantage. Post by: total_ass on December 14, 2004, 01:06:00 PM
omg there is a pedros the second...........
Post by: DaddyJ on December 14, 2004, 01:06:00 PM
Post by: krayzie on December 14, 2004, 01:08:00 PM
| QUOTE (DaddyJ @ Dec 14 2004, 10:09 PM) |
| Unless you added some code to automatically set the clock, based on a time server, if the xbox has access to online. |
sure any timeserver based dash would solve that but still that's only for xboxes connected to the internet.
Post by: big ben bullet on December 14, 2004, 01:09:00 PM
*sits back his lazy arse and waits until something comes up he can help with*
Post by: DaddyJ on December 14, 2004, 01:10:00 PM
Although the time wouldnt be accurate, it wouldnt be totally wrong.
Post by: zorxd on December 14, 2004, 02:17:00 PM
| QUOTE (Anusko @ Dec 14 2004, 10:50 PM) |
| is this image a pure fatx iso? why does it have to be exactly 500mb large? can i make an iso of my C drive with a PC fatx iso creation tool and use it as the C image? just to know if I can save some work |
this is not an ISO, it`s a FATX image
it can't be burned with nero
ISO9660 isn't the same filesystem as FATX
an xbox ISO (xISO) is neither the same than FATX, it's more like UDF
Post by: fghjj on December 14, 2004, 02:18:00 PM
| QUOTE (Anusko @ Dec 14 2004, 10:50 PM) |
| is this image a pure fatx iso? why does it have to be exactly 500mb large? can i make an iso of my C drive with a PC fatx iso creation tool and use it as the C image? just to know if I can save some work |
Why bother, the shadowcmaker.xbe is very fast. If I'm correct it only allocates 500mb and copies the files already on C into that image, so no long 1:1 byte duplication process.
Ps running NKpatcher 8.1 thanks for this Great Work®
Post by: Cain on December 14, 2004, 03:00:00 PM
| QUOTE (Bcat007 @ Dec 14 2004, 10:28 PM) |
| If we're talking about booting with a game/DVD, all of this "clock" talk seems irrelevant because nkpatcher would be bypassed correct? |
No, if the clock is corrupt the xbox dash (exploit) will launch regardless.
Whether games can be launched from the dash while the clock is corrupt I dont know.
But maybe nkpatcher could patch the kernel so it can?
Post by: PedrosPad on December 14, 2004, 03:05:00 PM
QUOTE(krayzie @ Dec 14 2004, 09:31 PM)
QUOTE(Cain @ Dec 14 2004, 09:29 PM)
QUOTE(chimpanzee @ Dec 14 2004, 07:51 PM)
QUOTE(krayzie @ Dec 14 2004, 12:05 PM)
Even though the whole softmod kill stuff is way to overated this virtual c feature is a great step in beating any way for m$ to harm our beloved xboxes. Normally it's just a cat and mouse game where we would have to beat any new security feature m$ has built into their system. Now we have taken 1 major step in front of them and it will not be easy for them to fix it and I doubt if they ever gonna try it.
Rmenhal has done it again.
Rmenhal has done it again.
While this feature is neat(no longer need to patch xboxdash.xbe), I believe the problem remains.
If nkpatcher is not in action(booting from retail games which may update xboxdash.xbe or going live), the problem would still be there as it is now(but the fonts hack may already prevent it).
If nkpatcher is in action, it blocks live anyway.
So the only new protection seems to be running games under nkpatcher that may either update xboxdash or in some case refers to c:\fonts.
How about using the clock loop issue to our advantage...
get nkpatcher to corrupt the clock on every boot, games wouldnt load on boot, instead it would go straight to the dash (UXE -> Nkpatcher).
Then there would be no way for MS to see the c: partition without hacking at their own BIOS, which I doubt they'd bother with.
Just a thought.
I actually thought of that too but it leaves you with an wrongly set clock every time.
A unset clock isn't the only condition that forces the HDD to be booted instead of the DVD-Rom.
From xbox-linux's EEPROM contents description:
QUOTE
//To reset XBOX to Factory settings, Make checksum3 0xFFFFFFFF and zero all data below (0x64-0xFF)
//Doing this will Reset XBOX and upon startup will get Language & Setup screen...
//Doing this will Reset XBOX and upon startup will get Language & Setup screen...
NKPatcher could restore these static settings from a disk file once it takes control, if needs be (unlike the ever changing clock). (I believe this can be done to a RAM shadow of the EEPROM, leaving the physical EEPROM still at factory settings ready for the next cold start.)
Post by: Cain on December 14, 2004, 04:52:00 PM
| QUOTE (PedrosPad @ Dec 14 2004, 11:08 PM) |
| A unset clock isn't the only condition that forces the HDD to be booted instead of the DVD-Rom. From xbox-linux's EEPROM contents description: NKPatcher could restore these static settings from a disk file once it takes control, if needs be (unlike the ever changing clock). (I believe this can be done to a RAM shadow of the EEPROM, leaving the physical EEPROM still at factory settings ready for the next cold start.) |
That's a great idea.
Not sure how the current fonts would react if there wasnt a language set (there seem to be issues with certain languages). I've also heard there are some issues with parental control turned on. As the memory gets layed out differently.
But, with the EEPROM in a known (pretty much blank) state, one set of new fonts may work for all (i.e. no s.xtf's needed).
You may have found the perfect solution.
Blank out the end of the EEPROM and get Nkpatcher to load your settings from a .cfg file/backup image into RAM.
It may also be a good idea to get Nkpatcher to back up the EEPROM itself and then zero out the data if checksum3 != 0xFFFFFFFF. Just in case it gets changed...
Actually, what would be good would be to intercept all calls to modify the EEPROM directly and modify the backup instead
. Though I doubt this would be possible.Then it would be perfect.
Post by: Millions Knives on December 14, 2004, 06:02:00 PM
I hate to sound stupid, but I'm having trouble going from PBL-Metoo M8plus 1.4.1 to nkpatcher v8.1
In the readme file for nkpatcher, rmenhal states:
"Edit files config.inc and xboxapp.asm to configure nkpatcher. Then compile using NASM (Netwide Assembler)."
Can I just use notepad to change the values so that nkpatcher looks for my UnleashX dash in E:\Dashboard\default.xbe instead of C:\evoxdash.xbe
And also, when I try to run NASM to recompile, the prompt opens for a split second and then closes out. I'm not sure how to use it exactlly so that might be why.
I'll be honest with you, I have no idea what I'm doing when it comes to compiling files. I read this whole post and read on the NASM website on how to use the program, but no luck.
I currently have UXE installed using ldolts 1.8 installer. I tried searching for the answer to this question, but have had a hard time finding much information.
Post by: zorxd on December 14, 2004, 07:58:00 PM
dd if=/dev/discs/disc0/part51 of=/mnt/E/shadowc/shadowc.img
it seems to work but it's read only
Post by: cocaloca on December 14, 2004, 08:15:00 PM
Post by: rmenhal on December 14, 2004, 08:52:00 PM
| QUOTE (fghjj @ Dec 14 2004, 11:21 PM) |
| Why bother, the shadowcmaker.xbe is very fast. If I'm correct it only allocates 500mb and copies the files already on C into that image, so no long 1:1 byte duplication process. |
It is a byte-for-byte copy.
I might make it check the shadow image file length and adjust partition size based on it - in some future version.
Post by: rmenhal on December 14, 2004, 08:54:00 PM
| QUOTE (Cain @ Dec 15 2004, 01:55 AM) |
| Then it would be perfect. |
Well, safety was the reason the clock set code was put into UDE/UXE fonts.
Post by: rmenhal on December 14, 2004, 09:10:00 PM
| QUOTE (zorxd @ Dec 15 2004, 05:01 AM) |
| does the program to create a virtual c:\ do the same than this linux command : dd if=/dev/discs/disc0/part51 of=/mnt/E/shadowc/shadowc.img it seems to work but it's read only |
It should work, but it doesn't. I banged my head on a wall on this one too while developing the shadow drive feature. It's actually a problem/bug/issue in Xbox-Linux kernel fatx file system implementation.
All fatx files created with Xbox-Linux kernel are slighly corrupt in the eyes of MS Xbox kernel. MS kernel refuses to write into such a file, that's why it's read-only. I believe this is also why people have to delete E:\cache files (and all cache drives?) after building their new HD with XboxHDM. Although the fatx allocation chains for all files are then ill-terminated, the cache (and game save) files are pretty much the only files that need to be written into. When a game can't do so, it will crash or go into some infinite loop. Only writing into file seems affected, but there might be also other issues, I don't know.
Below is the mail I sent to one of the Xbox-Linux fatx authors a few weeks ago. I haven't got a reply back or anything, so I don't know if they are ever going to fix this.
| CODE |
Hello, Seems there's a slight incompatibility between Xbox-Linux v2.4 kernel and MS Xbox kernel fatx file system implementions. Xbox-Linux marks the last cluster of a file with 0xfffffff8 (32-bit entries) and MS kernel marks with 0xffffffff. MS kernel doesn't like the former marking; writing to a file created by Xbox-Linux kernel fails to STATUS_FILE_CORRUPT_ERROR (0xc0000102). This can be seen by creating some, say 100000 byte, file using Xbox-Linux kernel and then booting to MS kernel and writing to the file with NtWriteFile(). Here's a quick and dirty patch: --- linux-2.4.28-xbox/fs/fatx/cache.c.~1.2.~ Sat Mar 15 09:19:45 2003 +++ linux-2.4.28-xbox/fs/fatx/cache.c Sat Nov 27 02:59:50 2004 @@ -59,9 +59,13 @@ PRINTK("FATX: fatx_access: 0x%x, nr=0x%x, first=0x%x, next=0x%x\n", b, n r, first, next); if (new_value != -1) { if (FATX_SB(sb)->fat_bits == 32) { + if (new_value == (int)0xfffffff8) + new_value = (int)0xffffffff; ((__u32 *)bh->b_data)[(first & (sb->s_blocksize - 1)) >> 2] = CT_LE_L(new_value); } else if (FATX_SB(sb)->fat_bits == 16) { + if (new_value == 0xfff8) + new_value = 0xffff; ((__u16 *)bh->b_data)[(first & (sb->s_blocksize - 1)) >> 1] = CT_LE_W(new_value); } |
Post by: easyguy on December 14, 2004, 09:17:00 PM
lefttrigger-righttrigger-black-back
thanks rmenhal for the virtual drive. wat ive been looking for a long time.
Post by: zorxd on December 15, 2004, 06:21:00 AM
| QUOTE (rmenhal @ Dec 15 2004, 06:13 AM) |
| It should work, but it doesn't. I banged my head on a wall on this one too while developing the shadow drive feature. It's actually a problem/bug/issue in Xbox-Linux kernel fatx file system implementation. All fatx files created with Xbox-Linux kernel are slighly corrupt in the eyes of MS Xbox kernel. MS kernel refuses to write into such a file, that's why it's read-only. I believe this is also why people have to delete E:\cache files (and all cache drives?) after building their new HD with XboxHDM. Although the fatx allocation chains for all files are then ill-terminated, the cache (and game save) files are pretty much the only files that need to be written into. When a game can't do so, it will crash or go into some infinite loop. Only writing into file seems affected, but there might be also other issues, I don't know. Below is the mail I sent to one of the Xbox-Linux fatx authors a few weeks ago. I haven't got a reply back or anything, so I don't know if they are ever going to fix this. |
I also tried to copy the first 2Mb from the C drive
It made a buggy not usable C:\ drive but at least it prevents dashboard updates
Post by: DaddyJ on December 15, 2004, 06:24:00 AM
| QUOTE (rmenhal @ Dec 15 2004, 12:13 AM) |
| All fatx files created with Xbox-Linux kernel are slighly corrupt in the eyes of MS Xbox kernel. MS kernel refuses to write into such a file, that's why it's read-only. I believe this is also why people have to delete E:\cache files (and all cache drives?) after building their new HD with XboxHDM. Although the fatx allocation chains for all files are then ill-terminated, the cache (and game save) files are pretty much the only files that need to be written into. When a game can't do so, it will crash or go into some infinite loop. Only writing into file seems affected, but there might be also other issues, I don't know. |
This explains alot, thanks for that bit of info.
Post by: PedrosPad on December 15, 2004, 09:38:00 AM
Not tired the ISO rip thing yet. I'll ask, is this the only way to create compatible ISOs, or can quix/etc. be used?
BTW - Bloddy nice work rmenhal.
Post by: PedrosPad on December 15, 2004, 10:18:00 AM
- now you can update your own root post.
Post by: total_ass on December 15, 2004, 10:41:00 AM
Post by: krayzie on December 15, 2004, 10:45:00 AM
Post by: total_ass on December 15, 2004, 10:47:00 AM
oh and yes it boots off the dvd while using IGR but i figured that was just the dash doing it.
anyway ignore my post.
sorry about that.
Post by: rossmac on December 15, 2004, 01:48:00 PM
Post by: Millions Knives on December 15, 2004, 02:04:00 PM
Post by: jimmsta on December 15, 2004, 08:23:00 PM
Post by: jimmsta on December 15, 2004, 08:41:00 PM
I managed to test the nkpatcher xbe that I compiled... and managed to make a shadow of my c drive, so I must have done something right...
Post by: krayzie on December 18, 2004, 11:39:00 PM
Post by: big ben bullet on December 19, 2004, 03:59:00 AM
| QUOTE |
| Another extra safety precaution to prevent the loading of retail games before the exploit would be to simply just change the xbe region number in the eeprom. |
being able to load retail games is my backup-plan for if i mess up
it's got to be able to boot mechassault for me :-)
otherwise i would have to xboxhdm everytime i mess up (and that's alot, 'cause i like to mess with things)
Post by: Flame2k on December 19, 2004, 08:07:00 AM
Post by: krayzie on December 19, 2004, 08:25:00 AM
| QUOTE (big ben bullet @ Dec 19 2004, 01:02 PM) |
| being able to load retail games is my backup-plan for if i mess up it's got to be able to boot mechassault for me :-) otherwise i would have to xboxhdm everytime i mess up (and that's alot, 'cause i like to mess with things) |
for your information mechassault works on multiple regions so you are always able to boot that prior to the exploit. I was just making another sugestion according to the clock coruption sugestions a page earlier in the thread.
Post by: big ben bullet on December 19, 2004, 09:46:00 AM
| QUOTE |
| for your information mechassault works on multiple regions so you are always able to boot that prior to the exploit. I was just making another sugestion according to the clock coruption sugestions a page earlier in the thread. |
so changing the eeprom region would still allow multi-region games to boot without nkpatcher kicking in first... leaving the c drive unprotected for possible 'updates'
though it would protect against region-specific games booting ;-)
anyway... i'm not scared of those updates, as long as i got mechassault to ftp in and put things straight again
Post by: krayzie on December 19, 2004, 02:10:00 PM
| QUOTE (big ben bullet @ Dec 19 2004, 06:49 PM) |
| so changing the eeprom region would still allow multi-region games to boot without nkpatcher kicking in first... leaving the c drive unprotected for possible 'updates' though it would protect against region-specific games booting ;-) anyway... i'm not scared of those updates, as long as i got mechassault to ftp in and put things straight again |
yeah mechassault works at least with regions 1 and 4 so if you'd change the region to one of that it will keep working from bootup. Anyway it's not like everybody should go change his region now. We were just discussing the possibilities of making the hack super proof. Right now there is no fear of games updating the dash/killing the exploits since they still look for fonts on the hd. And I doubt they ever gonna change that. Anyway like I said changing the region would be very easy to prevent any retail game booting up before exploit/nkpatcher except for mechassault and does't leave you with a wrong clock every time.
Post by: DaddyJ on December 19, 2004, 02:20:00 PM
| QUOTE (big ben bullet @ Dec 19 2004, 12:49 PM) |
| anyway... i'm not scared of those updates, as long as i got mechassault to ftp in and put things straight again |
I'd much rather have my XboxHDM restore cd
| QUOTE (krayzie @ Dec 19 2004, 12:49 PM) |
| Anyway like I said changing the region would be very easy to prevent any retail game booting up before exploit/nkpatcher except for mechassault and does't leave you with a wrong clock every time. |
Yes it would.
Post by: big ben bullet on December 19, 2004, 02:46:00 PM
| QUOTE |
| I'd much rather have my XboxHDM restore cd |
certainly... i have that too... but like i said, i don't like the hassle of opening up my pc everytime i mess my current softmod up ;-) that's why i need mechassault... if mechassault fails (or fails to load my evox save) -> xboxhdm 'll rebuild my drive ;-)
everyone should have at least one copy of a xboxhdm cd... preferably also a more recent working backed-up version on his pc in xboxhdm\linux\c (with eeprom in xboxhdm\linux\eeprom)
that's common knowledge ;-) or it SHOULD be anyway...
ohw, and about me messing up my softmods... hmmm i just like to mess with it (recompile fonts, nkpatcher... try another bios setting with pbl... keeps me busy ;-)
edited: i like your font compiler btw... any chance in making the source public? (i have to admit i know vb6... damn language)
Post by: DaddyJ on December 19, 2004, 02:52:00 PM
| QUOTE (big ben bullet @ Dec 19 2004, 05:49 PM) |
| any chance in making the source public? |
Never thought about it. But I see no reason why not. Its very basic code. Check the link in my sig in a few hours.
Post by: DaddyJ on December 19, 2004, 05:55:00 PM
I havent used nkpatcher before, but it sounds quite awesome.
From my understanding, my 'original C' remains in a soft-modded state, then nkpatcher loads and 'Visually' Overwrites the C, from here you can ftp in to set this 'C' drive up with orginal files?
Then games that are loaded (multi-games, etc) will read the fonts from c:\fonts, and those are the real fonts.
Is my basic grasp of this correct, or am I totally wrong.
Thx.
Post by: krayzie on December 19, 2004, 09:56:00 PM
| QUOTE (DaddyJ @ Dec 20 2004, 02:58 AM) |
| Can anyone explain the C shadowing feature. I havent used nkpatcher before, but it sounds quite awesome. From my understanding, my 'original C' remains in a soft-modded state, then nkpatcher loads and 'Visually' Overwrites the C, from here you can ftp in to set this 'C' drive up with orginal files? Then games that are loaded (multi-games, etc) will read the fonts from c:\fonts, and those are the real fonts. Is my basic grasp of this correct, or am I totally wrong. Thx. |
Your basic grap is correct. While nkpatcher is active there is a virtual C loaded which you can unmod so any games that autoupdate or have multi menus that uses fonts will work without problems.
any chance in explaining this?
| QUOTE |
| QUOTE (krayzie @ Dec 19 2004, 12:49 PM) Anyway like I said changing the region would be very easy to prevent any retail game booting up before exploit/nkpatcher except for mechassault and does't leave you with a wrong clock every time. Yes it would. |
Post by: Keo-Keo on December 19, 2004, 10:17:00 PM
| QUOTE |
\Device\Harddisk0\Partition1\APILog\default.xbe Loading nkpatcher \Device\CdRom0\default.xbe Loading from cd rom? Why should be loading from \Device\Harddisk0\Partition1\APILog\unleash.xbe or e:\APILog\unleashx.xbe Crashes or decides to boot my dash \Device\Harddisk0\Partition1\Dashboard\default.xbe \Device\Harddisk0\Partition1\x2_IGR_disabled \Device\Harddisk0\Partition1\TDATA\080299ff \Device\Harddisk0\Partition1\Dashboard |
Then abunch of dash shit. Whats wrong? Any idea's?
Post by: big ben bullet on December 20, 2004, 01:13:00 AM
| QUOTE |
| Never thought about it. But I see no reason why not. Its very basic code. Check the link in my sig in a few hours. |
Thx... i'll have a look at it when i get home ;-)
Post by: big ben bullet on December 20, 2004, 07:35:00 AM
| QUOTE |
| i thought thats what the dualboot.xbe in ltools is for. to give u a chance to correct your mistake in case u somehow messed up ur bios or dash or watever. the beauty is that u can simply boot ur xbox with the tray out n fix anything thru ftp. isnt that what its for? |
erh... what if you also mess up the second boot option?
Post by: total_ass on December 20, 2004, 07:49:00 AM
Post by: PedrosPad on December 20, 2004, 09:56:00 AM
| QUOTE (rmenhal @ Jun 20 2004, 06:39 PM) |
| Nkpatcher is proposed as a simple and temporary solution to the problem. The feature set is very limited and inferior to BIOSes such as Xecuter X2. <snip /> Kernel 5713+ users won't be able to use any dashboard exploit such as UDE, but could use a game-save exploit if they wish. |
rmenhal, due to your very hard work, the root post of this thread is increasingly out of date. You want'a use your new mod powers and bring it up to date?
Post by: easyguy on December 20, 2004, 10:54:00 AM
Post by: total_ass on December 20, 2004, 11:37:00 AM
then that leaves pretty much just deleting the image of the shadow drive a potential problem. the shadow drive can be any size? because if thats so then can it not be allowed the minimal size needed for the MS dash and fonts to operate, then perhaps 10 or 20 extra meg of space. then it could be stored on the real c drive? or is that technically impossible as the image itself could not be accessed after being mounted.
forgive me if i make no sense.
Post by: DaddyJ on December 21, 2004, 12:08:00 PM
Post by: total_ass on December 21, 2004, 12:20:00 PM
then the only thing that can bypass it is booting into a retail game, though this is down to the user and doesn't pose any threat to the exploit or to the shadow C drive.
very good
(btw i hate this new skin)
Post by: SpankyFarmer2K on December 28, 2004, 11:02:00 AM
Post by: krayzie on December 28, 2004, 11:07:00 AM
QUOTE(SpankyFarmer2K @ Dec 28 2004, 07:33 PM)
I accidently clicked on create c shadow in evox testing out different apps and now when i use flash fxp i cant edit or change or delete anything on the c drive i have no idea how to fix this any help would be appreciated.... thankss
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: krayzie on December 28, 2004, 11:41:00 AM
-
just ftp a bios loader to your apps folder
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: DaddyJ on December 28, 2004, 11:48:00 AM
-
Post by: krayzie on December 28, 2004, 11:41:00 AM
Post by: DaddyJ on December 28, 2004, 11:48:00 AM
QUOTE(SpankyFarmer2K @ Dec 28 2004, 02:16 PM)
im going to throw this fucking xbox out the window now it wont connect to my pc im going to take it back to walmart or something this is fucking gay
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: morpheous1777 on January 02, 2005, 02:13:00 PM
-
For windows xp users, if you need to create a file of a certain size and the file contents don't matter (Shadowc.img file), you can use the Fsutil command as follows:
opend command prompt:
fsutil file createnew <name of file> <size in bytes>
For example,
fsutil file createnew c:\shadowc.img 209715200
this will create an exact 200 mb file named shadowc.img in C:
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: Dupli on January 05, 2005, 11:46:00 AM
-
Hey,
I like the shadow C option but I can't understand one little thing:
I've used the UXE exploit and hexed the fonts so everything is now on the C partition. Now, I replaced the pbloader with the nkpatcher and everything runs well until I use the shadow C function. It seems nkpatcher runs everything off the Virtual C because when I delete everything on the virtual C, it gets the error #21.
But when I boot the mechassault and loads the savegame hack, I see all the files on the REAL C. This confuses me because I thought that the nkpatcher should boot the files on the REAL C instead of the VIRTUAL C ?
Greetz
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: PedrosPad on January 05, 2005, 12:07:00 PM
-
Power up with no original game disk in DVD-Rom drive:
HDD boots->C:\xboxdash.xbe runs->fonts exploit->NKPatcher runs->NKPatcher mounts Virtual C drive, etc., etc.
Power up with original MA game in DVD-Rom drive:
MA's D:\default.xbe runs->GameSav loads->Evox appears and FTPing shows real C' drive.
(Note how NKPatcher didn't feature at all in the above line.)
Hopefully a bit clearer now.
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: BlackWar on January 05, 2005, 01:08:00 PM
-
nope, pedro is 110% correct. the exploit (fonts/nkpatcher) gets loaded before anything else (evox, mediacenter, dashboards, ect).
Only by booting retail games do you bypass everything (and I mean everything).
The whole point to the shadow C: is for game compatibility, thats about it. only a handfull of retail games (the two games on one disk), require this. If you dont have these games, then the shadow c option is not really needed, but one hell of a cool feature to have implimented.
my question is.... can the shadow drive exist someplace other then e:? say like on F:? I want to keep my E: partition as neat and clean as possable, and have all of my dashboards and stuff stored on F:.
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: total_ass on January 05, 2005, 01:12:00 PM
-
the shadow drive can be stored wherever i believe. many peope store it on the actual C drive
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: total_ass on January 05, 2005, 01:54:00 PM
-
can i just confirm that
partition0 = C
partition1 = D
partition2 = E
partition3 = X
partition4 = Y
partition5 = Z
partition6 = F
partition7 = G
can someone just tell me thats right.
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: chimpanzee on January 05, 2005, 01:58:00 PM
-
1 = E
2 = C
3 = D
If memory serve.
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: YoshiKool on January 05, 2005, 02:01:00 PM
-
D:\ is a partition?
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: total_ass on January 05, 2005, 02:08:00 PM
-
thanks.
ah yes perhaps not a partition as such.
but it must still have a device number assigned to it.
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: krayzie on January 05, 2005, 03:35:00 PM
-
Post by: morpheous1777 on January 02, 2005, 02:13:00 PM
opend command prompt:
fsutil file createnew <name of file> <size in bytes>
For example,
fsutil file createnew c:\shadowc.img 209715200
this will create an exact 200 mb file named shadowc.img in C:
Post by: Dupli on January 05, 2005, 11:46:00 AM
I like the shadow C option but I can't understand one little thing:
I've used the UXE exploit and hexed the fonts so everything is now on the C partition. Now, I replaced the pbloader with the nkpatcher and everything runs well until I use the shadow C function. It seems nkpatcher runs everything off the Virtual C because when I delete everything on the virtual C, it gets the error #21.
But when I boot the mechassault and loads the savegame hack, I see all the files on the REAL C. This confuses me because I thought that the nkpatcher should boot the files on the REAL C instead of the VIRTUAL C ?
Greetz
Post by: PedrosPad on January 05, 2005, 12:07:00 PM
QUOTE(Dupli @ Jan 5 2005, 08:17 PM)
I like the shadow C option but I can't understand one little thing:
I've used the UXE exploit and hexed the fonts so everything is now on the C partition. Now, I replaced the pbloader with the nkpatcher and everything runs well until I use the shadow C function. It seems nkpatcher runs everything off the Virtual C because when I delete everything on the virtual C, it gets the error #21.
But when I boot the mechassault and loads the savegame hack, I see all the files on the REAL C. This confuses me because I thought that the nkpatcher should boot the files on the REAL C instead of the VIRTUAL C ?
I've used the UXE exploit and hexed the fonts so everything is now on the C partition. Now, I replaced the pbloader with the nkpatcher and everything runs well until I use the shadow C function. It seems nkpatcher runs everything off the Virtual C because when I delete everything on the virtual C, it gets the error #21.
But when I boot the mechassault and loads the savegame hack, I see all the files on the REAL C. This confuses me because I thought that the nkpatcher should boot the files on the REAL C instead of the VIRTUAL C ?
Power up with no original game disk in DVD-Rom drive:
HDD boots->C:\xboxdash.xbe runs->fonts exploit->NKPatcher runs->NKPatcher mounts Virtual C drive, etc., etc.
Power up with original MA game in DVD-Rom drive:
MA's D:\default.xbe runs->GameSav loads->Evox appears and FTPing shows real C' drive.
(Note how NKPatcher didn't feature at all in the above line.)
Hopefully a bit clearer now.
Post by: BlackWar on January 05, 2005, 01:08:00 PM
Only by booting retail games do you bypass everything (and I mean everything).
The whole point to the shadow C: is for game compatibility, thats about it. only a handfull of retail games (the two games on one disk), require this. If you dont have these games, then the shadow c option is not really needed, but one hell of a cool feature to have implimented.
my question is.... can the shadow drive exist someplace other then e:? say like on F:? I want to keep my E: partition as neat and clean as possable, and have all of my dashboards and stuff stored on F:.
Post by: total_ass on January 05, 2005, 01:12:00 PM
Post by: total_ass on January 05, 2005, 01:54:00 PM
partition0 = C
partition1 = D
partition2 = E
partition3 = X
partition4 = Y
partition5 = Z
partition6 = F
partition7 = G
can someone just tell me thats right.
Post by: chimpanzee on January 05, 2005, 01:58:00 PM
2 = C
3 = D
If memory serve.
Post by: YoshiKool on January 05, 2005, 02:01:00 PM
Post by: total_ass on January 05, 2005, 02:08:00 PM
ah yes perhaps not a partition as such.
but it must still have a device number assigned to it.
Post by: krayzie on January 05, 2005, 03:35:00 PM
QUOTE(total_ass @ Jan 5 2005, 10:39 PM)
thanks.
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: krayzie on January 05, 2005, 03:42:00 PM
-
c= device\hardisk0\partition2
e=....................partition1
f=....................partition 6
g=....................partition 7
x=....................partition 3
y=....................partition 4
z=....................partition 5
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: DaddyJ on February 20, 2005, 03:04:00 PM
-
Post by: krayzie on January 05, 2005, 03:42:00 PM
e=....................partition1
f=....................partition 6
g=....................partition 7
x=....................partition 3
y=....................partition 4
z=....................partition 5
Post by: DaddyJ on February 20, 2005, 03:04:00 PM
QUOTE(dosfan @ Feb 20 2005, 05:02 PM)
(first post...deep breaths)
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: cmiz on February 20, 2005, 03:07:00 PM
-
well i guess you could finagle something like that to work...only problem is that in the process you'd lose the ability to change dash settings or run games....which i kind of enjoy doing every so often...interesting concept but it wouldn't really pan out
edit: damn, daddyj got there first....as for changing your eeprom to do that, i'm not personally a fan of that idea because if you screwed something up, you couldn't try to fix it by booting a retail game. oh well though, to each his own. and some people don't mind xboxhdm that much...
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: DaddyJ on February 20, 2005, 03:22:00 PM
-
My xbox cant boot an orignal game anyways
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: krayzie on February 20, 2005, 03:27:00 PM
-
Just again another clarification since people don't seem to get this part.
Games will NOT upgrade your dash or destroy your exploit when coldbooted.
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: DaddyJ on February 21, 2005, 11:20:00 AM
-
Post by: cmiz on February 20, 2005, 03:07:00 PM
edit: damn, daddyj got there first....as for changing your eeprom to do that, i'm not personally a fan of that idea because if you screwed something up, you couldn't try to fix it by booting a retail game. oh well though, to each his own. and some people don't mind xboxhdm that much...
Post by: DaddyJ on February 20, 2005, 03:22:00 PM
QUOTE(cmiz)
edit: damn, daddyj got there first....as for changing your eeprom to do that, i'm not personally a fan of that idea because if you screwed something up, you couldn't try to fix it by booting a retail game. oh well though, to each his own. and some people don't mind xboxhdm that much...
My xbox cant boot an orignal game anyways
Post by: krayzie on February 20, 2005, 03:27:00 PM
Games will NOT upgrade your dash or destroy your exploit when coldbooted.
Post by: DaddyJ on February 21, 2005, 11:20:00 AM
QUOTE(dosfan @ Feb 21 2005, 01:19 PM)
I personally think that should that really read:
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: cmiz on February 21, 2005, 11:25:00 AM
-
hehehe yeah i was just thinking...the last time they gave us fonts, they sorta got slammed
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: triggernum5 on February 26, 2005, 08:52:00 AM
-
It would work with evox, you are just creating the shell of your shadowc in an unconventional manner.. One you fill it up with the proper files it will be just like any other shadowc..
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: Olipro on February 26, 2005, 12:56:00 PM
-
if they MD5'd it, then it would still be possible to root out a collision for it, so it'd only act as a delay, and for MD5, that shouldn't take an amazingly long time, whereas SHA-1 would really be a pain in the butt.
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: Ghengis on March 03, 2005, 08:05:00 PM
-
As if this thread wasn't long enough...
Anyway, it doesn't seem to have been updated for release 10, which seems to be current. I was going to humbly suggest that future releases look to e:\evoxdash.xbe instead of c:\evoxdash.xbe, because that would allow you to make your shadow C drive 100% pristine. As it stands, evox is loaded AFTER the shadow C is mounted, which means it loads evox from the image, not the actual drive. Or have I got something wrong here?
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: cmiz on March 04, 2005, 12:22:00 AM
-
Post by: cmiz on February 21, 2005, 11:25:00 AM
Post by: triggernum5 on February 26, 2005, 08:52:00 AM
Post by: Olipro on February 26, 2005, 12:56:00 PM
Post by: Ghengis on March 03, 2005, 08:05:00 PM
Anyway, it doesn't seem to have been updated for release 10, which seems to be current. I was going to humbly suggest that future releases look to e:\evoxdash.xbe instead of c:\evoxdash.xbe, because that would allow you to make your shadow C drive 100% pristine. As it stands, evox is loaded AFTER the shadow C is mounted, which means it loads evox from the image, not the actual drive. Or have I got something wrong here?
Post by: cmiz on March 04, 2005, 12:22:00 AM
QUOTE(Ghengis @ Mar 4 2005, 03:11 AM)
As if this thread wasn't long enough...
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: krayzie on March 04, 2005, 03:32:00 PM
-
Well it's supose to write to the actual eeprom. i tested this with the regular configmagic. Altough some weeks ago i changed regions with configmagic 1.6 and it only wrote to the virtual eeprom.
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: stoatie_weasel on March 05, 2005, 03:02:00 PM
-
Ok, I can confirm that configmagic v1.6 does write to the virtual eeprom and not the actual eeprom.
Didn't feel the need to test the original version of configmagic.
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: nprice on March 12, 2005, 06:25:00 PM
-
Just to clarify, can I use the driveimageutils 1.0.1 apps with nkpatcher 10? Nkpatcher's readme says:
I'm not quite understanding this... can someone explain?
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: krayzie on March 13, 2005, 12:31:00 AM
-
Post by: krayzie on March 04, 2005, 03:32:00 PM
Post by: stoatie_weasel on March 05, 2005, 03:02:00 PM
Didn't feel the need to test the original version of configmagic.
Post by: nprice on March 12, 2005, 06:25:00 PM
QUOTE
From version 8.1 to version 9:
* oz_paulb LBA48 and partition table support
* Virtual C image may now be of any size. You can make a virtual drive from
scratch by first creating a file (or copying any old), say 200 MB, and then
formatting it. You can for example virtualize the F with the unformatted image
first and then format F using Evox dashboard. Then copy stuff to F and then
use the done image file to virtualize C. The number at the end of
VIRTUAL_C_DRIVE option can be used to select any existing drive for
virtualizing. I'm sure there are also Linux tools for creating a FATX file
system inside a given file.
* oz_paulb LBA48 and partition table support
* Virtual C image may now be of any size. You can make a virtual drive from
scratch by first creating a file (or copying any old), say 200 MB, and then
formatting it. You can for example virtualize the F with the unformatted image
first and then format F using Evox dashboard. Then copy stuff to F and then
use the done image file to virtualize C. The number at the end of
VIRTUAL_C_DRIVE option can be used to select any existing drive for
virtualizing. I'm sure there are also Linux tools for creating a FATX file
system inside a given file.
I'm not quite understanding this... can someone explain?
Post by: krayzie on March 13, 2005, 12:31:00 AM
QUOTE(nprice @ Mar 13 2005, 01:31 AM)
Just to clarify, can I use the driveimageutils 1.0.1 apps with nkpatcher 10? Nkpatcher's readme says:
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on March 19, 2005, 12:33:00 PM
-
well if 137gig is FFFFFFF (dec 268435455)
and you want 60gig F:\ then set size to 60+8 (8=C:\,E X Y Z)
(68/137)*268435455=133238036 or 0x07f10d14
that should get you close...
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: DaddyJ on March 20, 2005, 08:42:00 AM
-
may I ask why?
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: dvanbrunt on March 21, 2005, 07:24:00 PM
-
Also, if anyone ones what to do with the default.xbe file once created I'm all ears. I have now made compiled the new one but am a bit lost as where to go from here to get it to repartition the drive.
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on March 22, 2005, 11:01:00 AM
-
Post by: xman954 on March 19, 2005, 12:33:00 PM
and you want 60gig F:\ then set size to 60+8 (8=C:\,E X Y Z)
(68/137)*268435455=133238036 or 0x07f10d14
that should get you close...
Post by: DaddyJ on March 20, 2005, 08:42:00 AM
QUOTE(dvanbrunt @ Mar 19 2005, 12:46 PM)
I want to know the process so I can convert my 80GB HD F to only be 60GB.
may I ask why?
Post by: dvanbrunt on March 21, 2005, 07:24:00 PM
Post by: xman954 on March 22, 2005, 11:01:00 AM
QUOTE(dvanbrunt @ Mar 21 2005, 08:30 PM)
Also, if anyone knows what to do with the default.xbe file once created I'm all ears. I have now made compiled the new one but am a bit lost as where to go from here to get it to repartition the drive.
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: dosfan on April 06, 2005, 03:04:00 AM
-
From a cold boot? the answer is no:
D:\default.xbe would be executed BEFORE nkpatcher would have a chance to kick in. (I assume you are softmodded, UXE?)
Launching an original disc after nkpatcher would keep the partition hidden, but that doesn't make it safe to XBL. Kernel memory has still been modified...but you probably already knew that.
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: SilentBob1638 on April 17, 2005, 09:41:00 AM
-
Any plans for next nkpatcher to support mounting Files/IMG/ISOs over SMB share? Would be handy for ppl with stock drives...
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: PedrosPad on April 20, 2005, 03:54:00 AM
-
In response to requests for NKP to be updated I thought reiterate (and support) rmenhalÂ’s belief that NKP should not turn monolithic - let's keep it a focused BIOS patcher! (It's good to read RiceCake's boot chain article at this point.) Many of the requested features already have workable solutions. I thought it useful to gather together the existing NKP workarounds I'd seen, before inviting ideas for further NKP development.
Existing NKPatcher workaround/solutions:
Retail BIOS->MS's update.xbe->font exploit->NKP->[whatever you like]->aftermarket dashboard!
Any other requirements?
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: PedrosPad on April 20, 2005, 10:51:00 AM
-
Post by: dosfan on April 06, 2005, 03:04:00 AM
D:\default.xbe would be executed BEFORE nkpatcher would have a chance to kick in. (I assume you are softmodded, UXE?)
Launching an original disc after nkpatcher would keep the partition hidden, but that doesn't make it safe to XBL. Kernel memory has still been modified...but you probably already knew that.
Post by: SilentBob1638 on April 17, 2005, 09:41:00 AM
Post by: PedrosPad on April 20, 2005, 03:54:00 AM
Existing NKPatcher workaround/solutions:
- "multiple boot paths" - You can do this already by simply inserting the "External tray-state branching utilities" into the boot chain! (the source is included should this need tailoring!).
- LED support? - don't most aftermarket dashboards now support this? (I guess Evox doesn't, but that's not been supported for a while and is getting a bit long-in-the-tooth now anyway).
- Screenshots With Nkpatcher.
- nkpatcher to set xbox to output vga signal
Retail BIOS->MS's update.xbe->font exploit->NKP->[whatever you like]->aftermarket dashboard!
Any other requirements?
Post by: PedrosPad on April 20, 2005, 10:51:00 AM
QUOTE(PedrosPad @ Apr 20 2005, 10:00 AM)
I thought it useful to gather together the existing NKP workarounds I'd seen, before inviting ideas for further NKP development.
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: Dolfhin on April 20, 2005, 11:08:00 AM
-
Post by: Dolfhin on April 20, 2005, 11:08:00 AM
QUOTE(PedrosPad @ Apr 20 2005, 04:57 PM)
Suggestions just in:
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: cmiz on April 20, 2005, 10:53:00 PM -
@pedrospas: those are some good work arounds, though i already knew about most of them. for the boot list, i'm not really buying the tray state booting as an alternative to it.
i'm not a huge fan of having to remember to boot with the right tray state and such...it would be more for an issue where you could have a backup dash in case you tried to modify the default one and messed up (mostly so we don't have to keep dealing with newbies doing that...)
for the leds, i was thinking more of a "warning: mod on" type thing. though you can change LED's with most dashes, if you cold booted a backup game, it would never load the dash...(unless you have nkpatcher set to only boot dash.
for the fan speed...does the dash fan setting carry over once you leave the dash? i've never actually checked. (again...setting nkpatcher to only boot dash would make sure the fan was set to whatever).
again though, i'm perfectly happy with what we HAVE....if somebody got bored and felt like adding some of those things, then it could possibly be BETTER...but i'm not complaining! -
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: SupaSaru on April 27, 2005, 06:01:00 AM -
cmiz, I wrote an UnleashX script for a buddy that insisted on fooling around in C. It just copied e:\mod\backup to C:\, and I used dual-habibi to let him launch it without a gamesave.
LEDs and Fan settings stay until you cold boot.
Add that stuff yourself if you dub nkpatcher not "good enough".
I've got a dirty hack to add dual-boot to nkpatcher. Requires you know how to cut and paste and reassemble it (possibly do some debugging, too, if I forget something).
I was debating on adding lights to it, also... I wanted to have a way to know whether or not I've loaded a shadowC/shadowEEPROM, and I figured the lights were the easiest way (one advantage to using nkpatcher to change the LED rather than UnleashX, etc). Really not that useful overall, if you think about it.
Also started working on a way to check for an e:\shadow[on,off] so I had an easy way to enable/disable shadowing without re-assembling/updating nkp. Again, not too useful to the end user.
Of course, the simple alternative to all of the above would be to assemble 2 versions of nkp, use the dual-habibi, and remember something like tray-open == no shadow, tray open == shadow... that would be too easy....
Overall, much love for nkp.
Also, couple questions for you guys....
1) Do you know of anyone making an xbox emulator? Not for the games, but just so we have an easy dev area for things like nkp.
2) Does anyone know offhand if Structured Exception Handling works on the xbox?
3) Sorry, but the xbox-scene v3 skin is hideous.
4) Where do the assembly geeks hang out now that xbdev is gone? Last I remember, that place was doing great, but now it's gone.....
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: TheMasterChef on April 29, 2005, 01:52:00 PM -
This thing patches the BIOS to a modified BIOS (not EvoX or anything) right?
Alternative to PBL+EvoX, right?
Could you use this to get a 1.6 on a modded BIOS then install EvoX over it? -
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: Flame2k on April 29, 2005, 01:56:00 PM - yes it will modify the xbox kernel and allow you to run non m$ code from your hard drive (eg evox)
-
Title: Reintroducing Kernel Patching - Nkpatcher
Post by: cmiz on April 29, 2005, 02:14:00 PM -
QUOTE(SupaSaru @ Apr 27 2005, 06:07 AM)Add that stuff yourself if you dub nkpatcher not "good enough".
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: TheMasterChef on April 29, 2005, 04:59:00 PM- Looks to me like I'm confused. Is the kernel stored on the BIOS or the dashboard? Doesn't look like you're talking about the XBOX OS, that could be done through FTP from EvoX, right..?
(Semi-n00b question indeed.)- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: cmiz on April 29, 2005, 05:08:00 PM- the kernel is the bios....dashboard version is just the "OS" that runs. you can change the dashboard version by putting different files onto your C drive whereas changing the bios requires soldering the write enable points and flashing (on a <1.6) and your only option for a 1.6 is bypassing the TSOP with a chip.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: TheMasterChef on April 30, 2005, 08:03:00 AM- "changing the bios requires soldering the write enable points and flashing (on a <1.6)"
Having to solder to change the BIOS on a <1.6? Softmodding doesn't need that.- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: kingroach on April 30, 2005, 08:12:00 AM- you dont change bios with softmod.. when xbox loads, it loads the retail bios, then exploit runs and bios loader (PBL) /kernel patcher (NKP) loads bios on the memory. and the xbox os you talk about is the "dash".. there is several version of"dash"..the latest version is 5659.03.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: TheMasterChef on April 30, 2005, 10:07:00 AM- "modified Windows kernel" -NT, I believe.
So the safest way to run a backup would be to get EvoX through a savegame exploit then run a game from there, without changing the dashboard on the XBOX's hdd, right? Wouldn't this method be better for a lot of people (namely 'Live users)?
So when a softmodded XBOX boots, it runs a signed modified dashboard...? Thought that wasn't possible...- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: cmiz on April 30, 2005, 10:32:00 AMQUOTE(TheMasterChef @ Apr 30 2005, 10:13 AM)"modified Windows kernel" -NT, I believe.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: SupaSaru on April 30, 2005, 04:15:00 PM
When a modded Xbox boots, it runs a signed *normal* MS dashboard. The fonts then overflow it, and modify the copy loaded in RAM. So launching an unmodified, signed executable is, of course, legal. The patching comes later.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: Flame2k on May 01, 2005, 05:18:00 AMQUOTE(SupaSaru @ Apr 30 2005, 10:21 PM)I thought it was W98? Ah well, either way, anything above 95 has NT internals.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: Olipro on May 01, 2005, 08:06:00 AM
it's not a good choice for the Xbox.
with regard to that little hack, I'd be interested in the code for that...
have you imbedded it inside of one of the macros already there, or created a separate one for it and then referenced it for each kernel version?- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: TheMasterChef on May 01, 2005, 08:16:00 AM- I think anything up to and including NT was DOS based.
So it works by modding the parts that don't need to be signed? Got it.
And the type of exploit you use is what doesn't-have-to-be-signed file you mod, right? (Eg you use a fonts mod you mod the fonts file that doesn't have to be signed.)- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: TheMasterChef on May 01, 2005, 08:17:00 AM- I think anything up to and including NT was DOS based.
So it works by modding the parts that don't need to be signed? Got it.
And the type of exploit you use is what doesn't-have-to-be-signed file you mod, right? (Eg you use a fonts mod you mod the fonts file that doesn't have to be signed.)- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: TheMasterChef on May 01, 2005, 04:29:00 PM- "rewriting the very thing that requires signing"
"that XBE must be habibi signed since that is the sig that matches the public key injected into the BIOS in memory", so it's been signed?
"that XBE must be habibi signed since that is the sig that matches the public key", mind me saying that really wasn't very clear.- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: SupaSaru on May 02, 2005, 10:23:00 AMQUOTE(Olipro @ May 1 2005, 09:12 AM)with regard to that little hack, I'd be interested in the code for that...
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: TheMasterChef on May 03, 2005, 03:18:00 PM- Just been reading this thread. Don't get when RSA is used... habibi is easily cracked, and the modded fonts get it to crash and only check for habibi, does it not check the fonts file for an RSA signature..?
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: PedrosPad on May 03, 2005, 03:29:00 PMQUOTE(TheMasterChef @ May 3 2005, 09:24 PM)Just been reading this thread. Don't get when RSA is used... habibi is easily cracked, and the modded fonts get it to crash and only check for habibi, does it not check the fonts file for an RSA signature..?
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: SupaSaru on May 04, 2005, 04:27:00 AMQUOTE(Olipro @ May 3 2005, 05:50 PM)I'm still interested in that multi-dash code, I've written my own add-in now for setting the colour of the front LED, so that's less of an interest now
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: SupaSaru on May 04, 2005, 01:46:00 PM- I'm done.
nkpatcher10+Saru --
Dual Boot
LED Color
+LED color for both dash and alternate
Someone tell me where I'm supposed to send this to get it tested and distroed.- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: SupaSaru on May 04, 2005, 03:35:00 PM- http://jupiter.walag...aru/6557039.zip
nkp10+Supa
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: slrhsapple on May 04, 2005, 05:09:00 PM- GREAT JOB MAN. Tested the dual boot & led w/virtualc &eeprom etc... and it works great. I noticed an error in the comment in config file.
";;; Cheat sheet: Red = 0x0f, Green = 0xf0, Orange = 0xff"
it should be
0x0f = green and 0xf0 is red
btw, how does your blinking system works? you noted,
;;; 0xf = Constant on, 1,2,4 or 8 blinks.
;;; 0x24 = Alternating off, red, green.
;;; 0x22 = Blinking orange.
ps. for people who want to use the bat to compile and sign your nkpatcher, you need xbedump.exe & nasmw.exe in your src folder- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: SupaSaru on May 04, 2005, 06:09:00 PMQUOTE(slrhsapple @ May 4 2005, 06:15 PM)GREAT JOB MAN. Tested the dual boot & led w/virtualc &eeprom etc... and it works great. I noticed an error in the comment in config file.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: h1jack3r on May 31, 2005, 11:32:00 AM- Hi,
I have a problem (excuse me for the english but i'm italian)
I have an xbox modded with a homebrew chip Enigmah 29wires, i have also in the same xbox the PBL 1.4 but that don't work like i would.
Can i install NKpatcher without take apart the Enigmah chip?
Thank you for the informations..- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: cRACKmONKEY421 on November 13, 2005, 06:23:00 AM- Apparently my friend has a magic xbox or something.. I used a Mech Assult software exploit from a Ndure installer and all worked well except eject fix and xbox live protection. So I thought I'd try PBL-lite along with the iND BFM bios which boasts both those features. Eject fix didn't work, of course. So I thought I'd try the next method that had an eject fix. I copied over nkpatcher10 and ran it after automatically running PBL-lite and whatever bios loader Ndure runs. I hit eject and it rebooted
. So then I checked the config.inc and took the semicolon out of "%define EJECT_FIX". Too bad I didn't know that was just part of the source code at the time, but apparently neither did the xbox. I ran nkpatcher after that and I was able to eject and put in a burned game; it played well. All this from a save game exploit. I rebooted and tested it a bunch. So I came home and tried to recreate the same thing with my modchip turned off. I can't get the eject fix to work just like everyone else. I actually broke his installation with a bad link, but tomorrow im going to fix it and hopefully get everything running. I'll copy all the files needed and post my results if anything good comes of it.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: krayzie on November 13, 2005, 08:10:00 AM- what exactly did you use and what exactly was the problem? it is normal the xbox resets when a game is in the drive and you eject it.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: aliasfallen on April 05, 2006, 10:32:00 PM- Hi everyone,
Here is a real noob question. How do you make it so that the NKPatcher10 file looks for a dashboard other than the default dashboard. I have XBMC and the dashboard is in E:\DASHBOARD and I think the NKPatcher is looking for C:\evoxdash.xbe
I tried changing the config.inc file with no luck but realize I may have set the parameter wrong. I typed in:
%define DASHBOARD_PATH '\Device\Harddisk0\Partition3\Dashboard\default.xbe'
I figured Partition3 was equal to the E drive.
Thanks!- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: jonels on April 06, 2006, 04:19:00 AMQUOTE(aliasfallen @ Apr 6 2006, 05:39 AM)
Hi everyone,
Here is a real noob question. How do you make it so that the NKPatcher10 file looks for a dashboard other than the default dashboard. I have XBMC and the dashboard is in E:\DASHBOARD and I think the NKPatcher is looking for C:\evoxdash.xbe
I tried changing the config.inc file with no luck but realize I may have set the parameter wrong. I typed in:
%define DASHBOARD_PATH '\Device\Harddisk0\Partition3\Dashboard\default.xbe'
I figured Partition3 was equal to the E drive.
Thanks!
almost mate.. partition1 is the e: partition... also don't forget to habibi sign you're new nkpatcher with xbedump.
edit.. make sure the rest of the config.inc is setup correctly, for instance, enable lba48 and chose the correct HD layout f: only or f: and g: .Check the paths for the virtual eeprom and virtual c: drive also match the setup you have or adjust accordingly. All the options in the config.inc file are explained pretty well within the files comments.- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: aliasfallen on April 06, 2006, 10:30:00 PM- jonels -
thank you sir. it works beautifully. how on earth they came up with partition 1 for e drive i will never know but it works.
just curious, why do you need a virtual c drive and virtual eeprom?- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: jonels on April 07, 2006, 04:56:00 AM- Shadowc was developed to protect the exploit files... xbox boots up, unlocks drive, runs the exploit files on c: , which runs Nkpatcher, which hides the c: drive with the exploit files and nkpatcher itself and replaces it with a shadowc. This means that when pesky little brother comes along and formats all the drives, the real c: is hidden and untouchable, so when you boot up the exploit still works but will error21 when no dash is found, so all you have to do to recover is boot a backup disc with a dash on to recover, so you can restore the dash (usually e:\dash or e:\dashboard).
In the same way the virtual eeprom protects the real eeprom... run enigma video selector with no worries.
Note if the shadowc/eeprom file paths are set to be hidden on the real c: partiton 2 (example.. c:\shadowc\shadowc.img) then the real c: must be assigned a diferent partiton; partition 8 is used, this can't be accesed by the user but nkpatcher can to load the image file.
%define VIRTUAL_C_DRIVE 2
%define ACTUAL_C_DRIVE 8
%define VIRTUAL_C_PATH '\Device\Harddisk0\Partition8\shadowc\shadowc.img'- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: A Murder of Crows on May 09, 2006, 04:52:00 AM- Ran into my 2nd major issue with nkpatcher today.
I have a 128mb upgraded box for use with emulation. I run an X3 chip for LCD support, but mostly use Krayzie's NDure 1.1.1 for everything.
I found out today that it is very possible that the softmod can't see the 128mb of ram, and therefore can't tell other programs its there.
THis happened in StepmaniaX. I used the mod chip most of the day to get some troublesome songs installed. Stepmania would freeze whenever it attempted to load these particular songs up with the mod chip enabled.
i then used the soft mod and it worked fine!!!
this was peculiar to say the least, so i worked hard at figuring out what was causing the crash....turned out it was some banner files saved as jpeg instead of png....resaved as png and stepmania could finally load.
i found this out while looking at the log, which i could only get when i used the soft mod or removed the songs. One thing i noticed was that the amount of ram i had when the chip was engaged was 128mb, but when using the soft mod i only got 64mb.
i figure that, for some reason, having 64mb allows the system to load the jpeg banner files....and running 128 causes the jpegs to hang the app. this has to be dealt with by Xport, but in the mean time, why didn't my softmod recognize all of my ram? is this something NKPatcher can take care of?- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: ugenn on July 17, 2006, 04:19:00 AM- Where can I find the source for NKPatcher 11 U2
(or whatever the latest is)?- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: kingroach on July 17, 2006, 06:08:00 AM
http://www.esnips.com/web/kingroach/
NKPatcher11_U02.zip is the latest release by xman954, NKPatcher11_U02_vga7K.rar patched by me with latest vga patch by Dr. oldschool and modified to used with my installer, NKPatcher11_U02_vga7.zip is plain xman954's release+vga patch.- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on July 24, 2006, 10:06:00 AM- here is the latest version with some changes/fixes
QUOTE--------------------
changes
--------------------
From version version 11-U02 to version 11-U03 (Unofficial)
* ADDED VGA 7 patch (Dr oldschool)
* FIXED LED mode for Green, it will now blink when open/close tray
* CHANGED location of config files to E:\NKP11\ (shadowC_off.bin, eeprom_off.bin, NKP11_config.bin)
* CHANGED clock check date to more current 7-7-2006 (use included ernie.xtf for NDURE only)
* REMOVED clock check from config file options
if you want it, you must put a copy of the MS xboxdash.xbe
in E:\NKP11\ as clock.xbe (E:\NKP11\clock.xbe)
http://www.esnips.com/web/Xman954QUOTENKPatcher11_U02_vga7.zip is plain xman954's release+vga patch.does not have vga7 patch
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: kingroach on July 24, 2006, 10:57:00 AM- xman.. does nkpatcher also checks clock if its in retail mode.. In last version there was two path for retail and modded mode..
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on July 24, 2006, 11:23:00 AMQUOTEbtw.. If clock setting is enabled with the file in the correct place, does nkpatcher check to see if the date is 7/7/2006 and then call clock.xbe if it exists ?yes (if before)QUOTEDoes this work on a simple Ndure setup where there is basically no M$ dash files on c: ? is the renamed clock.xbe all that is needed ... thanksno, the MS dash (clock.xbe) still needs support files
on C:\ but it will give a error, then you reboot and it will pass the clock check (must use the updated ernie.xtf)QUOTExman.. does nkpatcher also checks clock if its in retail mode.. In last version there was two path for retail and modded mode..NO, it could be if needed, never thought of that...- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on July 24, 2006, 05:35:00 PMQUOTEOn a side note.. couldn't the clock.xbe be a modified unleashx dash with just the clock setting available akin to how Krayzies gamesave installer works ?sure, then IGR- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: kingroach on July 24, 2006, 07:17:00 PM- is there any changes to nkp_top.asm file?
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: kingroach on July 24, 2006, 08:12:00 PM- that will depend on what kind of softmod you run ( esp. where is the bios file) and what is the path of your dashboard ( you need to edit dash path in config file)..
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on July 25, 2006, 08:30:00 PM- not sure if i can help with kingroach's 3.0
but i do know that version with the VGA7 patch
is not configurable with the run time config file, the bios.xbe must be replaced
some where in the NDTS folder there should be the one you need (maybe wait for kingroach to reply)
also there looks like there may be a need for a second runtime config file.
one that is used when booted with eject IE:
power button used, normal video output
eject button used, Progressive mode + SoG + any other runtime options set different.
or vice-versa
this would be a easy thing to do if it would serve any purpose...
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: jonels on July 26, 2006, 03:52:00 AM- edit...you may want to let Kingroach help on this as I'm not that familiar with the package. But this is what I think will sort it
The bios.xbe will be in the real c: so you will need to disable the virtual c: to do this here is a quote from the readme of the ndure3 version of nkpatcher..
* ADDED two global override functions
now there is a easy way to disable the shadowC and virtual EEPROM for making system changes.
just put any file named shadowC_off.bin and/or EEPROM_off.bin in the root of E:\
reboot and do what you need then delete or rename it.
... just replace the bios.xbe, it's somewhere on the real c: with the nkpatcher you want from the ndts folder, but you must re-name it bios.xbe as that's what ndure is set to boot. (bios.xbe is nkpatcher.xbe, just renamed for convinience)
delete/rename the shadowC_off.bin in e: afterwards to re-enable protection of you're softmod.- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: kingroach on July 26, 2006, 06:07:00 AM- download the nkpatcher11_U03 from here:
http://www.esnips.com/web/kingroach/
I configured it for ndure installer. Now, enable rgb in the config file and run make_nkp11.bat file and it will make the bios.xbe file.
Run E:\ndts\default.xbe and by ftp go to C:\bios\ folder and delete bios.xbe. Now copy the new bios.xbe you created to C:\bios\ folder.- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: kingroach on July 26, 2006, 10:44:00 AM- did you enable hd in ms dash?.. I dont know if this is necessery..
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: kingroach on July 26, 2006, 08:06:00 PM- I was wrong.. you dont need to enable hd, just enable 480pin xbox. Your xbox will show this option if you have a hd cable connected.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on July 27, 2006, 11:18:00 AMCODE--------------------
changes
--------------------
From version version 11-U02 to version 11-U03 (Unofficial)
* NOTE most options can be now turned on/off when using the runtime config file
* ADDED option for king boot mode NDURE 3.X
* ADDED option for a second runtime config file, one that is used for tray open (NKP11_config_open.bin
use the normal runtime config file and rename )
* CHANGED option for boot only to dash so that it can be configured in the runtime config (if used)
* ADDED VGA 7 patch (Dr oldschool)
* FIXED LED mode for Green, it will now blink when open/close tray
* CHANGED location of config files to E:\NKP11\ shadowC_off.bin, eeprom_off.bin, NKP11_config.bin
NKP11_config_open.bin, and boot1.bin (using king boot mode)
* CHANGED clock check date to more current 7-7-2006 (use included ernie.xtf for NDURE only)
it test the clock in tray open state now and if not set it will load E:\NKP11\clock.xbe (if found)
or the normal dash and set the LED to G,O,R,off to let you know the clock needs to be set
and it's in a modded state (set clock, do IGR and/or reboot to use normaly)
* REMOVED clock check from config file options
if you want it, you must put a copy of the MS xboxdash.xbe or other
in E:\NKP11\ as clock.xbe (E:\NKP11\clock.xbe)
--------------------- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: kingroach on July 27, 2006, 12:54:00 PMQUOTE(xman954 @ Jul 27 2006, 06:25 PM)
@ Kingroach
there is a new set of files with a lot of changes (WIP)
that now has a option for your King boot
everything is untested as of now, check it out
I
xman954 
. I will test it tonight..
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on August 04, 2006, 06:42:00 AM- when tray boot and king boot is enabled
when powered up with eject button it will look for E:\NKP11\boot1.bin (any file renamed to that)
if it is there it will boot the MS xonlinedash, if not the boots the MS xboxdash
(the dash files must be setup corectly first, C:\xb0xdash.xbe, C:\x2onlinedash.xbe)- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: Textbook on August 04, 2006, 08:28:00 AM- King boot sounds awesome. It's like an evolution of your tri-boot. Good job xman,
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on August 04, 2006, 09:08:00 AMQUOTEKing boot sounds awesomeit's mostly used for Kingroach's NDURE 3.X PC installer
anyone that wants to upgrade can use it (and the ernie.xtf)
then later on change things around using the runtime config file only
without having to mess with files on C:\
IE: single boot, dual boot to UX-XBMC and other combo's
tring to make NKP "universal" and fool proof
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: kingroach on August 05, 2006, 06:51:00 AMQUOTE(xman954 @ Aug 4 2006, 04:15 PM)
it's mostly used for Kingroach's NDURE 3.X PC installer
anyone that wants to upgrade can use it (and the ernie.xtf)
then later on change things around using the runtime config file only
without having to mess with files on C:\
IE: single boot, dual boot to UX-XBMC and other combo's
tring to make NKP "universal" and fool proof
is it possible to convert a dual boot nkpatcher to a single boot only with runtime file?..- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on August 05, 2006, 09:13:00 AMQUOTEis it possible to convert a dual boot nkpatcher to a single boot only with runtime file?..yes
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: quadriko on August 29, 2006, 11:41:00 AM- hi,
just wondering what that + 1 was next to the 7 on the Day entry was for. and wanted to know if editing the clock info in nkpatcher could harm anything aslong as it was a valid time/date. TIA
;--------------------------------------------------------------------------------------
mintime: dw 2006 ; Year
dw 7 ; Month
dw 7 + 1 ; Day
dw 0 ; Hour
dw 0 ; Minute
dw 15 ; Second
dw 0 ; Milliseconds
dw 0 ; Weekday (ignored)
;-------------------------------------------
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: PedrosPad on August 30, 2006, 01:47:00 AMQUOTE(quadriko @ Aug 29 2006, 06:48 PM)
hi,
just wondering what that + 1 was next to the 7 on the Day entry was for. and wanted to know if editing the clock info in nkpatcher could harm anything aslong as it was a valid time/date. TIA
;--------------------------------------------------------------------------------------
mintime: dw 2006 ; Year
dw 7 ; Month
dw 7 + 1 ; Day
dw 0 ; Hour
dw 0 ; Minute
dw 15 ; Second
dw 0 ; Milliseconds
dw 0 ; Weekday (ignored)
;-------------------------------------------
From http://msdn.MS.com/l...a04feff283e.asp but true of all M$ time functions:QUOTE
year
Required. The full year, for example, 1976 (and not 76).
month
Required. The month as an integer between 0 and 11 (January to December).
date
Required. The date as an integer between 1 and 31.
hours
Optional. Must be supplied if minutes is supplied. An integer from 0 to 23 (midnight to 11pm) that specifies the hour.
minutes
Optional. Must be supplied if seconds is supplied. An integer from 0 to 59 that specifies the minutes.
seconds
Optional. Must be supplied if milliseconds is supplied. An integer from 0 to 59 that specifies the seconds.
Notice how the date (aka. day-of-month) is '1'-based and only one that isn't zero based.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on August 30, 2006, 11:23:00 AMQUOTEand wanted to know if editing the clock info in nkpatcher could harm anything aslong as it was a valid time/date. TIAno problem there just, make sure you change the time in ernie.xtf to 15 sec before the time/date you chose (to avoid any posible clock problems by having missing files)
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: quadriko on September 09, 2006, 11:11:00 AM- tnx, i'm having problems right now with the time/date in my fonts and nkpatcher being out of sync. when it boots clock.xbe, and i set the time. after i reboot it just brings up clock.xbe agian and agian.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on September 09, 2006, 12:21:00 PM- did you press the A(green) after setting time and before IGR
is the time your setting before the time you changed NKP check time too..- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: Tp21 on September 10, 2006, 12:30:00 PM- how does the dual/tri boot works? (i know it's an noob question
).
in the config.inc are a lot of options for dual/tri boot, but from my view patchback and 'normal' dual boot are both enabled. can somebody explain it for me?- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on September 10, 2006, 12:54:00 PM- tri boot was used to boot a habibi signed disk with no other hacks to the kernal (just the public Key) if booted using eject with the disk allready in the drive (it closes the DVD tray) it's boots, otherwise boots
the alt dash
patchback is used to put back the orignal MS public Key so it will only run MS signed xbe's (kernal is unmoded at this point)
they have been used for XBL stuff in the past
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: Tp21 on September 10, 2006, 12:58:00 PMCODE
;;; tray boot enable (dual boot)
%define TRAY_BOOT
;;; tri-boot enable < dual is default, with tray_boot enabled
;%define TRI_BOOT
;;; close the tray when NOT tri-booting (faster booting then tri-boot)
;%define CLOSE_TRAY_ALLWAYS
;;;---------------------------------------------------------------------------
;;; default Dashboard path (and tray boot closed) 2=C 1=E 6=F 7=G
;;;---------------------------------------------------------------------------
%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dash\default.xbe'
%define DB_PATH2 '\Device\Harddisk0\Partition1\dashboard\default.xbe'
%define DB_PATH3 '\Device\Harddisk0\Partition6\dashboard\default.xbe'
;;;---------------------------------------------------------------------------
;;; Dashboard path's for tray OPEN dash when using dual/tri-boot
;;;---------------------------------------------------------------------------
;;; tray OPEN dash, when key IS NOT patched back (must be a habibi signed xbe
;;; and MUST be partition 1 or 2 when NOT using OPEN_DASH_WITH_NKP)
;;;
%define OPEN_PATH '\Device\Harddisk0\Partition1\dashboard\default.xbe'
;;; use this to enable all of NKP (disable to boot some other HACK)
%define OPEN_DASH_WITH_NKP
;;; use this to disable shadowC in open (alt) dash
;%define OPEN_DASH_shadowC_OFF
;;;---------------------------------------------------------------------------
;;; tray OPEN dash, when key IS patched back (must be a MS signed xbe)
;;; MUST BE PARTITION 1 or 2
;;;
%define PB_OPEN_PATH '\Device\Harddisk0\Partition2\xb0xdash.xbe'
;;; use this to patch back the MS key then boot PB_OPEN_PATH
%define PATCH_BACK_MS_KEY
it looks like patchback and opendash are enabled at the same time? or am i wrong here?- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on September 10, 2006, 09:29:00 PM- @tp 21
the order that the options are tested
1 TRAY_BOOT
if tray is open
2 TRI_BOOT
3 CLOSE_TRAY_ALLWAYS
4 PATCH_BACK_MS_KEY (if defined boots PB_OPEN_PATH )
5 OPEN_DASH_WITH_NKP
boot OPEN_PATH
so as you see it will boot the ms xboxdash (C:\xb0xdash.xbe)
sorry for the confusion- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: A Murder of Crows on September 22, 2006, 02:12:00 AM- xman
been trying to reach you regarding getting that program that will compare differences for 64mb/128mb rams boxes.
get back to me when you can.
thanx
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on September 22, 2006, 10:30:00 AM- Check sig
burn default.xbe to disk and cold boot with and without ram upgrade
(using the same bios that supports 128MB and same xbox version) output is E:\Kernal.bin
this is a good place to start but may not yield what is needed....but it needs to be done.
Winhex does good file compare and IDA pro is usefull to dissemble
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: A Murder of Crows on September 22, 2006, 01:23:00 PM- got it.
in order to get the same bios on both, i'll be using my x3. I've got NO CLUE if the 3924 bios is 128mb compatbile, beyond what i saw with my own eyes....
stepmania v12 would start up on my box, mod chip enabled, and state that it saw 128mb of ram. it would then crash.
running the same program with the mod chip disabled and krayzie's Ndure 1.1 running, it would see 64mb of ram, and then would work fine.
both were on the 128mb ram system.
if this is a good enough start, i'll get that output for you asap.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: Dolfhin on November 10, 2006, 09:25:00 AMQUOTE
;;; tray boot enable
;%define TRAY_BOOT
;;; tri-boot enable < dual is default, with tray_boot enabled
%define TRI_BOOT
;;; close the tray when NOT tri-booting (faster booting then tri-boot)
%define CLOSE_TRAY_ALLWAYSQUOTE
%define OPEN_PATH '\Device\Harddisk0\Partition1\Apps\XBMC\default.xbe'
;;; use this to enable all of NKP (disable to boot some other HACK)
%define OPEN_DASH_WITH_NKP
;;; use this to disable shadowC in open (alt) dash
;%define OPEN_DASH_shadowC_OFF
I then ran ''make_nkp11_with_listing.bat'' and copyd the default.xbe to C:\bios\bios.xbe overwriting the older xbe that was still in there. After a reboot I got the ''21'' error. My question is now? Is my bios.xbe not singed correctly? If so how do I sign it correctly? Is my config file wrong?
Entire Config file (config.inc) is here :QUOTE
%ifndef CONFIG_INC
%define CONFIG_INC
;;; --------------------------------
;;; Configuration file for NKPatcher 11
;;; --------------------------------
;;;---------------------------------------------------------------------------
;;; file name for NKPatcher11 to use at runtime (E:\NKP11\NKP11_config.bin)
%define CFG_FILE '\Device\Harddisk0\Partition1\NKP11\NKP11_config.bin'
%define CFG_FILE_OPEN '\Device\Harddisk0\Partition1\NKP11\NKP11_config_open.bin'
;;;---------------------------------------------------------------------------
;%define KINGROACH_VERSION ; NDURE 3.X <<<<<<<<<<<<<<<<<<<<<<<<<
;;;---------------------------------------------------------------------------
;;;
%define ORANGE 00FFh ; ----------------
%define ORANGE_BLINK 0077h ;
%define ORANGE_BLIP 0011h ;
%define RED 00F0h ; YOU CAN
%define RED_BLINK 0070h ; ADD YOUR
%define RED_BLIP 0010h ; OWN
%define GREEN 000Fh ;
%define GREEN_BLINK 0007h ;
%define GREEN_BLIP 0001h ;
%define CYCLE 00EBh ; R,O,G,O
%define CYCLE_BLINK 0063h ; R,O,G,Off
%define LED_OFF 0000h ; ----------------
;;;---------------------------------------------------------------------------
%define NKP_LED_COLOR ORANGE ; < CHANGE IT HERE
%define ALTDASH_LED_COLOR RED ; < CHANGE IT HERE
%define PATCHBACK_LED_COLOR GREEN ; < CHANGE IT HERE
%define TRIBOOT_LED_COLOR CYCLE_BLINK ; < CHANGE IT HERE
;;;---------------------------------------------------------------------------
;;; set fan speed with NKP modes only (if omitted then no fan speed change)
%define FAN_SPEED 35 ; < CHANGE IT HERE ( % fan speed / 2 ) 10-50 << changed !!!!
;;;---------------------------------------------------------------------------
;;; tray boot enable
;%define TRAY_BOOT
;;; tri-boot enable < dual is default, with tray_boot enabled
%define TRI_BOOT
;;; close the tray when NOT tri-booting (faster booting then tri-boot)
%define CLOSE_TRAY_ALLWAYS
;;;---------------------------------------------------------------------------
;;; default Dashboard path (and tray boot closed) 2=C 1=E 6=F 7=G
;;;---------------------------------------------------------------------------
%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dash\default.xbe'
%define DB_PATH2 '\Device\Harddisk0\Partition1\dashboard\default.xbe'
%define DB_PATH3 '\Device\Harddisk0\Partition6\dashboard\default.xbe'
;;;---------------------------------------------------------------------------
;;; Dashboard path's for tray OPEN dash when using dual/tri-boot
;;;---------------------------------------------------------------------------
;;; tray OPEN dash, when key IS NOT patched back (must be a habibi signed xbe
;;; and MUST be partition 1 or 2 when NOT using OPEN_DASH_WITH_NKP)
;;;
%define OPEN_PATH '\Device\Harddisk0\Partition1\Apps\XBMC\default.xbe'
;;; use this to enable all of NKP (disable to boot some other HACK)
%define OPEN_DASH_WITH_NKP
;;; use this to disable shadowC in open (alt) dash
;%define OPEN_DASH_shadowC_OFF
;;;---------------------------------------------------------------------------
;;; tray OPEN dash, when key IS patched back (must be a MS signed xbe)
;;; MUST BE PARTITION 1 or 2
;;;
%define PB_OPEN_PATH '\Device\Harddisk0\Partition2\xb0xdash.xbe'
;;; use this to patch back the MS key then boot PB_OPEN_PATH
%define PATCH_BACK_MS_KEY
;;;---------------------------------------------------------------------------
;;; VIDEO patches:
;;;
;;; VIDEO_FORCE_RGB = Patches kernel to output RGsB video signal (RGB with
;;; sync on green) if HDTV AV pack is detected. Intended for
;;; connecting the Xbox to VGA monitor. Connect AV pack Y output
;;; to monitor green input, Cr to monitor red input and Cb to
;;; monitor blue input. The monitor must support sync on green.
;;;
;;; VIDEO_FORCE_PROGRESSIVE = Patches kernel to convert 480i video modes to
;;; 480p if HDTV AV pack is detected. Note that when using HDTV AV
;;; pack, progressive scan video output will be forced even if 480p
;;; video support is disabled in msdash.
;;;
;;; Not enabled by default.
;%define VIDEO_FORCE_RGB
;%define VIDEO_FORCE_PROGRESSIVE
;;; Flicker Filter Patch (composite video only)
;;;
;;; When enabled any call to set the flicker filter value will be
;;; replaced by a call with the value FLICKER_FILTER_VALUE.
;;;
;;; Takes values in the range 0 (off) to 5 (max filter).
;;;
;;; Flicker filter patching is not enabled by default.
%define FLICKER_FILTER
%define FLICKER_FILTER_VALUE 1
;;; --------------------------------------------------------------------------
;;; Configuration for nkpatcher
;;; --------------------------------------------------------------------------
;;;
;;; Reset-on-eject behaviour:
;;;
;;; EJECT_FIX = Never reset on eject.
;;; CD_DVD_ALWAYS_ROE = Always reset on eject for CD/DVD loaded XBEs, never
;;; reset on eject for hard disk loaded XBEs.
;;;
;;; Default is to never reset on eject for hard disk loaded XBEs, but reset
;;; on eject CD/DVD loaded XBEs based on the ROE flag in the XBE header.
%define EJECT_FIX
; %define CD_DVD_ALWAYS_ROE
;;; Automatic game region settings:
;;;
;;; GAME_REGION_AUTO = Set game region automatically based on the game region
;;; field in XBE header. Since the header may have several
;;; regions enabled there's a choice to be made. First
;;; tried is the game region from EEPROM, then the primary
;;; through tertiary regions below.
;;; GAME_REGION_IGNORE_REAL = Ignore the region stored in EEPROM and only
;;; use primary through tertiary regions below.
;;;
;;; Default is to use only the game region stored in the EEPROM and not
;;; change it.
%define GAME_REGION_AUTO
; %define GAME_REGION_IGNORE_REAL
%ifdef GAME_REGION_AUTO
;;; Game regions:
;;;
;;; 1 = North America
;;; 2 = Japan
;;; 4 = Rest of world
%define GAME_REGION_PRIMARY 4
%define GAME_REGION_SECONDARY 1
%define GAME_REGION_TERTIARY 2
%endif ; GAME_REGION_AUTO
;;; In-Game Reset settings:
;;;
;;; IGR = Enable IGR code
;;;
;;; Button combinations:
;;; * triggers+back+start
;;; * triggers+back+black
;;; * triggers+start+black
;;;
;;; IGR_TO_DASHBOARD = Reset to dashboard, not DVD. Changed button combos:
;;; * triggers+back+start to dashboard
;;; * triggers+back+black to dashboard
;;; * triggers+start+black to first DVD, then dashboard
;;;
;;; IGR_FULL_REBOOT = Do a full reboot instead of the default quick reboot.
;;; Some games hang (Soul Calibur 2 during a match) with
;;; quick reboot.
;;;
;;; IGR_MASTER_PORT #port_number = Only allow IGR from pad port #port_number,
;;; where #port_number is 0-3 (0 the left-most
;;; port, 3 the right-most.)
;;;
;;; IGR is not enabled by default.
%define IGR
%define IGR_TO_DASHBOARD
; %define IGR_FULL_REBOOT
%define IGR_MASTER_PORT 0
;;; Xbox Live blocking:
;;;
;;; XBL_BLOCK = Enable blocking
;;;
;;; Blocking not enabled by default.
%define XBL_BLOCK
;;; Virtual/Shadow C drive:
;;;
;;; VIRTUAL_C_DRIVE #part_num = Enable virtual C drive. Access to the partition
;;; number #part_num will be redirected to file VIRTUAL_C_PATH,
;;; which must be an image of a raw FATX file system. Note that
;;; the usual C drive partition number is 2. However, you
;;; could replace any drive with a virtual drive. The feature
;;; name "virtual C" is thus a bit misleading, although there's
;;; not much point virtualizing any other drive.
;;;
;;; ACTUAL_C_DRIVE #part_num = Make the actual C drive appear as
;;; partition #part_num. This requires LBA48 patches
;;; enabled.
;;;
;;; Not enabled by default.
%define VIRTUAL_C_DRIVE 2
%define ACTUAL_C_DRIVE 8
%define VIRTUAL_C_PATH '\Device\Harddisk0\Partition8\shadowC\shadowc.img'
;;; Virtual CD/DVD drive:
;;;
;;; VIRTUAL_CDROM_DRIVE = Enable virtual C drive. This will create a virtual
;;; device \Device\CdRom1 and link it to \Device\CdRom0
;;; when an ISO image is attached to CdRom1 (through a system
;;; call.)
;;;
;;; Not enabled by default.
%define VIRTUAL_CDROM_DRIVE
;;; 48-bit Logical Block Addressing and partition table settings:
;;;
;;; LBA48 = Enable. Allows use of disk space beyond 137 GB. Only 32 bits are
;;; actually used so maximum used disk size is now 2 TB.
;;;
;;; PARTITION_METHOD #method_num = Select partitioning scheme,
;;; where #method_num is:
;;; 0, for only standard Xbox partitions i.e. no F or G drives
;;; 1, for partition 6 (F drive) takes rest of the drive (after standard)
;;; 2, for partition 6 takes up to 137 GB, partition 7 (G drive) rest
;;; 3, for partition 6 takes up to 137 GB, no partition 7
;;;
;;; Note that method 1 results in ".06 bios" and method 2 in ".67 bios".
;;;
;;; IGNORE_HD_PARTITION_TABLE = Don't use harddisk partition table even if it
;;; exists (on the first sector of the drive).
;;;
;;; LBA48 and partition table not enabled by default.
%define LBA48
;%define PARTITION_METHOD 0
;%define PARTITION_METHOD 1
%define PARTITION_METHOD 2
;%define PARTITION_METHOD 3
; %define IGNORE_HD_PARTITION_TABLE
;;; Virtual EEPROM settings:
;;;
;;; VIRTUAL_EEPROM = Enable. Access to the EEPROM through the kernel will be
;;; redirected to file VIRTUAL_EEPROM_PATH.
;;;
;;; ENABLE_REAL_EEPROM_WRITE = Enable writing to the real EEPROM.
;;; If the VIRTUAL_EEPROM_PATH file is not found nkpatcher (with
;;; VIRTUAL_EEPROM enabled) will default to using the real EEPROM,
;;; but writing disabled. If you want the writing enabled then
;;; use this option. The main purpose of having real writes
;;; disabled by default is that if you mistype the path in
;;; VIRTUAL_EEPROM_PATH then you might go messing with the real
;;; EEPROM thinking it was only the virtual.
;;;
;;; DISABLE_VIRTUAL_EEPROM_WRITE = Disable writing to the virtual EEPROM.
;;;
;;; Virtual EEPROM is disabled by default. Also note that normally you shouldn't
;;; define ENABLE_REAL_EEPROM_WRITE.
%define VIRTUAL_EEPROM
%define VIRTUAL_EEPROM_PATH '\Device\Harddisk0\Partition8\shadowC\eeprom.bin'
;%define DISABLE_VIRTUAL_EEPROM_WRITE
;%define ENABLE_REAL_EEPROM_WRITE
;;; nkpatcher Xbox application reboot behaviour after patching has been done:
;;;
;;; BOOT_DASH_ONLY = Don't boot DVD.
;;; NORMAL_BOOT_ALWAYS = Always boot first DVD then dashboard.
;;;
;;; default is to boot DVD first, unless doing IGR to dash.
%define BOOT_DASH_ONLY
;;; Patches inside INIT section (boot unlocked HDs etc.)
;;;
;;; INIT_SEC_PATCHES = enable
;;;
;;; Do NOT enable these for nkpatcher.xbe executed on the Xbox (will crash
;;; and/or weird behaviour.)
; %define INIT_SEC_PATCHES
;;; --------------------------------------------------------------------------
;;; Configuration end
;;; --------------------------------------------------------------------------
%endif ; CONFIG_INC
Thanks in advance!- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on November 10, 2006, 10:21:00 AMCODE;;;---------------------------------------------------------------------------
;;; tray boot enable
%define TRAY_BOOT
;;; tri-boot enable < dual is default, with tray_boot enabled
;;;%define TRI_BOOT
;;; close the tray when NOT tri-booting (faster booting then tri-boot)
%define CLOSE_TRAY_ALLWAYS
alsoCODE;;;---------------------------------------------------------------------------
;;; tray OPEN dash, when key IS patched back (must be a MS signed xbe)
;;; MUST BE PARTITION 1 or 2
;;;
%define PB_OPEN_PATH '\Device\Harddisk0\Partition2\xb0xdash.xbe'
;;; use this to patch back the MS key then boot PB_OPEN_PATH
;;;%define PATCH_BACK_MS_KEY
and don't useCODE;;; default is to boot DVD first, unless doing IGR to dash.
%define BOOT_DASH_ONLY
useCODE;;; default is to boot DVD first, unless doing IGR to dash.
;;;%define BOOT_DASH_ONLY
untill you know everything is working
also once everything is working it is simpler to use the runtime config file
just make sure to use the updated rtc.asm
but the way you had it it should have bootedCODE%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dash\default.xbe'
%define DB_PATH2 '\Device\Harddisk0\Partition1\dashboard\default.xbe'
%define DB_PATH3 '\Device\Harddisk0\Partition6\dashboard\default.xbe'
did the fan speed up then error21 ?????
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: Dolfhin on November 11, 2006, 11:31:00 AMQUOTE(xman954 @ Nov 10 2006, 06:28 PM)
it is signed when the bat file is ran
you did not change the ernie.xtf (the one from this pkg is for C:\bios\default.xbe)
in your config tray boot is not enabled
useCODE;;;---------------------------------------------------------------------------
;;; tray boot enable
%define TRAY_BOOT
;;; tri-boot enable < dual is default, with tray_boot enabled
;;;%define TRI_BOOT
;;; close the tray when NOT tri-booting (faster booting then tri-boot)
%define CLOSE_TRAY_ALLWAYS
alsoCODE;;;---------------------------------------------------------------------------
;;; tray OPEN dash, when key IS patched back (must be a MS signed xbe)
;;; MUST BE PARTITION 1 or 2
;;;
%define PB_OPEN_PATH '\Device\Harddisk0\Partition2\xb0xdash.xbe'
;;; use this to patch back the MS key then boot PB_OPEN_PATH
;;;%define PATCH_BACK_MS_KEY
and don't useCODE;;; default is to boot DVD first, unless doing IGR to dash.
%define BOOT_DASH_ONLY
useCODE;;; default is to boot DVD first, unless doing IGR to dash.
;;;%define BOOT_DASH_ONLY
untill you know everything is working
also once everything is working it is simpler to use the runtime config file
just make sure to use the updated rtc.asm
but the way you had it it should have bootedCODE%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dash\default.xbe'
%define DB_PATH2 '\Device\Harddisk0\Partition1\dashboard\default.xbe'
%define DB_PATH3 '\Device\Harddisk0\Partition6\dashboard\default.xbe'
did the fan speed up then error21 ?????
Thanks! I checked the dashboard (I still have XboxHDM on my PC so I can see what is where) and the dashboard is in the right location. That is no problem. I also fixed the dual boot thing. I guess I should have seen that error myself
I dont know if the fan did speed up, I would say it does but I cant really hear it clearly. Sorry for that.
The problem might be that I already have a runtime config file in E:\NKP11\NKP11_config.bin, the runtime file got made from config_runtime.inc , right? I couldn't really find any details about this in the configuration but my config_runtime.inc links to a non-existing path which would explain the error 21 I got. I only configured config.inc to my liking.
Where do I find the updated rtc.asm btw?
Time to get a few screwdrivers ready, It seems that I have some fixing to do.- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on November 12, 2006, 09:36:00 AM- you should have a rescue dash (evox) in the real C then it would have booted "C:\rescuedash\default.xbe"
but it still should boot a DVD when there is no dash to boot
the runtime config is not needed, used to change options from the way it was originally compiled
check sig for rtc.asm, the config you posted has flicker filter settings so it must be the WIP version- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: Dolfhin on November 13, 2006, 01:04:00 PMQUOTE(xman954 @ Nov 12 2006, 05:43 PM)
you should have a rescue dash (evox) in the real C then it would have booted "C:\rescuedash\default.xbe"
but it still should boot a DVD when there is no dash to boot
the runtime config is not needed, used to change options from the way it was originally compiled
check sig for rtc.asm, the config you posted has flicker filter settings so it must be the WIP version
That is true. I fixed the default dash, it boots XBMC now just fine
However it still doesnt boot UnleashX when I turn it on with tray boot enable. QUOTE
;;;---------------------------------------------------------------------------
%define ORANGE 00FFh ; ----------------
%define ORANGE_BLINK 0077h ;
%define ORANGE_BLIP 0011h ;
%define RED 00F0h ; YOU CAN
%define RED_BLINK 0070h ; ADD YOUR
%define RED_BLIP 0010h ; OWN
%define GREEN 000Fh ;
%define GREEN_BLINK 0007h ;
%define GREEN_BLIP 0001h ;
%define CYCLE 00EBh ; R,O,G,O
%define CYCLE_BLINK 0063h ; R,O,G,Off
%define LED_OFF 0000h ; ----------------
;;;---------------------------------------------------------------------------
%define NKP_LED_COLOR ORANGE ; < CHANGE IT HERE
%define ALTDASH_LED_COLOR RED ; < CHANGE IT HERE
%define PATCHBACK_LED_COLOR GREEN ; < CHANGE IT HERE
%define TRIBOOT_LED_COLOR CYCLE_BLINK ; < CHANGE IT HERE
;;;---------------------------------------------------------------------------
%define KINGROACH_VERSION ; NDURE 3.X <<<<<<<<<<<<<<<<<<<<<<<<<
;;;---------------------------------------------------------------------------
;;; set fan speed with NKP modes only (if omitted then no fan speed change)
%define FAN_SPEED 35 ; < CHANGE IT HERE ( % fan speed / 2 ) 10-50 << changed !!!!
;;;---------------------------------------------------------------------------
;;; tray boot enable
%define TRAY_BOOT
;;; tri-boot enable < dual is default, with tray_boot enabled
;%define TRI_BOOT
;;; close the tray when NOT tri-booting (faster booting then tri-boot)
%define CLOSE_TRAY_ALLWAYS
;;;---------------------------------------------------------------------------
;;; default Dashboard path (and tray boot closed) 2=C 1=E 6=F 7=G
;;;---------------------------------------------------------------------------
%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\apps\xbmc\default.xbe'
%define DB_PATH2 '\Device\Harddisk0\Partition2\shadowc\resc\default.xbe'
%define DB_PATH3 '\Device\Harddisk0\Partition1\UDATA\4d530017\62d648ebf155\default.xbe'
;;;---------------------------------------------------------------------------
;;; Dashboard path's for tray OPEN dash when using dual/tri-boot
;;;---------------------------------------------------------------------------
;;; tray OPEN dash, when key IS NOT patched back (must be a habibi signed xbe
;;; and MUST be partition 1 or 2 when NOT using OPEN_DASH_WITH_NKP)
;;;
%define OPEN_PATH '\Device\Harddisk0\Partition1\dash\default.xbe'
;;; use this to enable all of NKP (disable to boot some other HACK)
%define OPEN_DASH_WITH_NKP
;;; use this to disable shadowC in open (alt) dash
;%define OPEN_DASH_shadowC_OFF
;;;---------------------------------------------------------------------------
;;; tray OPEN dash, when key IS patched back (must be a MS signed xbe)
;;; MUST BE PARTITION 1 or 2
;;;
%define PB_OPEN_PATH '\Device\Harddisk0\Partition2\xb0xdash.xbe'
;;; use this to patch back the MS key then boot PB_OPEN_PATH
;%define PATCH_BACK_MS_KEY
;;;---------------------------------------------------------------------------
;;; VIDEO patches:
;;;
;;; VIDEO_FORCE_RGB = Patches kernel to output RGsB video signal (RGB with
;;; sync on green) if HDTV AV pack is detected. Intended for
;;; connecting the Xbox to VGA monitor. Connect AV pack Y output
;;; to monitor green input, Cr to monitor red input and Cb to
;;; monitor blue input. The monitor must support sync on green.
;;;
;;; VIDEO_FORCE_PROGRESSIVE = Patches kernel to convert 480i video modes to
;;; 480p if HDTV AV pack is detected. Note that when using HDTV AV
;;; pack, progressive scan video output will be forced even if 480p
;;; video support is disabled in msdash.
;;;
;;; Not enabled by default.
;%define VIDEO_FORCE_RGB
;%define VIDEO_FORCE_PROGRESSIVE
;;; Flicker Filter Patch (interlaced composite video only)
;;;
;;; When enabled any call to set the flicker filter value will be
;;; replaced by a call with the value FLICKER_FILTER_VALUE.
;;;
;;; Takes values in the range 0 (off) to 5 (max filter).
;;;
;;; Flicker filter patching is not enabled by default.
%define FLICKER_FILTER
%define FLICKER_FILTER_VALUE 1
;;;---------------------------------------------------------------------------
;;; used to boot the dash only
;;;
%define BOOT_DASH_ONLY
No obvious error, right? My dash is in the right place, I made sure of this.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: xman954 on November 13, 2006, 07:51:00 PMQUOTENo obvious error, right?well...CODE;;;---------------------------------------------------------------------------
%define KINGROACH_VERSION; NDURE 3.X <<<<<<<<<<<<<<<<<<<<<<<<<
;;;---------------------------------------------------------------------------
this is only for using boot1.bin to select MS online dash or MS dash
also at the end of NKP_top.asm
rescue dash paths need to be there...in case shadowC does not loadCODE;------------------------------
READ1: db '\Device\Harddisk0\Partition1\NKP11\boot1.bin',0,0
ee_fp: db '\Device\Harddisk0\Partition1\NKP11\EEPROM_off.bin',0,0
sc_fp: db '\Device\Harddisk0\Partition1\NKP11\shadowC_off.bin',0,0
clk_ph: db '\Device\Harddisk0\Partition1\NKP11\clock.xbe',0,0
;------------------------------
%ifdef BACKUP_DIR
eepromdirstr: db '\Device\Harddisk0\Partition',BACKUP_DRIVE,'\', BACKUP_DIR,'\', 0
eepromdir: dd $-eepromdirstr-1,0,0,0
eepromfilestr: db '\Device\Harddisk0\Partition',BACKUP_DRIVE,'\', BACKUP_DIR,'\', BACKUP_NAME, 0
%else
eepromfilestr: db '\Device\Harddisk0\Partition',BACKUP_DRIVE,'\', BACKUP_NAME, 0
%endif
eepromfile: dd $-eepromfilestr-1,0,0,0
;-------------------------------------------------------------------------------------------
%ifdef ACTUAL_C_DRIVE
%define ACD ACTUAL_C_DRIVE
%else
%define ACD 2
%endif
;-----------
rescuedash1: db '\Device\Harddisk0\Partition',ACD+030h,'\rescuedash\default.xbe',0,0
rescuedash2: db '\Device\Harddisk0\Partition2\rescuedash\default.xbe',0,0
;--------------------------------------------------------------------------------------------- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: kingroach on September 14, 2007, 10:03:00 AM- I dont think xboxhdm or any other distro has this fixed.. if you can please update the xboxhdm distro.. cause its main function is to create harddrive.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: dus on September 15, 2007, 06:14:00 AM- I belive the following patch would have the same effect as the patch above. It basically changes the end of file (EOF) constant to 0xffff (FAT16) alt. 0xffffffff (FAT32), used when creating files. The end of cluster (EOC) is left untouched because this is used when finding the end of the cluster list, which according to the normal FAT specification is anything between 0xfffffffe and 0xffffffff (32-bit).
(Disclaimer: I have NOT tested this. You might get lucky and it works.)CODE
--- kernel/include/linux/fatx_fs.h.~1.6.~ 2005-12-18 00:36:24.000000000 +0100
+++ kernel/include/linux/fatx_fs.h 2007-09-15 14:31:45.000000000 +0200
@@ -65,8 +65,8 @@
#define EOC_FAT16 0xFFF8 // end of chain marker
#define EOC_FAT32 0xFFFFFFF8 // end of chain marker
-#define EOF_FAT16 0xFFF8 // end of file marker
-#define EOF_FAT32 0xFFFFFFF8 // end of file marker
+#define EOF_FAT16 0xFFFF // end of file marker
+#define EOF_FAT32 0xFFFFFFFF // end of file marker
#define EOF_FAT(s) (FATX_SB(s)->fat_bits == 32 ? EOF_FAT32 : EOF_FAT16)
#define FATX_VALID_MODE (S_IFREG | S_IFDIR | S_IRWXU | S_IRWXG | S_IRWXO)- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: dus on September 15, 2007, 08:47:00 AM- Above I meant that EOC stands for end of chain.
In addition to this, according to the FAT specification, you should not consider the top 4 bits in the cluster number. In the xbox-linux file kernel/fs/fatx/cache.c, there is a next &= 0xffffffff, which I believe should be next &= 0x0fffffff.
This is quite amusingly stated in the linux-2.4.35.2 kernel (linux-2.4.35.2/fs/fat/cache.c):CODE[...]
next = CF_LE_L(((__u32 *) bh->b_data)[(first &
(sb->s_blocksize - 1)) >> 2]);
/* Fscking Microsoft marketing department. Their "32" is 28. */
next &= 0xfffffff;
[...]
Also, in the xbox-linux kernel kernel/fs/fatx/cache.c file the use of EOC_FAT32 and EOC_FAT16 misses the possibility of a bad cluster 0x?ffffff7 alt. 0xfff7. (Compare with the fat file of a linux-2.4.35.2 kernel.)
This just in case someone wants to do something about it.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: ldotsfan on March 23, 2008, 09:13:00 AMQUOTE(BitBasher @ Sep 15 2007, 04:30 AM)
It would be nice to update xboxhdm, but as far as I know, ldots never released the source code for it, and he hasn't been active on XS since mid 2005.
It's possible to fix all the patch files on xbox-linux, but that would still require everyone to grab the updated patches and rebuild their respective kernels. This may only be a problem with 2.4.xx kernels, as the code for the 2.6.xx kernels is different - I'm not 100% sure.
I just checked one box running Xebian 1.1.4 and it has the problem, and another box that was created using xboxhdm also has the problem. I'm not sure if Gentoox has this problem or not.
Bit.
I've used Xebian 1.1.4 as my development environment (running on vmware) and used the CVS copy of the 2.4.32 kernel from xbox-linux to fix this FATX bug. So xboxhdm can be updated and I've done it. My testing consists of running the version on vmware. I've dumped some files on it from my desktop's c drive and doing some file operations but of course this is not really a thorough test.
Actually the bulk of xboxhdm's meat is a list of shell scripts written by ldots and are self-documentary. Now the issue is how to test the new version of xboxhdm. Just three files in the isolinux folder need to be replaced. Any volunteers to test? Alternatively can somebody point out how I can cross-check the files created by MS kernel vs xboxhdm ?
Also is it useful to release a version of xboxhdm that can access shared folders on a remote windows machine and USB storage devices and add some scripts to ease access to these folders from Midnight Commander (like what ldots did for the xbrowser script)?
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: kingroach on March 23, 2008, 06:27:00 PM- I can put on some time if needed.. booting from usb shouldnt be a problem.. you just need to update the scrips a bit.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: ldotsfan on March 24, 2008, 06:50:00 AM- Thanks the link has been sent to you.
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: kingroach on March 24, 2008, 11:03:00 AM- I got it.. I will look into it asap..
- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: ldotsfan on March 28, 2008, 06:03:00 PM- I already used the kernel to rebuild/upgrade one xbox HD and so far it's not complaining yet (no obvious file corruption). Another issue is it seems a very common PC hardware configuration comes with only 1 IDE port and the rest are all SATA. I've tested this kernel with xboxhdm on vmware with only 1 IDE enabled and apart from the obvious function (cloning), the rest of the functions don't seem to be tied to secondary master for CD.
So it might be a good idea to upgrade xboxhdm to support CD on primary slave for all functions except cloning so that modern PCs are properly supported.- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: ldotsfan on April 21, 2008, 08:30:00 PM- @kingroach : Did you had the chance to do any testing on the FATX bugfix?
The USB flashdrive booting is working. Hotswapping from USB/IDE adapter should work too. Now in this test version, there's no need to reboot between building the xbox hdd (option 1,2) and locking it(option 3). No restrictions on the physical IDE connection - now it can be primary/secondary master/slave. And cloning should be faster since it's a newer kernel - in theory. I hope to include 32k/64k cluster size support as well. But I'm still working on the last feature.- Title: Reintroducing Kernel Patching - Nkpatcher
Post by: ldotsfan on April 22, 2008, 08:10:00 AMQUOTE(obcd @ Apr 22 2008, 04:35 PM)
I don't want to slow down your enthousiasm, but it was my opinion that a cdrom connected as primary slave could no longer be accessed once the harddisk on the primary master was locked. I could be wrong about this. You surely won't be able to do a hotswap that way. Booting from an usb stick might be the solution here. If you managed to use the lock tools in the same Kernel that has USB support, that shouldn't be a very big problem. Altough I wonder if they don't unmount the harddisk before they feed it the low level locking / unlocking commands. I suppose linux can do this without a reboot.
when xboxhdm was built, they didn't have a technology that has since matured - virtualization. I used qemu in my solution. Host is a 2.6 kernel with USB support , guest hosted by qemu is the original xboxhdm kernel (2.4) for FATX support. the cdrom is a virtual one running from the iso and before locking takes place, you would have shutdown the guest. QUOTE(obcd @ Apr 22 2008, 04:35 PM)
How can you see this xboxhdm disk corruption in the first place? (I know, it's not really a corruption.)
So many people used xboxhdm to create their xbox harddisk. I don't hear much complaining.
rmenhal is the one who spotted the bug and provided the original fix. Pls search for the post for details.QUOTE(obcd @ Apr 22 2008, 04:35 PM)
There exist a program called winhex that can analyse a harddisk on a very lowlevel way. I don't know how much fatx differs from fat32, but it might be a way to check the fat tables and see what was used to indicate the last cluster of a file. (Which is what differs if I read well.)
The equivalent in linux is the dd command. Can you suggest a specific test scenario that I could try out?QUOTE(obcd @ Apr 22 2008, 04:35 PM)
The primary purpose of xboxhdm is creating the C and E partition needed to make the harddisk usable in a xbox. The larger F and G partitions can be created afterwards. If a bigger cluster size is needed, xbpartionner can do the job, so I don't think you should put a lot of efford into the 32 and 64 bit Cluster size.
Actually it's basically done, I've posted the details in the linux forum, just need others to verify my work.QUOTE(obcd @ Apr 22 2008, 04:35 PM)
An upcoming problem is indeed the fact that most pc's only have one ide port left, and usually don't have a floppy drive anymore. An upgraded xboxhdm that solves those issues would help a lot of people.
Yes, that's the main motivation. - Title: Reintroducing Kernel Patching - Nkpatcher