What am I doing wrong? I put nasm into the src directory, and run:
You could be fancy and do what I did
Put both nasm.exe (make sure it's not nasmw.exe) and xbedump.exe in the src directory. Create a new file in notepad and copy in this code.
CODE
nasmw -o nkpatcher.xbe xboxapp.asm
xbedump nkpatcher.xbe -h
del nkpatcher
rename out.xbe default.xbe
Save the text file as compile.bat or something. This will then create a signed & compiled nkpatcher by just running the .bat file.
(That code might be slightly off btw, I did it from memory but you get the idea)
QUOTE(Australian Rat @ Jan 2 2005, 08:08 PM)
(make sure it's not nasmw.exe)
nasmw -o nkpatcher.xbe xboxapp.asm
LOL
QUOTE(total_ass @ Jan 2 2005, 07:25 PM)
yes, but i have to be honest, i get very nervous trying to modify something that i know will screw up if done incorrectly, especially if i've never done it before.
i'll try signing xboxdash.xbe with habibi then booting into it from ltools and seeing what happens.
You dont have your handy dandy XboxHDM Restore CD?
QUOTE(anjilslaire)
What am I doing wrong? I put nasm into the src directory, and run:
nasm -o nkpatcher.xbe xboxapp.asm
from the cmd prompt, and it processes for a few seconds,. but no new xbe is created, either in \src or anywhere else.
Any suggestions?
Are you running from a dos window? If you goto START-Run-cmd, then the box will stay open afterwards, this will inform you of any errors during compiling time, may help you resolve the issue.
Ah crapola...
See, told you it was from memory. Well, just make sure that it is nasmw.exe or change that script...
...we all have our moments
EDIT: btw, why can't we edit posts which have been replied to? Is that new or has it always been this way???
QUOTE(total_ass @ Jan 3 2005, 01:25 AM)
yes, but i have to be honest, i get very nervous trying to modify something that i know will screw up if done incorrectly, especially if i've never done it before.
i do indeed have backups of my modded and unmodded C partitions, but like i stated i don't have easy access to using xboxhdm, nor do i have my exploitable gamesave. so if i make a mistake on the hard drive its not quite as simple as just ftping into it and fixing it.
and i am changing to UXE because i no longer want to use ltools, its err how one would say 'messy' as it leaves tons of files on the C drive, leaves a bios loader on the E drive, as well as a once useful, but now annoying dualboot. I want to confine all mods to the C drive, keeping true C as clean as possible, and only leaving essential files such as the UXE, and NKpatcher on there, with the shadow C/eeprom. the dashboard i can leave on E as deleting that just requires a boot disk.
and of course yes i can do the upgrade myself, i am perfectly capable, and i do know what i am doing (well to an extent), but all it takes is one tiny mistake, and im in a very awkward position. this is why i wish to test out the boot process so to speak, though it would appear from the way the MS dash works, that i can only test out nkpatcher, which should be good enough.
QUOTE(krayzie @ Jan 3 2005, 08:27 AM)
If you are a member now for half a year and you post about basically everything you can come up with, why aren't you still able to do a simple upgrade yourself? also whe even upgrade to uxe if you allready got a working exploit. It can only cause more troubles.
QUOTE(anjilslaire @ Jan 3 2005, 09:38 AM)
lol, yes I know the difference between nasmw and nasm, and how to run from a cmd prompt
I would, just because of the way wordpad modifies the files before saving them.
Download the file again and try modifing with notepad instead.
No dice. Most of the errors are about the lba48 setting, but I haven't changed anything about it. Even tried recompiling "as is" without editing the inc file at all. No change.
Tried with notepad, wordpad, and textpad.
Hmm...
@Total_Ass you could do it first and ask questions later.
i am confused why you want to change, if you have a good thing going, why stop it.
lastly, could you run waffletools as an app, ftp in and replace your c:drive with your backup and then install UXE (that is what i would do)
QUOTE(anjilslaire @ Jan 4 2005, 08:19 AM)
No dice. Most of the errors are about the lba48 setting, but I haven't changed anything about it. Even tried recompiling "as is" without editing the inc file at all. No change.
I think I'd try a reinstall before buying a new PC!
QUOTE(nangsyde @ Jan 4 2005, 10:15 AM)
Also possibly try a slightly older version of nasm - this may just be me but it was churning out a chunk of errors for me with the latest release when I tried it, rolling back to an older version worked fine first time.
I'll try that when I get a chance later today.
Thanks.