Print

[xman954]

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

[DaddyJ]

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

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

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

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

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

[xman954]

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

[DaddyJ]

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

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

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

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.

[xman954]

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)

[DaddyJ]

Updated Binaries & released sources. available in root post.

[DaddyJ]

CODE

%define TRAY_BOOT

tyhen you need to define either of these

CODE

%define TRI_BOOT
%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.

[krayzie]

QUOTE(DaddyJ @ Sep 11 2005, 09:36 PM)

ok, lets see if i understand this.

[xman954]

CODE

%define NKP_LED_COLOR          ORANGE
%define DASHBOARD_PATH '\Device\Harddisk0\Partition1\dashboard\default.xbe'

as you can see this is in every case


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'

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'

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'

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'

[krayzie]

why is there no use fore the tri-retail setup? is it becuz it doesn't leave the tray open like the dual retail?

[DaddyJ]

that deifnitly clears things up, will make modifications, and update binaries & source.

[xman954]

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?

[krayzie]

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.

[DaddyJ]

ok, v.09 available (see root post), hope I made the correct adjustments to the selectable dual/tri modes.

[xman954]

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