QUOTE(xboxmods2977 @ Dec 29 2009, 04:37 PM)
This has got me puzzled pretty good. Weird problem you have here. It is almost as if, somehow your "Virtual C" from your previous softmod is still being loaded but I wouldn't think so.
I would try turning off any firewalls you may have running while ftp'ing to the xbox.
You could also try using a jump/key drive to transfer an ini file to the xbox HD to see if it becomes corrupted that way.
Another idea you can try is alternating the dashboard that is running when you ftp into the xbox, like ftp with evox running as the dash, zap a file over, and if corrupt, boot to unleashX and try again, Just to rattle off a few things off the top of my head that I would try in your spot.
For the most part, your problem doesn't sound TSOP related. It may just be coincidence that it is happening on your first (or latest) attempt.
Hope this helps, and be sure to let us know if you get the problem figured out.
Problem solved. Or rather a work around. Ofcourse I figured it out right after I posted my topic, but thats okay, maybe someone can find this solution useful.
I am not sure what causes this, but it seems like its an evox issue not liking my particular xbox. I don't see how it could possibly have anything to do with the virtual c, as the drives were formatted many times, and I also put a "never been in an xbox" drive and rebuilt it with the same issues, heck I threw in a 1TB sata for fun, also with the same issue.... But, you were pointing me to the right track with your UnleashX suggestion I think (this forum rox)... Anyways, the solution:
So, right after I posted my topic, I came across this thread here: link
. He had a similar problem with skin.ini file corrupting/emptying on him and solved it by using xbmc ftp instead of the evox ftp.
At first I thought, well, I have tried ftp Evox dashboard, ftp from Slayer, and ftp from Frosty's rescue disc. Then I realized, that all of those are still just Evox flavours. So I figured, I could install xbmc from slayer, and then run it as an application. But I thought to myself, well, I know how to install it, but how do I run it when I can't add items to my evox appication launch because of my ftping ini corrupting/emptying/clearing problem?
Then I remebered, frosty's rescue disc has a File manager on it that can launch SIMPLE xbe. I figured I will see if it can launch xbmc after I install it from slayer. So, in goes the frosty cd, under rescue applications, I choose the file manager and I pick xbmc, and it starts loading, but then hangs with no video. I expected that, because xbmc never liked being launched in that fashion (I think its because it has all these dependencies on other files and not just an xbe and ini file).
So, back to square one. But oh wait, that file manager on frosty has ftp capability! (I think it is just dvd2xbox actually). So I ftp in, I place my ing-bios.cfg file, and my evox.ini and evox xbe also in c. I clean all the other partitions. Restart, and bingo. FULL Evox dash loads up.
I go back into frosty's with the file manager, clear all drives, I put xbmc on my c:, edit ind cfg file to point to the xbmc xbe (default.xbe), reboot without frosty's. And I am greeted by xbmc! (being a softmodder for for the last 4 years, seeing my xbmc dashboard booting from my c: drive with nothing else in there but cfg file brought tears to my eyes)
What a nasty way to enter into the realm of tsoping! I hope my future endeavours are a bit smoother.
Well if you have any alternate work arounds, I would like to see them, or any other suggestions, at least something good can come of this adventure for future modders to see.
Thanks, and cheers