Related
i always tried to flash my rom using the new upgrade tool - when using old header and old tool, upgrade works perfectly.
You just have to edit the change.bat for your own demands. At the state you download it, it is configured to change header into T-Mobile WWE version.
click here
Code:
run change.bat first, then MaUpgradeUt.exe
André
I have the dutch T-mobile MDA Compact.
Will this patch work on it?
And with the upgrade do i get Swedish dialpad/keyboard?
Want to keep everything english if possible.
should work; guess you dont even have to edit the change.bat before excecuting.
you'll get a qtek dialer (which is only slightly different from the windows original since it uses a (nice looking) skin - the dialer itself is the same as the original)
if you dont want to have this stuff install you can skip installation via reset and install the things you wish manually.
André
Well the skin is no problem, i choose my own skins after instal.
But what worries me is that T9 is swedish after this upgrade?
Swedish words are useless for me, i want them english.
quappo said:
i always tried to flash my rom using the new upgrade tool - when using old header and old tool, upgrade works perfectly.
You just have to edit the change.bat for your own demands. At the state you download it, it is configured to change header into T-Mobile WWE version.
click here
Code:
run change.bat first, then MaUpgradeUt.exe
André
Click to expand...
Click to collapse
Did you tried it by yourself? Your change.bat is not complete, you forgot to convert nbf to nba. That's why change.bat do nothing.
Then, as I already wrote several days ago - I did the same what you are suggesting - old tool with new files. It crashed my device totally, I cannot do anything to repair. So, be careful
Thanks!!!!
I have edited change.bat with imate operator (CDL_404) and flashed successfully!!!! Work perfectly!
Thank you again!
@landau:
of course i tried it by myself. you may have noticed that the nba-files are already in the archive so they dont need to be decoded from any nbf files (actually that was the problem: xda3nbftool cant decrypt these new format nbf-files).
so just run change.bat and flash it!
@justifier:
t9 offers several languages, english, french, german, ... unfortunately no dutch. if you want dutch, just take the t9.cab out of your own ext rom and install it manually. after the upgrade you wont find any swedish things on your mda luckily.
quappo said:
@landau:
of course i tried it by myself. you may have noticed that the nba-files are already in the archive so they dont need to be decoded from any nbf files (actually that was the problem: xda3nbftool cant decrypt these new format nbf-files).
so just run change.bat and flash it!
Click to expand...
Click to collapse
Sorry, I downloaded rar archive from ftp://xda-developers.com/Magician/qtek_106_upgrade/ but there4 only nbf files, not nba...
some ****ing idots have changed the archive! who the hell is doing that bloody ****??? :twisted:
i'll upload it again.
there should only be ms_.nba and nk.nba in the archive (besides the update prog)
quappo said:
some ****ing idots have changed the archive! who the hell is doing that bloody ****??? :twisted:
i'll upload it again.
there should only be ms_.nba and nk.nba in the archive (besides the update prog)
Click to expand...
Click to collapse
no wonder I've got Country ID error....,
can you tell us after you have upload the actual rar files.. ??
Thanks in advance
Thanks quappo, it worked perfectly.
By the way, the UK version of the T-mob MDA Compact has id T-MOB005, not T-MOB101, so you have to alter that in change.bat to get it to work. For others here who're as clueless as me: to find your operator ID, all you have to do is:
1) copy getdevicedata.exe to your Magician and run it
2) look at \windows\devicedata.txt, it starts with something like: PM10A 0 A WWE E T-MOB005. Whatever you have instead of the T-MOB005 is your operator code, stick that in change.bat instead.
3) run change.bat
4) run the update!
archive is up now.
if new problems occur, please post here. we would have to secure the archive via password then :-(
arfster said:
Thanks quappo, it worked perfectly.
By the way, the UK version of the T-mob MDA Compact has id T-MOB005, not T-MOB101, so you have to alter that in change.bat to get it to work. For others here who're as clueless as me: to find your operator ID, all you have to do is:
1) copy getdevicedata.exe to your Magician and run it
2) look at \windows\devicedata.txt, it starts with something like: PM10A 0 A WWE E T-MOB005. Whatever you have instead of the T-MOB005 is your operator code, stick that in change.bat instead.
3) run change.bat
4) run the update!
Click to expand...
Click to collapse
good to hear that it worked for you
thanks for your instructions!
arfster said:
Thanks quappo, it worked perfectly.
By the way, the UK version of the T-mob MDA Compact has id T-MOB005, not T-MOB101, so you have to alter that in change.bat to get it to work. For others here who're as clueless as me: to find your operator ID, all you have to do is:
1) copy getdevicedata.exe to your Magician and run it
2) look at \windows\devicedata.txt, it starts with something like: PM10A 0 A WWE E T-MOB005. Whatever you have instead of the T-MOB005 is your operator code, stick that in change.bat instead.
3) run change.bat
4) run the update!
Click to expand...
Click to collapse
If i copy getdevicedata.exe i cant run it?
In the devicedata.txt i only see pm10a , nothing more.
Am i doing wrong something?
edit*** Ok should fitrst copy it to desktop and open with wordpad, can see the codes now ***
When i run change.bat i get 2 warnings about the nbf headers, Warning possibly wrong password bla bla .
Is this normal, or is something wrong?
Goes about ms.nba ms.nbf and nk.nba nk.nbf
quappo said:
arfster said:
Thanks quappo, it worked perfectly.
By the way, the UK version of the T-mob MDA Compact has id T-MOB005, not T-MOB101, so you have to alter that in change.bat to get it to work. For others here who're as clueless as me: to find your operator ID, all you have to do is:
1) copy getdevicedata.exe to your Magician and run it
2) look at \windows\devicedata.txt, it starts with something like: PM10A 0 A WWE E T-MOB005. Whatever you have instead of the T-MOB005 is your operator code, stick that in change.bat instead.
3) run change.bat
4) run the update!
Click to expand...
Click to collapse
good to hear that it worked for you
thanks for your instructions!
Click to expand...
Click to collapse
thanks for the instruction..., and thanks for quappo for the nba files...
you really did it man...., I have upgraded from O2 1.03 to 1.06 without any error..., many thanks...
still wonder how genius you are....
@justifire
warning is ok, proceed with flashing
[quote="JustifireWhen i run change.bat i get 2 warnings about the nbf headers, Warning possibly wrong password bla bla .
Is this normal, or is something wrong?
Goes about ms.nba ms.nbf and nk.nba nk.nbf[/quote]
Yes, that seems to be normal, I got it and it worked fine.
i've got an imate jam with wwe rom,but the txt file from getdevicedata shows only pm10a and wwe, no operator id. Does anybody knows what i have to write for operator id code?
pntzamaras said:
i've got an imate jam with wwe rom,but the txt file from getdevicedata shows only pm10a and wwe, no operator id. Does anybody knows what i have to write for operator id code?
Click to expand...
Click to collapse
See my above post.
U copy getdevicedata.exe to magician, doesn't mather wich map.
Click on this file with stylus.
Now browse to /windows/devicedata.txt ON YOUR DESKTOP PC and copy it to your DESKTOP.
Now you can open it with word or notepad and you will see that the code is much longer than what you see on your magician.
You gotta browse to the right in notepad to see the rest.
Good luck.
Does anyone have the Extended ROM Unlocker / Unhide Tool for the "Magician" or "Qtek S100"
zsa said:
Does anyone have the Extended ROM Unlocker / Unhide Tool for the "Magician" or "Qtek S100"
Click to expand...
Click to collapse
U mean unlock to R and W Extended ROM or just to share, to make visible?
Thanks for the reply, I mean Unlock + Unhide to Read/Write...
U know how to make it visible with no software utils and other stuff? I can tell you. It will let U to install that software from standart pack for your device, which you need - to optimize your PDA memory free disk space.
But this storage avaible only to view, not to store my files or delete it`s content.
Thanks URAN.
Yes, to view it would be helpful to view the Ext Rom, but i need to Modify the Extended ROM by placing my own files... I have a Qtek S100 and need to add files and hence Read/Write Access to the Extended ROM is also necessary.
I do need it too... but today I can only to make it visible. Actually I use Qtek S100 too.
So, what U need to do to make it visible:
step 1. Force HARD RESET
step 2. Pass all steps with adjusting screen. Then, it would be a short a short PAUSE, about 3 seconds. THAT`S IT!!! Do not look aside!!! It`s the sign to make step 3...
step 3. Force SOFT RESET - you should do it exactly during this pause. It`ll prevent installation of some of standart software tools (you can install `em later for your choice) and (!!!) hiding External ROM from your disks list.
That`s all.
All I can say - there is no any risk to damage your device.
Even Resetting is not necessary, just locate the file in your Windows folder ( it may be hidden, so don't use File Explorer on your PPC, but from your Desktop PC or Total Commander on your PPC) and tap on it. In File Explorer the Ext Rom folder wil be visible without any need to reset. Once you have done that, the next time you reset ( hard or soft) the extended rom will be hidden again. To counter that, just copy loadVDisk.exe from your Windows folder to the Sart-up folder, it will be loaded after every reset and the Ext Rom will stay visible.
Koksie said:
Even Resetting is not necessary...
Click to expand...
Click to collapse
I knew about this method, I tried it, but failed.
Koksie said:
...Total Commander...
Click to expand...
Click to collapse
Just installed this software on my PC. Can`t locate my Mobile with it... Do you know how to fix it?
If you look into Config.txt from External ROM, you`ll see why this disk become invisible:
Code:
Config.txt
===========================================
EXEC:\Extended_ROM\TPDisable.exe
CAB: \Extended_ROM\Delete_vdisk_shortcut_WWE.sa.CAB (this step hiding External ROM)
CAB: \Extended_ROM\Caller_ID_Magician_Generic_WWE_RC13.CAB
CAB: \Extended_ROM\SmartDialing_Magician_Generic_WWE_RC13.CAB
CAB: \Extended_ROM\PhonePad_Magician_Generic_WWE_RC12.CAB
CAB: \Extended_ROM\CAB-ArcsoftMMS-2.0.0.20-Magician-Generic-ENU-27Dec04.CAB
CAB: \Extended_ROM\CV2.41.386_WWE.CAB
CAB: \Extended_ROM\JMM101257_WWE_1004.CAB
CAB: \Extended_ROM\Patch_bthusb.CAB
CAB: \Extended_ROM\Version_WWE_106116.sa.CAB
EXEC:\Extended_ROM\TPEnable.exe
RST: Reset
===========================================
This file from Qtek S100. At other device list of .CABs can be different
WHat failed with this method? For me it worked perfectly. I located the file LoadVDisk.exe, executed it, moved it to the start-up folder and did a soft reset. Now I always seet he Ext Rom folder in File Explorer on my ppc. Can yopu tel me what went wrong with it?
I am sorry, I meant TotalCommander for PPC. I have that installed and it has more funcitionality then File Explorer. you can find it at www.ghisler.com (it is freeware)
Koksie said:
WHat failed with this method?...
Click to expand...
Click to collapse
dunno... just nothing has happen
There is a BIG PLUS of my method, is that you yourself choose what software from Extended ROM to install. You can get extra free disk space this way.
Remember, you can`t remove `em manually after they automatically install after Hard Reset.
All you need - is interrupt this automatic installation process starting after Hard Reset with Soft Reset.
URAN said:
Remember, you can`t remove `em manually after they automatically install after Hard Reset.
Click to expand...
Click to collapse
Not jet... (I mean modify the extended ROM)
A ROM Upgrade also modifies the extended ROM, so why can't anyone else do this (with a tiny intelligent program?)
Indeed your method makes it possible to customize you Magician and leave off Ext Rom apps that you don't like. If however you don't want to lose all data and are happy with the Ext Rom as it is, my method is easier.
Just to be sure we are understanding each other: Clicking the LoadVDisk.exe gives no visual output, you see nothing happen, untill you go to the root of your Magician in File Explorer and see the Extended Rom folder appearing there
I don't know if it's any use for you people, but i used the method that URAN is trying to describe to remove all T-Mobile extra's... Just noticed that idd the extended rom is visible.
Here's the content of my T-Mobile config.txt:
Code:
SHOW:\Extended_ROM\TMO_WallPaper.bmp
CAB: \Extended_ROM\Delete_vdisk_shortcut_WWE.sa.CAB
EXEC:\Extended_ROM\TPDisable.exe
CAB: \Extended_ROM\IntelliDialer_T-Mobile_WWE_RC10.CAB
CAB: \Extended_ROM\IntelliPad_TMO_WWE_B12.CAB
CAB: \Extended_ROM\Caller_ID_WWE_RC10.CAB
CAB: \Extended_ROM\Camera_Patch_WWE_B15.sa.CAB
CAB: \Extended_ROM\Zip_Magician_T-Mobile_WWE_B12.CAB
CAB: \Extended_ROM\EmailWiz_v1.01.0003_NL_1027.CAB
CAB: \Extended_ROM\MMS_2.0.0.13_WWE.CAB
CAB: \Extended_ROM\MMS_Setting_WWE_NL.CAB
CAB: \Extended_ROM\Java_10.1.2.57_WWE.CAB
CAB: \Extended_ROM\TMONL_CustomizeUI_WWE_B14.CAB
CAB: \Extended_ROM\Customize_101124.sa.CAB
CAB: \Extended_ROM\GPRSMonitor_WWE.sa.CAB
CAB: \Extended_ROM\UA_Profile_TMO.sa.CAB
CAB: \Extended_ROM\Patch_101123.sa.CAB
CAB: \Extended_ROM\Version_WWE_101124.sa.CAB
EXEC:\Extended_ROM\TPEnable.exe
RST: Reset
A screenshot of the contents of my extended rom directory is attached.
Just checking btw, now that i'm looking in that directory... There are a couple of patches that are probably imported to install right?? Obviously since i used the above method, all those patches were not installed.
Should i apply them or are they all just nonsence? (for example: should i install Camera_Patch_WWE_B15.sa.CAB?)
lak said:
Obviously since i used the above method, all those patches were not installed.
Click to expand...
Click to collapse
That`s right, they are not installed. If you understand what the every CAB is, you will customize your device perfectly.
lak said:
Should i apply them or are they all just nonsence? (for example: should i install Camera_Patch_WWE_B15.sa.CAB?)
Click to expand...
Click to collapse
I think U should, cause your Camera Patch is in autorun CABs list.
...as I understand, U already upgrade your device to 1.06.110
hey all,
I just got my hands on a JAM ( i'm lovin' it!!)
i've managed to get into the exrom, no hassle.
but !
I don't see the config .txt .
there are cab files, autorun.exe, setup.exe, and the TP enable/disable files.
will upgrading my device ROM to 1.06.110
in order to have one, or do I just manually create the config.txt.
and if i manually create it, will the setup.exe file need to be altered to recognise my additional cabs + config file ?
cheers !
I tried URAN's method and it works...
However I need to Modify the Extended ROM by placing some specific cab files for customization of the device...
Does anyone have a tool or know how to get Read/Write Access to the Extended ROM.
URAN said:
I think U should, cause your Camera Patch is in autorun CABs list.
...as I understand, U already upgrade your device to 1.06.110
Click to expand...
Click to collapse
Nope.. not yet.. I'm running the original T-Mobile ROM that came with my MDA, should i upgrade to the iMate Jam 1.06.110? I'm not sure after all that i've read around here..
zsa said:
I tried URAN's method and it works...
Does anyone have a tool or know how to get Read/Write Access to the Extended ROM.
Click to expand...
Click to collapse
i don't have any such tool.
however, i need to do the same thing in adding cab's to me exrom, so i'd love that tool aswell !
with the pda2k, there is a tool that unhides and unlocks the device.
but for the jam, it seems we can only unhide at this stage.
i've tried all the unlockers available, but none work.
it's a matter of finding the correct registry key i think.
How to change T-mobil skin to O2 skin?pls some help pls.
-Copy this file to your storage card
-Run this file from your PPC.
-Restar your PPC- O2 startup screen.
Fedo said:
How to change T-mobil skin to O2 skin?pls some help pls.
Click to expand...
Click to collapse
I would also like to know how to install a .cab during Customization (in 3 seconds). Does anyone know how?
anyone?
What do you mean by converting a .tsk????
Just put the .tsk in the OEMOperators Package instead of the one the ROM does and change the config file...i
yeah, i dont think that "convert" was the best word choice, but i basically just wanted to use a custom theme in my rom and was wondering how to do that. ill give this a shot, though
ryncppr said:
What do you mean by converting a .tsk????
Just put the .tsk in the OEMOperators Package instead of the one the ROM does and change the config file...i
Click to expand...
Click to collapse
I can't find that package, where is it?
ok, sorry, I found it and changed the theme successfully. Now, I might as well ask this one question:
is there any way to install a .cab to the device while the device is configuring during the first startup? That way users can uninstall it if they want to?
im sory, but does anyone have the answer for this? im pretty sure laurentius26 uses it in his roms, but thid thread has had 150+ views and no respnses other than mine on one other one...
For OEM you could make an cab of it then use packages creator 5.4.exe Might not be the simplest solution but..
For UC use the cab you made above
Atleast now you have something to go on.
raiisak said:
For OEM you could make an cab of it then use packages creator 5.4.exe Might not be the simplest solution but..
For UC use the cab you made above
Atleast now you have something to go on.
Click to expand...
Click to collapse
is this the solution for the theme? because I have figured that one out Now I'm looking for a way to install .cab's when the device says "It will configure your device in three seconds."
opgadgets said:
ok, sorry, I found it and changed the theme successfully. Now, I might as well ask this one question:
is there any way to install a .cab to the device while the device is configuring during the first startup? That way users can uninstall it if they want to?
Click to expand...
Click to collapse
Use kaiserkitchen. Run KAISERKITCHEN.cmd and choose p option then open the cab. if you need more info read. All the info you need is here already.
opgadgets said:
is this the solution for the theme? because I have figured that one out Now I'm looking for a way to install .cab's when the device says "It will configure your device in three seconds."
Click to expand...
Click to collapse
Check config_operator.txt under kaiserkitchen\OEM\OperatorPKG
raiisak said:
Check config_operator.txt under kaiserkitchen\OEM\OperatorPKG
Click to expand...
Click to collapse
I can't seem to find that file
There are two methods you can use to cook a cab into the customization install.
To hardcode the cab into the install locate the config.txt and add a line for your cab. The formatting is pretty self explanatory once you look in the file itself, or to be more user friendly and allow used to decide whether or not they want to install the cab in the first place rather than just make it uninstallable go here and include the cab(s) in a separate UC package.
there is no reason for a .cab what so ever just put your .tsk in the rom dump (dont even use package tools) and edit the config to your .tsk its really simple as the config.txt all ready has a line that installs the defualt .tsk so just edit that to the name of your .tsk lets say custom.tsk
fiendz said:
There are two methods you can use to cook a cab into the customization install.
To hardcode the cab into the install locate the config.txt and add a line for your cab. The formatting is pretty self explanatory once you look in the file itself, or to be more user friendly and allow used to decide whether or not they want to install the cab in the first place rather than just make it uninstallable go here and include the cab(s) in a separate UC package.
Click to expand...
Click to collapse
Ok I'm going to go for the first method. Now, is the config.txt in the Tier Install Package folder?
anyone? all I want to know is how to install .cab files while the "device is configuring please wait..." during an initial hard reset/flash
opgadgets said:
anyone? all I want to know is how to install .cab files while the "device is configuring please wait..." during an initial hard reset/flash
Click to expand...
Click to collapse
We told you already mate...
Open: C:\kaiserkitchen\OEM\OEMAPPS\Config_AP.txt
You will se something like this:
Code:
CAB: \WINDOWS\CVC-PPC-WWE-705142-DopodPPC.CAB
CFG: \Windows\config.txt
CVC-PPC-WWE-705142-DopodPPC.CAB is actually cyberon voice command
Now what you do is:
1. Place youre cab here: C:\kaiserkitchen\OEM\OEMAPPS
(let call it: search4answer.cab)
Now you have search4answer.cab in youre C:\kaiserkitchen\OEM\OEMAPPS folder.
2. Open: C:\kaiserkitchen\OEM\OEMAPPS\Config_AP.txt
and insert the name of the cab.
Code:
CAB: \WINDOWS\CVC-PPC-WWE-705142-DopodPPC.CAB
CAB: \WINDOWS\search4answer.cab
CFG: \Windows\config.txt
Remember Config_AP.txt is locked, unlock it and lock after you have edited.
Close all, and cook it up. Now youre cab will be installed under what you call 1-2-3 customization install.
The cab will be uninstable if you flaged it to be so.
GL.
raiisak said:
The cab will be uninstable if you flaged it to be so.
Click to expand...
Click to collapse
A little off topic, but i always wondered why chefs don't make most of their cooked cabs uninstallable. Coz' there's always a program or two (or 10) that you don't use, but you like the rom and stick with it. having a dosen programs you never use is a waste...
question to cooks
slovoflud said:
A little off topic, but i always wondered why chefs don't make most of their cooked cabs uninstallable. Coz' there's always a program or two (or 10) that you don't use, but you like the rom and stick with it. having a dosen programs you never use is a waste...
question to cooks
Click to expand...
Click to collapse
Bether rom performance when cooked in Metod above is not what we call "cooked in".
raiisak said:
We told you already mate...
Open: C:\kaiserkitchen\OEM\OEMAPPS\Config_AP.txt
You will se something like this:
Code:
CAB: \WINDOWS\CVC-PPC-WWE-705142-DopodPPC.CAB
CFG: \Windows\config.txt
CVC-PPC-WWE-705142-DopodPPC.CAB is actually cyberon voice command
Now what you do is:
1. Place youre cab here: C:\kaiserkitchen\OEM\OEMAPPS
(let call it: search4answer.cab)
Now you have search4answer.cab in youre C:\kaiserkitchen\OEM\OEMAPPS folder.
2. Open: C:\kaiserkitchen\OEM\OEMAPPS\Config_AP.txt
and insert the name of the cab.
Code:
CAB: \WINDOWS\CVC-PPC-WWE-705142-DopodPPC.CAB
CAB: \WINDOWS\search4answer.cab
CFG: \Windows\config.txt
Remember Config_AP.txt is locked, unlock it and lock after you have edited.
Close all, and cook it up. Now youre cab will be installed under what you call 1-2-3 customization install.
The cab will be uninstable if you flaged it to be so.
GL.
Click to expand...
Click to collapse
thanks a lot raiisak!
however, it's not working. For example, I placed a custom-made .cab file in OEMAPPS, then told the config.txt file to load that, but it didn't work. Any suggestions?
Oh, and I still can't figure out how to get the darned theme to load as the default theme...
hello,
I have a question about autorun.
After I have flashed my rom autorun starts to run but it doesn't install anything?
I have 3 files config, config_end, config_operator.
I thought maybe it is the name why it doesn't install.
I try different thing out to make it run but it doesn't work.
I have writed down what I have in these three files.
I'm also using checkautorun
config:
EXEC:\windows\AutoVer.exe
LOCK:Enabled
CAB: \WINDOWS\HTCMMSProviderCAB_20080506.CAB
CAB: \Windows\Opera_Skin.CAB
CFG: \Windows\config.txt
CFG: \Windows\config_end.txt
EXEC:\windows\CheckAutoRunt.exe
EXEC:\windows\2.mscr
LOCK: Disabled
config_end:
LOCK:Enabled
LOCK: Disabled
RST: Reset
config_operator:
LOCK:Enabled
XML: \WINDOWS\Menu_Operation.xml
CFG: \WINDOWS\config.txt
CFG: \WINDOWS\config_operator.txt
What am I doing wrong ?
I think you're messing up by calling out config.txt in config.txt, and doing the same with config_operator and config_end. Basically, you want one .txt file to lead into another, but it looks like you've got a loop going on. You can put the Reset command at the end of config.txt (I go straight to sk tools backup, restore my pim, then the device resets). So, just skip config_end. And I guess you should remove the 'CFG: \WINDOWS\config_operator.txt' from the end of config_operator, or just combine config_operator and config.txt.
I just use config.txt and add2config.txt (in each package where there's something running during customization-this works in EVK). Here's what my config.txt looks like:
LOCK:Enabled
EXEC:\WINDOWS\UnzipSkin.mscr
EXEC:\WINDOWS\UnzipVIO.mscr
EXEC:\WINDOWS\UnzipBing.mscr
EXEC:\WINDOWS\UnzipFNKBD.mscr
EXEC:\WINDOWS\UnzipGoogle.mscr
EXEC:\WINDOWS\UnzipWidgets.mscr
EXEC:\WINDOWS\StartMenuStartup.mscr
CAB: \WINDOWS\fexploreext.cab
EXEC:\WINDOWS\Unzip1.mscr
XML: \WINDOWS\zzz-Active Sync.xml
EXEC:\WINDOWS\Restore.mscr
EXEC:\WINDOWS\cleanup.mscr
LOCKisabled
EXEC:\Windows\skbackup.lnk
Click to expand...
Click to collapse
My actual config.txt in the kitchen just has this:
LOCK:Enabled
LOCKisabled
EXEC:\Windows\skbackup.lnk
Click to expand...
Click to collapse
The command queue just comes from a bunch of add2config's. I don't have all the other .txt files from the oem (the basic build is one of Da_G's kitchens).
You also need to have mxipupdate_oemoperators_107.provxml run during bootup-it has the autorun settings in it. I've tried removing this provxml and just adding the keys directly to the registry with an app.reg file, but then autorun doesn't work (tip: you can speed first boot by removing all the garbage in the provxml's and just cooking it straight into the registry. It works for reg keys, but you need the provxml's for databases and stuff like that).
<!--Autorun settings-->
<characteristic type="Registry">
<characteristic type="HKLM\Comm">
<parm name="AutoRunCFG" value="\windows\config.txt" datatype="string" />
<parm name="AutoRun" value="\windows\AutoRun.exe" datatype="string" />
</characteristic>
</characteristic>
Click to expand...
Click to collapse
thank you
Thank you for helping out.
I will try this out after I have some sleep and will respond back iff it works or not.
menomenic said:
Thank you for helping out.
I will try this out after I have some sleep and will respond back iff it works or not.
Click to expand...
Click to collapse
and the config_operator is first, at least by default, you can change that in registry. I just had a big trouble with autorun, find new facts about new autorun, downgraded to old one and wrote about discoveries here:
http://forum.xda-developers.com/showthread.php?t=684426