Hello,
The Realtek 8139 Nic driver fails to boot as indicated in the debug
messages .
The hivesys registry used is ne2000 and the rtl3139.sys has been renamed
to ne2000.sys + amd pcnet disabled
Note : this driver file is working fine with WinXP
Any idea ?
Regards
Gerard
----------------------------------------------------------------------
(ke/main.c:586) Module: 'ndis.sys' at c01b1000, length 0x00020db6
(ke/main.c:610) Process system hive registry chunk at c00fd000
(ke/main.c:625) Process hardware hive registry chunk at c010f000
(mm/ppool.c:317) Trying to allocate 116396032 bytes from paged
pool - nothing suitable found, returning NULL
(io/create.c:90) Parent is a Directory which is neither a file
type nor a device type
(ldr/loader.c:623)
LdrGetModuleObject(\SystemRoot\system32\drivers\ne2000.sys) called
(ldr/loader.c:634) Comparing ntoskrnl.exe and
\SystemRoot\system32\drivers\ne2000.sys
(ldr/loader.c:634) Comparing hal.dll and
\SystemRoot\system32\drivers\ne2000.sys
(ldr/loader.c:648) Could not find module
'\SystemRoot\system32\drivers\ne2000.sys'
(ldr/loader.c:301) Loading Module
\SystemRoot\system32\drivers\ne2000.sys...
ldr/loader.c:309
(io/create.c:90) Parent is a Directory which is neither a file
type nor a device type
ldr/loader.c:316
(ldr/loader.c:319) Could not open module file:
\SystemRoot\system32\drivers\ne2000.sys
(io/pnpmgr.c:1444) Initialization of service Ne2000 failed
(Status c0000001)
(ldr/loader.c:623)
LdrGetModuleObject(\SystemRoot\system32\drivers\pci.sys) called
Hi Folks:
I was a loooong long time away. I was really missing you all. I noticed something strange in my mailbox when I was looking at the dates and saw that October was not there in my ROS folder, that's why the ping. Today I noticed that they are all in the INBOX(it really takes time to clean so much mail and more if it is all mixed). It was a big surprise to read the changelog and see so much advance. Congratulations everyone. Thank's Steven. I'll update my filters.
Best Regards
Waldo Alvarez
________________________________
From: Steven Edwards [mailto:steven_ed4153@yahoo.com]
Sent: Mon 10/18/2004 9:58 PM
To: ReactOS Kernel List; Waldo Alvarez Cañizares
Cc: ReactOS Kernel List
Subject: Re: [ros-kernel] Pong
--- Mark IJbema <mark(a)ijbema.xs4all.nl> wrote:
> Pong
>
> On Mon, Oct 18, 2004 at 05:20:28PM -0400, Waldo Alvarez Ca?izares
> wrote:
> > Ping
Use ros-dev(a)reactos.com and not ros-kernel. Its going away.
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
Hi!
Ge van Geldorp wrote:
> CVSROOT: /CVS/ReactOS
> Module name: reactos
> Repository: reactos/lib/shlwapi/
> Changes by: gvg(a)mok.osexperts.com 04/10/20 09:20:23
>
> Modified files:
> reactos/include/wine/: shlwapi.h
> reactos/w32api/include/: shlwapi.h
> reactos/lib/shlwapi/: Makefile.ros-template
>
> Log message:
> Simplify wine/shlwapi.h
>
Not to sure how this started time wise,
i386-mingw32-gcc -DWINSHLWAPI= -D_SHLWAPI_ -D__USE_W32API -D_WIN32_IE=0x600 -D_WIN32_WINNT=0x501
-DWINVER=0x501 -D_STDDEF_H -I../../include/wine -I../../include -I../../w32api/include -pipe
-march=i486 -D_M_IX86 -c msgbox.c -o msgbox.o
In file included from msgbox.c:23:
../../include/wine/port.h:248: error: parse error before "pread"
../../include/wine/port.h:248: warning: data definition has no type or storage class
../../include/wine/port.h:252: error: parse error before "pwrite"
../../include/wine/port.h:252: warning: data definition has no type or storage class
make: *** [msgbox.o] Error 1
Thanks,
James
Hello,
Could someone that is a native speaker put together a overview of
ReactOS in English and German? Jason had a flyer we used at LinuxWorld
San Francisco but I am unable to find it. Jason if you still have can
you send it to the list so someone can translate? I will print out a
few hundred copies when I get there. I am leaving in just a bit. I also
have a master CD of the latest CVS that seems to work well for demos
that I am going to press to give 100 copies out while there.
GvG/Fireball can you burn a CD also just in case something goes wrong
with mine?
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
Before this change, the reactos build seems to want to put hal.a in the
root for me (which of course my user doesn't own). Should I commit this?
Also, why was this changed?
Index: tools/helper.mk
===================================================================
RCS file: /CVS/ReactOS/reactos/tools/helper.mk,v
retrieving revision 1.89
diff -u -r1.89 helper.mk
--- tools/helper.mk 20 Oct 2004 20:51:21 -0000 1.89
+++ tools/helper.mk 21 Oct 2004 02:24:43 -0000
@@ -270,7 +270,7 @@
MK_CPPFLAGS := -D__NTHAL__ -I.
MK_IMPLIB := yes
MK_IMPLIBONLY := no
- MK_IMPLIBDEFPATH :=
+ MK_IMPLIBDEFPATH := $(DDK_PATH_LIB)
MK_IMPLIB_EXT := .a
MK_INSTALLDIR := system32
MK_BOOTCDDIR := .
--
Hey, Adam Smith, keep your invisible hands to yourself!
Hi arty,
had the same problem here.
Cordially
PETREOLLE Sylvain
"You believe its the year 2004,
when in fact it's closer to 1984."
Matrix / 1984.
Say no to software patents !
-----Message d'origine-----
De : art yerkes [mailto:ayerkes@speakeasy.net]
Envoyé : jeudi 21 octobre 2004 05:17
À : ros-dev(a)reactos.com
Objet : [ros-dev] Change in tools/helper.mk
Before this change, the reactos build seems to want to put hal.a in the
root for me (which of course my user doesn't own). Should I commit this?
Also, why was this changed?
----------------------------------------------------------------------------
Ce message ainsi que toutes pièces jointes (le "message") sont confidentiels
et sont exclusivement destinés à l'usage de la personne à laquelle ils sont
adressés. Tout point de vue ou toute opinion contenus dans ce message
expriment la pensée personnelle de leur auteur et ne représentent pas
nécessairement la position des sociétés du Groupe GEFCO. Si vous n'êtes pas
la personne à laquelle ce message est destiné, veuillez noter que vous avez
reçu cet e-mail par erreur et qu'il vous est strictement interdit
d'utiliser, de diffuser, de transférer, d'imprimer ou de copier ce message.
Si vous avez reçu ce message par erreur, merci de contacter la personne qui
vous l'a adressé et de l'effacer immédiatement. Les sociétés du Groupe GEFCO
déclinent toute responsabilité en cas d'altération, de modification,
d'édition, de diffusion sans autorisation de ce message ou en cas
d'affection de ce message par un virus.
This message and any attachments (the "message") are confidential and
intended solely for the use of the individual to whom they are addressed.
Any views or opinions presented are solely those of the author and do not
necessarily represent those of the GEFCO Group of Companies. If you are not
the intended recipient, be advised that you have received this email in
error and that any use, dissemination, forwarding, printing, or copying of
this message is strictly prohibited. If you have received this message in
error please contact the sender and delete the message immediately. The
GEFCO Group of Companies shall not be liable for the message if altered,
changed, falsified, edited, diffused without authorization or affected by
any virus.
----------------------------------------------------------------------------
I'm having problems getting atapi drives recognized. Setup:
Primary controller
- master: HD HITACHI_DK23AA-60
- slave: CD-ROM COMPAQ CD-224E
Secondary controller
- master: not connected
- slave: not connected
First of all, the harddisk is not recognized. The call to
AtapiWaitForStatus() in atapi.c line 1159 times out. I can fix this by
increasing the timeout in that call from 20000 to 40000 (the harddisk needs
a minimum of around 38700 here).
After the harddisk is succesfully recognized, detection of the CD-ROM fails.
Again, the call to AtapiWaitForStatus in line 1159 times out, but this time
no amount of increasing the timeout (I've gone up to 4000000, 40 sec, more
than the 30 sec limit in the ATA spec) helps. I've attached the debug log.
Note the lines:
(atapi.c:1161) Timeout on drive 1
and
(atapi.c:992) Unexpected Interrupt, CommandPort=01f0, Status=ff, Count=1
I hope someone more familiar with the atapi driver can take a look at this.
Oh, btw, going back to atapi.c rev 48 cures the problem (both HD and CD-ROM
are recognized and working then).
All help appreciated, Gé van Geldorp.
Hi!
I have been working on some improvements to the device installer functions
of the setupapi dll. I am able to install class installers on my machine and
retrieve information about installed class installers.
My plan is to reorganize the setupapi dll in order to add the configuration
manager apis to this dll and to convert setupapi to a ReactOS dll. The
reason for this change is that additions to the device installer apis or
configuration manager apis are not usable by WINE because it does neither
support windows drivers nor a PnP-Manager. Of course, all additions to
setupapi will be licensed under the LGPL so Wine developers can port useful
code as they see fit.
What do you think?
Regards,
Eric
Hello,
I am going to move reactos/apps/tests in to rosapps as the current
system of tests we have there does not fit in with the ideas of
regression testing. I know there might be some objections to this but
it is not hard to checkout rosapps or add your own custom test there if
you want. We really need to put some effort in to using (And merging
the Wine tests in to) the regression system Jason and Casper have
developed.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
Hi,
sometimes I see a debug messages like this:
(mm/npool.c:1641) Trying to allocate 254736304 bytes from nonpaged pool -
nothing suitable found, returning NULL (objects/text.c:1832) WARNING:
Failed to render glyph!
If this occurs the desktop background is flashing white. The big allocation
request comes from freetype\src\raster\ftrend1.c line #178. Has anyone an
idea what is wrong?
- Hartmut
Hello,
I know we already have a few tests like this in the ReactOS tree but I
have not had time to look at all of them or dig in to this at all.
I am forwarding part of a message from Jeremy White along with some
tests of timers and schedualing in case anyone wants to compare Windows
and ReactOS. We ran in to quite a few issues under CrossOver with
Office applications and were able to work around them. Even
applications such as Internet Explorer are affected. See recent hacky
patches on wine-devel for winmm timer resolution. Anyway here is a bit
of his notes and the collection of tests if anyone is interested.
Thanks
Steven
".....Spinning threads get all the cpu they can chew; being in a
foreground Window gives a pretty high bias, but otherwise things seem
to be evenly spread. Aric did a test program which showed how
SetThreadPriority biases things; it tends to be that only priorities -2
through 2,and 15, have any meaning. Further, if threads yield, then
only thetop priority threads get any time. If all threads 'work', then
there is a stair step effect where high priority threads get 'more',
but don't necessarily get it all."
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
Hello,
I guess the message is directed at James. I am going to merge our
implementation of advpack.dll with the current winehq implementation.
Any objections or suggestions?
Thanks
Steven
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
> Everything looks ok for me. I forgot to mention that Reactos is booted
> from real hardware + freeldr diskette.
> The native ne2000.sys driver from Reactos has also the same problem .
> this can be simulted as follows :
>
> - Build a ntoskrnl.exe with NDEBUG commented in ldr.c
> - Disable Amd Pcnet entry and enable Ne2000 entry in hivesys.inf file
> - Make registry
> - Boot Reactos and check the debug traces for loading of ne2000.sys driver
>
1) corrupt file system
2) bad LFN entry for low case ne200.sys name
3) Ob case sensitive and ne2000.sys in the reg, but NE2000.SYS on fs
____________________________________________________________
Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione.
Abbonati subito su http://www.libero.it
Hartmut Birr wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/ntoskrnl/
>Changes by: hbirr(a)mok.osexperts.com 04/10/17 08:39:32
>
>Modified files:
> reactos/hal/halx86/: irql.c
> reactos/ntoskrnl/ex/: sysinfo.c
> reactos/ntoskrnl/include/internal/: ke.h
> reactos/ntoskrnl/ke/i386/: irq.c kernel.c
> reactos/ntoskrnl/ke/: dpc.c timer.c
> reactos/ntoskrnl/ps/: idle.c thread.c
> reactos/ntoskrnl/: ntoskrnl.def
>
>Log message:
> - Used variables from the KPCR for the current irql, for dpc's, for time counters and for the idle thread.
>
>_______________________________________________
>Ros-cvs mailing list
>Ros-cvs(a)reactos.com
>http://reactos.com/mailman/listinfo/ros-cvs
>
>
>
Hartmut,
_THANK_ You. I was looking forward to doing those changes (and others)
myself as soon as I'm done with the new header system.
Best regards,
Alex Ionescu
Hartmut Birr wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/ntoskrnl/include/internal/i386/
>Changes by: hbirr(a)mok.osexperts.com 04/10/17 03:53:08
>
>Modified files:
> reactos/ntoskrnl/include/internal/i386/: ps.h
>
>Log message:
> - Fixed the definition KPCR_SELF and KeGetCurrentKPCR.
>
>_______________________________________________
>Ros-cvs mailing list
>Ros-cvs(a)reactos.com
>http://reactos.com/mailman/listinfo/ros-cvs
>
>
>
Is that really right? I can swear fs:18h was still used until NT 5.2.
Also, it would be of critical importance to:
1) Change the hardcoded offsets to FIELD_OFFSET(...,...)
2) Make the ASM use the defines instead of hardcoding 1Ch/18h
Best regards,
Alex Ionescu
Hi,
sometimes I get a crash in
ExWorkerThreadEntryPoint/ExInterlockedRemoveHeadList. I've checked all calls
to ExQueueWorkItem. It seems that something is wrong in the tcpip/ndis
driver. There is a timer dpc which calls ExQueueWorkItem with a static work
queue item. If the worker is not execute previous the next timer call, the
item is queued for twice. Possible it is the same bug as #425.
- Hartmut
Hello, if I start the ReactOS Setup from the "make bootcd" I get an
INACCESSIBLE_BOOT_DEVICE. I use the CVS Version of ReactOS. Can you help?
Thanx, EnricoB
Hi all,
Still running the same kernel and subsystem (see previous post) now
for 1 day 5:23 (uptime). System memory is 1.1 GBytes. First build ros
on ros started at 5% use of memory. Now after the uptime, 45% after
third build. New start has it at 24%. Slow leak~ I did not enable the
memory dumps 8^(, So no real data there. The slow action on the cmd
win console has not changed, you can still count the chars displaying
across the screen.
FYI,
James
Currently there are quite a few places in ROS src where 64-bit integral
constants are either hard-coded to be GNU C only (?), or almost worse
littered with conditional compilation.
Neither is satisfactory. 1 is making it impossible to compile using e.g. an
MS compiler, and 2 makes the code so ugly that... Well, you understand.
So, in the interest of fixing this once and for all, the only option is to
name a macro to handle these compiler specifics in one place, and then use
that macro when defining 64-bit integral constants. The question is then,
what to name it? The macro will be defined something like (omitting unsigned
here):
#if defined __GNUC__
#define ZZZ(X) X##LL
#elif defined _MSC_VER
#define ZZZ(X) X##i64
#else
#error Unknown compiler for 64-bit integral constant suffix
#endif
Serious suggestions that have surfaced so far are:
DEFINE_INT64
MAKE_INT64
If suggesting something else, keep in mind that
- while short might be beautiful (and fast to type), using short macros is
likely to sooner or later create conflicts.
- leading underscore followed by capital character or another underscore is
not legal for C++.
- It's to make it clear that it's a 64-bit int defined, why suggestions
mentioning LL or i64, as in compiler-specific extensions/implementation
details, are likely not to help or be accepted since that's exactly what we
want to get away from.
Please comment.
/Mike