Post by: A Murder of Crows on May 14, 2006, 06:57:00 PM
Well, i'm finally trying to see what can be done about my X3/Krayzie's 1.1.1 dual mod setup....C drive doesn't have enough space on it for the apps to be happy when i run in x3 mode, and it is mainly due to shadowC.img being on the C drive.
what is the likelyhood of me moving ShadowC to the E drive instead, and still having the shadowc.img file hidden from the user?
thanx
Post by: xman954 on May 14, 2006, 07:10:00 PM
you can have it on E:\ if you want, it will be protected as long as NKP is running but you will need to recompile with that setting..
the user can see it when it is on E:\
Post by: A Murder of Crows on May 14, 2006, 08:42:00 PM
QUOTE(Nightbird @ May 14 2006, 06:28 PM) 
I have shadow c: on c: when running x3 without problems. Can't you leave shadow c: where it is and run your apps from e: or f:.
Try running avalaunch from E, like i do, with less than 2mb of space on C drive visible.....see what happens lol
xman - any word about the 128mb patch issue?
Post by: Ndure protagonist on May 14, 2006, 08:44:00 PM
(Albeit that's likely a non-issue for those with sufficient understanding to easily fix the real-C if it ever happens, of course.)
Post by: A Murder of Crows on May 14, 2006, 11:07:00 PM
What i REALLY need is a way to run a program at boot that forces the system to see the shadowc.img, load it as C and hide the real C.....the rest of the mod isn't nessescery at the moment, though it may be soon.
My eventual goal is to be able to run a Dual Modded system with a triple alt dash setup.....i use an X3 chip to enable the LCD screen i have and to change the flubber colors to match the Halo 2 case i have, and i have a distribution of Krayzie's installer that i want to be able to test out when the x3 chip is turned off.....
I'd like to have the chip utilize ShadowC and virtual Eeprom somehow, but trying to launch individual xbe files as the default boot xbe in the chip fails, causing black screen or error 21, or in the case of the nkpatcher xbe files, just launching the dashboard.
If there is a way to an x3 chip boot up an xbe file that loads a shadowC and virtual eeprom, then have it launch a dashboard, i'd be really happy.
Post by: A Murder of Crows on May 14, 2006, 11:33:00 PM
i noticed in the discussions surrounding the NDure discovery that it was POSSIBLE to use startup xmv files.
I'd like to do this (preferably with wmv files, but i'm sure i can convert them), but i haven't found anything in the thread yet explaining how....just that as many as 2 xmv files can be used.
Can you point me in the right direction for that?
thanx much
Post by: A Murder of Crows on May 15, 2006, 12:05:00 AM
Post by: A Murder of Crows on May 15, 2006, 12:48:00 PM
QUOTE(Nightbird @ May 15 2006, 08:33 AM)
You can flash a retail kernal to your X3 then boot up with the chip enabled which will utilize shadow c: and virtual eeprom and you will still be able to use your LCD, but you won't be able to have the custom flubber until you swith banks back to an X3 bios.
I figured that would work....it's difficult to lose the flubber now though...if there was just a simple way to color change a retail bios loaded on a chip.....
QUOTE
Lol. Just tried this and got the 'c: is full, things will stop working error message', but weird thing is everthing works. I only have 640k on real c:. This is caused by X3 bios looking at real c:.
Yep. That stupid error message completely messes me up when i need to work in Avalaunch, which isn't often, because i can't see behind it. man alive do i NOT want that stupid error there. I've been talking to people on the xecuter forums to attempt to see if they were going to release an updated firmware anytime soon.....now that xenium 24k is out, i may just jump the x3 ship. VERY dissapointed in them.
QUOTE
There is a work around and you can still use your LCD in Ava. Flash a retail bios to a bank on your chip.
Below is what i've tested. I've set X3 config live to boot Ava on F: and done same thing in the config.inc for NKpatcher:
X3 enabled with X3 1mb bios 3924 flashed to banks 1+2+3+4. Chip uses real c: and Ava gives the c: drive full message. Drive C: shows 640k free.
X3 enabled with X2 512k bios 5035 flashed to banks 5+6. Bios uses real c: and Ava gives the c: drive full message. Drive C: shows 640k free.
X3 enabled with 256kb Retail bios 5101 flashed to bank 8. Bios boots softmod and this looks at Shadow c:. Ava runs fine. Drive C: shows 120.5mb free. Can still use X3 LCD in Ava and XBMC but no custom flubber.
X3 disabled. Softmod boots and uses Shadow c: and Ava runs fine. Drive C: shows 120.5mb free. LCD stays off.
With your setup, is it possible to use the x3 on all systems you run across? I do a lot of repairs and currently need to outsource work on 1.6 boxes....i wanted that to change, but i use a 1.4 box personally. If the x2 bios on 5+6 is compatible with 1.6 boxes to do the basic repair stuff, i may have to copy your setup....
Though, i still feel that it would be easier to come up with an xbe that emulates the effect needed to use a shadowc. I'll have to look into config.inc for nkpatcher and see what all it does....if it is at all possible to come up with a way for the chip to make use of/load a virtual eeprom and shadowc, still keep my flubber colors and not have to switch/add more bioses to the banks, that's where i'd like to go....
eventually i want to have this system triple alt-dashed with Unleash at power on and xdk at eject for use of screenshots.....
the other thing i want to try to accomplish is to see if it is possible (by means of unleashx script or otherwise) to get a movie file played each time the xbox starts up. If anyone knows how i could go about that, let me know lol
Post by: Ndure protagonist on May 15, 2006, 12:54:00 PM
QUOTE(Nightbird)
Ndure protagonist. Do you know much space on c: the dashupdate.xbe needs to update and cock up the softmod? I've booted with everthing disabled(retail mode) and used fable lost chapters retail disc to try and crash the softmod. But obviously with only 640kb on my real c:, I get the can't update message, so the full c: is doing it's job.
I published my research and findings about that (when I posted as 'eh.'). However, krayzie's 1.1 is different in that regard because it uses a hacked version of the MS 5960 dash (which I do not support, due to its potential XBL usage ban/suspension risk via "Live Aware").
Post by: Ndure protagonist on May 16, 2006, 11:11:00 AM