ISDN Error after reboot XPe

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



.

Relevant Pages

  • Re: ISDN Error after reboot XPe
    ... You'll have a better shot in an XPe newsgroup. ... I reboot the machine, ... Now I install the ISDN modem drivers and I get three new devices: ... A VComm+ modem. ...
    (microsoft.public.windowsce.embedded)
  • Re: "Using XP Home Fax utility after setting up a network"
    ... Do you or do you not have an analog fax modem attached to an analog phone ... along the line while trying to configure the network access point through ... stand alone connection things operated automatically. ... > me offline and upset the ISDN connection that was already running. ...
    (microsoft.public.windowsxp.print_fax)
  • Re: "Using XP Home Fax utility after setting up a network"
    ... I can think of no reason you shouldn't be able to use the same analog phone ... line and analog fax modem with Win XP Fax as before you put in ISDN. ... > I have the usual set up on the ISDN, two cables which run from the phone ...
    (microsoft.public.windowsxp.print_fax)
  • Re: T1 VS ISDN
    ... ISDN is a dialup technology over a regular phone line using a special modem ... T1, because it is a speed designation, is always 1.54mbps both ways. ...
    (microsoft.public.windows.server.networking)
  • Re: Antwort an Daniel
    ... dann kannst Du auch mit ISDN faxen. ... mal von der Möglichkeit des digitalen ISDN-Faxens absieht, ... Also brauchst Du eine Hardware, die analog faxen kann, ... Es gibt einige Hersteller, die ein analoges Modem auf passiver ISDN-Hardware in Software emulieren, was dann zu Lasten der Performance des Servers geht und nicht immer hinreichend stabil funktioniert. ...
    (microsoft.public.de.german.win2000.networking)
Loading