Print

[DaddyJ]

v.10 available, updated root post.

[DaddyJ]

Updated root post with v.13 binaries & sources.

Fixed alot extended features as per xman's suggestions, also added auto compile & signing feature.

[DaddyJ]

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.

[xman954]

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+  

[DaddyJ]

thanks, for all your testing help and the additions you have added.......

[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.

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.

[DaddyJ]

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.

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?

[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.

[DaddyJ]

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.

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.

[DaddyJ]

Updated to v.15

This version just adds more loading of previously saved config.inc files.

[Horscht]

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

[DaddyJ]

That config.inc is not valid, it doesnt define the default boot path or led color..  definitly need to look further into that.

[Horscht]

again, after further investigation (upon reading your above post), the error only occurs if you have the option "disable boot settings" checked.

[DaBiscuit]

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.

[DaddyJ]

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.