Topic: The Blackwar Installer (Read 1126 times)

triggernum5 · « **Reply #105 on:** March 02, 2005, 10:29:00 PM »

The main advantages of the new installer are shadowc and eeprom.. There are a few oher things not possible with pbl..

kazpox · « **Reply #106 on:** March 04, 2005, 06:44:00 AM »

QUOTE(ChrisidPH @ Mar 4 2005, 12:22 AM)

two questions

kazpox · « **Reply #107 on:** March 04, 2005, 07:20:00 AM »

Issues w. the BWI1.3 007 installer:

Great installer! I have only experimenced minor inconsistencies.
Not a big deal, but I just thought I would report my experiences...

1)
When doing a restore stock C, it says that apps etc. will be wiped out. This does not seem to be the case. (But it should be mentioned that when I did it earlier on with BWI1.2 they the folders were removed.)
I am not sure what is intended here: To *only* restore C og also to clean E?
Anyway, it would be nice to have an option to restore C only, so that it is easier to do !Live management and then do the exploit reinstall afterwards and keeping files on E intact. (but maybe that option is already there?)

2)
When doing a reinstall on stock, the term "large hdd" is used in text. The text should probably be changed to "stock".

3)
After my last reinstall the folder CurrentDash held unleashx and a standard config.ini and not the BWI one. (Before the C restore/reinstall, I had put xbmc in that folder, so as to use it as default dash)

Also some more documentation would be nice as I don't consider it to obvious what exactly the individual restore/reinstall options do.

But again: Great work!

BlackWar · « **Reply #108 on:** March 04, 2005, 08:58:00 AM »

QUOTE(SuicideUZI @ Mar 2 2005, 08:01 PM)

So anyway could someone explain in retard terms what advantage this installer has over older installers such as ltools with PBL?

BlackWar · « **Reply #109 on:** March 04, 2005, 09:07:00 AM »

To play on xbl, it MUST be from a stock state. NO exploit can be running at all. even though it uses the shadowc function, xbl scans the xboxs memory, and it will find the exploit loaded in memory. that is why that you MUST uninstall ANY softmod to go on live. You can "cold boot" from a game disk to go on live, but some say it works, others say they got banned from this. the choice is yours to try.

as for 007......lol, yea, there are some wording issues that need to be takin care of. what version of 007 are you using? I thought I found them all and fixed them in the latest, but I could be wrong. also, for the default dash after install, the reason why I did it this route is because it is your xbox, you can use what ever skin you wish. Thanks to jcupp114, a custom skin was made for this installer, and intended solely for that use.

and, yes, I changed it so that if you installed, un-installed and then re-installed, your apps and stuff will still be there (except for the dash). this is so you dont have to go through and re-install everything after you un-installed to play on live, hide the fact that its modded from your parents, ect.

SuicideUZI · « **Reply #110 on:** March 04, 2005, 11:55:00 PM »

QUOTE(BlackWar @ Mar 4 2005, 04:13 PM)

To play on xbl, it MUST be from a stock state. NO exploit can be running at all. even though it uses the shadowc function, xbl scans the xboxs memory, and it will find the exploit loaded in memory. that is why that you MUST uninstall ANY softmod to go on live. You can "cold boot" from a game disk to go on live, but some say it works, others say they got banned from this. the choice is yours to try.

I thought one of the features of nkpatcher10 was making it impossible to even access Live while the exploit was running, so doesnt that mean xbl would never be able to find the exploit loaded in the memory even if you decide to coldboot instead of uninstalling the mod every time?

krayzie · « **Reply #111 on:** March 05, 2005, 03:09:00 AM »

QUOTE(SuicideUZI @ Mar 5 2005, 07:01 AM)

I thought one of the features of nkpatcher10 was making it impossible to even access Live while the exploit was running, so doesnt that mean xbl would never be able to find the exploit loaded in the memory even if you decide to coldboot instead of uninstalling the mod every time?

KMA · « **Reply #112 on:** March 06, 2005, 04:54:00 PM »

After a long ass time of tryng to hotswap, i was finally able to put The BlackWar Installer
on my xbox. after i rebooted the xbox and loaded Mechassualt, i still can't run linux. wtf?

I am so frustrated with this. everything sounds so simple until you go to do it. everytime you advance, you get another obastcle and 100's off pages of more reading or another 100 doubts.

I am glad to say that when i put in "Fight Night 2004", and i allow it to play on "Demo Mode", you can hotswap at that point. it worked like a charm. I've been trying to hotswap for a long ass time and this is the first and only way i've been able to get the drive unlocked.

Regardless, whats the deal with this installer. what did i do wrong? i put the installer in xboxhdm disc. I put the udata folder in the e: folder of the disc. then i create the disc, do the hotswap, put file on to xbhd in udata, and still unable to run linux!!!! am i missing somethng or?

?

jcupp114 · « **Reply #113 on:** March 06, 2005, 05:01:00 PM »

Blackwar installer does not utilize linux. If you have blackwar installed then your halfway there. View the .nix OS on xbox to get info about the linux end.

The hdm disc does run linux but for a recovery stage. More-less a utility that saves "Beee Hinds" so to speak.
Take care
Jcupp114

jcupp114 · « **Reply #114 on:** March 06, 2005, 07:53:00 PM »

dantheman
Its in the works! The MA is a little loopy so its seems to be taking a little longer my man. Sorry for bustin in on this thread reply. Take care
Jcupp114

adam1972 · « **Reply #115 on:** March 06, 2005, 11:25:00 PM »

Not to beat a dead horse.. Using the 007 savefile I changed the X: to an E: on the savefile's config.xml because the previous attempts were giving me a blank C: partition.. I removes the Xploit and did the Reinstall Large HD (using E: instead of X:) and it still shows a blank C: drive.. I even tried copying the Original files back to C: from the E:/StockC folder and cold booted.. Still blank. I figure it must'v copied the files to the virtual C: and that the fully functioning C: partition must still work because the XBox still works normally.. ultimately does it matter that the contents of C: are NOT visible when I FTP into it? Or does it put some risk into running it this way?

1.6isabitch · « **Reply #116 on:** March 07, 2005, 07:40:00 AM »

Does this work on the 1.6 version?

BlackWar · « **Reply #117 on:** March 07, 2005, 09:27:00 AM »

this expoit should work on all versions of xbox pal and ntsc alike, because it uses the uxe exploit to run.

Before I get started on the SC one, I want to get MA fixed. I understand that this is frusterating to most of you, but please try to understand the frusteration that the MA users are going through. I myself made the mistake that being that the 007 went rather flawlessly, the MA one would also. I am sorry for this but we are working hard to resolve this issue as fast as possable.

007 is giving you an empty c:? the only reason why I can think of this happining is because you only changed one xml file from x: to E:. this installer package uses several xml files, and they all work together, so if you change one, and not the others (found in the zip files), this installer will fail on you. The 007 did not suffer the blank C: issue that I am aware of, only the MA did. I will look further into this just to be sure that there is no hidden issue in 007 that never came up until now.

adam1972 · « **Reply #118 on:** March 07, 2005, 11:37:00 AM »

BlackWar · « **Reply #119 on:** March 07, 2005, 12:20:00 PM »

besides, I am not sure if the bonus will fit the installer package, only time can tell....

Author Topic: The Blackwar Installer (Read 1126 times)