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