Error in Loading OEM Layer DLL | developer.brewmp.com Error in Loading OEM Layer DLL | developer.brewmp.com

Developer

Error in Loading OEM Layer DLL

Forums:

Hi,

I've installed BREW Tools Suite v3.0.0 and when I started the AppLoader (right after it is installed), the following error message was generated:

"Error in Loading OEM Layer DLL: C:\PROGRA~1\BREWTO~1.0
\OEMLayer\QCOMOEM.dll. Exiting ..."

Can anyone help me with this problem?

Thanks,
amariska

It sounds like the QCOMOEM.dll is corrupt. Have you tried removing and reinstalling it?
- Skavenger

It sounds like the QCOMOEM.dll is corrupt. Have you tried removing and reinstalling it?
- Skavenger

Yes, I have already done that twice, but I still get the same error message. :confused:
-amariska-

Yes, I have already done that twice, but I still get the same error message. :confused:
-amariska-

I still can't run the BREW AppLoader in my computer. It's still generating the same error message (error in loading QCOMOEM.dll file) when I start the AppLoader. Does this problem have something to do with the settings of the computer, since it works fine in any other computers.
Could anyone please help me out with this problem? I really need the AppLoader to work.
Thanks,
amariska

I still can't run the BREW AppLoader in my computer. It's still generating the same error message (error in loading QCOMOEM.dll file) when I start the AppLoader. Does this problem have something to do with the settings of the computer, since it works fine in any other computers.
Could anyone please help me out with this problem? I really need the AppLoader to work.
Thanks,
amariska

We had a case of AppLoader version 2.1 stopped working after installing service pack 2 for winXP. i think the problem was some environment variables that got screwed up. here are the env variables i have that seem to be used by the apploader, you can check if you have the same ones
BREWTOOLSDIR
BREWTOOLSDIR300
BTILDIR
BTILDIR300
all 4 are set to this C:\PROGRA~1\BREWTO~1.0
i also have this added in my path C:\PROGRA~1\BREWTO~1.1\OEMLayer\Server
and i also have these Registry Keys that i know are important to run apploader
- HKEY_LOCAL_MACHINE/SOFTWARE/Qualcomm BREWTools/BREW Tools Suite v3.0.0
Default REG_SZ (value not set)
InstallPath REG_SZ path on computer
Publisher REG_SZ QUALCOMM
VersionInfo REG_SZ 3.0.0.12
- HKEY_LOCAL_MACHINE/SOFTWARE/Qualcomm BREWTools/BREW Tools Suite v3.0.0/3.0.0.12
Default REG_SZ (value not set)
hope it helps

We had a case of AppLoader version 2.1 stopped working after installing service pack 2 for winXP. i think the problem was some environment variables that got screwed up. here are the env variables i have that seem to be used by the apploader, you can check if you have the same ones
BREWTOOLSDIR
BREWTOOLSDIR300
BTILDIR
BTILDIR300
all 4 are set to this C:\PROGRA~1\BREWTO~1.0
i also have this added in my path C:\PROGRA~1\BREWTO~1.1\OEMLayer\Server
and i also have these Registry Keys that i know are important to run apploader
- HKEY_LOCAL_MACHINE/SOFTWARE/Qualcomm BREWTools/BREW Tools Suite v3.0.0
Default REG_SZ (value not set)
InstallPath REG_SZ path on computer
Publisher REG_SZ QUALCOMM
VersionInfo REG_SZ 3.0.0.12
- HKEY_LOCAL_MACHINE/SOFTWARE/Qualcomm BREWTools/BREW Tools Suite v3.0.0/3.0.0.12
Default REG_SZ (value not set)
hope it helps

How can I get the Registry Keys?

How can I get the Registry Keys?

run regedit
but you should be carefull if you want to edit them if you dont know what you are doing.
Everything else i mentionned was ok?

run regedit
but you should be carefull if you want to edit them if you dont know what you are doing.
Everything else i mentionned was ok?

I have all 4 environment variables.
I'm trying to add the path you mentioned: C:\PROGRA~1\BREWTO~1.1\OEMLayer\Server
But is it supposed to be BREWTO~1.1 or BREWTO~1.0?
Do I add it to the path in System variables or do I have to create a new user variable?
I'm still not sure how to run the regedit where can I find it.
Could you please help me?
Thanks,
amariska

I have all 4 environment variables.
I'm trying to add the path you mentioned: C:\PROGRA~1\BREWTO~1.1\OEMLayer\Server
But is it supposed to be BREWTO~1.1 or BREWTO~1.0?
Do I add it to the path in System variables or do I have to create a new user variable?
I'm still not sure how to run the regedit where can I find it.
Could you please help me?
Thanks,
amariska

hmmm you are right it's 1.1 in my exambple, means it's an old path for the 2.1 Tool Suite... so maybe it's not necessary, you can try it anyway with the right path.
for the rededit you open your windows start menu and select run, and just type regedit and enter. You will have a windows explorer like interface to check your registry. Im pretty sure it's there, it would probably not even start if you didnt have it.....
these were the things i set that could have been changed on your machine.... if everything is ok, i dont really see what else could be wrong... really looks like your QCOMOEM.dll is broken.... do you have toolsuite 2.1 and 3.0 installed on your machine? maybe somehow there is a path error and the Apploader 3.0 tries to open with the 2.1 dll....

hmmm you are right it's 1.1 in my exambple, means it's an old path for the 2.1 Tool Suite... so maybe it's not necessary, you can try it anyway with the right path.
for the rededit you open your windows start menu and select run, and just type regedit and enter. You will have a windows explorer like interface to check your registry. Im pretty sure it's there, it would probably not even start if you didnt have it.....
these were the things i set that could have been changed on your machine.... if everything is ok, i dont really see what else could be wrong... really looks like your QCOMOEM.dll is broken.... do you have toolsuite 2.1 and 3.0 installed on your machine? maybe somehow there is a path error and the Apploader 3.0 tries to open with the 2.1 dll....

I don't have the Tools Suite 2.1. I just have the 3.0 one.
I've run the regedit, and seems like I have the correct registry keys in my machine.
I've also added to the path C:\PROGRA~1\BREWTO~1.0\OEMLayer\Server
I don't understand why it still generates error when loading the QCOMOEM.dll.
Does it have something to do with the Port?
I don't have Communication Ports in my machine (I have only USB Ports, no Serial ports). If you open the QCOMOEM.INI, the default DeviceId is COM1. Could this be a problem also?
Thanks

I don't have the Tools Suite 2.1. I just have the 3.0 one.
I've run the regedit, and seems like I have the correct registry keys in my machine.
I've also added to the path C:\PROGRA~1\BREWTO~1.0\OEMLayer\Server
I don't understand why it still generates error when loading the QCOMOEM.dll.
Does it have something to do with the Port?
I don't have Communication Ports in my machine (I have only USB Ports, no Serial ports). If you open the QCOMOEM.INI, the default DeviceId is COM1. Could this be a problem also?
Thanks

That's possible.
To comunicat to the device with the apploader via USB cable, thee will be COM port created when you install the usb drivers and plug the device in. So maybe you could install and plug your device, find out what com port it's creating when your device is plugged, and set that com as default, and try again.

That's possible.
To comunicat to the device with the apploader via USB cable, thee will be COM port created when you install the usb drivers and plug the device in. So maybe you could install and plug your device, find out what com port it's creating when your device is plugged, and set that com as default, and try again.

My ini states DeviceId=COM10
because that's the last one i used. It's not a real com port it's a fake one created by the usb drivers.

My ini states DeviceId=COM10
because that's the last one i used. It's not a real com port it's a fake one created by the usb drivers.

The AppLoader works now in my machine :)
So the problem is with the ports.
Thanks a lot for your help. I really appreciate it.
-amariska-

The AppLoader works now in my machine :)
So the problem is with the ports.
Thanks a lot for your help. I really appreciate it.
-amariska-

Good to know this can happen, will know what to do if we encounter this trouble here.
Have fun Apploading now ;)
:)

Good to know this can happen, will know what to do if we encounter this trouble here.
Have fun Apploading now ;)
:)