Re: Error when running hello world
From: michel (anonymous_at_discussions.microsoft.com)
Date: 05/28/04
- Next message: Dante444: "Re: BIOS boot loader splash screen, invalid image"
- Previous message: michel: "Re: Error when running hello world"
- In reply to: Bruce Eitman \(eMVP\): "Re: Error when running hello world"
- Next in thread: Dean Ramsier: "Re: Error when running hello world"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 28 May 2004 12:06:03 -0700
I'll try to explain more clearly. I have a custom-configured image with a display. When I build a RAM-based Debug version I have no problem, it downloads to my target, I boot the target, and PB connects. When I build the RAM-based Retail version (retail kitl, no kernel debugger), I download, and during boot I get the errors regarding the missing ordinals:
Kernel debugger is waiting to connect with target.
0 PID:0 TID:0 Sp=ffffc7cc
Welcome to the Windows CE Shell. Type ? for help.
2459 PID:81bd0a0a TID:81bedb56 ERROR: function @ Ordinal 347 missing in Module 'coredll.dll'
2459 PID:81bd0a0a TID:81bedb56 !!! Please Check your SYSGEN variable !!!
2701 PID:81bd0a0a TID:81bedb56 ERROR: function @ Ordinal 353 missing in Module 'coredll.dll'
2702 PID:81bd0a0a TID:81bedb56 !!! Please Check your SYSGEN variable !!!
2836 PID:81bd0a0a TID:81bedb56 ERROR: function @ Ordinal 353 missing in Module 'coredll.dll'
2836 PID:81bd0a0a TID:81bedb56 !!! Please Check your SYSGEN variable !!!
3007 PID:81bd0a0a TID:81bedb56 ERROR: function @ Ordinal 353 missing in Module 'coredll.dll'
3007 PID:81bd0a0a TID:81bedb56 !!! Please Check your SYSGEN variable !!!
I can connect to the target using the Remote tools. I notice a bunch of different things including hte fact that the files in the /Windows directory are different (not all the files that should be in there for the Retail are there), and the Registry is depleted. The PID above points to device.exe so I imagine it's one of the drivers that's misbehaving. Since device.exe bails, the shell doesn't fire up and undoubtedly these 2 explain the Registry differnces.
The missing ordinals are RasEnumConnections and RasSetEntryDialParams (if you believe the output above). When I looked at the Registry I noticed only AFD and NDIS had proper Driver\Builtin settings, so I tried to follow the "order" field of the Driver\Builtins in the reginit.ini file and think that the culprit is autoras.dll as _it_ wants the above mentioned Ras... functions (but it also wants an additional one about which it doesn't complain).
Clearly I am floundering here. My target is a Logic PD LH7A400 board if that helps at all.
/michel
- Next message: Dante444: "Re: BIOS boot loader splash screen, invalid image"
- Previous message: michel: "Re: Error when running hello world"
- In reply to: Bruce Eitman \(eMVP\): "Re: Error when running hello world"
- Next in thread: Dean Ramsier: "Re: Error when running hello world"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|