: could this particular aspect of the installer also create the shadowc.img (that would nearly fill the C-partition)* so that the user wouldn't subsequently be at risk of dashupdate.xbe clobbering it entirely (unless they decide not to ftp the shadowc.img over)?
I am updating the installer.. with new installer, shadowc will be autometically created.. There will be three dummy file.. shadowc.img which is shadowc and 300MB, and one 50MB dummy and one 4MB dummy.. This will enable future user updates if they want like adding a new dashboard or adding something.. even if they want to install largest dashboard.. they can just remove the 50MB file to make the space..
2: I haven't checked, but if the virtualEEPROM isn't enabled already could it be (and pre-named) but not actually created, so that a "non-overwritable" virtualEEPROM results?
virtual eeprom is enable.. virtual eeprom patch will be C:/shadowc/eeprom.bin
3: could the "retail" setup be the default (instead of the "basic") so the user must uncheck things if they decide not to have the settings required for that?
I will look into installer documentation if it can be done.. ( I am sure I saw something like that but forgot where it is..
I tried the awesome "M$ dash conversion" feature; copied my 5960 (185ead00) to a folder, chose that folder name and it added the files into a sub-folder named C.
A directory is created not to mixup with other files.. anyway user has to delete the /C at the end..