i ve reported once the problem here :
http://forums.xbox-scene.com/index.php?showtopic=328837

and rmenhal, suggested that :
http://forums.xbox-scene.com/index.php?sho...dpost&p=2197611
(see the "EDIT" part of the post)

i softmodded 2 xboxes in the last 2 weeks using nkpatcher. one box was v1.0 and the other was a v1.6. on both boxes, unleashx worked fine as my default dash on shadowc. i was using unleashx v.37 build 543.

as far as running it from virtual F or G...why? why are you doing such a funky thing?
just run it like normal from E...sheesh

click here :

rmenhal has maybe found the bug in unleashx about being launched from a virtualized g drive

however it works from a virtualized f drive

and it s very useful when softmodding because :
all the exploit files are located on the real C drive and the virtualisation let me totally hide the real C (by setting "use F drive" to "no" to unleash and every other apps that have the possibility to see the f drive)

so, now, my friends have no risk to screw with the exploit

yes, i am aware of the purported reasons to virtualize C (hiding it from the user, etc.)

why would you virtualize F or G? in the post you linked, you said it was because you were using the stock, retail hard-drive, but i don't see why that is a good reason. you could put unleashx on E and run it from there.

there may have been a misunderstanding here, i dont speak english fluently, but what i mean was :
- my real C drive was shadowed to the G drive
- so G is a virtual partition (that s what i call virtualise G, but this may be incorrect), but unleashx doesnt work properly from here due to a bug described by rmenhal
- so i did the same thing but on F, real C shadowed on F, and i set F not to be used, so non accessible... and everything runs from it

i hope i m clearer

ok, you are virtualizing C. you keep the virtual C image on F or G. that makes sense. thanks for clearing that up. sorry to give you a hard time about it.

Ok as an outsider Opinion here you making a virtual drive of G: when you have no F: I'd say that if unleashX see's that you don't have a F: drive it dosn't even bother to look for G: since in the pre nkpatcher wor'ld that just dosn't happen if you have G: you must have F:

i said this too quickly, virtual drive F can't be hidden after all, maybe unleashx can't hide drive with content in it?

and furthermore, if i set F not to be used, mini icons in the "settings" menu doesnt show, but they appear when i set F to be used.

so as a conclusion, unleashx :
- can t load config.xml from a virtual G drive, but can hide F & G
- can t hide the partion F, where it was launched (the purpose of lastest nkpatcher, for a newbie friendly softmod experience : do not have the possibility to access vital exploit files)

It doesn't work on my G drive even though I have an F drive. I would very much like to see this bug fixed for the next release.

yes, you are still saying it too quickly. when you say virtual drive F, you must mean that you have a virtual C drive (shadowc.img) somewhere on your F drive...because it would seem crazy to actually virtualize F...what would be the purpose?
from the nkpatcher config.inc file:

not trying to bust your balls about your english, i'm just trying to make sure the problem is really understood...so it can be fixed.

when i speak about virtual f drive i mean : nkpatcher puts real c drive on f

and, in my case, every exploit files (unleashx too) are located on the real c drive even the shadowc.img

so after nkpatcher is launched : on the c, i have the content of shadowc.img
and on the f, i have the content of the real c drive

so now i just want to hide the f (by settting use f drive to no in unleashx settings) to avoid possible mess with exploit files but it s not possible, furthermore icons in the settings menu of unleashx aren t visible

but another thing now

when i do the same exact thing but on G, this time G is not visible, but unleashx can be launched by nkpatcher but cant load config.xml, so unleashx appears without any skin, or any other settings like network... (and still the same settings icons bug, they dont appear on the settings menu)
and we cant change/save any settings...

i hope i m clear enough

nkpatcher provides the facilities to hide partitions. why are you trying to hide the real C by mapping it to F and then disabling F drive support in unleashx?

so it sounds to me like you want to use a virtual C drive (shadowc.img) and hide the real C drive. if you wanted the real C drive hidden, why did you map it to F? with your shadowc.img on C, once the shadowc.img is loaded you will not see the shadowc.img on C and you will not see the real C because the virtual C (shadowc.img) has been loaded. doesn't that sound more logical?

i also want to hide shadowc.img

so shadowc.img is on the real c drive, so i m forced to locate real c to f or any other letter to allow the shadowing to be effective

indeed nkpatcher cant load shadow.img directly from real C to map it to a new virtual c

i'm pretty sure you are mistaken about many things in your post...but i will double check tonight by re-reading the documentation and actually putting the proposed setup on my box.

i had a little aim chat with someone for configmation...

1. you CAN have shadowc.img on the REAL c partition and nkpatcher will load it.
2. once the shadowc.img is loaded, the reall C partition is hidden. at this point, if you see a shadowc.img on C you can just delete it.
3. you CAN remap the real C to some other drive letter, though i'm not sure why you would need this, i've come to understand that it is a common practice, so...i won't try to disuade you from this...still seems ridiculous though if you want to sometimes hide it...by disabling the F drive in your dashboard. if you need access to the real C drive back to upgrade nkpatcher in the future, you could just boot a hacked gamesave. that's seems very convenient to me...unless you don't have one of the games...but if you're a soft-modder and you don't have one of the games...that's crazy to me too.

anyway, i'll shut up now and won't try to disuade people do whatever crazy things they want to do...because it's just crazy for me to try and do that

ok here i may be wrong, i wasnt sure at the time i was posting


why? because nkpatcher need to launch unleashx (located on the real C)
so without the remap, i cant have access to unleash (and no i dont wanna launch it from E )

ava and evox does it, so unleashx should do it cause ux does it better for all the rest

Hey Kyro , instead of using F or G drive ( Partition6=F or Partition7=G) have you tried mounting real C as Partition8 ? (there's no reserved drive letter for partition 8 as far as I'm aware).

That's what I'm doing with unleashx atm and it's working fine.

why Partition8 you may ask. The reason I use Partition8 is I use F & G for files. (320GB HD) while real C is mapped to partition8 it won't rob me of my files on F or G.

My shadowc.img is on real C, My real C is mapped to partition8 , my shadow C is 200MB with orig MS Dash and UnleashX.
In my shadowc.img I have placed pbl+M8 and in the config.xml in shadowc has a passworded menu item to launch pbl+M8 from unleashx menu. This way I can always get back to real C for editing and others I do it for don't accidently tamper with real C.

This works on standard xbox hd with no F or with F partition.
Once you put it together this way you'll be able to use your real C/shadowc on any xbox with any size HD with out sacraficing a useable partition and it'll keep others that use your xbox from changing real C by accident.

My 2 cents , but each his own.

my shadowc only contains the ms dash,

unleashx is on my real C,
on my retail xbox (so no f, and no g), once remap on f, g or patition 8, unleashx doesnt work properly :
- when real c is remaped to g or partition 8, unleashx cant even load its config.xml
- but when real c is remaped to f, it can load its config.xml but there are still little icon bugs (icons in the settings menu doesn t show)

now I can see why you got probs with unleashx while running a shadowc.img...

I have unleashx on real c as well (That's for when I boot pbl so I can get to real C when needed)
But I also have my unleashx in shadowc.img. I can only see nothing but probs running a shadowc but running the dash from real C while it's mapped to G.
Now I see where your coming from sort of.

What's the purpose/benefits of running unleashx from a hiddden mapped real C while running a shadowc.img? ... I'm missing something here I'm sure.

If you have Unleashx & orig MS Dash inside your shadowc.img and your shadow.img is on real C and you point nkpatcher to map real C to partition 8 , mount your shadowc.img on partition8 as partition2 © then unleashx doesn't miss a beat.

newbie proof installation, and then none of the vital exploit files could be removed by accident

??? that don't make sense to me... unleashx isn't a vital needed part to keep the exploit files proteccted....

If you hide unleashx config.xml and unleashx from the user (n00b or ol'skool) then it just means they can't configure their dash while shadowc is loaded.
That's not really a fault of the unleashx dash.

Even if a n00b deleted UnleashX or the MS dash out of shadowc then the xbox would still boot from disc be it orig game or an unsigned code disc ,so it still doesn't render the xbox/exploit useless.

The only way I can see the vital exploit files being deleted is if the user booted the xbox without running shadowc and deleted files on real c that are actually part of the exploit or if the eeprom hasn't been edited to stop a disc loading and it forced a dash update before nkpatcher loaded.

Sorry but I still don't see the point of running unleashx from anywhere outside the shadowc while shadowc is loaded.
It's just my thick head I'm sure.

That's enuff said by me.
Best of Luck.

smashly, thank you for being so articulate and having patience...my thoughts exactly on everything you've said...except i don't understand the need to re-map the real C to another partition if you do have unleashx installed in the shadowc.img...especially if you want to hide the real C anyway...

yes it is, avalaunch and evolutionx can do it without any problem (and those 2 dashboards can be configured even if shadowc is loaded


i know that the dashboard could be on E or in shadowc.img, and i know that a boot disc could resolve a possible deletion problem, but i just want the best newbie proof installation (it s just too bad to see a bug in unleashx that is not present in ava and evox)

noob proof? what happens when your noob decides to upgrade his dashboard switch to a different one? just think about an army of noobs who had someone else setup their xbox this way...coming to these forums trying to get help. can you imagine how much confusion it would create? i think this is an awful way to 'noob-proof' a box. noob-proofing should be done through careful menu construction imho.

bug? i wouldn't call it a bug. i'm sure this has to do with how the different dashes mount their partitions. obviously, unleashx made some different design choices than avalaunch and evox. unleashx was on the scene before nkpatcher and the ability to do all this crazy partition re-mapping and hiding. imho this is not a bug. it's an unsupported user configuration. i'm sure support will eventually be added if it makes sense. it doesn't make sense to me, but i'm just an idiot.

Your welcome

Reason why I would map my real C to a partition ( partition8 in my case) is if I don't map my real C when my shadowc.img is on real C then where would nkpatcher look to load/link shadowc.img as virtual C.
From what I gathered if you wanna run your shadowc.img it has to be on some form of mapped patition .... as partition8 as real C then my real C is hidden from current day apps dashes on patition 8 (no defined drive letter for patition8) and it doesn't reserve my F or G drive leaving them available for files that I wanna use while shadowc is loaded.

I found if I had my shadowc on the real C and I didn't map real C to a partition then my xbox just hung on boot , prob just me or something I missed, but I tried mutiple differant ways with shadowc on real C and the only way it worked for me was to map real C and load shadowc from the mapped real C.

wow did I type all that .. I'm gunna have to learn shorten my responses.
sorry about that.