Ros-dev December 2004

ros-dev@reactos.org

62 participants
119 discussions

RE: [ros-dev] SYSCALL instruction
by Waldo Alvarez Cañizares 23 Dec '04

23 Dec '04

Hi Martin: Last time I saw it no I haven't checked in a while), but I guess my answer should be not yet since I have not seen any discussion about that on the list until now that you ask. If you want to be sure check ntdll (the interface is machine generated so you need to check the program that builds it, what I remember is that it generated an .asm, you can also check the asm after you build the system). Also the ROS build system needs sub architectures configurable to use this one since this instruction is PII+ hey I bet we all know we are missing a lot of great stuff only implemented in more recent processors, SYSCALL is only one of them. Another thing that could be done is to detect the CPU at some time during initialization and use one of two ntdll (on with SYSCALL an another without it). The question is: should an installed ReactOS resist a CPU downgrade? Probably yes but most of the times is just a waste. regards Waldo ________________________________ From: ros-dev-bounces(a)reactos.com on behalf of Maritn "E.T." Misuth Sent: Wed 12/22/2004 5:10 PM To: ReactOS Development List Subject: [ros-dev] SYSCALL instruction Does ReactOS use optimized SYSCALL instruction on modern processors when invoking kernel functions? _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev

3 2

The hanging after 2nd stage install bug
by art yerkes 23 Dec '04

23 Dec '04

This patch works around the 'hanging after 2nd stage install' bug but I don't really understand what's going on here. Basically, It looks like ProcessData is null on the very last call (the one that would seemingly flush the registry and reboot). If i comment the break, nothing breaks and reactos reboots as expected when i press the reboot button. -- 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 1

SYSCALL instruction
by Maritn "E.T." Misuth 23 Dec '04

23 Dec '04

Does ReactOS use optimized SYSCALL instruction on modern processors when invoking kernel functions?

2 1

more sharing with Wine?
by Gunnar Dalsnes 22 Dec '04

22 Dec '04

Hi, I'm tired of fixing bugs in code ported from wine <x> years ago. In most cases the bugs has already been fixed in the wine code we ripped from, but the ros variant is forked so much its impossible to inc. those fixes into ros, so the only choice is to rip the whole wine source over again, loosing any possible fixes/improvements we had made to the ros variant vs. the wine variant. Take for example the file lib\kernel32\misc\profile.c. This file is 99.9% unchanged from wine, and only includes and some prototypes needed changes. I want to move files like this into wine subdirs. like lib\kernel32\misc\wine\profile.c and generate an initial diff lib\kernel32\misc\wine\profile.diff with changes made to make it run on ros using the wine porting headers. It does not mean that this diff will contain ERR changed to DPRINT etc. Only the bare changes to make it compile. Moving files into wine dirs in off course not necesary, but it makes it clear that this file(s) are shared thus there are rules to follow when changing them. I have made scripts that updates our profile.c, using the profile.diff and any updated profile.c from wine, and i have made a script for generating patches that we send to wine. It all seems to work fine. HELP: where does the winehq2ros.patch files used in comctl32 etc. fit into this? The only problem is wines strange unicode strings, their FIXME, ERR etc. and indentation. I think its worth it if we can share more, but dunno if the majority agrees. From what i can see, much of kernel32 and ntdll can be shared this way, and probably much stuff in user32/gdi32 also. Regards Gunnar

8 12

Re: [ros-cvs] CVS Update: reactos
by Alex Ionescu 22 Dec '04

22 Dec '04

royce(a)cvs.reactos.com wrote: >CVSROOT: /CVS/ReactOS >Module name: reactos >Repository: reactos/ntoskrnl/mm/ >Changes by: royce(a)mok.osexperts.com 04/12/21 21:17:46 > >Modified files: > reactos/ntoskrnl/include/internal/: test.h > reactos/ntoskrnl/ke/i386/: exp.c > reactos/ntoskrnl/mm/: virtual.c > >Log message: > MiQueryVirtualMemory(): created because ZwQueryVirtualMemory() didn't work for me, added cases for memory area types that I needed to walk stack traces. > Stack traces now use MiQueryVirtualMemory to make sure they never step outside the allocated stack they started in ( this prevents page faults at high irql ) - for some reason this patch eliminates the NtW32Callback() crash everybody is seeing with GDI_DEBUG enabled, tho I don't understand why. > > > > Nice fix Royce. Keep it up! Best regards, Alex Ionescu

1 0

Crash in ppool
by Hartmut Birr 20 Dec '04

20 Dec '04

Hi, I've problems with the paged pool routines and if the optimisation is enabled. Ros does crash. It seems that the line numbers for ppool.c are wrong. - Hartmut KeBugCheckWithTf at ke/catch.c:180 Bug detected (code 1e param 0 0 0 0) KMODE_EXCEPTION_NOT_HANDLED Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:80044769 <ntoskrnl.exe: 44769 (mm/ppool.c:292 (RFreeInit))> cr2 4 cr3 29f000 Proc: 805e2068 Pid: 1 <SYSTEM> Thrd: 805e2c40 Tid: 1 DS 10 ES 10 FS 30 GS 10 EAX: 00000004 EBX: 8cdd593c ECX: 00000000 EDX: 00000004 EBP: 800a9a80 ESI: 8cdd593c ESP: 800a9a04 EDI: 00000002 EFLAGS: 00210202 kESP 800a9a04 kernel stack base 800a7000 Frames: <ntoskrnl.exe: 44efc (mm/ppool.c:596 (RFreeSplit))> <ntoskrnl.exe: 4557d (mm/ppool.c:505 (ExAllocatePagedPoolWithTag))> <ntoskrnl.exe: 44019 (mm/pool.c:63 (EiAllocatePool))> <800779EB> <ntoskrnl.exe: b6fc (ke/main.c:863 (KiSystemStartup))> <8007849F> <ntoskrnl.exe: 1140

2 2

rcopy && gcc-3.4.2 on linux
by David Kredba 20 Dec '04

20 Dec '04

Hello, I got : Current date: 2004-12-20 ROS Version : 0.3-CVS (Build 20041220) rcopy.c: In function `copy_file': rcopy.c:90: error: storage size of `ut_buffer' isn't known rcopy.c:132: warning: implicit declaration of function `utime' rcopy.c:90: warning: unused variable `ut_buffer' make[1]: *** [rcopy] Error 1 make: *** [tools] Error 2 Regards, David

2 2

Version info
by Ge van Geldorp 20 Dec '04

20 Dec '04

After reading a question on the forum, I decided to find out exactly what is keeping Visual Basic programs from running and see if it's easy to fix. It turns out that about the first thing that the VB runtime (msvbvm60.dll) does is check the version number of the OS. At the moment we return: dwMajorVersion = 4 dwMinorVersion = 0 dwBuildNumber = 0 dwPlatformId = 2 szCSDVersion = "ReactOS 0.2.5-CVS (Build 20041216)" wServicePackMajor = 6 wServicePackMinor = 0 wSuiteMask = 0 wProductType = 0 The VB runtime wants at least NT4/SP3. The checks that currently fail are dwBuildNumber (needs at least 1381) and the check for the service pack. It expects the szCSDVersion field to be "Service Pack x" and extracts the service pack number from that. (Good thing btw that there are not more than 10 service packs for NT4...). Anyway, dwBuildNumber will have to be increased to 1381, that's no problem. But the szCSDVersion is currently the only way for usermode programs to get the ReactOS version. I know it's used by e.g. cmd.exe to display the version number. So, I don't think we have much choice, szCSDVersion will have to be set to "Service Pack 6". Question is how to make the ReactOS version string available. I've been thinking about adding it after the "Service Pack 6" string (so the sp6 string is terminated with a nul byte, following the nul byte is the ReactOS version string). Another option would be to store it in the registry, but that would mean that it could get out of sync with the version info in the kernel. So, I'd like to store it as second string in szCSDVersion. Any objections to that? Gé van Geldorp.

9 10

Re: LinuxWorld Boston 2005 .org Pavilion
by Steven Edwards 20 Dec '04

20 Dec '04

It will be faxed to you in 30. --- Debbie_Camerato(a)idg.com wrote: > Right now I have only have 2 spaces left....and it is first come, first > served, so I would send in your contract asap! __________________________________ Do you Yahoo!? Send a seasonal email greeting and help others. Do good. http://celebrity.mail.yahoo.com

1 0

RE: [ros-cvs] CVS Update: reactos
by Ge van Geldorp 20 Dec '04

20 Dec '04

> From: greatlrd(a)cvs.reactos.com > > Added files: > reactos/lib/dxdigan/: Makefile.in Makefile.ros-template > container.c dxdiag_main.c > dxdiag_private.h > dxdiagn.spec makefile provider.c regsvr.c > version.rc I'm afraid you're mixing up "dxdiagn" (correct name) with "dxdigan" in quite a few places. Could you make everything "dxdiagn" please? Gé van Geldorp.

2 1

← Newer
1
2
3
4
5
6
7
...
12
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev December 2004