Ros-dev May 2007

ros-dev@reactos.org

16 participants
28 discussions

Re: [ros-dev] QEMU support broken!!!
by Aleksey Bragin 10 May '07

10 May '07

Hello, the problem was introduced in 26666 and successfuly fixed in 26668 (read commit logs for more details). WBR, Aleksey Bragin. On May 10, 2007, at 4:47 PM, carlo.bramix wrote: > The last SVN builds don't run under qemu. > The last working image is livecd-26665-rel.iso > It looks like something wrong has been changed in the last 24 hours. > > Sincerely, > > Carlo Bramini. >

1 0

Getting act together
by CK Raju 05 May '07

05 May '07

Wouldn't it be better if we got our act together from like minded groups. Crystalxp.net group's offering of Bricopacks http://www.crystalxp.net/bricopack/en.htm which mimics the look and feel of Vista. Is ReactOS ready for such an integration ? Plus, can this auditing be distributed and shared ? I have set up a group of volunteer professionals to work on ReactOS. CK Raju ros-dev-request(a)reactos.org wrote: Welcome to the Ros-dev(a)reactos.org mailing list! --------------------------------- Office firewalls, cyber cafes, college labs, don't allow you to download CHAT? Here's a solution!

2 1

Re : DbgPrint() - DPRINT() - DPRINT1()
by Sylvain Petreolle 03 May '07

03 May '07

Hi, You actually have to define YDEBUG to see messages produced by DPRINT() If NDEBUG is defined (default), no message is shown. DPRINT1 is used in case of error/ fix needed. Kind regards, Sylvain Petreolle (aka Usurp) --- --- --- --- --- --- --- --- --- --- --- --- --- Run your favorite Windows apps with free ReactOS : http://www.reactos.org Listen to non-DRMised Music: http://www.jamendo.com ----- Message d'origine ---- De : "breakoutbox(a)web.de" <breakoutbox(a)web.de> À : Ros-dev(a)reactos.org Envoyé le : Jeudi, 19 Avril 2007, 16h21mn 55s Objet : [ros-dev] DbgPrint() - DPRINT() - DPRINT1() Hello, can please anybody explain me how You want DbgPrint() - DPRINT() - DPRINT1() to be used ? I found a lot of DPRINT() _for_example_ in "win32/in32k/objects/dc.c" but it is not shown on serial debug (?) (and also SOME ot these DPRINT1() .. ) 1) If I use DPRINT1() instead, it is always shown. If I use DbgPrint() instead, it is only shown when #DEBUG is defined in the file + in *.rbuild But what's the sense of DPRINT() then ? => 2) 2nd stage: on installing from BootCD I can see serial debug only when I select DEBUG from startup options. Is this DPRINT1() suppressed when I DON'T select DEBUG ? 3) Why is there not one DbgPrint() in "win32/in32k/objects/dc.c" (and also in other files in /DRIVER/ and /NTOSKRNL/ ..) ? I now have to change every serial debug output to be able to see anything .. ( if You don't explain me ... ;-) ) Best regards, Peter. _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

3 4

Re: [ros-dev] Bug into log10 function.
by carlo.bramix 03 May '07

03 May '07

Thank you for your reply. You are right, in theoury I should keep a copy of the sources at the same level of the ones into ReactOS's repository, and recompile a new version when something changed. Unfortunately, I cannot do it because my machine is an old Pentium MMX at 200MHz and 190 MB free into the harddisk. It is technically impossible for me to do that and my only chances are limited to the usage of a live CD or a QEMU session with a precompiled image. However, I'm happy that this small issue had been already tracked and solved! Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Tue, 1 May 2007 01:04:12 +0200 Subject : Re: [ros-dev] Bug into log10 function. > This bug have already been fixed by me. > log time ago. some time after 0.3.1 was relase or under 0.3.1 release process. > plese use svn source code, and try make own build of reactos as well. the trunk > is changes so fast, the code in 0.3.1 is already outdated in many areas. > > > > Citerar "carlo\\.bramix" <carlo.bramix(a)libero.it>: > > > While I was doing the final tests with ReactOS Calc before releasing the new > > version, I discovered that it didn't work because a bug into log10 function. > > This happens because the two operands are swapped into: > > > > \ReactOS-0.3.1\lib\crt\math\i386\log10_asm.s > > > > I attached the patch. > > > > Sincerely, > > > > Carlo Bramini. > > > > > > > > > > ------------------------------------------------------ > > Leggi GRATIS le tue mail con il telefonino i-mode di Wind > > http://i-mode.wind.it/ > > > > > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

2 1

ReactOS 0.3.2- trunk feature-frozen!
by Aleksey Bragin 02 May '07

02 May '07

Hi, as I promised, it's time for a new release. But... After a quick analysis of the trunk, I found out following problems which block the release: 1. NPFS problem, leading to a non-working networking (and probably other problems related with PnP). 2. Regress of the VMWare's display driver support. 3. The command prompt doesn't work for some people, including me (see bug 2201). 4. Icons rendering problems (Ged said it could be hackfixed in a branch). Those 4 are quite important, and release is not going to happen if they are not fixed. !!I ATTENTION !! Dear ReactOS developers, having commit access! Those problems must be fixed as top priority, in trunk. We are not going to branch for a release and keep copying trunk commits into it, because those fundamental bugs must be fixed in trunk. So trunk is put into a frozen state now. Please commit *only* bugfixes, do not commit any new features, change something significantly without a reason, or any other kind of activity not aimed at fixing existing problems which prevent a scheduled release. Thank you for your understanding, WBR, Aleksey Bragin.

2 1

Notepad-Icon is from Windows Vista!
by theUser BL 01 May '07

01 May '07

Hi! Your actual ROS-Notepad Icons is absolutly the same like that on Windows-Vista. On March 2006 there was already something like that, there you used a WinXP-notepad-icon, what I sayd at http://www.reactos.org/pipermail/ros-dev/2006-March/007932.html The new icon, what you then choosed looks very like MS-Windows, but it wasn't a icon from Windows until WinXP. But now I have looked at Windows Vista (in a Virtual machine and on real hardware in an Internetcafé which I know) and there I see, that the ROS-notepad icon and the Windows-Vista Notepad icon are completely the same! But, existing at first the Vista icon or at first the ROS-icon??? What me wonder is, that the icon was in ROS before the first betas of Vista where out... And btw: For all the people who have still not seen Vista: It is the biggest crap I have ever seen. I hope ROS 1.0 looks more like WinXP then like Vista. - In Vista you can not run DOS-programs. But in C:\windows\system32 there are files like edit.com and edlin.exe. But if you want to run it, there comes a window: That there eixting a problem with this programs. If you want to continue or abort. If I choose contine, then Vista hangs up. - The german version of Windows have also the English-Filenames: C:\Program Files\ C:\User\ .. which you can easily see in the command-window (dos-box). but the Explorer shows for the user translated names like C:\Programme\ C:\Benutzer\ and there is a a possibility, if you are in such a directory to see in the address-field of the explorer the real directory name. But at first you see the wrong one. - The games like minesweeper wants D3D hardware-driver, to run fast enough. - the happy colors of XP don´t existing there. All is in black. Black here, black there. The only other look and feel is the look of Win2000. - The icons on the desktop are all very big, for me too big. In the explorer on the other side the icons are per default small, that you can´t see what a symbol it is ... 16x16 or so icons. - If you have a 64bit Windows you can not see, which programs are 32bit and whgich 64 bit. In the name it stand there if you run it. There stands in the "about"-window something like "I am a 64 bit window program". But you can also develop a 32bit window program, which says, that it is 64bit. You can not see, if it is right or not. With Linux - on the other side -, the command "file" do not show only information about the Linux-format files, if you have a 32bit or 64bit program, it shows also, if you have a 32bit or 64bit Windows *.exe file. Additional it says if the *.exe-file is completly of native-code (so, that WINE could run it for example), if it is completly .net-code (so that Mono could run it on Linux for example) or if it include native and .net code mixed like some developer do it with Visual C++.net / managed C++. There you can mix native and .net code and neither WINE nor Mono can run this files. The games of Vista are such files with mixed code. Windows XP is _much_ better then Windows Vista!! Greatings theuserbl _________________________________________________________________ Sie suchen E-Mails, Dokumente oder Fotos? Die neue MSN Suche Toolbar mit Windows-Desktopsuche liefert in sekundenschnelle Ergebnisse. Jetzt neu! http://desktop.msn.de/ Jetzt gratis downloaden!

4 3

Re: [ros-dev] [ros-diffs] [gedmurphy] 26616: quick hack to make sysdm.cpl open our standalone device manager it's a democracy : http://www.reactos.org/forum/viewtopic.php?t=3835
by Alex Ionescu 01 May '07

01 May '07

You don't run a software engineering project by user-based democracy. Doing that is called Microsoft. Listening to your developers and internal vision while ignoring users is called Apple. Which makes the more user-friendly product? Best regards, Alex Ionescu -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of gedmurphy(a)svn.reactos.org Sent: May-01-07 12:25 PM To: ros-diffs(a)reactos.org Subject: [ros-diffs] [gedmurphy] 26616: quick hack to make sysdm.cpl open our standalone device manager it's a democracy : http://www.reactos.org/forum/viewtopic.php?t=3835 Author: gedmurphy Date: Tue May 1 20:25:26 2007 New Revision: 26616 URL: http://svn.reactos.org/svn/reactos?rev=26616&view=rev Log: quick hack to make sysdm.cpl open our standalone device manager it's a democracy : http://www.reactos.org/forum/viewtopic.php?t=3835 Modified: trunk/reactos/dll/cpl/sysdm/hardware.c Modified: trunk/reactos/dll/cpl/sysdm/hardware.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/cpl/sysdm/hardware.c?r… ============================================================================== --- trunk/reactos/dll/cpl/sysdm/hardware.c (original) +++ trunk/reactos/dll/cpl/sysdm/hardware.c Tue May 1 20:25:26 2007 @@ -14,6 +14,10 @@ BOOL LaunchDeviceManager(HWND hWndParent) { +/* hack for ROS to start our devmgmt until we have mmc */ +#ifdef __REACTOS__ + return ((INT)ShellExecuteW(NULL, L"open", L"devmgmt.exe", NULL, NULL, SW_SHOWNORMAL) > 32); +#else HMODULE hDll; PDEVMGREXEC DevMgrExec; BOOL Ret; @@ -33,6 +37,7 @@ Ret = DevMgrExec(hWndParent, hApplet, NULL /* ??? */, SW_SHOW); FreeLibrary(hDll); return Ret; +#endif /* __REACTOS__ */ } /* Property page dialog callback */

1 0

Re: [ros-dev] [ros-diffs] [dgorbachev] 26608: - Fix infinite loop. - Add debug msg.
by Alex Ionescu 01 May '07

01 May '07

You CANNOT return from PSEH! You must use SEH_LEAVE or the newest SHE construct that KJK added (forgot what he called it, check commit logs). -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of dgorbachev(a)svn.reactos.org Sent: May-01-07 4:53 AM To: ros-diffs(a)reactos.org Subject: [ros-diffs] [dgorbachev] 26608: - Fix infinite loop. - Add debug msg. Author: dgorbachev Date: Tue May 1 12:52:59 2007 New Revision: 26608 URL: http://svn.reactos.org/svn/reactos?rev=26608&view=rev Log: - Fix infinite loop. - Add debug msg. Modified: trunk/reactos/ntoskrnl/ke/i386/exp.c Modified: trunk/reactos/ntoskrnl/ke/i386/exp.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/exp.c?rev… ============================================================================== --- trunk/reactos/ntoskrnl/ke/i386/exp.c (original) +++ trunk/reactos/ntoskrnl/ke/i386/exp.c Tue May 1 12:52:59 2007 @@ -980,7 +980,9 @@ /* Set EIP to the User-mode Dispatcher */ TrapFrame->Eip = (ULONG)KeUserExceptionDispatcher; - _SEH_LEAVE; + + /* Dispatch exception to user-mode */ + return; } _SEH_EXCEPT(KiCopyInformation) { @@ -1000,9 +1002,6 @@ } } _SEH_END; - - /* Dispatch exception to user-mode */ - return; } /* Try second chance */ @@ -1018,6 +1017,7 @@ } /* 3rd strike, kill the process */ + DPRINT1("Kill the process\n"); ZwTerminateProcess(NtCurrentProcess(), ExceptionRecord->ExceptionCode); KeBugCheckEx(KMODE_EXCEPTION_NOT_HANDLED, ExceptionRecord->ExceptionCode,

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