hi,
please advise if i am wrong with my thoughts.
i think it is useless and a waste of performance to use LNK files (at least the ms ones).
lets have a look at the calendar.lnk:
if you want to launch the calendar app, you are launching first the calendar.lnk. the lnk file points to a registry setting (mscalendar). so the launcher (or systemhandler or whatever) needs to lookup there to findout what the programm-name and the required parameters are (in this case "poutlook.exe calendar". now after a while of doing nothing effectively the system finally begins to execute poutlook.exe calendar...
so whats the point of using lnk files?
i see so many launchers, programms even tweak utilities which make use of lnk files.
e.g. if you change one of your softkeys with a tweak utility to "phone", it does the same useless thing: it points to a link file instead directly to cprog.exe.
hopefully i am totally wrong but then please give me some advise.
thx
lnk is shortcut files
same as in windows
in windows if you want to start your program from the desktop
and dont want to copy the tons of files the exe file needs to start
to the desktop too you have a shortcut to the exe file
Some more on the subject:
The use of lnk files does not slow down the loading, in fact it can make it much more officiant.
Take Skype for example: it has a large executable (several MB). If you were to place that exe under "programs" to launch it it will take the system several seconds (quite noticeable period of time) just to find the icon inside the exe so even if you were just scrolling through your programs the device would appear to hang while the icon was loading.
A solution to that (which now became official part of the program installation) was to keep the icon in smaller exe (a resource dll or just plain ico file can also be used) and the lnk will "state" that the icon is not in the main exe.
Another use of the lnk files is the one you mentioned your self:
poutlook.exe calendar
Without lnk files you would be forced to type any parameters manually every time just like in the good old dos days.
By the way, the process you described, lnk-registry-exe does not take that long on current devices.
Just try launching a given exe directly and check if you notice any difference in lag.
If anything, it is the certificate check combined with relatively slow read speeds of flash memory that make WM 5 and 6 devices look sluggish.
levenum,
thanks a lot for your time and explanation.
sure, i was aware that lnk files help you to launch more easily programs with longer command strings when you use the default launcher.
but how about a different launcher (e.g. rltoday), where you setup once your config within that launcher. would you really point to the calendar.lnk file (which points to registry, which points to an exe file) instead of typing "poutlook.exe -calendar" directly into the launching path within rltoday?
anyway, if you say that there is no time lag, the discussion is more or less of "academical nature".
thanks
oliver
I am not familiar with rltoday, but it all comes down to how the programmer implemented the launcher.
There are two different commands, CreateProcess designed specifically to launch executable files and for that purpose only.
SellExecuteEx that acts exactly like a click in file explorer. The writer of the launcher has the option of which to use and I suspect they often use the second command.
The reason is simple: they want to give the user as much options as possible. If you want to bother and look up the exe and its command line, good for you, go for it. But what if you are a regular user who just wants to get that stupid icon on his today screen?
He wouldn't know or care about lnk->registry->exe. He just knows to look under windows\start menu\programs for something familiar.
Also having to interpret input of different types may be extra work so some launcher creators may want to only allow lnk and let the system understand and run their content.
That way they do not need to implement options for different icons, command line parameters and control panel applets.
............................................
.....................................
excellent work as always, thanks a lot!
Nice. Make as many options as there can be.
email settings
very nice, just installed so far so good. installed my cabs no problem, instruction to do this are pretty clear.
i have been reading about UC from slueth on how it install my setting for my email, not having much luck understanding, got it to install my cabs no problem. next i am trying to learn how to copy my email settings, i dont know if this can be done with this program? and if you can help me do this, its only 1 email account pop3 so not much info.
thanks
Lupe
Sounds cool, in fact, I liked it the first time, When it was UC. Just kidding I had to say it, just had to. I look forward to giving this a go when I have a moment.
JimmyMcGee said:
Sounds cool, in fact, I liked it the first time, When it was UC. Just kidding I had to say it, just had to. I look forward to giving this a go when I have a moment.
Click to expand...
Click to collapse
Thanks...I think
Let me take this opportunity however to say a couple of things about UC, and specifically how this tool is really for a different purpose.
First off, although UC is a nice standard, even Sleuth acknowledges that there is really nothing new in what he is doing with UC. He took some standard autorun.exe techniques and registry entries and bundled them to make a procedure that used to take 3 or 4 steps now take 2. UC adds nothing new, other than a standardized way to use autorun.
Also, UC mainly is meant for fully automated installs of a storage card. So, you pop your card in the slot, and sdautorun processes the sdconfig.txt automatically. UC can install CABs, provision XML and copy files (with limited success). However you must first set up your sdconfig.txt file and build your XML files manually or by exporting registry keys. You must set all this up beforehand in the sdconfig file.
SASHIMI takes a different approach in that you don't need to set up a config.txt file and it isn't bound to statically install the same things each time. In addition, since it can import reg keys natively (well, technically it calls another included app to do it, but it's all bundled in the installer) you don't need to go through the hassle of exporting reg keys, and then converting them to .XML (and optionally rolling them into a .CAB file).
Other advantages SASHIMI has:
In addition to running fully automated, you can choose to run only Manual, or Manual+Auto which will allow you each time to be prompted with a set of CABs and .REG files which you wish to install.
Customizing .CAB installs by tethering/binding .REG and .MSCR files so you can easily map additional configuration entries to a particular .CAB
Logging, so you can track what has been done
Transfer entire directory structure. If you have several folders with multiple subfolders you want transfered from storage you can do this easily.
Modular - the multiple directory structure allows for nice compartamentalization and organization of applications and configuration settings. Things aren't stored in static config.txt files or difficult XML. Simple .REG files, CABS, and optionally MortScript files if you want to use them.
All of these benefits come with only one drawback, which is inherent in this technique. That is it may not be fully automated. Of course this makes sense because if you want to be prompted about which CABs you want to set up or where you want to install them, you need to invest a little time answering prompts. I think the time to do this is considerably less than creating a config.txt file.
In addition, SASHIMI can be run using only Auto mode, in which case it is fully automated (and logged). In fact, it can even be configured to be run automatically when the SD card is put in if you so choose (I will be writing up instructions for that).
So, it really depends what you want to do. I honestly feel that SASHIMI can do everything autorun (and thus UC) can do and more. The exception is it can't import XML. I may update this by including autorun in the package and build this feature in as well. Personally, I think it's easier to work with .REG than .XML. UC however, has a slightly simpler structure which of course why it isn't as feature rich. I think it lends itself more to it's main purpose...which is to be cooked into ROMs and do a fully automated install at boot.
However, as the name implies, SASHIMI is a RAW installer and is meant more for users who want full control of what is getting installed (generally users who use lighter, uncooked ROMs and want to install more apps, etc.
Although, as I said everyone can use it. I think you really need to download it and run through the tutorial to see the power it has.
thx!
Awesome!!!!!! Been following your dev work on this and I should say this is a really great new level you've taken this package!!!!
Gonanaaa try this!
Thanks for this
Sashimi works great. You did a marvelous job of documenting it. Follow the directions and you have an easy solution for us flashing junkies....Bravo!
parleyp said:
Sashimi works great. You did a marvelous job of documenting it. Follow the directions and you have an easy solution for us flashing junkies....Bravo!
Click to expand...
Click to collapse
Thanks for your support.
Please feel free to make suggestions/bug reports/feature enhancements.
I couldn't think of anything else it needed at the time, but I'm sure it's not perfect.
On my list so far is:
Add support to use XML provisioning files (in addition to REG). - Not sure if I will put this in both Manual AND Auto modes...thinking maybe just Auto.
Writeup instructions, and maybe a little update that shows/updates the program to run in UC/Autorun mode. - This will allow it to run in auto mode as soon as the SD card is placed in the device (or a new device is started for the first time with the SD in the slot).
Integrate a config.txt / sdconfig.txt file so those of you who run UC can easily move/switch between both apps. Basically the idea is SASHIMI will process the config.txt file in addition to what it already does. It is kind of repetitive, since then you would be able to either import an XML through my methods, or just put your XML/CPY/EXEC commands in the config.txt file. Obviously if you ONLY use config/sdconfig.txt then there really isn't a need to use SASHIMI too, but if you want the extra options while still maintaining any work you did with UC then it's a go!
I would like to try to keep the app aroung it's central purpose, which is as an installer automater/helper app...so try to keep suggestions/recommendations around that.
thanks
better than uc, imho
thanks for you help bengalih, from your other thread, got my emails set up,
i used tiermanns Personal OEMizer to create my provisioning XML.
i then used the task manager you provided and bam, it worked.
this is why i believe SASHIMI is the best choice. i flash many roms, not all roms have the same programs installed, when i use uc i have to change my config.txt or i might install something that is already in the rom or i might miss something that is not in the rom. yea yea i know, cry me a river
heres what i like, i put my stuff in auto file, like my spb mobile, spb weather and a few others that no one installs because they must be purchased, then all my others in the "manual file" stuff like pcm keyboard, rss hub, htc end key, etc and google search which makes you stop and accept user agreement, if i have something in the manual file thats already installed in the rom you just flashed, just click no when it gets to it and on to the next cab.
i believe with sleuths uc if a cab requires a reboot it cant be used, for example i can put spb phone suite in manual and once completed it ask if i want to reboot, i select no and now it goes to the next cab, once im done with the cabs i want to install then i reboot very very nice
thanks
Lupe
overhaulengines said:
thanks for you help bengalih, from your other thread, got my emails set up,
i used tiermanns Personal OEMizer to create my provisioning XML.
i then used the task manager you provided and bam, it worked.
this is why i believe SASHIMI is the best choice. ...
Click to expand...
Click to collapse
Thanks Lupe...glad you got it worked out.
I am finishing up the next version, which will incorporate UC as well, so if users have an sdconfig.txt file they want to use it can also be used by SASHIMI (in reality I am calling UC's SDAutorun.exe to do it). So, it will be like a combined installer.
There still isn't a substitute for UC in terms of cooking it into a ROM to run automatically on first boot, but with my next version you will be able to use the sdconfig.txt and you will also be able to initiaze SASHIMI when the storage card is inserted. This makes it ideal if you need to provision alot of phones and each one is slightly different.
It sounds like you are taking advantage of the manual+auto install...great. FYI if a .CAB is already unstalled, then the following will happen:
1) If in Manual mode, it will ask you to remove the old CAB first and then it will ask you the location to install the new one. Of course you can always skip the CAB in manual mode if you don't want to reinstall.
2) If in Auto mode it will automatically remove the CAB and install it again.
Ah, one last thing...the Task Manager is DotFred's task manager, I can't take the credit for that application, and I will be sure to credit him in the next release notes.
Version 3.0 coming soon.
I'm finishing up version 3.0 to be release by end of week.
Here are the following updates:
v.3.0
- XML integration added! Use XMLs with/instead of .REG files to provision your device.
- UC integration and the ability to use sdconfig.txt files.
- Option to auto-launch when Storage Card is inserted.
- Better Log handling and INTEGRATED log viewer.
- Additional menus for less clutter and more choices!
- More status dialogs to let you know what's happening when.
- Ability to create/restore Program Menu shortcuts to any location.
- \Scripts and \Root directories available in both Auto and Manual modes for more control!
- Moved tandem/bundled .REG processing before .CAB installation for the ability to import registry entries prior to application install. .MSCR and .XML tandem files process after .CAB installation.
- Optimized code formatting
Let me know if there are additional options you would like to see.
Does the SDConfig.txt file use eliminate the ability to use the programs default folder based way of separating and installing? The program is excellent as is. But if I were shooting for the moon I would suggest adding ability to export personal information to .XML or .REG from current device for use after flash...
aadadams said:
Does the SDConfig.txt file use eliminate the ability to use the programs default folder based way of separating and installing? The program is excellent as is. But if I were shooting for the moon I would suggest adding ability to export personal information to .XML or .REG from current device for use after flash...
Click to expand...
Click to collapse
I completely agree with this. If you were able to have the tool create the .xml and/or .reg files from your currently installed ROM, it would make an excellent tool a killer app.
Thanks for the work!
aadadams said:
Does the SDConfig.txt file use eliminate the ability to use the programs default folder based way of separating and installing? The program is excellent as is. But if I were shooting for the moon I would suggest adding ability to export personal information to .XML or .REG from current device for use after flash...
Click to expand...
Click to collapse
No, the SDConfig.txt file is an ADDITIONAL step in the Auto phase.
So, after running either the Auto, or Manual+Auto modes the last step will be to process an SDConfig.txt file if it exists AND the option to use UC is enabled within SASHIMI.
I think that answers your question.
I did also add the option to do a backup of the entire registry to a file. But, your suggestion gives me an idea....
I can't really provide an interface with MortScript to do a selective backup of the registry, but what I may be able to do is read another configuration file. So, the user would create a file with the following format:
HKCU\Settings\Phone Settings\
HKLM\Control Panel\Sounds\
HKLM\Software\Application1\
Click to expand...
Click to collapse
Whatever keys are listed in the entries will be written out to a .REG file in the Manual\Reg directory and can then be imported if desired or moved to Auto\Reg.
Would that suffice for what you are asking?
That, my friend, would be EXCELLENT! This is an awesome application! Keep up the good work!
Thanks for everything, sir. I cannot wait to try this out.
Ok, I have implemented all the above features.
I just need to do a bit more testing and then repackage the .CAB and update the documentation.
Unless i get anymore feature requests/bug reports I will be upping this probably by Friday.
If any new feature requests are too complex (but worth doing) they may wait until next version.
I know at least one of you have installed a program before on your Smartphone that wasn't able to be found in the "Remove Programs" option under settings.
I'm havin' this problem with a program called "TopOCR-Mobile LE."
It was an .exe file that had to be installed on the device. So I did, and now I can't seem to remove it. I deleted the .exe under program files, but the blank icons still remain (there's two of them 'cause I thought I could be smart and run the .exe twice and it'd ask if I would want to remove the program; it didn't - instead it just installed it TWICE).
Is there a way to remove those icons? I already used Regedit's and Total Commander's search features, but I couldn't find any files with the name "topocr" or "mtopocr" (it's installation name).
What are my options (besides throwing my Kaiser against the wall or hard resetting)?
Where exactly do you see those blank icons that you are talking about
programs icons are located in
\windows\start menu\programs
it it's a program which auto start then
\windows\startup
PIE is working and connects through whatever means however it's not the same for quickgps. Even when there's no connection running it won't even try to start a GPRS connection. Forget activesync and wifi it's the same story. Assistance please
Make sure the quick gps service is running-it's launched by bootlauncher, and most task managers don't register it. XTask will show if it's working.
Nope, service is not running. What now?
You need this registry key.
Code:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\HTC\BootLauncher\Services\QuickGPS]
"Index"=dword:00000000
"Info"=dword:00000000
"Module"="\\windows\\GPSAux.dll"
"Order"=dword:000000ff
"Prefix"="GUX"
Pour favour, could you place all that into a REG file for me? I'm trying to input the values but the only ones I'm sure I got are "Module" and "Prefix".
Just cut-and-paste the full code I posted (inc. the Windows Registry editor bit) into a text file. You can do it on a pc or your ppc. Then change the file extension to .reg, and import the key with a registry editor like dotfred's task manager or phm regedit.
Imported the key and soft resetted. Confirmed that the service is NOT running as per the registry entry. However, I found a "QuickGPS app service(GUX0" running with most of the settings you gave me there in the registry.
2 differences:
- it's described as "dll for icon in TodayScreen" (yes, it's bull, i know)
- and entry called "Keep=dword:00000001"
help... still nothing
Well a hard reset worked and am gonna backup all QuickGPS related registry keys, but I really doubt that it's that simple. If this problem comes again I'll likely have to do this again.
Watch this space.