Re: ISDN Error after reboot XPe
- From: "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT com>
- Date: Thu, 4 May 2006 08:47:36 -0700
Someone may have an answer for you here, but you've posted to a Windows CE,
not Windows XPe, newsgroup (microsoft.public.***windowsce***.embedded).
You'll have a better shot in an XPe newsgroup.
Paul T.
"Bas Biesheuvel" <athaphian@xxxxxxxxx> wrote in message
news:%23rZF600bGHA.2456@xxxxxxxxxxxxxxxxxxxxxxx
Hello all,
Together with a collegue of me, Im developing an XPe based target machine
with an ISDN application running on it. I first build the image with some
customized things in it and install it to the target machine and run the
fba. No problems whatsoever here. (The Reseal phase is set to 0 for manual
reseal). I reboot the machine, do not run fbreseal yet.
Now I install the ISDN modem drivers and I get three new devices:
An ISDN TA network card.
A VComm+ modem.
A VComm+ virtual com port.
The drivers seem to be installed and working and I have a working
capi2032.dll in my system32.
Next I install our own made custom ISDN application to dial out to a
number. And.. it works just fine. We get a connection to another phone in
the building.
Now I run "ewfmgr c: -commit", because Im using the ewf manager. And
reboot.
I startup the isdn application again to do a final test before fbreseal
and suddenly we get the following error:
"Invalid Information Element Contents"
A quick search on the internet shows that this is an ISDN related error
message. The 'Information Element' is said to be a block of data.
What we think is that somewhere between the hardware and our software
something went wrong in the modem driver or XPe hardware layer. That
because of the reboot, some elements did not get saved to disk or got
corrupted. Because of that, the communication between the ISDN devices
gets interpreted wrong on one of the sides, resulting in the error. But
what XPe component could be responsible for corrupting the data block
(either outgoing or incomming).
Does anyone know what I can do next? Am I missing a crucial component? Am
I using ewfmgr wrong? Should I make a new component of the modem driver
(because I havent succeeded in doing this)? Does anyone know what happens
during the reboot that may cause this failure?
Some additional info:
Same result on more images we tried.
Standard modem, unknown modem components are installed.
We seem to have the right components, since it works initially before the
reboot.
Target machine is on a VIA microboard with onboard everything, but I doubt
this is the cause.
ISDN Modem used: Sitecom DC-104 (but this modem works just fine on another
winXP pro installation, also after reboot.
Can anyone please help, we have a deadline for next week.
Regards,
Athaphian
.
- References:
- ISDN Error after reboot XPe
- From: Bas Biesheuvel
- ISDN Error after reboot XPe
- Prev by Date: SBOOT Problem in CEPC Platform
- Next by Date: Re: touch.dll
- Previous by thread: ISDN Error after reboot XPe
- Next by thread: getenv() equievalent in Win CE
- Index(es):
Relevant Pages
|
