- Ros-dev - ReactOS.org

Please add pcnet.sys to the bootcd.
by WaxDragon 24 Nov '04

24 Nov '04

I noticed yesterday while installing ros from a locally generated bootcd that pcnet.sys is not included. Could someone add it to reactos.dff? Thanks! Andrew -- The cheese stands alone.

2 1

ReactOS and Viruses
by Rick Langschultz 24 Nov '04

24 Nov '04

Sun will be releasing Solaris 10 shortly as a commercial product available for purchase. There is a new file system that is 128-bit, and is protected by md5 checksums, I think this is a great idea for reactos. I think before a program executes there should be a binary verifier that checks this checksum and then allows the program to run. This would help in deterring Windows viruses from attaching themselves to reactos binaries. Since ReactOS is open source it will be harder to protect a binary if there is an attack and a malicious user replaces a dll or an exe. Perhaps this can be done using a small xml file or a txt file called md5sums or something. Please let me know what you think.

5 6

Idea to protect ReactOS
by Jeff Smith 24 Nov '04

24 Nov '04

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.

12 16

Windows NT architecture
by Maritn "E.T." Misuth 24 Nov '04

24 Nov '04

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?

4 3

Ekush.com up again
by Ibrahim Damlaj 23 Nov '04

23 Nov '04

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. "

7 8

[Fwd: [ros-cvs] CVS Update: reactos] BUG 446 Fixed - NIC Realtek8139
by Gge 23 Nov '04

23 Nov '04

The bug 446 is fixec and can be closed following this commit The nic driver Realtek8139 loads and start successfully Regards Gerard

1 0

core reorg. request
by Gunnar Dalsnes 23 Nov '04

23 Nov '04

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

4 4

Is ROS-CVS ever going to work?
by Richard Campbell 22 Nov '04

22 Nov '04

Is the ROS cvs list ever going to be functional again? Richard

1 0

RE: [ros-diffs] [CVS reactos] fix kernel queues + misc fixes/cleanups
by Casper Hornstrup 21 Nov '04

21 Nov '04

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

1 0

headers suggestion
by Jonathan Wilson 21 Nov '04

21 Nov '04

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.

4 12

File format and message box icons
by Klemens Friedl 21 Nov '04

21 Nov '04

Hi! I created 13 file format icons (bmp, dll, gif, jpg, mid, mp3, png, psd, rtf, tif, txt, unknown, wav) and 5 message box icons. I hope the icons are useful for ReactOS! License: GNU LESSER GENERAL PUBLIC LICENSE File Format Icons: -> http://reactosde.re.funpic.de/mediadetail.php?sec=Graphic arts&cat=icons&mdnr=58 or -> http://reactos.com/bugzilla/show_bug.cgi?id=449 Message Box Icons: -> http://reactosde.re.funpic.de/mediadetail.php?sec=Graphic arts&cat=icons&mdnr=57 or -> http://reactos.com/bugzilla/show_bug.cgi?id=448 I also built a ReactOS compatibility database (for applications and device drivers) and media files for ROS. Klemens Friedl -- NEU +++ DSL Komplett von GMX +++ http://www.gmx.net/de/go/dsl GMX DSL-Netzanschluss + Tarif zum superg�nstigen Komplett-Preis!

2 2

booting ros is broken (was: fix broken work item impl.)
by Hartmut Birr 21 Nov '04

21 Nov '04

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

4 4

KQUEUE race condition
by Filip Navara 21 Nov '04

21 Nov '04

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; + } + } }

3 3

Keyboard layout DLLs
by Casper Hornstrup 20 Nov '04

20 Nov '04

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

4 3

A call for help getting putty working
by art yerkes 20 Nov '04

20 Nov '04

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

4 7

headers in reactos/w32api/include and reactos/include/wine
by Steven Edwards 20 Nov '04

20 Nov '04

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

7 10

Request for use of Logo on items at CafePress
by Wierd Wierd 19 Nov '04

19 Nov '04

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

5 4

RE: [ros-dev] question about some old changes (hartmut)
by Hartmut Birr 19 Nov '04

19 Nov '04

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

2 2

fix for regedit
by Christian Koinig 19 Nov '04

19 Nov '04

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); ------------------------------------------------------

5 4

Greenville: The story of Freetype VS the windows rasterizer---
by Wierd Wierd 19 Nov '04

19 Nov '04

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

4 3

RE: [ros-dev] ReactOS Versions
by Waldo Alvarez Cañizares 18 Nov '04

18 Nov '04

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.

2 1

"no current process" problem
by Gunnar Dalsnes 18 Nov '04

18 Nov '04

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

1 0

Hmm, another petition:
by Lucio Diaz 18 Nov '04

18 Nov '04

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

6 5

Loading ReactOS from Floopy
by Lucio Diaz 18 Nov '04

18 Nov '04

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

5 7

NDIS suggestion
by eric.kohl＠t-online.de 18 Nov '04

18 Nov '04

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

2 2

Important software
by Casper Hornstrup 18 Nov '04

18 Nov '04

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

5 4

question about some old changes (hartmut)
by Gunnar Dalsnes 18 Nov '04

18 Nov '04

Hi. What was the reason for these changes? It looks like a workaround for some other bug. http://cvs.reactos.com/cgi-bin/cvsweb.cgi/reactos/ntoskrnl/ke/wait.c.diff?r1 =1.51 <http://cvs.reactos.com/cgi-bin/cvsweb.cgi/reactos/ntoskrnl/ke/wait.c.diff?r 1=1.51&r2=1.52> &r2=1.52 Gunnar

1 0

What is difference in installation procedure w/wo DGG, KDBG set ?
by David Kredba 17 Nov '04

17 Nov '04

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

4 8

Support of NIC Realtek 8139
by Gge 17 Nov '04

17 Nov '04

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

4 7

AFD_IMMEDIATE' undeclared
by David Kredba 17 Nov '04

17 Nov '04

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

3 3

RE: [ros-diffs] [CVS reactos] fix broken work item impl.
by Hartmut Birr 17 Nov '04

17 Nov '04

Hi Gunnar, for synchronisation between an unlimited count of objects (or 256) in a wait queue and more than one waiters which removes this objects, there _must_ be used a semaphore (or equivalent code). Please revert your changes. - Hartmut -----Original Message----- From: ros-diffs-bounces(a)reactos.com [mailto:ros-diffs-bounces@reactos.com] On Behalf Of gdalsnes(a)osexperts.com Sent: Tuesday, November 16, 2004 12:15 AM To: ros-diffs(a)reactos.com Subject: [ros-diffs] [CVS reactos] fix broken work item impl. Commit in reactos/ntoskrnl/ex on MAIN work.c <> +16 -18 1.20 <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ex/work.c?rev=1.20&c ontent-type=text/x-cvsweb-markup> - <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ex/work.c.diff?r1=te xt&tr1=1.20&r2=text&tr2=1.21&f=h> > 1.21 <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ex/work.c?rev=1.21&c ontent-type=text/x-cvsweb-markup> fix broken work item impl. _____ reactos <http://cvs.reactos.com/cgi-bin/cvsweb/reactos> /ntoskrnl <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl> /ex <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ex> work.c 1.20 <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ex/work.c?rev=1.20&c ontent-type=text/x-cvsweb-markup> - <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ex/work.c.diff?r1=te xt&tr1=1.20&r2=text&tr2=1.21&f=h> > 1.21 <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ex/work.c?rev=1.21&c ontent-type=text/x-cvsweb-markup> diff -u -r1.20 -r1.21 --- work.c 22 Oct 2004 20:18:37 -0000 1.20 +++ work.c 15 Nov 2004 23:14:36 -0000 1.21 @@ -1,4 +1,4 @@ -/* $Id: work.c,v 1.20 2004/10/22 20:18:37 ekohl Exp $ +/* $Id: work.c,v 1.21 2004/11/15 23:14:36 gdalsnes Exp $ * * COPYRIGHT: See COPYING in the top level directory * PROJECT: ReactOS kernel @@ -36,7 +36,7 @@ /* * PURPOSE: Worker threads with nothing to do wait on this event */ - KSEMAPHORE Sem; + KEVENT Event; /* * PURPOSE: Thread associated with work queue @@ -84,7 +84,7 @@ } else { - KeWaitForSingleObject((PVOID)&queue->Sem, + KeWaitForSingleObject((PVOID)&queue->Event, Executive, KernelMode, FALSE, @@ -102,9 +102,10 @@ InitializeListHead(&WorkQueue->Head); KeInitializeSpinLock(&WorkQueue->Lock); - KeInitializeSemaphore(&WorkQueue->Sem, - 0, - 256); + KeInitializeEvent(&WorkQueue->Event, + SynchronizationEvent, + FALSE); + for (i=0; i<NUMBER_OF_WORKER_THREADS; i++) { PsCreateSystemThread(&WorkQueue->Thread[i], @@ -164,30 +165,27 @@ ExInterlockedInsertTailList(&EiNormalWorkQueue.Head, &WorkItem->List, &EiNormalWorkQueue.Lock); - KeReleaseSemaphore(&EiNormalWorkQueue.Sem, - IO_NO_INCREMENT, - 1, - FALSE); + KeSetEvent(&EiNormalWorkQueue.Event, + IO_NO_INCREMENT, + FALSE); break; case CriticalWorkQueue: ExInterlockedInsertTailList(&EiCriticalWorkQueue.Head, &WorkItem->List, &EiCriticalWorkQueue.Lock); - KeReleaseSemaphore(&EiCriticalWorkQueue.Sem, - IO_NO_INCREMENT, - 1, - FALSE); + KeSetEvent(&EiCriticalWorkQueue.Event, + IO_NO_INCREMENT, + FALSE); break; case HyperCriticalWorkQueue: ExInterlockedInsertTailList(&EiHyperCriticalWorkQueue.Head, &WorkItem->List, &EiHyperCriticalWorkQueue.Lock); - KeReleaseSemaphore(&EiHyperCriticalWorkQueue.Sem, - IO_NO_INCREMENT, - 1, - FALSE); + KeSetEvent(&EiHyperCriticalWorkQueue.Event, + IO_NO_INCREMENT, + FALSE); break; #ifdef __USE_W32API email" href="http://www.badgers-in-foil.co.uk/projects/cvsspam/">CVSspam 0.2.8

4 5

ReactOS eating CPU time
by Casper Hornstrup 16 Nov '04

16 Nov '04

In VMware, ReactOS eats up all available CPU time. Does anyone have an idea why? Does it also do this on real hardware? Casper

10 14

CVS Logs?
by Filip Navara 15 Nov '04

15 Nov '04

Can someone please send a change log of CVS since 03/11/2004 (eg. generated using cvs2cl)? Thanks, Filip

2 1

RE: [ros-diffs] [CVS reactos] Fix handling of debug traps in GDB stub/KiDispatchException.
by Hartmut Birr 14 Nov '04

14 Nov '04

Hi, this changes breaks the handling of exceptions if KDB isn't set. In KiDispatchException the variable Action is preinitialized with kdContinue. After your changes, KiDispatchException does always return without any action. After this changes, I'm not able to install reactos. At the second stage setup I do never see the reboot page. - Hartmut -----Original Message----- From: ros-diffs-bounces(a)reactos.com [mailto:ros-diffs-bounces@reactos.com] On Behalf Of Gregor Anich Sent: Sunday, November 14, 2004 12:00 AM To: ros-diffs(a)reactos.com Subject: [ros-diffs] [CVS reactos] Fix handling of debug traps in GDB stub/KiDispatchException. _____ reactos <http://cvs.reactos.com/cgi-bin/cvsweb/reactos> /ntoskrnl <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl> /ke <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ke> catch.c 1.51 <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ke/catch.c?rev=1.51& content-type=text/x-cvsweb-markup> - <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ke/catch.c.diff?r1=t ext&tr1=1.51&r2=text&tr2=1.52&f=h> > 1.52 <http://cvs.reactos.com/cgi-bin/cvsweb/reactos/ntoskrnl/ke/catch.c?rev=1.52& content-type=text/x-cvsweb-markup> diff -u -r1.51 -r1.52 --- catch.c 11 Nov 2004 12:27:40 -0000 1.51 +++ catch.c 13 Nov 2004 23:00:15 -0000 1.52 @@ -16,7 +16,7 @@ * along with this program; if not, write to the Free Software * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. */ -/* $Id: catch.c,v 1.51 2004/11/11 12:27:40 ekohl Exp $ +/* $Id: catch.c,v 1.52 2004/11/13 23:00:15 blight Exp $ * * PROJECT: ReactOS kernel * FILE: ntoskrnl/ke/catch.c @@ -80,13 +80,13 @@ else if (KdDebuggerEnabled && KdDebugState & KD_DEBUG_KDB) { Action = KdbEnterDebuggerException (ExceptionRecord, Context, Tf); - if (Action == kdContinue) - { - return; - } } #endif /* KDBG */ - if (Action != kdDoNotHandleException) + if (Action == kdContinue) + { + return; + } + else if (Action != kdDoNotHandleException) { if (PreviousMode == UserMode) { @@ -94,7 +94,7 @@ { PULONG Stack; ULONG CDest; - char temp_space[12 + sizeof(EXCEPTION_RECORD) + sizeof(CONTEXT)]; // FIXME: HACKHACK + char temp_space[12 + sizeof(EXCEPTION_RECORD) + sizeof(CONTEXT)]; /* FIXME: HACKHACK */ PULONG pNewUserStack = (PULONG)(Tf->Esp - (12 + sizeof(EXCEPTION_RECORD) + sizeof(CONTEXT))); NTSTATUS StatusOfCopy; @@ -125,10 +125,11 @@ } else { - // Now it really hit the ventilation device. Sorry, - // can do nothing but kill the sucker. + /* Now it really hit the ventilation device. Sorry, + * can do nothing but kill the sucker. + */ ZwTerminateThread(NtCurrentThread(), ExceptionRecord->ExceptionCode); - DPRINT1("User-mode stack was invalid. Terminating target thread\nn"); + DPRINT1("User-mode stack was invalid. Terminating target thread\n"); } Tf->Eip = (ULONG)LdrpGetSystemDllExceptionDispatcher(); return; email" href="http://www.badgers-in-foil.co.uk/projects/cvsspam/">CVSspam 0.2.8

2 1

Our ne2000 driver and tcpip
by art yerkes 14 Nov '04

14 Nov '04

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

1 0

Genesi
by Jason Filby 14 Nov '04

14 Nov '04

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

5 6

RE: [ros-cvs] CVS Update: reactos
by Hartmut Birr 12 Nov '04

12 Nov '04

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 >

2 1

Re: [ros-dev] taskmgr crashes in regobj.c - CmiObjectParse on VirtualPC
by Theodor Willax 12 Nov '04

12 Nov '04

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!

2 1

Reactos Sound - Testing
by Gge 12 Nov '04

12 Nov '04

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

1 0

ReactOS Versions
by Rick Langschultz 12 Nov '04

12 Nov '04

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.

6 6

taskmgr crashes in regobj.c - CmiObjectParse on Virtual PC
by Theodor Willax 12 Nov '04

12 Nov '04

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!

2 1

RE: Ekush
by Ge van Geldorp 11 Nov '04

11 Nov '04

> 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.

1 0

Race Condition?
by James Tabor 11 Nov '04

11 Nov '04

Hi, I believe with the new cvs changes by Hartmut caused the illusive lockups I'm having to pop up more often now. Two today and yesterday. This print out looks good, but I've had debug messages overlapping each other at the beginning of the building process. Debug output before lockup, there seems to be a double print out, before just one every KernelTime, and the KernelTime looks like it had stopped, (KERNEL32:mem/global.c:412) Memory Load: 14 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266465 PFFree: 65536 PFUsed: 0 MC_CACHE 22993, MC_USER 4858, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 217935 (KERNEL32:mem/global.c:412) Memory Load: 14 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266465 PFFree: 65536 PFUsed: 0 MC_CACHE 23009, MC_USER 4864, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 217913 (KERNEL32:mem/global.c:412) Memory Load: 14 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266465 PFFree: 65536 PFUsed: 0 MC_CACHE 23009, MC_USER 4864, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 217913 (KERNEL32:mem/global.c:412) Memory Load: 14 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266471 PFFree: 65536 PFUsed: 0 MC_CACHE 23025, MC_USER 4870, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 217891 (KERNEL32:mem/global.c:412) Memory Load: 14 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266471 PFFree: 65536 PFUsed: 0 MC_CACHE 23025, MC_USER 4870, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 217891 (KERNEL32:mem/global.c:412) Memory Load: 14 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22065, MC_USER 4876, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218845 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22065, MC_USER 4876, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218845 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22081, MC_USER 4882, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218823 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22081, MC_USER 4882, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218823 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22097, MC_USER 4888, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218801 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22097, MC_USER 4888, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218801 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22113, MC_USER 4889, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218784 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22113, MC_USER 4889, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218784 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22129, MC_USER 4900, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218757 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22129, MC_USER 4900, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218757 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22145, MC_USER 4904, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218737 (KERNEL32:mem/global.c:412) Memory Load: 13 (ex/sysinfo.c:964) SystemFullMemoryInformation (ex/sysinfo.c:972) PID: 1, KernelTime: 4266474 PFFree: 65536 PFUsed: 0 MC_CACHE 22145, MC_USER 4904, MC_PPOOL 1079, MC_NPPOOL 7069, MmStats.NrFreePages 218737 (KERNEL32:mem/global.c:412) Memory Load: 13 System lockup, keyboard works???, num & scroll light works on/off. Anyone have a good guess where to start? Thanks, James

8 15

Ekush part II
by James Tabor 11 Nov '04

11 Nov '04

Hi all! Ros Kernel task switcher, http://blight.eu.org/reactos/ekush-tskswitch.html Great job Blight! On slashdot.org! http://slashdot.org/article.pl?sid=04/11/10/1320231&tid=201&tid=190&tid=1 Thanks a mil GvG! Kick'en A$$ mode, "Lets get our hate on"! )8^| James ps Moven it over to the General list.

3 2

Re: Ros-dev Digest, Vol 3, Issue 15
by Lucio Diaz 10 Nov '04

10 Nov '04

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

3 2

Ekush
by Ge van Geldorp 10 Nov '04

10 Nov '04

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.

16 24

RE: [ros-dev] Ekush
by Colin Burn 10 Nov '04

10 Nov '04

Somebody should email Wine\QEmu\Whoever else and let them know about these guys. Col

1 0

ReactOS setup CD-ROM crashes on old hardware.
by Mike Swanson 10 Nov '04

10 Nov '04

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.

4 4

Website Changes
by Steven Edwards 09 Nov '04

09 Nov '04

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

1 0

Hi!
by K McI 09 Nov '04

09 Nov '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 PING! ~ -Q -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBkTbW7mze81O92HkRAhWzAJ0Su/H6oOYnpwB1fxdiz3o4N1YcegCeOBBt RWLgqgJKj3IhNKE59wqmLrY= =JPza -----END PGP SIGNATURE-----

1 0

Re: [ros-cvs] CVS Update: reactos
by Alex Ionescu 08 Nov '04

08 Nov '04

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

9 25

What I have learned on my time off (LinuxWorld)
by Steven Edwards 08 Nov '04

08 Nov '04

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

4 6

Patch - somebody please review (FPU state saving)
by Gregor Anich 08 Nov '04

08 Nov '04

Hi! Here's a patch which mainly adds FPU state saving support on taskswitching. It does not protect User/Kernel mode "mixup" because I want this to be discussed further before it is implemented. I have also attached a program which tests if the FPU state is saved, it creates 2 threads which both do some FPU calculations and checks the result. One thing which is changed in the patch is that the taskswitching function (Ki386ContextSwitch) does not calculate the TSS->Esp0 from NewThread->InitialStack but saves it on the stack and restores it. For a v86 call there seems to be no more reason to change the InitialStack of the thread (InitialStack seems to be used only for setting up TSS->Esp0 on taskswitch - not anymore - and for IoGetInitialStack) so a v86 call saves and changes TSS->Esp0 instead of Thread->InitialStack. I have been talking with Filip about having 2 FPU save areas, one for kernel and one for user-mode... he was against it because of the stack space which is taken away. He also told me that the stack size cannot be changed because some drivers rely on it to calculate the remaining stack. What we could do is 1) Use KeSave/RestoreFloatingState() in KM when FPU is used. 2) Compile kernel-mode code with soft-fpu switch to make the compiler call a softfpu lib instead of using the x87 3) Put the FPU save areas somewhere else. Maybe we could allocate MM_STACK_SIZE + 2 * sizeof (FX_SAVE_AREA) and set InitialStack to StackBase + MM_STACK_SIZE (like now) so the stack size available for code would not change. It would also be cool to save the state only when needed. Maybe this could be done with a per-processor pointer to a FX_SAVE_AREA which is set to the last thread's FX_SAVE_AREA which used the FPU. When a not-present exception happens (after a taskswitch where TS in %cr0 was set) we check if the pointer is NULL, if it is not we save the current state into the area it points to and set it to point to the current thread's FX_SAVE_AREA and load the saved state (if any) of the current thread. When a thread terminates and per-processor FX_SAVE_AREA pointer points to the terminated thread's FX_SAVE_AREA we set it to NULL. Thanks, blight Index: include/ntos/tss.h =================================================================== RCS file: /CVS/ReactOS/reactos/include/ntos/tss.h,v retrieving revision 1.4 diff -u -r1.4 tss.h --- include/ntos/tss.h 5 Jan 2004 14:28:19 -0000 1.4 +++ include/ntos/tss.h 29 Oct 2004 14:55:49 -0000 @@ -5,7 +5,8 @@ #ifndef __INCLUDE_DDK_I386_TSS_H #define __INCLUDE_DDK_I386_TSS_H -#define KTSS_ESP0 (0x4) +#define KTSS_ESP0 (0x4) +#define KTSS_EFLAGS (0x24) #define KTSS_IOMAPBASE (0x66) #ifndef __ASM__ Index: ntoskrnl/include/internal/trap.h =================================================================== RCS file: /CVS/ReactOS/reactos/ntoskrnl/include/internal/trap.h,v retrieving revision 1.4 diff -u -r1.4 trap.h --- ntoskrnl/include/internal/trap.h 8 Sep 2002 10:23:23 -0000 1.4 +++ ntoskrnl/include/internal/trap.h 3 Nov 2004 17:43:44 -0000 @@ -27,10 +27,9 @@ #ifndef __NTOSKRNL_INCLUDE_INTERNAL_TRAP_H #define __NTOSKRNL_INCLUDE_INTERNAL_TRAP_H -#define TF_SAVED_ORIG_STACK (0x8C) -#define TF_REGS (0x90) -#define TF_ORIG_EBP (0x94) - +#define TF_SAVED_EXCEPTION_STACK (0x8C) +#define TF_REGS (0x90) +#define TF_ORIG_EBP (0x94) #ifndef __ASM__ @@ -40,7 +39,7 @@ { KTRAP_FRAME Tf; - ULONG SavedInitialStack; + ULONG SavedExceptionStack; /* * These are put on the top of the stack by the routine that entered Index: ntoskrnl/include/internal/i386/fpu.h =================================================================== RCS file: /CVS/ReactOS/reactos/ntoskrnl/include/internal/i386/fpu.h,v retrieving revision 1.5 diff -u -r1.5 fpu.h --- ntoskrnl/include/internal/i386/fpu.h 12 Oct 2004 00:33:30 -0000 1.5 +++ ntoskrnl/include/internal/i386/fpu.h 22 Oct 2004 22:37:26 -0000 @@ -20,11 +20,20 @@ #ifndef __NTOSKRNL_INCLUDE_INTERNAL_I386_FPU_H #define __NTOSKRNL_INCLUDE_INTERNAL_I386_FPU_H +#define SIZEOF_FX_SAVE_AREA 528 + +#ifndef __ASM__ + +#include <internal/i386/ke.h> + extern ULONG HardwareMathSupport; VOID KiCheckFPU(VOID); +NTSTATUS +KiHandleFpuFault(PKTRAP_FRAME Tf, ULONG ExceptionNr); + typedef struct _FNSAVE_FORMAT { ULONG ControlWord; ULONG StatusWord; @@ -62,4 +71,7 @@ ULONG Cr0NpxState; } FX_SAVE_AREA, *PFX_SAVE_AREA; +#endif /* !__ASM__ */ + #endif /* __NTOSKRNL_INCLUDE_INTERNAL_I386_FPU_H */ + Index: ntoskrnl/include/internal/i386/ke.h =================================================================== RCS file: /CVS/ReactOS/reactos/ntoskrnl/include/internal/i386/ke.h,v retrieving revision 1.15 diff -u -r1.15 ke.h --- ntoskrnl/include/internal/i386/ke.h 31 Oct 2004 12:49:36 -0000 1.15 +++ ntoskrnl/include/internal/i386/ke.h 4 Nov 2004 00:17:41 -0000 @@ -69,9 +69,17 @@ #define KTRAP_FRAME_RESERVED9 (0x8A) #define KTRAP_FRAME_SIZE (0x8C) +#define X86_EFLAGS_IF 0x00000200 /* Interrupt Enable flag */ +#define X86_EFLAGS_IOPL 0x00003000 /* I/O Privilege Level bits */ +#define X86_EFLAGS_NT 0x00004000 /* Nested Task flag */ #define X86_EFLAGS_VM 0x00020000 /* Virtual Mode */ #define X86_EFLAGS_ID 0x00200000 /* CPUID detection flag */ +#define X86_CR0_NE 0x00000020 /* enable native FPU error reporting */ +#define X86_CR0_TS 0x00000008 /* enable exception on FPU instruction for task switch */ +#define X86_CR0_EM 0x00000004 /* enable FPU emulation (disable FPU) */ +#define X86_CR0_MP 0x00000002 /* enable FPU monitoring */ + #define X86_CR4_PAE 0x00000020 /* enable physical address extensions */ #define X86_CR4_PGE 0x00000080 /* enable global pages */ @@ -85,6 +93,11 @@ #define X86_EXT_FEATURE_3DNOW 0x40000000 /* 3DNOW! extension present */ +/* Possible values for KTHREAD's NpxState */ +#define NPX_STATE_INVALID 0x01 +#define NPX_STATE_VALID 0x02 +#define NPX_STATE_DIRTY 0x04 + #ifndef __ASM__ typedef struct _KTRAP_FRAME @@ -187,12 +200,20 @@ : "r" (X)); #define Ke386SaveFlags(x) __asm__ __volatile__("pushfl ; popl %0":"=g" (x): /* no input */) #define Ke386RestoreFlags(x) __asm__ __volatile__("pushl %0 ; popfl": /* no output */ :"g" (x):"memory") -#define Ke386GetCr4() ({ \ + +#define _Ke386GetCr(N) ({ \ unsigned int __d; \ - __asm__("movl %%cr4,%0\n\t" :"=r" (__d)); \ + __asm__("movl %%cr" #N ",%0\n\t" :"=r" (__d)); \ __d; \ }) -#define Ke386SetCr4(X) __asm__ __volatile__("movl %0,%%cr4": :"r" (X)); +#define _Ke386SetCr(N,X) __asm__ __volatile__("movl %0,%%cr" #N : :"r" (X)); + +#define Ke386GetCr0() _Ke386GetCr(0) +#define Ke386SetCr0(X) _Ke386SetCr(0,X) +#define Ke386GetCr2() _Ke386GetCr(2) +#define Ke386SetCr2(X) _Ke386SetCr(2,X) +#define Ke386GetCr4() _Ke386GetCr(4) +#define Ke386SetCr4(X) _Ke386SetCr(4,X) static inline void Ki386Cpuid(ULONG Op, PULONG Eax, PULONG Ebx, PULONG Ecx, PULONG Edx) { @@ -207,6 +228,7 @@ #elif defined(_MSC_VER) + #define Ke386DisableInterrupts() __asm cli #define Ke386EnableInterrupts() __asm sti #define Ke386HaltProcessor() __asm hlt Index: ntoskrnl/include/internal/i386/ps.h =================================================================== RCS file: /CVS/ReactOS/reactos/ntoskrnl/include/internal/i386/ps.h,v retrieving revision 1.16 diff -u -r1.16 ps.h --- ntoskrnl/include/internal/i386/ps.h 30 Oct 2004 23:48:56 -0000 1.16 +++ ntoskrnl/include/internal/i386/ps.h 3 Nov 2004 19:02:51 -0000 @@ -26,6 +26,7 @@ #define KTHREAD_STACK_LIMIT 0x1C #define KTHREAD_TEB 0x20 #define KTHREAD_KERNEL_STACK 0x28 +#define KTHREAD_NPX_STATE 0x31 #define KTHREAD_APCSTATE_PROCESS 0x44 #define KTHREAD_SERVICE_TABLE 0xDC #define KTHREAD_PREVIOUS_MODE 0x137 @@ -51,12 +52,12 @@ #pragma pack(push,4) -// Fixme: Use correct types? +/* Fixme: Use correct types? */ typedef struct _KPROCESSOR_STATE { PCONTEXT ContextFrame; PVOID SpecialRegisters; } KPROCESSOR_STATE; - + /* ProcessoR Control Block */ typedef struct _KPRCB { USHORT MinorVersion; Index: ntoskrnl/ke/main.c =================================================================== RCS file: /CVS/ReactOS/reactos/ntoskrnl/ke/main.c,v retrieving revision 1.202 diff -u -r1.202 main.c --- ntoskrnl/ke/main.c 24 Oct 2004 15:26:14 -0000 1.202 +++ ntoskrnl/ke/main.c 3 Nov 2004 17:43:51 -0000 @@ -297,6 +297,7 @@ ASSERT(FIELD_OFFSET(KTHREAD, InitialStack) == KTHREAD_INITIAL_STACK); ASSERT(FIELD_OFFSET(KTHREAD, Teb) == KTHREAD_TEB); ASSERT(FIELD_OFFSET(KTHREAD, KernelStack) == KTHREAD_KERNEL_STACK); + ASSERT(FIELD_OFFSET(KTHREAD, NpxState) == KTHREAD_NPX_STATE); ASSERT(FIELD_OFFSET(KTHREAD, ServiceTable) == KTHREAD_SERVICE_TABLE); ASSERT(FIELD_OFFSET(KTHREAD, PreviousMode) == KTHREAD_PREVIOUS_MODE); ASSERT(FIELD_OFFSET(KTHREAD, TrapFrame) == KTHREAD_TRAP_FRAME); @@ -307,6 +308,7 @@ ASSERT(FIELD_OFFSET(KPROCESS, IopmOffset) == KPROCESS_IOPM_OFFSET); ASSERT(FIELD_OFFSET(KPROCESS, LdtDescriptor) == KPROCESS_LDT_DESCRIPTOR0); ASSERT(FIELD_OFFSET(KTRAP_FRAME, Reserved9) == KTRAP_FRAME_RESERVED9); + ASSERT(FIELD_OFFSET(KV86M_TRAP_FRAME, SavedExceptionStack) == TF_SAVED_EXCEPTION_STACK); ASSERT(FIELD_OFFSET(KV86M_TRAP_FRAME, regs) == TF_REGS); ASSERT(FIELD_OFFSET(KV86M_TRAP_FRAME, orig_ebp) == TF_ORIG_EBP); @@ -314,6 +316,12 @@ ASSERT(FIELD_OFFSET(KPCR, Self) == KPCR_SELF); ASSERT(FIELD_OFFSET(KPCR, PrcbData) + FIELD_OFFSET(KPRCB, CurrentThread) == KPCR_CURRENT_THREAD); + ASSERT(FIELD_OFFSET(KTSS, Esp0) == KTSS_ESP0); + ASSERT(FIELD_OFFSET(KTSS, Eflags) == KTSS_EFLAGS); + ASSERT(FIELD_OFFSET(KTSS, IoMapBase) == KTSS_IOMAPBASE); + + ASSERT(sizeof(FX_SAVE_AREA) == SIZEOF_FX_SAVE_AREA); + LdrInit1(); KeLowerIrql(DISPATCH_LEVEL); Index: ntoskrnl/ke/i386/bthread.S =================================================================== RCS file: /CVS/ReactOS/reactos/ntoskrnl/ke/i386/bthread.S,v retrieving revision 1.10 diff -u -r1.10 bthread.S --- ntoskrnl/ke/i386/bthread.S 31 Oct 2004 19:46:10 -0000 1.10 +++ ntoskrnl/ke/i386/bthread.S 3 Nov 2004 19:05:17 -0000 @@ -141,18 +141,6 @@ addl $24, %esp .L3: - /* - * Load the floating point registers - */ - movl (_HardwareMathSupport), %eax - testl %eax,%eax - jz .L2 - testl $(CONTEXT_FLOATING_POINT & ~CONTEXT_i386), %ebx - jz .L2 - frstor (%esp) -.L2: - addl $112, %esp - /* Load the rest of the thread's user mode context. */ movl $0, %eax jmp KeReturnFromSystemCallWithHook Index: ntoskrnl/ke/i386/exp.c =================================================================== RCS file: /CVS/ReactOS/reactos/ntoskrnl/ke/i386/exp.c,v retrieving revision 1.93 diff -u -r1.93 exp.c --- ntoskrnl/ke/i386/exp.c 22 Oct 2004 20:32:48 -0000 1.93 +++ ntoskrnl/ke/i386/exp.c 23 Oct 2004 18:26:36 -0000 @@ -40,6 +40,10 @@ #define _STR(x) #x #define STR(x) _STR(x) +#ifndef ARRAY_SIZE +# define ARRAY_SIZE(x) (sizeof (x) / sizeof (x[0])) +#endif + extern void interrupt_handler2e(void); extern void interrupt_handler2d(void); @@ -84,6 +88,7 @@ "Stack Segment Fault", "General Protection", "Page Fault", + "Reserved(15)", "Math Fault", "Alignment Check", "Machine Check" @@ -106,6 +111,7 @@ STATUS_STACK_OVERFLOW, STATUS_ACCESS_VIOLATION, STATUS_ACCESS_VIOLATION, + STATUS_ACCESS_VIOLATION, /* RESERVED */ STATUS_ACCESS_VIOLATION, /* STATUS_FLT_INVALID_OPERATION */ STATUS_DATATYPE_MISALIGNMENT, STATUS_ACCESS_VIOLATION @@ -167,7 +173,7 @@ } else { - if (ExceptionNr < 16) + if (ExceptionNr < ARRAY_SIZE(ExceptionToNtStatus)) { Er.ExceptionCode = ExceptionToNtStatus[ExceptionNr]; } @@ -190,7 +196,7 @@ ULONG KiDoubleFaultHandler(VOID) { - unsigned int cr2_; + unsigned int cr2; ULONG StackLimit; ULONG StackBase; ULONG Esp0; @@ -211,15 +217,7 @@ Esp0 = OldTss->Esp; /* Get CR2 */ -#if defined(__GNUC__) - __asm__("movl %%cr2,%0\n\t" : "=d" (cr2_)); -#elif defined(_MSC_VER) - __asm mov eax, cr2; - __asm mov cr2_, eax; -#else -#error Unknown compiler for inline assembler -#endif - + cr2 = Ke386GetCr2(); if (PsGetCurrentThread() != NULL && PsGetCurrentThread()->ThreadsProcess != NULL) { @@ -245,7 +243,7 @@ /* * Print out the CPU registers */ - if (ExceptionNr < 19) + if (ExceptionNr < ARRAY_SIZE(ExceptionTypeStrings)) { DbgPrint("%s Exception: %d(%x)\n", ExceptionTypeStrings[ExceptionNr], ExceptionNr, 0); @@ -257,7 +255,7 @@ DbgPrint("CS:EIP %x:%x ", OldTss->Cs, OldTss->Eip); KeRosPrintAddress((PVOID)OldTss->Eip); DbgPrint("\n"); - DbgPrint("cr2 %x cr3 %x ", cr2_, OldCr3); + DbgPrint("cr2 %x cr3 %x ", cr2, OldCr3); DbgPrint("Proc: %x ",PsGetCurrentProcess()); if (PsGetCurrentProcess() != NULL) { @@ -420,7 +418,7 @@ /* * Print out the CPU registers */ - if (ExceptionNr < 19) + if (ExceptionNr < ARRAY_SIZE(ExceptionTypeStrings)) { DbgPrint("%s Exception: %d(%x)\n", ExceptionTypeStrings[ExceptionNr], ExceptionNr, Tf->ErrorCode&0xffff); @@ -529,7 +527,7 @@ * Complete CPU context */ { - unsigned int cr2_; + unsigned int cr2; NTSTATUS Status; ULONG Esp0; @@ -540,22 +538,15 @@ Esp0 = (ULONG)&Tf->Eip; /* Get CR2 */ -#if defined(__GNUC__) - __asm__("movl %%cr2,%0\n\t" : "=d" (cr2_)); -#elif defined(_MSC_VER) - __asm mov eax, cr2; - __asm mov cr2_, eax; -#else -#error Unknown compiler for inline assembler -#endif - Tf->DebugPointer = (PVOID)cr2_; + cr2 = Ke386GetCr2(); + Tf->DebugPointer = (PVOID)cr2; /* * If this was a V86 mode exception then handle it specially */ if (Tf->Eflags & (1 << 17)) { - return(KeV86Exception(ExceptionNr, Tf, cr2_)); + return(KeV86Exception(ExceptionNr, Tf, cr2)); } /* @@ -574,7 +565,7 @@ */ if (ExceptionNr == 14) { - if (Ke386NoExecute && Tf->ErrorCode & 0x10 && cr2_ >= KERNEL_BASE) + if (Ke386NoExecute && Tf->ErrorCode & 0x10 && cr2 >= KERNEL_BASE) { KEBUGCHECKWITHTF(ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY, 0, 0, 0, 0, Tf); } @@ -585,7 +576,7 @@ Status = MmPageFault(Tf->Cs&0xffff, &Tf->Eip, &Tf->Eax, - cr2_, + cr2, Tf->ErrorCode); if (NT_SUCCESS(Status)) { @@ -606,15 +597,27 @@ } /* + * Try to handle device-not-present and math-fault exceptions. + */ + if (ExceptionNr == 7 || ExceptionNr == 16) + { + Status = KiHandleFpuFault(Tf, ExceptionNr); + if (NT_SUCCESS(Status)) + { + return(0); + } + } + + /* * Handle user exceptions differently */ if ((Tf->Cs & 0xFFFF) == USER_CS) { - return(KiUserTrapHandler(Tf, ExceptionNr, (PVOID)cr2_)); + return(KiUserTrapHandler(Tf, ExceptionNr, (PVOID)cr2)); } else { - return(KiKernelTrapHandler(Tf, ExceptionNr, (PVOID)cr2_)); + return(KiKernelTrapHandler(Tf, ExceptionNr, (PVOID)cr2)); } } Index: ntoskrnl/ke/i386/fpu.c =================================================================== RCS file: /CVS/ReactOS/reactos/ntoskrnl/ke/i386/fpu.c,v retrieving revision 1.13 diff -u -r1.13 fpu.c --- ntoskrnl/ke/i386/fpu.c 15 Aug 2004 16:39:05 -0000 1.13 +++ ntoskrnl/ke/i386/fpu.c 4 Nov 2004 02:48:39 -0000 @@ -32,6 +32,33 @@ #define NDEBUG #include <internal/debug.h> +/* DEFINES *******************************************************************/ +#define EXCEPTION_FLT_DENORMAL_OPERAND (0xc000008dL) +#define EXCEPTION_FLT_DIVIDE_BY_ZERO (0xc000008eL) +#define EXCEPTION_FLT_INEXACT_RESULT (0xc000008fL) +#define EXCEPTION_FLT_INVALID_OPERATION (0xc0000090L) +#define EXCEPTION_FLT_OVERFLOW (0xc0000091L) +#define EXCEPTION_FLT_STACK_CHECK (0xc0000092L) +#define EXCEPTION_FLT_UNDERFLOW (0xc0000093L) + +/* x87 Status Word exception flags */ +#define X87_SW_IE (1<<0) /* Invalid Operation */ +#define X87_SW_DE (1<<1) /* Denormalized Operand */ +#define X87_SW_ZE (1<<2) /* Zero Devide */ +#define X87_SW_OE (1<<3) /* Overflow */ +#define X87_SW_UE (1<<4) /* Underflow */ +#define X87_SW_PE (1<<5) /* Precision */ +#define X87_SW_SE (1<<6) /* Stack Fault */ + +#define X87_SW_ES (1<<7) /* Error Summary */ + +#if 0 +#define X87_SW_C0 (1<<8) /* Condition code */ +#define X87_SW_C1 (1<<9) /* Condition code */ +#define X87_SW_C2 (1<<10) /* Condition code */ +#define X87_SW_C3 (1<<14) /* Condition code */ +#endif + /* GLOBALS *******************************************************************/ ULONG HardwareMathSupport; @@ -42,56 +69,41 @@ KiCheckFPU(VOID) { unsigned short int status; - int cr0_; + int cr0; HardwareMathSupport = 0; - -#if defined(__GNUC__) - __asm__("movl %%cr0, %0\n\t" : "=a" (cr0_)); - /* Set NE and MP. */ - cr0_ = cr0_ | 0x22; - /* Clear EM */ - cr0_ = cr0_ & (~0x4); - __asm__("movl %0, %%cr0\n\t" : : "a" (cr0_)); + cr0 = Ke386GetCr0(); + cr0 |= X86_CR0_NE | X86_CR0_MP; + cr0 &= ~X86_CR0_EM; + Ke386SetCr0(cr0); +#if defined(__GNUC__) __asm__("clts\n\t"); __asm__("fninit\n\t"); __asm__("fstsw %0\n\t" : "=a" (status)); - if (status != 0) - { - __asm__("movl %%cr0, %0\n\t" : "=a" (cr0_)); - /* Set the EM flag in CR0 so any FPU instructions cause a trap. */ - cr0_ = cr0_ | 0x4; - __asm__("movl %0, %%cr0\n\t" : - : "a" (cr0_)); - return; - } - /* fsetpm for i287, ignored by i387 */ - __asm__(".byte 0xDB, 0xE4\n\t"); #elif defined(_MSC_VER) - __asm mov eax, cr0; - __asm mov cr0_, eax; - cr0_ |= 0x22; /* Set NE and MP. */ - cr0_ &= ~0x4; /* Clear EM */ __asm { - mov eax, cr0_; - mov cr0, eax; clts; fninit; fstsw status } +#else +#error Unknown compiler for inline assembler +#endif + if (status != 0) { - __asm mov eax, cr0_; - __asm or eax, 4; /* Set the EM flag in CR0 so any FPU instructions cause a trap. */ - __asm mov cr0, eax; + /* Set the EM flag in CR0 so any FPU instructions cause a trap. */ + Ke386SetCr0(Ke386GetCr0() | X86_CR0_EM); return; } + /* fsetpm for i287, ignored by i387 */ +#if defined(__GNUC__) + __asm__(".byte 0xDB, 0xE4\n\t"); +#elif defined(_MSC_VER) __asm _emit 0xDB __asm _emit 0xe4 -// __asm fsetpm; -// __asm__(".byte 0xDB, 0xE4\n\t"); #else #error Unknown compiler for inline assembler #endif @@ -109,6 +121,12 @@ { char *FpState; + /* check if we are doing software emulation */ + if (!HardwareMathSupport) + { + return STATUS_ILLEGAL_FLOAT_CONTEXT; + } + FpState = ExAllocatePool(PagedPool, FPU_STATE_SIZE); if (NULL == FpState) { @@ -146,3 +164,104 @@ return STATUS_SUCCESS; } + +NTSTATUS +KiHandleFpuFault(PKTRAP_FRAME Tf, ULONG ExceptionNr) +{ + if (ExceptionNr == 7) /* device not present */ + { + unsigned int cr0 = Ke386GetCr0(); + PFX_SAVE_AREA FxSaveArea = (PFX_SAVE_AREA)((char *)KeGetCurrentThread()->InitialStack - sizeof (FX_SAVE_AREA)); + + ASSERT((cr0 & X86_CR0_TS) == X86_CR0_TS); + ASSERT((Tf->Eflags & X86_EFLAGS_VM) == 0); + ASSERT((cr0 & X86_CR0_EM) == 0); + + Ke386DisableInterrupts(); + + cr0 &= ~X86_CR0_TS; + Ke386SetCr0(cr0); + + DPRINT("Device not present exception happened! (Cr0 = 0x%x, NpxState = 0x%x)\n", Ke386GetCr0(), KeGetCurrentThread()->NpxState); + if (KeGetCurrentThread()->NpxState & NPX_STATE_VALID) + { +#if 1 + DPRINT("Restoring previous FPU state\n"); + DPRINT("ControlWord = 0x%08x\n", FxSaveArea->U.FnArea.ControlWord); + DPRINT("StatusWord = 0x%08x\n", FxSaveArea->U.FnArea.StatusWord); + DPRINT("TagWord = 0x%08x\n", FxSaveArea->U.FnArea.TagWord); + DPRINT("ErrorOffset = 0x%08x\n", FxSaveArea->U.FnArea.ErrorOffset); + DPRINT("ErrorSelector = 0x%08x\n", FxSaveArea->U.FnArea.ErrorSelector); + DPRINT("DataOffset = 0x%08x\n", FxSaveArea->U.FnArea.DataOffset); + DPRINT("DataSelector = 0x%08x\n", FxSaveArea->U.FnArea.DataSelector); + DPRINT("Thread->InitialStack = 0x%08x\n", (ULONG)KeGetCurrentThread()->InitialStack); + DPRINT("Thread->KernelStack = 0x%08x\n", (ULONG)KeGetCurrentThread()->KernelStack); +#endif + __asm__ __volatile__("frstor %0" : : "m"(*FxSaveArea)); + } + else /* NpxState & NPX_STATE_INVALID */ + { + DPRINT("Setting up clean FPU state\n"); + __asm__ __volatile__("finit"); + } + KeGetCurrentThread()->NpxState |= NPX_STATE_DIRTY; + DPRINT("Device not present exception handled!\n"); + Ke386EnableInterrupts(); + return STATUS_SUCCESS; + } + else + { + WORD FpuStatusWord; + EXCEPTION_RECORD Er; + CONTEXT Context; + KPROCESSOR_MODE PreviousMode; + + ASSERT(ExceptionNr == 16); /* math fault */ + + PreviousMode = ((Tf->Cs & 0xffff) == USER_CS) ? (UserMode) : (KernelMode); + DPRINT("Math-fault happened! (PreviousMode = %s)\n", + (PreviousMode == UserMode) ? ("UserMode") : ("KernelMode")); + /* Get fpu status and clear exception flags */ + __asm__("fnstenv %0" : "=m"(Context.FloatSave)); + __asm__("fnclex"); /* FIXME: clear only handled exceptions? */ + FpuStatusWord = Context.FloatSave.StatusWord & 0xffff; + + Ke386EnableInterrupts(); + + DPRINT("FpuStatusWord = 0x%04x\n", FpuStatusWord); + + /* Dispatch exception */ + if (FpuStatusWord & X87_SW_IE) + Er.ExceptionCode = EXCEPTION_FLT_INVALID_OPERATION; + else if (FpuStatusWord & X87_SW_DE) + Er.ExceptionCode = EXCEPTION_FLT_DENORMAL_OPERAND; + else if (FpuStatusWord & X87_SW_ZE) + Er.ExceptionCode = EXCEPTION_FLT_DIVIDE_BY_ZERO; + else if (FpuStatusWord & X87_SW_OE) + Er.ExceptionCode = EXCEPTION_FLT_OVERFLOW; + else if (FpuStatusWord & X87_SW_UE) + Er.ExceptionCode = EXCEPTION_FLT_UNDERFLOW; + else if (FpuStatusWord & X87_SW_PE) + Er.ExceptionCode = EXCEPTION_FLT_INEXACT_RESULT; + else if (FpuStatusWord & X87_SW_SE) + Er.ExceptionCode = EXCEPTION_FLT_STACK_CHECK; + else + ASSERT(0); /* not reached */ + + Er.ExceptionFlags = 0; + Er.ExceptionRecord = NULL; + /* FIXME: is this the right way to get the correct EIP of the faulting instruction? */ + Er.ExceptionAddress = (PVOID)Context.FloatSave.ErrorOffset; + Er.NumberParameters = 0; + + /* FIXME: we should pass in a context with floating save area to KiDispatchException */ + DPRINT("Dispatching exception\n"); + KiDispatchException(&Er, NULL, Tf, PreviousMode, TRUE); + + DPRINT("Math-fault handled!\n"); + return STATUS_SUCCESS; + } + + return STATUS_UNSUCCESSFUL; +} + Index: ntoskrnl/ke/i386/multiboot.S =================================================================== RCS file: /CVS/ReactOS/reactos/ntoskrnl/ke/i386/multiboot.S,v retrieving revision 1.28 diff -u -r1.28 multiboot.S --- ntoskrnl/ke/i386/multiboot.S 31 Oct 2004 19:46:10 -0000 1.28 +++ ntoskrnl/ke/i386/multiboot.S 3 Nov 2004 19:02:53 -0000 @@ -3,6 +3,7 @@ #include <internal/i386/segment.h> #include <internal/ps.h> #include <internal/i386/mm.h> +#include <internal/i386/fpu.h> #define MULTIBOOT_HEADER_MAGIC (0x1BADB002) @@ -279,7 +280,7 @@ /* * Load the initial kernel stack */ - movl $_init_stack_top, %esp + movl $(_init_stack_top - SIZEOF_FX_SAVE_AREA), %esp /* * Initialize EFLAGS Index: ntoskrnl/ke/i386/thread.c =================================================================== RCS file: /CVS/ReactOS/reactos/ntoskrnl/ke/i386/thread.c,v retrieving revision 1.33 diff -u -r1.33 thread.c --- ntoskrnl/ke/i386/thread.c 15 Aug 2004 16:39:05 -0000 1.33 +++ ntoskrnl/ke/i386/thread.c 4 Nov 2004 00:18:55 -0000 @@ -31,13 +31,6 @@ #define NDEBUG #include <internal/debug.h> -/* GLOBALS *******************************************************************/ - -#define FLAG_NT (1<<14) -#define FLAG_VM (1<<17) -#define FLAG_IF (1<<9) -#define FLAG_IOPL ((1<<12)+(1<<13)) - /* FUNCTIONS *****************************************************************/ NTSTATUS @@ -77,10 +70,10 @@ { return(STATUS_UNSUCCESSFUL); } - if ((Context->EFlags & FLAG_IOPL) != 0 || - (Context->EFlags & FLAG_NT) || - (Context->EFlags & FLAG_VM) || - (!(Context->EFlags & FLAG_IF))) + if ((Context->EFlags & X86_EFLAGS_IOPL) != 0 || + (Context->EFlags & X86_EFLAGS_NT) || + (Context->EFlags & X86_EFLAGS_VM) || + (!(Context->EFlags & X86_EFLAGS_IF))) { return(STATUS_UNSUCCESSFUL); } @@ -93,40 +86,37 @@ PULONG KernelStack; ULONG InitSize; PKTRAP_FRAME TrapFrame; + PFX_SAVE_AREA FxSaveArea; /* * Setup a stack frame for exit from the task switching routine */ - InitSize = 5 * sizeof(DWORD) + sizeof(DWORD) + 6 * sizeof(DWORD) + - sizeof(FLOATING_SAVE_AREA) + sizeof(KTRAP_FRAME); + InitSize = 6 * sizeof(DWORD) + sizeof(DWORD) + 6 * sizeof(DWORD) + + + sizeof(KTRAP_FRAME) + sizeof (FX_SAVE_AREA); KernelStack = (PULONG)((char*)Thread->KernelStack - InitSize); /* Set up the initial frame for the return from the dispatcher. */ - KernelStack[0] = 0; /* EDI */ - KernelStack[1] = 0; /* ESI */ - KernelStack[2] = 0; /* EBX */ - KernelStack[3] = 0; /* EBP */ - KernelStack[4] = (ULONG)&PsBeginThreadWithContextInternal; /* EIP */ + KernelStack[0] = (ULONG)Thread->InitialStack - sizeof(FX_SAVE_AREA); /* TSS->Esp0 */ + KernelStack[1] = 0; /* EDI */ + KernelStack[2] = 0; /* ESI */ + KernelStack[3] = 0; /* EBX */ + KernelStack[4] = 0; /* EBP */ + KernelStack[5] = (ULONG)&PsBeginThreadWithContextInternal; /* EIP */ /* Save the context flags. */ - KernelStack[5] = Context->ContextFlags; + KernelStack[6] = Context->ContextFlags; /* Set up the initial values of the debugging registers. */ - KernelStack[6] = Context->Dr0; - KernelStack[7] = Context->Dr1; - KernelStack[8] = Context->Dr2; - KernelStack[9] = Context->Dr3; - KernelStack[10] = Context->Dr6; - KernelStack[11] = Context->Dr7; - - /* Set up the initial floating point state. */ - memcpy((PVOID)&KernelStack[12], (PVOID)&Context->FloatSave, - sizeof(FLOATING_SAVE_AREA)); + KernelStack[7] = Context->Dr0; + KernelStack[8] = Context->Dr1; + KernelStack[9] = Context->Dr2; + KernelStack[10] = Context->Dr3; + KernelStack[11] = Context->Dr6; + KernelStack[12] = Context->Dr7; /* Set up a trap frame from the context. */ - TrapFrame = (PKTRAP_FRAME) - ((char*)KernelStack + 12 * sizeof(DWORD) + sizeof(FLOATING_SAVE_AREA)); + TrapFrame = (PKTRAP_FRAME)(&KernelStack[13]); TrapFrame->DebugEbp = (PVOID)Context->Ebp; TrapFrame->DebugEip = (PVOID)Context->Eip; TrapFrame->DebugArgMark = 0; @@ -149,12 +139,39 @@ TrapFrame->ErrorCode = 0; TrapFrame->Cs = Context->SegCs; TrapFrame->Eip = Context->Eip; - TrapFrame->Eflags = Context->EFlags | FLAG_IF; - TrapFrame->Eflags &= ~(FLAG_VM | FLAG_NT | FLAG_IOPL); + TrapFrame->Eflags = Context->EFlags | X86_EFLAGS_IF; + TrapFrame->Eflags &= ~(X86_EFLAGS_VM | X86_EFLAGS_NT | X86_EFLAGS_IOPL); TrapFrame->Esp = Context->Esp; TrapFrame->Ss = (USHORT)Context->SegSs; /* FIXME: Should check for a v86 mode context here. */ + /* Set up the initial floating point state. */ + if (Context->ContextFlags & CONTEXT_FLOATING_POINT) + { + FxSaveArea = (PFX_SAVE_AREA)((ULONG_PTR)KernelStack + InitSize - sizeof(FX_SAVE_AREA)); + memcpy((PVOID)&FxSaveArea->U.FnArea, (PVOID)&Context->FloatSave, sizeof(FxSaveArea->U.FnArea)); + FxSaveArea->Cr0NpxState = Context->FloatSave.Cr0NpxState; + /* FIXME: for SSE we have to convert FLOATING_SAVE_AREA to FX_SAVE_AREA */ + +#ifndef NDEBUG + DPRINT1("Thread's initial FPU status (0x%x):\n", (ULONG)FxSaveArea); + DPRINT1("ControlWord = 0x%08x\n", FxSaveArea->U.FnArea.ControlWord); + DPRINT1("StatusWord = 0x%08x\n", FxSaveArea->U.FnArea.StatusWord); + DPRINT1("TagWord = 0x%08x\n", FxSaveArea->U.FnArea.TagWord); + DPRINT1("ErrorOffset = 0x%08x\n", FxSaveArea->U.FnArea.ErrorOffset); + DPRINT1("ErrorSelector = 0x%08x\n", FxSaveArea->U.FnArea.ErrorSelector); + DPRINT1("DataOffset = 0x%08x\n", FxSaveArea->U.FnArea.DataOffset); + DPRINT1("DataSelector = 0x%08x\n", FxSaveArea->U.FnArea.DataSelector); + DPRINT1("Thread->InitialStack = 0x%08x\n", (ULONG)Thread->InitialStack); + DPRINT1("Thread->KernelStack = 0x%08x\n", (ULONG)Thread->KernelStack); +#endif + Thread->NpxState = NPX_STATE_VALID; + } + else + { + Thread->NpxState = NPX_STATE_INVALID; + } + /* Save back the new value of the kernel stack. */ Thread->KernelStack = (PVOID)KernelStack; @@ -175,21 +192,25 @@ * Setup a stack frame for exit from the task switching routine */ - KernelStack = (PULONG)((char*)Thread->KernelStack - (8*4)); - KernelStack[0] = 0; /* EDI */ - KernelStack[1] = 0; /* ESI */ - KernelStack[2] = 0; /* EBX */ - KernelStack[3] = 0; /* EBP */ - KernelStack[4] = (ULONG)&PsBeginThread; /* EIP */ - KernelStack[5] = 0; /* Return EIP */ - KernelStack[6] = (ULONG)StartRoutine; /* First argument to PsBeginThread */ - KernelStack[7] = (ULONG)StartContext; /* Second argument to PsBeginThread */ + KernelStack = (PULONG)((char*)Thread->KernelStack - (9 * sizeof(DWORD)) - sizeof(FX_SAVE_AREA)); + KernelStack[0] = (ULONG)Thread->InitialStack - sizeof(FX_SAVE_AREA); /* TSS->Esp0 */ + KernelStack[1] = 0; /* EDI */ + KernelStack[2] = 0; /* ESI */ + KernelStack[3] = 0; /* EBX */ + KernelStack[4] = 0; /* EBP */ + KernelStack[5] = (ULONG)&PsBeginThread; /* EIP */ + KernelStack[6] = 0; /* Return EIP */ + KernelStack[7] = (ULONG)StartRoutine; /* First argument to PsBeginThread */ + KernelStack[8] = (ULONG)StartContext; /* Second argument to PsBeginThread */ Thread->KernelStack = (VOID*)KernelStack; + /* + * Setup FPU state + */ + Thread->NpxState = NPX_STATE_INVALID; + return(STATUS_SUCCESS); } - - - /* EOF */ + Index: ntoskrnl/ke/i386/tskswitch.S =================================================================== RCS file: /CVS/ReactOS/reactos/ntoskrnl/ke/i386/tskswitch.S,v retrieving revision 1.19 diff -u -r1.19 tskswitch.S --- ntoskrnl/ke/i386/tskswitch.S 31 Oct 2004 19:46:10 -0000 1.19 +++ ntoskrnl/ke/i386/tskswitch.S 4 Nov 2004 00:32:57 -0000 @@ -17,16 +17,18 @@ * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. */ /* - * FILE: ntoskrnl/ke/i386/tskswitch.S - * PURPOSE: Microkernel thread support + * FILE: ntoskrnl/ke/i386/tskswitch.S + * PURPOSE: Microkernel thread support * PROGRAMMER: David Welch (welch(a)cwcom.net) * UPDATE HISTORY: - * Created 09/10/00 + * Created 09/10/00 */ /* INCLUDES ******************************************************************/ #include <internal/i386/segment.h> +#include <internal/i386/ke.h> +#include <internal/i386/fpu.h> #include <internal/ps.h> #include <ntos/tss.h> #include <internal/ntoskrnl.h> @@ -34,12 +36,13 @@ /* FUNCTIONS ****************************************************************/ .globl _Ki386ContextSwitch +.func Ki386ContextSwitch _Ki386ContextSwitch: -/* +/* * FUNCTIONS: Switches to another thread's context * ARGUMENTS: - * Thread = Thread to switch to - * OldThread = Thread to switch from + * Thread = Thread to switch to + * OldThread = Thread to switch from */ pushl %ebp movl %esp, %ebp @@ -60,7 +63,7 @@ * Get the pointer to the new thread. */ movl 8(%ebp), %ebx - + /* * Set the base of the TEB selector to the base of the TEB for * this thread. @@ -89,7 +92,7 @@ xorl %eax, %eax movl KTHREAD_APCSTATE_PROCESS(%ebx), %edi testw $0xFFFF, KPROCESS_LDT_DESCRIPTOR0(%edi) - jz .L4 + jz 0f pushl KPROCESS_LDT_DESCRIPTOR1(%edi) pushl KPROCESS_LDT_DESCRIPTOR0(%edi) @@ -99,35 +102,46 @@ movl $LDT_SELECTOR, %eax -.L4: +0: lldtw %ax + movl 12(%ebp), %ebx + /* - * Load up the iomap offset for this thread in - * preparation for setting it below. + * FIXME: Save debugging state. */ - movl KPROCESS_IOPM_OFFSET(%edi), %eax /* - * FIXME: Save debugging state. + * Save floating point state if TS was unset. */ + movl %cr0, %eax + testl $X86_CR0_TS, %eax + jnz 1f + movl KTHREAD_INITIAL_STACK(%ebx), %eax + fnsave -SIZEOF_FX_SAVE_AREA(%eax) + movb $NPX_STATE_VALID, KTHREAD_NPX_STATE(%ebx) +1: /* - * FIXME: Save floating point state. + * Load up the iomap offset for this thread in + * preparation for setting it below. */ + movl KPROCESS_IOPM_OFFSET(%edi), %eax + + /* + * Save the stack pointer in this processors TSS + */ + movl %fs:KPCR_TSS, %esi + pushl KTSS_ESP0(%esi) /* * Switch stacks */ - movl 12(%ebp), %ebx movl %esp, KTHREAD_KERNEL_STACK(%ebx) movl 8(%ebp), %ebx movl KTHREAD_KERNEL_STACK(%ebx), %esp movl KTHREAD_STACK_LIMIT(%ebx), %edi - /* - * Set the stack pointer in this processors TSS - */ movl %fs:KPCR_TSS, %esi /* @@ -135,9 +149,6 @@ */ movw %ax, KTSS_IOMAPBASE(%esi) - movl KTHREAD_INITIAL_STACK(%ebx), %eax - movl %eax, KTSS_ESP0(%esi) - /* * Change the address space */ @@ -146,8 +157,16 @@ movl %eax, %cr3 /* - * FIXME: Restore floating point state + * Restore the stack pointer in this processors TSS + */ + popl KTSS_ESP0(%esi) + + /* + * Set TS in cr0 to catch FPU code and load the FPU state when needed */ + movl %cr0, %eax + orl $X86_CR0_TS, %eax + movl %eax, %cr0 /* * FIXME: Restore debugging state @@ -162,9 +181,9 @@ call _KeReleaseSpinLockFromDpcLevel@4 cmpl $0, _PiNrThreadsAwaitingReaping - je .L3 + je 4f call _PiWakeupReaperThread@0 -.L3: +4: /* * Restore the saved register and exit @@ -175,3 +194,5 @@ popl %ebp ret +.endfunc + Index: ntoskrnl/ke/i386/tss.c =================================================================== RCS file: /CVS/ReactOS/reactos/ntoskrnl/ke/i386/tss.c,v retrieving revision 1.9 diff -u -r1.9 tss.c --- ntoskrnl/ke/i386/tss.c 15 Aug 2004 16:39:05 -0000 1.9 +++ ntoskrnl/ke/i386/tss.c 27 Oct 2004 19:53:02 -0000 @@ -134,7 +134,7 @@ KeGetCurrentKPCR()->TSS = Tss; /* Initialize the boot TSS. */ - Tss->Esp0 = (ULONG)Ki386InitialStackArray[Id]; + Tss->Esp0 = (ULONG)Ki386InitialStackArray[Id] + MM_STACK_SIZE; /* FIXME: - sizeof(FX_SAVE_AREA)? */ Tss->Ss0 = KERNEL_DS; Tss->IoMapBase = 0xFFFF; /* No i/o bitmap */ Tss->IoBitmap[8192] = 0xFF; @@ -154,9 +154,9 @@ /* Initialize the TSS used for handling double faults. */ TrapTss->Eflags = 0; - TrapTss->Esp0 = ((ULONG)TrapStack + MM_STACK_SIZE); + TrapTss->Esp0 = ((ULONG)TrapStack + MM_STACK_SIZE); /* FIXME: - sizeof(FX_SAVE_AREA)? */ TrapTss->Ss0 = KERNEL_DS; - TrapTss->Esp = ((ULONG)TrapStack + MM_STACK_SIZE); + TrapTss->Esp = ((ULONG)TrapStack + MM_STACK_SIZE); /* FIXME: - sizeof(FX_SAVE_AREA)? */ TrapTss->Cs = KERNEL_CS; TrapTss->Eip = (ULONG)KiTrap8; TrapTss->Ss = KERNEL_DS; @@ -211,7 +211,7 @@ Ki386InitialStackArray[0] = (PVOID)&init_stack; /* Initialize the boot TSS. */ - KiBootTss.Esp0 = (ULONG)&init_stack_top; + KiBootTss.Esp0 = (ULONG)&init_stack_top - sizeof(FX_SAVE_AREA); KiBootTss.Ss0 = KERNEL_DS; // KiBootTss.IoMapBase = FIELD_OFFSET(KTSS, IoBitmap); KiBootTss.IoMapBase = 0xFFFF; /* No i/o bitmap */ @@ -232,9 +232,9 @@ /* Initialize the TSS used for handling double faults. */ KiBootTrapTss.Eflags = 0; - KiBootTrapTss.Esp0 = (ULONG)&trap_stack_top; + KiBootTrapTss.Esp0 = (ULONG)&trap_stack_top; /* FIXME: - sizeof(FX_SAVE_AREA)? */ KiBootTrapTss.Ss0 = KERNEL_DS; - KiBootTrapTss.Esp = (ULONG)&trap_stack_top; + KiBootTrapTss.Esp = (ULONG)&trap_stack_top; /* FIXME: - sizeof(FX_SAVE_AREA)? */ KiBootTrapTss.Cs = KERNEL_CS; KiBootTrapTss.Eip = (ULONG)KiTrap8; KiBootTrapTss.Ss = KERNEL_DS; Index: ntoskrnl/ke/i386/v86m_sup.S =================================================================== RCS file: /CVS/ReactOS/reactos/ntoskrnl/ke/i386/v86m_sup.S,v retrieving revision 1.11 diff -u -r1.11 v86m_sup.S --- ntoskrnl/ke/i386/v86m_sup.S 31 Oct 2004 19:46:10 -0000 1.11 +++ ntoskrnl/ke/i386/v86m_sup.S 3 Nov 2004 19:12:48 -0000 @@ -71,27 +71,24 @@ * Since we are going to fiddle with the stack pointer this must be * a critical section for this processor */ - - /* - * Save the old initial stack - */ - movl %fs:KPCR_CURRENT_THREAD, %esi - movl KTHREAD_INITIAL_STACK(%esi), %edi - pushl %edi - - /* - * We also need to set the stack in the kthread structure - */ - movl %esp, KTHREAD_INITIAL_STACK(%esi) + cli + + /* + * Save the exception handler stack from the TSS + */ + movl %fs:KPCR_TSS, %esi + pushl KTSS_ESP0(%esi) /* * The stack used for handling exceptions from v86 mode in this thread * will be the current stack adjusted so we don't overwrite the * existing stack frames */ - movl %fs:KPCR_TSS, %esi movl %esp, KTSS_ESP0(%esi) + /* Exit the critical section */ + sti + /* * Create the stack frame for an iret to v86 mode */ @@ -180,18 +177,10 @@ cli /* - * Restore the initial stack + * Restore the exception handler stack in the TSS */ - popl %eax movl %fs:KPCR_TSS, %esi - movl %eax, KTSS_ESP0(%esi) - - /* - * We also need to set the stack in the kthread structure - */ - movl %fs:KPCR_CURRENT_THREAD, %esi - movl KTHREAD_INITIAL_STACK(%esi), %edi - movl %eax, KTHREAD_INITIAL_STACK(%esi) + popl KTSS_ESP0(%esi) /* Exit the critical section */ sti @@ -207,3 +196,4 @@ movl %ebp, %esp popl %ebp ret + Index: ntoskrnl/ps/w32call.c =================================================================== RCS file: /CVS/ReactOS/reactos/ntoskrnl/ps/w32call.c,v retrieving revision 1.17 diff -u -r1.17 w32call.c --- ntoskrnl/ps/w32call.c 30 Oct 2004 23:48:57 -0000 1.17 +++ ntoskrnl/ps/w32call.c 3 Nov 2004 19:13:38 -0000 @@ -44,6 +44,8 @@ PNTSTATUS CallbackStatus; PKTRAP_FRAME SavedTrapFrame; PVOID SavedCallbackStack; + PVOID SavedExceptionStack; + UCHAR SavedNpxState; } NTW32CALL_SAVED_STATE, *PNTW32CALL_SAVED_STATE; typedef struct @@ -81,6 +83,8 @@ PNTW32CALL_SAVED_STATE State; PKTRAP_FRAME SavedTrapFrame; PVOID SavedCallbackStack; + PVOID SavedExceptionStack; + UCHAR SavedNpxState; Thread = PsGetCurrentThread(); if (Thread->Tcb.CallbackStack == NULL) @@ -102,6 +106,8 @@ StackLimit = State->SavedStackLimit; SavedTrapFrame = State->SavedTrapFrame; SavedCallbackStack = State->SavedCallbackStack; + SavedExceptionStack = State->SavedExceptionStack; + SavedNpxState = State->SavedNpxState; /* * Copy the callback status and the callback result to NtW32Call @@ -129,7 +135,9 @@ Thread->Tcb.StackLimit = StackLimit; Thread->Tcb.TrapFrame = SavedTrapFrame; Thread->Tcb.CallbackStack = SavedCallbackStack; - KeGetCurrentKPCR()->TSS->Esp0 = (ULONG)Thread->Tcb.InitialStack; + Thread->Tcb.NpxState = SavedNpxState; + KeGetCurrentKPCR()->TSS->Esp0 = (ULONG)SavedExceptionStack; + Ke386SetCr0(Ke386GetCr0() | X86_CR0_TS); /* set TS */ KeStackSwitchAndRet((PVOID)(OldStack + 1)); /* Should never return. */ @@ -282,9 +290,9 @@ } /* FIXME: Need to check whether we were interrupted from v86 mode. */ - memcpy((char*)NewStack + StackSize - sizeof(KTRAP_FRAME), Thread->Tcb.TrapFrame, - sizeof(KTRAP_FRAME) - (4 * sizeof(DWORD))); - NewFrame = (PKTRAP_FRAME)((char*)NewStack + StackSize - sizeof(KTRAP_FRAME)); + memcpy((char*)NewStack + StackSize - sizeof(KTRAP_FRAME) - sizeof(FX_SAVE_AREA), + Thread->Tcb.TrapFrame, sizeof(KTRAP_FRAME) - (4 * sizeof(DWORD))); + NewFrame = (PKTRAP_FRAME)((char*)NewStack + StackSize - sizeof(KTRAP_FRAME) - sizeof(FX_SAVE_AREA)); NewFrame->Esp -= (ArgumentLength + (4 * sizeof(ULONG))); NewFrame->Eip = (ULONG)LdrpGetSystemDllCallbackDispatcher(); UserEsp = (PULONG)NewFrame->Esp; @@ -304,10 +312,19 @@ SavedState.CallbackStatus = &CallbackStatus; SavedState.SavedTrapFrame = Thread->Tcb.TrapFrame; SavedState.SavedCallbackStack = Thread->Tcb.CallbackStack; + SavedState.SavedExceptionStack = (PVOID)KeGetCurrentKPCR()->TSS->Esp0; + SavedState.SavedNpxState = Thread->Tcb.NpxState; + if (Thread->Tcb.NpxState & NPX_STATE_DIRTY) /* thread has used FPU, save context */ + { + __asm__("fsave %0" : : "m"(*((char *)Thread->Tcb.InitialStack - sizeof(FX_SAVE_AREA)))); + SavedState.SavedNpxState = NPX_STATE_VALID; + Ke386SetCr0(Ke386GetCr0() | X86_CR0_TS); + } Thread->Tcb.InitialStack = Thread->Tcb.StackBase = (char*)NewStack + StackSize; - Thread->Tcb.StackLimit = (ULONG_PTR)NewStack; - Thread->Tcb.KernelStack = (char*)NewStack + StackSize - sizeof(KTRAP_FRAME); - KeGetCurrentKPCR()->TSS->Esp0 = (ULONG)Thread->Tcb.InitialStack; + Thread->Tcb.StackLimit = (ULONG)NewStack; + Thread->Tcb.KernelStack = (char*)NewStack + StackSize - sizeof(KTRAP_FRAME) - sizeof(FX_SAVE_AREA); + Thread->Tcb.NpxState = NPX_STATE_INVALID; + KeGetCurrentKPCR()->TSS->Esp0 = (ULONG)Thread->Tcb.InitialStack - sizeof(FX_SAVE_AREA); KePushAndStackSwitchAndSysRet((ULONG)&SavedState, Thread->Tcb.KernelStack); /*

2 2

Re: [MinGW-dvlpr] Problem with binutils-2.15.91-20040904-1.tar.gz
by Steven Edwards 08 Nov '04

08 Nov '04

--- "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

1 0

Re: Web site maintenance.
by Lucio Diaz 07 Nov '04

07 Nov '04

> > 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

4 3

Problem with binutils-2.15.91-20040904-1.tar.gz
by Steven Edwards 07 Nov '04

07 Nov '04

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

2 1

Rosapps broken in current CVS (CTM)
by Gge 07 Nov '04

07 Nov '04

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> -------------------------------------------------------

1 0

Crash on current CVS
by Steven Edwards 07 Nov '04

07 Nov '04

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

2 2

PATCH - Add support for Wine Regression Tests
by Steven Edwards 06 Nov '04

06 Nov '04

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

1 0

RE: [ros-dev] KMODE_EXCEPTION after pressing CancelbuttoninTaskbarSettings dia
by Theodor Willax 06 Nov '04

06 Nov '04

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.

1 0

RE: [ros-dev] KMODE_EXCEPTION after pressing Cancel buttoninTaskbarSettings dia
by Theodor Willax 06 Nov '04

06 Nov '04

>--- 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!

1 0

RE: [ros-dev] KMODE_EXCEPTION after pressing Cancel button inTaskbarSettings dia
by Theodor Willax 06 Nov '04

06 Nov '04

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!

3 2

Test stub generator
by art yerkes 06 Nov '04

06 Nov '04

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

1 0

Re: Re: [ros-dev] ReactOS setup CD-ROM crashes on old hardware.
by christoph＠apiviewer.de 06 Nov '04

06 Nov '04

> 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

1 0

ROS Build Failure with Explorer
by Michael B. Trausch 06 Nov '04

06 Nov '04

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

2 1

Why Ekush can't GPL
by Alex Ionescu 06 Nov '04

06 Nov '04

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

1 0

The ne2000 driver
by art yerkes 05 Nov '04

05 Nov '04

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

2 2

ros-cvs list question
by Hartmut Birr 04 Nov '04

04 Nov '04

Hi, it is possible, to add the version of a commited file? - Hartmut

1 0

Do you need this file?
by Jakob Eriksson 04 Nov '04

04 Nov '04

http://www.acc.umu.se/~bosse/ntifs.h

2 1

KMODE_EXCEPTION after pressing Cancel button in Taskbar Settings dialog
by Theodor Willax 04 Nov '04

04 Nov '04

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!

2 1

Re: [ros-dev] connect gdb to named pipe in ms virtual pc session
by Theodor Willax 04 Nov '04

04 Nov '04

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!

1 0

Using zones in NTOS
by Aliberti Emanuele 03 Nov '04

03 Nov '04

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

3 6

RE: [ros-dev] connect gdb to named pipe in ms virtual pc session
by Theodor Willax 03 Nov '04

03 Nov '04

>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!

2 1

address of a variable
by Hartmut Birr 03 Nov '04

03 Nov '04

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

2 4

connect gdb to named pipe in ms virtual pc session
by Theodor Willax 03 Nov '04

03 Nov '04

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!

1 0

Re: [ros-cvs] CVS Update: reactos
by Alex Ionescu 03 Nov '04

03 Nov '04

weiden(a)cvs.reactos.com wrote: > 1. reformatted the code so human beings can read it > > Best CVS log comment. Ever.

2 1

Re: [ros-cvs] CVS Update: reactos
by Filip Navara 02 Nov '04

02 Nov '04

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

2 1

FreeLoader now multiboot compliant
by Ge van Geldorp 01 Nov '04

01 Nov '04

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.

2 1

RE: [ros-cvs] CVS Update: reactos
by Hartmut Birr 01 Nov '04

01 Nov '04

Hi, it seems you have forgot to change the named pipe and mail slot driver. - 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: Sunday, October 31, 2004 3:40 PM > To: ros-cvs(a)reactos.com > Subject: [ros-cvs] CVS Update: reactos > > > CVSROOT: /CVS/ReactOS > Module name: reactos > Repository: reactos/include/ddk/ > Changes by: ion(a)mok.osexperts.com 04/10/31 15:40:11 > > Modified files: > reactos/include/ddk/: iotypes.h > > Log message: > Mailslot/Named Pipe structures. > > _______________________________________________ > Ros-cvs mailing list > Ros-cvs(a)reactos.com > http://reactos.com/mailman/listinfo/ros-cvs >

3 2

gcc question
by Hartmut Birr 01 Nov '04

01 Nov '04

Hi, it is possible, to tell gcc to use the fs register directly for addressing variables in the pcr? - Hartmut

2 1

Re: [ros-cvs] CVS Update: reactos
by James Tabor 31 Oct '04

31 Oct '04

Alex! Hi! ion(a)cvs.reactos.com wrote: > CVSROOT: /CVS/ReactOS > Module name: reactos > Repository: reactos/ntoskrnl/io/ > Changes by: ion(a)mok.osexperts.com 04/10/31 14:21:41 > > Modified files: > reactos/include/ddk/: iofuncs.h iotypes.h > reactos/ntoskrnl/io/: cleanup.c irp.c > > Log message: > Use proper IRP structure I'm get'en this, i386-mingw32-gcc -I./include -Wall -Werror -D_DISABLE_TIDENTS -D__3GB__ -D__NTOSKRNL__ -I. -D_SEH_NO_NATIVE_NLG -I../include -I../w32api/include -pipe -march=i486 -D_M_IX86 -c io/cleanup.c -o io/cleanup.o io/cleanup.c: In function `IoSecondStageCompletion': io/cleanup.c:195: error: `by' undeclared (first use in this function) io/cleanup.c:195: error: (Each undeclared identifier is reported only once io/cleanup.c:195: error: for each function it appears in.) io/cleanup.c:195: error: parse error before "DeviceObject" make: *** [io/cleanup.o] Error 1 Not sure what time this poped up, James

2 1

Guarded mutex
by Aliberti Emanuele 31 Oct '04

31 Oct '04

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

3 2

RE: [ros-cvs] CVS Update: reactos
by Hartmut Birr 31 Oct '04

31 Oct '04

Hi, this changes prevents from using debug print's in the very early boot phase, because the processor runs at HIGH_LEVEL and asserts in KfAcquireSpinLock. - Hartmut > -----Original Message----- > From: ros-cvs-bounces(a)reactos.com > [mailto:ros-cvs-bounces@reactos.com] On Behalf Of > navaraf(a)cvs.reactos.com > Sent: Saturday, October 30, 2004 6:30 AM > To: ros-cvs(a)reactos.com > Subject: [ros-cvs] CVS Update: reactos > > > CVSROOT: /CVS/ReactOS > Module name: reactos > Repository: reactos/hal/halx86/ > Changes by: navaraf(a)mok.osexperts.com 04/10/30 06:30:05 > > Modified files: > reactos/hal/halx86/: display.c > > Log message: > - Use KfAcquireSpinLock/KfReleaseSpinLock instead of > KiAcquireSpinLock/KiReleaseSpinLock. > > _______________________________________________ > Ros-cvs mailing list > Ros-cvs(a)reactos.com > http://reactos.com/mailman/listinfo/ros-cvs >

2 3

list administrator
by Hartmut Birr 30 Oct '04

30 Oct '04

Hi, who is is the administrator of our ros-dev mailing list? I would like to ask a question outside of the list. - Hartmut

2 1

Explorer make failure
by Enrico Bartky 30 Oct '04

30 Oct '04

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

2 1

ros on a multiprocessor system
by Hartmut Birr 30 Oct '04

30 Oct '04

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

2 2

FreeLdr: FsOpenVolume
by Filip Navara 30 Oct '04

30 Oct '04

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"));

2 1

Msi.dll
by James Tabor 30 Oct '04

30 Oct '04

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

3 4

Re: [ros-cvs] CVS Update: reactos
by Aliberti Emanuele 29 Oct '04

29 Oct '04

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

5 6

FPU saving + V86 problem - not sure how to solve it
by Anich Gregor 28 Oct '04

28 Oct '04

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

2 1

Re: [ros-cvs] CVS Update: reactos
by Alex Ionescu 27 Oct '04

27 Oct '04

navaraf(a)cvs.reactos.com wrote: >CVSROOT: /CVS/ReactOS >Module name: reactos >Repository: reactos/w32api/include/ddk/ >Changes by: navaraf(a)mok.osexperts.com 04/10/17 06:08:27 > >Modified files: > reactos/include/ddk/: exfuncs.h > reactos/ntoskrnl/ex/: interlck.c list.c > reactos/ntoskrnl/: ntoskrnl.def > reactos/w32api/include/ddk/: winddk.h > >Log message: > - Fix calling convention of ExInterlocked* functions. > >_______________________________________________ >Ros-cvs mailing list >Ros-cvs(a)reactos.com >http://reactos.com/mailman/listinfo/ros-cvs > > > Hi, Please reverse this change. ExInterlocked* functions are FASTCALL, as previously defined. Best regards, Alex Ionescu

2 4

Recommended dev Tools (was Re: INACCESSIBLE_BOOT_DEVICE)
by Enrico Bartky 25 Oct '04

25 Oct '04

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

2 2

About tagging memory blocks
by Aliberti Emanuele 25 Oct '04

25 Oct '04

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

1 0

PDNS_RECORDA
by Carlos Manuel Duclos Vergara 25 Oct '04

25 Oct '04

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

1 0

RE: [ros-cvs] CVS Update: reactos
by Casper Hornstrup 25 Oct '04

25 Oct '04

Hmm, generated files in CVS? Also kmregtests/, kmrtint/ and win32base/ is removed in HEAD. > -----Original Message----- > From: ros-cvs-bounces(a)reactos.com > [mailto:ros-cvs-bounces@reactos.com] On Behalf Of ion(a)cvs.reactos.com > Sent: 24. oktober 2004 18:37 > To: ros-cvs(a)reactos.com > Subject: [ros-cvs] CVS Update: reactos > > CVSROOT: /CVS/ReactOS > Module name: reactos > Repository: reactos/regtests/win32base/ > Changes by: ion(a)mok.osexperts.com 04/10/24 18:36:41 > > Added files: > reactos/regtests/: Tag: new_headers Makefile > reactos/regtests/kmregtests/: Tag: new_headers Makefile.tests > _regtests.c kmregtests.map > kmregtests.nostrip.sys > kmregtests.sym kmregtests.sys > reactos/regtests/kmrtint/: Tag: new_headers kmrtint.dll > kmrtint.map kmrtint.nostrip.dll > kmrtint.sym > reactos/regtests/regtests/: Tag: new_headers .cvsignore > Makefile > regtests.c regtests.def > reactos/regtests/shared/: Tag: new_headers .cvsignore Makefile > regtests.c regtests.h > reactos/regtests/win32base/: Tag: new_headers Makefile.tests > _regtests.c win32base.dll > win32base.map > win32base.nostrip.dll > win32base.sym > > Log message: > Final addition, regtests. (These additions are due due > cvs crashing when making the branch and not adding everythign > properly) > > _______________________________________________ > Ros-cvs mailing list > Ros-cvs(a)reactos.com > http://reactos.com/mailman/listinfo/ros-cvs >

2 1

RE: [ros-dev] RE: LinuxWorld Germany
by Theodor Willax 25 Oct '04

25 Oct '04

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!

1 0

OT: Filip is getting famous...
by Richard Campbell 25 Oct '04

25 Oct '04

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.

2 1

Re: [ros-dev] Re: [ros-cvs] CVS Update: reactos
by ea＠iol.it 25 Oct '04

25 Oct '04

> 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

1 0

Re: [ros-dev] Re: [ros-cvs] CVS Update: reactos
by ea＠iol.it 25 Oct '04

25 Oct '04

> 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

1 0

Packaging ros' files
by Sebastian Schmidt 25 Oct '04

25 Oct '04

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.

3 2

Re: [ros-cvs] CVS Update: reactos
by Alex Ionescu 24 Oct '04

24 Oct '04

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

1 0

RE: [ros-dev] LinuxWorld Germany
by Theodor Willax 24 Oct '04

24 Oct '04

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!

5 5

SCSI support?
by Bernd Blaauw 23 Oct '04

23 Oct '04

Is installing ReactOS on a SCSI controller/harddisk already possible? VMware has opensource win2000/xp drivers for the Buslogic controller they emulate http://www.vmware.com/download/open_sources.html http://www.vmware.com/download/downloadscsi.html so it might be interesting to add it to ReactOS, in order to test the 'install to SCSI' procedure. regards, Bernd Blaauw

2 2

RE: [ros-cvs] CVS Update: reactos
by Casper Hornstrup 23 Oct '04

23 Oct '04

Should they be public? > -----Original Message----- > From: ros-cvs-bounces(a)reactos.com > [mailto:ros-cvs-bounces@reactos.com] On Behalf Of > navaraf(a)cvs.reactos.com > Sent: 23. oktober 2004 01:11 > To: ros-cvs(a)reactos.com > Subject: [ros-cvs] CVS Update: reactos > > CVSROOT: /CVS/ReactOS > Module name: reactos > Repository: reactos/w32api/include/ddk/ > Changes by: navaraf(a)mok.osexperts.com 04/10/23 01:11:09 > > Modified files: > reactos/w32api/include/ddk/: winddk.h > > Log message: > - Add declarations for the PnP arbiter and resource > translation interfaces (ARBITER_REQUEST_SOURCE, > ARBITER_RESULT, ARBITER_ACTION, ARBITER_CONFLICT_INFO, > ARBITER_PARAMETERS, ARBITER_LIST_ENTRY, PARBITER_HANDLER, > ARBITER_INTERFACE, RESOURCE_TRANSLATION_DIRECTION, > PTRANSLATE_RESOURCE_HANDLER, > PTRANSLATE_RESOURCE_REQUIREMENTS_HANDLER, TRANSLATOR_INTERFACE). > > _______________________________________________ > Ros-cvs mailing list > Ros-cvs(a)reactos.com > http://reactos.com/mailman/listinfo/ros-cvs >

2 1

Loading failure of rtl8139.sys driver.
by Gge 22 Oct '04

22 Oct '04

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

8 25

Kernel-mode stack layout (FPU save area, trap frames, etc.)
by KJK::Hyperion 22 Oct '04

22 Oct '04

I've finally taken the time to write it all down: <http://mok.lvcm.com/cgi-bin/reactos/roswiki?KernelModeStackLayout> Let me know if you see any mistakes or omissions

3 9

RE: [ros-kernel] Pong
by Waldo Alvarez Cañizares 21 Oct '04

21 Oct '04

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

1 0

Re: [ros-cvs] CVS Update: reactos
by James Tabor 21 Oct '04

21 Oct '04

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

3 2

LinuxWorld Germany
by Steven Edwards 21 Oct '04

21 Oct '04

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

2 1

Change in tools/helper.mk
by art yerkes 21 Oct '04

21 Oct '04

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!

2 1

RE: [ros-dev] Change in tools/helper.mk
by PETREOLLE Sylvain 21 Oct '04

21 Oct '04

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. ----------------------------------------------------------------------------

1 0

atapi problems
by Ge van Geldorp 19 Oct '04

19 Oct '04

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.

1 0

Setupapi improvements
by eric.kohl＠t-online.de 19 Oct '04

19 Oct '04

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

3 5

regression tests and reactos/apps/tests
by Steven Edwards 19 Oct '04

19 Oct '04

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

3 2

Bug in freetype.dll?
by Hartmut Birr 19 Oct '04

19 Oct '04

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

2 4

Timers and Scheduler - "What I learned on my fall vacation"
by Steven Edwards 18 Oct '04

18 Oct '04

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

1 0

advpack.dll
by Steven Edwards 18 Oct '04

18 Oct '04

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

2 5

Re: [ros-dev] Loading failure of rtl8139.sys driver - Ed2 = same for ne2000.sys
by ea＠iol.it 18 Oct '04

18 Oct '04

> 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

1 0

NDIS 6
by Aliberti Emanuele 17 Oct '04

17 Oct '04

NDIS 6 to come in Longhorn. MS again changes how network is implemented in NT 5.1. http://www.ndis.com/news/longhornnetdevnews.htm

2 3

Re: [ros-cvs] CVS Update: reactos
by Alex Ionescu 17 Oct '04

17 Oct '04

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

1 0

ReactOS scripts (to make life easy) ;)
by Francisco TLF 17 Oct '04

17 Oct '04

Hi. I made some modifications on scripts to compile ReactOS (on linux, but I don't know if they works in some other plattform). You can check it at: http://telefrancisco.iespana.es/telefrancisco/linux/reactos/ Best regards. ______________________________________________________ Get Paid... With Your Free Email at http://www.zwallet.com/index.html?user=telefrancisco

1 0

Re: [ros-cvs] CVS Update: reactos
by Alex Ionescu 17 Oct '04

17 Oct '04

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

2 2

Crash in ExWorkerThreadEntryPoint
by Hartmut Birr 16 Oct '04

16 Oct '04

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

1 0

INACCESSIBLE_BOOT_DEVICE
by Enrico Bartky 16 Oct '04

16 Oct '04

Hello, I have attached the error, ....

1 0

INACCESSIBLE_BOOT_DEVICE
by Enrico Bartky 15 Oct '04

15 Oct '04

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

3 4

Memory Leak
by James Tabor 15 Oct '04

15 Oct '04

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

1 0

Compiler-independence for 64-bit integral constants
by Mike Nordell 14 Oct '04

14 Oct '04

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

9 9

Lockup and multi video driver load.
by James Tabor 13 Oct '04

13 Oct '04

Hi, Managed to get things running again. I'm getting this when compiling ros on ros in lib/msvcrt/stdlib; (create.c:36) <\Win32Pipes.00003775.00000001> = <\Win32Pipes.00003775.00000001>, than it just locked up and had to do a ctrl-c to break out and run make again. Now it is slowing down and you can count the char's type across the console screen. Process 4 thread 50 of csrss is eating kernel time. Process 1 thread 3 has the same or less than process 1 thread 0 (aka IdleProcessThread). Note. We need a standalone idle process (0) and thread (0) out side of SYSTEM. Anyway, it finished with out anymore errors or lockups. Next I noticed both vbemp.sys and vgamp.sys loaded. ModuleName Code Data Bss Paged Init LinkDate ------------------------------------------------------------------------------ ntoskrnl.exe 569344 8192 163840 0 49152 Wed Oct 13 19:53:14 2004 hal.dll 28672 4096 135168 0 0 Wed Oct 13 19:53:31 2004 pci.sys 16384 0 4096 0 0 Wed Oct 13 19:54:09 2004 scsiport.sys 20480 0 4096 0 0 Wed Oct 13 20:14:49 2004 atapi.sys 20480 0 4096 0 0 Wed Oct 13 20:14:42 2004 class2.sys 16384 0 0 0 0 Wed Oct 13 20:14:44 2004 disk.sys 12288 0 0 0 0 Wed Oct 13 20:14:45 2004 vfatfs.sys 57344 4096 4096 0 0 Wed Oct 13 20:13:55 2004 bootvid.sys 8192 4096 4096 0 0 Wed Oct 13 20:13:25 2004 ndis.sys 28672 4096 4096 0 0 Wed Oct 13 20:14:16 2004 floppy.sys 20480 0 20480 0 0 Wed Oct 13 20:14:48 2004 cdrom.sys 8192 0 0 0 0 Wed Oct 13 20:14:43 2004 fs_rec.sys 8192 0 0 0 0 Wed Oct 13 20:13:37 2004 beep.sys 4096 0 0 0 0 Wed Oct 13 20:13:22 2004 null.sys 4096 4096 0 0 0 Wed Oct 13 20:13:24 2004 serial.sys 4096 0 0 0 0 Wed Oct 13 20:13:24 2004 psaux.sys 12288 4096 4096 0 0 Wed Oct 13 20:13:28 2004 keyboard.sys 8192 4096 4096 0 0 Wed Oct 13 20:13:26 2004 mouclass.sys 4096 0 0 0 0 Wed Oct 13 20:13:27 2004 debugout.sys 4096 0 0 0 0 Wed Oct 13 20:13:23 2004 blue.sys 8192 0 0 0 0 Wed Oct 13 20:13:22 2004 videoprt.sys 16384 0 4096 0 0 Wed Oct 13 20:15:05 2004 vbemp.sys 8192 0 0 0 0 Wed Oct 13 20:14:59 2004 vgamp.sys 4096 4096 4096 0 0 Wed Oct 13 20:14:58 2004 msfs.sys 8192 0 0 0 0 Wed Oct 13 20:13:39 2004 npfs.sys 12288 0 0 0 0 Wed Oct 13 20:13:42 2004 kmregtests.sys 8192 0 4096 0 0 Wed Oct 13 19:53:19 2004 freetype.dll 417792 4096 0 0 0 Wed Oct 13 19:58:51 2004 win32k.sys 413696 8192 28672 0 0 Wed Oct 13 20:12:30 2004 kbdus.dll 4096 4096 4096 0 0 Wed Oct 13 20:10:01 2004 tcpip.sys 147456 4096 8192 0 0 Wed Oct 13 20:14:34 2004 afd.sys 40960 4096 0 0 0 Wed Oct 13 20:14:09 2004 framebuf.DLL 8192 4096 0 0 0 Wed Oct 13 20:14:57 2004 ------------------------------------------------------------------------------ Total 1953792 69632 405504 0 49152 FYI, James

1 0

Yet another build failure...
by Richard Campbell 13 Oct '04

13 Oct '04

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.

3 3

Re: [ros-cvs] CVS Update: reactos
by Alex Ionescu 13 Oct '04

13 Oct '04

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 > > >

1 0

Missing debug symbols
by WaxDragon 12 Oct '04

12 Oct '04

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.

2 1

Save FPU on task switch/SSE support
by Gregor Anich 12 Oct '04

12 Oct '04

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

5 12

2GB Boundary
by Alex Ionescu 11 Oct '04

11 Oct '04

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

8 13

Diffs from cvsspam
by David Kredba 10 Oct '04

10 Oct '04

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

5 4

RE: [ros-dev] Re: [ros-cvs] CVS Update: reactos
by PETREOLLE Sylvain 09 Oct '04

09 Oct '04

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. ----------------------------------------------------------------------------

1 0

Re: [ros-cvs] CVS Update: reactos
by James Tabor 09 Oct '04

09 Oct '04

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

1 1

CVS Build Dead
by Alex Ionescu 08 Oct '04

08 Oct '04

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

7 12

Re: [ros-cvs] CVS Update: reactos tcpip
by James Tabor 08 Oct '04

08 Oct '04

Hi, arty(a)cvs.reactos.com wrote: > CVSROOT: /CVS/ReactOS > Module name: reactos > Repository: reactos/drivers/net/tcpip/tcpip/ > Changes by: arty(a)mok.osexperts.com 04/10/07 08:04:45 > > Modified files: > reactos/drivers/lib/ip/: makefile > reactos/drivers/lib/ip/network/: ip.c neighbor.c > reactos/drivers/net/tcpip/include/: ip.h > reactos/drivers/net/tcpip/tcpip/: main.c > > Log message: > some formatting and prototype changes > memtrack on > moved timer dpc out of libip > added work item for ip timer callback to work at passive level > i386-mingw32-gcc -Wl,--base-file,base.tmp \ -Wl,--entry,_DriverEntry@8 \ -nostartfiles -nostdlib \ -o junk.tmp \ ./tcpip.coff tcpip/buffer.o tcpip/dispatch.o tcpip/fileobjs.o tcpip/irp.o tcpip/main.o tcpip/pool.o tcpip/info.o tcpip/ninfo.o tcpip/tinfo.o tcpip/iinfo.o datalink/lan.o datalink/loopback.o tests/_rtstub.o tests/regtests.a ../../../dk/nkm/lib/../../../dk/w32/lib/oskittcp.a ../../../dk/nkm/lib/../../../dk/w32/lib/ip.a ../../../dk/nkm/lib/../../../dk/w32/lib/rosrtl.a ../../../dk/nkm/lib/ndis.a ../../../dk/nkm/lib/ntoskrnl.a ../../../dk/nkm/lib/hal.a tcpip/buffer.o(.text+0x754):buffer.c: undefined reference to `TrackWithTag' tcpip/buffer.o(.text+0x7c0):buffer.c: undefined reference to `TrackWithTag' tcpip/buffer.o(.text+0x825):buffer.c: undefined reference to `TrackWithTag' tcpip/buffer.o(.text+0x8f4):buffer.c: undefined reference to `UntrackFL' tcpip/buffer.o(.text+0x918):buffer.c: undefined reference to `UntrackFL' tcpip/buffer.o(.text+0x947):buffer.c: undefined reference to `UntrackFL' tcpip/irp.o(.text+0x15):irp.c: undefined reference to `TrackWithTag' tcpip/irp.o(.text+0x3e):irp.c: undefined reference to `UntrackFL' tcpip/main.o(.text+0xaf1):main.c: undefined reference to `TrackingInit' tcpip/main.o(.text+0xafe):main.c: undefined reference to `TrackTag' tcpip/main.o(.text+0xb0e):main.c: undefined reference to `TrackTag' tcpip/main.o(.text+0xb1e):main.c: undefined reference to `TrackTag' tcpip/main.o(.text+0xb2e):main.c: undefined reference to `TrackTag' tcpip/pool.o(.text+0x7d):pool.c: undefined reference to `TrackWithTag' tcpip/pool.o(.text+0x9c):pool.c: undefined reference to `UntrackFL' datalink/lan.o(.text+0x1332):lan.c: undefined reference to `TrackWithTag' datalink/lan.o(.text+0x1351):lan.c: undefined reference to `UntrackFL' ../../../dk/nkm/lib/../../../dk/w32/lib/ip.a(ip.o)(.text+0x1207):ip.c: undefined reference to `TrackWithTag' ../../../dk/nkm/lib/../../../dk/w32/lib/ip.a(ip.o)(.text+0x1226):ip.c: undefined reference to `UntrackFL' make[1]: *** [tcpip.nostrip.sys] Error 1 Thanks, James

2 1

RE: [ros-dev] Re: [ros-cvs] CVS Update: reactos tcpip
by PETREOLLE Sylvain 08 Oct '04

08 Oct '04

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. ----------------------------------------------------------------------------

1 0

OpenOffice Rendering Help
by Steven Edwards 08 Oct '04

08 Oct '04

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

2 2

(gethostbyname and gethostname) needed for DHCP Server
by Steven Edwards 07 Oct '04

07 Oct '04

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

3 3

Warnings during shell32 build
by Ge van Geldorp 07 Oct '04

07 Oct '04

> 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.

1 0

Re: [ros-cvs] CVS Update: reactos
by eric.kohl＠t-online.de 06 Oct '04

06 Oct '04

<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

3 4

Sanos
by David Kredba 06 Oct '04

06 Oct '04

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

3 3

Overrun in lib/rtl/acl.c and possible fix
by art yerkes 06 Oct '04

06 Oct '04

>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!

2 1

Re: [ros-cvs] CVS Update: reactos
by Alex Ionescu 06 Oct '04

06 Oct '04

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 > > >

1 0

Annotations to dhcpd
by eric.kohl＠t-online.de 05 Oct '04

05 Oct '04

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

3 4

install path question
by Hartmut Birr 05 Oct '04

05 Oct '04

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

2 1

RE: [ros-cvs] CVS Update: reactos
by Hartmut Birr 04 Oct '04

04 Oct '04

Hi, please commit this changes again. The real problem was in loader.c. - Hartmut > -----Original Message----- > From: ros-cvs-bounces(a)reactos.com > [mailto:ros-cvs-bounces@reactos.com] On Behalf Of > chorns(a)cvs.reactos.com > Sent: Monday, October 04, 2004 3:17 AM > To: ros-cvs(a)reactos.com > Subject: [ros-cvs] CVS Update: reactos > > > CVSROOT: /CVS/ReactOS > Module name: reactos > Repository: reactos/ntoskrnl/ > Changes by: chorns(a)mok.osexperts.com 04/10/04 03:17:00 > > Modified files: > ./: ChangeLog > reactos/tools/: helper.mk > reactos/ntoskrnl/: Makefile > > Log message: > Revert: > 2004-10-02 Casper S. Hornstrup <chorns(a)users.sourceforge.net> > > * ntoskrnl/Makefile: Fix dependencies when PCH is enabled. > > 2004-10-02 Casper S. Hornstrup <chorns(a)users.sourceforge.net> > > * tools/helper.mk: Support for kernel TARGET_TYPE. > * ntoskrnl/Makefile: Simplified makefile. > > _______________________________________________ > Ros-cvs mailing list > Ros-cvs(a)reactos.com > http://reactos.com/mailman/listinfo/ros-cvs >

1 0

Build Errors
by James Tabor 04 Oct '04

04 Oct '04

Hello! make[2]: Entering directory `/home/ros/reactos/drivers/net/tcpip' i386-mingw32-gcc -Wl,--base-file,base.tmp \ -Wl,--entry,_DriverEntry@8 \ -nostartfiles -nostdlib \ -o junk.tmp \ ./tcpip.coff tcpip/buffer.o tcpip/dispatch.o tcpip/fileobjs.o tcpip/irp.o tcpip/main.o tcpip/pool.o tcpip/info.o tcpip/ninfo.o tcpip/tinfo.o tcpip/iinfo.o datalink/lan.o datalink/loopback.o tests/_rtstub.o tests/regtests.a ../../../dk/nkm/lib/../../../dk/w32/lib/oskittcp.a ../../../dk/nkm/lib/../../../dk/w32/lib/ip.a ../../../dk/nkm/lib/../../../dk/w32/lib/rosrtl.a ../../../dk/nkm/lib/ndis.a ../../../dk/nkm/lib/ntoskrnl.a ../../../dk/nkm/lib/hal.a ../../../dk/nkm/lib/../../../dk/w32/lib/ip.a(receive.o)(.text+0x188d): In function `ProcessFragment': /home/ros/reactos/drivers/lib/ip/network/receive.c:474: undefined reference to `DisplayIPPacket' make[2]: *** [tcpip.nostrip.sys] Error 1 make[2]: Leaving directory `/home/ros/reactos/drivers/net/tcpip' make[1]: *** [preall] Error 2 8^) James

2 1

Wow
by Richard Campbell 04 Oct '04

04 Oct '04

Diablo 2 now installs successfully on ROS...now to get it to work... ;)

1 0

What i've been working on
by Richard Campbell 04 Oct '04

04 Oct '04

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.

2 3

Re: [ros-cvs] CVS Update: reactos
by James Tabor 04 Oct '04

04 Oct '04

Hi, chorns(a)cvs.reactos.com wrote: > CVSROOT: /CVS/ReactOS > Module name: reactos > Repository: reactos/tools/ > Changes by: chorns(a)mok.osexperts.com 04/10/02 01:44:54 > > Modified files: > ./: ChangeLog > reactos/lib/gdiplus/tests/: .cvsignore Makefile > reactos/lib/gdiplus/tests/tests/: test-1.c > reactos/regtests/shared/: regtests.h > reactos/tools/: helper.mk regtests.c > Added files: > reactos/lib/gdiplus/tests/: stubs.tst > Removed files: > reactos/lib/gdiplus/tests/: passthrough.c > > Log message: > 2004-10-02 Casper S. Hornstrup <chorns(a)users.sourceforge.net> > > * lib/gdiplus/tests/.cvsignore: Ignore _hooks.c and _stubs.S. > * lib/gdiplus/tests/Makefile (TARGET_OBJECTS): Remove passthrough.o and > add _hooks.o and _stubs.o. > * lib/gdiplus/tests/tests/test-1.c: Test API hooking. > * regtests/shared/regtests.h: Add support for API hooking. > * tools/helper.mk: Generate stubs. > * tools/regtests.c: Add support for generating stubs and hooks. > * lib/gdiplus/tests/passthrough.c: Remove. > * lib/gdiplus/tests/stubs.tst: New file. > Build problem, i386-mingw32-gcc -I../include -DUNICODE -Wall -Werror -fno-builtin -D__USE_W32API -DWINVER=0x0600 -D_WIN32_WINNT=0x0501 -I../../../regtests/shared -I. -I../../../include -I../../../w32api/include -pipe -march=i486 -D_M_IX86 -g -c _hooks.c -o _hooks.o _hooks.c:7:17: missing terminating " character _hooks.c:8:1: missing terminating " character _hooks.c:9: error: parse error before '{' token _hooks.c:9:17: missing terminating " character _hooks.c:10:1: missing terminating " character _hooks.c:11:18: missing terminating " character _hooks.c:12:1: missing terminating " character _hooks.c:13: error: parse error before ';' token make[1]: *** [_hooks.o] Error 1 make[1]: Leaving directory `/home/ros/reactos/lib/gdiplus/tests' make: *** [tests/_regtests.c] Error 2 Thanks, James

2 5

Can some people rebuild/commit this patch
by Steven Edwards 03 Oct '04

03 Oct '04

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

1 0

Tree isn't compiling...
by Richard Campbell 03 Oct '04

03 Oct '04

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

1 0

Re: [ros-cvs] CVS Update: reactos
by Filip Navara 03 Oct '04

03 Oct '04

Ge van Geldorp wrote: >CVSROOT: /CVS/ReactOS >Module name: reactos >Repository: reactos/ntoskrnl/ps/ >Changes by: gvg(a)mok.osexperts.com 04/10/03 11:53:05 > >Modified files: > reactos/lib/rosrtl/thread/: exit.c > reactos/ntoskrnl/ps/: kill.c > >Log message: > Move final user stack cleanup to kernelmode > > This is actually wrong. See http://www.reactos.com/bugzilla/show_bug.cgi?id=36. Regards, Filip

1 0

RE: [ros-cvs] CVS Update: reactos
by Hartmut Birr 03 Oct '04

03 Oct '04

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 >

4 11

`TebBlock' undeclared
by David Kredba 03 Oct '04

03 Oct '04

Are you someone getting this ? Thanks, David mingw32-gcc -I../lib/kjs/include -I./include -I../include -D__NTOSKRNL__ -g -Wall -Werror -D_DISABLE_TIDENTS -D_SEH_NO_NATIVE_NLG -I../include -I../w32api/include -pipe -march=i686 -D_M_IX86 -D__NTOSKRNL__ -I. -D_SEH_NO_NATIVE_NLG -I../include -I../w32api/include -pipe -march=i686 -D_M_IX86 -g -D__NTOSKRNL__ -I. -D_SEH_NO_NATIVE_NLG -I../include -I../w32api/include -pipe -march=i686 -D_M_IX86 -g-c mm/marea.c -o mm/marea.o mm/marea.c: In function `MmReleaseMemoryAreaIfDecommitted': mm/marea.c:670: error: `TebBlock' undeclared (first use in this function) mm/marea.c:670: error: (Each undeclared identifier is reported only once mm/marea.c:670: error: for each function it appears in.) make[1]: *** [mm/marea.o] Error 1 make[1]: Leaving directory `/home/dave2/ros/reactos/ntoskrnl' make: *** [ntoskrnl] Error 2 -- David Kredba <kredba at ibot.cas.cz> GPG: ID 1024D/5B6B02DE Fingerprint: F0B3312596BEDCF91DFB 0699E06AACD75B6B02DE

2 4

build system problem
by Hartmut Birr 03 Oct '04

03 Oct '04

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

2 1

ROS and microsoft kernel debugger
by Jonathan Wilson 03 Oct '04

03 Oct '04

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?)

1 0

Build Failure
by Steven Edwards 03 Oct '04

03 Oct '04

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

2 1

EULAs == VALID
by Alex Ionescu 03 Oct '04

03 Oct '04

/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 /

2 1

Re: [ros-cvs] CVS Update: reactos
by Richard Campbell 02 Oct '04

02 Oct '04

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 > > >

1 0

ReactOS Inf handler tool
by Michael Biggins (Gamecentrix.co.uk) 02 Oct '04

02 Oct '04

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 :)

1 0

RE: [ros-cvs] CVS Update: reactos
by Casper Hornstrup 02 Oct '04

02 Oct '04

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.

5 8

ReactOS miniport failure.
by Devin Smith 01 Oct '04

01 Oct '04

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.inf http://home.pe.net/~dsmith/ros/hivedef.inf http://home.pe.net/~dsmith/ros/hiveinst.inf http://home.pe.net/~dsmith/ros/hivesft.inf http://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

2 3

Some input please...
by Richard Campbell 01 Oct '04

01 Oct '04

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.)

4 3

Re: [ros-cvs] Current CVS boot failure on real hardware
by Richard Campbell 01 Oct '04

01 Oct '04

It is a result of the winehq merge, which breaks explorer. James Tabor wrote: > Hi! > Between yesterdays (2300z time) and the current CVS (2300z time) I get > this, > > > > (environment.c:292) CreateEnvironmentBlock() called > DriverBase for \SystemRoot\System32\framebuf.DLL: de07a000 > (ntuser/desktop.c:808) RtlQueryRegistryValues failed for > PaintDesktopVersion: st > atus=c0000005 > FIXME: CopyImage doesn't support IMAGE_ICON correctly! > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find mxdMessage > (NTDLL:ldr/utils.c:2061) Relocating (77300000 -> b01000) > C:\ReactOS\system32\msa > cm32.dll > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find auxMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find mxdMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find midMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find modMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find widMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find wodMessage > (NTDLL:ldr/utils.c:2061) Relocating (76160000 -> 564000) > C:\ReactOS\system32\mid > imap.dll > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find auxMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find mxdMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find midMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find widMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find wodMessage > (windows/input.c:97)(GetAsyncKeyState) is unimplemented, please try > again later. > unknown Exception: 0x80070002 > Context: WinMain() > Location: utility/shellclasses.h:882 > Context Trace: > - WinMain() > - main > > (compobj.c:1561:CoCreateInstance) no classfactory created for CLSID > {4657278a-41 > 1b-11d2-839a-00c04fd918d0}, hres is 0x80040154 > (ntuser/hook.c:504) Not implemented: HookId 3 Global TRUE > unknown Exception: 0x80070002 > Context: WinMain() > Location: utility/shellclasses.h:882 > Context Trace: > - WinMain() > - main > > (KERNEL32:except/except.c:146) Unhandled exception > (KERNEL32:except/except.c:147) Address: > (KERNEL32:except/except.c:150) 401210 C:\ReactOS\explorer.exe > CS:EIP 1b:401210 > DS 23 ES 23 FS 3b GS 23 > EAX: ffffffff EBX: 00000000 ECX: 0078dfe6 > EDX: 007b1888 EBP: 0078defe ESI: 00000000 ESP: 0078dee6 > EDI: 0078f566 EFLAGS: 00010286 > (KERNEL32:except/except.c:153) Frames: > (KERNEL32:except/except.c:161) 77f2bbf3 > C:\ReactOS\system32\kernel32.dll > (KERNEL32:except/except.c:161) 77f2616a > C:\ReactOS\system32\kernel32.dll > (KERNEL32:except/except.c:161) 77fa6dd6 > C:\ReactOS\system32\ntdll.dll > (KERNEL32:except/except.c:161) 77fa6a59 > C:\ReactOS\system32\ntdll.dll > (KERNEL32:except/except.c:161) 77f8db84 > C:\ReactOS\system32\ntdll.dll > (objects/gdiobj.c:401) Can't delete hObj:0x0000001c, type:0x007f0000, > flag:0 > (objects/gdiobj.c:401) Can't delete hObj:0x00000020, type:0x007f0000, > flag:0 > (objects/gdiobj.c:401) Can't delete hObj:0x00000024, type:0x007f0000, > flag:0 > (ntuser/windc.c:739) [000000f4] GetDC() without ReleaseDC()! > > > Explorer and mouse, > > and,,,, on the blue screen, > > think you ought to know I'm feeling very depressed > > second reboot, > > So long, and thanks for all the fish > > > LOL! WTH is this! Oh! Funny little computer box, I should pick you up > and throw you > through my window! > > > 8^) > James > > _______________________________________________ > Ros-cvs mailing list > Ros-cvs(a)reactos.com > http://reactos.com/mailman/listinfo/ros-cvs >

7 11

RE: [ros-cvs] CVS Update: reactos
by Colin Burn 30 Sep '04

30 Sep '04

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

2 1

FAT Patent Rejected
by vldpodun＠pop.videotron.ca 30 Sep '04

30 Sep '04

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/ .

4 3

Re: [ros-cvs] Current CVS boot failure on real hardware
by Alex Ionescu 30 Sep '04

30 Sep '04

James, This is due to the Explorer breakage. GvG posted a patch to WineHQ which should fix it. Those quotes are the shutdown quotes (not BSODs). Best regards, Alex Ionescu James Tabor wrote: > Hi! > Between yesterdays (2300z time) and the current CVS (2300z time) I get > this, > > > > (environment.c:292) CreateEnvironmentBlock() called > DriverBase for \SystemRoot\System32\framebuf.DLL: de07a000 > (ntuser/desktop.c:808) RtlQueryRegistryValues failed for > PaintDesktopVersion: st > atus=c0000005 > FIXME: CopyImage doesn't support IMAGE_ICON correctly! > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find mxdMessage > (NTDLL:ldr/utils.c:2061) Relocating (77300000 -> b01000) > C:\ReactOS\system32\msa > cm32.dll > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find auxMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find mxdMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find midMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find modMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find widMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find wodMessage > (NTDLL:ldr/utils.c:2061) Relocating (76160000 -> 564000) > C:\ReactOS\system32\mid > imap.dll > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find auxMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find mxdMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find midMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find widMessage > (NTDLL:ldr/utils.c:1205) LdrGetExportByName(): failed to find wodMessage > (windows/input.c:97)(GetAsyncKeyState) is unimplemented, please try > again later. > unknown Exception: 0x80070002 > Context: WinMain() > Location: utility/shellclasses.h:882 > Context Trace: > - WinMain() > - main > > (compobj.c:1561:CoCreateInstance) no classfactory created for CLSID > {4657278a-41 > 1b-11d2-839a-00c04fd918d0}, hres is 0x80040154 > (ntuser/hook.c:504) Not implemented: HookId 3 Global TRUE > unknown Exception: 0x80070002 > Context: WinMain() > Location: utility/shellclasses.h:882 > Context Trace: > - WinMain() > - main > > (KERNEL32:except/except.c:146) Unhandled exception > (KERNEL32:except/except.c:147) Address: > (KERNEL32:except/except.c:150) 401210 C:\ReactOS\explorer.exe > CS:EIP 1b:401210 > DS 23 ES 23 FS 3b GS 23 > EAX: ffffffff EBX: 00000000 ECX: 0078dfe6 > EDX: 007b1888 EBP: 0078defe ESI: 00000000 ESP: 0078dee6 > EDI: 0078f566 EFLAGS: 00010286 > (KERNEL32:except/except.c:153) Frames: > (KERNEL32:except/except.c:161) 77f2bbf3 > C:\ReactOS\system32\kernel32.dll > (KERNEL32:except/except.c:161) 77f2616a > C:\ReactOS\system32\kernel32.dll > (KERNEL32:except/except.c:161) 77fa6dd6 > C:\ReactOS\system32\ntdll.dll > (KERNEL32:except/except.c:161) 77fa6a59 > C:\ReactOS\system32\ntdll.dll > (KERNEL32:except/except.c:161) 77f8db84 > C:\ReactOS\system32\ntdll.dll > (objects/gdiobj.c:401) Can't delete hObj:0x0000001c, type:0x007f0000, > flag:0 > (objects/gdiobj.c:401) Can't delete hObj:0x00000020, type:0x007f0000, > flag:0 > (objects/gdiobj.c:401) Can't delete hObj:0x00000024, type:0x007f0000, > flag:0 > (ntuser/windc.c:739) [000000f4] GetDC() without ReleaseDC()! > > > Explorer and mouse, > > and,,,, on the blue screen, > > think you ought to know I'm feeling very depressed > > second reboot, > > So long, and thanks for all the fish > > > LOL! WTH is this! Oh! Funny little computer box, I should pick you up > and throw you > through my window! > > > 8^) > James > > _______________________________________________ > Ros-cvs mailing list > Ros-cvs(a)reactos.com > http://reactos.com/mailman/listinfo/ros-cvs >

1 0

Re: [ros-cvs] CVS Update: reactos
by Richard Campbell 30 Sep '04

30 Sep '04

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 > > >

3 2

User Login, etc.
by Richard Campbell 30 Sep '04

30 Sep '04

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

2 1

Wizard Edit box Bug
by Alex Ionescu 30 Sep '04

30 Sep '04

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

1 0

Re: [ros-cvs] CVS Update: reactos
by eric.kohl＠t-online.de 30 Sep '04

30 Sep '04

"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

4 5

MmMapViewOfSection compile error.
by James Tabor 29 Sep '04

29 Sep '04

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

2 2

Page protection ldr change breaks VMware SVGA driver
by Ge van Geldorp 29 Sep '04

29 Sep '04

> 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.

3 6

ASSERT_IRQL and unrelated mm/mdl.c
by art yerkes 29 Sep '04

29 Sep '04

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!

3 4

ReactOS and Cygwin
by WaxDragon 29 Sep '04

29 Sep '04

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.

1 0

RE: [ros-dev] RE: [ros-kernel] BootCD doesn't boot...
by Richard Campbell 28 Sep '04

28 Sep '04

(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.

4 7

RE: [ros-kernel] BootCD doesn't boot...
by Hartmut Birr 28 Sep '04

28 Sep '04

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. >

3 4

(no subject)
by Pattersonmpt＠aol.com 28 Sep '04

28 Sep '04

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,

1 0

userenv license: ekohl, chorns, weiden, kjk
by Steven Edwards 28 Sep '04

28 Sep '04

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

2 1

Problem looking up mangled names
by Steven Edwards 27 Sep '04

27 Sep '04

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

6 8

VMware driver regression
by Steven Edwards 27 Sep '04

27 Sep '04

Also it seems that using the VMware driver has regressed vs current CVS. DriverBase for \SystemRoot\system32\drivers\vmx_svga.sys: dccfa000 DriverBase for \SystemRoot\system32\drivers\VIDEOPRT.SYS: dcd1a000 KeBugCheckWithTf at ke/catch.c:164 Bug detected (code 1e param 0 0 0 0) KMODE_EXCEPTION_NOT_HANDLED Page Fault Exception: 14(3) Processor: 0 CS:EIP 8:dccfc451 <vmx_svga.sys: 2451> cr2 dccfcc60 cr3 2a4000 Proc: c03ea010 Pid: 1 <SYSTEM> Thrd: c03ead58 Tid: 1 DS 10 ES 10 FS 30 GS 10 EAX: 00000000 EBX: c0454334 ECX: 00000000 EDX: 00000000 EBP: c00aea08 ESI: dccfa4d0 ESP: c00ae8c8 EDI: 0000000b EFLAGS: 00210246 kESP c00ae8c8 kernel stack base c00ac000 Frames: <vmx_svga.sys: 1c0f> <VIDEOPRT.SYS: 2213> <VIDEOPRT.SYS: 10a5> <ntoskrnl.exe: 2c093> <ntoskrnl.exe: 34cef> <ntoskrnl.exe: 34d5e> <ntoskrnl.exe: 343c1> <ntoskrnl.exe: 343f7> <ntoskrnl.exe: 343f7> <ntoskrnl.exe: 3443d> <ntoskrnl.exe: 34dc4> <C0082A0B> _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com

1 0

Const Error
by James Tabor 26 Sep '04

26 Sep '04

Hi! i386-mingw32-gcc -D_WIN32_IE=0x0600 -D_WIN32_WINNT=0x0501 -I./include -DUNICODE -D_UNICODE -D__REACTOS__ -D__USE_W32API -D_HIDPI_ -D_HIDPI_NO_FUNCTION_MACROS_ -Wall -Werror -fno-builtin -I. -I../../include -I../../w32api/include -pipe -march=i486 -D_M_IX86 -g -c hid.c -o hid.o hid.c: In function `HidD_Hello': hid.c:374: warning: duplicate `const' make: *** [hid.o] Error 1 const PCHAR const HelloString = "Hello\n"; ^ | is that right? I'm back online! James

3 2

Memory Manager problem
by Ge van Geldorp 26 Sep '04

26 Sep '04

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.

1 0

Re: Ros-kernel Digest, Vol 12, Issue 36
by Lucio Diaz 26 Sep '04

26 Sep '04

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

4 3

Re: [ros-cvs] CVS Update: reactos
by eric.kohl＠t-online.de 26 Sep '04

26 Sep '04

"Hartmut Birr" <hbirr(a)cvs.reactos.com> wrote: > CVSROOT: /CVS/ReactOS > Module name: reactos > Repository: reactos/drivers/storage/atapi/ > Changes by: hbirr(a)mok.osexperts.com 04/09/26 02:14:21 > > Modified files: > reactos/drivers/storage/atapi/: atapi.c > > Log message: > - Reselected the drive (master/slave) after a soft reset. This fixes the bug on my machine. All drives are detected. Regards, Eric

1 0

Welcome to ros-dev!
by Jason Filby 26 Sep '04

26 Sep '04

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

1 0

(no subject)
by Hanken 26 Sep '04

26 Sep '04

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev