I looked at that location in the installer and the "sid6" UX skin files are all there and I can see nothing wrong with them. The filemanager, loading and menu JPGs all work and there's nothing obviously wrong with the skin.xml that I can see.
I don't want to run the installer but I've copied the skin itself which should work as a standalone and if that loads it will at least confirm there is nothing wrong with the skin itself.
What happens when you run the installer? Does it revert to the UnleashX Default blue skin? That's what you'd expect if there was a UX skin issue.
EDIT
Confirmed: there is nothing wrong with the skin so if there is a problem with SID v6 selecting the SID6 UX skin it must be something else.
Last edited by ArchAngle on Sat Feb 19, 2022 2:04 am; edited 1 time in total
k0rkenzieher Xbox-HQ Newbie Xbox Version: v1.6 Modded: Xecuter 2.6 CE
Joined: Sep 08, 2020 Posts: 2
Posted: Fri Feb 18, 2022 2:40 pm Post subject:
there is a bug with the e drive dashboard. the wrong path in the xml:: UnZip" Arg1="E:\UDATA\21585554\000000000000\Files\unleashx.zip" Arg2="E:\SID_TMP\
correct path::
UnZip" Arg1="E:\UDATA\21585554\000000000000\Files\unleashx.zip" Arg2="E:\
[sorry for my bad english...]
ArchAngle V.I.P. Lifetime Xbox Version: v1.6 Modded: Xecuter 2.6 CE
Joined: Oct 03, 2014 Posts: 367
Posted: Sat Feb 19, 2022 3:07 am Post subject:
I think I've found the config.xml entry you are talking about.
What I question is whether you have used the correct path.
In my copy of SID v6 there is no "unleashx.zip" in the Files folder.
There is "unleashx-vcoff.zip" and "unleashx-vcon" and these are the entries in the the Config.xml:-
I am not qualified to troubleshoot a config.xml but it is clear from the fact the EvoX dash installs use the same "SID_TMP" path for the "Virtual C + eeprom" boot options and the "Standard" boot options use the "E:\" that these are correct.
I just checked SID v5.12 and instead of "SID_TMP" it uses "SID5" but has exactly the same syntax differences between the "Standard" and "Virtual C + eeprom" config.xml entries.
Do not ask me why but since both v6 and v5.12 use different paths for the "Standard" install and the "Virtual C + eeprom" boot install options I doubt very much that a mistake has been made.
|
All times are GMT |Page 1 of 1
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
HQ Network: 9,073 | 
Guests: 2031 | 
Members: 0 
Forums 
