I am a long time forum reader, and a a fairly recent forum poster. I just want to start by thanking you all for such a great community, and the wealth of information and help available. I am hoping I can give back someday. But today, I ask for more help
I Recently dove into TSOPing. XBOX was a 1.0 stock drive softmodded (frosty's vga softmod). I sodlered the two points, and loaded latest evox with IND 5003 bios in the bios folder. Flashed it, and all went good. No problems.
Loaded slayer disc 2.7, formated drive (basically all is empty). I wanted xbmc as my dash, so I threw it on C: drive, and put the ind-cfg file in the C: and pointed the first dash to the xbmc xbe. Booted with a IND bios error "can't load dashboard". So I went back into C:, and went with the evox dashbaord. and it loaded. Except for some bizarre reason, it didn't read my evox.ini file properly. I got the dumbed down evox version. When I ftp and checked the ini file, I found it to be empty. Replaced it, rebooted, and same thing, it gets emptied again, and I get the dumbed down evox version.
Also, I tried to put the evox dash on e: and boot from there, so I updated the ind cfg file pointing to partition1 (E: drive), and I got the error "can not load dashboard". So it doesn't seem to read the cfg file. (in fact when I go in and look at the file, it is 0 bytes if I try to get it again through ftp). Also noted that without the cfg file at all, I also get the "no dashboard error"
After experimenting some more, I have come with the following conclusions:
1. An ind bios 5003 (a virgin one, not an injected one) NEEDS the ind-bios.cfg file to load the dashboard, and will give an error if it is not there in C: drive (can somebody confirm this?)
2. I think what is happening is that, for some reason my files are not ftping correctly, so I end up with a corrupt ing-bios.cfg, and then the bios uses the default dash location which is evoxdash.xbe in C: drive.
3. With evoxdash.xbe and its ini and skin files in c: and a ind-bios.cfg also in C:. IND bios loads the evox dash, but the evox that gets loaded is the dumbed down version you would get as if the ini file didn't exist or got corrupt. This further implies that I am not ftping text type files correctly (i.e. ini and cfg files). Additionally, if I try to run xbmc as an application, I get errors relating to .xml files (xml files are text type files, so they are not copying properly as well)
If anybody has any idea what is going on, please help me out. This is very frustrating. And just for the record, I have tried a different harddrive, with the same exact issues. I tried windows explorer ftp as well as filezilla. Same issues. I have also tried other bioses, M8 and X2 4xxx, they don't have cfg files like ind, but they had the same evox.ini issue.
I have also tried X2 5035, but it would just stop at the X2 logo screen. My guess it tries to load it x2config.ini file, but it can't because it is corrupt (because of my weird ftp problem), and stops there, it probably doesn't have a default that it can fall back to like ind, so just ends up hanging there.
For your referecne, I have no problem booting any rescue discs, frosty's, slayer 2.7, and a latest evox all work, so I can do stuff.
YOU ARE MY LAST HOPE! before I give up on tsoping for good.....
Thanks in advance.