greatlrd(a)svn.reactos.com wrote:
>Fixing directx headers from wine, by adding alot of missing struct and some struct was wrong. Complete the header dmemmgr.h it was missing and move stuff into that header.
>
>
>Added files:
>trunk/reactos/w32api/include/ddk/dmemmgr.h
>
>Updated files:
>trunk/reactos/w32api/include/ddk/ddrawi.h
>trunk/reactos/w32api/include/ddk/ddrawint.h
>trunk/reactos/w32api/include/ddk/dvp.h
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.org
>http://www.reactos.org/mailman/listinfo/ros-svn
>
>
>
This breaks the build.
Best regards,
Alex Ionescu
Fantastic news Alex!
Can't wait to get hold of it and read through it, and put it through some
tests.
It's all about the networking with me ;)
-----Original Message-----
From: Alex Ionescu [mailto:ionucu@videotron.ca]
Sent: 15 October 2005 09:06
To: ReactOS Development List
Subject: [ros-dev] Winsock 2.2 Status
Hi,
As many of you know, I've been working on Winsock for the last 3 weeks,
then lost all my work. I have finished writing everything that I had
lost and did some serious tests with MIRC. I want to update Ged,
Waxdragon, Ge, Magnus and the others which were interested in a status
report.
MIRC uses some serious features, including asyncronous hostname lookups,
which is an extremly complex part of ws2_32.dll. After fixing about 20
bugs (let me add a small note here: Microsoft has done some SERIOUSLY
amazing work with MSVC 2005. The latest RC1 is now even faster, since
the internal build system was updated and now supports multi-threaded
compiles: ws2_32 takes me 2.5 seconds (officially timed) to compile AND
link AND rc with full optimizations + pdb generated... not only did fast
rebuild times help out during testing, but the integrated debugger just
keeps getting better too. Finding those 20 bugs was extremly easy), I
was able to connect to MIRC by using /server irc.freenode.net and join
the channels, identify and talk normally. DCC transfer worked as well.
Almost all of the ws2_32 APIs were being called, and both TCP and UDP
(from dnsapi) communication seemed to work fine. In other words, mirc
was fully usable with my ws2_32.dll
My next test app is firefox. As of now, it loads fine but hangs at 100%
cpu usage. I'm guessing it must be another small bug causing an inifite
loop somewhere. Since it's 4AM now, I'll go sleep and check it out tomorrow.
Best regards,
Alex Ionescu
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
************************************************************************
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
hpoussin(a)svn.reactos.com wrote:
> Remove entries that are created by netcfgx.dll
>
>
> Updated files:
> trunk/reactos/bootdata/hivesys.inf
>
Hi!
Will we need to add entries in hivesys for ROS Ne2K pci (2) driver?
Currently the driver loads but ROS dhclient does not work. All
my other dhclient systems, Win98-2 and XP work.
Thanks,
James
Notes:
I have two net cards installed.
1)
VIA VT6102 Rhine II Fast Ethernet Controller rev. 116, Irq 11, IO 0xe800 [0xe8ff], mem
0xde001000 [0xde001fff], W2k driver not tested yet.
2)
RealTek RTL-8029, IO 0xd000, Irq 11 Ne2K-pci, using ROS ne2000.sys.
My hivesys.inf setup. This works very well.
; NIC drivers are like any other drivers - but no card-specific info here.
; Comment the networking stuff out if you don't have the card and don't want to see errors
; NE2000 NIC driver
HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","ErrorControl",0x00010001,0x00000001
HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","Group",0x00000000,"NDIS"
HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","ImagePath",0x00020000,"system32\drivers\ne2000.sys"
HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","Start",0x00010001,0x00000003
HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","Type",0x00010001,0x00000001
HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","Route",0x00000000,"Ne20001"
; Configuration Entries for the NE2000 Adapter
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","Characteristics",0x00010001,0x00000000
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","DriverDesc",0x00000000,"Ne2000"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","ProviderName",0x00000000,"Provider
Name(from Inffile)"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","NetCfgInstanceId",0x00000000,"{RANDOMCFGGUIDFOR_NE20001}"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001\Linkage","Export",0x00000000,"\Device\Ne20001"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001\Linkage","RootDevice",0x00000000,"Ne20001"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001\Linkage","UpperBind",0x00000000,"Tcpip"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","Port",0x00000000,"D000"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","Irq",0x00000000,"B"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","NetworkAddress",0x00000000,"001122334455"
HKLM,"SYSTEM\CurrentControlSet\Services\Ne20001\Parameters\Tcpip","DefaultGateway",0x00010000,"10.65.145.1"
HKLM,"SYSTEM\CurrentControlSet\Services\Ne20001\Parameters\Tcpip","IPAddress",0x00010000,"10.65.145.79"
HKLM,"SYSTEM\CurrentControlSet\Services\Ne20001\Parameters\Tcpip","SubnetMask",0x00010000,"255.255.255.0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","BusType",0x00000000,"5"
;This is from the Registry from Windows 2000
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","SlotNumber",0x00000000,"11"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","BusNumber",0x00000000,"0"
;And this i get from the BIOS bootscreen.
On Fri, 14 Oct 2005 11:50, Richard Campbell wrote:
> Murphy, Ged (Bolton) wrote:
> >Richard Campbell wrote:
> >>But how WELL does mozilla work with it? Well enough we could include it
> >>with 0.2.8?
> >
> >No, it's still full of bugs.
> >Mozilla won't be included anyway, it's a 3rd party app.
> >
> >Ged.
>
> Normally i'd take this hardline stance on 3rd party apps, but if we say,
> ship firefox with ReactOS 0.3, we'd raise a lot of eyebrows. Suddenly
> this puny operating system that crashes all the time and isn't
> compatible with much of anything is running several complex, everyday
apps.
Actually, come to this of it, you make a fair point.
I'm dead against having application code in the trunk, as I'm sure everyone
else is. However shipping a few 'enhancements' with the prebuilt release
builds can only help with much needed publicity. (assuming they meet
licensing demands). They can always be dropped as we get closer to the 1.0
build (where I think user choice should take precedence via the package
manager)
WaxDragon mentioned including some of our apps like Solitaire with 0.2.8.
Although everyone seemed to like the idea, we don't have a definitive answer
yet.
Are we going ahead with this one?
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
As requested:
> From: nadja friedl <nadja.fiedl(a)gmx.at>
> Sent: Friday, October 14, 2005 18:45
>
> Hello!
> I am the sister of Klemens!
> He is since the 3rd. Oct. at the Austrian army and since the
> 7th. Oct. ill.
> So he is not allowed to come home and he has no possibility
> to surf the net!
> Are there any news about reactOS?
> Please tell the others of my brothers illnes!
> He hopes that he could come home next week!
>
> If you want to reply write to my email adresse and I' ll tell
> him the things!
hpoussin(a)svn.reactos.com wrote:
>Don't always return STATUS_BUFFER_TOO_SMALL when an error occurs in ZwQueryValueKey.
>The "if" was triggered because ValueInformation->DataLength is 0xcdcdcdcd at the return of the function
>
But that means that the memory was freed during the failure, so now the
ExFreePool will run into a double-free!
>Modified: trunk/reactos/ntoskrnl/io/pnpmgr.c
>
>
> ------------------------------------------------------------------------
> *Modified: trunk/reactos/ntoskrnl/io/pnpmgr.c*
>
>--- trunk/reactos/ntoskrnl/io/pnpmgr.c 2005-10-14 13:00:18 UTC (rev 18441)
>+++ trunk/reactos/ntoskrnl/io/pnpmgr.c 2005-10-14 13:04:11 UTC (rev 18442)
>@@ -322,15 +322,18 @@
>
> *ResultLength = ValueInformation->DataLength;
> ZwClose(KeyHandle);
>
>
>
>- if (ValueInformation->DataLength > BufferLength)
>- Status = STATUS_BUFFER_TOO_SMALL;
>-
>
>
> if (!NT_SUCCESS(Status))
> {
> ExFreePool(ValueInformation);
> return Status;
> }
>
>
>
>+ if (ValueInformation->DataLength > BufferLength)
>+ {
>+ ExFreePool(ValueInformation);
>+ return STATUS_BUFFER_TOO_SMALL;
>+ }
>+
>
>
> /* FIXME: Verify the value (NULL-terminated, correct format). */
>
> RtlCopyMemory(PropertyBuffer, ValueInformation->Data,
>
>
Please check this out in more detail...
Best regards,
Alex Ionescu
Richard Campbell wrote:
> But how WELL does mozilla work with it? Well enough we could include it
> with 0.2.8?
>
No, it's still full of bugs.
Mozilla won't be included anyway, it's a 3rd party app.
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
Hi Gunnar,
gdalsnes(a)svn.reactos.com wrote:
>make classes use session wide atom table. should fix bug 899
>
>
>Added files:
>trunk/reactos/subsys/win32k/ntuser/session.c
>
>
What are you plans for managing multiple instances of win32k.sys?
--
:Emanuele Aliberti
Hi,
the termination bug is in co_DestroyThreadWindows.
co_DestroyThreadWindows hangs in an endless loop which calls
UserRefObjectCo. UserRefObjectCo allocates some bytes from stack with
alloca. After some rounds, the kernel stack is eaten up.
- Hartmut