--- "Aaron W. LaFramboise" <aaron77thyme(a)aaronwl.com> wrote:
> I know nothing about ReactOS internals, but theres a chance someone
> might be able to help if you could check all objects with the bad
> binutils against all objects with the good binutils, and somewhere
> post
> the objects that differed. I'd take a look if you could post this
> much
> information.
According to Filip Navara there was a bug in binutils that is fixed in
current CVS. I dont really have the time to check all the objects.
Thanks
Steven
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
>
> Today's Topics:
>
> 1. Re: What I have learned on my time off
> (LinuxWorld) (Jason Filby)
----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 6 Nov 2004 10:07:57 +0200
> From: Jason Filby <jason.filby(a)gmail.com>
> Subject: Re: [ros-dev] What I have learned on my
> time off (LinuxWorld)
> To: ReactOS Development List <ros-dev(a)reactos.com>
> Message-ID:
> <e7a1591e04110600072d5b1306(a)mail.gmail.com>
> Content-Type: text/plain; charset=US-ASCII
>
> Steven
>
> >1. We need a roadmap for the future.
>
> Agreed.
>
> >2. We have to have regression testing in place.
>
> Yes - Casper's doing a lot of great work on this;
> with regards to
> WineHQ tests, well, we'll have to see if we can't
> find a way to
> integrate them. Right now let's just focus on
> getting the Continuous
> Integration System going.
>
> >3. We need to improve our documentation and
> website.
>
> I've already thought about this a lot; definitely a
> wiki for the
> Library - with access only to devs to make changes;
> a wiki doesn't
> have to allow just anyone to make a change and I
> don't think that's a
> good idea. I've already introduced MedaWiki at work
> (it powers
> Wikipedia.com) and would really want to get this on
> reactos.com for
> our Library -- probably a few other pages as well.
>
> I don't want to see a wiki only site. A wiki doesn't
> enforce
> structure, which is nice for something like a blog
> or list of
> compatible hardware/software, or forum. We'll use
> the best software
> suited to the job -- this means that a lot of effort
> will have to go
> into integration: search but more importantly login.
>
> It's just that to get there is a ton of work! The
> website needs its
> own roadmap, for sure.
>
Mr. Filby, i have ofered twice to colaborate with my
limited capabilities in the proyect, i have offered to
actualize the website from time to time, and the made
of a FAQ (this will be more difficult, as i will have
to test and ask many howtos on reactos) if you find
this could be usefull.
I am still waiting for an answer.
Best regards,
Lucio Diaz-Flores.
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
Hello,
The most recent binutils package might have a bug in it but I am not
quite sure. When running ReactOS after building with the newer binutils
you will see errors like in this thread
http://reactos.com:8080/archives/public/ros-dev/2004-November/000492.html
Sorry I dont have time to dig in to it further.
Thanks
Steven
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
The current Rosapps module in CVS fails to build
I am using the recommended compiler indicated in Reactos.com
Regards
Gerard
------------------------------------------------------
mingw32-make[1]: Leaving directory `D:/Gerard/Reactos/Ros/rosapps/sysutils'
mingw32-make -C sysutils\ctm
mingw32-make[1]: Entering directory
`D:/Gerard/Reactos/Ros/rosapps/sysutils/ctm'
windres --include-dir ../../../reactos/include --include-dir
../../../reactos/w32api/include ctm.rc -o ctm.coff
gcc -I. -I../../../reactos/include -I../../../reactos/w32api/include
-pipe -march=i486 -D_M_IX86 -g -c ctm.c -o ctm.o
ctm.c:41:20: epsapi.h: No such file or directory
ctm.c: In function `PerfDataRefresh':
ctm.c:430: warning: assignment makes pointer from integer without a cast
ctm.c:433: warning: assignment makes pointer from integer without a cast
ctm.c:444: warning: assignment makes pointer from integer without a cast
ctm.c:532: warning: assignment makes pointer from integer without a cast
mingw32-make[1]: *** [ctm.o] Error 1
mingw32-make[1]: Leaving directory
`D:/Gerard/Reactos/Ros/rosapps/sysutils/ctm'
mingw32-make: *** [sysutils\ctm] Error 2
D:\Gerard\Reactos\Ros\rosapps>
-------------------------------------------------------
Hi,
I am kind of stuck at the momement as the current CVS wont boot for me.
My build env does not quite match the recommended spec for Mingw under
Windows so I guess that could be the problem. Is anyone else seeing
this?
(ke/i386/kernel.c:330) CPU supports PAE mode
(ke/i386/kernel.c:341) CPU doesn't run in PAE mode
(ke/i386/kernel.c:346) CPU Vendor: AuthenticAMD
(ke/i386/kernel.c:350) CPU Model: AMD Athlon(tm) XP 2400+
(ke/i386/kernel.c:353) Ke386CacheAlignment: 64
(ke/i386/kernel.c:356) Ke386L1CacheSize: 128kB
(ke/i386/kernel.c:360) Ke386L2CacheSize: 256kB
(io/pnpmgr.c:962) InstancePath is Root\PCI\0000
(io/pnpmgr.c:962) InstancePath is Root\Ne2000\0000
(io/pnpmgr.c:962) InstancePath is Root\LEGACY_UNKNOWN\0000
(io/pnpmgr.c:962) InstancePath is Root\LEGACY_UNKNOWN\0000
DriverBase for \SystemRoot\system32\drivers\pci.sys: dcc60000
Peripheral Component Interconnect Bus Driver
(io/pnpmgr.c:962) InstancePath is
PCI\VEN_1274&DEV_1371&SUBSYS_13711274&REV_02\0000
(io/pnpmgr.c:962) InstancePath is
PCI\VEN_1022&DEV_2000&SUBSYS_20001022&REV_10\0000
(io/pnpmgr.c:962) InstancePath is
PCI\VEN_104B&DEV_1040&SUBSYS_1040104B&REV_01\0000
(io/pnpmgr.c:962) InstancePath is
PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00\0000
(io/pnpmgr.c:962) InstancePath is
PCI\VEN_8086&DEV_7113&SUBSYS_197615AD&REV_08\0000
(io/pnpmgr.c:962) InstancePath is
PCI\VEN_8086&DEV_7111&SUBSYS_197615AD&REV_01\0000
(io/pnpmgr.c:962) InstancePath is
PCI\VEN_8086&DEV_7110&SUBSYS_197615AD&REV_08\0000
(io/pnpmgr.c:962) InstancePath is
PCI\VEN_8086&DEV_7191&SUBSYS_00000000&REV_01\0000
(io/pnpmgr.c:962) InstancePath is
PCI\VEN_8086&DEV_7190&SUBSYS_197615AD&REV_01\0000
DriverBase for scsiport.sys: dcc69000
DriverBase for atapi.sys: dcc74000
(ldr/loader.c:1476) LdrPEGetExportByName(): failed to find
NTOSKRNL.RtlConvertUlongToLargeInteger
(ldr/loader.c:1561) Failed to import
NTOSKRNL.RtlConvertUlongToLargeInteger from scsiport.sys
KeBugCheckWithTf at ke/catch.c:164
Bug detected (code 1e param 0 0 0 0)
KMODE_EXCEPTION_NOT_HANDLED
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:58
cr2 58 cr3 2a7000 Proc: c0401010 Pid: 1 <SYSTEM> Thrd: c0406050 Tid: 1
DS 10 ES 10 FS 30 GS 10
EAX: 00000058 EBX: ccbd0998 ECX: 00000000
EDX: 00000000 EBP: c00b1c00 ESI: ccbd0998 ESP: c00b1ad0
EDI: 00000f00 EFLAGS: 00210286 kESP c00b1ad0 kernel stack base
c00af000
Frames: <C007FE69>
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
Hello,
I am sending this in for review as I dont know how the CI system works
and I dont know how to tie the Wine tests in to that system. I have
already applyed Filips patch to wine/test.h that allows the test
failure output to be redirected to DbgPrint so the CI system can log
it.
This patch only adds support for building the Wine tests in our build
system. I have attached a sample set of tests (I dont know if they pass
or not).
just apply the winetest.patch and then dump the extract the tests
folder in your reactos/lib/shlwapi folder.
Now the next time you build shlwapi it will also build the tests.
Thanks
Steven
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
Hi Ge,
I've set my options accordingly now.
Theo
>From: "Ge van Geldorp" <gvg(a)reactos.com>
>Reply-To: ReactOS Development List <ros-dev(a)reactos.com>
>To: "'ReactOS Development List'" <ros-dev(a)reactos.com>
>Subject: RE: [ros-dev] KMODE_EXCEPTION after pressing
>CancelbuttoninTaskbarSettings dia
>Date: Sat, 6 Nov 2004 23:49:21 +0100
>
> > From: Theodor Willax
> >
> > Who will apply this patch to cvs
>
>I just did, thanks for debugging and providing the patch
>
> > and has it the right format?
>
>Not critical for a small patch like this, but it would be better if you
>could use "cvs diff -u" to get some context next time.
>
>Gé van Geldorp.
>
>
>_______________________________________________
>Ros-dev mailing list
>Ros-dev(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-dev
_________________________________________________________________
Wenns mal schnell gehen soll. MSN Suche. http://search.msn.de/ Jetzt
kostenlos nutzen und keine Zeit mehr verlieren.
>--- Theodor Willax <theodor_willax(a)hotmail.com> wrote:
> > thank's for the hint Ge. The patch below should fix this issue. Who
> > will
> > apply this patch to cvs and has it the right format?
>
>It needs to be in diff -u format.
>
>Thanks
>Steven
Here we are again with diff -u format
cvs -z9 diff -u desktop.c (in directory
D:\home\willaxt\Entwicklung\ros\reactos\subsys\win32k\ntuser\)
Index: desktop.c
===================================================================
RCS file: /CVS/ReactOS/reactos/subsys/win32k/ntuser/desktop.c,v
retrieving revision 1.22
diff -u -r1.22 desktop.c
--- desktop.c 28 Sep 2004 15:02:30 -0000 1.22
+++ desktop.c 6 Nov 2004 22:40:12 -0000
@@ -700,7 +700,7 @@
DPRINT("PaintDesktopVersionCallback ValueType=%d ValueLength=%d\n",
ValueType, ValueLength);
if (ValueType==REG_DWORD && ValueLength==sizeof(DWORD))
- *((DWORD*)Context) = *(DWORD*)ValueData;
+ *((DWORD*)EntryContext) = *(DWORD*)ValueData;
return STATUS_SUCCESS;
}
_________________________________________________________________
Geschlossene Gesellschaft. MSN Hotmail mit McAfee® Anti-Virus.
http://www.msn.de/email/antivirus/ Jetzt kostenlos anmelden und Viren
bleiben vor der Tür!
Hi,
> > How could I debug this error?
>
>You can use the map files to find out where things went wrong. On the BSOD
>you attached you can find that the kernel crashed at <win32k.sys: 142f8>.
>So
>you can go to subsys/win32k/win32k.map and find (relative) address 142f8.
>If
>you compiled with DBG := 1 in your config file this should give you the
>exact source line where the crash occurred.
>
>If you need a stack backtrace, use the values on the "Frames:" line in the
>same way.
>
>Gé van Geldorp.
thank's for the hint Ge. The patch below should fix this issue. Who will
apply this patch to cvs and has it the right format?
Theo
cvs -z9 diff desktop.c (in directory
D:\home\willaxt\Entwicklung\ros\reactos\subsys\win32k\ntuser\)
Index: desktop.c
===================================================================
RCS file: /CVS/ReactOS/reactos/subsys/win32k/ntuser/desktop.c,v
retrieving revision 1.22
diff -r1.22 desktop.c
703c703
< *((DWORD*)Context) = *(DWORD*)ValueData;
---
> *((DWORD*)EntryContext) = *(DWORD*)ValueData;
_________________________________________________________________
Die rote Karte für lästige E-Mails. MSN Hotmail mit Junk-Mail-Filter.
http://www.msn.de/antispam/prevention/junkmailfilter Jetzt kostenlos
anmelden!
I wrote a small tool to generate the tests/stubs.tst file for a component.
http://mok.lvcm.com/cgi-bin/reactos/roswiki?TestStubsGenerator
--
Here's a simple experiment. Stand on a train track between two locomotives
which are pushing on you with equal force in opposite directions. You will
exhibit no net motion. None the less, you may soon begin to notice that
something important is happening.
-- Robert Stirniman
> Thanks for reporting. Such error was already reported by one person on
> our IRC channel, but AFAIK wasn't solved yet.
That was me :-)
Please notice me if a newer freeloader is available for testing...
Christoph von Wittich
Okay, I'm just trying to build the system to see what's going on with it,
and thinking about doing some application related work, maybe, at some
point, but in any case, I can't get ReactOS to build. The build dies when
it reaches explorer.cpp, and you can see in the attached error log
(explorer-build.log-2). The version of gcc used was:
fd0man@fd0man:~> i386-mingw32msvc-gcc --version
i386-mingw32msvc-gcc (GCC) 3.4.1 (mingw special)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
The compiler is a Linux-to-Win32 cross compiler. The CVS tree is fully
up-to-date as of right this minute, as I just ran the update before I sent
this off and didn't see any changes occur.
I don't have the ability to poke around with it at the moment, nor do I
have the slightest clue of what's causing it... it seems that it's saying
something about an overloaded function - when it's a completely different
function that's called on the line it's complaining about, anyway, just
doesn't seem to make sense to me. *shrugs*
Later,
Michael
Hi,
I'm sure you've all heard about ekush... I recently read this and though
it was a pearl:
"Licensing is one of the problems the *Ekush* team is expecting to face.
As the project is not based in the US, *Ekush* OS will not be able to
obtain the license banner of General Public License (GPL), the US-based
licensing company."
It just made me burst out laughing :)
Best regards,
Alex Ionescu
I'm continuing to have trouble with the ne2000 driver, and I'm honestly not
sure how to fix it.
I've been poking around a little, so I'll put a diff from my tree as well.
Basically, the problem i see is that BusType and BusNumber from
IoGetDeviceProperty(..., DevicePropertyLegacyBusType, ..., &Adapter->BusType, ...)
and
IoGetDeviceProperty(..., DevicePropertyLegacyBusNumber, ...)
are always -1 in drivers/net/ndis/ndis/miniport.c, line 1404.
Even when i force these values to sensible ones (Isa, 0), the ne2000 gives
0xff for all the bytes of the mac address.
I should mention that I'm using qemu. I've tried my trusty 32-bit 0.5.5
build, 32-bit 0.6.0, and 64-bit 0.6.0 builds.
http://64.81.145.152/~arty/ne2000-goodies.zip
--> arty/arty-poke.diff
--> arty/run-log.txt
--> arty/qemu-0.* (various versions of qemu i tested if it helps)
--
Here's a simple experiment. Stand on a train track between two locomotives
which are pushing on you with equal force in opposite directions. You will
exhibit no net motion. None the less, you may soon begin to notice that
something important is happening.
-- Robert Stirniman
Hello,
I'm getting repeatedly a KMODE_EXCEPTION when pressing the Cancel button in
the Taskbar Settings dialog. See both screenshots attached.
I got this blue screen with several versions of the 0.2.5 cvs tree on my
virtual pc. The last build I did with the cvs tree from yesterday evening.
How could I debug this error?
Thanks,
Theo
_________________________________________________________________
Machen Sie lästigen E-Mails ein Ende. MSN Hotmail mit Junk-Mail-Filter.
http://www.msn.de/antispam/prevention/junkmailfilter Jetzt kostenlos
anmelden!
Hello Filip,
I see what your patch should achieve. But pipetunnel doesn't work although I
defined out the serial port detection code according to your patch.
I will post if I'm successful in getting pipetunnel to work on virtual pc.
Thanks,
Theo
>From: Filip Navara <xnavara(a)volny.cz>
>Reply-To: ReactOS Development List <ros-dev(a)reactos.com>
>To: ReactOS Development List <ros-dev(a)reactos.com>
>Subject: Re: [ros-dev] connect gdb to named pipe in ms virtual pc session
>Date: Wed, 03 Nov 2004 19:37:21 +0100
>
>Theodor Willax wrote:
>
>>a) Do I need to compile the cvs snapshot with special make options to
>>debug trough serial ports?
>
>Generally no, but for Virtual PC you need to get do a CVS build of HAL with
>hacked serial port detection. The standard detection approach doesn't work
>in VPC because of "bug" in the emulated hardware. (Yes, it's really broken.
>It works in Linux because it assumes that two ports always exist and skips
>the detection. See the Linux source for details.) I don't have the original
>patch I used while debugging the S3 driver under VPC anymore, but the
>attached one should work (I hope)...
>
>BTW, I'm not able to answer your other questions, sorry.
>
>Regards,
>Filip
>
>Index: hal/halx86/kdbg.c
>===================================================================
>RCS file: /CVS/ReactOS/reactos/hal/halx86/kdbg.c,v
>retrieving revision 1.8
>diff -u -r1.8 kdbg.c
>--- hal/halx86/kdbg.c 29 Apr 2004 17:06:21 -0000 1.8
>+++ hal/halx86/kdbg.c 3 Nov 2004 18:32:30 -0000
>@@ -102,6 +102,7 @@
> /* clear all modem output bits */
> WRITE_PORT_UCHAR (SER_MCR(BaseAddress), 0x10);
>
>+#if 0
> /* read the Modem Status Register */
> msr = READ_PORT_UCHAR (SER_MSR(BaseAddress));
>
>@@ -123,6 +124,7 @@
> */
> if ((msr & 0xF0) == 0xF0)
> {
>+#endif
> /*
> * setup a resonable state for the port:
> * enable fifo and clear recieve/transmit buffers
>@@ -133,8 +135,10 @@
> READ_PORT_UCHAR (SER_RBR(BaseAddress));
> WRITE_PORT_UCHAR (SER_IER(BaseAddress), 0);
> found = TRUE;
>+#if 0
> }
> }
>+#endif
>
> /* restore MCR */
> WRITE_PORT_UCHAR (SER_MCR(BaseAddress), mcr);
>_______________________________________________
>Ros-dev mailing list
>Ros-dev(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-dev
_________________________________________________________________
Ungestört surfen. MSN Toolbar mit Pop-up-Blocker. http://toolbar.msn.de/
Jetzt kostenlos downloaden!
What are the advantages in using zones when allocating memory in kernel
mode?
Are there other ways to pre-allocate an address range to be used for
small memory objects management (NP pool)?
Emanuele
>From: "Theodor Willax" <theodor_willax(a)hotmail.com>
>Reply-To: ReactOS Development List <ros-dev(a)reactos.com>
>To: ros-dev(a)reactos.com
>Subject: [ros-dev] connect gdb to named pipe in ms virtual pc session
>Date: Wed, 03 Nov 2004 11:40:35 +0000
>
>Hi,
>
>could anybody tell me how to connect gdb.exe to my named pipe
>"\\.\pipe\roscom2" of a virtual pc session (on virtual com2 port). I'm
>running gdb on Win XP SP2 and use ros 0.2.5-cvs last updated 11/03/04.
>I set up "pipetunnel.exe roscom2" in one command prompt window, started
>virtual pc session in debug mode and now try to connect gdb to pipetunnel.
>pipetunnel is now listening on tcp port 9999.
>
>Thanks,
>Theo
>
Hi,
it's me again. Some more questions:
a) Do I need to compile the cvs snapshot with special make options to debug
trough serial ports?
b) Works the named pipe approach with ms virtual pc?
c) Do I need a special gdb version? I've this one:
D:\home\willaxt\Entwicklung\ros>gdb -version
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Many thank's,
Theo
_________________________________________________________________
Geschlossene Gesellschaft. MSN Hotmail mit McAfee® Anti-Virus.
http://www.msn.de/email/antivirus/ Jetzt kostenlos anmelden und Viren
bleiben vor der Tür!
Hi,
if I have address of a variable in the bss section from ntoskrnl, how can I
find out the name? Searching into the map file doesn't help. Possible the
address is a pointer into a structure.
- Hartmut
Hi,
could anybody tell me how to connect gdb.exe to my named pipe
"\\.\pipe\roscom2" of a virtual pc session (on virtual com2 port). I'm
running gdb on Win XP SP2 and use ros 0.2.5-cvs last updated 11/03/04.
I set up "pipetunnel.exe roscom2" in one command prompt window, started
virtual pc session in debug mode and now try to connect gdb to pipetunnel.
pipetunnel is now listening on tcp port 9999.
Thanks,
Theo
_________________________________________________________________
Geschlossene Gesellschaft. MSN Hotmail mit McAfee® Anti-Virus.
http://www.msn.de/email/antivirus/ Jetzt kostenlos anmelden und Viren
bleiben vor der Tür!
Hartmut Birr wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/ntoskrnl/ke/
>Changes by: hbirr(a)mok.osexperts.com 04/10/31 07:24:08
>
>Modified files:
> reactos/ntoskrnl/ke/: timer.c
>
>Log message:
> - The quantum of the idle thread must also end.
>
>
I thought that the NtYieldExecution call in PsIdleThreadMain should be
sufficient, isn't it?
Regards,
Filip