chk = oem.checkfileexist("\\Internal Storage\\sdconfig.txt")
if chk == 1 then
runcc.addrun("RunExtra", "run", "\\Internal Storage\\sdconfig.txt")
but got an error when it was going to install a cab, so I decided to combine the use of RunCC and SDAutorun without the need for Mortscript to start SDAutorun (I still use mortscript for other purposes, just not to start SDAutorun). This way I don't need to figure out how much time Mortscript must pause before launching SDAutorun.exe.
I'm using RunCC 22.214.171.124 (although I don't know if it's official or from a leaked ROM since I got it from a WM6.5 Kitchen in Diamond ROM Development section).
I would like to try that RunCC 126.96.36.199 you are talking about here to see whether it works or not, if someone will be kind enough to attach it here.
So, here's what I did:
Following the tutorial in [REF] RunCC & AutoRun & SDAutorun [12-04-2009], I removed CheckAutorun.exe & CheckAutorun.lnk from the ROM OEM folders and the line in the initflashfiles.dat.
I also removed the welcome.lnk from the SYS folders and the line in initflashfiles.dat.
The contents of the key files used in my UC mix:
chk = oem.checkfileexist("\\Windows\\Autorun.txt")
if chk == 1 then
runcc.addrun("RunDefault", "run", "\\Windows\\Autorun.txt")
RunX.mscr (adapted to my needs from the original by Noonski)
The file copied to the startup folder which will run at 2nd boot and will delete itself after running.
Used to Run Welcome.exe (for screen alignment), deleting some unnecessary files no longer used, etc...
So, there's no need to include reset command in SDConfig.txt, or even to create a reset file with mortscript.
I hope I made myself clear on what I did (if not, feel free to ask).
Since I have very little spare time these days, this took me a while to complete and as usual in XDA, is still a work in progress. Also due to lack of time I haven't had the time to study this new XDA_UC method.
I don't mean to disrespect any of the work being done here; I just wanted to share my experience, and maybe provide a little more knownledge to this great community.
Also, I'm providing a zip file with my packages used for this method in case someone wants to use them for something.
Device history .: Magician | Prophet G4 | Trinity | Diamond | Diamond 2 | Desire HD :.
I didn't even know the
Well for starters it is going to be a lot easier to configure in the new way.
But your post does show one of my initial intentions more control over what happens when after a flash. And it confirms that not all versions of RunCC are as good as the one L3v5y is using.
In the first tests i did i could not get RunCC to accept
EXEC:\WINDOWS\SDAutorun.exe It just wouldn't run.
I then had one of my month and a half XDA Vacation stints because of a lot of bad luck.
Then when i started again i retried some stuff and found the mistake i made before that made me stop pursuing the silent install parameter for WCEload.
But then Cmonex put me on the right syntax for that and it changed my whole perspective on the case.
I posted to this forum because i would meet more cooks that would have direct problems from the new Rom Config setup. But the final version will be setup for older devices without RunCC to.
Thanks for your work here I'm trying this out now and will report back. I tried SDAutorun with RunCC and I put AutoRun in as well and while they would run the AutoRun would try to run sometimes before the RunCC and thus cause screen recalibration evertime a soft reset. If I got through the calibration and date fast enough and the RunCC started first it worked ok.
Glad to know many good chef and developers are working on this.
HTC One T-Mobile version Current ROM:Stock Carrier:Solavei
Own your Cell service. Say no to contracts and take charge of your service.
@Noonski, I got your invite to come look at this thread. I saw you stopped the group we were in. I apologize, I got busy trying to learn enough to finish S.V.I's Angel since he could not finish since his phone stopped syncing.
Just to let you know where I ended up with your ideas.
1) I still use the old SDAutoRun.exe since I wasn't sure what I would gain from trying the beta.
2) My Config.txt contains
I found I had to set attributes to not be readonly to get unzipall to work with nested subdirectories in the zip file. Also, if a file already exists, unzip fails and locks up. I'll have to post Mort about getting an overwrite = TRUE for unzipall.
RoryB.zip contains some files I want without having them in windows. For example the manuals for mortscript get unzipped to where I want them and there is only RoryB.zip in the windows folder. It also contains registry settings.reg such as network wizard settings to turn it on after the first boot instead of right after the hard reset. This avoids the notification during customization.
The foreach statement parses through registry key HKLM\Software\MortShortcut and and gets each parm and its value. It is similar to autoshortcut without adding another exe file. As an example the mxipupdate_QuickMenu_MortShortcut.provxml file contains
User_C zip and the reg file contains what it takes to have programs on sd card run without using the cab to install. Basically I unzip files to their correct folders and the User_C.reg sets the registry for the programs.
HTC is also switching from putting their autoshortcut links from provxml files and moving these to rgu.
Should save those extra unneeded provxml files.
This new setup should reduce a lot of the scripting for those not familiar with it. But again it's great to see how others are leveraging the added control in a creative way that suits them best.
But i have to say to others "Don't get get scared away" by some of the previously posted methods. The basis of the XDA_UC will be very easy to implement. But you'd be giving the hardcore tweaking part of our community a lot of freedom in adding their own customizations.
PS: Your using QuickMenu, cool, it rocks so much more in straight forward quick use. To bad it's not updated regularly. Hoping for a release to Get rid of that damn Manilla issue taskswitch issue.
Last night I realized I could move the registry settings to the rgu and get rid of the provxml. We do seem to attack this from different directions and end up at the same place or close to it.
I forgot to subscribe to this thread so I just now saw your posts as I went to mention this idea.
I'll need to add the delete registry key to my script.
I cannot download the OEM packages. I am trying to see your command line for wceload to see is there a way to force not asking where to install. That is why I still use sdautorun. If I could install cabs without having to respond I would use a mortscript line to do so.
The future certainly looks like it is full of wearables. … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?