hpoussin(a)svn.reactos.com wrote:
> Implement SetupGetInfFileListW and SetupGetInfInformationW
> Inf file parser now accept UNICODE files with FF FE header
> Return required buffer size when buffer is too small in SetupGetLineTextA/W, SetupGetStringFieldA/W
I think you forgot to commit changes to a header file:
lib\setupapi\parser.c: In function 'SetupGetInfInformationW':
lib\setupapi\parser.c:1874: error: 'INFINFO_INF_SPEC_IS_HINF' undeclared
(first
use in this function)
lib\setupapi\parser.c:1874: error: (Each undeclared identifier is
reported only
once
lib\setupapi\parser.c:1874: error: for each function it appears in.)
lib\setupapi\parser.c:1875: error: 'INFINFO_INF_NAME_IS_ABSOLUTE'
undeclared (fi
rst use in this function)
lib\setupapi\parser.c:1876: error: 'INFINFO_DEFAULT_SEARCH' undeclared
(first us
e in this function)
lib\setupapi\parser.c:1877: error: 'INFINFO_REVERSE_DEFAULT_SEARCH'
undeclared (
first use in this function)
lib\setupapi\parser.c:1877: error: 'INFINFO_INF_PATH_LIST_SEARCH'
undeclared (fi
rst use in this function)
lib\setupapi\parser.c: In function 'SetupGetInfFileListW':
lib\setupapi\parser.c:2019: error: 'INFINFO_INF_SPEC_IS_HINF' undeclared
(first
use in this function)
Hi Alex,
--- ion(a)svn.reactos.com wrote:
> Add failure cases for more things then a WINE test could shake a stick at (hopefully)
Great! The virtual test no longer causes a bugcheck. Want to try this one? =)
kernel32_test sync
sync.c:93: Test failed: should succeed
KeBugCheckWithTf at ntoskrnl/ke/catch.c:228
A problem has been detected and ReactOS has been shut down to prevent damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
Technical information:
*** STOP: 0x0000001E (0xc0000047,0x80007cfb,0x000ef350,0x9e89bc5c)
*** ntoskrnl.exe - Address 0x8002ad39 base at 0x80000000, DateStamp 0x0
Exception: -2131009312(0)
Processor: 0 CS:EIP 8:8002ad39 <ntoskrnl.exe:2ad39 ({standard input}:1521 (ZwRaiseException))>
cr2 8069be40 cr3 5522000 Proc: 80fa3cb0 Pid: 128 <kernel32_test.e> Thrd: 80f98718 Tid: 12c
DS 10 ES 10 FS 30 GS 0
EAX: 00000096 EBX: 000000ce ECX: 00000000
EDX: 9e89bd74 EBP: 9e89bc0c ESI: 006afdf0 ESP: 9e89b89c
EDI: 9e89bd74 EFLAGS: 00000292 kESP 9e89b89c kernel stack base 9e899000
Frames:
<ntoskrnl.exe:1bc3a (ntoskrnl/ex/error.c:64 (ExRaiseStatus))>
<ntoskrnl.exe:7cfb (ntoskrnl/ke/sem.c:104 (KeReleaseSemaphore))>
<ntoskrnl.exe:77df0 (ntoskrnl/ob/wait.c:276 (NtSignalAndWaitForSingleObject))>
<ntoskrnl.exe:95ca2 ({standard input}:177 (KiSystemService))>
<kernel32.dll:341c4 (lib/kernel32/synch/wait.c:283 (SignalObjectAndWait))>
KeBugCheckWithTf at ntoskrnl/ke/catch.c:228
A problem has been detected and ReactOS has been shut down to prevent damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
Technical information:
*** STOP: 0x0000001E (0x80000003,0x800a0187,0x00000000,0x9e89b0e0)
*** ntoskrnl.exe - Address 0x800a0187 base at 0x80000000, DateStamp 0x0
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
With the trunk.
kernel32_test.exe virtual
virtual.c:36: Test failed: VirtualAlloc should fail on zero-sized allocation
virtual.c:37: Test failed: got -559038737, expected ERROR_INVALID_PARAMETER
Assertion 'marea->StartingAddress != Node->StartingAddress' failed at ntoskrnl/mm/marea.c line 437
KeBugCheckWithTf at ntoskrnl/ke/catch.c:228
A problem has been detected and ReactOS has been shut down to prevent damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
Technical information:
*** STOP: 0x0000001E (0x80000003,0x8009fe71,0x80fc6364,0x9e89bb70)
*** ntoskrnl.exe - Address 0x8009fe71 base at 0x80000000, DateStamp 0x0
Breakpoint Exception: 3(0)
Processor: 0 CS:EIP 8:8009fe71 <ntoskrnl.exe:9fe71 ({standard input}:23 ())>
cr2 6ad9a8 cr3 589f000 Proc: 80fc48d8 Pid: 12c <kernel32_test.e> Thrd: 80f984d8 Tid: 124
DS 10 ES 10 FS 30 GS 0
EAX: 00000063 EBX: 0000000b ECX: 00000000
EDX: 000003f8 EBP: 9e89bc54 ESI: 006afdf8 ESP: 9e89bbc4
EDI: 9e89bd74 EFLAGS: 00000296 kESP 9e89bbc4 kernel stack base 9e899000
Frames:
<ntoskrnl.exe:5a309 (ntoskrnl/mm/marea.c:437 (MmInsertMemoryArea))>
<ntoskrnl.exe:5ad47 (ntoskrnl/mm/marea.c:1015 (MmCreateMemoryArea))>
<ntoskrnl.exe:53f65 (ntoskrnl/mm/anonmem.c:640 (NtAllocateVirtualMemory))>
<ntoskrnl.exe:95992 ({standard input}:177 (KiSystemService))>
<kernel32.dll:100e5 (lib/kernel32/mem/virtual.c:31 (VirtualAllocEx))>
KeBugCheckWithTf at ntoskrnl/ke/catch.c:228
A problem has been detected and ReactOS has been shut down to prevent damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
Technical information:
*** STOP: 0x0000001E (0x80000003,0x8009fe77,0x00000000,0x9e89b388)
*** ntoskrnl.exe - Address 0x8009fe77 base at 0x80000000, DateStamp 0x0
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
Hi,
something is wrong with the keyboard and mouse. I get the following
message on real hardware and keyboard and mouse are not usable:
(drivers\input\i8042prt\registry.c:215) Can't read registry: c0000034
(drivers\input\i8042prt\registry.c:226) Manually set defaults
(drivers\input\i8042prt\i8042prt.c:538) Got fe instead of 55
(drivers\input\i8042prt\i8042prt.c:565) Basic keyboard detection failed:
c0000185
- Hartmut
Hi,
since some time, I'm not able to change the screen resolution after a
fresh installation. It isn't possible to move the display dialog in a
position, where it is possible to hit the 'OK' button. This has worked
in the past.
- Hartmut
> -----Original Message-----
> From: Murphy, Ged (Bolton) [mailto:MurphyG@cmpbatteries.co.uk]
> Sent: 05 August 2005 08:18
> To: 'ros-dev(a)reactos.com'
> Subject: [ros-dev] RE: [ros-bugs] [Bug 695] New: Tracert -
> Wrong outpout
>
> This is because GetNameInfo is not implememted in ROS. I
> originally used
> GetHostByAddr, but if the IP does not have a hostname, it
> takes a long time
> for the function to return, blocking the flow of the program.
> This is the
> reason tracert hasn't been added to the bootcd yet.
>
> Alex's ws2_32 rewrite should solve this. I'm hoping he's used
> GetNameInfo,
> as GetHostByAddr is depricieted anyway now in favour of this.
>
> I also need to do testing with tracert in ROS, as it is
> currently untested
> and will more that likely contain a few bugs. (such
> confidence I have in my
> code :) )
>
> I'm also wondering why node 11 and 12 are the same in the
> above windows
> output. I haven't seen that happen before. Again, I'll look into it.
>
> Ged.
Sorry, I also forgot to mention that TTL support is not yet acessable via
the SetSockOpt routine.
TTL will therefore default to 128 IIRC, which will break out of the loop
imidietly as it would if it had hit the default maximum of 30 hops in
tracert.
All this info is available in the usage screen which can be viewed by
entering 'tracert' with no args.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
> -----Original Message-----
> From: ReactOS.Bugzilla(a)reactos.com
> [mailto:ReactOS.Bugzilla@reactos.com]
> Sent: 05 August 2005 06:52
> To: ros-bugs(a)reactos.com
> Subject: [ros-bugs] [Bug 695] New: Tracert - Wrong outpout
>
>
> http://reactos.com/bugzilla/show_bug.cgi?id=695
>
> Summary: Tracert - Wrong outpout
> Product: ReactOS
> Version: 0.3.0-SVN
> Platform: x86 Hardware
> OS/Version: ReactOS
> Status: NEW
> Severity: normal
> Priority: P3
> Component: Networking
> AssignedTo: ros-bugs(a)reactos.com
> ReportedBy: gerard.gatineau(a)laposte.net
>
>
> Test done with svn 17040
>
> The "tracert command" does not display correct result as below
>
> Ros Tracert in Ros
> ------------------
>
> Tracing route to www.laposte.net [81.255.54.10]
> over a maximum of 30 hops:
>
> 1 164 ms 80 ms 81 ms
> aaaAAaaaaaaAaaaa-LIBGCCW32-EH-2-SJLJ-GTHR-MINGW32 [81.255.54.10]
>
> Trace complete.
>
> The tracert command ( from Ros ) ran in windows displays correctly .
> It means that the tracert program in Reactos is correct but
> the Ros networking
> support is the problem
>
> Ros Tracert in Windows
> ----------------------
>
> Tracing route to www.laposte.net [81.255.54.10]
>
> over a maximum of 30 hops:
>
> 1 1 ms <1 ms <1 ms 192.168.0.254
> 2 83 ms 84 ms 84 ms 192.168.254.254
> 3 61 ms 59 ms 59 ms
> vlq-6k-2-a11.routers.proxad.net [212.27.37.190]
> 4 62 ms 61 ms 62 ms
> p19-6k-2-v800.intf.routers.proxad.net [212.27.50.6]
> 5 62 ms 62 ms 62 ms
> aub-6k-1-v806.routers.proxad.net [212.27.50.162]
> 6 60 ms 62 ms 61 ms
> GE0-3-0-0.noaub101.Aubervilliers.francetelecom.net [193.252.161.97]
> 7 60 ms 59 ms 62 ms
> pos5-0.ntaub301.Aubervilliers.francetelecom.net
> [193.252.103.86]
> 8 69 ms 69 ms 70 ms pos9-0.nrlyo201.Lyon.francetelecom.net
> [193.252.103.77]
> 9 73 ms 72 ms 75 ms pos6-0.ncnic201.Nice.francetelecom.net
> [193.252.101.157]
> 10 74 ms 73 ms 74 ms 81.255.54.252
> 11 76 ms 75 ms 74 ms www.laposte.net [81.255.54.10]
> 12 74 ms 76 ms 77 ms www.laposte.net [81.255.54.10]
>
> Trace complete.
>
This is because GetNameInfo is not implememted in ROS. I originally used
GetHostByAddr, but if the IP does not have a hostname, it takes a long time
for the function to return, blocking the flow of the program. This is the
reason tracert hasn't been added to the bootcd yet.
Alex's ws2_32 rewrite should solve this. I'm hoping he's used GetNameInfo,
as GetHostByAddr is depricieted anyway now in favour of this.
I also need to do testing with tracert in ROS, as it is currently untested
and will more that likely contain a few bugs. (such confidence I have in my
code :) )
I'm also wondering why node 11 and 12 are the same in the above windows
output. I haven't seen that happen before. Again, I'll look into it.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Would it not be easier to wait until the website is back up and use the poll
feature.
This could get confusing.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Hi!
I can install Xchat 2.4.4 from http://www.silverex.org/news/.
It look horrible but it does run with some exceptions. One, you may have to
start the app from it's lib directory, "..\xchat". I do not have a screen-
shot 8^P. But here is a debug print, this does not happen often, only when
exiting the app from the X button. It looks like something I posted before.
GTK+ apps are starting to work under ROS, this alone should speak volumes!
Btw! We need to implement NtGdiOffsetClipRgn, I dont care if it is a haxed wine
port, atleast something. Bitmap seems broken too.
X-Chat,
WARNING: NtGdiOffsetClipRgn at subsys/win32k/objects/cliprgn.c:330 is UNIMPLEME
NTED!
WARNING: NtGdiOffsetClipRgn at subsys/win32k/objects/cliprgn.c:330 is UNIMPLEME
NTED!
(subsys/win32k/misc/object.c:463) Object type mismatch 0x2 0x5
(subsys/win32k/misc/object.c:463) Object type mismatch 0x2 0x5
(lib/comctl32/toolbar.c:416) bitmap for ID 0, index 1 is not valid, number of bi
tmaps in imagelist: 0
(subsys/win32k/misc/object.c:463) Object type mismatch 0x2 0x5
(subsys/win32k/objects/gdiobj.c:545) GdiHdr->Locks: 1
Assertion 'FALSE' failed at subsys/win32k/objects/gdiobj.c line 549
KeBugCheckWithTf at ntoskrnl/ke/catch.c:228
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
Technical information:
*** STOP: 0x0000001E (0x80000003,0x8009fdf1,0x9dcf622e,0x00000009)
*** ntoskrnl.exe - Address 0x8009fdf1 base at 0x80000000, DateStamp 0x0
Breakpoint Exception: 3(0)
Processor: 0 CS:EIP 8:8009fdf1 <ntoskrnl.exe:9fdf1 ({standard input}:23 ())>
cr2 77ee23f6 cr3 20c91000 Proc: 817108e0 Pid: 128 <gtk2_prefs.exe> Thrd: 81c744b
8 Tid: 120
DS 10 ES 10 FS 30 GS 0
EAX: 00000044 EBX: 000000d5 ECX: 00000000
EDX: 000003f8 EBP: 9db53c14 ESI: 0068fec0 ESP: 9db53b84
EDI: 9db53d74 EFLAGS: 00000292 kESP 9db53b84 kernel stack base 9db51000
Frames:
<win32k.sys:802b8 (subsys/win32k/objects/gdiobj.c:549 (GDIOBJ_FreeObj))>
<win32k.sys:805d2 (subsys/win32k/objects/gdiobj.c:670 (GDI_CleanupForProcess))>
<win32k.sys:3aea3 (subsys/win32k/main/dllmain.c:102 (Win32kProcessCallback))>
<ntoskrnl.exe:82c0e (ntoskrnl/ps/win32.c:99 (PsTerminateWin32Process))>
<ntoskrnl.exe:7a5f2 (ntoskrnl/ps/kill.c:295 (PspExitThread))>
<ntoskrnl.exe:7ad74 (ntoskrnl/ps/kill.c:593 (NtTerminateProcess))>
<ntoskrnl.exe:958f2 ({standard input}:177 (KiSystemService))>
<kernel32.dll:32142 (lib/kernel32/process/proc.c:592 (ExitProcess))>
gdi32_crosstest bitmap,
(subsys/win32k/objects/gdiobj.c:802) Attempted to lock object 0x0 that is delete
d!
(subsys/win32k/objects/gdiobj.c:802) Attempted to lock object 0x0 that is delete
d!
(subsys/win32k/objects/gdiobj.c:939) Attempted to lock object 0x0 that is delete
d!
Assertion 'Dest != NULL && Source != NULL && DestRect != NULL && SourcePoint !=
NULL' failed at subsys/win32k/eng/copybits.c line 53
KeBugCheckWithTf at ntoskrnl/ke/catch.c:228
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
Technical information:
*** STOP: 0x0000001E (0x80000003,0x8009fdf1,0x00000296,0x0a32ec37)
*** ntoskrnl.exe - Address 0x8009fdf1 base at 0x80000000, DateStamp 0x0
Breakpoint Exception: 3(0)
Processor: 0 CS:EIP 8:8009fdf1 <ntoskrnl.exe:9fdf1 ({standard input}:23 ())>
cr2 930000 cr3 3aeda000 Proc: 816eb508 Pid: 120 <gdi32_crosstest> Thrd: 816f63c0
Tid: 124
DS 10 ES 10 FS 30 GS 0
EAX: 00000085 EBX: 0000106a ECX: 00000000
EDX: 000003f8 EBP: 9f32e8c0 ESI: 006cee54 ESP: 9f32e830
EDI: 9f32ed74 EFLAGS: 00000282 kESP 9f32e830 kernel stack base 9f32c000
Frames:
<win32k.sys:30ce0 (subsys/win32k/eng/copybits.c:53 (EngCopyBits))>
<win32k.sys:7a1e3 (subsys/win32k/objects/dib.c:508 (NtGdiGetDIBits))>
<ntoskrnl.exe:958f2 ({standard input}:177 (KiSystemService))>
<gdi32_crosstest.EXE:565c>
This is a call to all devs! The 0.2.7 branch has a input bug that
is currently listed as a blocker for the release. We have been unable
to get ahold of tinus (the i8042prt author) to take a look at this
particular bug. If anyone is capable and interested in fixing this,
please contact myself or simply join #reactos and offer help.
Bug info:
http://www.reactos.com/bugzilla/show_bug.cgi?id=657
WD
--
#irc.freenode.net #reactos
01:03PM <filip2307> i don't know about any bug
01:04PM <filip2307> none exist
01:04PM <filip2307> ReactOS is prefect
> From: gvg(a)svn.reactos.com
>
> Added files:
> trunk/reactos/lib/cpl/intl/sv.rc
>
> Deleted files:
> trunk/reactos/lib/cpl/intl/Sv.rc
The main intl.rc file referred to "sv.rc", but the file was named "Sv.rc".
I've corrected this, but it might give problems when svn up'ing on windows.
Just delete lib/cpl/intl/Sv.rc before doing an update.
Gé van Geldorp.
Well, look at this page to find other nice things we would like to have, we need more then client:
http://www2.reactos.com/wiki/index.php/ReactOS_Terminal_Services or
http://www.reactos.com/wiki/index.php/ReactOS_Terminal_Services
Yours sincerely,
Jaix Bly
----Ursprungligt meddelande-----
From: Wesley Parish wes.parish(a)paradise.net.nz
Date: Mon, 1 Aug 2005 15:07:19 +0200
To: ReactOS Development List ros-dev(a)reactos.com
Subject: [ros-dev] rdesktop
> http://www.rdesktop.org/
> Another link in the chain of compatibility.
>
> All we need for it is for the networking code to become mature.
>
> Wesley Parish
> --
> Clinersterton beademung, with all of love - RIP James Blish
> -----
> Mau e ki, he aha te mea nui?
> You ask, what is the most important thing?
> Maku e ki, he tangata, he tangata, he tangata.
> I reply, it is people, it is people, it is people.
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
I keep getting the following error:
lib\ntdll\string\ctype.c:280: warning: '_pctype' defined locally after
being referenced with dllimport linkage
mingw32-make: *** [obj-i386\lib\ntdll\string\ctype.o] Error 1
I found a cheap little trick to it, commenting out line 280 in ctype.c
will fix it (for now)
--
-David W. Eckert
Most reactos.com services should be available again. The
forum is still offline. Mailing lists, main website, wiki and
bugzilla are functional again.
It might take a little while for the DNS changes to trickle
down the system, so if it doesn't work for you yet just try
again in half a day or so.
Gé van Geldorp.
Most reactos.com services should be available again. The forum is still
offline. Mailing lists, main website, wiki and bugzilla are functional
again.
It might take a little while for the DNS changes to trickle down the system,
so if it doesn't work for you yet just try again in half a day or so.
Gé van Geldorp.
http://www.rdesktop.org/
Another link in the chain of compatibility.
All we need for it is for the networking code to become mature.
Wesley Parish
--
Clinersterton beademung, with all of love - RIP James Blish
-----
Mau e ki, he aha te mea nui?
You ask, what is the most important thing?
Maku e ki, he tangata, he tangata, he tangata.
I reply, it is people, it is people, it is people.
Hello,
the main XML build file "ReactOS.xml" is referencing a DTD file
"tools/rbuild/project.dtd". But it's not included in the SVN
repository. Is there already such a file? And in that case - could you
please check it in?
Thanks,
Martin
Hi. I'm implementing an EventLog service now. I want to make it 100%
compatible with windows. Windows machines will be able to access reactos
eventlog via rpc.
Undocumented rpc interface is almost reversed now. You can find it in
attached archive with some tests. Ansi functions work very well, but
I have some problems with unicode ones. When I pass initialized with
nulls UNICODE_STRING to a function, it works. When I initialize
structure with some other values, exception is raised on server side
(1783 Stub received bad data). I don't know why this happens. Advapi32
initializes structures with RtlInitUnicodeString, nothing special. Any
ideas?
And I don't know how to compile this with widl and gcc. SEH is not
implemented in gcc, right? How rpc exceptions are handled in ROS? Widl
returns strange errors. Somebody familiar with widl please help me =)
I summarize below the networking status for nic rtl8139 in real hardware
, with the help of Alex , Filip and Hpoussin
- Ping ok with svn 15400
- ping Nok with SVN15402+15404 and >
- ping ok with head (svn 16894) + patch 15402/15404 removed
The interesting part is this:
1) svn 15400
(ndis/io.c:824)(NdisMRegisterInterrupt) Called. InterruptVector (0xA)
InterruptLevel (0xA) SharedInterrupt (1) InterruptMode (0x0)
(ndis/io.c:843)(NdisMRegisterInterrupt) Connecting to interrupt vector
(0x4A) Affinity (0xFFFFFFFF).
(ndis/io.c:848)(NdisMRegisterInterrupt) Leaving. Status (0x0).
2) svn 15402/15404
(ndis/io.c:824)(NdisMRegisterInterrupt) Called. InterruptVector (0x0)
InterruptLevel (0x0) SharedInterrupt (1) InterruptMode (0x0)
(ndis/io.c:843)(NdisMRegisterInterrupt) Connecting to interrupt vector
(0x40) Affinity (0xFFFFFFFF).
(ndis/io.c:848)(NdisMRegisterInterrupt) Leaving. Status (0x0).
3) Svn 16860
(ndis\ndis\io.c:824)(NdisMRegisterInterrupt) Called. InterruptVector
(0x9) InterruptLevel (0x9) SharedInterrupt (1) InterruptMode (0x0)
(ndis\ndis\io.c:843)(NdisMRegisterInterrupt) Connecting to interrupt
vector (0x49) Affinity (0xFFFFFFFF).
(ndis\ndis\io.c:848)(NdisMRegisterInterrupt) Leaving. Status (0x0).
Regards
Gerard