With the issue of Ekush talking about sending us patches once they
publish thier code and what not I as many of you are worried about being
tainted, I have an idea, but I don't know how safe it is from a GPL
stand point (I know nothing of the GPL) here's the idea, when we get
patches that are questionable from *any* source, we send MS a copy of
the suggested patch, and request they compare it with thier code to see
if it is differant or the same as thier Windows code, if MS comes back
and says it's teh same we delete the patch and move on...
I know this idea sounds bad but we need to discuss a plan for any
potential tainting and how we'd deal with it, please if you don't like
my idea then please by all means suggest something else.
Hello people,
can you post some sources (links etc.) where I can find some info about
internal NT kernel structure/architecture/whatever suitable for lamers
and newbs like me?
I don't know if anyone has been to ekush.com recently:
> " We are also decided to remove all the non-GPL'd code from our source tree and re-publishing the project based on React OS and Wine. All the Ekush sources will be merged to the React OS tree; sources and binary both will be published accordingly under the GNU GPL and EKUSH.COM will be the official web home for Ekush OS. Hope it will eliminate all the confusion and misunderstanding regarding Ekush Operating System. "
Hi,
Does anyone object agains:
-moving every NtXxx functions into new files under ntoskrnl\nt?
-moveing functions related to ob managed types into new files (thrdobj.c,
procobj,c, eventobj.c, fileobj.c etc)?
This will make it clearer where the functions are and what they do.
Gunnar
I really would like to see less "Fixed feature X" commit messages. Sometimes a features is "fixed" more than once in a short period
of time. Please specify what was changed in the commit message so others have a better chance of knowing what was actually changed
(without looking through the whole patch to figure it out). I'm not saying that simple typos or other trivial changes couldn't have
a "Fixed X" commit message, just that the non-trivial ones shouldn't.
Casper
In light of e.g.
http://reactos.com:8080/archives/public/ros-dev/2004-November/000658.html
I would like to suggest the following header ideas.
Currently MingW has:
1.A set of headers that contain a copy of part of the platform SDK
2.Some extra stuff (like that ntdll.h)
3.A set of headers that contain a copy of part of the windows DDK
4.Mabie again some extra stuff MS doesnt have (I dont know)
5.A set of headers that contain a copy of part of the visual C++ runtime
library
6.Some extra stuff (mainly bits required to deal with differences between
GCC and Visual C I think)
WINE has:
1.A set of headers that are supposed to contain a copy of part of the
platform SDK (although some things have been claimed to be wrong)
2.A set of headers that are supposed to contain a copy of part of the
visual C++ runtime library (although again there may be things that are wrong)
and 3.Extra definitions for stuff in both header sets microsoft doesnt
define in the platform SDK (e.g. internal bits, functions microsoft doesnt
document etc)
ReactOS has:
w32api (the ROS import of it)
include/ddk (the ReactOS version of the windows DDK)
include/wine (the WINE windows API headers)
include/msvcrt (the MSVCRT headers ROS uses to build and link with msvcrt)
include (various misc ReactOS specific headers)
What I suggest for ReactOS (and I think some of this is already being done)
is as follows:
grab any headers from include/* that are public DDK headers (if there are
any) and make sure they are all in include/ddk
grab everything from the current WINE headers MingW is missing. Check that
its all correct and stuff and add it to the ReactOS import of w32api. (if
anything is found to be wrong in the wine headers, it should be fixed)
grab anything from include itself and add to w32api as needed
Get permission to relicence the stuff and contribute back to the main
w32api tree.
grab contents of include/msvcrt on ReactOS plus include/msvcrt on WINE and
also mingw-runtime.
Create one set of header files from the 3 sets such that it matches the
microsoft headers as closely as possible.
Merge w32api DDK headers with ROS DDK headers and create one set that,
again, matches the MS headers.
For w32api/mingw-runtime, the suggestion is that they look at all the "new
stuff" generated by the merging of the 3 sets of msvcrt headers plus the
ROS/WINE/w32api merger plus the DDK merger and look at acccepting it.
For WINE, I suggest they start using the new "merged" headers if at all
possible.
Basicly, the idea is that mingw-runtime would become the "definitive" set
of msvcrt.dll headers out there and that ReactOS, MingW and WINE would
start using it for any case where you are talking to msvcrt.dll from the
public side.
both ROS and WINE would then have their own internal msvcrt headers as
necessary to build their msvcrt* builds
Then, w32api would become the "definitive" set of win32 api headers and
would contain as much of the Microsoft Platform SDK as people have legally
cloned. All userland components of ReactOS (as well as kernel-side bits
that need the stuff in the userland headers e.g. win32k.sys) would use
this. Be nice if WINE were to use this too but because of what WINE is and
how it is built/used, there may be reasons for the WINE team not to use
w32api as the build headers used to build WINE.
And, there would be one "definitive" set of DDK headers which would be good
enough for building ReactOS with. And for building any kernel-side stuff
WINE decides to add (e.g. that stuff to load the device drivers for
vaerious copy protection systems that was being worked on). And for anyone
using MingW and MingW GCC to build kernel-mode stuff.
Anything private or project specific would go into a set of private headers
as needed for the different projects and sub-sections (dlls etc) within them
Anything exported by microsoft but undocumented would go into a set of
"undocumented" headers (which could then be shared between ReactOS and WINE
since I dont think w32api would accept anything not documented in MSDN)
Just suggestions btw, if they are good, say so
If they are bad, say so (and say why)
If there are issues with my idea, say what they are.
Hi,
I've added the 'work item fix' to my source tree for testing. I'm not able
to boot reactos. Ros hangs somewhere in ndis:
...
(ldr/loader.c:319) Could not open module file:
\SystemRoot\system32\drivers\DLKRTS.SYS
(io/pnpmgr.c:1521) Initialization of service DLKRTS failed (Status c0000001)
DriverBase for \SystemRoot\system32\drivers\pci.sys: 9cd89000
Peripheral Component Interconnect Bus Driver
(io/create.c:90) Parent is a Directory which is neither a file type nor a
device type
(io/pnpmgr.c:1521) Initialization of service Ne2000 failed (Status c0000001)
DriverBase for scsiport.sys: 9cd93000
DriverBase for atapi.sys: 9cd9f000
DriverBase for aic78u2.sys: 9cdc9000
DriverBase for class2.sys: 9ce6b000
DriverBase for disk.sys: 9ce75000
DriverBase for vfatfs.sys: 9ce7e000
DriverBase for bootvid.sys: 9ce93000
DriverBase for ndis.sys: 9ceb4000
(ndis/main.c:52)(DriverEntry) Called.
(ke/main.c:710) CommandLine: multi(0)disk(0)rdisk(0)partition(3)\ReactOS
Without the fix, booting continues after that point with:
DriverBase for \SystemRoot\system32\drivers\DLKRTS.SYS: 9cf09000
(ndis/miniport.c:1090)(NdisInitializeWrapper) Called.
(ndis/miniport.c:1631)(NdisMRegisterMiniport) Called.
(ndis/miniport.c:1577)(NdisIAddDevice) LinkageKey:
Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0002\Linkage.
(ndis/miniport.c:1374)(NdisIStartAdapter) creating device \Device\DLKRTS1
(ndis/miniport.c:1394)(NdisIStartAdapter) opened device reg key
(ndis/miniport.c:1396)(NdisIStartAdapter) acquiring miniport block lock
...
- Hartmut
Hi,
I think I found a race condition in KQUEUE code, but I'm not sure my
solution is optimal. If no items are queued, KeRemoveQueue calls
KeWaitForSingleObject and then after it finishes it acquires dispatcher
lock and removes a list item. The problem arises when someone calls
KeRemoveQueue just after the KeWaitForSingleObject call finishes and
before the dispatcher lock is acquired. In this case he can remove the
last item in the list and this will cause the first KeRemoveQueue (the
one that waited) to return garbage. Can anybody think of better solution
than the attached patch?
Regards,
Filip
Index: ntoskrnl/ke/queue.c
===================================================================
RCS file: /CVS/ReactOS/reactos/ntoskrnl/ke/queue.c,v
retrieving revision 1.11
diff -u -r1.11 queue.c
--- ntoskrnl/ke/queue.c 15 Aug 2004 16:39:05 -0000 1.11
+++ ntoskrnl/ke/queue.c 21 Nov 2004 00:39:52 -0000
@@ -159,27 +159,38 @@
return ListEntry;
}
- //need to wait for it...
- KeReleaseDispatcherDatabaseLock (OldIrql);
-
- Status = KeWaitForSingleObject(Queue,
- WrQueue,
- WaitMode,
- TRUE,//Alertable,
- Timeout);
-
- if (Status == STATUS_TIMEOUT || Status == STATUS_USER_APC)
- {
- return (PVOID)Status;
- }
- else
+ for (;;)
{
- OldIrql = KeAcquireDispatcherDatabaseLock ();
- ListEntry = RemoveHeadList(&Queue->EntryListHead);
+ //need to wait for it...
KeReleaseDispatcherDatabaseLock (OldIrql);
- return ListEntry;
- }
+ Status = KeWaitForSingleObject(Queue,
+ WrQueue,
+ WaitMode,
+ TRUE,//Alertable,
+ Timeout);
+
+ if (Status == STATUS_TIMEOUT || Status == STATUS_USER_APC)
+ {
+ return (PVOID)Status;
+ }
+ else
+ {
+ OldIrql = KeAcquireDispatcherDatabaseLock ();
+
+ /*
+ * Prevent a race condition. If someone calls KeRemoveQueue
+ * just after we end up waiting and before acquiring the spin
+ * lock he can get the last item in the list...
+ */
+ if (IsListEmpty(&Queue->EntryListHead))
+ continue;
+
+ ListEntry = RemoveHeadList(&Queue->EntryListHead);
+ KeReleaseDispatcherDatabaseLock (OldIrql);
+ return ListEntry;
+ }
+ }
}
These are a big mystery to me. I'd like to document how to create them, but I need to know how to create them first. Please send me
any information you have on them.
Casper
I'm hoping to get putty working to use as another test case for the network
code. I'm running into problems right now, however and could really use
a hand.
There are two versions of putty in here, built with symbols as well as a
diff against the original sources and a mingw-able makefile named
makefile.mgw
I haven't tried the mingw makefile on windows but it shouldn't take too
much effort.
putty-noshow differs from the release putty only in that it contains
debug messages and symbols. The putty dialog is created and the caret
timer even fires, but the window is never shown. w3seek thinks that
the dialog functions in user32 and win32k are correct, but the dialog
shows on windows and wine so something is wrong.
If I add a ShowWindow as in putty-show, the dialog shows, so the
problem is clearly in reactos.
I'm seeing some random crashes as well accessing the registry that
will be the subject of another mail.
my putty musings: http://64.81.145.152/~arty/putty.zip
Putty page: http://www.chiark.greenend.org.uk/~sgtatham/putty/
--
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
Does anyone care if I merge the duplicate headers from
reactos/include/wine in to the headers in the reactos/w32api/include
folder? There are a few headers we will want to keep in
reactos/include/wine but now that we have our own copy of the w32api we
dont need most of these headers that do the #include_next thing.
Thanks
Steven
__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com
I have set up an account at CafePress, and would like
to make some ReactOS merchanise, for advertisment
purposes. I do not intend on adding a retail markup
to the base price of the items in question- the prices
will be solely the price mandated by CafePress for
fabrication and shipment. (this means I make nothing)
Some of the items that can be made, include Mugs,
buttons, mousepads, T-shirts, hoodies... ...Thongs...
and other misc. items.
I think it could have utility for us as a project, on
occasions where we are promoting our project-- Things
like "ReactOS Developer" buttons for our booth
sitters, etc...
I would like a "Yeah"/"Nay" vote, and then I may
require a written letter of permission allowing me to
use the logo. (The letter is required by the CafePress
legal terms of service contract)
Please let me know what you think of the idea.
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com
Hi,
>What was the reason for these changes? It looks like a workaround for
some other bug.
it is a nice question after more than one year.
>http://cvs.reactos.com/cgi-bin/cvsweb.cgi/reactos/ntoskrnl/ke/wait.c.diff?r
1=1.51&r2=1.52
KeRemoveAllWaitsThread was called in two situations. One was a real
unblocking of the thread, if the thread was waiting on a waitable object
which was signaled. The other was the terminating of the thread by an other
thread. In this case KeRemoveAllWaitsThread has worked if the thread was
waiting on a waitable object. If the thread was simply suspended,
RemoveEntryList has bug checked because Waiter->WaitListEntry wasn't in any
list. The reason for these changes was the implementation of the CTRL-C
handlers in csrss.
- Hartmut
This fixes the problem with regedit (regedit freezes after opening a
child window).
Regards
Christian
------------------------------------------------------
Index: framewnd.c
===================================================================
RCS file: /CVS/ReactOS/reactos/subsys/system/regedit/framewnd.c,v
retrieving revision 1.11
diff -u -p -r1.11 framewnd.c
--- framewnd.c 11 Oct 2004 21:08:05 -0000 1.11
+++ framewnd.c 18 Nov 2004 21:56:01 -0000
@@ -670,8 +670,10 @@ FrameWndProc(HWND hWnd, UINT message, WP
OnMenuSelect(hWnd, LOWORD(wParam), HIWORD(wParam), (HMENU)lParam);
break;
case WM_ACTIVATE:
- if (LOWORD(hWnd))
- SetFocus(g_pChildWnd->hWnd);
+ // I don't know what this is supposed to do (except for
creating an infinite "setfocus loop").
+ // If someone ever figures it out put it back in plz.
+ //if (LOWORD(hWnd))
+ // SetFocus(g_pChildWnd->hWnd);
break;
case WM_DESTROY:
WinHelp(hWnd, _T("regedit"), HELP_QUIT, 0);
------------------------------------------------------
Hey everybody-
I seem to be consistantly running into troubles with
Freetype and Greenville. I suspect the problem stems
from Freetype trying to render the glyph with too many
shades of grey, and I *SERIOUSLY NEED* somebody to fix
it.
Here is a more technical view of the situation, and
the problem:
The TrueType hinting system allows each pixel to be
subdivided into sub-units. There are 81 subunits per
pixel, in a 9x9 grid, with the center being the origin
point. So, it looks something like this:
87654321012345678
7XXXXXXXXXXXXXXXX
6XXXXXXXXXXXXXXXX
5XXXXXXXXXXXXXXXX
4XXXXXXXXXXXXXXXX
3XXXXXXXXXXXXXXXX
2XXXXXXXXXXXXXXXX
1XXXXXXXXXXXXXXXX
0XXXXXXXXXXXXXXXX
1XXXXXXXXXXXXXXXX
2XXXXXXXXXXXXXXXX
3XXXXXXXXXXXXXXXX
4XXXXXXXXXXXXXXXX
5XXXXXXXXXXXXXXXX
6XXXXXXXXXXXXXXXX
7XXXXXXXXXXXXXXXX
8XXXXXXXXXXXXXXXX
That represents the total number of subunits, and
their coordinate placements within 1 pixel.
The windows rasterizer determines the 'shade' the
pixel will get, based on % of coverage this pixel gets
from the outline, as does freetype. The problem shows
up, because The windows type rasterizer only renders
16 shades, including Black and White, while the
Freetype one renders 256 shades.
There are only 81 units, however.
What does this mean? It means that under freetype as
it currently stands, if even *ONE* pixel subunit is
covered by an outline, it will render as a shade of
grey--- While the exact same pixel, with the windows
rasterizer, will render as 'white' instead.
This is because "white" is 1/256th coverage, and there
are only 81 subunits-- Essentially meaning that in
order to get 'white' out of freetype, the pixel cannot
be touched *AT ALL* by the glyph outline.
On the windows rasterizer, there are only 16 shades of
grey, so up to 1/16th of the area can be covered, and
still rendered as 'white'-- or 5 subunits covered.
This is why the windows rasterizer produces crisper
images than Freetype.
I don't know how to fix this behavior in Freetype, and
*SERIOUSLY* need said behavior changed, As soon as
possible.
Thank you.
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com
Hi Rick:
I think you mean something like the make xconfig or make gconfig you can do when building the Linux kernel. Hmm I think if that´s what you mean ROS could have a little GUI application to configure the system. I mean to make life easier to non-programmers that wish to build a custom system. That's one of the things Linux users enjoy very much and I think that would be good for ROS too and won't take very long to do. Also if it is done general enough won't have to be maintained in the future. Well at least not that much.
Regards
Waldo
________________________________
De: ros-dev-bounces(a)reactos.com en nombre de Rick Langschultz
Enviado el: Jue 11/11/2004 6:53 p.m.
Para: ros-dev(a)reactos.com
Asunto: [ros-dev] ReactOS Versions
When ReactOS is built and runs windows executables stabily I think we should have a program for windows that will let you customize the platform like windows ce and compile it with all the features you want. I think that it would be a great idea because of different types of systems such as PBX/VOIP servers, application servers, and domain name servers. This would allow security to be integrated into ReactOS by limiting programs allowing open ports, and Denial of service attacks. Maybe even support for multiple architectures like SH, ARM, X86, AMD64, PPC??? With FAT, FAT32, NTFS, XFS, EXT3, EXT2, and many others. Maybe even a rom based os... Please tell me what you all think.
Hi.
I'm was fixing some code,
se\semgr.c->SeLockSubjectContext/SeUnlockSubjectContext, where apc's were
not disabled before/after
ExAcquireResourceExclusiveLite/ExReleaseResourceLite using
KeEnterCriticalRegion/KeLeaveCriticalRegion.
KeEnterCriticalRegion/KeLeaveCriticalRegion access current thread and this
triggers bsod->"no current process".
call chain:
CmInitializeRegistry->ObCreateObject->SeCaptureSubjectContext->SeLockSubject
Context
CmInitializeRegistry is called in ke\main.c before the initial process is
created.
What should i do? Add checks for if the current process/thread exist or not
in KeEnterCriticalRegion/KeLeaveCriticalRegion or is there some other way to
fix this?
Gunnar
As someone have stated in the forum, the Roadmap is
YEARS old, could you send me the projects you are
working in, and the expected (realist ones) dates of
conclusion.
That way i could make a new roadmap.
Thankyou again,
Lucio Diaz.
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
I am working in a Howto for installing ReactOS, so i
tried the diferent ways for instalating it, but in
recent builds there was no option to install the
Freeloader in a diskete (XP machine here) in the Real
Hardware instalation.
I tried downloading the binaries and copying them to
C:\ReactOS , download the Freeloader image and
RAWwrite it in a diskete, but i could not get the
configuration screen (it worked for me, but maybe not
for others without configuration options)
Is there any way i could install the Freeloader image
and still have a "normal" configuration phase of
ReactOS.? This will help convince people to install
reactOS, not having to touch the Boot sector for a
ReactOS insatllation regardless the OS you have
installed would be great. I imagine something like
this:
--------------------------------------
1) Download the ReactOS binaries (8 Megs) from
sourceforge
2) Use Winzip to extract them to C:\ that way a Folder
called C:\ReactOS will be created with all the reactos
files(It must be a FAT32 partition).
3) Download the Program Rawwrite for windows and
extract it to any folder you wish.
4) Download the Freeloader Floopy Disk image and
extract it to any folder you wish.
5) Insert a new formated Floopy Disk and Execute
Rawwrite:
6) Select the image file from the folder you extracted
the Freeloader:
7) Press write, and wait till the program ends writing
the image to the Floopy.
8) Restart the computer booting from the Floopy Disk:
----------------------------------------
This is the option i would like as user. Copy the
program to a folder, and the use a Diskete to load it.
Usefull both in 95/98/NT/XP and Linux, with minimal
risks for people who fears burning their HD.
But the question, Can this be done?. I have downloaded
the source code but i am lost. Can someone help me
with this?
Thanks in advance,
Lucio Diaz.
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
Hi!
Isn't it possible to call NdisIStartAdaper (in ndis/miniport.c) when the
miniport driver recieves an IRP_MJ_PNP/IRP_MN_START_DEVICE request? Right
now it is called from NdisIAddDevice.
This means the miniport device is started before resource lists are assigned
to the NICs device node. NdisMQueryAdaperResources and
NdisMPciAssignResources cannot be implemented oe won't work because of this.
Regards,
Eric
I intend to move the following important software from rosapps to reactos/subsys/system:
calc
regedt32
regsvr32
sysutils/ctm
and the following to reactos/apps/utils/net:
net/ping
net/arp
net/finger
net/ipconfig
net/netstat
net/telnet
net/whois
Actually there are two telnet applications. Which is better?
If I've left out something important, please speak up.
Casper
For a many month I am unable to install ReactOS with DBG=1 and KDBG=1
enabled.
On the same hardware, version with DBG=0 and KDBG=0 installs and runs fine.
DBG=1, KDBG=1 enabled ReactOS booted by freeldr asks for COMUTERNAME,
Name, password, time zone etc. etc. and asks for reboot.
Then it bugchecks with :
bt
Frames: vmwinst.exe: vmwinst.c: 75 (DetectVMware)
bugcheck
KeBugCheck at dbg/kdb.c: 1495
Bug detected (code deaddead param 0 0 0 0)
Page fault at high IRQL was 2
KeBugCheckWithTf at ke/catch.c:165
Bug detected (code 1e param 0 0 0 0)
KMODE_EXCEPTION_NOT_HANDLED
Page fault Exception: 14(0)
Processo: 0 CS:EIP 8:c00b8cb7 <ntoskrnl.exe: rtl/message.c:108
(RtlFindMessage)>
cr2 e07a4604 cr3 1d84a000
Proc: c0eb1c90 Pid:7 <vmwinst> Thrd: c0ebd08 Tid: 2c
DS 10 ES 10 FS 30 GS 10
kernel stack base df255000
KeBugCheckWithTf
KeBugCheckEx
KeBugCheck
DbgBugCheckCommand
KdbDoCommand
KdbMainLoop
KdbInternalEnter
KdbEnterDebuggerException
KiDispatchException
ke/i386/usertrap.c: 139 KiUserTrapHandler
ke/i386/exp.c: 613 KiTrapHandler
/tmp/ccphDdwg.s: 146 KeUserModeCallback
vmwinst.c: 75 DetectVMware
vmwinst.c:1016 WinMain
1047 WinMain
kernel32.dll: BaseProcessStart <DEADBEEF>
If someone is interested in more debugging informations, I can send
processor registers and map files.
Regards,
David
--
David Kredba <kredba at ibot.cas.cz>
GPG: ID 1024D/5B6B02DE
Fingerprint: F0B3312596BEDCF91DFB 0699E06AACD75B6B02DE
PLease find the status of the Reactos support for the Nic Realtek8139 as
per my testing.
1) Detection of Pci Bus2 = Fixed
The problem of enumerating cards located on PCI BUS 2 has been fixed by
Eric Khol . The bug# 436 can be closed
2) Start Nic driver failure
The RTL8139.SYS driver loads successfully but fails to start due to the
"NdisMQueyAdapterResources" function which is unimplemnted .
The Bug#446 has been created
=> This is a blocking point for networking with this popular Nic
Best regards
Gerard
Are you getting this ?
(DBG=1, KDBG=1)
make[1]: Entering directory `/home/dave2/ros/reactos/lib/msafd'
mingw32-gcc -I./include -Wall -Werror -fno-builtin -DUNICODE
-D__USE_W32API -I.-I../../include -I../../w32api/include -pipe
-march=i486 -D_M_IX86 -g -c misc/sndrcv.c -o misc/sndrcv.o
misc/sndrcv.c: In function `WSPRecv':
misc/sndrcv.c:66: error: `AFD_IMMEDIATE' undeclared (first use in this
function)
misc/sndrcv.c:66: error: (Each undeclared identifier is reported only once
misc/sndrcv.c:66: error: for each function it appears in.)
misc/sndrcv.c: In function `WSPRecvFrom':
misc/sndrcv.c:214: error: `AFD_IMMEDIATE' undeclared (first use in this
function)
misc/sndrcv.c: In function `WSPSend':
misc/sndrcv.c:365: error: `AFD_IMMEDIATE' undeclared (first use in this
function)
misc/sndrcv.c: In function `WSPSendTo':
misc/sndrcv.c:503: error: `AFD_IMMEDIATE' undeclared (first use in this
function)
David
--
David Kredba <kredba at ibot.cas.cz>
GPG: ID 1024D/5B6B02DE
Fingerprint: F0B3312596BEDCF91DFB 0699E06AACD75B6B02DE
I found the bug in our ne2000 driver that perplexed filip. The bug was that
the meaning of the PACKET_HEADER part in ne2000 that was skipped was a simple
header put on each packet to determine what buffer page would be used next.
This header is only 4 bytes and has nothing to do with the ethernet frame
header.
I've now factored in the ethernet frame header and made tcpip work the right
way, that is to remove consideration of the ethernet frame header at layers
above lan in the receive pipe. This should make all adapters work the same
way for larger packets (and ne2000 now work right).
I found few references to how this actually works so I could still be wrong,
but I'm going on what filip said and this:
http://cvs.sourceforge.net/viewcvs.py/openh323/pwlib/tools/PacketVxD/epacke…
Which basically confirms filip's opinion.
Please try it out.
--
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
Just came across this: http://www.genesi.lu/
Appears to be a new PPC based platform with published specs - would be
great to have ROS running on this!
Cheers
Jason
Hi,
I think some of your changes in apc.c are wrong. Apc's are always thread
local. They have nothing to do with the dispatcher database lock. The only
locking object is the ApcQueueLock from the thread structure.
- Hartmut
> -----Original Message-----
> From: ros-cvs-bounces(a)reactos.com
> [mailto:ros-cvs-bounces@reactos.com] On Behalf Of ion(a)cvs.reactos.com
> Sent: Thursday, November 11, 2004 2:24 PM
> To: ros-cvs(a)reactos.com
> Subject: [ros-cvs] CVS Update: reactos
>
>
> CVSROOT: /CVS/ReactOS
> Module name: reactos
> Repository: reactos/ntoskrnl/ps/
> Changes by: ion(a)mok.osexperts.com 04/11/11 14:23:53
>
> Modified files:
> reactos/include/ddk/: kefuncs.h ketypes.h
> reactos/ntoskrnl/include/internal/: ke.h ps.h
> reactos/ntoskrnl/ke/: apc.c process.c wait.c
> reactos/ntoskrnl/mm/: marea.c virtual.c
> reactos/ntoskrnl/mm/i386/: page.c
> reactos/ntoskrnl/ps/: psmgr.c
>
> Log message:
> Kernel:
> - apc.c: Fixed some bugs and used Dispatcher Lock.
> Simplified some functions and renamed/inlined others.
> - wait.c: Fixed some assumptions about Dispatcher Lock
> and Waiting/Alertability
> - process.c: Fully implemented KeStackAttachProcess and
> KeStackDetachProcess. Made all functions use PKPROCESS and
> not PEPROCESS.
> Memory Manager: Fixed calls to
> KeAttachProcess/DetachProcess to typecast PKPROCESS
> Process Manager: Removed call to empty function in apc.c
>
> _______________________________________________
> Ros-cvs mailing list
> Ros-cvs(a)reactos.com
> http://reactos.com/mailman/listinfo/ros-cvs
>
Hi James,
>I can start taskmgr but it does not display at all! I've even seen it
>running
>by executing ps.exe. I started with cmd at boot time and executed taskmgr
>from
>the cmd prompt and I get the gui loaded but w/o the taskmgr displayed.
>After
>a Alt-F4 and a click of the mouse I get this.
>
>(objects/gdiobj.c:711) called from: objects/color.c:453
>(objects/gdiobj.c:537) Invalid ObjectHandle 0x00050022
>(objects/gdiobj.c:709) GDIOBJ_LockObj failed for 0x00080021, reqtype
>0x00080000
>reason 1
>(objects/gdiobj.c:711) called from: objects/color.c:453
>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:dd7af992 <win32k.sys: 13992>
>cr2 f000e8e2 cr3 3ce4e000 Proc: c0b24228 Pid: 4 <csrss> Thrd: c0b7c900 Tid:
>27
>DS 10 ES 10 FS 30 GS 10
>EAX: f000e816 EBX: 00000000 ECX: f000e816
>EDX: ccfc0eb0 EBP: ddc26dcc ESI: 00d2feb0 ESP: ddc26d40
>EDI: ddc26f84 EFLAGS: 00010282 kESP ddc26d40 kernel stack base ddc24000
>Frames: <win32k.sys: 130c7> <win32k.sys: 13290> <win32k.sys: 1d1e6>
><win32k.sys:
> 1d7f7> <win32k.sys: 1db26> <ntoskrnl.exe: 35cd> <77E7036B>
>
>This was with real hardware.
>
I will try it on real hardware in the next days too.
>
>Sorry I'm still hacken it,
>James
What are you hacking?
Theo
_________________________________________________________________
So einfach geht das. MSN Toolbar mit Pop-up-Blocker. http://toolbar.msn.de/
Jetzt kostenlos downloaden und gut ist!
Hello,
As some work is being done on sounds , i am willing to make some testing
as well on my real hardware configuration based on "SB live value!"
sound card
In order to be efficient , and to merge effort , I 'd like to know on
what basis the test can be done :
1) drivers
- Reactos drivers
- Oem drivers
- Drivers available as Gpl
2) Applications
- Winamp version 2 or 5 , version lite , full ?
- other applications
3) Test progress - results
How to share the test progress ? Wiki page ?Reactos Reactos
Best regards
Gerard
When ReactOS is built and runs windows executables stabily I think we
should have a program for windows that will let you customize the
platform like windows ce and compile it with all the features you want.
I think that it would be a great idea because of different types of
systems such as PBX/VOIP servers, application servers, and domain name
servers. This would allow security to be integrated into ReactOS by
limiting programs allowing open ports, and Denial of service attacks.
Maybe even support for multiple architectures like SH, ARM, X86, AMD64,
PPC??? With FAT, FAT32, NTFS, XFS, EXT3, EXT2, and many others. Maybe
even a rom based os. Please tell me what you all think.
Hi,
I'm getting repeatedly kernel crashes in regobj.c - CmiObjectParse (line
168). To reproduce the crash start task manager with a right click on the
taskbar, minimize this instance of taskmanager and start a new one.
Here the code
----
else
{
if ((FoundObject->KeyCell->Flags & REG_KEY_LINK_CELL) &&
!((Attributes & OBJ_OPENLINK) && (EndPtr == NULL)))
{
DPRINT("Found link\n");
RtlInitUnicodeString(&LinkPath, NULL);
----
FoundObject->KeyCell is NULL. Does anybody else have the same problem?
I've attached two screenshots of the BSODs. Clean compile of last cvs
snapshot.
Regards,
Theo
_________________________________________________________________
Tun Sie Ihrem Rechner was Gutes. MSN Hotmail mit McAfee® Anti-Virus.
http://www.msn.de/email/antivirus/ Jetzt kostenlos anmelden!
> From: nazmul ahsan [mailto:nahsan@hotmail.com]
>
> I am not associated with the Ekush project, but as a
> Bangladeshi I feel
> embarassed at the boneheadedness of a fellow countryman.
>
> However, while you're demanding that he/them be brought to
> justice, please be aware of the nature of Bangladeshi law
> enforcement:
> http://www.hrcbmdfw.org/bk_news/press_release_09082004.htm
Please note that we have not demanded that the people of the Ekush project
be brought to justice. The only thing we demand is that they either stop
distributing Ekush as long as it contains our code, or comply with the GPL
by putting back copyright notices and publishing source. Since the Ekush
website is currently down, effectively stopping the distribution I don't
think we'll be taking further action.
Gé van Geldorp.
ReactOS is quite slow today, are we under a DoS
atack?, maybe related to this ekush guy?.This is
weird.
Lucio Diaz.
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
Ekush (http://www.ekush.com) published some binaries. Surprise, surprise, it
looks like ReactOS very much (Check e.g. the radio buttons on the "Accept
License" screen during 2nd stage setup). Their readme.rtf
(epc/doc/Readme.rtf) has these entries:
<quote start>
Q. Is the OS completely written from scratch?
A. Not really in many cases, at least 50% of the components has been shared
or taken from some other projects. In fact, we mostly get the ideas and
writing them for ours. Eventually we are coding them new folks are based on
something else (in wish list) and slowly-slowly they will be removed from
our main source tree.
Q. You guys says Project published under the GPL but why dont you
published sources?
A. Initially we decided that, EKUSH should be published under the GPL. But,
still there is some confusion within the team. We are now sharing sources
between team members only and unless the confusion goes removed we cannot
publish sources.
Finally, we decided to use a BSD styled license for Ekush and sources or
binaries whatever we publish should be free to public and covered by the
same license (until a functional edition is released).
Information sources and Wish List:
Bochs, Wine, QEMU, Freetype, React OS, Nova OS, Minuet OS, Flask, Athe OS,
FreeBSD, Systernals, Flik OS, Plan 9, Fravee, V2 OS, Uranium, Fhreed JS,
Free Dos, OP OS, Jlink Wrap, NETrove, Fedora, LFS, Tiny OS, Pear PC, BartPE,
KDesktop, Line, WinPenguins, 3D Desktop,
Dr. Anil Basu, Jason Robin, William Harry, Luiz Quarteiro, Fernando Adantas,
Sergio Luiz Silva, John Abraham, Little Robin, Lina Sen, Maria, Adnan, James
Bukan, Dr. Piera and Project 21 Team."
<quote end>
My guess is they are in violation of the GPL by using (some of) our source
and not publishing their source.
Gé van Geldorp.
I took a picture of the screen:
http://mike.warpedbelief.com/images/ros-crash.jpg
It crashed immediately after I hit a key during the "Press any key to
boot CD..." prompt.
I can't really figure out if any hardware could cause problems. This
is the configuration:
Pentium 120 MHz
64 MB of RAM
2 GB hard disk (I think it's Western Digital)
2 MB ET4000 video
36x CD-ROM drive
One floppy drive
The hard disk partition scheme is this:
One primary partition. FAT16. Windows NT 4 Server install on it. Takes
up the whole 2 GB.
Hello,
While you guys are working on the website changes I would like to add
that the Wine application database is GPL, in CVS and is done in PHP.
http://cvs.winehq.com/cvsweb/appdb/
Thanks
Steven
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
chorns(a)cvs.reactos.com wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/tools/
>Changes by: chorns(a)mok.osexperts.com 04/10/24 10:51:33
>
>Modified files:
> ./: ChangeLog
> reactos/ntoskrnl/: Makefile
> reactos/regtests/regtests/: regtests.c regtests.def
> reactos/regtests/shared/: regtests.h
> reactos/tools/: regtests.c
>Added files:
> reactos/ntoskrnl/tests/: .cvsignore Makefile setup.c stubs.tst
> reactos/ntoskrnl/tests/tests/: .cvsignore
>
>Log message:
> 2004-10-24 Casper S. Hornstrup <chorns(a)users.sourceforge.net>
>
> * ntoskrnl/Makefile (TARGET_REGTESTS): Define to yes.
> * regtests/regtests/regtests.c (_ExitProcess): Declare.
> * regtests/regtests/regtests.def (_ExitProcess@4): Ditto.
> * regtests/shared/regtests.h (_ExitProcess): Ditto.
> * tools/regtests.c: Exit process using _ExitProcess();
> Properly support fastcall symbols.
> * ntoskrnl/tests: New directory.
> * ntoskrnl/tests/tests: Ditto.
> * ntoskrnl/tests/.cvsignore: New file.
> * ntoskrnl/tests/Makefile: Ditto.
> * ntoskrnl/tests/setup.c: Ditto.
> * ntoskrnl/tests/stubs.tst: Ditto.
> * ntoskrnl/tests/tests/.cvsignore: Ditto.
>
>_______________________________________________
>Ros-cvs mailing list
>Ros-cvs(a)reactos.com
>http://reactos.com/mailman/listinfo/ros-cvs
>
>
>
Hi,
I can't say I'm terribly overjoyed with having the /tests directory in
/ntoskrnl. Would it be possible instead to have a /tests root (on the
new SVN server) where all the tests would go? like /tests/ntoskrnl,
/tests/kmregtests etc...
I think it would make it a bit clearer...it just bugs me to have /tests
in ntoskrnl.
Best regards,
Alex Ionescu
Hi Everyone,
We got very good feedback from LinuxWorld.de and I will be returning
next year. 90% of the people visting our booth left thinking very
highly of our work. All in all the results were much better than the
last expo. I very surprised that so many people came up to us and said
"we have heard of ReactOS or we have tried it out".
Here is my rough list of notes on where I think we need to go from here
after discussion with the developers and users.
1. We need a roadmap for the future.
THIS DOES NOT MEAN THAT THERE ARE FIRM DATES ATTACHED!!!!
But we do need to plan our 0.3, 0.4, 0.5 and 1.0 releases. During a
dinner discussion with some of the dev team I asked the question "What
do we need before we can have a ReactOS Workstation 1.0" and it does
not seem to be to far out of grasp. Dont get me wrong there are LOTS of
little things that must be done but the major things we need to have a
real replacement workstation are below. If you think about what Windows
NT 4 had even with Service Pack 6 we are not that far off. Note I am
not talking about a server replacement here. Just a usable client OS.
- Networking (0.3)
- Samba port needs to implemented (0.4)
- We need to implement Windows style printing support (0.4 or 0.5)
- Most applications need to install..Office 2000/XP, Quicken, etc
(0.4)
- We have to develop our own Hardware Compatibity List (0.5)
- NTFS (????)
- It must be stable (1.0)
2. We have to have regression testing in place.
Lack of stablity and regressions are killing us. We have to have the
Wine tests in ReactOS. We also need a suite of kernel mode tests.
Casper's system seems like its going to work well for the kernel mode
side but most of us seem to be worried about the lack of being able to
use Winehq regression tests for user mode.
3. We need to improve our documentation and website.
After much discussion and two too many beers on my part our discussions
turned to documentation and the website. We all agreed that the current
system is not working and we need to develop a method of storing most
of the website in CVS so that people can send us a patch. Same thing
with the documentation....none of us wants to use ezPublish to develop
documentation when we can all use docbook right out of cvs and submit
diffs. Most of us even like the Wiki system as its not hassle and can
maintain a history as well.
4. We need to develop relationships with vendors.
This ties in to getting ReactOS stable and usable. Once we have 0.3 out
the door I expect things will change for us in ways no one can see. I
am going to focus more on this in the coming months, first in the way
of hardware donations.
5. Moving to subversion.
There still seems to be some problems with this and while we all seem
to look forward to it, CVS is doing its job for the moment. GvG has
offered to setup a CVS mirror to help with some of the bandwith
problems of mok.
In closing it was very cool to get to meet all of the developers that
were able to make it, I feel like we are going in the right direction
and I look forward to your feedback.
Thanks
Steven
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
--- "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
Freeldr can now be loaded as a "multiboot kernel" by multiboot compliant
bootstrap loaders like Grub. To load FreeLoader from Grub use something
like this:
title ReactOS
root (hd0,0)
kernel /freeldr.sys
You can also override settings in the [FREELOADER] section of freeldr.ini by
passing them on the command like, like this:
title ReactOS
root (hd0,0)
kernel /freeldr.sys DefaultOS=ReactOS TimeOut=0
title ReactOS (Debug)
root (hd0,0)
kernel /freeldr.sys DefaultOS=ReactOS_Debug TimeOut=0
After selecting "ReactOS" from the Grub menu you won't have to make another
selection on the freeldr menu because of the "TimeOut=0"
Gé van Geldorp.
I found a note, in Kernel Mustard's (Steve Dispensa) blog, about guarded
mutexes, which is a completely new synchronization object to me.
typedef struct _KGUARDED_MUTEX
ULONG Count;
PKTHREAD Owner;
ULONG Contention;
KGATE Gate;
WORD KernelApcDisable;
WORD SpecialApcDisable;
ULONG CombinedApcDisable;
} KGUARDED_MUTEX, *PKGUARDED_MUTEX;
What are they? KM says they are less expensive than FAST_MUTEXes.
By the way, what is a KGATE?
Emanuele
Hello, if I try to compile explorer the following error occurs:
explorer.cpp: In function `int wWinMain(HINSTANCE__*, HINSTANCE__*, TCHAR*, int)':
explorer.cpp:714: error: call of overloaded `wcsstr(TCHAR*&, const wchar_t[9])' is ambiguous
c:/mingw/bin/../lib/gcc/mingw32/3.4.1/../../../../include/string.h:119: note: candidates are: wchar_t* wcsstr(const wchar_t*, const wchar_t*)
c:/mingw/bin/../lib/gcc/mingw32/3.4.1/../../../../include/c++/3.4.1/cwchar:227: note: wchar_t* std::wcsstr(wchar_t*, wchar_t*)
...
mingw32-make: *** [explorer.o] Error 1
Is there a problem with my w32api version?
EnricoB
Hi,
currently I'm trying to get ros to work on a multiprocessor system. There
exist many problems. The major problem is a dead lock, which occurs if
different processors try to acquire the DispatcherDatabaseLock and the
PiThreadLock. Sometimes, it seems, the sequence to acquire the two locks is
different. It would be nice, if someone can look for this problem.
- Hartmut
Hi,
since there have been several reports of the ROS CDs failing to boot
with the "Invalid partition table magic" message I though if the line 85
in freeldr/fs/fs.c can be the cause. If the CD-ROM drive would get
assigned the 0x80 BIOS number (can this everr happen?) then we would end
up reading partition table from it and crash later.
Any thoughts?
Regards,
Filip
Index: freeldr/fs/fs.c
===================================================================
RCS file: /CVS/ReactOS/freeldr/freeldr/fs/fs.c,v
retrieving revision 1.14
diff -u -r1.14 fs.c
--- freeldr/fs/fs.c 25 May 2004 21:31:27 -0000 1.14
+++ freeldr/fs/fs.c 30 Oct 2004 15:01:41 -0000
@@ -82,7 +82,7 @@
}
// Check for ISO9660 file system type
- if (DriveNumber > 0x80 && FsRecIsIso9660(DriveNumber))
+ if (DriveNumber >= 0x80 && FsRecIsIso9660(DriveNumber))
{
DbgPrint((DPRINT_FILESYSTEM, "Drive is a cdrom drive. Assuming ISO-9660 file system.\n"));
Hi,
Is it okay to commit a broken port of wine Msi.dll source to our cvs? 8^P
I'm working on avdpack.dll with msiexec.exe.
I have bison working with building the port, that was not the problem.
It's this;
i386-mingw32-gcc -Wl,--base-file,base.tmp \
-Wl,--entry,_DllMain@12 \
-mdll -Wl,--image-base,0x777c0000 \
-o junk.tmp \
version.coff action.o create.o distinct.o handle.o insert.o msi.o msiquery.o order.o
package.o record.o regsvr.o select.o string.o suminfo.o table.o tokenize.o update.o where.o
sql.tab.o cond.tab.o ../../dk/w32/lib/shell32.a ../../dk/w32/lib/cabinet.a
../../dk/w32/lib/oleaut32.a ../../dk/w32/lib/ole32.a ../../dk/w32/lib/version.a
../../dk/w32/lib/user32.a ../../dk/w32/lib/advapi32.a ../../dk/w32/lib/kernel32.a
../../dk/w32/lib/libwine.a ../../dk/w32/lib/wine_uuid.a ../../dk/w32/lib/ntdll.a
Warning: resolving _MsiGetFileVersionW by linking to _MsiGetFileVersionW@20
Use --enable-stdcall-fixup to disable these warnings
Use --disable-stdcall-fixup to disable these fixups
action.o(.text+0x879e):action.c: undefined reference to `LoadTypeLib@8'
action.o(.text+0x8830):action.c: undefined reference to `RegisterTypeLib@12'
action.o(.text+0x88c6):action.c: undefined reference to `ITypeLib_Release'
suminfo.o(.text+0x3e):suminfo.c: undefined reference to `IPropertyStorage_Release'
suminfo.o(.text+0x324):suminfo.c: undefined reference to `IPropertySetStorage_Open'
suminfo.o(.text+0x396):suminfo.c: undefined reference to `IPropertyStorage_AddRef'
suminfo.o(.text+0x3e9):suminfo.c: undefined reference to `IPropertyStorage_Release'
suminfo.o(.text+0x3fd):suminfo.c: undefined reference to `IPropertySetStorage_Release'
suminfo.o(.text+0x569):suminfo.c: undefined reference to `IPropertyStorage_ReadMultiple'
make: *** [msi.nostrip.dll] Error 1
Thanks,
James
chorns(a)cvs.reactos.com wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/tools/
>Changes by: chorns(a)mok.osexperts.com 04/10/28 12:02:01
>
>Log message:
> 2004-10-28 Casper S. Hornstrup <chorns(a)users.sourceforge.net>
>
> * drivers/net/tcpip/tests/setup.c: Include windows.h.
> * lib/gdiplus/tests/setup.c: Ditto.
> * lib/kernel32/tests/setup.c: Ditto.
> * lib/ws2_32/tests/setup.c: Ditto.
> * subsys/win32k/tests/setup.c: Ditto.
> * ntoskrnl/tests/setup.c: Ditto.
> * ntoskrnl/include/ntoskrnl.h: Include test.h.
> * ntoskrnl/mm/virtual.c (NtLockVirtualMemoryInternal): New function.
> (NtLockVirtualMemory): Use NtLockVirtualMemoryInternal.
>
>
Should we define a sort of "best practice" in inserting a little "p"
after the subsystem prefix and before the proper function's o
structure's name, to mark the *p*rivate symbols, or use the "Internal"
suffix?
1) NtpLockVirtualMemory (MmpLockVirtualMemory)
2) NtLockVirtualMemoryInternal
IMHO, not only an aesthetics problem.
Option (1) means that any symbol in ntoskrnl/include have a "p" or "P"
in their names.
> * ntoskrnl/tests/Makefile (TARGET_CFLAGS): Add -I../include.
> * ntoskrnl/tests/stubs.tst: Remove stubs for functions in libgcc.
> * regtests/shared/regtests.h: Make independent of windows.h.
> * tools/helper.mk (run): Link with libgcc.
> * tools/regtests.c (EXESTUB): Include windows.h.
> * ntoskrnl/include/internal/test.h: New file.
> * ntoskrnl/tests/tests/VirtualMemory.c: Ditto.
>
>
>
Emanuele
Hi!
I have a problem with my FPU state saving changes and v86 mode.
In ke/i386/v86m_sup.S are the functions which enter/leave v86 mode...
Ki386RetToV86Mode enters v86 mode. It changes CurrentThread->InitialStack and
TSS->Esp0 to %esp to make the exception handler run below the used stack and
not overwrite it.
The exception handler (KeV86GPF) uses a PKV86M_TRAP_FRAME, which contains a
KTRAP_FRAME at the beginning and some additional info behind. This additional
info is the data on the stack of Ki386RetToV86Mode, since it sets TSS->Esp0
to %esp, the CPU will push the trap-frame below when an exception is raised
and the additional info will be after the trap-frame.
The problem is that for reserving a FX_SAVE_AREA at the top of the
kernel-stack (without changing the KTHREAD->InitialStack value) i changed
tskswitch.S to set TSS->Esp0 to NewThread->InitialStack -
sizeof(FX_SAVE_AREA), not NewThread->InitialStack. Now if it's switching away
and back to a v86 task TSS->Esp0 will be sizeof(FX_SAVE_AREA) less than
before, and the V86 exception handler will be unable to find the additional
info from Ki386RetToV86Mode's original stack.
I am not sure how to solve it. I think it could be done by
1) Adding another variable somewhere (or maybe there is already one somewhere
which is meant to be used for this) for the exception-handler stack of the
thread, which can then be used by tskswitch.S to update TSS->Esp0.
2) only substract sizeof(FX_SAVE_AREA) from InitalStack for setting up
TSS->Esp0 in tskswitch.S if the VM bit of the EFLAGS is not set. Problem is
that the CPU unsets the VM bit if using protected-mode exception handlers for
v86 tasks, so we would need to get a copy (or pointer to) the eflags pushed
by the CPU for the IRQ handler into tskswitch.S (change
PsDispatchThread/PsDispatchThreadNoLock prototypes)
All this assumes that the FPU would never be used in V86 mode (and I hope that
this assumption is correct ;-))
Any suggestions are welcome.
- blight
Hello, I have searched for the error in the subject but can not find a solution. The daily snapshots (http://reactos.csh-consult.dk/) works fine. I have tried gcc 3.3.1, 3.4.1, 3.4.2. I use the binutils 2.15.91. Is there an error in my build tools?
EnricoB
The DDK says ExAllocatePool is obsolete. We sould use
ExAllocatePoolWithTag instead. The same applies to other generic pool APIs.
Here is a unofficial list of memory pool tags:
http://alter.org.ua/docs/win/pooltag/index.php
Emanuele
Hi,
now I have some spare time I'm back with gethostbyname and gethostbyaddr (I
don't know if they are still needed but according to my last update of my cvs
tree they are still unimplemented), I was not able to find the declaration of
PDNS_RECORDA. It would be nice to know where can I find it or at least how
can I operate with it. My research and guess makes me believe that I should
probably deal with DNS_STRUCT, but I think that would be better to have some
functionality to avoid messing with the whole structure. Am I totally lost
here?
bye
--
Carlos Manuel Duclos Vergara
carlos(a)embedded.cl
Sorry I could not translate. I was not online last weekend.
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] RE: LinuxWorld Germany
>Date: Sun, 24 Oct 2004 19:57:36 +0200
>
> > From: Freeworld
> >
> > Is the translation done? When has it to be ready?
> > If nobody else does it, I could help out.
>
>Yes, the translation is already done. Thanks to apollo11 for doing it and
>thanks to you for your offer.
>
>Gé van Geldorp.
>
>
>_______________________________________________
>Ros-dev mailing list
>Ros-dev(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-dev
_________________________________________________________________
Nicht lange suchen finden! MSN Suche. http://search.msn.de/ Jetzt testen!
I was recently updating my win32 QEMU installation when i noticed:
qemu-0.6.0-ppc.patch.gz
<http://www.h7.dion.ne.jp/%7Eqemu-win/download/qemu-0.6.0-ppc.patch.gz>
PReP support by F. Navara.
at the bottom. Can't go anywhere without seeing his name anymore ;)
Hehe, anyways, good job filip.
> You have to remember that our CVS is anonymous and there are many
> non-developers (much more then developers) who will be using it and have
> absolutely no interest in downloading tests, and they consider it seperate.
How will they validate what they compile? Will they trust the code and the
compilation process as is?
Emanuele
____________________________________________________________
Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione.
Abbonati subito su http://www.libero.it
> removed apps/tests). The advantage of the SVN tree will be that the
> /tests directory will have its own repository but still be included of a
> master repository/makefile for those who wish to have it all.
For when is the SVN switch planned?
Are there utilities to convert a local CVS codebase to a local SVN codebase, to
save a full checkout?
Emanuele
____________________________________________________________
Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione.
Abbonati subito su http://www.libero.it
Moin!
What do you think about a package system for reactos' files? We could
create seperate packages for, e.g. ntoskrnl, explorer,
drivers-networking, drivers-video, etc. pp., so it would be more easy
for users to upgrade. (ros-get update and ros-get upgrade or so)
I'd like to implement this, but I still have some open questions:
- What about overwriting files which are currently "in use"? Is it
possible to overwrite them w/o rebooting?
- We need a mechanism for postinst scripts, which update registry values
and so on. cmd.exe scripts are ugly, as VBScript is. bash on
windows/reactos is IMHO also not the best way. Maybe the package
installation system (the dpkg/rpm equivalent) could parse a special
script file with the syntax like NetInstall Script. What to you think?
Sebastian
--
signature intentionally left blank.
ion(a)cvs.reactos.com wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/w32api/include/reactos/wine/
>Changes by: ion(a)mok.osexperts.com 04/10/24 16:11:03
>
>Added files:
> reactos/w32api/include/reactos/: Tag: new_headers .cvsignore
> config.h debug.h defines.h
> epsapi.h heap.h helper.h
> resource.h roscfg.h string.h
> version.h
> reactos/w32api/include/reactos/wine/: Tag: new_headers cguid.h
> commctrl.h commdlg.h
> config.h cpl.h debug.h
><SNIP>
>
>Log message:
> Headers..
>
>_______________________________________________
>Ros-cvs mailing list
>Ros-cvs(a)reactos.com
>http://reactos.com/mailman/listinfo/ros-cvs
>
>
>
All right guys, I have no idea what just went on in CVS, but it somehow
got confused and started adding stuff to w32api even though I was
nowhere near that directory. So please disregard anything in my branch
that seems to have been commited in that directory, it's total nonsense.
I'll have to start over or something. I'm really getting annoyed with CVS.
Best regards,
Alex Ionescu
Hello,
if someone has an English version I could translate it to German. For a
English overview my English an ReactOS knowlege is to bad.
Theo
>From: Steven Edwards <steven_ed4153(a)yahoo.com>
>Reply-To: ReactOS Development List <ros-dev(a)reactos.com>
>To: ros-dev(a)reactos.com
>Subject: [ros-dev] LinuxWorld Germany
>Date: Thu, 21 Oct 2004 06:55:49 -0700 (PDT)
>
>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
>_______________________________________________
>Ros-dev mailing list
>Ros-dev(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-dev
_________________________________________________________________
MSN Hotmail. Anmelden und gewinnen! http://www.msn.de/email/webbased/ Ihre
Chance, eines von 10 T-Mobile MDA II zu gewinnen!
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
gcc -I./include -I../include -D__NTOSKRNL__ -Wall -Werror
-D_DISABLE_TIDENTS -
D_SEH_NO_NATIVE_NLG -D__3GB__ -I../include -I../w32api/include -pipe
-march=i486
-D_M_IX86 -D__NTOSKRNL__ -I. -D_SEH_NO_NATIVE_NLG -I../include
-I../w32api/incl
ude -pipe -march=i486 -D_M_IX86 -D__NTOSKRNL__ -I. -D_SEH_NO_NATIVE_NLG
-I../inc
lude -I../w32api/include -pipe -march=i486 -D_M_IX86 -c ke/i386/exp.c -o
ke/i386
/exp.o
ke/i386/exp.c: In function `KiTrapHandler':
ke/i386/exp.c:579: error: `ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY'
undeclared (fi
rst use in this function)
ke/i386/exp.c:579: error: (Each undeclared identifier is reported only once
ke/i386/exp.c:579: error: for each function it appears in.)
mingw32-make[1]: *** [ke/i386/exp.o] Error 1
mingw32-make[1]: Leaving directory `C:/reactos/ntoskrnl'
mingw32-make: *** [ntoskrnl] Error 2
C:\reactos>gcc --version
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.
I've tried my best to make a working implementaiton of
StackAttach/StackDetach, because it's almost one of the most important
APIs in NT5+ Drivers. I think I've got Detach working properly, but
Attach will require some changes to KeAttach itself so that it can save
the old ApcState & other things. I might get around to fixing it, but at
least the API should work now and allow more drivers to run sucesfully.
Also, if any Intel experts woudl like to check out KeFlushCurrentTb... I
followed the Intel Manual specs, just want to make sure I did it
properly...my GNU Assembler syntax sucks.
Best regards,
Alex Ionescu
ion(a)cvs.reactos.com wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/ntoskrnl/ke/
>Changes by: ion(a)mok.osexperts.com 04/10/12 18:42:15
>
>Modified files:
> reactos/include/ddk/: kefuncs.h
> reactos/ntoskrnl/: Makefile.i386
> reactos/ntoskrnl/include/internal/: ke.h ps.h
> reactos/ntoskrnl/ke/: apc.c device.c dpc.c kthread.c process.c
>
>Log message:
> Implemented KeAreApcsDisabled, KeFlushEntireTb, KeIsExecutingDpc, KeSetKernelStackSwapEnable, KeQueryPriorityThread, KeRevertToUserAffinityThread, KeSetIdealProcessorThread, KeSetSystemAffinityThread, KeTerminateThread, KeStackAttachProcess, KeUnstackDetachProcess
>
>_______________________________________________
>Ros-cvs mailing list
>Ros-cvs(a)reactos.com
>http://reactos.com/mailman/listinfo/ros-cvs
>
>
>
Hello,
For almost a week now my symbols have been missing. It started
with gdb not reading in any symbols when I was trying to hunt down
cygwin problems, then I re-enabled KDBG in config and rebuilt and KDBG
can tell you the function name, but not the file name and line number.
Last night, I deleted my sandbox and checked out a fresh copy from
CVS, only enabling DBG. I think it was Arty who suggested I check to
see if the targets are getting the "-g" flag. I captured the entire
build into a log, and these are the only targets that had "-g" on the
gcc command line:
ntdll (-g)
opengl32 (-g3)
dnsapi (-g)
bzip2 (-g)
oskittcp (-g)
patblt (-g)
primitives (-g)
strechblt (-g)
txtscale (-g)
wm_erasebkgnd (-g)
I checked this against my symbols directory and they correspond to
.sym files that appear to be valid. All the others are 16 bytes, and
don't appear to contain any useful information.
I'm not much of a make guru, so I thought I would report it rather
than continue to hunt it down alone. ;0)
Thanks,
Andrew
--
The cheese stands alone.
Hi!
Since I have seen mesa32 crash with SSE enabled I looked into fixing it
a bit...
When I was looking at ntoskrnl/ke/i386/tskswitch.S I found FIXMEs for
debug/FPU save/restore.
Now I am wondering where should this information be stored? I think it
should be part of the TSS (include/ntos/tss.h) but I am not sure.
For SSE support the SSE registers would also have to be saved/restored
on task switches and some other stuff which I do not yet know I think.
Maybe somebody can tell me where the FPU state should be stored so I can
try to implement it.
Thanks,
blight
Hi,
Anyone against switching ROS to be compiled by default on the 2GB
boundary? (This can always be locally changed by /3GB = 1)
For the sake of consistency and perhaps better driver support, as has
been found in the past.
Then we can start working on a real freeldr PE loader...
Best regards,
Alex Ionescu
Why is CVSspam output generated for only some of the ReactOS developers ?
Reading what was changed is very interesting for me
and CVSspam produces very nice diff.
Thanks, David
--
David Kredba <kredba at ibot.cas.cz>
GPG: ID 1024D/5B6B02DE
Fingerprint: F0B3312596BEDCF91DFB 0699E06AACD75B6B02DE
Hi James,
please update to the latest version, this has been fixed.
see
http://cvs.reactos.com/cgi-bin/cvsweb.cgi/reactos/subsys/system/winefile/it.
rc.diff?r1=1.2&r2=1.3
-----Message d'origine-----
De : James Tabor
[mailto:jimtabor@adsl-64-217-116-74.dsl.hstntx.swbell.net]
Envoyé : samedi 9 octobre 2004 03:17
À : ros-dev(a)reactos.com
Objet : [ros-dev] Re: [ros-cvs] CVS Update: reactos
mf(a)cvs.reactos.com wrote:
> CVSROOT: /CVS/ReactOS
> Module name: reactos
> Repository: reactos/subsys/system/winefile/
> Changes by: mf(a)mok.osexperts.com 04/10/08 13:20:15
>
> Modified files:
> reactos/subsys/system/winefile/: winefile.c winefile.h
>
> Log message:
> call vswprintf@msvcrt in Wine's UNICODE version
>
i386-mingw32-windres -D__USE_W32API -DNDEBUG -DWIN32 -D_ROS_ -D__WINDRES__
-DUNICODE --include-dir
../../../include --include-dir ../../../w32api/include winefile.rc -o
winefile.coff
i386-mingw32-windres: it.rc:184: parse error
make: *** [winefile.coff] Error 1
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev
----------------------------------------------------------------------------
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.
----------------------------------------------------------------------------
Richard and I can't get the ros cvs build to boot...I get stuck on a
black screen, and he gets a freeze on ndis.sys as well as a blackscreen
if running the bootcd.
Can anyone confirm?
Best regards,
Alex Ionescu
Hi arty,
Immediately after your answer on #reactos,
I did make clean in drivers/lib/ip and drivers/net/tcpip.
The problem is still here.
I even tried doing make clean in drivers/ to be sure.
Usurp.
"You believe its the year 2004,
when in fact it's closer to 1984."
Matrix / 1984.
-----Message d'origine-----
De : art yerkes [mailto:ayerkes@speakeasy.net]
Envoyé : vendredi 8 octobre 2004 03:50
À : ReactOS Development List
Cc : jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net
Objet : Re: [ros-dev] Re: [ros-cvs] CVS Update: reactos tcpip
On Fri, 08 Oct 2004 00:54:07 +0000
James Tabor <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net> wrote:
You need to make clean in drivers/lib/ip and drivers/net/tcpip. Hopefully
this will be the last time.
--
Hey, Adam Smith, keep your invisible hands to yourself!
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev
----------------------------------------------------------------------------
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.
----------------------------------------------------------------------------
Hello,
OpenOffice will load if you copy a working install from a Windows box
but we have some major problems in painting in the program. Is anyone
interested in looking at it?
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
Hello,
Arty and I played around a bit with the busybox dhcpd for Windows and I
was able to get it to run under Wine and give a address to my IP phone
and Art said that it should work under ReactOS once we implement
gethostbyname and gethostname. Does anyone want to take a stab at
implementing these? Art has said that a good deal of the functionality
is implemented in dnsapi.
Thanks
Steven
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
> From: Ge van Geldorp
>
> Log message:
> -Don't define COBJMACROS in objbase.h.
> Update the Wine sources accordingly.
I know this will cause warnings during shell32 compilation ("warning:
"COBJMACROS" redefined"), will fix this with the next Wine sync.
Gé van Geldorp.
<ion(a)cvs.reactos.com> wrote:
> CVSROOT: /CVS/ReactOS
> Module name: reactos
> Repository: reactos/ntoskrnl/mm/
> Changes by: ion(a)mok.osexperts.com 04/10/04 14:38:49
>
> Modified files:
> ./: config rules.mak
> reactos/include/ntdll/: rtl.h
> reactos/ntoskrnl/: Makefile
> reactos/ntoskrnl/include/internal/i386/: mm.h
> reactos/ntoskrnl/ke/i386/: multiboot.S
> reactos/ntoskrnl/mm/: mminit.c
>
> Log message:
> Un-hardcoded the 0xC0000000 value, and stuck the define in one single
> place both for ASM and C code. This define is 0x80000000 by default, but
> automatically sets itself to 0xC0000000 if 3GB is set to 1 in
> reactos/config. This option is turned on by default for now, because the
> Default heap is at 0xA0000000, which doesn't work on a non 3GB system.
> Lower values seem to crash Win32K but I fill figure out a solution.
I tried a NULL base address in the call to RtlCreateHeap (in
lib/ntdll/ldr/startup.c) and regedit (WIN32 app) works very well. The NULL
base address enables the default bottom-up memory allocation so the heap
will be allocated from the bootom of the process address space just like
Windows does. HEAP_BASE should have been removed ages ago.
Regards,
Eric
Is Sanos`s implementation of ndis and rtl8139 driver etc.
interesting for ReactOS developers ?
http://www.jbox.dk/sanos/index.htm
Regards, David
--
David Kredba <kredba at ibot.cas.cz>
GPG: ID 1024D/5B6B02DE
Fingerprint: F0B3312596BEDCF91DFB 0699E06AACD75B6B02DE
>From current CVS, running in whole-page alloc mode, I see a buffer
overrun in lib/rtl/acl.c early in the boot process. What I see is
a few calls to RtlpAddKnownAce which slowly overgrow the available
buffer. The following patch fixes it, but I don't know if it's
right as I'm not sure if AclSize should be adjusted. The reason
a patch like this is needed is that AclSize is checked against
the size of the Sid to be copied in, but that size never changes
so as many sids as desired could be copied in without the check
at line 136 going off, thus overrunning available space.
--
Hey, Adam Smith, keep your invisible hands to yourself!
Hi Hartmut,
Thanks for the commit, I wasn't sure how to fix those!
Best Regards,
Alex Ionescu
Hartmut Birr wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/ntoskrnl/ke/i386/
>Changes by: hbirr(a)mok.osexperts.com 04/10/05 11:53:28
>
>Modified files:
> reactos/ntoskrnl/mm/i386/: page.c
> reactos/ntoskrnl/ke/i386/: multiboot.S
>
>Log message:
> - Removed some hard coded values, which depend on a kernel base of 0xc0000000.
>
>_______________________________________________
>Ros-cvs mailing list
>Ros-cvs(a)reactos.com
>http://reactos.com/mailman/listinfo/ros-cvs
>
>
>
Hi,
I just want to make a few annotations to the new dhcpd.
Why do we have to add these useless files, like shell scripts, makefile.am,
makefile.in, etc. to the CVS tree if we want to make dhcpd a real service?
The source code will loose its portability anyway. And why keep this rather
complex directory structure for such a simple utility?
Btw, the dhcp server looks like a hack to me. It is leaking lots of memory
because there is not a single call to free() in the source and the dhcp
options handling it pretty crude. And it doesn't seem to work with a Win2K
client.
I'd suggest to use the Moreton dhcp server (dhcp-win-0.8.25.tar) instead. It
has got a much better internal structure and it works properly. I ran it on
Win98SE and tested it with a Win2K client. The only disadvantage of the
Moreton server is that it uses a binary config file.
Regards,
Eric
Hi,
why is the drive letter added to users path if the install drive isn't C?
CreateDirectory("G:\Documents and
Settings\Administrator.REACTOS_G\Application Data\Microsoft")
CreateDirectory("G:\Documents and
Settings\Administrator.REACTOS_G\Application Data\Microsoft\Internet
Explorer")
CreateDirectory("G:\Documents and
Settings\Administrator.REACTOS_G\Application Data\Microsoft\Internet
Explorer\Quick Launch")
- Hartmut
In regards to the earlier change, this is why i made it ;)
The broodwar installer works, along with d2, and the d2 expansion.
Starcraft's installer fails with an odd error mentioning an invalid
window handle.
Hi,
I really doubt it will matter but it seems the newer mingw-gcc is
bombing in quite a few places when building ReactOS. This patch allows
it to mostly build for me.
Thanks
Steven
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
Okay guys, The tree is NOT compiling.
Latest errors i'm getting are
C:/reactos/drivers/net/tcpip/tcpip/fileobjs.c:74: undefined reference to
`A2S'
tcpip/fileobjs.o(.text+0x14c):C:/reactos/drivers/net/tcpip/tcpip/fileobjs.c:74:
undefined reference to `A2S'
tcpip/fileobjs.o(.text+0x1340): In function `FileOpenAddress':
C:/reactos/drivers/net/tcpip/tcpip/fileobjs.c:377: undefined reference
to `A2S'
datalink/lan.o(.text+0x1598): In function `BindAdapter':
C:/reactos/drivers/net/tcpip/datalink/lan.c:714: undefined reference to
`A2S'
datalink/lan.o(.text+0x15f4):C:/reactos/drivers/net/tcpip/datalink/lan.c:719:
un
defined reference to `A2S'
collect2: ld returned 1 exit status
mingw32-make[2]: *** [tcpip.nostrip.sys] Error 1
mingw32-make[2]: Leaving directory `C:/reactos/drivers/net/tcpip'
mingw32-make[1]: *** [preall] Error 2
mingw32-make[1]: Leaving directory `C:/reactos/drivers/net/tcpip'
mingw32-make: *** [tcpip] Error 2
C:\reactos>
GCC 3.4.1
G++ 3.4.1
Bin Utils 2.15.90 20040222
Hi,
this patch (or some areas in ntoskrnl) isn't correct. This patch puts always
64kB between the TEB's. This limits the number of threads to 30,000 or less.
I've found this by an other bug in kernel32.
- Hartmut
> -----Original Message-----
> From: ros-cvs-bounces(a)reactos.com
> [mailto:ros-cvs-bounces@reactos.com] On Behalf Of Ge van Geldorp
> Sent: Tuesday, September 28, 2004 12:49 PM
> To: ros-cvs(a)reactos.com
> Subject: [ros-cvs] CVS Update: reactos
>
>
> CVSROOT: /CVS/ReactOS
> Module name: reactos
> Repository: reactos/ntoskrnl/ps/
> Changes by: gvg(a)mok.osexperts.com 04/09/28 12:49:21
>
> Modified files:
> reactos/ntoskrnl/ex/: sysinfo.c
> reactos/ntoskrnl/include/internal/: mm.h
> reactos/ntoskrnl/mm/: anonmem.c marea.c
> reactos/ntoskrnl/ps/: process.c
>
> Log message:
> NtAllocateVirtualMemory() should return 64k aligned areas
>
> _______________________________________________
> Ros-cvs mailing list
> Ros-cvs(a)reactos.com
> http://reactos.com/mailman/listinfo/ros-cvs
>
Hi,
it exist a variable TARGET_CPPAPP. If this variable is set to yes, the
object files for the real target are linked directly. If the variable is not
set, the object files are prelinked to a single object file with the option
'--strip-debug'. User mode images are always linked with the option
'--strip-debug'. TARGET_CPPAPP has no effect. Kernel mode images are not
linked with '--strip-debug'. They contains a large debug section if either
TARGET_CPPAPP is set to yes or if they are linked to a library which
contains debug symbols. Currently, Ntoskrnl contains a large debug section.
I'm able to boot ros from a harddisk but I'm not able to install ros from a
cd. The pc reboots after loading the boot files from the cd. In bochs I see
a short debug message:
Page fault at high IRQL was 31
KeBugCheckWithTf at ke/catch.c:164
Something is different between freeldr and setupldr. This occurs since
ntoskrnl uses helper.mk. If I build ntoskrnl with the option
'--strip-debug', there exist no problem.
- Hartmut
When doing kernel development, it is common to develop with the MS kernel
debugger running live on machine a (with the driver in question running)
and then connecting to it remotly from machine b.
Does ReactOS run the remote part of the kernel debugger yet? (i.e. can it
act as the "machine b" in the equasion?)
What is going on here.....
This is a new mingw enviroment from sourceforge and a new source tree.
getopt.c: In function `_getopt_initialize':
getopt.c:401: warning: implicit declaration of function `getenv'
getopt.c:401: warning: assignment makes pointer from integer without a
cast
getopt.c: In function `_getopt_internal':
getopt.c:577: warning: implicit declaration of function `strcmp'
getopt.c:653: warning: implicit declaration of function `strncmp'
getopt.c:656: warning: implicit declaration of function `strlen'
mingw32-make[2]: *** [getopt.o] Error 1
mingw32-make[1]: *** [wmc_target] Error 2
mingw32-make: *** [tools] Error 2
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
/The EFF reported <http://eff.org/news/archives/2004_09.php#001962>
that the Vivendi/Blizzard vs. the good guys case has been decided, and
it doesn't look good. Some highlights from the ruling
<http://www.freedom-to-tinker.com/doc/2004/bnetd_30sep.pdf> are: A
clickthrough EULA isn't unconscionable (and thus enforceable); Fair Use
rights can be waived in a EULA; First Sale rights (!) can be waived in a
EULA; The DMCA's interoperability provisions are not a defense. If this
ruling is allowed to stand, it will allow one-sided EULAs to force the
waiver of the rights of First Sale and Fair Use.
Sigh.
Best regards,
Alex Ionescu
/
I apologized, i was going to fix the issues, but my computer monitor
died. I just got a new one late last night and had to work all day today.
ekohl(a)cvs.reactos.com wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/bootdata/
>Changes by: ekohl(a)mok.osexperts.com 04/10/02 05:35:12
>
>Modified files:
> reactos/bootdata/: hivesft.inf
>
>Log message:
> Add common user shell folder key.
>
>_______________________________________________
>Ros-cvs mailing list
>Ros-cvs(a)reactos.com
>http://reactos.com/mailman/listinfo/ros-cvs
>
>
>
Hey all, Phonica here.
A little tool I knocked up - Takes an INF file as a param (If none is given
a common open box shows up) and passes it to setupapi.dll to be installed.
Usefull for installing device drivers etc.
Tool + Source Can be found on bugzilla bug 428
http://www.reactos.com/bugzilla/show_bug.cgi?id=428
Writen in VC60 C++ (no MFC)
Hope y'all like it :)
What are you kidding??? Please change this back as it makes ReactOS
worse than before. Now your ReactOS installation will conflict with
an existing Windows or ReactOS installation. This is IMHO way worse
than not supporting two broken applications.
Casper
> -----Original Message-----
> From: ros-cvs-bounces(a)reactos.com
> [mailto:ros-cvs-bounces@reactos.com] On Behalf Of Richard Campbell
> Sent: 30. september 2004 08:40
> To: ros-cvs(a)reactos.com
> Subject: [ros-cvs] CVS Update: reactos
>
> CVSROOT: /CVS/ReactOS
> Module name: reactos
> Repository: reactos/bootdata/
> Changes by: rcampbell(a)mok.osexperts.com 04/09/30 08:39:49
>
> Modified files:
> reactos/bootdata/: hivedef.inf hivesft.inf
>
> Log message:
> - For now, hardcode the all users profile path until we
> get better user management code in place
> - removed the %USERPROFILE% prefix, this will go in
> combination with my other fix to hopefully get things working
> right again.
Hello,
Recently I've been trying to figure out why I am unable to load
ReactOS. I am being stopped each time when ReactOS attempts to load
the miniport driver. I believe the problem is that DISPLAY1 is not
being expanded/pointed to some real file. I assume somewhere in the boot
process that \??\DISPLAY1 is supposed to link to somewhere. I am using CVS
(synced from 09/29/2004) and am wondering if any of you guys can take a
look at the debug log and tell me what i'm missing.
The debug log [around 80k] is here:
http://home.pe.net/~dsmith/ros/093005
I have also posted my hive files if they are relevant:
http://home.pe.net/~dsmith/ros/hivecls.infhttp://home.pe.net/~dsmith/ros/hivedef.infhttp://home.pe.net/~dsmith/ros/hiveinst.infhttp://home.pe.net/~dsmith/ros/hivesft.infhttp://home.pe.net/~dsmith/ros/hivesys.inf
I am open to trying any patches or enabling debugging on any additional
files to help out. Currently, the following modules are enabled for
debugging support:
ntoskrnl\ke\main.c
ntoskrnl\io\create.c
ntoskrnl\ldr\init.c
subsys\csrss\init.c
subsys\win32k\ldr\loader.c
subsys\win32k\objects\dc.c
I have tried copying the file vbemp.sys to E:\DISPLAY1 but I got the same
debug log. If you have any questions feel free to ask.
Thanks in advance,
Devin Smith
I am currently planning on fixing our User Management code. Before i do
i'd like some advice.
First, We need to decide on some folder names for User Profiles. I'd
recommend a "ReactOS Users" folder or equivalent. This doesn't
interfere with Windows nor older versions of ReactOS.
Second, I'm beginning to understand enough about MSGINA/WinLogon/and the
log on process in general that i could probably implement a basic form
of user authentication. However, this will mean that ROS will end up
asking for a username/password every time it boots...shall i implement
this now and maybe add an #if 0 to skip over it? Or shall we use some
sort of auto login functionality. (like windows, but the implementation
won't be the same, i'm unsure about how windows accomplishes it)
Eric Khol has done a good job with alot of the security related stuff,
but there is soooo much more to be added, and alot to be changed. (As
previously mentioned here and discussed on IRC, Windows does NOT USE
environment variables in the registry. The stuff is hardcoded, registry
is set up the first time the user logs on.)
How about
"Now I am satisfied. Thank God, I have done my duty"
-----Original Message-----
From: royce(a)cvs.reactos.com [mailto:royce@cvs.reactos.com]
Sent: 30 September 2004 07:45
To: ros-cvs(a)reactos.com
Subject: [ros-cvs] CVS Update: reactos
CVSROOT: /CVS/ReactOS
Module name: reactos
Repository: reactos/ntoskrnl/ex/
Changes by: royce(a)mok.osexperts.com 04/09/30 06:44:49
Modified files:
reactos/ntoskrnl/ex/: power.c
Log message:
You're such a trooper, Marvin
_______________________________________________
Ros-cvs mailing list
Ros-cvs(a)reactos.com
http://reactos.com/mailman/listinfo/ros-cvs
Hi everyone,
Great news, it seems that Microsoft's patent on FAT has been rejected. This
means that our LFN conversion is safe from any licensing issues, and any
other patents we might've had the possiblity to infringe.
Best regards,
Alex Ionescu
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .
GvG
This change breaks explorer.
Ge van Geldorp wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/lib/shell32/
>Changes by: gvg(a)mok.osexperts.com 04/09/29 00:01:38
>
>Modified files:
> reactos/lib/shell32/: folders.c shfldr.h shlfolder.c
>
>Log message:
> Robert Shearman <rob(a)codeweavers.com>
> - Simplify getting custom icons for a folder by utilising the new
> SHELL32_GetCustomFolderAttribute function.
> - Add support for custom shell folders, such as the History folder.
> - Always try to initialize folder using IPersistFolder3 interface and
> then fall back on IPersistFolder if not supported.
>
>_______________________________________________
>Ros-cvs mailing list
>Ros-cvs(a)reactos.com
>http://reactos.com/mailman/listinfo/ros-cvs
>
>
>
Well, As Royce pointed out to me yesterday, it appears that the user
profile is created the first time the user logs on...and the registry
entries are set up. My question is how should this be handled in ROS?
In WINLOGON? Does anyone have any documentation on the windows logon
procedure available?
Richard
Hi,
This is especially in regard to Steven, since he mentionned it might be
a WINE bug. I had mentionned that the Edit Box cursor/text isn't always
centered...and I finally managed to get a good picture, attached below.
I agree this is a trivial bug but I'm just posting it for all to see and
so that Steven can possibly put it on WINE's bug list (if it's indeed a
WINE bug)
Best regards,
Alex Ionescu
"Richard Campbell" <rcampbell(a)cvs.reactos.com> wrote:
> CVSROOT: /CVS/ReactOS
> Module name: reactos
> Repository: reactos/bootdata/
> Changes by: rcampbell(a)mok.osexperts.com 04/09/28 18:26:36
>
> Modified files:
> reactos/bootdata/: hivedef.inf hivesft.inf
>
> Log message:
> - Changed a few REG_EXPAND_SZ to REG_SZs as per Windows
Please revert that change! These values _must_ be expandable in ReactOS to
work properly, no matter which type is used by Windows.
Regards,
Eric
Hi,
i386-mingw32-gcc -I./include -D__NTOSKRNL__ -g -Wall -Werror -D_DISABLE_TIDENTS
-D_SEH_NO_NATIVE_NLG -I../include -I../w32api/include -pipe -march=i486 -D_M_IX86 -c mm/section.c -o
mm/section.o
mm/section.c: In function `MmMapViewOfSection':
mm/section.c:3812: error: too few arguments to function `MmFindGap'
make: *** [mm/section.o] Error 1
Need to make clean and recompile ntoskrnl.
Thanks,
James
> From: Hartmut Birr
>
> Log message:
> - Rewrote (copied from ntdll) parts of the relocation
> and import fixup code.
> - Don't load no-load sections at the end of the driver.
> - Don't relocate the relocation section itself.
> - Set the correct page protection for section which are
> executable.
With current CVS, the VMware SVGA driver crashes. It happens in a
HwFindAdapter() call. While tracing through the driver, I got this eery
"I've been here before" feeling. And sure enough, I fixed this same crash
about a year and a half ago.
The problem is that vmx_svga.sys has a section alignment of 0x20 instead of
the normal 0x1000. So, sections are much smaller than the page size. When
setting the page protections you need to take into account all the sections
which might be mapped to that page. This was implemented in
ntoskrnl/ldr/loader.c rev 1.126.
Gé van Geldorp.
I started putting in ASSERT_IRQL in ntoskrnl, hoping that only my own code
would break from it. The results are ... interesting.
I've put a metabug (426) on bugzilla which is about reactos not honoring
documented irql requirements. I fixed a place in win32k.sys, but there
are probably more. I think we should clean these up and get the
assert_irqls into HEAD, so that people like me won't get bitten over and
over by assuming we're in one irql when we're in another.
Unrelated, please take a look at the following patch, anyone who's cozy
with the mm. The reason why this code is needed is that MmNotPresentFault
and MmAccessFault will try to lock the address space as well as
MmProbeAndLockPages. Since this is a spin lock, reactos will always
bugcheck when MmProbeAndLockPages faults in a page, even if that would
be legal otherwise. I'm not sure if this patch fixes it right but it does
seem to work this way. If i don't hear too many complaints i'll think
about committing something similar.
There are a couple of other places where MmNotPresentFault is called
(section.c) within a MmLockAddressSpace. Another idea would be to give
MmNotPresentFault and MmAccessFault an extra argument so they can ignore
locking if the address space is already locked.
--
Hey, Adam Smith, keep your invisible hands to yourself!
Hello!
I thought I would try running Cygwin on a ReactOS CVS build, and
after talking with some of you on IRC, I went ahead.
After setting PATH=c:\cygwin\bin;%PATH%, dd.exe, uniq.exe,
bash.exe, and ls.exe all drop ros to the kernel debugger with an
exception 14. This is on the now dead Command Prompt:
41 [Main] ? 10 cygheap_user::init: SetTokenInformation
(TokenDefaultDacl): Win32 error 1
Here is the debug output leading up to the exection of uniq.exe:
(objects/gdiobj.c:401) Can't delete hObj:0x00042d77, type:0x007f0000, flag:0
(objects/gdiobj.c:401) Can't delete hObj:0x00042f72, type:0x007f0000, flag:0
(ntuser/desktop.c:808) RtlQueryRegistryValues failed for
PaintDesktopVersion: status=c0000005
(NTDLL:ldr/utils.c:2060) Relocating (10000000 -> 631000)
C:\cygwin\bin\cygiconv-2.dll
(NTDLL:ldr/utils.c:2060) Relocating (77f00000 -> 941000)
C:\ReactOS\system32\KERNEL32.dll
(NTDLL:ldr/utils.c:2060) Relocating (77dc0000 -> 9ba000)
C:\ReactO(NTDLL:ldr/utils.c:2060) Relocating (61000000 -> 9d0000)
C:\cygwin\bin\cygwin1.dll
S\system32\advapi32.dll
(sec/misc.c:489) GetUserNameA: stub
Entered debugger on exception number 14.
Entered kernel debugger (type "help" for a list of commands)
kdb:> bt
Frames: <ntoskrnl.exe: e326c (ob/security.c:311 (NtSetSecurityObject))>
<ntoskrnl.exe: 3e5b (:148 (KeUserModeCallback))>
<ntdll.dll: 3379 (napi.c:404 (NtSetSecurityObject))>
All of the above commands result in the "GetUserNameA: stub" error and
the message on the command prompt.
Andy
--
The cheese stands alone.
(io/arcname.c:375) Booting from CD-ROM!
(io/arcname.c:319) Could not find ntoskrnl.exe
IoCreateSystemRootLink FAILED: (0xc0000001) - %KERNEL-WRN-UNSUCCESSFUL
UNSUCCESSFUL
KeBugCheck at ke/main.c:687
Bug detected (code 7b param 0 0 0 0)
INACCESSIBLE_BOOT_DEVICE
Frames: <ntoskrnl.exe: a859> <ntoskrnl.exe: a879> <C0082E12>
<ntoskrnl.exe: c0a9> <C0083681> <ntoskrnl.exe: 115c>
this is using the livecd, haven't figured out how to mod the bootcd to
display that output.
Hi,
can you disable line #32 (#define NDEBUG)in ntoskrnl\io\arcname.c and try it
again?
- Hartmut
> -----Original Message-----
> From: ros-kernel-bounces(a)reactos.com
> [mailto:ros-kernel-bounces@reactos.com] On Behalf Of Richard Campbell
> Sent: Tuesday, September 28, 2004 7:34 PM
> To: ros-kernel(a)reactos.com
> Subject: [ros-kernel] BootCD doesn't boot...
>
>
> Hello all
>
> I'm using a fresh CVS checkout and ROS fails to boot in
> either VMWare or
> QEMU via the iso built by mingw32-make bootcd.
>
> Attached is a screen.
>
Hi!
I e-mailed Brian Palmer, he said it comes down to what I want to do (I asked
him if I could help with ReactOS.
Anything need done?
my email address is either pattersonmpt(a)aol.com or xtreme101(a)btinternet.com
Darren,
Hello,
The Wine guys are interested in our implementation of userenv.dll. I
know you guys dont normally care about releasing the libs as LGPL but I
want to check with the four of you before I change the license
header(s) and merge attempt to get a patch ready for Winehq. Is this
cool with the four of you?
Thanks
Steven
__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo
Hello,
I have been trying to test Firefox and OpenOffice under ReactOS and it
seems to be having trouble looking up mangled names in msvcrt. Firefox
fails like this
(NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find
??3@YAXPAX@Z
and OpenOffice fails to find this name ??1type_info@@UAE@XZ
Both of them are implemented and point to code I imported from Wine a
long time ago. Anyone have any idea whats up?
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail
Attached is a test program that demonstrates a problem with memory mapped
files. Basically, if you try to MapViewOfFile() a part of the file at
non-zero file offset, ReactOS will still map the beginning of the file.
I think I found the cause of this, the attached .diff fixes it. My fix
uncovered another (small) problem, ViewOffset is relative to the start of
the segment, not the start of the section. So instead of passing
SectionSegments[i].VirtualAddress we need to pass 0.
I'd appreciate it if someone who actually understands the Mm stuff can take
a look at this.
Gé van Geldorp.
99% of the windows users consider networking as
browsing internet. Give suport for TCP/IP , for a
basic browser (wish it were graphical, and most common
ethernet cards (kind of realtek or others widely used)
and you can say. ¡We have networking!.
An extra would be suport for some widely used modems.
Noone expect apache or emule working in an alpha OS,
even FTP is prescindible in 0.3.
Regards,
Lucio Diaz.
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
Hi all
Ros-dev is now functional. Please refrain from posting to ros-kernel
and use this new list instead - I've moved all subscriptions over to
this list. Ros-kernel will be discontinued in a few days.
Cheers
Jason