S60 5th ed emulator startup failed

[hony]

hi all,

does the s60 5th Ed emulator conflict with something? every time I tried to start the emulator I got the message "epoc.exe has encountered a problem and needs to close..", I've installed several sdks of other versions abd they all work fine.

following is the log during the startup:

PlatSecEnforcement OFF
PlatSecDiagnostics ON
PlatSecProcessIsolation ON
PlatSecEnforceSysBin ON
PlatSecDisabledCaps NONE
0.000 Thread 00957468 created @ 0x957468 - Win32 Thread ID 0xf24
0.000 Thread EKern.exe::Supervisor created @ 0xa51c58 - Win32 Thread ID 0x1924
0.000 Thread EKern.exe::DfcThread0 created @ 0xa528bc - Win32 Thread ID 0x1204
0.000 Thread EKern.exe::DfcThread1 created @ 0xa52cec - Win32 Thread ID 0xcd8
0.000 Thread EKern.exe::TimerThread created @ 0xa533dc - Win32 Thread ID 0x1548
0.085 Thread EKern.exe::FlashThread created @ 0xa62c68 - Win32 Thread ID 0x17d4
0.480 Thread EKern.exe::MultiMediaCard0 created @ 0xa63dfc - Win32 Thread ID 0x19f8
0.490 Thread EKern.exe::NandThread created @ 0xa6eee4 - Win32 Thread ID 0x1b58
0.495 Thread EFile.exe::Main created @ 0xa6fcb8 - Win32 Thread ID 0x1cb8
0.495 Thread EFile.exe::Local-00a71d40 created @ 0xa72000 - Win32 Thread ID 0x1b5c
0.500 Thread EFile.exe::LoaderThread created @ 0xa73c90 - Win32 Thread ID 0xa34
0.500 Thread EFile.exe::StartupThread created @ 0xa742ac - Win32 Thread ID 0x188c
0.540 Thread E32STRT.EXE::Main created @ 0xa79c30 - Win32 Thread ID 0xfd4
0.545 Thread EFile.exe::Local-00a79d70 created @ 0xa7a030 - Win32 Thread ID 0x1d40
0.545 Thread EFile.exe::Local-00a7a324 created @ 0xa7a5e4 - Win32 Thread ID 0x1384
0.555 Thread EFile.exe::InitCompleteThread created @ 0xa7c95c - Win32 Thread ID 0x1d4
0.600 Thread HALSettings.exe::Main created @ 0xa7cf20 - Win32 Thread ID 0x600
0.600 Thread HALSettings.exe::Main Killed -12
0.610 Thread EFile.exe::Local-00a7c890 created @ 0xa7cb50 - Win32 Thread ID 0x1b04
0.640 Thread domainSrv.exe::Main created @ 0xa7d99c - Win32 Thread ID 0x1dcc
0.735 Thread SYSSTART.EXE::Main created @ 0xaadf8c - Win32 Thread ID 0x858
0.735 [STRT][S]: [TIMESTAMP] (3:54:35.730000 us) Begin S60 startup
0.770 Thread centralrepositorysrv.EXE::Main created @ 0xa7f9f8 - Win32 Thread ID 0x1b8c
0.790 [STRT][S]: [INFO]: Adaptation time limit = 30000000 us
0.790 [STRT][S]: [INFO]: Monitoring time limit = 60 s
0.790 [STRT][S]: [INFO]: Startup completion time limit = 20 s
0.790 [STRT][S]: [INFO]: Creating start list from file 'Z:\resource\starter.RSC'
0.795 [STRT][S]: [INFO]: Initializing Feature Manager
0.825 Thread FeatMgrServer.exe::Main created @ 0xa80874 - Win32 Thread ID 0x1950
0.870 Thread ecomserver.EXE::Main created @ 0xa81704 - Win32 Thread ID 0x144c
0.925 Assertion failed: Kernel must be unlocked
Function: Kern::HalFunction(TInt, TInt, TAny*, TAny*)
0.925 Assertion failed: Do not call in ISR context
Function: Kern::HalFunction(TInt, TInt, TAny*, TAny*)
0.925 Assertion failed: Kernel must be unlocked
Function: NKern::LockSystem
0.925 Assertion failed: Do not call in ISR context
Function: NKern::LockSystem
0.925 Assertion failed: Do not call in ISR context
Function: NKern::Lock
0.925 Assertion failed: Do not call from bare Win32 threads
Function: NKern::Lock
0.925 Assertion failed: Kernel must be locked exactly once
Function: NFastMutex::Wait
0.925 Assertion failed: Do not call in ISR context
Function: NKern::Unlock
0.925 Assertion failed: Do not call from bare Win32 threads
Function: NKern::Unlock
0.925 Assertion failed: Do not call in ISR context
Function: NKern::Lock
0.925 Assertion failed: Do not call from bare Win32 threads
Function: NKern::Lock
0.925 Assertion failed: Do not call in ISR context
Function: NKern::Unlock
0.925 Assertion failed: Do not call from bare Win32 threads
Function: NKern::Unlock


thanks!

[wizard_hu_]

You may consider sharing some details of your PC. Like the OS for example. Can it happen that you are using 64-bit OS?

[chirag_cel]

Hi,

You need to check RAM size as well. If RAM is ok then i think somewhat linking issue with perl script.

[hony]

Hi, thanks for your reply.

here are some details of my pc:

CPU: Intel Pentium 4 3.00GHz
OS: Windows Xp professional(5.1 build 2600)
System Model:HP Compaq dx7200 Microtower
Memory: 2GB

I've Installed all the necessary softwares including jre v1.6.0_10 and ActivePerl v5.6.1, and I also installed several other versions of SDK, such as S60v3 fp1, S60v3 fp2 etc. They all work fine.

I noticed that there are some "Assertion failed" in the log of startup:

0.925 Assertion failed: Kernel must be unlocked
Function: Kern::HalFunction(TInt, TInt, TAny*, TAny*)
0.925 Assertion failed: Do not call in ISR context
Function: Kern::HalFunction(TInt, TInt, TAny*, TAny*)
0.925 Assertion failed: Kernel must be unlocked

is it normal? or maybe it's the reason why emulator crashed,But what causes it?

[zoiks_guy]

Hi,
Your SDK installation path must be too deep. Reinstall your SDK in at a simple and short path, eg: c:\SDK and it shall work.
njoyeee

[fazevedo]

Hi,
Your SDK installation path must be too deep. Reinstall your SDK in at a simple and short path, eg: c:\SDK and it shall work.
njoyeee

That is correct. I had the same problem and the provided solution worked.

[stenlik]

Hi,

I do not know if your problem is same as I have, but to run 3rd FP2 and 5th Edition emulator I have to chanage boot.ini to be able to boot with NoExecute=OptOut or/and NoExecute=OptIn.

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows XP Professional OptOut" /fastdetect /NoExecute=OptOut
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows XP Professional OptIn" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows XP Professional Execute" /fastdetect /Execute

I have found it occasionally, as I had the same problem also with WinCE emulator:
http://forums.microsoft.com/MSDN/Sho...82429&SiteID=1

BR
STeN

[hony]

Hi,
Your SDK installation path must be too deep. Reinstall your SDK in at a simple and short path, eg: c:\SDK and it shall work.
njoyeee

Yes, it works, Merci beaucoup!!!

[enzam]

Ya, it works. Thnx