Database Users

n00b question about adding my own programs

Okay I understand you have to use mkrom and Linux (or cygwin on Windows) to roll your own ROM my question is regarding how one could say remove one program from the SE ROM and include something else, for instance take off the byte counter and put another different counter on or such, would you just copy the necessary files (.exe and dll's) to the files1 or files2 folder and that's it ? What more is involved? Thanks in advance!

for simple programs, that is all there is to it.
some might need more research, as to which registry settings need to be tweaked to get te program to run from the windows directory. and what settings it needs to run at all.

You copy the files to either files1 or files2. Both sets of files end up in the \Windows subdir. So if you do not want to copy the files to RAM (see below), you should make sure the program is set to run from \Windows. Then you add any necessary registry keys to "default.reg", and any file-copy or directory creation commands to initobj.txt. Then run "mkrom <ROMfile>" and hey-presto.

Thanks so much for all your guys awesome work!!

entropy1980 said:
ok sounds good, what would one need to do to mod the registry for the programs (By that I mean prior to booting) I don't want to be mucking around with a reg editor after the device boots just to get the progs to work...
Click to expand...
Click to collapse
Not sure I understand the question. Default.reg just holds the entire registry as present after a cold restart. So if you put something in there, this will be in the registry when the device wakes up.

I think we wrote at the same time , so you answered my question before I posted it !!! What you said made complete sense! Thanks!

entropy1980 said:
[...]so you answered my question before I posted it !!! [...]
Click to expand...
Click to collapse
I installed the phpBB telepathy mod a couple of days ago, so I guess it's working.

Hey I knew you were going to say that.... :lol: :lol:

hi,
i want to add the skelmir java virtual machine (thats default installed in windows\ceej) and copy the swingall.jar in the windows\ceej map.
I have the cab file of the virtual machine but i can't find out which files are in it (when i open it with cabextract is shows .001 files and not the files that i find back in the device)
please help me

Using Special Edition ROM, Tthe CabInst tool will run CAB files on the device if you move it there manually and double-tap it. It allows to set a new directory to install in.
Also the System Snapshot tool will write a file in the root of the device which holds a list of the entire filesystem and registry contents, so you can compare and see what changed. UltraEdit for the desktop has a compare function.
Good luck...

hi,
i installed it to a seperate directory and zipped the files. i also took a snapshot when the xda was fresh and after install. i only can't find where the xda's gets is files from in:
43 <! [\Windows\AppMgr]
8544 <! 31/12/2002 12:31 1632 FC0E9EE1 Skelmir CEEJ Virtual Machine.DAT
8576 <! 16/02/2003 23:10 27 AEBB1DF3 CEEJ.lnk
8587 <! 16/02/2003 23:10 40 1EAF4EB3 CEEJ Examples.lnk
8588 <! 16/02/2003 23:10 27 AEBB1DF3 CEEJ.lnk
because these are not in the map where i extracted the cab file too. maybe you can take a look for me and tell me what i have to change in mkrom to have ceej by default installed
the extraced cab map:
http://www.devosjansen.nl/xda/java installed.rar
the snapfiles:
http://www.devosjansen.nl/xda/xda snapshots files.rar
thanks in advance

laurens0619 said:
hi,
i installed it to a seperate directory and zipped the files. i also took a snapshot when the xda was fresh and after install. i only can't find where the xda's gets is files from in:
43 <! [\Windows\AppMgr]
Click to expand...
Click to collapse
These files are generated during the install process, and contain uninstall information. You do not need to write them if you install in ROM, since you don't need/want your programs to show up the in the 'Add/Remove Programs' dialogue.

ah i understand,
so i just put the files in the files1 or files2 directory and add this reg files to the default.reg? i dony really understand the readme file

ah little kick,
isn't also good for the next SE rom? because you have finally a java virtual machine on the xda and the app is freeware (got it from www.skelmir.com)

laurens0619 said:
isn't also good for the next SE rom?
Click to expand...
Click to collapse
Noted...

nice but can you please help me out for the moment? i dont know which part i must add to the default.reg file

laurens0619 said:
I dont know which part i must add to the default.reg file
Click to expand...
Click to collapse
default.reg holds the registry that is present when the system wakes up from cold-boot. So any registry entries your installer (or first run of the app) has made that you would like to have present should go in there. Clear enough?

almost
so i just copy paste the **** at the end of the reg file? and the files in the files 2 map
but how will the rom know where to put the files??
sorry if i'm stupid but i don't want to f*ck my rom so i can use me xda's as a frisbee

Yes, the registry entries can be pasted at the end of default.reg. It doesn't matter if there's earlier entries with the same values, since the latter ones override.
All files in files1 and files2 will end up in \Windows, and if you want them somewhere else, (where they'll take up RAM), you must manually copy them (or pre-made links pointing to them) by issueing commands in initobj.txt.
Take a real close look at initobj.txt, and you'll get the picture.

Wait Cursor

Hello everybody
I searched 10 times this forum but i could not find it
IS there a way to change animated wait cursor ?? in HTC wizard ??
I found this program http://www.pocketgear.com/software_detail.asp?id=14638&associateid=162
but i don't think it will work with WM5
thanks,
DNO

yes there is a way. the icon is in a dll. so you need a dll editor. there´s a topic here somewhere in the forum. i read it the other day. just can´t remember where. Just look for dll editor or something like that. i think vijay555 changed his once to a hamster. just keep looking.

Yes there sure is.
It is in GWES.EXE and can be edited using a resource editor (google for Resource Hacker)
There are 16 bitmaps in the Bitmap section, running from 1024 to 1039 for QVGA and from 1040 to 1055 for VGA.
QVGA resolution in 32x32, VGA is 44x44
So change them with the resource editor and copy back GWES.EXE to
your device.
Cheers

thanks tweakradje
got it and I sure knwo how to change pics in dll, and exe
thank you very much

I found only gwes.exe.0409.mui in /windows
is this the one ??
tweakradje
I think you are using WM 2003
becuae in WM5 there is no file name gwes.exe

dno555 said:
I found only gwes.exe.0409.mui in /windows
is this the one ??
Click to expand...
Click to collapse
could be in there also
I think you are using WM 2003
becuae in WM5 there is no file name gwes.exe
Click to expand...
Click to collapse
I think you need to extract it from a ROM.

the file gwes.exe does exist. i can see it if i´m in resco file explorer. but i can´t copy it. i always get an encryption error. and if i go through activsync i can´t see it. then i only see the one you see. with the 0409 on it.

freezor said:
the file gwes.exe does exist. i can see it if i´m in resco file explorer. but i can´t copy it. i always get an encryption error. and if i go through activsync i can´t see it. then i only see the one you see. with the 0409 on it.
Click to expand...
Click to collapse
same here

yes it is in gwes.exe.0409.mui (US)
Some examples can be found here:
http://4pda.ru/forum/index.php?showtopic=25257
EDIT 8 feb 2007: Check this out http://www.masellis.com/wait/cartoons.htm
Cheers

Been looking into this for a while here, but have had no luck in WM5. I had this great Cartman eating Cheesy-Poofs animation in WM2003 that was so much fun.
Both "gwes.exe.0409.mui" and "gwes.exe" contain the icons that make up the animation for the busy/wait cursor.
Using Resource Hacker I made the change for those 16 icons in gwes.exe.0409.mui. Finally got it to overwrite the existing file in the /windows folder by creating a cab that replaced it after a restart. Unfortunately, even though the new file is now where the old one was, I'm still getting the old animation.
Did the same with gwes.exe using Resource Hacker, but for the life of me, I cannot find anyway of overwriting the file on my PPC. When I tried to overwrite by using the cab file install method, I get a message that says the install was unsuccessful because I didn't have permission to modify the file. I wish there were some way to overwrite the file while it was resetting, or even after a hard reset. I spent quite a bit of time trying to find a way to replace it via the Kitchen Rom avenue, but I couldn't do it.
Any ideas?

Hi,
You only need to replace \windows\gwes.exe.0409.mui in this case (rename the old one first) Then after a soft reset the new animation will show.
Mui must be activated though. Check
HKLM\MUI
Enable dword 0x1
Syslang dword 0x409
Cheers

Thanks tweakradje for the tip to rename gwes.exe.0409.mui first. I removed the read-only and system attributes, then renamed it to .old and it accepted that! Then copied my new file over, and I've got my Cartman back!! Wahooo!

Nice to hear. Can you share it here?
I am always interested.
Cheers

Hi,
You only need to replace \windows\gwes.exe.0409.mui in this case (rename the old one first) Then after a soft reset the new animation will show.
Mui must be activated though. Check
HKLM\MUI
Enable dword 0x1
Syslang dword 0x409
Cheers
Click to expand...
Click to collapse
I did that and was able to replace the file with the new one checked the reg settings, I also removed the gwes.exe.0409.old file and I still get the old animation. am I missing something?
do I need to edit the gwes.exe file too?

Hi,
Check in your registry if the MUI values are present and that SysLang is set to 0x409. Of course the file must be in \windows.
No need to change gwes.exe if MUI is working.
Cheers

tweakradje said:
Hi,
Check in your registry if the MUI values are present and that SysLang is set to 0x409. Of course the file must be in \windows.
No need to change gwes.exe if MUI is working.
Cheers
Click to expand...
Click to collapse
i also have a problem doing it. i am sure registry values are right as you said. but when i'm trying to rename the file it just won't rename, or change attributes... i'm using total commander... any ideas?

can somebody please post the original here? WM5
I kinda overwrote it by mistake

leepriestenator said:
can somebody please post the original here? WM5
I kinda overwrote it by mistake
Click to expand...
Click to collapse
how could you overwrote it? it's in rom so as far as i understand thac cannot be done... someone please put some light on the matter ;]
i would post the original, if only i could copy it anywhere outside windows folder... :/

Please, how to rename the gwes.exe.040C.mui.
I try under explorer and Resco explore, I can't, when I change properties of files, it came back to system and read only.
Thx.
JaY

Seems that with my WM5 it does not want to work with the Reg OK and the MUI files changed. It is still going with the icons in GWES.EXE and I cannot copy it from my device to change those icons and EVEN if I could, I would have to copy it back!
Any ideas how to copy over my GWES.EXE?

ROM Chefs: SDAutoRun gives customziation to everybody!

User Customization is a config.txt file that's located on an SD card which can install cab & xml files located there too! Think about it: this gives anyone who loads your rom the ability to automatically install their preferred apps/settings as part of customization. Here's how to make your next ROM UC capable:
Cook the attached SDAutoRun.exe into \windows
if AutoRun.exe isn't already in \windows then place a copy there too. Note: some devices don't have a compatible AutoRun.exe. If you have issues, try the attached version.
Replace the "RST: Reset" line in config.txt with "EXEC:\windows\SDAutoRun.exe"
That's it! SDAutoRun will do the final reset unless it encounters a file called SDConfig.txt in the root directory of the storage card. If it sees this file, it will restart autorun and install cabs/configure settings from SDConfig.txt which can point to files that are also located on the SD card.
What's important is this: If every chef uses this system then ROM junkies will be able to freely move between ROMs. If you decide to include this in your next cooked ROM, then make sure you indicate that it's UC capable. I'd really like to make this a standard because it will greatly ease the time consuming task of re-installing apps/settings.
UC v2.0 is now Live!
Changelog
Works with non-WWE ROMs & Internal Storage Roms. SDAutoRun uses the registry to determine the default name for the Storage Card now. For newer devices, this key might be missing altogether so just cook it in. The "Folder" value points to the actual location that contains sdconfig.txt. Here's the key:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\SDMemory]
"Folder"="Storage Card"
Automatically corrects SDConfig.txt formatting errors. Extra/missing tabs, spaces, newline characters etc are corrected before passing to autorun.exe.
New string value "SDAutoRunVersion" created in HKLM\comm contains "2.0". This will help debug SDConfig.txt file issues in the user thread.
SDAutorun v2.0 is fully compatible with all SDConfig.txt files created to date. Additionally, there now shouldn't be a config file users can throw at it that it won't re-format to the following template:
Commands will be left justified into the first 5 characters and space filled
Parameters will be left justified to the 6th character and trailing whitespace will be removed
Lines that don't contain a command will not be passed to autorun. Note: To determine validity, I only check for a ":" in postion 4 or 5 here to allow for future command expansion.
if no valid commands are encountered, then a file containing only "RST: Reset" will be created
Assumptions
SDAutoRun is not signed so security must be relaxed in HKLM\Security\Policies\Polices by setting the value 0000101a to a 1.
SDConfig.txt cannot be Unicode.
Here's a link to the User's side of ROM customization:
ROM Flashing Junkies: User Customization is here!
If you build a UC capable ROM, be sure to link to the above thread. Also shoot me a PM and I'll add your ROM to the UC capable list.
The key here is that UC is an automated, unattended configuration. Setting it up is done out of the Hard Reset window and once its on your SD card, it works any time you hard reset. Automated is good because it allows mass customization from a business standpoint too. Any business using a UC capable ROM can set up a single "ROM customization" SD card then give it to their IT staff for the daily provisioning of company software/branding on new devices. Your UC capable ROMs have business appeal now!
We are also working on tools that will simplify the XML/SDConfig.txt file creation process. Several good ones have already surfaced in the Users thread.
Useful Stuff
OEM Package for Kaiser

I think this is/will be a great standard! Well done Sleuth for initiating this.

Genius idea.

Good news: doedoe is looking at building a provisioning tool! Now we have two developers working on this. We can sure use more help though. See the user thread for more info!

Good But What S About Cab Wich Prompt For Choosing Languages Or Some Parameters To Be Installed ?

UC
Very nice.
For flashing junkies it's necassary yes, after each flash all your favorit apps auto installed is awsom, nice one Sleuth

a request
can someone make it for all devices/ for example wizard? that will be awesome

Hehe many many thanks.
I tried to get this working with the standard AutoRun from SD but i couln't get it working.
Screw Extended Rom completly.
Great Work.
Making A bookmark.

character said:
can someone make it for all devices/ for example wizard? that will be awesome
Click to expand...
Click to collapse
ROM chefs should be able to use UC on any ROM. Post a link on your favorite ROM Chef's thread if you want to see UC.

SETOUF said:
Good But What S About Cab Wich Prompt For Choosing Languages Or Some Parameters To Be Installed ?
Click to expand...
Click to collapse
Those will need to be researched by the community. Post findings in the user thread (see page 1 for the link)

Awesome application.. so simple I'm amazed it took this long for someone to think of it!
I've cooked it into my ROM.. but I haven't released it so it cant really count as a UC compliant ROM..
It's definitely useful though and I'd love to see others using it. Thanks Sleuth

Already Found in Kin0kin ROMS
Great idea; however Kin0kin released a couple of roms some time ago that do this plus his final WM6 rom is also capable of auto install of applications off a storage card in this way.
WB

And why not change the reg
HKLM\Comm
\Extended_ROM\autorun.exe
and
\Extended_ROM\config.txt
into
\Storage Card\autorun.exe
and
\Storage Card\config.txt
Most ELF roms don't use Ext rom Auto installs any ways.
I still think this is a good cause because he's trying to get more people into doing this.
Instead of one or a few cooks integrating this.
Sleuth255 said:
sorry. AutoRun, by HTC design, cannot install apps to your storage card.
Click to expand...
Click to collapse
Well it shouldn't be hard to patch cab files hardcoded to a path on SD Card. (once i have found all my software back) But not something for a regular user nope.
Sorry to hear that Limitation still exists, seeing your actually using the Original Autorun.
I was allready removing this from my Roms.

Noonski said:
And why not change the reg
HKLM\Comm
\Extended_ROM\autorun.exe
and
\Extended_ROM\config.txt
into
\Storage Card\autorun.exe
and
\Storage Card\config.txt
Click to expand...
Click to collapse
that's pretty much what SDAutoRun does. It reconfigures the reg settings as you indicate and re-runs autorun. First however, it changes SDconfig.txt referenced cabs to RO since on a kaiser at least, the reg settings to prevent post installation CAB removal are ignored by AutoRun. Also, if no SDConfig.txt exists or there is no SD card installed, then it generates a quick one line config.txt containg the RST: command then re-runs autorun. On a Kaiser at least, the RST: command also re-activates the radio first. Without it, the device comes up with the radio disabled. I figured this scheme would maintain compatibility across all devices.
The standard is the important thing though as you indicate. You don't need to incorporate SDAutoRun in the manner I suggest. Whatever scheme works best for you is fine as long as it meets the following specifications:
user config occurs after all other autorun config
if SDConfig.txt is found on the storage card, set up the registry and re-run autorun
if SDConfig.txt is missing or there is no storage card installed then perform the final RST:
don't remove CABS from the storage card after installation.
I just thought my little 31K pgm was the easiset way to accomplish this. On deck is a way to do this even if the user renames the storage card...

Well looks like you can ad me to the list after monday.
I'm going to strip The new 6. rom to the bone and make some custom cabs hardcoded to SD card installation for the stripped Apps that can work from SD.

Cool... shoot me the link to your support thread when you do & I'll put it up on pg 1 of the UC user thread.

Regedit setting
Sleuth255 said:
HKLM\Security\Policies\Polices by setting the value 0000101C to a 1.
Click to expand...
Click to collapse
Can someone tell me what's "a 1"?
??[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101C"=dword:a 1??
or
??[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101C"=dword:a1??
Cheers

Strange that it's contain hardcoded paths ...! The name of my Storage card is Speicherkarte and so it's useless for me!

Probably a dumb question but where would I put this file in the base kit I have. I have a base kit for wm6.1 on titan. Ide love to cook up a rom but I dont know where this file goes.

smarvest said:
Can someone tell me what's "a 1"?
??[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101C"=dword:a 1??
or
??[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101C"=dword:a1??
Cheers
Click to expand...
Click to collapse
set the value "000101c" to a 1 ie:
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101C"=dword:1

How to write .rgu properly??

Hi, i have an Herald with the original windows mobile 6 executable i downloaded on a website and i extracted the RUU_signed.nbh, then i used Hypercore to get the OS.nb and then i got the OEM and SYS folders to start building my ROM the way i like it. First i thought about including my own registry modifications and i know those modification have to be installed in the device at the end of everything to over write the default that get install first so in the OEM folder i created a sub folder i called zzz_My_registry_OEM. As you can see, my attempt there is to put the .rgu file in there and because the name of the folder start by zzz, it will obviously be installed at the end. Is that right? Because if i'm wrong please tell me, i never did that before, its my first time cooking a ROM. Then, i face a new problem. I have the complete list of all the registry tweak i want to put in the .rgu file, i know i have to begin the file by REGEDIT4, the lines starting by ";" are not recognise so i can put a note of what the registry is for (for personnal reminder), then at the end of all my registry tweaks, i have to leave a blank line but... I just dont know how to write the lines properly because i know its some sort of code and i have to write in code. I'll show you precisely what i mean. Here i have a tweak to change the temp file to the storage card and it goes like this:
HKEY_LOCAL_MACHINE\System\FileSys
edit temp path key \Storage card\Volatile
Here an other one to change the language of the slide out keyboard to US:
HKEY_CURRENT_USER\ControlPanel\Keybd
create a new string
Name: Locale
Value: 0409
The problem as you can see, that is good if i tweak the registry of my already installed ROM from a registry editor, thats not valid for a .rgu file while cooking a ROM. But i have no idea how to write those codes properly and i found absolutely no instruction no where. And i have a lot more tweaks like that that i want to do. Is there any one here willing to link me to a detailed and intelligent tutorial or to translate my reg tweaks for me so i can finally nail that once for all? I thank you all in advance for your help. Anything could help because even if you dont have a complete answer, i'll do the job of reading the post and take all the bits together and figure it out. Some of you know a little bit that will complete some that an other one know to finally form the big picture.

[solved] No Customisation + Welcome.exe [email protected]

Device flashes - Device boots - Device runs the Welcome.exe, but then no Customisation.
Iv recently added some EXT packages into my rom. i made them myself from .cab's with cab2ext. ive tested the .cab's before adding to my rom, they do work. but some programs that did work before adding the new EXT's now dont because of no customisation eg, Task Manager - the one on the today screen and also Windows Live. (iv only noticed these two at the moment but there will be more, to be honest i cant be arsed looking for programs that work or dont work when its quite obvious its because of no Customisation, if i fix that, they will work again.. simples )
Anyway...
I opened the new EXT packages ive added and checked all the files.. eg, .dat .reg and all "FILES" files, i even checked the .lnk's and all seems ok. i then checked them again.. yet everything still looks ok, but something is seriously f*cked!
Also another problem, a wierd one..
When i Soft-Reset/Restart the device, it boots up with the Welcome.exe again? (the Welcome.exe is meant to only run the once and then dissable )
Help? iv almost got my rom the way i want it - ive been working on this rom for 2months and i dont want to start building the rom from scratch...
..again! pmsl
Does anyone have any idea what is wrong, if this has happened to you, how did you fix it?
Thanks!
Rn

Check your runcc.lua, then the conf*.txt files you include in your rom, then all the commands you execute inside them.
One of these commands go wrong in your first boot and so you are stuck on customization.
If you use xda_uc or another user customization method, check those scripts as well.
It may happen, for example, if you try to install a cab and for some reason it fails.
If in your recent packages you overwrite one of your conf*.txt file, this could be the cause.
Ciao

...
cheers dude, thanks for your time and help, i think i understand what you meen..
[1)config*.txt <-- all config files are ok.]
[2)runcc <-- googled and i dont use]
[3)xda_uc <-- googled and i dont use]
raving_nanza said:
iv almost got my rom the way i want it - ive been working on this rom for 2months and i dont want to start building the rom from scratch.....again! pmsl
Click to expand...
Click to collapse
its ok claros, f*ck it dude, its the second time this problem has happened to me, it happened on my first rom too.. (2months ago.lol)
i litteraly started again from scratch (a nice clean slate) ill just start my rom again like i did then which will solve my problem.lol ive got all my programs and setting backed up (*in a messy folder of messy folders )
my new kitchen will basicly be up and running again by the end of the day, its my birthday on wednesday so i may as well set it as the rom date.lol
Raving_1337_Rom_V3 (Alpha)
Cheers anyway dude, muchly appreciated!
Rn
[changed title to solved, @claros]

raving_nanza said:
its ok claros, f*ck it dude, its the second time this problem has happened to me, it happened on my first rom too.. (2months ago.lol)
Click to expand...
Click to collapse
This happened to me at least 20 times, or more
Let's check together what happen at first boot, if I'm wrong anybody else will correct me.
1) files are moved from \windows to other directory according to your app.dat / initflashfiles.dat.
2) .provxml files are parsed to change config values or filesystem
3) welcome is executed, but this command don't stop startup so:
3a) autorun.exe or runcc is executed too to customize rom: these package runs according to the commands inside various config*.txt files in oem packages or sometimes in ext packages
4) user configuration, usually included as a call inside one of conf*.txt files is executed. If you don't use xda_uc, user customization should follow the same syntax as autorun/runcc
5) Last conf*.txt file should include at least a
LOCK: Disabled and a reset
At this point you should have completed the welcome wizard. If not, and your calibration data is not in registry, your are prompted again with welcome wizard at second boot.
Common errors during boot sequence are:
- wince.nls is missing
- app.dat / initflashfiles.dat error, such as creating subfolders inside non existent folders or statements not in unicode format
- registry / provxml errors during setup of welcome.exe itself, for example you disable the whole welcome wizard but don't write calibration data into registry
- chain error inside conf*.txt files, such as config.txt calls config_operator.txt which call config.txt, generating a loop
- a cab or command inside a config*.txt files cannot be installed, for example for lack of space or a missing certificate
What I usually do in these cases is:
- check platformrebuild log file for errors
- save my last tmp/dump folder to check what is really inside the rom and what is really overwritten by what
- If you can connect by activesync to device before reboot, explore the device itself, it's processes and registry
- recompile the rom putting semaphores inside app.reg files, .provxml files, config*.txt file. I usually add an ext package to be included as the last one (ZZZ_Claros_Fix) where I put a special app.reg, a .provxml and a modified copy of config.txt, config_operator.txt, config_end.txt etc etc.. If you don't have a diamond, you can boot without sdcard to avoid any sd_config.txt error
Starting a new kitchen from scratch for me is at least 20 days of work, I'd spend a day more finding a solution
Ciao

claros said:
This happened to me at least 20 times, or more
Click to expand...
Click to collapse
A Mortscript called Autorun.exe
V2 working again, Cheers!
*i started setting up a new kitchen then thought f*ck that!
Rn

Are you saying that you were cooking in mortscript, and the autorun.exe file from the mortscript package over-wrote the one from your OEM package? I think that happened to me once a while ago. I just left out the one from mortscript; I've never needed it before, anyway.

...
yeah a mortscript called Autorun.exe over-wrote my OEM Autorun.exe
i deleted it the mortscript, everythings sound now