IWiaLog still not working
I've asked this question a while back and no one seemed to know the
answer. But I have a bit more info this time.
I've built a WIA minidriver using the DDK compiler and linker. But for
some reason, I've not been able to output trace and warning messages
through system WIA log facility. I've enabled logging with the DDK's
Wia Logging Configuration Tool---I added the module and set the debug
output to full (level 3; trace, warning, & error messages enabled).
I've also tried directly using the IWiaLog interface instead of the
macros, to make sure the call is made. But no messages are output.
However, I CAN get messages written to the log as long as I specify
the WIA_ERROR flag in the call to IWiaLog::Log(). But if I specify
WIA_TRACE or WIA_WARNING, the messages do not get sent to the log.
That sounds as if something in Windows is configured to output error
messages but not trace or warning messages. And there is a place in
the registry for this at:
HKLM\System\CurrentControlSet\Control\StillImage\Logging\
I've made sure that my module appears there and that the level is set
to 7. And I've restarted the WIA service after making those changes.
But still no warning or trace messages. I've also set the levels to 7
for the modules listed under:
HKLM\System\CurrentControlSet\Control\StillImage\Debug\
although I don't believe that should have anything to do with it. It
was something to try.
So why is it that I can output only WIA_ERROR messages but not
WIA_TRACE or WIA_WARNING messages? It seems like it should be simple
but I can't find it. I hate having to debug the debugging facility. :( Tag: Windows XP bootup issue with wireless 802.1x Tag: 33111
low resource situation during IRP_MN_SET_POWER
Hello
I have modeled my power handling along the lines of toaster example in
the DDK. The example allocates separate work item and queues it to
handle device specific power handling which gets scheduled at passive
level. When I am running it with driver verifier enabled and low
resource simulation option turned on, I find that at times allocation
of work item can fail. Now as per DDK, the Device can never fail the
IRP_MN_SET_POWER IRP.
I am looking for suggestions on how to handle these and other kind of
resource failures that can happen during IRP_MN_SET_POWER.
Thanks in advance.
Puneet Tag: Windows XP bootup issue with wireless 802.1x Tag: 33106
capturing text information using a display driver
I am using DrvTextOut to capture the text information. However,
whenever I type anything on any editor I first get a DrvBitBlt which gives
the co-ordiante of the entire client area of the editor as the destination
surface and then only I get the DrvTextOut call. I want to know why the
DrvBitBlt call comes in this case and not only the DrvTextOut call. Is there
a way to distinguish this call from the DrvBitBlt which comes when there is
actual change in the screen.
Thanks,
Sachin Tag: Windows XP bootup issue with wireless 802.1x Tag: 33100
Setting Events???
Hi.
How can I SetEvents in the kernal mode which are initialised by the user
mode without completing the IRP.... so that the user mode can know that the
event is signalled?
Iam using a DeviceIoControl( ) in the user mode and this comes to the Kernal
mode as an IRP. DeviceIoControl ( ) is called in an asynchronous mode with
lpOverLapped ( with a handle to an event created in the UserMode) . When I
complete this IRP in the kernal mode the the event is fired and the UserMode
which waits in the WaitForSingleObject (for this event) gets processed.
Now I want to Set the Event (created in the UserMode) in the Kernal Mode
without completing the related IRP.
I have two questions...
If I send the event in the IOBuffer and extract it and set it using
KeSetEvent in KMD, does the WaitForSingleObject ( ) in UserMode fires????
Or
Is there any other mechanism, by which I can send messages to the UserMode
from the KernalMode without using IRP???
Thanks
Anand. Tag: Windows XP bootup issue with wireless 802.1x Tag: 33092
GetPaletteEntries
Hello!
Is it possible to determine the palette information of a driver within
application level?
Say, create and application then query for its default palette
information such
as PAL_BITFIELDS or PAL_INDEXED or the RGB value of the each entry in
the palette.
Thank you.
alvin Tag: Windows XP bootup issue with wireless 802.1x Tag: 33088
IEEE1394 Gapcount
I my 1394 network the gapcount changes sometimes dynamically to a low value
e.g. if I have three nodes in my network the gapcount will set to 7.
How can I be certain that the gapcount keeps the max value, that is 63?
Is there a registry setting that the IEEE1394 stack of Win2k and WinXP uses?
Or is it maybe sufficient enough to set the gapcount only once with the
IoControl call IOCTL_SET_LOCAL_HOST_INFORMATION using level
SET_LOCAL_HOST_PROPERTIES_GAP_COUNT?
Thanks in advance,
Ronny Tag: Windows XP bootup issue with wireless 802.1x Tag: 33082
Debug Symbols for WinXPSP1 FreeBuild
I downloaded the xpsp1sym_x86.exe symbol file Win XP Sp1
x86 Freebuild at
http://www.microsoft.com/whdc/ddk/debugging/symbolpkg.mspx
but when I try to execute it an error message box appears
saying
"xpsp1sym_x86.exe is not a valid Win32 application".
How do I get this to extract/load/work?
Also, where in the world can Win XP Checked Build be
purchased? Can this only be obtained by ordering from
Microsoft or are there particular CD-ROM retailers or
computer stores which carry it?
Thanks in advance.
Antranik Tag: Windows XP bootup issue with wireless 802.1x Tag: 33075
WPA problem under Windows XP
Hello...
I have developed wireless lan device driver.
Now I have tested WPA and there is a issue in the XP SP1+ WPA patch.
[AP environment]
AP - Athelos AP(a/g/b and supporting WPA)
: 11g/11b mode
: WPA-PSK, key=0x0123456789,cipher type = AUTO
: AP software 2.4.2.2
## Auto cipher means AP uses unicast cipher as TKIP and AES.
[Client environemt]
:Ahtelos a/b/g card, Intersil reference card,TI 11b cardbus
[sympton]
- in the 4way handshake, the XP does not send 4rd messages to AP.
- the 3 cards have same result.
- just changing the Cipher type as TKIP,AES and then there is no problem.
- but using FUNK WPA software(ver 2.22,Auto cipher) there is no problem.
--
Bruce
WLAN Card develpoment, R&D Center
Samsung Electro-Mechanics Co., LTD.
Tel : +82-31-210-6713
Fax : +82-31-210-5529
E-mail: brucejr@samsung.com
http://www.magicLAN.com Tag: Windows XP bootup issue with wireless 802.1x Tag: 33065
MS Word landscape - Portrait mix - w2000 Print driver
I have a problem with printing a Word 2000 document which has both
landscape and portrait. The document pages start in portrait, and
switche to landscape. For some reason, Word draws the first landscape
page as landscape, and the subsequent pages as portait.
I have watched the DrvDocumentPropertySheets function and the passed
in DevMode, and can see Word switch the orientation to portrait.
Anybody suggestions? Anybody?
thanks
Rollin
I am using Windows 2000. Tag: Windows XP bootup issue with wireless 802.1x Tag: 33063
Disk Filter Driver won't unload
When I stop my disk filter driver it receives a stop message and a remove
message, but it does not unload. I presume this is because it has not
released a resource that it has allocated. I've checked my code and can not
see any problems. If I omit to set the FILE_REMOVABLE_MEDIA flag then the
driver will unload, but windows will not assign a driver letter to the
device.
I assume that by setting the FILE_REMOVABLE_MEDIA flag Windows does
something extra that I need to tell it to undo, but I am unclear as to what
to do. Do I need to release the drive letter allocation somehow? Tag: Windows XP bootup issue with wireless 802.1x Tag: 33059
WINDBG 6.2.0013.0 Hang
Debugee is Windows 2000 SP4 system. Debugger is Windows XP
SP1 system running WINDBG 6.2.0013.0, com1, 115200. When
Win2000 system selects debug start, "Starting Windows"
progress bar goes to full sweep, WINDBG gets
to "Executable search path is", then both hang.
If Debuggee does not select debug start, startup is
normal, can login.
What might be hanging the debug session? Thanks. Tag: Windows XP bootup issue with wireless 802.1x Tag: 33056
Usb isochronous transmision error
Hello,
I have written a USB driver for a simple USB camera. The OS is Windows 2000.
I use isochronous mode for reading data basing on code from isousb (DDK W2k
example).
On my own machine all work well (I've Duron 1000 with sis Usb interface --
ohci?).
I've also tested driver using other computers (Celeron 400 + Intel usb
interface -- uhci ?, 2xPentium 3 600 with intel usb interface), and the last
one with VIA usb interface).
The results of testing wasn't good, after a few good received iso packages
occured packed with status code 0x0000009. As I read, it's means, that
system load is too high / cpu is too slow, but in all cases idle process
takes 40-60 % of CPU.
Even, if driver don't process received data, bad packeges occures.
I use the same pipe configuration, as orginal driver which works very good
on all of this configuration.
I set USBD_TRANSFER_DIRECTION_IN | USBD_START_ISO_TRANSFER_ASAP flag (the
same as orginal drv). USBD_SHORT_TRANSFER_OK make no difference. Also
reseting pipe don't help.
<<My brain is boiling now - please help...>>
best regards
--
Tomasz Berg
*** remove "x" from before and after "tomasz.berg" for direct email *** Tag: Windows XP bootup issue with wireless 802.1x Tag: 33053
devcon source from DDK
Hello.
I need to take a look to devcon souce code from Windows DDK.
Please send or post it.
Thanks,
Vlad Tag: Windows XP bootup issue with wireless 802.1x Tag: 33051
Can I support 2 disks on a single USB device using two interfaces
Can I support 2 disks on a single USB device using two interfaces?
I know you can't natively do this for COM ports, is there any similar
limitation for mass storage devices?
Thanks in advance,
Marc Reinig
System Solutions Tag: Windows XP bootup issue with wireless 802.1x Tag: 33049
reading from a HID device
I've got an application that's reading from my HID driver,
and most of the time there's no problems. But there seems
to be occassions when some of the packets the driver reads
in from the device, never make it to the application. I'm
using the system ReadFile, to get these packets, so I
thought I'd have sidestepped missing packet troubles. Can
this be avoided somehow? Any help would be appreciated!
benjamin Tag: Windows XP bootup issue with wireless 802.1x Tag: 33043
IM driver under Win98
Will an IM driver for Win98 work under WinMe also?
Where can I read about installation of an IM driver under Win98, I read
somewhere it's a bit tricky
TIA
Zuka Tag: Windows XP bootup issue with wireless 802.1x Tag: 33040
driver not starting failing with file specified not found in XP and 2003
Hello,
We are installing our product in XP and 2003. After the
reboot of the machine, we find that our drivers and
services are not started. The reason given in the system
event log is the file specified not found. The imagepath
in the registry is \systemroot\system32\drivers\[driver
name]. The file is in that path too. If we change the
file to some other directory like \systemroot\system32
\bob\[driver name], the driver is getting started. This
error is happening only in XP and 2003. We checked in the
System Information and found that the driver is being
pointed to the right path. Please let me know the
traces/logs/dumps or docs that you need to analyse the
problem.
Regards,
Ramki Tag: Windows XP bootup issue with wireless 802.1x Tag: 33031
IP address not setting with NDIS IM installed?
Hi, All!
What could be the origin to following problem:
When I change TCP/IP host address in the card properties with my IM
filter driver installed, ipconfig remain to show _previous_ IP address
(before change), and only when I uninstall my IM driver - ipconfig
starts to show _new_ IP address.
Say, at start (when no USB device plugged in) - ipconfig shows up
"0.0.0.0". Then I install IM driver and plug USB card in. Then I change
IP address to "192.168.5.239" and ipconfig still shows "0.0.0.0". When I
remove IM driver - ipconfig starts to show "192.168.5.239". If I install
IM driver back - ipconfig shows IP "192.168.5.239", but when I change
it, say, to "192.168.5.111" - it continues to show "192.168.5.239" until
I uninstall IM filter driver.
What the f*? I mean what could be handled wrong to lead to described
behaviour?
Thanks in advance. Tag: Windows XP bootup issue with wireless 802.1x Tag: 33029
Detecting PCI devices on Win98 and XP
Hi,
I am relatively new to the DDK and am trying to familiarize myself
with hardware detection and interaction.
Currently I am writing a little application to detect what devices are
on a users computer, and have run into a trouble spot. PCI devices.
I realize that with the SetupAPI, I can get PCI device information
from Win 2000 and XP, but I am looking for a more suitable solution
that would cover all Windows operating systems. I have done this for
the USB detection already.
Is it possible to code a one stop shop for PCI devices as well?
So - to boil it down, does anyone have any information concerning PCI
Device detection, and/or, examples that might put me on the path to
success!?
Thanks in advance,
Bert Grantges Tag: Windows XP bootup issue with wireless 802.1x Tag: 33021
Writing and Reading Directly to a Hard Drive
Can someone point me in the right direction as to how I can write directly to a location on a
harddrive and read directly from a location on a harddrive. Assume I know little to nothing about
low level hard drive communication. Tag: Windows XP bootup issue with wireless 802.1x Tag: 33014
Unable to be "WPA Capable" because of some OID handshake problem.
Hi,
I am developing a WLAN Ndis driver and use latest ntddndis.h. I have
applied Q815485 WPA Wireless Security Update on WinXPSP1a as mentioned
in WPA-Overview document by Microsoft. According to "IEEE 802.11
Network Adapter Design Guidelines for Windows XP, May 22, 2003" (pg 7)
I get a query/set OID_802_11_AUTHENTICATION_MODE as
Ndis802_11AuthModeWPA followed by 3 query/sets of
OID_802_11_ENCRYPTION_STATUS for Ndis802_11Encryption3/2/1Enabled.
After this I keep receiving query OID_802_11_ENCRYPTION_STATUS once in
a couple of minutes where I return Ndis802_11Encryption1Enabled.
I don't receive set/query on OID_802_11_ADD_KEY nor
OID_802_11_ASSOCIATION_INFORMATION. Due to which I am unable to get
'WPA' in Wireless-N/W-Prop->Association->N/W-Authentication dropbox.
Can somebody please tell why I don't receive ADD_KEY or
ASSOCIATION_INFORMATION 802.11 OID's. Is there anything else to be
done for being 'WPA Capable' ?
Thanks,
Ashirwad.
(One off the track observation is that the 802.11 OID's in ntddndis.h
are not #defined in ascending numeric order e.g.#define
OID_802_11_STATISTICS, OID_802_11_POWER_MODE, OID_802_11_BSSID_LIST.
This is just fyi.) Tag: Windows XP bootup issue with wireless 802.1x Tag: 33005
Physical Address
When I look at the allocated resources in the device
manager, are the memory ranges "Physical Addresses"?
Are these the same addresses that I get from the
PCM_PARTIAL_RESOURCE_LIST in my StartDevice function
before calling MmMapIoSpace?
Is it possible for two unrelated drivers to map the same
physical address? Can I intentionally send PCI transfers
to someone else's card through this method?
By the way, this pathelogical code is intended only as an
architectural test and not deliverable code. I'm trying
to write to the memory range of a bus analyzer. Tag: Windows XP bootup issue with wireless 802.1x Tag: 33002
EAPOL-Key and OID_802_11_ADD_WEP
Hello,
I was wondering if someone could help me.
I am trying to implement the EAPOL-KEY frame and have had
no luck so far.
This is the scenario:
After successful authentication I receive two EAPOL-Key
frames
EAPOL Key 1:
Type: 0x01 // RC4
Key Length: 0x05 // 40 bit
Counter: ... 8 bytes
IV: ... 16 bytes
Key Index: 0x00 // first bit is 0 so broadcast key
Signature: ... 16 bytes
Encrypted Key: 5 bytes ( decrypt using RC4key: IV+MPPE-
SEND-KEY which result in 0102030405 in my case).
EAPOL Key2:
Type: 0x01 // RC4
Key Length: 0x05 // 40 bit
Counter: ... 8 bytes
IV: ... 16 bytes
Key Index: 0x83 (10000011) // first bit is 1 so unicast
key which is mapped to index 3
Signature: ... 16 bytes
Key: 0 bytes so I use the last 5 bytes of the generated
MPPE-Recv-Key
What am I suppose to set for the index using the
OID_802_11_ADD_WEP in both cases?
I read the MS documentation but got confused...
You have two keys:
- per-client key, used to send info to the AP
- global key, used for broadcast to AP clients, but also
for unicast.
But in the index definition they state the following:
Bit 31 of the Index is the key used to transmit to the AP.
(global key????) Bit 30 of the Index is the per client key.
So when I receive the broadcast key (EAPOL Key 1) I should
set bit 31 and when I receive the unicast key I should set
bit 30?
I tried this btw, but as soon as I set bit 30 I get a
error back from the NIC: INVALID_DATA.
I am a newbie to the wireless scene so I think I am just
missing the basic use of multicast and unicast (global,
per client???) WEP keys.
Please educate me....
Thanks.
Tom. Tag: Windows XP bootup issue with wireless 802.1x Tag: 32993
NDIS Mux IM Driver : HCT Driver Verifier Test
Hi All,
I am developing an NDIS Intermediate Mux Driver for
WinXp/WS2003. I use Microsoft Mux sample code as base.
I had pass out NDIS test of HCT 11.2 Kit.
But NDIS test which is run as subtest of Driver Verifier
test of HCT, My Mux driver crash in 1c_Reset test.
1 . In my MpReset Routine I had not implemented nothing
but only written
*AddressingReset = TRUE;
return NDIS_STATUS_SUCCESS;
2. It crashes in 1c_Reset test of NDISTest(subtest of
Driver verifier test) for
OID_PNP_ADD_WAKE_UP_PATTERN OID (fd010103) after
MpSetInformation routine call for that OID.
Can you tell me that which way I pass my Driver
verifier test. One more thing that My driver pass this
1c_Reset Test for HCT NDIS Test but fail for same test
when run with Driver Verifier test.
3. Log :
==========> PtRequestComplete ....
=====================> PtCompleteForwardedRequest ....
PtCompleteForwardedReq: pVElan 82400D20, OID fd010103,
Status c0000001 -->NDIS_STATUS_PENDING
========== NdisRequestSetInformation ....
========== NdisMSetInformationComplete request set info
bfor ....
crash by calling ->NdisMSetInformationComplete(pVElan-
>MiniportAdapterHandle, Status)
where Status == NDIS_STATUS_PENDING
*** Assertion failed: NDIS_STATUS_SUCCESS == Status
*** Source File: d:\xpclient\net\ndis\sys\requestm.c,
line 1058
Break repeatedly, break Once, Ignore, terminate Process,
or terminate Thread (boipt)?
Paresh Tag: Windows XP bootup issue with wireless 802.1x Tag: 32992
GDIINFO's hpalDefault information
Hello!
The handle of the default driver palette can be retrieved through GDIINFO's
hpalDefault.
Is it possible to get the information of the default driver palette?
Say, how the palette was be defined such as PAL_BITFIELDS or PAL_INDEXED.
Thank you.
alvin Tag: Windows XP bootup issue with wireless 802.1x Tag: 32987
a question about PCSC driver under win98
I find I must restart PC after I plugged out the device
which is a PCSC USB driver.I traced into my driver.And I
found the resource manage had not called the
createclose .The function must be called after the PC is
restarted. Tag: Windows XP bootup issue with wireless 802.1x Tag: 32971
free large 1394 address error(2Mbytes)
i'm developing a data collecting card using the 1394 bus
interface,and the windows system is win2000 or winXP.i've
written a driver according to your sample "1394diag",it
can work well in win2000 without SP3 or SP4.but when i add
sp3 or sp4 to the win2000,or run it in winXP,there are
something error,in the driver,i allocate a block of 1394
address with the number of 2M bytes,the action is
success.but there is an error when i free the block of
1394 address,the return status code is 0xc000000d,it says
there are something error with the input parameters to the
IRP.Yet,when i only allocate 512 bytes 1394 address,i can
free it success.i wonder if you can tell me why. Tag: Windows XP bootup issue with wireless 802.1x Tag: 32966
regarding NDISUIO driver
hi all,
i changed the name of sample NDISUIO driver in XPDDK.
it is working in the machine where DDK is installed and is not working on
machine without DDK.
is there some dependency on DDK?.
also on this machine it is giving error code 259 (GetLastError())in
enumerate devices.
which is the error that no more data is available..
also i am using checked build of driver ...
regards
Tarun Tag: Windows XP bootup issue with wireless 802.1x Tag: 32964
Error_gen_failure
Hi all,
I am getting the error Error_gen_failure in the Dll when i try to access the
PCI driver thru DeviceIoctl API function.In this function i am passing the
handle to the device , a pointer to the structure as input/ouput
buffer.Please suggest me if i am doing anything wrong.
thanks
sai Tag: Windows XP bootup issue with wireless 802.1x Tag: 32953
one question about PNP(thanks)
I have finished one usb driver which is the driver of PCSC
Reader.
Now I want to promote my driver.I found some driver could
still make system identify the devcie after the device had
been plugged out.Then there is the icon of the device in
control pannel.How can they realize it?Who can tell me?
NOTE:the system will send irp_remove_device to the driver
when the device is plugged out.
Thanks a lot! Tag: Windows XP bootup issue with wireless 802.1x Tag: 32952
PCI PDOs.
Hi,
How do I gain access to all PDOs created by the bus PCI drivers without a
bus upper filter?
Currently, I'm using ZwQueryDirectoryObject to enumerate all names of PCI
PDOs and then calling IoGetDeviceObjectPointer to get the device object at
the top of the stack.
This works fine for some of PDOs. IoGetDeviceObjectPointer fails on others
(STATUS_INVALID_DEVICE_REQUEST) not matter what access type I passed in.
Is there other way to get access to PCI PDOs?
Thanks,
Calvin Tag: Windows XP bootup issue with wireless 802.1x Tag: 32946
CD ROM & CD RW drives not working
Hi everyone, sorry if this is the wrong place to post this but I'm having
little luck posting elsewhere and this seems to be the only place where
"drivers" is listed.
I have two different CD Rom drives (one is a CDRW) and they are from two
different manufacturers. It seems that I can WRITE to the CDRW, but neither
drive can read CDR's - ones I burned ions ago that used to read without
issues.
I recently installed service pack 4 and uninstalled it. Still, my drives
won't read the CDR's. I'm desperate as I have so much work I need to
retrieve from these CDR's.
Please, if anyone knows anything (even if you don't) please post & cc: me on
an email also - this way I'm sure to get it.
Thank you so much in advance. Tag: Windows XP bootup issue with wireless 802.1x Tag: 32945
Can't Microsoft stop the virus postings on their newsgroups?
The subject says it all. I thought these were managed newsgroups.
Where's the sysop to keep spam and viruses out?
--
Walter Oney, Consulting and Training
Basic and Advanced Driver Programming Seminars
Check out our schedule at http://www.oneysoft.com Tag: Windows XP bootup issue with wireless 802.1x Tag: 32943
How to enumerate all PDOs created by PCI bus driver?
Or How do I get the device object pointer from it device name? I've tried
ZwQueryDirectoryObject/IoGetDeviceObjectPointer. But it failed on *some* of
PDOs. How does OSR's devicetree enumerate all device objects?
Thanks,
Calvin Tag: Windows XP bootup issue with wireless 802.1x Tag: 32938
Toaster filter driver
Hi All,
The toaster filter driver of ver. 2600.1106 is implemented w/o
IoAcquireRemoveLock/IoReleaseRemoveLock brackets
The toaster filter driver of ver. 3790 uses
IoAcquireRemoveLock/IoReleaseRemoveLock brackets full steam
Why is this?
Is it an error in the driver of ver. 2600.1106 or more restrictive rules of
the game on Server 2003?
TIA
Andrew Tag: Windows XP bootup issue with wireless 802.1x Tag: 32927
Modem Driver - Carrer Detect Line
I'm trying to create a Windows 2000 driver for a GSM modem that I have.
The problem is that the modem has only the RX/TX/GND pins connected, so
windows is not able to detect the CD.
I managed to get the .inf file correctly, but I still have problems with the
CD, and I guess that because of that the PPP session never works.
The log file is attached. Anyone has any idea how to solve it?
Thanks ahead
09-24-2003 16:24:07.154 - File: C:\WINNT\system32\unimdm.tsp, Version
5.0.2195 - Retail
09-24-2003 16:24:07.154 - File: C:\WINNT\system32\unimdmat.dll, Version
5.0.2195 - Retail
09-24-2003 16:24:07.154 - File: C:\WINNT\system32\uniplat.dll, Version
5.0.2195 - Retail
09-24-2003 16:24:07.154 - File: C:\WINNT\system32\drivers\modem.sys, Version
5.0.2195 - Retail
09-24-2003 16:24:07.154 - File: C:\WINNT\system32\modemui.dll, Version
5.0.2195 - Retail
09-24-2003 16:24:07.154 - Modem type: MyModem
09-24-2003 16:24:07.154 - Modem inf path: oem40.inf
09-24-2003 16:24:07.154 - Modem inf section: LCU500G
09-24-2003 16:24:07.154 - Opening Modem
09-24-2003 16:24:07.154 - 19200,8,N,1, ctsfl=0, rtsctl=1
09-24-2003 16:24:07.154 - Initializing modem.
09-24-2003 16:24:07.154 - DSR is low while initializing the modem. Verify
modem is turned on.
09-24-2003 16:24:07.154 - CTS is low while initializing modem.
09-24-2003 16:24:07.164 - Send: AT<cr>
09-24-2003 16:24:07.174 - TSP(0000): Making call
09-24-2003 16:24:07.204 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:07.204 - Interpreted response: OK
09-24-2003 16:24:07.214 - Send: AT &F0 &D2 &C1 E0<cr>
09-24-2003 16:24:07.254 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:07.254 - Interpreted response: OK
09-24-2003 16:24:07.264 - Send: AT V1 W1 S95=47<cr>
09-24-2003 16:24:07.295 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:07.295 - Interpreted response: OK
09-24-2003 16:24:07.305 - Send: AT&K3<cr>
09-24-2003 16:24:07.335 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:07.335 - Interpreted response: OK
09-24-2003 16:24:07.345 - Send: AT<cr>
09-24-2003 16:24:07.375 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:07.375 - Interpreted response: OK
09-24-2003 16:24:07.385 - Send: AT+CGDCONT=1,"IP","internet";<cr>
09-24-2003 16:24:07.445 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:07.445 - Interpreted response: OK
09-24-2003 16:24:07.445 - Waiting for a call.
09-24-2003 16:24:07.455 - Send: ATS0=0<cr>
09-24-2003 16:24:07.485 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:07.485 - Interpreted response: OK
09-24-2003 16:24:07.485 - 19200,8,N,1, ctsfl=0, rtsctl=1
09-24-2003 16:24:07.485 - Initializing modem.
09-24-2003 16:24:07.485 - DSR is low while initializing the modem. Verify
modem is turned on.
09-24-2003 16:24:07.485 - CTS is low while initializing modem.
09-24-2003 16:24:07.495 - Send: AT<cr>
09-24-2003 16:24:07.525 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:07.525 - Interpreted response: OK
09-24-2003 16:24:07.535 - Send: AT &F0 &D2 &C1 E0<cr>
09-24-2003 16:24:07.585 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:07.585 - Interpreted response: OK
09-24-2003 16:24:07.595 - Send: AT V1 W1 S95=47<cr>
09-24-2003 16:24:07.625 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:07.625 - Interpreted response: OK
09-24-2003 16:24:07.635 - Send: AT&K3<cr>
09-24-2003 16:24:07.665 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:07.665 - Interpreted response: OK
09-24-2003 16:24:07.675 - Send: AT<cr>
09-24-2003 16:24:07.705 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:07.705 - Interpreted response: OK
09-24-2003 16:24:07.715 - Send: AT+CGDCONT=1,"IP","internet";<cr>
09-24-2003 16:24:07.775 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:07.775 - Interpreted response: OK
09-24-2003 16:24:07.775 - Dialing.
09-24-2003 16:24:07.775 - TSP(0000): LINEEVENT: LINECALLSTATE_DIALING
09-24-2003 16:24:07.775 - TSP(0000): LINEEVENT: LINECALLSTATE_PROCEEDING
09-24-2003 16:24:07.785 - Send: ATDT*###<cr>
09-24-2003 16:24:07.855 - Recv: <cr>
09-24-2003 16:24:07.855 - Interpreted response: Informative
09-24-2003 16:24:07.855 - Recv: <lf>
09-24-2003 16:24:07.855 - Interpreted response: Informative
09-24-2003 16:24:07.865 - Recv: CARRIER 9600
09-24-2003 16:24:07.865 - Interpreted response: Informative
09-24-2003 16:24:07.865 - Recv: <cr>
09-24-2003 16:24:07.865 - Interpreted response: Informative
09-24-2003 16:24:07.875 - Recv: <lf>
09-24-2003 16:24:07.875 - Interpreted response: Informative
09-24-2003 16:24:07.875 - Recv: <cr>
09-24-2003 16:24:07.875 - Interpreted response: Informative
09-24-2003 16:24:07.875 - Recv: <lf>
09-24-2003 16:24:07.875 - Interpreted response: Informative
09-24-2003 16:24:07.875 - Recv: PROTOCOL: ALT
09-24-2003 16:24:07.875 - Interpreted response: Informative
09-24-2003 16:24:07.885 - Recv: <cr>
09-24-2003 16:24:07.885 - Interpreted response: Informative
09-24-2003 16:24:07.885 - Recv: <lf>
09-24-2003 16:24:07.885 - Interpreted response: Informative
09-24-2003 16:24:07.885 - Recv: <cr>
09-24-2003 16:24:07.885 - Interpreted response: Informative
09-24-2003 16:24:07.885 - Recv: <lf>
09-24-2003 16:24:07.885 - Interpreted response: Informative
09-24-2003 16:24:07.905 - Recv: COMPRESSION: NONE
09-24-2003 16:24:07.905 - Interpreted response: Informative
09-24-2003 16:24:07.905 - Recv: <cr>
09-24-2003 16:24:07.905 - Interpreted response: Informative
09-24-2003 16:24:07.905 - Recv: <lf>
09-24-2003 16:24:07.905 - Interpreted response: Informative
09-24-2003 16:24:07.915 - Recv: <cr>
09-24-2003 16:24:07.915 - Interpreted response: Informative
09-24-2003 16:24:07.915 - Recv: <lf>
09-24-2003 16:24:07.915 - Interpreted response: Informative
09-24-2003 16:24:07.925 - Recv: CONNECT 9600/ARQ
09-24-2003 16:24:07.925 - Interpreted response: Connect
09-24-2003 16:24:07.925 - Receive Connect but CD was low, Waiting for signal
to go high
09-24-2003 16:24:07.945 - After waiting 20ms CD is still low.
09-24-2003 16:24:07.965 - After waiting 20ms CD is still low.
09-24-2003 16:24:07.985 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.006 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.026 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.046 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.066 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.086 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.126 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.146 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.166 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.186 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.206 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.226 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.246 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.266 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.286 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.306 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.326 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.346 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.366 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.386 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.406 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.426 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.446 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.466 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.486 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.506 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.526 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.546 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.566 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.586 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.606 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.626 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.646 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.666 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.687 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.707 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.727 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.747 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.767 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.787 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.807 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.827 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.847 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.867 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.887 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.907 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.927 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.947 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.967 - After waiting 20ms CD is still low.
09-24-2003 16:24:08.987 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.007 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.027 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.047 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.067 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.087 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.107 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.127 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.147 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.167 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.187 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.207 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.227 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.247 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.267 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.287 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.307 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.327 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.347 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.367 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.388 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.408 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.428 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.448 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.468 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.488 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.508 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.528 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.548 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.568 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.588 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.608 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.628 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.648 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.668 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.688 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.708 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.728 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.748 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.768 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.788 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.808 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.828 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.848 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.868 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.888 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.908 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.928 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.948 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.968 - After waiting 20ms CD is still low.
09-24-2003 16:24:09.988 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.008 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.028 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.048 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.068 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.089 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.109 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.129 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.149 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.169 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.189 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.209 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.229 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.249 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.269 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.289 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.309 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.329 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.349 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.369 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.389 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.409 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.429 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.449 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.469 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.489 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.509 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.529 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.549 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.569 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.589 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.609 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.629 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.649 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.669 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.689 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.709 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.729 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.749 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.769 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.790 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.810 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.830 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.850 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.870 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.890 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.910 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.930 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.950 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.970 - After waiting 20ms CD is still low.
09-24-2003 16:24:10.990 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.010 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.030 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.050 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.070 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.090 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.110 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.130 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.150 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.170 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.190 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.210 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.230 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.250 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.270 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.290 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.310 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.330 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.350 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.370 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.390 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.410 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.430 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.450 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.471 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.491 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.511 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.531 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.551 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.571 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.591 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.611 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.631 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.651 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.671 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.691 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.711 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.731 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.751 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.771 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.791 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.811 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.831 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.851 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.871 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.891 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.911 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.931 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.951 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.971 - After waiting 20ms CD is still low.
09-24-2003 16:24:11.991 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.011 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.031 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.051 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.071 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.091 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.111 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.131 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.151 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.172 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.192 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.212 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.232 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.252 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.272 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.292 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.312 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.332 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.352 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.372 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.392 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.412 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.432 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.452 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.472 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.492 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.512 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.532 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.552 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.572 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.592 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.612 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.632 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.652 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.672 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.692 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.712 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.732 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.752 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.772 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.792 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.812 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.832 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.852 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.873 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.893 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.913 - After waiting 20ms CD is still low.
09-24-2003 16:24:12.933 - CD never went high, Proceeding with connection.
09-24-2003 16:24:12.933 - Connection established at 9600bps.
09-24-2003 16:24:12.933 - Error-control on.
09-24-2003 16:24:12.933 - Data compression off or unknown.
09-24-2003 16:24:12.933 - TSP(0000): LINEEVENT: LINECALLSTATE_CONNECTED
09-24-2003 16:24:42.936 - Read: Total: 656, Per/Sec: 13, Written: Total: 99,
Per/Sec: 0
09-24-2003 16:24:53.070 - TSP(0000): Dropping call
09-24-2003 16:24:53.070 - Hanging up the modem.
09-24-2003 16:24:53.070 - Recv:
~<ff>}#<c0>!}!%} }8}"}&} }*} } }'}"}(}"}%}&<<e9><cf><9a>
09-24-2003 16:24:53.070 - Unknown Response
09-24-2003 16:24:53.070 - Recv:
(}"}%}&<<e9><cf><9a>}#}$<c0>#A<db>~~<ff>}#<c0>!}!%} }8}"
09-24-2003 16:24:53.070 - Unknown Response
09-24-2003 16:24:53.070 -
Recv: }8}"}&} }*} } }'}"}(}"}%}&<<e9><cf><9a>}#}$<c0>#A<db>~~
09-24-2003 16:24:53.070 - Unknown Response
09-24-2003 16:24:53.070 - Recv:
<9a>}#}$<c0>#A<db>~~<ff>}#<c0>!}!%} }8}"}&} }*} } }'}"}(
09-24-2003 16:24:53.070 - Unknown Response
09-24-2003 16:24:53.070 - Recv:
*} } }'}"}(}"}%}&<<e9><cf><9a>}#}$<c0>#A<db>~~<ff>}#<c0>
09-24-2003 16:24:53.070 - Unknown Response
09-24-2003 16:24:53.070 - Recv: <cr><lf>NO CARRIER<cr><lf>
09-24-2003 16:24:53.070 - Unknown Response
09-24-2003 16:24:53.271 - Send: ATH<cr>
09-24-2003 16:24:53.321 - Recv: <cr><lf>NO CARRIER<cr><lf>
09-24-2003 16:24:53.321 - Interpreted response: No Carrier
09-24-2003 16:24:53.321 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:53.321 - Interpreted response: OK
09-24-2003 16:24:53.331 - Send: ATH<cr>
09-24-2003 16:24:53.401 - Recv: <cr><lf>NO CARRIER<cr><lf>
09-24-2003 16:24:53.401 - Interpreted response: No Carrier
09-24-2003 16:24:53.411 - Send: ATH<cr>
09-24-2003 16:24:53.411 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:53.411 - Interpreted response: OK
09-24-2003 16:24:53.421 - 19200,8,N,1, ctsfl=0, rtsctl=1
09-24-2003 16:24:53.421 - Initializing modem.
09-24-2003 16:24:53.421 - DSR is low while initializing the modem. Verify
modem is turned on.
09-24-2003 16:24:53.421 - CTS is low while initializing modem.
09-24-2003 16:24:53.431 - Send: AT<cr>
09-24-2003 16:24:53.511 - Recv: <cr><lf>NO CARRIER<cr><lf>
09-24-2003 16:24:53.511 - Interpreted response: No Carrier
09-24-2003 16:24:53.511 - TSP(0000): LINEEVENT:
LINECALLSTATE_DISCONNECTED(0x1)
09-24-2003 16:24:53.511 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
09-24-2003 16:24:53.511 - TSP(0000): Dropping call
09-24-2003 16:24:53.511 - TSP(0000): Closing Call
09-24-2003 16:24:53.511 - TSP(0000): LINEEVENT: LINE_CLOSE
09-24-2003 16:24:53.511 - Session Statistics:
09-24-2003 16:24:53.511 - Reads : 16 bytes
09-24-2003 16:24:53.511 - Writes: 3 bytes
09-24-2003 16:24:53.541 - File: C:\WINNT\system32\unimdm.tsp, Version
5.0.2195 - Retail
09-24-2003 16:24:53.541 - File: C:\WINNT\system32\unimdmat.dll, Version
5.0.2195 - Retail
09-24-2003 16:24:53.541 - File: C:\WINNT\system32\uniplat.dll, Version
5.0.2195 - Retail
09-24-2003 16:24:53.541 - File: C:\WINNT\system32\drivers\modem.sys, Version
5.0.2195 - Retail
09-24-2003 16:24:53.541 - File: C:\WINNT\system32\modemui.dll, Version
5.0.2195 - Retail
09-24-2003 16:24:53.541 - Modem type: MyModem
09-24-2003 16:24:53.541 - Modem inf path: oem40.inf
09-24-2003 16:24:53.541 - Modem inf section: LCU500G
09-24-2003 16:24:53.541 - Opening Modem
09-24-2003 16:24:53.541 - 19200,8,N,1, ctsfl=0, rtsctl=1
09-24-2003 16:24:53.541 - Initializing modem.
09-24-2003 16:24:53.541 - DSR is low while initializing the modem. Verify
modem is turned on.
09-24-2003 16:24:53.541 - CTS is low while initializing modem.
09-24-2003 16:24:53.551 - Send: AT<cr>
09-24-2003 16:24:53.601 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:53.601 - Interpreted response: OK
09-24-2003 16:24:53.611 - Send: AT &F0 &D2 &C1 E0<cr>
09-24-2003 16:24:53.661 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:53.661 - Interpreted response: OK
09-24-2003 16:24:53.671 - Send: AT V1 W1 S95=47<cr>
09-24-2003 16:24:53.701 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:53.701 - Interpreted response: OK
09-24-2003 16:24:53.711 - Send: AT&K3<cr>
09-24-2003 16:24:53.741 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:53.741 - Interpreted response: OK
09-24-2003 16:24:53.751 - Send: AT<cr>
09-24-2003 16:24:53.781 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:53.781 - Interpreted response: OK
09-24-2003 16:24:53.791 - Send: AT+CGDCONT=1,"IP","internet";<cr>
09-24-2003 16:24:53.851 - Recv: <cr><lf>OK<cr><lf>
09-24-2003 16:24:53.851 - Interpreted response: OK
09-24-2003 16:24:53.851 - Session Statistics:
09-24-2003 16:24:53.851 - Reads : 36 bytes
09-24-2003 16:24:53.851 - Writes: 76 bytes Tag: Windows XP bootup issue with wireless 802.1x Tag: 32916
Is IoSetCompletionRoutine callback deterministic?
Hello,
I find there is a latency as high as 110mS between ending of a
hardware event and entry into the callback routine set by
IoSetCompletionRoutine in WinXP. This is not random but periodic.
For instance the latency alternates between 10mS and 110mS every
successive IRP.
I beleive this is got to do something with scheduling of IRP
completion by the OS.
How is the callback routine scheduded? Can the user alter its
priority?
Regards,
Mark Tag: Windows XP bootup issue with wireless 802.1x Tag: 32913
Unable to Read Printer Status info with ReadPrinter
Hello all,
I am trying to read printer status information without writing a language or port monitor.
I have been trying to do this by using the ReadPrinter function. So far, I have been unsuccessful.
Has anyone tried this, or know how to do it? Thanks in advance. Tag: Windows XP bootup issue with wireless 802.1x Tag: 32912
PCI device, machine.inf and Win2k SP4
A little while ago I started developing a device driver for a PCI
board we designed. As the chips we use on the board are not production
ones yet we can't set the ID's on the PCI controller part of it. When
inserted into a Win2K machine it sees the card as a PCI CPU host
bridge and loads the standard driver for that device. To get it to
load my driver I just comment out the section in machine.inf that
tells the system to load the default driver for CPU host bridges. That
all worked well.
We recently updated our test rig with Service Pack 4 for Win2k and now
the system always sees our card as a CPU host bridge and tries to load
the default driver again, even though the line in machine.inf is still
commented out.
Anyone any idea what may have changed in this service pack to cause
this ?
Thanks in advance
p.s.
this is the line in machine.inf ....
PCI/CC_0600.DeviceDesc% = NO_DRV,PCI\CC_0600; HOST PCI BRIDGE Tag: Windows XP bootup issue with wireless 802.1x Tag: 32910
Hooking a keyboard driver to block keystrokes
I am interested in writing as non-intrusive of a keyboard hook as I can in
order to block SAS (Ctrl-Alt-Del) and Alt-Tab at a low level. I have
already written a GINA stub for SAS purposes, but it ended up at a dead end
when I discovered that the SAS caused a short hiccup while the stub function
returned. My client needs something to catch the ctrl-alt-del before it
happens, and this seems to be my last option. The problem is that I've
never written a driver before! I have obtained the DDK and am ready to
begin, but I wanted to seek preliminary information as to which path I might
have the most luck going down, which books / articles / documentation to
consult and which (if any) samples I might start with. I will currently be
going through the "kbfiltr" MS sample on the DDK disc.
Very many thanks!
Eric Tag: Windows XP bootup issue with wireless 802.1x Tag: 32905
What happens to a PCI device when the driver is unloaded?
Is there any information on what actually happens to a PCI device when
its driver is unloaded? Of course everything happens that I program in
the appropriate IRP handler, but after that? What happens physically
to the device?
The reason I'm asking is because sometimes "my" device gets in a state
where I can not access it anymore. Reloading the driver usually helps,
though, and I'd like to know what happens at that point.
Thorsten Tag: Windows XP bootup issue with wireless 802.1x Tag: 32903