Post by: DaddyJ on January 05, 2005, 07:27:00 PM
Project was discontinued, and no longer available.
And with Xman's additions to external boot file, this isnt needed.
This post has been edited by DaddyJ: Dec 14 2005, 06:20 AM
Post by: WITWICS on January 05, 2005, 07:29:00 PM
Post by: gamera on January 05, 2005, 07:23:00 PM
Post by: Australian Rat on January 05, 2005, 10:22:00 PM
Not for my own benifit but I'm kind of tired of seeing all these posts asking for help on nk10
This should help loads 
Post by: atomiX on January 05, 2005, 11:08:00 PM
i probably won't be using it since i like doing it manually but i bet its gonna save a few lives for ppl that don't like to mess with ASM
:beer:
Post by: krayzie on January 05, 2005, 11:22:00 PM
Post by: |vibez| on January 06, 2005, 03:19:00 AM
Post by: DaddyJ on January 06, 2005, 02:11:00 PM
QUOTE(Australian Rat)
I'm kind of tired of seeing all these posts asking for help on nk10
Thats whut I'm hoping as well.
Post by: DaddyJ on January 06, 2005, 07:51:00 PM
Just fool-proofing the options, dont want anything special happening ;)
This post has been edited by DaddyJ: Sep 16 2005, 04:21 PM
Post by: celinedrules on January 06, 2005, 07:46:00 PM
Post by: Australian Rat on January 06, 2005, 09:49:00 PM
I've always wanted to learn how to make simple programs like this using Visual Basic, I'll use this to learn as I go I'm going to include a few of the options you apparently left out of yours, just to give it slightly more flexibility.
Post by: wafflezone on January 07, 2005, 12:36:00 AM
Post by: DaddyJ on January 07, 2005, 09:51:00 PM
This release has been tested. Please verify that you have the correct version of NASM for auto compiling, it can be found here.
If your wanting the auto signing feature, then you must also have XBEDUMP.EXE is the same folder as well. It will automatically -habibi sign & rename the out.xbe to default.xbe, ready for production use.
Please report any errors to this thread.
The original CONFIG.INC is renamed to CONFIG.BAK during use, then renamed back into CONFIG.INC after program has run, this is to maintain the original source, no other files are modified.
Post by: BlackWar on January 07, 2005, 11:53:00 PM
QUOTE(DaddyJ @ Jan 7 2005, 11:22 PM)
The original CONFIG.INC is renamed to CONFIG.BAK during use, then renamed back into CONFIG.INC after program has run, this is to maintain the original source, no other files are modified.
hey, that is a damned good idea! I am growning tired of having all of these copies of sources all over my desktop (and root of C:, and root of D:...... <_<
Post by: GoldStar on January 08, 2005, 12:38:00 PM
its called something like shell and wait or simmilar..This would definatly be better programming.
http://www.vbcode.co....asp?theID=9026
try that one..use it for calling the "nasm -o blah blah" and "xbedump blah -habibi" ...that way the program REALLY knows when nasm and xbedump are finished..Just a little tip..
Post by: DaddyJ on January 08, 2005, 04:35:00 PM
The program isnt suppose to be elaborate, and doesnt use a high tech programming skill. It was written with everything it should have been written with.
The choice of SELECT CASE & IF THEN ELSE is an either way path, because of the seperate values I'm checking for, everything is pretty much ON/OFF which is more of a IF THEN ELSE kinda method. SELECT CASE is better in unlimited selection choices.
Post by: Australian Rat on January 08, 2005, 05:18:00 PM
QUOTE
The original CONFIG.INC is renamed to CONFIG.BAK during use, then renamed back into CONFIG.INC after program has run, this is to maintain the original source, no other files are modified.
Yeah, I did this for the next version of mine. Too many config*.bak file files were popping up
Post by: DaddyJ on January 08, 2005, 10:36:00 PM
Fixes v.02 Binaries
Fixed a few bugs in GUI, also fixed a few output bugs.
Fixes v.02 Sources
Fixed a few small typos.
This will be my last update on this project.
Post by: Yuyu on January 08, 2005, 10:59:00 PM
QUOTE(DaddyJ @ Jan 9 2005, 12:07 AM)
Updated to v.02
-
Title: Nkp-config
Post by: DaddyJ on January 09, 2005, 01:06:00 PM
-
Although it is the last version of nkp-config, I am working ona new development, discussed in over in this thread.
I Will include all available NKPatcher option in it.
-
Title: Nkp-config
Post by: DaddyJ on January 09, 2005, 07:25:00 PM
-
Haha that will never happen.
Thanks.
-
Title: Nkp-config
Post by: DaddyJ on January 21, 2005, 12:28:00 PM
-
You are probably refering to NKPatcher editor, as my GUI doesnt let you specify the virtual C IMG file to be placed on Partition 6 or 7.
-
Title: Nkp-config
Post by: total_ass on January 21, 2005, 01:08:00 PM
-
daddy you are adding support for this in another gui aren't you?
-
Title: Nkp-config
Post by: DaddyJ on January 21, 2005, 01:11:00 PM
-
Yes, this project has been updated into a plugin version for 'Another GUI', This and a few other features that wernt available, WILL be available in that version.
-
Title: Nkp-config
Post by: total_ass on January 21, 2005, 01:13:00 PM
-
an all-in-one tool.
-
Title: Nkp-config
Post by: DaddyJ on January 21, 2005, 01:16:00 PM
-
I'm hoping...
-
Title: Nkp-config
Post by: total_ass on January 27, 2005, 02:56:00 PM
-
hmm good tool.
if 'Show Actual' is unchecked next to the shadow drive option, am i correct in assuming that the C partition is not redefined at all? does this make all files on the real C drive (i.e virtual eeprom, shadow C) inaccessible? well obviously the shadow c would still be accessible, but what about the eeprom being stored on real C. would calls still be redirected to it?
-
Title: Nkp-config
Post by: DaddyJ on August 23, 2005, 05:07:00 PM
-
Will Be Updating This tool for the new additions to NKPatcher v10 abilities,
e.g.
Tri-Boot
Fan Speed
LED Controls
VGA Support
Thx to xman954 & dr_oldschool for these great additions.
Expect a beta in about a week,
Any suggestions make it now.
-
Title: Nkp-config
Post by: ikecomp on August 23, 2005, 08:18:00 PM
-
Just wanna give a shot out to u, krayzie and people like u that make all this possible.
-
Title: Nkp-config
Post by: Keo-Keo on August 23, 2005, 10:51:00 PM
-
Glade to see alot has been changing in the XBE Exploits with new additions to Nkpatcher.. It's a amzaing to see the changes when you come and go in a few months.. You guys should drop by sometime in the XDSL forums i mean *nix on the xbox (might as well be XDSL heheh )
-
Title: Nkp-config
Post by: xman954 on August 27, 2005, 12:15:00 AM
-
-
Title: Nkp-config
Post by: DaddyJ on August 27, 2005, 07:21:00 AM
-
Post by: DaddyJ on January 09, 2005, 01:06:00 PM
QUOTE(BlackWar)
this is your final release?
ahhh man. I was hoping you would release an "expert" feature that included the other options that you left out.
ahhh man. I was hoping you would release an "expert" feature that included the other options that you left out.
Although it is the last version of nkp-config, I am working ona new development, discussed in over in this thread.
I Will include all available NKPatcher option in it.
Post by: DaddyJ on January 09, 2005, 07:25:00 PM
QUOTE(BlackWar)
I thought maybe you were starting to get frusterated with peeps pokin fun at how you coded it
Haha that will never happen.
QUOTE(BlackWar)
I would like to say thank you, DaddyJ, for all the help you have given and for all that you have contributed to the scene.
Thanks.
Post by: DaddyJ on January 21, 2005, 12:28:00 PM
QUOTE(stevenho78)
dunno which version i got, but found that when i specified the virtual c path to be on drive f, it actually incorrectly set the partition number to 7 rather than 6.
You are probably refering to NKPatcher editor, as my GUI doesnt let you specify the virtual C IMG file to be placed on Partition 6 or 7.
Post by: total_ass on January 21, 2005, 01:08:00 PM
Post by: DaddyJ on January 21, 2005, 01:11:00 PM
QUOTE(total_ass @ Jan 21 2005, 04:39 PM)
daddy you are adding support for this in another gui aren't you?
Yes, this project has been updated into a plugin version for 'Another GUI', This and a few other features that wernt available, WILL be available in that version.
Post by: total_ass on January 21, 2005, 01:13:00 PM
an all-in-one tool.
Post by: DaddyJ on January 21, 2005, 01:16:00 PM
QUOTE(total_ass)
an all-in-one tool.
I'm hoping...
Post by: total_ass on January 27, 2005, 02:56:00 PM
if 'Show Actual' is unchecked next to the shadow drive option, am i correct in assuming that the C partition is not redefined at all? does this make all files on the real C drive (i.e virtual eeprom, shadow C) inaccessible? well obviously the shadow c would still be accessible, but what about the eeprom being stored on real C. would calls still be redirected to it?
Post by: DaddyJ on August 23, 2005, 05:07:00 PM
e.g.
Tri-Boot
Fan Speed
LED Controls
VGA Support
Thx to xman954 & dr_oldschool for these great additions.
Expect a beta in about a week,
Any suggestions make it now.
Post by: ikecomp on August 23, 2005, 08:18:00 PM
Post by: Keo-Keo on August 23, 2005, 10:51:00 PM
Post by: xman954 on August 27, 2005, 12:15:00 AM
Post by: DaddyJ on August 27, 2005, 07:21:00 AM
QUOTE(xman954 @ Aug 27 2005, 02:26 AM)
an auto save/load of your last settings would be nice
-
Title: Nkp-config
Post by: Australian Rat on August 27, 2005, 08:08:00 PM
-
-
Title: Nkp-config
Post by: DaddyJ on September 02, 2005, 06:48:00 PM
-
Posted screenshots of v.03 in the root post.....
Any final comments, this would be the time.
-
Title: Nkp-config
Post by: xman954 on September 02, 2005, 11:48:00 PM
-
NKpatcher boot options
(X) Boot dash only ........ (X) Boot DVD first
Default boot path E : path ; default.xbe >>> (has been split into two entrys)
LED color (X) red
...............(X) orange
...............(X) green
...............(X) other FF >>> (user enters hex value)
(X) Tray state Booting
opens this block----------------------------------
(X) open retail >>> (uses green led ,patch back and C:\msxboxdash.xbe as alt dash, as forced settings)
(X) open alt dash.......(X) tri-boot
open boot path E : altdash ; default.xbe
LED color (X) red
...............(X) orange
...............(X) green
...............(X) other FF >>> (user enters hex value)
-----------------------------------------------------
(X) set fan speed
opens this block----------------------------------
(X) 30%.....(X) 40%.....(X) 50%
(X) 60%.....(X) 70%.....(X) 80%
>>> (or have user enter %)
---------------------------------------------------
hope it makes sence
-
Title: Nkp-config
Post by: xman954 on September 03, 2005, 12:11:00 AM
-
sorry out of time
OR
(X) set fan speed user %
-
Title: Nkp-config
Post by: Cio on September 03, 2005, 06:25:00 AM
-
Checking the asm (if VGA stuff is actually there) and auto compiling/signing options maybe? (i kinda hate commandline utils..)
-
Title: Nkp-config
Post by: DaddyJ on September 03, 2005, 11:13:00 AM
-
@xman,
The default boot path is native to nkpatcher, as soon as you enable the tri-boot settings, the default boot path is no longer valid, as it will be replaced with 2 boot paths, and then and option to select MA, 007, or SC gamesaves as the tri, and maybe a custom as well.
Keep the feedback comming in,
-
Title: Nkp-config
Post by: xman954 on September 03, 2005, 11:35:00 AM
-
yes it is still valid for boot with power switch
the only difference from dual to tri is that the tray will close
and if a habibi disk is inserted before it closes it will boot that disk and not
the alt dash (mostly used for recovery and testing new stuff)
edit this might be misleading
it sould say
-
Title: Nkp-config
Post by: DaddyJ on September 03, 2005, 11:59:00 AM
-
this is the path if you additions are non-active.
when you additions become active, this path is still used, but moved into your additions frame of options.
And just so I'm clear
(these are defaults)
DEFAULT_PATH - boot from power (LED-ORANGE)
OPEN_PATH - Boot from eject (LED - RED)
PB_OPEN_PATH - boot with eject (no disc present) (LED - GREEN)
I feel i am mis-understanding the "when the KEY is patched back and when it is not" (it is patched back on open and no disc?)
am i understanding the terms correctly?
-
Title: Nkp-config
Post by: xman954 on September 03, 2005, 01:05:00 PM
-
that line should be in the .inc at all times
it was done so that you would not have to do two different types
of path define's in your code, the orignal and the split " path ; *.xbe "
note: in any setup (dual/tri) NKpatcher will boot when tray is closed and use it's led defaults
OK now the open-retail is for NDURE related tray booting and it think it should be
forced (in you code, so user does not have any option to change it, so they can't get banned from XBL )
%define PATCH_BACK_MS_KEY and PB_OPEN_PATH that is set to C:\msxboxdash.xbe
also PATCHBACK_LED_COLOR should be set to green
(PB_OPEN_PATH is short for patched back tray open path)
it was done this way in case a new MS signed xbe was found then the path could be changed very easy
OK now tri boot should not use the PATCH_BACK_MS_KEY it could
but most people would want to put there orignal game in to play XBL
and if you did that it would ERROR 21 becouse it is MS signed and not habibi signed
but if no disk was inserted it would do the same as open-retail (with the ability to boot a habibi disk) but you would have to open the tray put your game in and close tray to play on XBL
remember this has to be user friendly and not give them every option that could be set or you will never here the end of it LOL
put the default LED colors to what you think they should be
-
Title: Nkp-config
Post by: xman954 on September 03, 2005, 01:36:00 PM
-
-
Title: Nkp-config
Post by: DaddyJ on September 09, 2005, 08:09:00 PM
-
Just so you know, I havent forgotten about this project, was really busy at work this week, and didnt have much time to dedicate, but it is around 80% complete now, and hope to release a working version sometime tommorow night hopefully.
Will support all of the newest VGA code and your newest renditions also xman,
just had a few questions on the Fan speed codes, as i am guessing alot of people dont know them, can you possibly make a list of them
or maybe just the common 10 20 30 40 & 50, so that I may create a nice GUI conversion for them. thanks.
-
Title: Nkp-config
Post by: xman954 on September 09, 2005, 10:19:00 PM
-
very simple to do
hex value = % of desired speed from 20-100 /2
so for 40% 40/2 = 20 dec = 0014h (hex)
50% = 25 dec = 0019h
70% = 35 = 0023h
90% = 45 = 002Dh
so it would change every 2% (rounding)
-
Title: Nkp-config
Post by: DaddyJ on September 10, 2005, 02:50:00 PM
-
Root Post has been updated with v.06 beta binaries link.
WARNING
This version does have know issues,
Will not load CONFIG.INC files.
Does not auto compile or sign. (Included a script to do it, but user interaction is required.)
Will post source, and update as time permits, have fun with it, post any errors please.
-
Title: Nkp-config
Post by: xman954 on September 10, 2005, 03:36:00 PM
-
1 you must have unrar.dll for it to work
2 somthing wrong in virtual settings (shadow, eeprom swaped)
3 not all extra settings need to be enabled at once
you should not use tri-boot with patch back at the same time
and each feature should be inabled by it's self
led color for NKP (normal boot) in all cases must be set or
you will get errors
and if options are not enabled no extra code is generated
as the readme states that there is
take a look about 10 posts back and see if that makes more sence now
edit: the split path has been removed now it's one entry
-
Title: Nkp-config
Post by: DaddyJ on September 10, 2005, 04:06:00 PM
-
Easy enuff. (forgot to include that.)
a little more specific on this please?
i used your default settings, I plan on adding more options soon.
was it not set by default ???? I thought I set all by default.
yep, will fix.
I removed the split path output, the split path selections, do not interfer.
selecting E & then typing dashboard\default.xbe will produce
'\Device\Harddisk0\Partition1\dashboard\default.xbe' respectivly
-
Title: Nkp-config
Post by: xman954 on September 10, 2005, 04:45:00 PM
-
in vga section there needs to be a
VIDEO_FORCE_PROGRESSIVE (480p) option
if you don't select Enable tri-boot,fan & LED settings
you still need to define NKP_LED_COLOR
tray options that can be set are dual-boot, open-retail, tri-boot
and (tri-retail, but it's not of any use and thats way you have it set now)
the default settings (in orignal config.inc) was tri-boot
and it does not use "%define PATCH_BACK_MS_KEY" it is only for open-retail
-
Title: Nkp-config
Post by: DaddyJ on September 10, 2005, 04:55:00 PM
-
will fix.
umm there is, vga additions & enable SoG must be selected.
If your additions arent active, this wasnt in the orignal config.inc before your additions, are you sure this must be defined?
guess im still a little confused about whut patch back is actually for.
Also I discovered an issue with preview, as the program will cut the preview size, but saving still outputs complete code.
-
Title: Nkp-config
Post by: xman954 on September 10, 2005, 05:25:00 PM
-
yes that is the only code that is, it like 20 bytes it was done at last Minute as a request
could fix, but that may cause too much confusion
with different src files (the xboxapps would have to be updated)
if you want it for your project i will do it
oh ok sorry, i think there is only 2 options now for VGA-6 (SoG not used)
yes, if you save first then the preview is correct
it changes the habibi key back to the MS key so that only a MS signed xbe can boot (only if tray is open and tray boot is enabled)
-
Title: Nkp-config
Post by: DaddyJ on September 10, 2005, 08:06:00 PM
-
Updated Binaries & released sources. available in root post.
-
Title: Nkp-config
Post by: DaddyJ on September 11, 2005, 01:25:00 PM
-
tyhen you need to define either of these
If any of those are not defined then you define
more on tri & dual
if tri boot is defined then,
PB_OPEN_PATH
OPEN_PATH
DASHBOARD_PATH are used.
whut about in dual boot mode, which to paths need to be defined and set?
Correct? hopefully.
-
Title: Nkp-config
Post by: krayzie on September 11, 2005, 01:29:00 PM
-
Post by: Australian Rat on August 27, 2005, 08:08:00 PM
Post by: DaddyJ on September 02, 2005, 06:48:00 PM
Any final comments, this would be the time.
Post by: xman954 on September 02, 2005, 11:48:00 PM
(X) Boot dash only ........ (X) Boot DVD first
Default boot path E : path ; default.xbe >>> (has been split into two entrys)
LED color (X) red
...............(X) orange
...............(X) green
...............(X) other FF >>> (user enters hex value)
(X) Tray state Booting
opens this block----------------------------------
(X) open retail >>> (uses green led ,patch back and C:\msxboxdash.xbe as alt dash, as forced settings)
(X) open alt dash.......(X) tri-boot
open boot path E : altdash ; default.xbe
LED color (X) red
...............(X) orange
...............(X) green
...............(X) other FF >>> (user enters hex value)
-----------------------------------------------------
(X) set fan speed
opens this block----------------------------------
(X) 30%.....(X) 40%.....(X) 50%
(X) 60%.....(X) 70%.....(X) 80%
>>> (or have user enter %)
---------------------------------------------------
hope it makes sence
Post by: xman954 on September 03, 2005, 12:11:00 AM
OR
(X) set fan speed user %
Post by: Cio on September 03, 2005, 06:25:00 AM
Post by: DaddyJ on September 03, 2005, 11:13:00 AM
@xman,
The default boot path is native to nkpatcher, as soon as you enable the tri-boot settings, the default boot path is no longer valid, as it will be replaced with 2 boot paths, and then and option to select MA, 007, or SC gamesaves as the tri, and maybe a custom as well.
Keep the feedback comming in,
Post by: xman954 on September 03, 2005, 11:35:00 AM
QUOTE
The default boot path is native to nkpatcher, as soon as you enable the tri-boot settings, the default boot path is no longer valid, as it will be replaced with 2 boot paths
yes it is still valid for boot with power switch
the only difference from dual to tri is that the tray will close
and if a habibi disk is inserted before it closes it will boot that disk and not
the alt dash (mostly used for recovery and testing new stuff)
edit this might be misleading
QUOTE
(X) open retail >>> (uses green led ,patch back and C:\msxboxdash.xbe as alt dash, as forced settings)
it sould say
QUOTE
(X) open retail >>> (uses green led ,PATCH_BACK_MS_KEY and C:\msxboxdash.xbe in PB_OPEN_PATH, as forced settings)
Post by: DaddyJ on September 03, 2005, 11:59:00 AM
CODE
%define DASHBOARD_PATH DEFAULT_PATH,';', DEFAULT_NAME
this is the path if you additions are non-active.
when you additions become active, this path is still used, but moved into your additions frame of options.
And just so I'm clear
(these are defaults)
DEFAULT_PATH - boot from power (LED-ORANGE)
OPEN_PATH - Boot from eject (LED - RED)
PB_OPEN_PATH - boot with eject (no disc present) (LED - GREEN)
I feel i am mis-understanding the "when the KEY is patched back and when it is not" (it is patched back on open and no disc?)
am i understanding the terms correctly?
Post by: xman954 on September 03, 2005, 01:05:00 PM
QUOTE(DaddyJ @ Sep 3 2005, 02:10 PM)
Ok you might mis-interpreting.
default boot path is
default boot path is
CODE
%define DASHBOARD_PATH DEFAULT_PATH,';', DEFAULT_NAME
that line should be in the .inc at all times
it was done so that you would not have to do two different types
of path define's in your code, the orignal and the split " path ; *.xbe "
note: in any setup (dual/tri) NKpatcher will boot when tray is closed and use it's led defaults
OK now the open-retail is for NDURE related tray booting and it think it should be
forced (in you code, so user does not have any option to change it, so they can't get banned from XBL )
%define PATCH_BACK_MS_KEY and PB_OPEN_PATH that is set to C:\msxboxdash.xbe
also PATCHBACK_LED_COLOR should be set to green
(PB_OPEN_PATH is short for patched back tray open path)
it was done this way in case a new MS signed xbe was found then the path could be changed very easy
OK now tri boot should not use the PATCH_BACK_MS_KEY it could
but most people would want to put there orignal game in to play XBL
and if you did that it would ERROR 21 becouse it is MS signed and not habibi signed
but if no disk was inserted it would do the same as open-retail (with the ability to boot a habibi disk) but you would have to open the tray put your game in and close tray to play on XBL
remember this has to be user friendly and not give them every option that could be set or you will never here the end of it LOL
put the default LED colors to what you think they should be
Post by: xman954 on September 03, 2005, 01:36:00 PM
Post by: DaddyJ on September 09, 2005, 08:09:00 PM
Will support all of the newest VGA code and your newest renditions also xman,
just had a few questions on the Fan speed codes, as i am guessing alot of people dont know them, can you possibly make a list of them
or maybe just the common 10 20 30 40 & 50, so that I may create a nice GUI conversion for them. thanks.
Post by: xman954 on September 09, 2005, 10:19:00 PM
hex value = % of desired speed from 20-100 /2
so for 40% 40/2 = 20 dec = 0014h (hex)
50% = 25 dec = 0019h
70% = 35 = 0023h
90% = 45 = 002Dh
so it would change every 2% (rounding)
Post by: DaddyJ on September 10, 2005, 02:50:00 PM
WARNING
This version does have know issues,
Will not load CONFIG.INC files.
Does not auto compile or sign. (Included a script to do it, but user interaction is required.)
Will post source, and update as time permits, have fun with it, post any errors please.
Post by: xman954 on September 10, 2005, 03:36:00 PM
1 you must have unrar.dll for it to work
2 somthing wrong in virtual settings (shadow, eeprom swaped)
3 not all extra settings need to be enabled at once
you should not use tri-boot with patch back at the same time
and each feature should be inabled by it's self
led color for NKP (normal boot) in all cases must be set or
you will get errors
and if options are not enabled no extra code is generated
as the readme states that there is
take a look about 10 posts back and see if that makes more sence now
edit: the split path has been removed now it's one entry
Post by: DaddyJ on September 10, 2005, 04:06:00 PM
QUOTE(xman954)
1 you must have unrar.dll for it to work
Easy enuff. (forgot to include that.)
QUOTE(xman954)
2 somthing wrong in virtual settings (shadow, eeprom swaped)
a little more specific on this please?
QUOTE(xman954)
3 not all extra settings need to be enabled at once
you should not use tri-boot with patch back at the same time
and each feature should be inabled by it's self
you should not use tri-boot with patch back at the same time
and each feature should be inabled by it's self
i used your default settings, I plan on adding more options soon.
QUOTE(xman954)
led color for NKP (normal boot) in all cases must be set or
you will get errors
you will get errors
was it not set by default ???? I thought I set all by default.
QUOTE(xman954)
and if options are not enabled no extra code is generated
as the readme states that there is
as the readme states that there is
yep, will fix.
QUOTE(xman954)
take a look about 10 posts back and see if that makes more sence now
edit: the split path has been removed now it's one entry
edit: the split path has been removed now it's one entry
I removed the split path output, the split path selections, do not interfer.
selecting E & then typing dashboard\default.xbe will produce
'\Device\Harddisk0\Partition1\dashboard\default.xbe' respectivly
Post by: xman954 on September 10, 2005, 04:45:00 PM
in vga section there needs to be a
VIDEO_FORCE_PROGRESSIVE (480p) option
if you don't select Enable tri-boot,fan & LED settings
you still need to define NKP_LED_COLOR
tray options that can be set are dual-boot, open-retail, tri-boot
and (tri-retail, but it's not of any use and thats way you have it set now)
the default settings (in orignal config.inc) was tri-boot
and it does not use "%define PATCH_BACK_MS_KEY" it is only for open-retail
Post by: DaddyJ on September 10, 2005, 04:55:00 PM
QUOTE(xman954)
when you select enable virtual C the box has E:\shadowC\eeprom.bin (not shadowC.img) and the eeprom has shadowC.img
will fix.
QUOTE(xman954)
in vga section there needs to be a
VIDEO_FORCE_PROGRESSIVE (480p) option
VIDEO_FORCE_PROGRESSIVE (480p) option
umm there is, vga additions & enable SoG must be selected.
QUOTE(xman954)
if you don't select Enable tri-boot,fan & LED settings
you still need to define NKP_LED_COLOR
you still need to define NKP_LED_COLOR
If your additions arent active, this wasnt in the orignal config.inc before your additions, are you sure this must be defined?
QUOTE(xman954)
tray options that can be set are dual-boot, open-retail, tri-boot
and (tri-retail, but not of any use)
the default settings (in orignal config.inc) was tri-boot
and it does not use "%define PATCH_BACK_MS_KEY" it is only for open-retail
and (tri-retail, but not of any use)
the default settings (in orignal config.inc) was tri-boot
and it does not use "%define PATCH_BACK_MS_KEY" it is only for open-retail
guess im still a little confused about whut patch back is actually for.
Also I discovered an issue with preview, as the program will cut the preview size, but saving still outputs complete code.
Post by: xman954 on September 10, 2005, 05:25:00 PM
QUOTE
If your additions arent active, this wasnt in the orignal config.inc before your additions, are you sure this must be defined?
yes that is the only code that is, it like 20 bytes it was done at last Minute as a request
could fix, but that may cause too much confusion
with different src files (the xboxapps would have to be updated)
if you want it for your project i will do it
QUOTE
umm there is, vga additions & enable SoG must be selected.
oh ok sorry, i think there is only 2 options now for VGA-6 (SoG not used)
QUOTE
Also I discovered an issue with preview, as the program will cut the preview size, but saving still outputs complete code.
yes, if you save first then the preview is correct
QUOTE
uess im still a little confused about whut patch back is actually for.
it changes the habibi key back to the MS key so that only a MS signed xbe can boot (only if tray is open and tray boot is enabled)
Post by: DaddyJ on September 10, 2005, 08:06:00 PM
Post by: DaddyJ on September 11, 2005, 01:25:00 PM
CODE
%define TRAY_BOOT
tyhen you need to define either of these
CODE
%define TRI_BOOT
%define DUAL_BOOT
%define OPEN_RETAIL
%define DUAL_BOOT
%define OPEN_RETAIL
If any of those are not defined then you define
CODE
%define PATCH_BACK_MS_KEY
more on tri & dual
if tri boot is defined then,
PB_OPEN_PATH
OPEN_PATH
DASHBOARD_PATH are used.
whut about in dual boot mode, which to paths need to be defined and set?
Correct? hopefully.
Post by: krayzie on September 11, 2005, 01:29:00 PM
QUOTE(DaddyJ @ Sep 11 2005, 09:36 PM)
ok, lets see if i understand this.
-
Title: Nkp-config
Post by: xman954 on September 11, 2005, 09:09:00 PM
-
aka: dual-boot
aka: open-retail (for NDURE)
aka: tri-boot
aka: tri-retail (there is no use for this setup)
-
Title: Nkp-config
Post by: krayzie on September 11, 2005, 10:37:00 PM
-
why is there no use fore the tri-retail setup? is it becuz it doesn't leave the tray open like the dual retail?
-
Title: Nkp-config
Post by: DaddyJ on September 12, 2005, 05:05:00 AM
-
that deifnitly clears things up, will make modifications, and update binaries & source.
-
Title: Nkp-config
Post by: xman954 on September 12, 2005, 11:16:00 AM
-
Post by: xman954 on September 11, 2005, 09:09:00 PM
CODE
%define NKP_LED_COLOR ORANGE
%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dashboard\default.xbe'
as you can see this is in every case%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dashboard\default.xbe'
aka: dual-boot
CODE
%define TRAY_BOOT
%define ALTDASH_LED_COLOR RED
%define OPEN_PATH '\Device\Harddisk0\Partition1\UDATA\4d530017\62d648ebf155\default.xbe'
%define NKP_LED_COLOR ORANGE
%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dashboard\default.xbe'
%define ALTDASH_LED_COLOR RED
%define OPEN_PATH '\Device\Harddisk0\Partition1\UDATA\4d530017\62d648ebf155\default.xbe'
%define NKP_LED_COLOR ORANGE
%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dashboard\default.xbe'
aka: open-retail (for NDURE)
CODE
%define TRAY_BOOT
%define PATCH_BACK_MS_KEY
%define PATCHBACK_LED_COLOR GREEN
%define PB_OPEN_PATH '\Device\Harddisk0\Partition2\msxboxdash.xbe'
%define NKP_LED_COLOR ORANGE
%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dashboard\default.xbe'
%define PATCH_BACK_MS_KEY
%define PATCHBACK_LED_COLOR GREEN
%define PB_OPEN_PATH '\Device\Harddisk0\Partition2\msxboxdash.xbe'
%define NKP_LED_COLOR ORANGE
%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dashboard\default.xbe'
aka: tri-boot
CODE
%define TRAY_BOOT
%define TRI_BOOT
%define ALTDASH_LED_COLOR RED
%define OPEN_PATH '\Device\Harddisk0\Partition1\UDATA\4d530017\62d648ebf155\default.xbe'
%define NKP_LED_COLOR ORANGE
%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dashboard\default.xbe'
%define TRI_BOOT
%define ALTDASH_LED_COLOR RED
%define OPEN_PATH '\Device\Harddisk0\Partition1\UDATA\4d530017\62d648ebf155\default.xbe'
%define NKP_LED_COLOR ORANGE
%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dashboard\default.xbe'
aka: tri-retail (there is no use for this setup)
CODE
%define TRAY_BOOT
%define TRI_BOOT
%define PATCH_BACK_MS_KEY
%define PATCHBACK_LED_COLOR GREEN
%define PB_OPEN_PATH '\Device\Harddisk0\Partition2\msxboxdash.xbe'
%define NKP_LED_COLOR ORANGE
%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dashboard\default.xbe'
%define TRI_BOOT
%define PATCH_BACK_MS_KEY
%define PATCHBACK_LED_COLOR GREEN
%define PB_OPEN_PATH '\Device\Harddisk0\Partition2\msxboxdash.xbe'
%define NKP_LED_COLOR ORANGE
%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dashboard\default.xbe'
Post by: krayzie on September 11, 2005, 10:37:00 PM
Post by: DaddyJ on September 12, 2005, 05:05:00 AM
Post by: xman954 on September 12, 2005, 11:16:00 AM
QUOTE(krayzie @ Sep 12 2005, 12:48 AM)
why is there no use fore the tri-retail setup? is it becuz it doesn't leave the tray open like the dual retail?
-
Title: Nkp-config
Post by: krayzie on September 12, 2005, 11:20:00 AM
-
ok that's what I thought. I get it that it probably suck to wait till it closes and then open it up again. And alot of impatient people would face an error 21.
-
Title: Nkp-config
Post by: DaddyJ on September 12, 2005, 07:37:00 PM
-
ok, v.09 available (see root post), hope I made the correct adjustments to the selectable dual/tri modes.
-
Title: Nkp-config
Post by: xman954 on September 13, 2005, 12:03:00 AM
-
very nice and very close to "done"
mostly name conventions
from: Enable tri-boot, FAN & LED control settings
to: Enable tray booting, FAN & LED control settings
from: open with power color
to: boot with power color
......(all NKP features)
from: open with eject color
to: boot with eject color
......(no NKP features)
from: patchbach color
to: M$ dash color (or set it green allways, also it is not used unless open-retail (NDURE) is selected)
from: Enable M$ patchback
to: Enable Open-retail (NDURE)
remove:
"open with power path" settings block (it will use "default boot path" in "booting Options", don't make that go away when "Enable tray booting, Fan & LED" is selected.
(then there is no need for the words single boot only)
now:
with tri-boot enabled the only path's that are needed/used is "Boot with eject path" and "default boot path".
(tri-boot is when you put a disk in before it closes it will boot it, otherwise
it will "Boot with eject path")
with dual-boot enabled the only path that are needed/used is "Boot with eject path" and "default boot path".
with open retail enabled the only path's that are needed/used is "patchback path" and "default boot path".
also "patchback path" should be renamed to "M$ dash path"
with no try-boot, open-retail or dual-boot selected the only color option
should be "boot with power color" renamed to "NKPatcher color" in this case only
-
Title: Nkp-config
Post by: DaddyJ on September 13, 2005, 08:26:00 AM
-
v.10 available, updated root post.
-
Title: Nkp-config
Post by: DaddyJ on September 15, 2005, 04:19:00 PM
-
Updated root post with v.13 binaries & sources.
Fixed alot extended features as per xman's suggestions, also added auto compile & signing feature.
-
Title: Nkp-config
Post by: DaddyJ on September 16, 2005, 07:43:00 AM
-
v.14 is available in root post.
added a few final fixes in extended sections, and partial loading ability of compatible config.inc files.
Will be finalizing the loading module, and adding advanced options soon.
-
Title: Nkp-config
Post by: xman954 on September 16, 2005, 10:53:00 AM
-
very nice, good job man
can't wait till you add the "save my default settings"
there is 1 warning for users:
when using tray options no kernal patching
is done before these decisions are made
you must use C:\ (the real C) or E:\
in "Boot with Eject Path" or "M$ dash Path"
if you try to use F,G,8 it will not work...
everyone should try this program
to config NKPatcher V10+
-
Title: Nkp-config
Post by: DaddyJ on September 16, 2005, 12:37:00 PM
-
thanks, for all your testing help and the additions you have added.......
-
Title: Nkp-config
Post by: Horscht on September 21, 2005, 09:53:00 AM
-
When I tried to "save & compile" myself a nkpatcher with the latest version (v. 14), I got an error and xbedump colsed itself. I am not sure what it says usualy in english language, but when I translate the error from german it says something along those lines:
xbedump.exe has detected a problem and must be terminated.
If you haven't saved your work, data might be lost
for more information click here
when I click there, i get another window:
Problemsignature
AppName: xbedump.exe AppVer 0.0.0.0 ModName xbedump.exe
ModVer: 0.0.0.0 Offset: 000077bc
to see technical informations to the problemreport, clickb here
when I click there I get alot of numbers and letters. If you need this information anyways, I'll make a few screenies.
This error only occurs if I try to compile it with NKP-Config v. 14, but not with the make-tray_nkp.bat included in the nkpatcher10_xman package.
-
Title: Nkp-config
Post by: DaddyJ on September 21, 2005, 10:08:00 AM
-
What Operating system?
Also manually check the src directory and manually add the saved .inc file to it named config.inc and run compile.bat, does this work?
-
Title: Nkp-config
Post by: Horscht on September 21, 2005, 12:05:00 PM
-
1. Sorry, forgot to add that: Windows XP SP1
2. No manual adding the inc and running the compile.bat won't work either.
-
Title: Nkp-config
Post by: DaddyJ on September 21, 2005, 03:16:00 PM
-
From the sounds of it, it almost sounds as if either
A. the nasm.exe and/or xbedump.exe are corrupted.
(you could try replacing them, but you must replace them after the program has been started as proginfo.dat is uncompressed at runtime.)
or
b. nasm isnt producing a xbe for xbedump to sign causing the error. (usually only caused if the config.inc isnt present or invalid code is presented, email me the config.inc or the saved filename for further examination.(pm for email))
I will look into this, but do not experience in my environment, so am kinda working in the blind.
-
Title: Nkp-config
Post by: DaddyJ on September 21, 2005, 07:12:00 PM
-
Updated to v.15
This version just adds more loading of previously saved config.inc files.
-
Title: Nkp-config
Post by: Horscht on September 22, 2005, 06:26:00 AM
-
-
Title: Nkp-config
Post by: DaddyJ on September 22, 2005, 06:51:00 AM
-
That config.inc is not valid, it doesnt define the default boot path or led color.. definitly need to look further into that.
-
Title: Nkp-config
Post by: Horscht on September 22, 2005, 07:01:00 AM
-
again, after further investigation (upon reading your above post), the error only occurs if you have the option "disable boot settings" checked.
-
Title: Nkp-config
Post by: DaBiscuit on September 22, 2005, 07:04:00 AM
-
I hope it's OK to ask a few n00bish questions here, DaddyJ.
1) This config.inc file, is it a runtime config file, or a compile-time config file? I believe it to be the latter, but I'd like confirmation
2) If it is a compile-time config tool, and I create my own custom NK10, can I just use it as a drop-in replacement for the one provided by the NDURE installer? Will I need to change anything else?
I'm tempted to get a little "deeper" into understanding how softmods work, and this sort of thing is how I figure I'll learn. Just being able to make my softmod work isn't enough for me anymore. I want to know the how and the why. If anyone can suggest some threads/pages/whatever that might help me along, please PM me.
-
Title: Nkp-config
Post by: DaddyJ on September 22, 2005, 07:51:00 AM
-
Awesome detective work, i was thinking the same think trying to recreate the problem, this is definitly a bug in code, will release a fix later tonight, after work.
-
Title: Nkp-config
Post by: DaddyJ on September 22, 2005, 07:56:00 AM
-
This tool creates a custom config.inc for use with xman's & dr_oldschool's additions to nkpatcher10. This program in no way changes any other file.
If you'd like to change the nkpatcher internals, then you must repackage the proginfo.dat file which is just the "fixed" src directory rar'd. This folder must have the compile.bat nasm.exe & xbedump.exe present if changed. ** changing the proginfo.dat file is not recommended.
If configured correctly the outputted default.xbe can be used in all applications, seek the information on your particular settings in the ndure thread.
-
Title: Nkp-config
Post by: DaddyJ on September 22, 2005, 10:10:00 AM
-
OK, have found a bug in v.14 (thanx horscht) which when enabled tray-boot options, but disabled multi booting options.
The default paths donot get set.
This was not fixed, but actually changed in v.15, v.15 disabled the disable booting options (this is what happens when you make changes to source at 2 different locations)
I will re-apply all the correct options, later on this evening.
-
Title: Nkp-config
Post by: DaddyJ on September 22, 2005, 02:09:00 PM
-
V.19 - Horscht, please try this version, with the same settings as before, i believe to have fixed the selectable options.
i will be adding auto updating in v.20.
-
Title: Nkp-config
Post by: Horscht on September 22, 2005, 03:10:00 PM
-
Post by: krayzie on September 12, 2005, 11:20:00 AM
Post by: DaddyJ on September 12, 2005, 07:37:00 PM
Post by: xman954 on September 13, 2005, 12:03:00 AM
mostly name conventions
from: Enable tri-boot, FAN & LED control settings
to: Enable tray booting, FAN & LED control settings
from: open with power color
to: boot with power color
......(all NKP features)
from: open with eject color
to: boot with eject color
......(no NKP features)
from: patchbach color
to: M$ dash color (or set it green allways, also it is not used unless open-retail (NDURE) is selected)
from: Enable M$ patchback
to: Enable Open-retail (NDURE)
remove:
"open with power path" settings block (it will use "default boot path" in "booting Options", don't make that go away when "Enable tray booting, Fan & LED" is selected.
(then there is no need for the words single boot only)
now:
with tri-boot enabled the only path's that are needed/used is "Boot with eject path" and "default boot path".
(tri-boot is when you put a disk in before it closes it will boot it, otherwise
it will "Boot with eject path")
with dual-boot enabled the only path that are needed/used is "Boot with eject path" and "default boot path".
with open retail enabled the only path's that are needed/used is "patchback path" and "default boot path".
also "patchback path" should be renamed to "M$ dash path"
with no try-boot, open-retail or dual-boot selected the only color option
should be "boot with power color" renamed to "NKPatcher color" in this case only
Post by: DaddyJ on September 13, 2005, 08:26:00 AM
Post by: DaddyJ on September 15, 2005, 04:19:00 PM
Fixed alot extended features as per xman's suggestions, also added auto compile & signing feature.
Post by: DaddyJ on September 16, 2005, 07:43:00 AM
added a few final fixes in extended sections, and partial loading ability of compatible config.inc files.
Will be finalizing the loading module, and adding advanced options soon.
Post by: xman954 on September 16, 2005, 10:53:00 AM
can't wait till you add the "save my default settings"
there is 1 warning for users:
when using tray options no kernal patching
is done before these decisions are made
you must use C:\ (the real C) or E:\
in "Boot with Eject Path" or "M$ dash Path"
if you try to use F,G,8 it will not work...
everyone should try this program
to config NKPatcher V10+
Post by: DaddyJ on September 16, 2005, 12:37:00 PM
Post by: Horscht on September 21, 2005, 09:53:00 AM
xbedump.exe has detected a problem and must be terminated.
If you haven't saved your work, data might be lost
for more information click here
when I click there, i get another window:
Problemsignature
AppName: xbedump.exe AppVer 0.0.0.0 ModName xbedump.exe
ModVer: 0.0.0.0 Offset: 000077bc
to see technical informations to the problemreport, clickb here
when I click there I get alot of numbers and letters. If you need this information anyways, I'll make a few screenies.
This error only occurs if I try to compile it with NKP-Config v. 14, but not with the make-tray_nkp.bat included in the nkpatcher10_xman package.
Post by: DaddyJ on September 21, 2005, 10:08:00 AM
QUOTE(Horscht)
When I tried to "save & compile" myself a nkpatcher with the latest version (v. 14), I got an error and xbedump colsed itself. I am not sure what it says usualy in english language, but when I translate the error from german it says something along those lines:
xbedump.exe has detected a problem and must be terminated.
xbedump.exe has detected a problem and must be terminated.
What Operating system?
Also manually check the src directory and manually add the saved .inc file to it named config.inc and run compile.bat, does this work?
Post by: Horscht on September 21, 2005, 12:05:00 PM
2. No manual adding the inc and running the compile.bat won't work either.
Post by: DaddyJ on September 21, 2005, 03:16:00 PM
QUOTE(Horscht)
1. Sorry, forgot to add that: Windows XP SP1
2. No manual adding the inc and running the compile.bat won't work either.
2. No manual adding the inc and running the compile.bat won't work either.
From the sounds of it, it almost sounds as if either
A. the nasm.exe and/or xbedump.exe are corrupted.
(you could try replacing them, but you must replace them after the program has been started as proginfo.dat is uncompressed at runtime.)
or
b. nasm isnt producing a xbe for xbedump to sign causing the error. (usually only caused if the config.inc isnt present or invalid code is presented, email me the config.inc or the saved filename for further examination.(pm for email))
I will look into this, but do not experience in my environment, so am kinda working in the blind.
Post by: DaddyJ on September 21, 2005, 07:12:00 PM
This version just adds more loading of previously saved config.inc files.
Post by: Horscht on September 22, 2005, 06:26:00 AM
CODE
;v10
;;; NKPatcher v10 CONFIG.INC Compatible Output file
%ifndef CONFIG_INC
%define CONFIG_INC
%define ORANGE 00FFh
%define ORANGE_BLINK 0077h
%define RED 00F0h
%define RED_BLINK 0070h
%define GREEN 000Fh
%define GREEN_BLINK 0007h
%define CYCLE 00EBh
%define LED_OFF 0000h
%define NKP_LED_COLOR ORANGE
%define ALTDASH_LED_COLOR RED
%define PATCHBACK_LED_COLOR GREEN
%define FAN_SPEED 00Ah
%define CD_DVD_ALWAYS_ROE
%define GAME_REGION_AUTO
%define GAME_REGION_PRIMARY 4
%define GAME_REGION_SECONDARY 1
%define GAME_REGION_TERTIARY 2
%define IGR
%define IGR_MASTER_PORT 1
%define XBL_BLOCK
%define VIRTUAL_C_DRIVE 2
%define VIRTUAL_C_PATH '\Device\Harddisk0\Partition8\shadowc.img'
%define ACTUAL_C_DRIVE 8
%define LBA48
%define PARTITION_METHOD 1
%define VIRTUAL_EEPROM
%define VIRTUAL_EEPROM_PATH '\Device\Harddisk0\Partition8\eeprom.bin'
%define NORMAL_BOOT_ALWAYS
%endif
;;; NKPatcher v10 CONFIG.INC Compatible Output file
%ifndef CONFIG_INC
%define CONFIG_INC
%define ORANGE 00FFh
%define ORANGE_BLINK 0077h
%define RED 00F0h
%define RED_BLINK 0070h
%define GREEN 000Fh
%define GREEN_BLINK 0007h
%define CYCLE 00EBh
%define LED_OFF 0000h
%define NKP_LED_COLOR ORANGE
%define ALTDASH_LED_COLOR RED
%define PATCHBACK_LED_COLOR GREEN
%define FAN_SPEED 00Ah
%define CD_DVD_ALWAYS_ROE
%define GAME_REGION_AUTO
%define GAME_REGION_PRIMARY 4
%define GAME_REGION_SECONDARY 1
%define GAME_REGION_TERTIARY 2
%define IGR
%define IGR_MASTER_PORT 1
%define XBL_BLOCK
%define VIRTUAL_C_DRIVE 2
%define VIRTUAL_C_PATH '\Device\Harddisk0\Partition8\shadowc.img'
%define ACTUAL_C_DRIVE 8
%define LBA48
%define PARTITION_METHOD 1
%define VIRTUAL_EEPROM
%define VIRTUAL_EEPROM_PATH '\Device\Harddisk0\Partition8\eeprom.bin'
%define NORMAL_BOOT_ALWAYS
%endif
Post by: DaddyJ on September 22, 2005, 06:51:00 AM
Post by: Horscht on September 22, 2005, 07:01:00 AM
Post by: DaBiscuit on September 22, 2005, 07:04:00 AM
1) This config.inc file, is it a runtime config file, or a compile-time config file? I believe it to be the latter, but I'd like confirmation
2) If it is a compile-time config tool, and I create my own custom NK10, can I just use it as a drop-in replacement for the one provided by the NDURE installer? Will I need to change anything else?
I'm tempted to get a little "deeper" into understanding how softmods work, and this sort of thing is how I figure I'll learn. Just being able to make my softmod work isn't enough for me anymore. I want to know the how and the why. If anyone can suggest some threads/pages/whatever that might help me along, please PM me.
Post by: DaddyJ on September 22, 2005, 07:51:00 AM
QUOTE(Horscht)
again, after further investigation (upon reading your above post), the error only occurs if you have the option "disable boot settings" checked.
Awesome detective work, i was thinking the same think trying to recreate the problem, this is definitly a bug in code, will release a fix later tonight, after work.
Post by: DaddyJ on September 22, 2005, 07:56:00 AM
QUOTE(DaBiscuit)
1) This config.inc file, is it a runtime config file, or a compile-time config file? I believe it to be the latter, but I'd like confirmation
This tool creates a custom config.inc for use with xman's & dr_oldschool's additions to nkpatcher10. This program in no way changes any other file.
If you'd like to change the nkpatcher internals, then you must repackage the proginfo.dat file which is just the "fixed" src directory rar'd. This folder must have the compile.bat nasm.exe & xbedump.exe present if changed. ** changing the proginfo.dat file is not recommended.
QUOTE(DaBiscuit)
2) If it is a compile-time config tool, and I create my own custom NK10, can I just use it as a drop-in replacement for the one provided by the NDURE installer? Will I need to change anything else?
If configured correctly the outputted default.xbe can be used in all applications, seek the information on your particular settings in the ndure thread.
Post by: DaddyJ on September 22, 2005, 10:10:00 AM
The default paths donot get set.
This was not fixed, but actually changed in v.15, v.15 disabled the disable booting options (this is what happens when you make changes to source at 2 different locations)
I will re-apply all the correct options, later on this evening.
Post by: DaddyJ on September 22, 2005, 02:09:00 PM
i will be adding auto updating in v.20.
Post by: Horscht on September 22, 2005, 03:10:00 PM
QUOTE(DaddyJ @ Sep 22 2005, 10:20 PM)
Horscht, please try this version
-
Title: Nkp-config
Post by: DaddyJ on September 22, 2005, 04:29:00 PM
-
i believe you are correct, will fix, good ketch.
-
Title: Nkp-config
Post by: xman954 on September 22, 2005, 05:06:00 PM
-
there is no actual order, any option can be anywhere in the file
the complier reads the whole file then moves on
-
Title: Nkp-config
Post by: DaddyJ on September 22, 2005, 06:42:00 PM
-
thanx xman....
Also added partial autoupdating, so you wont have to keep check here
-
Title: Nkp-config
Post by: DaddyJ on September 22, 2005, 06:43:00 PM
-
damn!
-
Title: Nkp-config
Post by: DaddyJ on September 26, 2005, 10:00:00 AM
-
v.23 in root post, this is the last version that will need manually updated, future versions can be updated thru the program itself.
-
Title: Nkp-config
Post by: DaddyJ on September 29, 2005, 08:32:00 PM
-
v.24 in root post & auto-update.
added dus's clock check feature, coded by Xman954.
-
Title: Nkp-config
Post by: xman954 on September 29, 2005, 09:36:00 PM
-
http://forums.xbox-s...dpost&p=2938876
-
Title: Nkp-config
Post by: DaddyJ on November 10, 2005, 07:02:00 AM
-
This project has been discontinued, and I will be providing no more updates to it... The newest sources will be released, so if anyone would like to take this project on, feel free to do so.
-
Title: Nkp-config
Post by: DaddyJ on November 10, 2005, 09:45:00 AM
-
Post by: DaddyJ on September 22, 2005, 04:29:00 PM
Post by: xman954 on September 22, 2005, 05:06:00 PM
QUOTE
I was under the impression Nkpatcher would somehow use the definitions in order.
there is no actual order, any option can be anywhere in the file
the complier reads the whole file then moves on
Post by: DaddyJ on September 22, 2005, 06:42:00 PM
thanx xman....Also added partial autoupdating, so you wont have to keep check here
Post by: DaddyJ on September 22, 2005, 06:43:00 PM
Post by: DaddyJ on September 26, 2005, 10:00:00 AM
Post by: DaddyJ on September 29, 2005, 08:32:00 PM
added dus's clock check feature, coded by Xman954.
Post by: xman954 on September 29, 2005, 09:36:00 PM
http://forums.xbox-s...dpost&p=2938876
Post by: DaddyJ on November 10, 2005, 07:02:00 AM
Post by: DaddyJ on November 10, 2005, 09:45:00 AM
QUOTE(jonels @ Nov 10 2005, 10:49 AM)
Thats a shame, I found your utilty very handy.
-
Title: Nkp-config
Post by: DaddyJ on November 10, 2005, 05:12:00 PM
-
Last post, I posted the latest sources here........
Have fun .....
-
Title: Nkp-config
Post by: ravenray on December 13, 2005, 06:59:00 PM
-
Hmmm, I assume that no one has tried to compiled this then?
-
Title: Nkp-config
Post by: DaddyJ on December 13, 2005, 10:12:00 PM
-
Hmmm, I assume that no one has tried to compiled this then?
This project was discontinued some time ago, the last released sources were corrupted... and would not compile.
-
Title: Nkp-config
Post by: DaddyJ on December 14, 2005, 12:24:00 PM
-
naw, with the latest releases from xman, a config.inc compilier arnt really needed.
Post by: DaddyJ on November 10, 2005, 05:12:00 PM
Have fun .....
Post by: ravenray on December 13, 2005, 06:59:00 PM
Post by: DaddyJ on December 13, 2005, 10:12:00 PM
QUOTE(ravenray @ Dec 13 2005, 09:06 PM) 
Hmmm, I assume that no one has tried to compiled this then?
This project was discontinued some time ago, the last released sources were corrupted... and would not compile.
Post by: DaddyJ on December 14, 2005, 12:24:00 PM