Few changes you might find important:
- WDK builder has been added to scheduler. All trunk revisions are from now on built on both gcc and wdk.
- Cameron-requested USB builder is added as well. This one, connected to usb-bringup-trunk branch, is triggered manually from web interface. All builds are stored on diablo, so team-members with ftp accounts on it can access the builds just as all other ones. Please contact me if one needs an account.
Enjoy
--
With best regards
Caemyr
A second RC for 0.3.14 has been posted here:
http://sourceforge.net/projects/reactos/files/ReactOS/0.3.14/0.3.14-RC2.iso…
The main purpose of this RC is to see whether the hack Cameron Gutman
provided works around the memory manager issue causing hangs while
copying mshtml.dll during installation. Due to problems with the
wallpapers, a livecd will not be built at this time.
Z98
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
No, the Apache License isn't compatible with GPLv2, but it's
compatible with GPLv3
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPKys0AAoJEOb7MMS0s1Vr6u0H/irIogS+rc59Q+8RUVS48OyA
6bPFeyGM//egEWmERvLOl4CBRe9DsPQiGhFzxOeo79khwA6lWhWD+bO5hOGuWpCZ
GaKD5Ejy5kXf3ksDBH39/taYRCJo5z84aKEujncvKBhWSMFEVKGOADVopV/X1v8y
bj9OrVJJzuUDZJw/uBkZFmbTLdGAPIAv/Z8+5qfsiUJnD/lWGN+9n+by/08shpG7
7fJW7OJu+z0j/VTxNwsP6cGlgLSOFONlMHrjBHLMd9wLqdN3FwnxOlkgwAch8lj+
XXVGcv5P1diubQt/Foy+clRYUWBL9xfbClBLU7+V+mdE6n3ssLYI7MZnbCR5LIw=
=4MHl
-----END PGP SIGNATURE-----
Hello,
we just had a monthly meeting in the beginning of January, so I don't
see much of a reason to do another one at our usual date (and there are
no urgent questions required for decision).
Next meeting is going to happen in the end of February as scheduled.
WBR,
Aleksey.
pschweitzer(a)svn.reactos.org wrote:
> touch boot/bootdata/packages/reactos.dff.in
We can't put this one-liner into the CMakeLists.txt file?
execute_process should do the job if there is no "touch" command in
CMake itself.
Your change makes RosBE depend on a very specific file in a very
specific path of the source tree (=> tree change only possible with an
updated RosBE). In addition, these hooks separate the build logic
between CMake and RosBE and pave the way for even more source tree
dependent changes in RosBE. I like to avoid this.
- Colin
zguo(a)svn.reactos.org wrote:
> Change version string to release header for rbuild. Next time we
> release, do this in the cmake file.
Don't forget the actual version number in the very same file ;-)
Apart from this, please also check the SVN log of
svn://svn.reactos.org/reactos/tags/ReactOS-0.3.13. I recall some regular
changes for each release, which haven't been documented on the Wiki
(e.g. RApps shortcut on the desktop).
- Colin
Hi,
a third release candidate of RosBE-Unix 2.0 is now available on
http://svn.reactos.org/RosBE-Temp/. Compared to second RC, it only comes
with changes to the installation script (letting you define more
precisely how you want to build it).
Once installed, it is the same RosBE that RC2.
Unless major issues are found in this RC3, this will be the last RC
before release.
Regards,
Pierre
0.3.14 has been branched and a test ISO built. The developers request
that testers test the "golden" applications to determine if there are
any regressions. Details can be found here:
http://www.reactos.org/wiki/Testing_Central
Hi,
with this mail, I propose we drop support for FireFox > 2 releases in
rapps.
The motivation is crystal clear: with their new release plan, they are
releasing too often, and they don't maintain old links nor they provide
a symbolic link to latest version. So, FireFox links in rapps are too
often dead. So, they require a constant attention we can't offer (we
have other cats to fry!).
So, let's drop these multiple versions from rapps, and let just our 2.0.
This will let users install a web browser and then install the browser
they like using it.
Anyone against this proposal? Otherwise, I'll drop all those links in a
week.
Regards,
Pierre
That reminds me of my attempt to fix this mess. I gave up, when almost
every change of a structure size broke boot.
Obviously there is code that relies on certain structure sizes,
independent from the actual structure definitions, but I didn't find
where there was.
Good luck ;-)
Am 17.01.2012 18:42, schrieb ion(a)svn.reactos.org:
> Author: ion
> Date: Tue Jan 17 17:42:47 2012
> New Revision: 54990
>
> URL: http://svn.reactos.org/svn/reactos?rev=54990&view=rev
> Log:
> Fix boot. The fact this fixes it should worry about the state of CSRSS...
...
> Modified: trunk/reactos/include/reactos/subsys/csrss/csrss.h
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/include/reactos/subsys/csr…
> ==============================================================================
> --- trunk/reactos/include/reactos/subsys/csrss/csrss.h [iso-8859-1] (original)
> +++ trunk/reactos/include/reactos/subsys/csrss/csrss.h [iso-8859-1] Tue Jan 17 17:42:47 2012
> @@ -51,6 +51,7 @@
>
> typedef struct
> {
> +#if 0
> //
> // NT-type structure (BASE_CREATEPROCESS_MSG)
> //
> @@ -65,6 +66,7 @@
> PVOID PebAddressNative;
> ULONG PebAddressWow64;
> USHORT ProcessorArchitecture;
> +#endif
> //
> // ReactOS Data
> //
>
>
>
Hello everybody.
You will find attached to this e-mail the minutes for the meeting of 2011.
A topic as also been opened on the ReactOS forum
:http://reactos.org/forum/viewtopic.php?f=2&t=10352
<http://reactos.org/forum/viewtopic.php?f=2&t=10352>
I'm deeply sorry for the delay.
Regards.
Jérôme
Hi,
a second release candidate of RosBE-Unix 2.0 is now available on
http://svn.reactos.org/RosBE-Temp/. Compared to first RC, it comes with
CMake 2.8.7 (with Jérôme's patches), and binutils 2.22 (patched as
well).
Please try this BE and report any issues you may encounter. This will
help us to fix everything for the CMake switch.
If you're still lost in the use of CMake, have a look to the following
page: http://www.reactos.org/wiki/CMake
To sum it up:
$ ./configure.sh
$ (cd output-i386-MinGW/host-tools; makex)
$ (cd reactos; makex)
Regards,
Pierre
Hi,
as the results of the trunk testing depict, there are no major
problems/regressions (compared to the previous release). Thus I propose
to branch the 0.3.14 release.
Any comments, motivated objections? If not, then branching will be done
on Monday, 18th of December 2011.
WBR,
Aleksey Bragin.
Hi all,
I'm trying to compiling the latest ReactOS on ubuntu. However, I met
some problems(I can build it on Windows successfully). Could you help
me to have a look? The following is what I did:
1. Get the latest cdoe from SVN, svn co
svn://svn.reactos.org/reactos/trunk/reactos/
2. Install MinGW64, sudo apt-get install gcc-ming-w64
3. modify Makefile, ROS_PREFIX = i686-w64-mingw32
4. compiling error is as below:
-------------------------------------------------------------------------------------------------------
marvin@marvin-VirtualBox:~/reactos/src/latest/reactos$ make
[CC] dll/win32/aclui/sidcache.c
dll/win32/aclui/sidcache.c: In function ‘LookupSidInformation’:
dll/win32/aclui/sidcache.c:216:11: error: variable ‘SidLength’ set but
not used [-Werror=unused-but-set-variable]
cc1: all warnings being treated as errors
make: *** [obj-i386/dll/win32/aclui/sidcache_aclui.o] Error 1
-------------------------------------------------------------------------------------------------------
My questions are:
1. Which version of MinGW on linux did you use?
2. How to control compiling program to build Rlease and Debug version?
Thanks.
Marvin
Forwarding this with Johannes' consent:
-------- Original Message --------
Subject: [ros-priv] Status of the usb-bringup Branch
Date: Sat, 07 Jan 2012 16:21:24 +0100
From: Johannes Anderwald <janderwald(a)reactos.org>
To: ReactOS developers private list <ros-priv(a)reactos.org>
Hi Folks!
For those who are interested in the status of the usb-bringup branch,
here is a short summary of the current state, implemented features and
required work to have it working in ReactOS.
=== USB Core Status ===
1. There are 2 USB specifications for the USB 1.1 standard. Devices
which are used in this standard are mice / keyboards etc
OHCI (Open Host Controller Interface Standard) - All transfers
types are implemented (bulk, iso, control, interrupt)
UHCI (Universal Host Controller Interface Standard) - Totaly
missing. Though it should be do-able to use ohci driver as a base and
use Haiku driver[2]
2. EHCI (Enhanced Host Controller Interface) - Implemented transfer
types: bulk & control. Interrupt & Isochronous transfers are not
implemented. Due to the missing transfer types, devices who utilize
those transfer types will not be available
3.) USBHUB - driver for managing port and hubs - Implementation state is
unknown - michel martin has more information on that
=== USB Mass Storage Support Status ===
USB Mass Storage is implemented in usbstor driver and is fully working.
Tested in WinXP + USBEHCI + USBSTOR. Mass storage support requires bulk
and control transfers, which are implemented in USBEHCI
=== HID Status ===
The HID framework is built on 5 drivers
1. HIDUSB - this is the interface driver for the USB bus. Currently
supported devices are mice. Basic keyboard support should also work
currently
2. HIDCLASS - this is the class driver for HIDUSB and others.
Functionality for mice & keyboard is implemented, though support for
sending output reports is not implemented
3. MOUHID - mouse function driver for usb hid standard - Fully
implemented and working
4. KBDHID - keyboard function driver for the hid standard - 90 %
implemented, needs KbdHid_InsertScanCodes implemented for keyboard scan
code dispatching to kbdclass and led status indicator support (which
requires sending output reports)
5. HIDPARSE - driver for parsing report descriptors - functionality
implemented for mice, keyboard support needs HidParser_TranslateUsage
fully implemented for modifier state (caps lock, num lock, scroll lock)
=== What works and not ===
1. Mouse support has been tested in WinXP with ReactOS USBOHCI + HIDUSB
+ HIDCLASS + MOUHID + HIDPARSE and is working. The USB + HID stack does
not work in ReactOS at the moment, appears to be a problem with win32k,
which only opens the first mice (\\Device\\PointerClass0) [...]
2. Basic Keyboard support need a 2/3 functions but probably suffer from
the same bugs which affect HID mice support
3. Usb Mass storage support - Needs mountmgr / partmgr driver
implemented. Will also need mountvol and other missing PnP stuff
============
As I will be working on my master thesis the next few months, I`ll have
no time to focus on the usb or any ReactOS related development. If
anybody wants to work on the usb branch, I`m very happy with it. Feel
free to change anything, or rewrite evrything :) I`ll available via my
reactos email address if any questions come up.
kind regards,
Johannes
Links:
[1] svn://svn.reactos.org/reactos/branches/usb-bringup
[2]
http://cgit.haiku-os.org/haiku/tree/src/add-ons/kernel/busses/usb/uhci.cpp
_______________________________________________
Ros-priv mailing list
Ros-priv(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-priv
On Jan 8, 2012, at 1:08 AM, cgutman(a)svn.reactos.org wrote:
> - Run "wlanconf -s <SSID>" to connect to an unencrypted wireless network
> - Run "wlanconf -s <SSID> -w <WEP key>" to connect to a WEP encrypted wireless network (WPA not supported)
>
"wlanconf -s" does a network scan and lists networks in range. "wlanconf -c <SSID>" connects to a network. Sorry for the mixup.
If anyone does get around to testing this, please report results to me.
Regards,
Cameron
Hi,
what's the point of this change? IMO it's just ugly when we start
casting from PVOID everywhere.
Timo
Am 04.01.2012 13:22, schrieb fireball(a)svn.reactos.org:
> Author: fireball
> Date: Wed Jan 4 12:22:38 2012
> New Revision: 54833
>
> URL: http://svn.reactos.org/svn/reactos?rev=54833&view=rev
> Log:
> [NTOS]
> - Cast to actually returned types not just PVOID.
>
> Modified:
> trunk/reactos/ntoskrnl/include/internal/lpc_x.h
>
> Modified: trunk/reactos/ntoskrnl/include/internal/lpc_x.h
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/include/internal/…
> ==============================================================================
> --- trunk/reactos/ntoskrnl/include/internal/lpc_x.h [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/include/internal/lpc_x.h [iso-8859-1] Wed Jan 4 12:22:38 2012
> @@ -103,7 +103,7 @@
>
> /* Allocate a message from the port zone while holding the lock */
> KeAcquireGuardedMutex(&LpcpLock);
> - Message = ExAllocateFromPagedLookasideList(&LpcpMessagesLookaside);
> + Message = (PLPCP_MESSAGE)ExAllocateFromPagedLookasideList(&LpcpMessagesLookaside);
> if (!Message)
>
Happy New Year to you all.
Holidays fade away and I celebrate by submitting this tool.
Patches are filed as Bugzilla #6802 (not a bug duh.. ;)
http://www.reactos.org/bugzilla/show_bug.cgi?id=6802
ComMon is a simple COM port monitor utility to capture debug strings.
It is meant to be used with com0com or a null modem cable.
Usage and technical descriptions are in the ReadMe file.
I currently build ComMon with VC6 and gcc (i.e RosBE).
I see no reason it should not build with any MSVS or MinGW as well.
Project files for MSVC6 and Code::Blocks, plus rbuild files, are included.
Any questions.. contact me by email or ask right here.
Best Regards
Love
Hi,
due to expressed concerns about 0.PI release, there is no need to hurry
and the release is being moved to January 2012.
Regarding the monthly meeting, last thursday of this month turns out to
be 29th of December, which obviously makes some people unable to attend.
Preliminary date for the next meeting is 5th of January, and it depends
on how many of our team could attend at that date.
WBR,
Aleksey Bragin.
Hey,
On 2011-12-31 15:33, jgardou(a)svn.reactos.org wrote:
> Author: jgardou
> Date: Sat Dec 31 14:33:35 2011
> New Revision: 54793
>
> URL: http://svn.reactos.org/svn/reactos?rev=54793&view=rev
> Log:
> [NEWINFLIB]
> - use _snwprintf instead of swprintf (MSVC is not compliant with standard here)
since _snwprintf seems unavailable on Unix, perhaps
-D_CRT_NON_CONFORMING_SWPRINTFS
would be an appropriate solution? That should cause VS2010 (2008 seems to have
the version without a length) to use the non-standard no-length version just
like GCC.
That [1] gets rid of the warnings for me.
Regards (and a happy new year :p),
Tom
[1] http://pastebin.com/4XU2SCXR
This revision has caused a strange issue with both testbots. At kernel32:console crash, when testbot restarts vm, the test suite seems to begin right from the start, instead of next kernel32 test group. It happens subsequently whenever testbot reaches console test and crashes, leading to an ugly loop.
--
With best regards
Caemyr
Piece of good news too..
FileZilla FTP Client 3.5.2 (latest) installs and runs with flying colors
by the looks of it.
Would suggest it's added to the Rapps list :D
(http://filezilla-project.org/download.php)
Best Regards
// Love
On 2011-12-10 19.00, ros-dev-request(a)reactos.org wrote:
> Send Ros-dev mailing list submissions to
> ros-dev(a)reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.reactos.org/mailman/listinfo/ros-dev
> or, via email, send a message with subject or body 'help' to
> ros-dev-request(a)reactos.org
>
> You can reach the person managing the list at
> ros-dev-owner(a)reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Invisible dialogs (Love Nystrom)
> 2. Re: Invisible dialogs (Giannis Adamopoulos)
> 3. Re: Invisible dialogs (James Tabor)
> 4. Re: Invisible dialogs (James Tabor)
> 5. Re: Missing RtlSetUnhandledExceptionFilter (Love Nystrom)
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
I did a brief comparison of wiki pages for 0.3.13 and 0.3.14 and found
out at least the following apps which worked in 0.3.13 but does not work
in 0.3.14 RC (aka trunk, we'll set exact revision soon):
AbiWord
Irfanview
Opera 9.64
Python - bug #5767
SMPlayer 0.6.9
VB5 Runtime
I will try to go through the list and see what are the problems.
Everyone is welcome to do the same and distribute the workforce on
fixing those issues.
Certainly, on the positive side, there are "green" fields in the new
test results which were previously "red" in 0.3.13, so user-visible
progress definitely exists, we just need to make sure it's continuously
going better and better, without steps backward.
WBR,
Aleksey Bragin.
Hi,
Thanks for the pointer.
I think other testers (devs too?) may find it useful, so it would be
convenient to put it in ROS codebase.
I'll file a patch with usage and technical description shortly.
Best Regards
// Love
On 2011-12-17 19.00, ros-dev-request(a)reactos.org wrote:
> Subject:
> Re: [ros-dev] COM Monitor
> From:
> caemyr(a)myopera.com
> Date:
> Fri, 16 Dec 2011 23:44:29 +0100
>
> To:
> "ReactOS Development List" <ros-dev(a)reactos.org>
>
>
> Hiya
>
> I think it depends what do you want to do with it. If you want it in ROS codebase (not necessarily in trunk, but still on svn) you should post a patch to bugzilla, with some info on how it works.
>
> Best regards
>
After installing boot screen does not show the image
debug.log
(ntoskrnl\kd\kdio.c:172)
---------------------------------------------------------------
(ntoskrnl\kd\kdio.c:173) ReactOS 0.3.13 (Build 20110828-rUNKNOWN)
(ntoskrnl\mm\mminit.c:243) 0x80000000 - 0x81000000 Boot Loaded Image
(ntoskrnl\mm\mminit.c:247) 0xB0000000 - 0xB0900000 PFN Database
(ntoskrnl\mm\mminit.c:251) 0xB0900000 - 0xB38B0000 ARM³ Non Paged Pool
(ntoskrnl\mm\mminit.c:255) 0xBC000000 - 0xBD000000 System View Space
(ntoskrnl\mm\mminit.c:259) 0xBD000000 - 0xC0000000 Session Space
(ntoskrnl\mm\mminit.c:262) 0xC0000000 - 0xC0300000 Page Tables
(ntoskrnl\mm\mminit.c:265) 0xC0300000 - 0xC0400000 Page Directories
(ntoskrnl\mm\mminit.c:268) 0xC0400000 - 0xC0800000 Hyperspace
(ntoskrnl\mm\mminit.c:272) 0xE1000000 - 0xF2400000 ARM³ Paged Pool
(ntoskrnl\mm\mminit.c:275) 0xF2400000 - 0xF7BE0000 System PTE Space
(ntoskrnl\mm\mminit.c:278) 0xF7BE0000 - 0xFFBE0000 Non Paged
Pool Expansion PTE Space
(hal\halx86\generic\legacy\bussupp.c:591) Your machine has a
PCI-to-PCI or CardBUS Bridge. PCI devices may fail!
(hal\halx86\generic\legacy\bussupp.c:620) Found parent bus (indicating
PCI Bridge). PCI devices may fail!
====== PCI BUS HARDWARE DETECTION =======
00:00.0 RAM memory [0500]: MCP78S [GeForce 8200] Memory Con
[10de:0754] (rev a2)
Subsystem: Unknown [1019:2646]
Flags: bus master, 66MHz, latency 0
00:01.0 ISA bridge [0601]: MCP78S [GeForce 8200] LPC Bridge
[10de:075c] (rev a2)
Subsystem: Unknown [1019:2646]
Flags: bus master, 66MHz, latency 0
I/O ports at 2f00 [size=256]
00:01.1 SMBus [0c05]: nVidia Corporation MCP78S [GeForce 8200] SMBus
[10de:0752] (rev a1)
Subsystem: Unknown [1019:2646]
Flags: 66MHz, latency 0, IRQ 10
I/O ports at 2900 [size=256]
I/O ports at 2d00 [size=256]
I/O ports at 2e00 [size=512]
Device is using IRQ 10! ISA Cards using that IRQ may fail!
00:01.2 RAM memory [0500]: MCP78S [GeForce 8200] Memory Con
[10de:0751] (rev a1)
Subsystem: Unknown [1019:2646]
Flags: 66MHz, latency 0
00:01.3 Co-processor [0b40]: MCP78S [GeForce 8200] Co-Process
[10de:0753] (rev a2)
Subsystem: Unknown [1019:2646]
Flags: bus master, 66MHz, latency 0, IRQ 11
Memory at f8e80000 (32-bit, non-prefetchable) [size=512K]
Device is using IRQ 11! ISA Cards using that IRQ may fail!
00:01.4 RAM memory [0500]: MCP78S [GeForce 8200] Memory Con
[10de:0568] (rev a1)
Subsystem: Unknown [1019:2646]
Flags: 66MHz, latency 0
00:02.0 USB Controller [0c03]: MCP78S [GeForce 8200] OHCI USB 1
[10de:077b] (rev a1)
Subsystem: Unknown [1019:2646]
Flags: bus master, 66MHz, latency 0, IRQ 15
Memory at f8e7f000 (32-bit, non-prefetchable) [size=4K]
Device is using IRQ 15! ISA Cards using that IRQ may fail!
Device is an OHCI (USB) PCI Expansion Card. Turn off Legacy USB in your BIOS!
00:02.1 USB Controller [0c03]: MCP78S [GeForce 8200] EHCI USB 2
[10de:077c] (rev a1)
Subsystem: Unknown [1019:2646]
Flags: bus master, 66MHz, latency 0, IRQ 10
Memory at f8e7ec00 (32-bit, non-prefetchable) [size=1K]
Device is using IRQ 10! ISA Cards using that IRQ may fail!
00:04.0 USB Controller [0c03]: MCP78S [GeForce 8200] OHCI USB 1
[10de:077d] (rev a1)
Subsystem: Unknown [1019:2646]
Flags: bus master, 66MHz, latency 0, IRQ 10
Memory at f8e7d000 (32-bit, non-prefetchable) [size=4K]
Device is using IRQ 10! ISA Cards using that IRQ may fail!
Device is an OHCI (USB) PCI Expansion Card. Turn off Legacy USB in your BIOS!
00:04.1 USB Controller [0c03]: MCP78S [GeForce 8200] EHCI USB 2
[10de:077e] (rev a1)
Subsystem: Unknown [1019:2646]
Flags: bus master, 66MHz, latency 0, IRQ 11
Memory at f8e7e800 (32-bit, non-prefetchable) [size=2K]
Device is using IRQ 11! ISA Cards using that IRQ may fail!
00:06.0 IDE interface [0101]: nVidia Corporation MCP78S [GeForce 8200]
IDE [10de:0759] (rev a1)
Subsystem: Unknown [1019:2646]
Flags: bus master, 66MHz, latency 0
I/O ports at ffa0 [size=32]
00:07.0 Audio device [0403]: MCP72XE/MCP72P/MCP78U/MCP78S Hig
[10de:0774] (rev a1)
Subsystem: Unknown [1019:2646]
Flags: bus master, 66MHz, latency 0, IRQ 15
Memory at f8e78000 (32-bit, non-prefetchable) [size=32K]
Device is using IRQ 15! ISA Cards using that IRQ may fail!
00:08.0 PCI bridge [0604]: MCP78S [GeForce 8200] PCI Bridge
[10de:075a] (rev a1)
Subsystem: GLoria L [0000:0000]
Flags: bus master, 66MHz, latency 0
Memory at 20010100 (32-bit, non-prefetchable) [size=256]
Memory at 228000f0 (32-bit, non-prefetchable) [size=8M]
Memory at 0000fff0 (32-bit, non-prefetchable) [size=256]
Memory at 0000fff0 (32-bit, non-prefetchable) [size=256]
00:09.0 SATA controller [0106]: MCP78S [GeForce 8200] AHCI Contr
[10de:0ad4] (rev a2)
Subsystem: Unknown [1019:2646]
Flags: bus master, 66MHz, latency 0, IRQ 05
I/O ports at b480 [size=128]
I/O ports at b400 [size=1K]
I/O ports at b080 [size=128]
I/O ports at b000 [size=4K]
I/O ports at ac00 [size=1K]
Memory at f8e76000 (32-bit, non-prefetchable) [size=8K]
Device is using IRQ 5! ISA Cards using that IRQ may fail!
00:0b.0 PCI bridge [0604]: MCP78S [GeForce 8200] PCI Expres
[10de:0569] (rev a1)
Subsystem: GLoria L [0000:0000]
Flags: bus master, latency 0
Memory at 00020200 (32-bit, non-prefetchable) [size=512]
I/O ports at 2000c1c0 [size=64]
Memory at f9f0f8f0 (32-bit, non-prefetchable) [size=2K]
I/O ports at cff1c600 [size=512]
00:10.0 PCI bridge [0604]: MCP78S [GeForce 8200] PCI Expres
[10de:0778] (rev a1)
Subsystem: GLoria L [0000:0000]
Flags: bus master, latency 0, IRQ 10
Memory at 00030300 (32-bit, non-prefetchable) [size=256]
I/O ports at 2000d1d0 [size=16]
Memory at fde0fa00 (32-bit, non-prefetchable) [size=512]
I/O ports at dff1d000 [size=4K]
00:12.0 PCI bridge [0604]: MCP78S [GeForce 8200] PCI Expres
[10de:075b] (rev a1)
Subsystem: GLoria L [0000:0000]
Flags: bus master, latency 0, IRQ 11
Memory at 00040400 (32-bit, non-prefetchable) [size=1K]
I/O ports at 01f0 [size=16]
Memory at 0000fff0 (32-bit, non-prefetchable) [size=256]
I/O ports at 1fff0 [size=16]
00:13.0 PCI bridge [0604]: MCP78S [GeForce 8200] PCI Bridge
[10de:077a] (rev a1)
Subsystem: GLoria L [0000:0000]
Flags: bus master, latency 0, IRQ 15
Memory at 00050500 (32-bit, non-prefetchable) [size=256]
I/O ports at 01f0 [size=16]
Memory at 0000fff0 (32-bit, non-prefetchable) [size=256]
I/O ports at 1fff0 [size=16]
00:14.0 PCI bridge [0604]: MCP78S [GeForce 8200] PCI Bridge
[10de:077a] (rev a1)
Subsystem: GLoria L [0000:0000]
Flags: bus master, latency 0, IRQ 07
Memory at 00060600 (32-bit, non-prefetchable) [size=512]
I/O ports at 2000e1e0 [size=32]
Memory at fdf0fdf0 (32-bit, non-prefetchable) [size=256]
I/O ports at f7f1f7f0 [size=16]
00:18.0 Host bridge [0600]: K10 [Opteron, Athlon64, Sempron]
[1022:1200] (rev 00)
Subsystem: GLoria L [0000:0000]
Flags: latency 0
00:18.1 Host bridge [0600]: K10 [Opteron, Athlon64, Sempron]
[1022:1201] (rev 00)
Subsystem: GLoria L [0000:0000]
Flags: latency 0
00:18.2 Host bridge [0600]: K10 [Opteron, Athlon64, Sempron]
[1022:1202] (rev 00)
Subsystem: GLoria L [0000:0000]
Flags: latency 0
00:18.3 Host bridge [0600]: K10 [Opteron, Athlon64, Sempron]
[1022:1203] (rev 00)
Subsystem: GLoria L [0000:0000]
Flags: latency 0
00:18.4 Host bridge [0600]: K10 [Opteron, Athlon64, Sempron]
[1022:1204] (rev 00)
Subsystem: GLoria L [0000:0000]
Flags: latency 0
02:00.0 VGA compatible controller [0300]: nVidia Corporation C77
[GeForce 8200] [10de:0849] (rev a2)
Subsystem: Unknown [1019:2646]
Flags: latency 0, IRQ 10
Memory at f9000000 (32-bit, non-prefetchable) [size=16M]
Memory at c8000000 (64-bit, prefetchable) [size=128M]
Memory at c6000000 (64-bit, prefetchable) [size=32M]
I/O ports at cc00 [size=1K]
Device is using IRQ 10! ISA Cards using that IRQ may fail!
03:00.0 VGA compatible controller [0300]: nVidia Corporation G92
[GeForce 9800 GT] [10de:0605] (rev a2)
Subsystem: GLoria L [0000:0000]
Flags: bus master, latency 0, IRQ 10
Memory at fc000000 (32-bit, non-prefetchable) [size=64M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at dc00 [size=1K]
Device is using IRQ 10! ISA Cards using that IRQ may fail!
06:00.0 Ethernet controller [0200]: RTL8111/8168B PCI Express Gigabi
[10ec:8168] (rev 02)
Subsystem: Unknown [1019:8111]
Flags: bus master, latency 0, IRQ 07
I/O ports at e800 [size=2K]
Memory at fdfff000 (64-bit, non-prefetchable) [size=4K]
Memory at f7ff0000 (64-bit, prefetchable) [size=64K]
Device is using IRQ 7! ISA Cards using that IRQ may fail!
====== PCI BUS DETECTION COMPLETE =======
PC Compatible Eisa/Isa HAL Detected
(ntoskrnl\io\iomgr\iorsrce.c:882) IoReportResourceUsage is halfplemented!
(ntoskrnl\io\iomgr\iorsrce.c:882) IoReportResourceUsage is halfplemented!
(hal\halx86\generic\legacy\bussupp.c:1149) Slot assignment for 5 on bus 0
(hal\halx86\generic\legacy\bus\pcibus.c:719) WARNING: PCI Slot
Resource Assignment is FOOBAR
(ntoskrnl\io\iomgr\driver.c:1540) '\Driver\BUSLOGIC' initialization
failed, status (0xc00000c0)
(ntoskrnl\io\iomgr\iorsrce.c:725) Failed opening given symbolic link!
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading:
\SystemRoot\System32\DRIVERS\pci.sys at F7A30000 with b pages
(ntoskrnl\io\pnpmgr\pnpmgr.c:183) Warning: PnP Start failed (Root\*PNP0A03\0001)
(ntoskrnl\io\pnpmgr\pnpmgr.c:183) Warning: PnP Start failed (Root\*PNP0A03\0000)
2011/12/17, ros-dev-request(a)reactos.org <ros-dev-request(a)reactos.org>:
> Send Ros-dev mailing list submissions to
> ros-dev(a)reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.reactos.org/mailman/listinfo/ros-dev
> or, via email, send a message with subject or body 'help' to
> ros-dev-request(a)reactos.org
>
> You can reach the person managing the list at
> ros-dev-owner(a)reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-dev digest..."
>
>
> Today's Topics:
>
> 1. Apps regressions in 0.3.14 vs. 0.3.13 (Aleksey Bragin)
> 2. Re: Apps regressions in 0.3.14 vs. 0.3.13 (Igor Paliychuk)
> 3. Re: Apps regressions in 0.3.14 vs. 0.3.13 (Aleksey Bragin)
> 4. Re: COM Monitor (caemyr(a)myopera.com)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 16 Dec 2011 16:46:07 +0400
> From: Aleksey Bragin <aleksey(a)reactos.org>
> Subject: [ros-dev] Apps regressions in 0.3.14 vs. 0.3.13
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <4EEB3D8F.7060405(a)reactos.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I did a brief comparison of wiki pages for 0.3.13 and 0.3.14 and found
> out at least the following apps which worked in 0.3.13 but does not work
> in 0.3.14 RC (aka trunk, we'll set exact revision soon):
>
> AbiWord
> Irfanview
> Opera 9.64
> Python - bug #5767
> SMPlayer 0.6.9
> VB5 Runtime
>
> I will try to go through the list and see what are the problems.
> Everyone is welcome to do the same and distribute the workforce on
> fixing those issues.
>
> Certainly, on the positive side, there are "green" fields in the new
> test results which were previously "red" in 0.3.13, so user-visible
> progress definitely exists, we just need to make sure it's continuously
> going better and better, without steps backward.
>
>
> WBR,
> Aleksey Bragin.
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 16 Dec 2011 15:31:41 +0200
> From: Igor Paliychuk <mansonigor(a)gmail.com>
> Subject: Re: [ros-dev] Apps regressions in 0.3.14 vs. 0.3.13
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID:
> <CAM0_0mZcLikSyHWJvfDfK3+qKi7OXKsTnJ3gCjtv0pjQNaNScA(a)mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Afaik Infanview needs mfc libs to work so it's not regression, just
> app requirement(though i didn't try to run it)
>
> 2011/12/16, Aleksey Bragin <aleksey(a)reactos.org>:
>> I did a brief comparison of wiki pages for 0.3.13 and 0.3.14 and found
>> out at least the following apps which worked in 0.3.13 but does not work
>> in 0.3.14 RC (aka trunk, we'll set exact revision soon):
>>
>> AbiWord
>> Irfanview
>> Opera 9.64
>> Python - bug #5767
>> SMPlayer 0.6.9
>> VB5 Runtime
>>
>> I will try to go through the list and see what are the problems.
>> Everyone is welcome to do the same and distribute the workforce on
>> fixing those issues.
>>
>> Certainly, on the positive side, there are "green" fields in the new
>> test results which were previously "red" in 0.3.13, so user-visible
>> progress definitely exists, we just need to make sure it's continuously
>> going better and better, without steps backward.
>>
>>
>> WBR,
>> Aleksey Bragin.
>>
>> _______________________________________________
>> Ros-dev mailing list
>> Ros-dev(a)reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 16 Dec 2011 19:57:38 +0400
> From: Aleksey Bragin <aleksey(a)reactos.org>
> Subject: Re: [ros-dev] Apps regressions in 0.3.14 vs. 0.3.13
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <4EEB6A72.50908(a)reactos.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Update:
>
> out of this list, only VB5 Runtime remains untested. Everything else is
> tested and works except for the newer version of AbiWord (2.9) which is
> probably not a regression (and I fixed SxS-related problem this version
> of AbiWord was suffering from).
>
>
> On 16.12.2011 17:31, Igor Paliychuk wrote:
>> Afaik Infanview needs mfc libs to work so it's not regression, just
>> app requirement(though i didn't try to run it)
>>
>> 2011/12/16, Aleksey Bragin<aleksey(a)reactos.org>:
>>> I did a brief comparison of wiki pages for 0.3.13 and 0.3.14 and found
>>> out at least the following apps which worked in 0.3.13 but does not work
>>> in 0.3.14 RC (aka trunk, we'll set exact revision soon):
>>>
>>> AbiWord
>>> Irfanview
>>> Opera 9.64
>>> Python - bug #5767
>>> SMPlayer 0.6.9
>>> VB5 Runtime
>>>
>>> I will try to go through the list and see what are the problems.
>>> Everyone is welcome to do the same and distribute the workforce on
>>> fixing those issues.
>>>
>>> Certainly, on the positive side, there are "green" fields in the new
>>> test results which were previously "red" in 0.3.13, so user-visible
>>> progress definitely exists, we just need to make sure it's continuously
>>> going better and better, without steps backward.
>>>
>>>
>>> WBR,
>>> Aleksey Bragin.
>>>
>>> _______________________________________________
>>> Ros-dev mailing list
>>> Ros-dev(a)reactos.org
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>
>> _______________________________________________
>> Ros-dev mailing list
>> Ros-dev(a)reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 16 Dec 2011 23:44:29 +0100
> From: caemyr(a)myopera.com
> Subject: Re: [ros-dev] COM Monitor
> To: "ReactOS Development List" <ros-dev(a)reactos.org>
> Message-ID:
> <1324075469.24028.140661012646145(a)webmail.messagingengine.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Hiya
>
> I think it depends what do you want to do with it. If you want it in ROS
> codebase (not necessarily in trunk, but still on svn) you should post a
> patch to bugzilla, with some info on how it works.
>
> Best regards
>
> On Fri, Dec 16, 2011, at 01:34 PM, Love Nystrom wrote:
>> Hi,
>>
>> I wrote a test/debug util (COM monitor) for logging ReactOS dbg/bt
>> messages,
>> and wonder if it will be better to submit it as a bugzilla patch, or
>> start a sourceforge
>> or codeproject page for it ?
>>
>> Most of you probably have other utils, but ComMon is quite handy with
>> it's
>> auto enumerated COM ports, extended selection mode list, copy selected
>> to clip,
>> save/clear list etc..
>>
>> I have it in my reactos/tools tree and it currently builds with the
>> RosBE toolchain
>> (standalone w C::B, currently not by rbuild).
>>
>> Would you be interested at all ?
>>
>> Best Regards
>> // Love
>>
>> _______________________________________________
>> Ros-dev mailing list
>> Ros-dev(a)reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
>
> --
> With best regards
> Caemyr
>
>
>
> ------------------------------
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> End of Ros-dev Digest, Vol 88, Issue 13
> ***************************************
>
Hi,
I wrote a test/debug util (COM monitor) for logging ReactOS dbg/bt messages,
and wonder if it will be better to submit it as a bugzilla patch, or
start a sourceforge
or codeproject page for it ?
Most of you probably have other utils, but ComMon is quite handy with it's
auto enumerated COM ports, extended selection mode list, copy selected
to clip,
save/clear list etc..
I have it in my reactos/tools tree and it currently builds with the
RosBE toolchain
(standalone w C::B, currently not by rbuild).
Would you be interested at all ?
Best Regards
// Love
Has anyone noticed notepad? While user32_winetest win > data, then
notepad data! The balance program go into high speed swapping!!
Bunches of theses:
(ntoskrnl/mm/section.c:2110) Pagint out 692d.
(ntoskrnl/cc/view.c:403) Evicted 256 cache pages
(ntoskrnl/mm/balance.c:167) Trimming consumer 0: Freed 256 pages with
a target of 256 pages
looping over and over~
When all this is going on I managed to get taskman up, notepad using
74,5?? K, wow!
Just wondering,
James
Piece of good news too..
FileZilla FTP Client 3.5.2 (latest) installs and runs with flying colors
by the looks of it.
Would suggest it's added to the Rapps list :D
(http://filezilla-project.org/download.php)
Best Regards
// Love
Filed as #6753.
MinGW / Msys-1.0: Sh.exe deadlock seems to be result of unhandled
exception.
(I.e. got nothing to do with batch processing).
Best Regards
// Love
It may be old news, but the fact that RtlSetUnhandledExceptionFilter is
unimplemented
makes it impossible for many apps to handle their heap allocation
errors, aggravating
the work for the memory manager, and resulting in crashes, leaks, and
heap corruption.
Whoever knows our SEH well enough could do a major improvement by fixing
this.
I came across this while testing MinGW 20100909 on r 54606,
where sh.exe deadlocks after causing leaks in base/shell/cmd/batch.c
[213,116,332].
(I was aiming for a fully bootstrapped system by letting ROS build ROS.)
I'll try to establish a trace on the batch processing bug, and file it.
Best Regards
// Love
I've come across a whopper size bug, likely somewhere in USER or GDI (in
r54606).
If you switch app while you have a modal dialog open, and the new window
covers that dialog,
then when you come back that dialog is invisible, but it's window proc
still active, meaning
you have no way to back out of it, and you have to kill the app with
taskman (if you can).
I would nominate this a real blocker, it's just too embarrassing to release.
I'll try to figure a repeatability and file a bug, and I'd recommend
that USER and GDI
devs heed Alekseys request for feature freeze and roll up their sleeves
on this one.
Best Regards
// Love
Hello testers,
your help is greatly needed.
Trunk needs to be tested using this template as a guideline
http://www.reactos.org/wiki/Tests_for_0.3.14
Imagine that trunk is a 0.3.14 RC (I don't want to branch because I
already called for a feature freeze, so essentially trunk is in "release
mode" right now, and branching would just require merging all revisions
from trunk to the branch).
Fill in the revision number in the "comments" section of that page when
you test.
Also, please be prepared that this might be a double work because after
testing more changes (fixes) would come in and eventually require
retesting, but it is vital to get clear non-biased understanding on how
well trunk performs right now.
Thank you,
looking forward to see results,
Aleksey Bragin.
Quick typo, your param checks in LdrpCheckForKnownDll come after your initialization
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of fireball(a)svn.reactos.org
Sent: 07 December 2011 17:51
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [fireball] 54606: [NTDLL/LDR] - Improve LdrpCheckForKnownDll by adding parameters validation, return status value, better failure paths handling.
Author: fireball
Date: Wed Dec 7 17:51:18 2011
New Revision: 54606
URL: http://svn.reactos.org/svn/reactos?rev=54606&view=rev
Log:
[NTDLL/LDR]
- Improve LdrpCheckForKnownDll by adding parameters validation, return status value, better failure paths handling.
Modified:
trunk/reactos/dll/ntdll/include/ntdllp.h
trunk/reactos/dll/ntdll/ldr/ldrutils.c
Olaf, please don't leave, the project needs you just
as much as it needs the developers.
Eric, Olaf's regression testing can not entail patching/rebuilding
the system to accomodate disk structure (as you surely realize).
That said, your reasons for change are sound, but perhaps you
can make provisions to temporarily revert this if it causes massive
problems. The timing _is_ not good if indeed a release is close
at hand.. Can it wait until after the release?
Alex, calling Olaf "not an OS tester" is a bit harsh, don't you think?
Not everyone can be as weather hardened and experienced as you are.
Regarding the reasons for change:
Max CHS capacity: 10 bit C, 6 bit S, 8 bit H
2^10 * 2^6 * 255 == 16711680 sect(512) == 8.5 GB
This is the geometry Eric wants to use, which makes sense
because it can utilize the full CHS addressing capacity,
and reflects the absolute limit of BIOS int 13h CHS calls.
Previous 32S 64H CHS limit:
2^10 * 32 * 64 == 2097152 sect(512) == 1 GB
This is an artificial and unnecessary limit, imposed by some
strange design decision in Redmond a long long time ago.
For non-devs: In CHS mode BIOS has an absolute disk limit of 8.5 GB,
due to the available address bits, a 10/6 bit Cylinder/Sector composite,
and an 8 bit head number. Any disk bigger than that can only be addressed
in LBA mode (logical sector nr), which has a limit of 2^32 sectors == 2 TB.
And, if anyone didn't know, the geometry parameters are stored
in the boot sector, not in the MBR.
There's more to it, but I stop at that.
So.. Eric's change _should_ not cause any problem on disks
larger than 8.5 GB, since they run in LBA mode by necessity.
Concordingly, there could be forseeable problems on virtual disks
which will often be smaller than 8 GB and may be running CHS mode.
That'll be my penny to the pot for now.
PS. A standard sector is 512 bytes. Bigger sectors, e.g 1kB, have been used
in the past to increase capacity, but are _very_ unusual since they require
proportionately higher bit frequencies on the media and are error-prone.
Best Regards
// Love
This should fix a bunch of weird issues with 3rd party NIC drivers. Most NICs use deserialized drivers and indicate packets using the NdisMIndicatePacket function. I'm fairly sure every modern NIC driver will display a similar problem to http://www.reactos.org/paste/index.php/9607/ and http://www.reactos.org/paste/index.php/9608/ where the driver eventually depletes its packet pool then quits sending and receiving packets. It also causes a leak of non-paged pool since we leak the buffers attached to the packet descriptor. The VirtIO NetKVM driver seems to have a particularly small packet queue (256 RX) and dies very early.
I'd be interested to see what kind of uptime you guys can get with a 3rd party NIC driver now. I'm going to do some testing here in VirtualBox with a PRO/1000 to see how much data I can send/receive without problems.
Regards,
Cameron
Hello,
Let me invite you to the monthly status meeting taking place last thursday
of this month, 24th of November, 19:00 UTC.
The meeting will be atirc://fezile.reactos.org (Port 6667, no SSL) in the
channel #meeting. Note that the IRC service will only be started shortly
before the meeting. Everyone is invited to listen, and active community
members have their passwords so that they can participate in the
discussion.
If someone still is not getting passwords sent before a meeting - please
email
Colin or Pierre before the meeting started to get one.
Proposed agenda for the meeting:
1. Release status
2. Website revamp status
3. CMake adoption status
More suggestions are welcome as usual.
With the best regards,
Aleksey Bragin.
Is the new geometry backward-compatible? If i recreate the partitions, will they be visible when i regress test revisions before 54511?
--
With best regards
Caemyr
Hi,
due to connectivity issues with our servers in Sweden, I've taken our
rbuild debug buildslave & our KVM testbot offline.
This doesn't affect ISOs storage for the moment.
Regards,
Pierre
I see this and I LMFAO!
co_IntSendMessageNoWait(Window->head.h, WM_WINDOWPOSCHANGING, 0,
(LPARAM) WinPos);
co_IntSendMessageNoWait(WinPos.hwnd, WM_WINDOWPOSCHANGED, 0, (LPARAM) &WinPos);
There is more too! Amazing!
Please tell me this is not wrong!!!!
James
Hi People,
I'm back after my ordeal in Europe and finally got an inet line..
But now I've over 300 mails from the list to wade through.. Ugh.
It's gonna take some time to get up to speed.
Hi Eric,
That's all fine, it's just an educated choice of disk parameters as I see
it.
But anyway, all disk handling software (drivers etc) should honor whatever
disk parameters you write in the boot record when you format the partition,
and whatever geometry you write in the MBR when the disk gets partitioned,
whether it's this or that.
Just in case someone forgot ;)
Best Regards
Love
> From: Eric Kohl <eric.kohl(a)t-online.de>
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Date: Mon, 21 Nov 2011 23:17:40 +0100
> Subject: [ros-dev] Announcement: New harddisk geometry next weekend
> Hi!
>
> I plan to change the standard harddisk geometry from the old 32 sectors
and 64 heads geometry to the > new 63 sectors and 255 heads geometry next
weekend. The old disk geometry was used up to
> Windows NT4 and the new geometry is used since Windows 2000. So I guess
it is time for ReactOS to > make this change too. ;-)
>
> This should improve the compatiibility with other OSs because every
modern OS uses the new disk
> geometry.
>
> Please note that you must delete and re-create all partitions on your
virtual harddisk in order to get
> a clean partition table when the new disk geomerty is in use.
>
> Regards,
> Eric
Am 24.11.2011 01:07, schrieb cgutman(a)svn.reactos.org:
> Author: cgutman
> Date: Thu Nov 24 00:07:15 2011
> New Revision: 54484
>
> URL: http://svn.reactos.org/svn/reactos?rev=54484&view=rev
> Log:
> [SCSIPORT]
> - Implement ScsiPortGetLogicalUnit
>
> Modified:
> trunk/reactos/drivers/storage/scsiport/scsiport.c
>
> ...
> +
> + /* Return the logical unit miniport extension */
> + return (LunExtension + 1);
> }
This looks broken to me. The old code was
"&LunExtension->MiniportLunExtension", which seems to make more sense.
Hi!
I plan to change the standard harddisk geometry from the old 32 sectors
and 64 heads geometry to the new 63 sectors and 255 heads geometry next
weekend. The old disk geometry was used up to Windows NT4 and the new
geometry is used since Windows 2000. So I guess it is time for ReactOS
to make this change too. ;-)
This should improve the compatiibility with other OSs because every
modern OS uses the new disk geometry.
Please note that you must delete and re-create all partitions on your
virtual harddisk in order to get a clean partition table when the new
disk geomerty is in use.
Regards,
Eric
Am 18.11.2011 00:41, schrieb cgutman(a)svn.reactos.org:
> Author: cgutman
> Date: Thu Nov 17 23:41:18 2011
> New Revision: 54415
>
> URL: http://svn.reactos.org/svn/reactos?rev=54415&view=rev
> Log:
> [I8042PRT]
> - Implement support for hot plugging PS/2 mice if one was present at boot (same requirement as Windows)
> - Fixes bug 1395
>
>
Exellent!
--
Johannes Anderwald
Hi all,
As some of you know, I have started university about a month ago. Due to
the amount of time I have to spend on university tasks these days, I can
no longer fulfil all my project obligations. Therefore, I'm looking for
new maintainers in the following areas:
* RosBE-Unix
* My Web tools (especially Testman and the rest of the regression
testing system, but also GetBuilds/People Map/Subsystem integration)
* Release Engineering (unless Ziliang can fully takeover my position)
Provided that I find time, I'll introduce the new maintainers into these
tasks as good as possible.
I try to stay available for infrastructure and foundation tasks, but my
time for these will definitely be limited as well.
Best regards,
Colin
Debug log from testing cmake soundchip in KSStudio.
http://www.reactos.org/paste/index.php/9568/
Btw i'm getting crash in cmuda.sys on two different PCs (though i didn't
notiv=ce if chips are the same)
To get your attention, Johannes ;)
Am 16.11.2011 22:17, schrieb tfaber(a)svn.reactos.org:
> Author: tfaber
> Date: Wed Nov 16 21:17:38 2011
> New Revision: 54401
>
> URL: http://svn.reactos.org/svn/reactos?rev=54401&view=rev
> Log:
> [ATL] - Fix buffer overflow in CComDynamicUnkArray::Add. Found by Coverity (CID 2474)
> [NDK] - Remove meaningless const attribute from pointer rvalues to make Coverity's life easier
> -#define SharedUserData ((KUSER_SHARED_DATA *CONST)USER_SHARED_DATA)
> +#define SharedUserData ((KUSER_SHARED_DATA *)USER_SHARED_DATA)
It is like this (with the const) in wdm.h
#define SharedUserData ((KUSER_SHARED_DATA * const) KI_USER_SHARED_DATA)
maybe its supposed to express that "SharedUserData" is a constant and
not a variable... although that doesn't make much sense
>The Total Commander comboboxes for the left and right drive list
>are Unicode. However, Total Commander calls
>SendMessage(handle,CB_ADDSTRING,0,(LPARAM)ansitext);
>to add items as ANSI text. This seems to work, but it's adding some
>extra text at the end.
If I understand correctly, Total Commander is calling SendMessage, which in
this case is translated to SendMessageW (as the comboboxes are Unicode).
So TC is calling SendMessageW to append an ANSI string to a Combobox.
Let's give a look to SendMessageW implementation thanks to Doxygen:
http://doxygen.reactos.org/da/d64/winuser_8h_a18e5b961d742150a18d3039b5dd88…
02161 Result = NtUserMessageCall( Wnd,
02162 KMMsg.message,
02163 KMMsg.wParam,
02164 KMMsg.lParam,
02165 (ULONG_PTR)&Result,
02166 FNID_SENDMESSAGE,
02167 FALSE);
Line 2167 FALSE is the BOOL ANSI param of NtUserMessageCall.
But in this case the BOOL ANSI should be TRUE as the string is really ANSI.
So since this moment we are treating TC call ( SendMessageW(handle,CB_ADDSTRING,0,(LPARAM)ansitext); )
in the same way as we would be treating SendMessageW(handle,CB_ADDSTRING,0,(LPARAM)unicodetext);
This seems a bug for me.
Feel free to correct me, but seems that SendMessageW is able to set both kind
of strings ANSI and UNICODE in Windows, while we are forcing to our
SendMessageW implementation to treat them as UNICODE always.
Am I wrong?
This could be a big potential issue as this could affect to all the SendmessageW calls.
This is all just a guess, so please feed me with your knowledge.
Thanks a lot!
Hi all,
Looking at
https://verein.ing-diba.de/sonstiges/33378/reactos-deutschland-ev, we
have scored the 810th place in the tough competition and just won 1000
EUR for the foundation! :-)
Even if we lost our position in the top of the list, comparable German
Open-Source foundations like KDE e.V. or Free Software Foundation Europe
are both out of the game.
I'd like to use this opportunity to thank every voter for the great
support towards the project! Over 8000 votes in four weeks really shows
that we still have a huge fan base.
Best regards,
Colin
I'm getting questions, if it's "just formatting and no code changes",
why author names are removed for good and not readded in the new file?
WBR,
Aleksey Bragin.
On 07.11.2011 3:01, ion(a)svn.reactos.org wrote:
> Author: ion
> Date: Sun Nov 6 23:01:04 2011
> New Revision: 54323
>
> URL: http://svn.reactos.org/svn/reactos?rev=54323&view=rev
> Log:
> [KERNEL32]: Move the "curdir.c" APIs into path.c as well, as they are Path APIs. No code changes (just formatting and moving to DPRINTs).
> Removed: trunk/reactos/dll/win32/kernel32/client/file/curdir.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/kernel32/client/…
> ==============================================================================
> --- trunk/reactos/dll/win32/kernel32/client/file/curdir.c [iso-8859-1] (original)
> +++ trunk/reactos/dll/win32/kernel32/client/file/curdir.c (removed)
> @@ -1,388 +1,0 @@
> -/* $Id$
> - *
> - * COPYRIGHT: See COPYING in the top level directory
> - * PROJECT: ReactOS system libraries
> - * FILE: lib/kernel32/file/curdir.c
> - * PURPOSE: Current directory functions
> - * PROGRAMMER: Eric Kohl
> - * Filip Navara
> - * Steven Edwards
> - * Thomas Weidenmueller
> - * Gunnar Andre' Dalsnes
> - * UPDATE HISTORY:
> - * Created 30/09/98
> - */
>
Hi!
What I have run across in regards of ReactOS send message subsystem,
ros is not packing before co_MsqSendMessage and unpacking after
co_IntCallWindowProc! Instead packing before co_IntCallWindowProc with
send message. Does that not raise any questions?
co_IntSendMessageWithCallBack seems to do it almost right, but
IntCallWndProc/Ret should be called when calling the client via
co_IntCallWindowProc and should pack before the call to MsqWakeQueue
and then unpack after the call to co_IntCallWindowProc. Confused?
Basing this on IntCallLowLevelEvent and co_IntCallLowLevelHook when
the lParam is used to save information that could get lost in a stack
switch or release.
Setting up the pattern; Pack before co_MsqSendMessage or related
friends and Unpack after calling co_IntCallWindowProc to client. Have
co_MsqDispatchOneSentMessage call something other than
co_IntSendMessage so the Packed data can be handled correctly when
calling to the client via co_IntCallWindowProc.
I'm sure Michael Martin has brought this up to me on many occasions.
Let's see where this goes!
Thanks,
James
Hi,
the Linux build slave will be relocated (changing data center & country)
starting tomorrow. It will, obviously, be offline during the meantime.
So, you will not have any Linux builds nor KVM tests.
We will do our best to get it back online as soon as possible.
Regards,
The ReactOS Sysadmins.
Hello all,
Here are the minutes from the last ReactOS meeting on the 27th of October
2011:
20:20 Aleksey Bragin called the meeting to order
- Aleksey Bragin shared a video interview about ReactOS at
http://alenapopova.ru/egov/react-os-kraudsorsing-pri-sozdanii-operacionnoj-…
- Aleksey Bragin stated the meeting agenda as being:
1. Website revamp status
2. CMake adoption
3. Release status
1. Website Revamp
-----------------
- Amine Khaldi started on the Website revamp status and stated that
unfortunately nothing has progressed since the last meeting because of
aross, superdog and nisky being extremely busy.
- He also stated that Aleksey has yet to commit the bridges needed and
that the actual milestone is the theme (ie design/layout that matches
the current website), after which devs will need to investigate phpbb
issue.
- Aleksey Bragin added that almost the only thing left is the theme
and with it progress could be made fast to the website engine and have
a test run with real data.
- He also stated that all details could be provided to anyone
motivated enough with HTML/CSS.
- Matthias Kupfer said he could support HTML/CSS around Christmas, but
not earlier.
- Aleksey Bragin asked Maciej Bialas if he could assist in theming.
- Maciej Bialas said he could, and added that he tried to create a
simple theme first resembling the current one, and that aross said he
could have done better by using some Drupal modules Maciej was not
aware of.
- Aleksey Bragin stated that a simple theme would suffice for now and
a better one can always be done later.
- Ziliang Guo asked about user and forum transfer status.
- Aleksey Bragin replied that the forum is phpbb and therefore easily
transferable
- Ziliang Guo asked about the reason for sticking with phpbb.
- Amine Khaldi and Aleksey Bragin stated that it was for the sake of
easier migration (ie migrate one thing at a time not everything at
once)
- Maciej Bialas stated that one downside to this was tedious
integration with phpbb.
- Aleksey Bragin pointed out that playground.reactos.org (with its
intact database) will be what the new main site looks like when the
switch is made.
- Ziliang Guo said he can start trying to add content the coming weekend.
- Amine Khaldi asked Ziliang Guo to keep everything minimalistic.
- Aleksey Bragin moved the meeting on to the CMake adoption topic on the agenda.
2. CMake adoption
--------------------
- Aleksey Bragin took this chance to welcome Alex Ionescu back to the
ReactOS project.
- Amine Khaldi stated that Alex Ionescu stumbled upon a way to
separate debug info from binaries, in a pdb similar way, using
objcopy. He also mentioned that Alex helped by fixing two bugs in
windmc and windres.
- He went on to say that Alex suggested that we go back to using
dwarf-2, only this time with pdb style debug, and with an improved,
out of the kernel, symbols handling. He mentioned that Thomas Faber
was kind enough to sketch a batch script that takes a debug log and
translates the addresses inside it.
- Amine Khaldi further stated that with the script + the CMake changes
to take account of windres and objcopy, we'll be able to reduce the
iso size, reduce the memory footprint, reduce the disk space needed to
compile, use windres alone and get rid of handling symbols in the
kernel (something "no other OS does" as Alex describes it).
- He then explained that, on the RosBE level, this will only require
updating binutils (gcc will stay at 4.4.3) with the patched windres
and windmc, and it will also require the translating script to be part
of RosBE.
A discussion ensued about testing the new RosBE and the following
conclusions where reached:
- Have a new Build Environment Release Candidate (2.0) which is an
update to binutils (ld, windres, windmc, addr2line... etc) until the
next meeting.
- Keep the 4.4.3 version of gcc until the next meeting.
- Alex Ionescu suggested having the new RosBE ready by the time of the
next release. He also noted that this does not mean the new BE will be
released along with the next version of ReactOS, but that it must be
ready by then.
- Cameron Gutman then brought up the issue of switching to gcc 4.6,
but it was decided to keep gcc 4.4.3 until after the next release.
- Thomas Faber then suggested an outlined step by step plan:
1) Update BE
2) Release new version of ReactOS (0.3.14)
3) Get rid of wrc
4) Get rid of rbuild
5) Switch to dwarf
6) Adopt new compiler (gcc 4.6)
After some deliberating it was agreed upon that Thomas Faber's
proposed course of action is the best way to go, and his proposal was
accepted.
- Amine Khaldi then moved the meeting to the next topic
3. Release status
--------------------
- Cameron Gutman inquired about the progress on the heap regression issue.
- Thomas Faber stated that although he himself hasn't made much
progress because he is very busy during the week, Jerome has been
tracking it down pretty well and that it is apparently caused by
resource loading.
- Amine Khaldi took this chance too thank everyone for the awesome
bugfixing phase, and stated that a lot of bugs has been fixed and a
lot of regression has been addressed. He also went on to thank
testers, and outlined the importance they have, and stated that he
hopes this will be the mentality of the ReactOS project team, as
thanks to it ReactOS is improving a lot.
- He went on to say that as far as the remaining blockers are
concerned, more team work on fixing them is needed, as this has proved
very effective in the past. He also added that Jim Tabor did a good
one man job on the jre issue, but that the other issues could use some
teaming up.
- Aleksey Bragin further added to this that ReactOS is on the way to
possibly one of the best releases, and that after years have passed
everyone is working towards the same goal, which, he added, is
fantastic.
- Cameron Gutman agreed that ReactOS is indeed very stable now,
especially in kernel mode.
- Olaf Siejka went on to sum up that entering the release stage would
require at the very least fixing mshtml bug and fixing ldr
regressions.
- Aleksey Bragin agreed with Olaf Siejka on that point.
- Kamil Hornicek inquired about the official stance about hackfixing
certain bugs.
- Aleksey Bragin and Amine Khaldi both explained that while hackfixing
should be avoided, there are some bugs which cannot be resolved in a
timely fashion. But hackfixing these should clearly be reflected in
the commit message and comments in the code.
- Amine Khaldi went on to ask for a more visible teaming up, for
example on IRC and through bug reports, and to also request marking
bugs as assigned when devs take them. He mentioned that since the
release blockers remained unassigned for a while, it was difficult at
times to keep track of who is working on what.
- Cameron Gutman inquired if anybody objects to modifying the default
color depth from 16-bit to 32-bit.
- Olaf Siejka raised some concerns about this as it will affect QEMU
since it does not support 32bpp.
- Cameron Cutman further inquired about the possibility of falling
back more gracefully as far as color depth is concerned when a video
card does not support a certain resolution (right now it falls back
directly to 8bpp). He went further to ask Timo Kreuzer if this is
standard windows behavior.
- Timo Kreuzer said he would need to investigate this issue.
- Aleksey Bragin formally ended the meeting, thanking everyone for
their time and information.
Minutes by Claudiu Mihail.
Hello,
Let me invite you to the monthly status meeting taking place last thursday
of this month (hint: today), 27th of October, 19:00 UTC.
The meeting will be atirc://fezile.reactos.org (Port 6667, no SSL) in the
channel #meeting. Note that the IRC service will only be started shortly
before the meeting. Everyone is invited to listen, and active community
members have their passwords so that they can participate in the discussion.
If someone still is not getting passwords sent before a meeting - please email
Colin or Pierre before the meeting started to get one.
Proposed agenda for the meeting:
1. Release status
2. CMake adoption status
3. Website revamp status
More suggestions are welcome.
With the best regards,
Aleksey Bragin.
Hello!
Time flies fast, and soon we are going to face the deadline (next status
meeting) by which we decided to create a RC of the upcoming release.
And, there are some problems.
I will start from good stuff. Since the last meeting took place, quite a
few regressions were fixed, and interesting bugs have also been closed.
This is very good and I appreciate your efforts.
However some problems remains, and here is where your help is urgently
needed! For the current milestone (0.3.14), there are 3 blocker
regressions and 2 big buckets of issues - ldr rewrite regressions and
shell32 rewrite regressions.
From blocker stuff, the most important is the heap-related one.
Mephisto provided a good explanation here
(http://www.reactos.org/bugzilla/show_bug.cgi?id=5857), and we need
someone with a fresh eye to look into this problem. N.B. Please don't go
into "let's fix some unrelated stuff in the heap code just to make it
better". Look strictly into the specified bug and try to spot the place
where the heap lists are getting corrupted.
Anyone volunteers to have a look?
LDR regressions: there are relatively many of them, but all are
more-or-less nicely fixable because of the new, good LDR code. Alex -
maybe you could please devote a bit of your time to check the code and
see if that fixes some of the regressions?
shell32 regressions: I already see some improvements being committed,
please continue this way.
We can make a good 0.3.14 release only if we act as a team now. It's not
someone, it's YOUR help which matters. Testers are already doing as much
as they can, retesting issues, providing newer debug logs, and other
other things. Now it's time to act and fix regressions before moving
further. It's just stupid to move further, if a rewrite introduces new
bugs instead of fixing existing. I know how hard it is, but let's finish
smaller steps and hence move forward.
There is no way forward at all if old bugs are stacked and new
regressions are introduced all the time. We can't bring in new good
changes (wine syncs, 3rd party code syncs, arwinss, whatever else) until
0.3.14 is ready, and 0.3.14 is not ready until blocking regressions are
fixed. As simple as it is.
Thanks for reading and I hope you understand.
With the best regards,
Aleksey Bragin.
Hiya
Its still at least two weeks until next meeting, hence i suppose ros-dev could be used in decision making even before that. I have two things i would like to push, things that i discussed a bit with varioius team memebers on IRC and got positive feedback. I would like you guys to comment on those and if you feel that one of both of them are wrong/unnecessary/not needed, please voice it out here. If there is no opposition for them, i`ll consider those two accepted and push for them to be finialised. Here we go:
1. Adding a default theme to ReactOS.
We need at least one to test Themes service in trunk ootb and avoid copying it to ros install each time, which is really important in regression testing. Also, a theme is a must for our upcoming release. Since its not a big file usually, it should be present in trunk, not only in release ISO.
2. Moving Starfield screensaver from rosapps to trunk.
Rosapps, no matter how much cheered, is a wasteland, a museum, a forgotten place. It will not be even buildable when we move away from rbuild. Old and unneeded code should land there, but not a new creation Carlo has been working on. Apart from that, Starfield is using OpenGL, which is also a handy ootb test tool for 3d acceleration, also important in regression testing. If you think that two screensavers are the top amount you can accept, then lets replace one of the trunk screensavers with Starfield.
--
With best regards
Caemyr
Dear ReactOS Community Member,
We contact you today, because you have signed up for a myReactOS account
some time ago. And we need your help!
A German bank is currently running a sponsoring campaign for all kinds of
foundations. The 1000 foundations with the most votes receive 1000 EUR each
by the 15th November.
You can easily increase our chances by voting on the following website:
https://verein.ing-diba.de/sonstiges/33378/reactos-deutschland-ev
Here is the complete voting procedure:
* Open the link above
* Click on the orange button "Stimme abgeben" (= Vote)
* Enter your E-Mail address and solve the captcha, then hit the button
"Absenden" (= Send)
* You will receive a confirmation E-Mail where you have to click the first
link. Finally click on "Stimme abgeben" again and you're done.
Note that you can vote UP TO 3 TIMES with a single E-Mail address, and you
can even cast all votes to the same foundation.
You may also share this, so that we can get as many people as possible to
vote for us.
Let's get ReactOS among the top 1000!
Cheers and thanks for your support,
Aleksey Bragin and Colin Finck
in the name of the ReactOS Team and ReactOS Deutschland e.V.
Hi,
Since one of my recent video driver loading changes, livecd video is vga
mode. The reson is:
When installing bootcd, there will be only 1 video driver installed:
based on 1st stage selection, either vbe or vga will be installed the
other one is deactivated (start mode = manual). When installing a 3rd
party driver, that one used to be installed and loaded prior to VBE and
thus became Device/Video0, which win32k happily used as primary adapter.
This behaviour changed with ACPI hal and VBE is loaded first, resulting
is non functional VBox driver.
I fixed this, by having win32k decide which driver to use, by looking if
its a vga compatible driver and use that one only as fallback, if no
other is present. additionally the VBE was marked as VgaCompatible.
Now livecd behaves differently and simply installs both VGA and VBE. and
since both are now marked as VgaCompatible, win32k doesn't know which
one to use and currently uses VGA.
Now how does this work in Windows? Windows has only one Adapter
installed for VGA and VBE (vga.sys +
vga.dll/vga256.dll/vga64k.dll/framebuf.dll) This service is always
loaded and marked as "VgaCompatible". It is also used when a 3rd party
driver is installed, when you switch to fullscreen console mode.
This adapter is only replaced by a 3rd party adapter if that one is also
vga compatible.
This way its easy for win32k to decide which one to use: based on
whether /BASEVIDEO is passed, either the vga compatible one or the other
one can be selected.
Possible solutions:
1) Add another workaround to win32k, checking if 2 VGA adapters are
installed and then using the first one, instead of the second one as
currently (because 1st is VGA, simply the second is used), but thats not
a real solution.
2) Fix whatever is neccessary to have VBE be replaced by a 3rd party
driver that is installed. (Cameron said it was related to VBE not being
PNP ready.) This way we can stop marking it as VgaCompatible.
3) Combine VGA and VBE miniport into one vga compatible driver, like
it's in windows. Alex mentioned that eVb has more or less finished that.
Question is: whats missing to have the code comitted?
Comments and feedback appreciated,
Timo
I think that will not unload the last driver.
Looking at MMDRV_Install, MMDrvsHi is the index of the first free array
field and its incremented each time MMDRV_Install is called. The assert
in line 465 is wrong. It should be "<". The for () loop in line 432 is
also wrong
Your change starts with MMDrvsHi - 1, the last used index, then
decrements i by one before doing anything else.
Am 17.10.2011 18:35, schrieb jgardou(a)svn.reactos.org:
> Author: jgardou
> Date: Mon Oct 17 16:35:10 2011
> New Revision: 54179
>
> URL: http://svn.reactos.org/svn/reactos?rev=54179&view=rev
> Log:
> [WinMM]
> - avoid buffer overrun.
> - do not try to unload uninitialized driver.
> See issue #6343 for more details.
>
> Modified:
> trunk/reactos/dll/win32/winmm/lolvldrv.c
>
> Modified: trunk/reactos/dll/win32/winmm/lolvldrv.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/winmm/lolvldrv.c…
> ==============================================================================
> --- trunk/reactos/dll/win32/winmm/lolvldrv.c [iso-8859-1] (original)
> +++ trunk/reactos/dll/win32/winmm/lolvldrv.c [iso-8859-1] Mon Oct 17 16:35:10 2011
> @@ -634,7 +634,7 @@
> }
>
> /* unload driver, in reverse order of loading */
> - i = sizeof(MMDrvs) / sizeof(MMDrvs[0]);
> + i = MMDrvsHi - 1;
> while (i--> 0)
> {
> MMDRV_ExitPerType(&MMDrvs[i], MMDRV_AUX);
>
>
>
Hello all,
The "Trunk_x86_GCCLin Debug" Buildslave has been migrated to RosBE-Unix
2.0-RC1. All builds starting with r53983 are now created using a CMake
environment.
Unfortunately, the CMake builds don't boot under KVM on the same
machine, but apparently for everybody else. To give you an idea what I
mean by "don't boot": http://img830.imageshack.us/img830/5145/image1iz.png
If nobody has an idea how to debug or fix this, I'm afraid I have to
revert everything back to the rbuild scripts until a proper solution is
found.
- Colin
This is the original command-line:
mingw32-ld --entry=_DllMain@12 --image-base=0x74ae0000 @obj-i386/dll/win32/msxml3/msxml3_objs.rsp --start-group "/usr/local/new/RosBE/i386/lib/gcc/mingw32/4.4.3/libgcc.a" obj-i386/lib/3rdparty/libxml2/libxml2.a output-i386/dll/3rdparty/libxslt/libxslt.dll obj-i386/lib/3rdparty/libwine/wine.a obj-i386/lib/3rdparty/libwine/wineldr.a obj-i386/dll/win32/urlmon/liburlmon.a obj-i386/dll/win32/wininet/libwininet.a obj-i386/dll/win32/ws2_32/libws2_32.a obj-i386/dll/win32/comctl32/libcomctl32.a obj-i386/dll/win32/shell32/libshell32.a obj-i386/dll/win32/shlwapi/libshlwapi.a obj-i386/dll/win32/cabinet/libcabinet.a obj-i386/dll/win32/oleaut32/liboleaut32.a obj-i386/dll/win32/ole32/libole32.a obj-i386/dll/win32/version/libversion.a obj-i386/dll/win32/user32/libuser32.a obj-i386/dll/win32/gdi32/libgdi32.a obj-i386/dll/win32/advapi32/libadvapi32.a obj-i386/lib/sdk/uuid/uuid.a obj-i386/dll/ntdll/libntdll.a obj-i386/lib/3rdparty/mingw/mingw_common.a obj-i386/lib/3rdparty/mingw/oldnames.a obj-i386/dll/ntdll/libntdll.a obj-i386/dll/win32/kernel32/libkernel32.a obj-i386/dll/win32/msvcrt/libmsvcrt.a obj-i386/lib/debugsup/debugsup_ntdll.a --end-group -disable-stdcall-fixup -file-alignment=0x1000 -section-alignment=0x1000 --shared --exclude-all-symbols -o output-i386/dll/win32/msxml3/msxml3.dll
This is on RosBE 2.0 with RBUILD.
Note that it's trying to link with libxslt.dll, which obviously won-t work on a non-Windows host.
Removing that broken linkage makes the link work fine if I do it by hand. Can anyone fix?
--
Best regards,
Alex Ionescu
Hi all,
A first release candidate of RosBE-Unix 2.0 is now available on
http://svn.reactos.org/RosBE-Temp/. Compared to 1.5, it finally includes
CMake 2.8.5 (with Jerome's patches), an updated GNU Make and new GMP and
MPFR libraries. For the latter ones, I've added a patch to fix building
under Mac OS X 10.7.
Please try it out and tell me about your results. If there's anything
that needs to be fixed before the release, please tell me in a reply to
this mail.
For the reference, the current CMake building commands in a ReactOS
checkout are as follows:
- ./configure.sh
- cd output-i386-MinGW/host-tools
- makex
- cd ../reactos
- makex bootcd
I'll also set up this Build Environment on the Debug Buildslave as soon
as possible.
Happy building,
Colin
Hello!
As per discussion during the last status meeting, I proposed to set
up a deadline for having a 0.3.14 Release Candidate available by the
time of the next meeting.
Olaf, Amine and others were kind enough to make an up-to-date list of
critical bugs and regressions to be fixed. It's available here:
http://www.reactos.org/wiki/Buglist (indeed this page should be in
your web browser's Favorites!) .
I want to ask all of you to concentrate on fixing regressions and
critical/blocker bugs first, before going into fancy features or
implementing something else. It's really important, we need to make
0.3.14 as the last release before switching to 0.4. We have all
necessary prerequisites, and just need to sit down and fix regressions.
I personally put off all of my ReactOS-related "fancy" projects
because I want a solid trunk first, and I am working only on stuff
which is urgently needed - fixing remaining LDR rewrite regressions,
special pool to catch pool corruptions, etc. It's meaningless to work
on something else now if regressions aren't fixed.
Hopefully you will follow my advice and we will have a wonderful
bugfixing week(s)!
Thank you!
WBR,
Aleksey Bragin.
Hi all,
Previously I used edited version of freeldr.ini to build livecd ISOs,
it is in \output-i386\livecd\
Now freeldr.ini is becoming overwritten in make process by newly
generated "standard" one, and it is overwriting my manually edited
version.
So
1) what is now the correct way is to have custom freeldr.ini in iso image?
2) For what are these new automagical erase-and-newly-generate scripts?
Although I can now manually edit (in iso image) what has been done
earlier automatically, replace the file, but, at my PoV something goes
wrong.
--
Best Regards,
M.A.
Hi!
Well if anyone cares! This commit message is a lie!
In IntKeyboardInput I added support for KF_DLGMODE and KF_MENUMODE !
BTW is used! In Dialog.c DF_DIALOGACTIVE! So someone will fix it
right?
Okay,
James
You might know me as a stout supporter of CMake transition, but a single experience shattered my certainity. Today i tried to resolve a backtrace for a bug report, done with a cmake iso. The results were horrendous. The backtrace was lenghty, but on rbuild such task would take around 15 mintues for me, having all files extracted and prepped log.. At the present moment, cmake bt resolving is a total mess and practically prevents anyone doing such log. I might not be a programmer, but was somewhat skilled in my testers duties, also as some recall, i loved doing manual traces by raddr2line. With cmake - i hate it:
1. the whole process takes minutes more per frame: you need the base address, add the offset and type in the addr2line command
2. base address from kdbg: mod is not reliable, as modules might be relocated. addr2line doesn't know about that...
3. C++ function names are not demangled. For those modules that are written in c++ you will only get source lines, unless you check them up manually.
4. Being somewhat experienced, i see no way how i`m to explain newcomer how to do a backtrace... on the other hand, do you expect anyone to waste half an hour doing so?
This HAS to be resolved before rbuild is put to retirement. Amine was talking about getting back to rsym - sure, why not? Anything that works will be better than current situation.
--
With best regards
Caemyr
cgutman(a)svn.reactos.org wrote:
> - Implement support for scatter/gather DMA
This commit deserves a huge LIKE button, thanks!
Will try it out as soon as I have access to my ReactOS laptop again.
Finally a chance for getting its Ethernet port to work :-)
- Colin
Hi!!
This is wrong, 8^(
+ class.style |= CS_GLOBALCLASS;
+ class.hInstance = COMCTL32_hModule;
The point in THEMING_Initialize was to get the current global classes
and make locals for each process. So that process could have it. Not
the whole system!
Note from a msdn blog, "If you pass the CS_GLOBALCLASS flag when
registering the class, then the window manager will ignore the
instance handle when looking for your class. All of the USER32 classes
are registered as global."
I spent a week now looking through it all, ReactOS is handling the
class registration correctly. My best guess, if themes is active do as
the original code had it before and use IsThemeActive like it is
setup. Keep class.hInstance = COMCTL32_hModule; and don't use
CS_GLOBALCLAS so you can find it again.
Thanks,
James
Hi,
today, after looking at the daily source analysis we have, I found out
that all that stuff could be improved by lightening trunk. We have huge
amount of unused code (even not linked in CMake) rotting in trunk.
I'm mainly talking about icu4ros. AFAIK it was an attempt from KJK for I
even don't recall what.
Here is my proposal: we do a branch for this. And then, we remove it
from trunk. This will make things lighter, without loosing code.
Any objections/comments?
Regards,
Pierre
With this attempt Thomas proved that it is possible to use patchbot for both trunk and rostests patching. Ask him how he did it:>
On Wednesday, October 05, 2011 9:05 AM, ReactOS.Bugzilla(a)reactos.org wrote:
> --- Comment #1 from ThFabba <thfabba(a)gmx.de> 2011-10-05 09:05:44 CET ---
> Created an attachment (id=6782)
> --> (http://www.reactos.org/bugzilla/attachment.cgi?id=6782)
> patch 2
>
> Maybe this works :p
>
--
With best regards
Caemyr
Hi,
I've been looking at VirtualBox 4.1.x guest additions, which don't install
in ROS [1] and came up with a patch [2] that seems to fix them.
While patchbot says this is okay [3] (and the last hunk even fixes a few
setupapi tests), I am very unsure about the SP_COPY_NOOVERWRITE part.
The correct solution might instead be to handle SetupCopyOEMInf returning
ERROR_FILE_EXISTS or I might be "fixing" something in the completely
wrong place.
It would be great if someone with some insight into setupapi
(Eric? Hervé? ;]) could review this and give some pointers.
Thanks!
-Thomas
[1] http://www.reactos.org/bugzilla/show_bug.cgi?id=6522
[2] http://www.reactos.org/bugzilla/attachment.cgi?id=6753
[3] http://www.reactos.org/testman/compare.php?ids=8272,8294,8303,8305
Patch explanation:
- The first hunk isn't really required, but I guess it shouldn't break
anything, and seems to find what it's looking for this way.
- The second hunk is in the code path used by VBox guest additions setup.
It is apparently called with an already-existing inf file, but I have
no idea why. :|
- The third hunk is a trivial bug that our CreateService just didn't
complain about before r53872/r53886
Though the August minutes were already posted on the forum, they are being
resent here for people who may have missed them.
August Summary
A proposal was made to do winesyncs before a release to force the project to
do a better job keeping things in sync and perhaps do a better job making
syncs feasible/less time consuming. Rejected by plurality of votes.
Questions about how/whether to continue the driver signing program was
raised. An advisory vote was held and the majority wished to continue it in
one form or another. Feedback based on the advisory vote was incorporated
into revised guidelines posted on the Driver Signing wiki page. New projects
are now required to find a sponsor ReactOS "core developer" willing to audit
their code if they wish to get their driver signed.
Decision to integrate arwinss into trunk under a separate directory
structure and make it a compile-time option. Passed by majority vote.
Decision to switch main Linux build server to use cmake. Passed by majority
vote.
September Summary
Agenda
1. CMake Adoption Status
2. Release Preparation, Determination of Release Date
3. Webportal Upgrade Status
4. ReactOS Target Version
Report
1. The build environments for both Windows and Unix have gone through
several release candidates and are effectively finalized. For the Windows
BE an installer release client using MSI instead of NSIS also needs to be
prepared. Minor problems still seem to exist on Mac OS X when using a
combination of GCC and LLVM, but these were deemed non-blockers. Building
ReactOS using CMake has been reported to take more time than using rbuild,
though developers are still working to verify and determine the cause.
Current theory is related to changed debug format and more thorough
dependency checking by CMake. At present the plan is to put the build
environment release candidates on the Linux build servers and determine if
there are any problems. The Windows build servers have already been running
the new build environments for testing purposes.
2. Due to the significant number of regressions and overall bugginess of
ReactOS' current state, release scheduling has been deferred until the next
meeting. A list of regressions and bugs has already been compiled and the
team intends to work its way through the reported issues in the meantime.
At the next meeting, the OS' state will be re-assessed to see whether a
release is viable or not.
3. Most of the modules needed to bridge Drupal with things like Bugzilla
have already been completed. To speed the transition, a decision was made
to retain the current website design. Once the transition is complete, the
web team can go back to updating the site's theme. Desired content changes
will also not block transition to the new backend. No timetable was given
for when the transition would happen.
4. For a while the project adopted the goal of targeting the Windows 2003
kernel and the latest version of Windows for user mode components. Several
developers however raised objections to this and presented examples where
this methodology does not work. A specific example involved symbolic link
support, which required Microsoft rearchitecture not only NTFS but also the
kernel's security systems. Its addition in ReactOS, assuming it is done
correctly, would require changes to the kernel to adopt features from the
Vista kernel, thus violating the kernel target. With these considerations,
the project has decided to set both the user and kernel targets to Windows
2003. Dependency on Wine for many user mode libraries actually complicates
this, as Wine has been adding Vista and later APIs without proper
segregation and the developers will need to figure out how to deal with this
in the long run.
Am 02.10.2011 22:59, schrieb akhaldi(a)svn.reactos.org:
> Author: akhaldi
> Date: Sun Oct 2 20:59:15 2011
> New Revision: 53941
>
> URL: http://svn.reactos.org/svn/reactos?rev=53941&view=rev
> Log:
> [RBUILD]
> * Plug a leak.
Bugfix of the month! ;-)
Hi,
at present I work for mid-sized company for ticketing, parking and mobile
solutions in Germany (and Great Britain). I personally work in a project for
railway services (using gsm-r network). To understand the tools given below I
want to figure out our target and environment in short. We develop for
embedded Linux systems with ARM-CPU and Qt-Framework. Therefore C++ was and
is used as programming language.
Apart from he usual tools like
- make-alike build tools (written in perl - a project specific one)
- regular make files for some special targets
- SVN for source code management
we use some interesting tools to keep the source readable and to preserve a
minimum of source quality automatically (bear in mind we use C++ instead of
C, for our purpose we need to alter some tools for our needs):
- Hudson for automatic build and checking the source (see below)
- cpplint.py (by Google) for some checking the source
- cppcheck for another check of the source
- doxygen for checking the missing documentation (in that special case check
only by tricky configuration instead of costly generating all documentation
files)
- format the source code (after agreement of all devs) in a uniform style with
astyle before commit (for ReactOS better as commit hook)
- finally we gather all check results in one table and mark the results for
hudson as stable (if no errors), failed (in case of any errors), unstable (in
case of some low-prio warnings)
Maybe we can think about some of them, because even if some problems of
development remains, it might give us some edge and may also attract some
devs. I don't make any suggestions, but I want to tell you how others work.
Matthias
PS: We are the first project in the company going that way and other project
groups would like to adapt the way, because they see the benefit for
their/other/future projects.
--
Matthias Kupfer phone +49 371 236 46 52
Wilhelm-Firl-Straße 21 mobile +49 160 859 43 54
09122 Chemnitz, Germany
Hi,
due to a HDD failure in one of our major servers, you've been
encountering services interruptions (mail, svn, web, mainly) this
afternoon and tonight. The issue has been successfully addressed right
now, and the server is back online with its new hard-drive.
Regards,
The ReactOS sysadmins.
Hi,
this is a reminder about the Status meeting, which is to happen
tomorrow, 29th of September at 19:00 UTC. Please don't miss it. The
meeting is declared private. I will lead the meeting, as usual.
Proposed agenda for the meeting:
1. CMake adoption progress.
2. Release preparation status report, deciding on the release date.
3. Webportal upgrade plans.
4. ReactOS target version: strict sticking to it or hybrid.
List of participants:
- Giannis Adamopoulos (smiley1_)
- Johannes Anderwald (janderwald)
- Javier Agustìn Fernàndez Arroyo (elhoir)
- Maciej Bialas (niski)
- Jan Blomqvist-Kinander (JaixBly)
- Aleksey Bragin (abragin)
- Thomas Faber (ThFabba)
- Colin Finck (Colin_Finck)
- Jérôme Gardou (zefklop)
- Danny Götte (dangerground)
- Cameron Gutman (aicom)
- Ziliang Guo (ZWabbit)
- Rafal Harabien (rafalh)
- Andrew Hill (ash77)
- Kamil Hornicek (Pigglesworth)
- Gabriel Ilardi (gabriel_it)
- Alex Ionescu (Alex_Ionescu)
- Amine Khaldi (AmineKhaldi)
- Igor Koshpaev (tower)
- Timo Kreuzer (tkreuzer)
- Matthias Kupfer (Collibri)
- Michael Martin (mjmartin)
- Victor Martinez (vicmarcal)
- Roel Messiant (Mephisto)
- Claudiu Mihail (KlausM)
- Andrew Munger (WaxDragon)
- Ged Murphy (GedMurphy)
- Igor Paliychuk (igorko)
- Sylvain Petreolle (Usurp)
- Hervé Poussineau (hpoussin)
- Daniel Reimer (dreimer)
- Pierre Schweitzer (HeisSpiter)
- Samuel Serapion (encoded)
- Olaf Siejka (Caemyr)
- James Tabor (jimtabor)
- Christoph von Wittich (Christoph_vW)
- Art Yerkes (arty)
WBR,
Aleksey Bragin.
FYI:
This is Linus' interview. http://h30565.www3.hp.com/t5/Feature-
Articles/Linus-Torvalds-s-Lessons-on-Software-Development-Management/
ba-p/440
He very correctly outlines many things. One of the most important:
"The other thing—and it's kind of related—that people seem to get
wrong is to think that the code they write is what matters. No, even
if you wrote 100% of the code, and even if you are the best
programmer in the world and will never need any help with the project
at all, the thing that really matters is the users of the code. The
code itself is unimportant; the project is only as useful as people
actually find it.”
And this:
"Way too many projects seem to think that the code is more important
than the user, and they break things left and right, and they don't
apologize for it, because they feel that they are ‘fixing’ the code
and doing the right thing.”
WBR,
Aleksey Bragin.
Hi all,
Just for your information, I have enabled ACPI for the KVM machine used
by the Linux Testslave today.
For reference, the full VM configuration is like this:
* QEMU/KVM-based i686 ACPI machine
* 256MB of RAM
* 512MB HDD on IDE Primary Master
* ReactOS ISO on IDE Secondary Master
* AMD PCNet-compatible Network Adapter
* COM1 port redirected to a virtual Linux terminal device
* PS/2 mouse
* Tablet pointing device on USB
Usually useful if any KVM machine is controlled over VNC, but probably
not relevant for ReactOS yet.
As you see, there is no virtual sound card (disabled as of 2011-06-07
due to r52098 according to my notes). Is this still correct?
- Colin
Wont be that usual. Happened twice today, still broken atm. I`m not a dev, hence i have no idea how the devs commit stuff works and all the problems you guys have to overcome...
I suppose it is too difficult for you simply to visit http://build.reactos.org/waterfall and just check if its all green (yes, no need to check stdio, just noticing the color). Your time is probably too precious to wait up to 5 bloody minutes, to see if previous build was ok...
I`m not even talking about runtime regressions. Its understandable, that 45 minutes is often too much to wait, but 5??
I`m not even talking about patchbot, why should I? Already did, already tried, to no effect.
If you really care about ROS, then by commiting on a broken trunk, you are practically shooting yourself in your foot. Trunk will be most likely not fixed until several other commits, sometimes a day or so. ISO will not be build. Commits will not be tested, neither by automation, nor by community, bugs will not be reported and regressions will only be found in more distant future. Then, you will ask for regtesting.
You should better start doing it yourself, because you guys too often are not doing even the simplest things to keep trunk clean and working, making development harder for everyone around!
--
With best regards
Caemyr
Hi,
Are there any bugs:
/reactos/dll/directx/ksproxy/allocator.cpp: In member function 'void
CKsAllocator::FreeMediaSamples()':
/reactos/dll/directx/ksproxy/allocator.cpp:586:16: warning: deleting
object of abstract class type 'IMediaSample' which has non-virtual
destructor will cause undefined behaviour [-Wdelete-non-virtual-dtor]
/reactos/dll/directx/ksproxy/proxy.cpp: In function 'HRESULT
CKsProxy_Constructor(IUnknown*, const IID&, void**)':
/reactos/dll/directx/ksproxy/proxy.cpp:3188:16: warning: deleting
object of polymorphic class type 'CKsProxy' which has non-virtual
destructor might cause undefined behaviour [-Wdelete-non-virtual-dtor]
In file included from /reactos/dll/win32/browseui/precomp.h:8:0,
from /reactos/dll/win32/browseui/browseui.cpp:21:
/reactos/lib/atl/atlcom.h: In instantiation of 'static HRESULT
ATL::CComCreator<T1>::CreateInstance(void*, const IID&, void**) [with
T1 = ATL::CComObjectCached<ATL::CComClassFactory>, HRESULT = int, IID
= _GUID, LPVOID = void*]':
/reactos/dll/win32/browseui/browseui.cpp:32:1: required from here
/reactos/lib/atl/atlcom.h:253:5: warning: deleting object of
polymorphic class type 'ATL::CComObjectCached<ATL::CComClassFactory>'
which has non-virtual destructor might cause undefined behaviour
[-Wdelete-non-virtual-dtor]
/reactos/lib/atl/atlcom.h: In instantiation of 'ULONG
ATL::CComObjectCached<Base>::Release() [with Base =
ATL::CComClassFactory, ULONG = unsigned int]':
/reactos/dll/win32/browseui/browseui.cpp:121:1: required from here
/reactos/lib/atl/atlcom.h:304:4: warning: deleting object of
polymorphic class type 'ATL::CComObjectCached<ATL::CComClassFactory>'
which has non-virtual destructor might cause undefined behaviour
[-Wdelete-non-virtual-dtor]
In file included from /reactos/dll/win32/shell32/precomp.h:50:0,
from /reactos/dll/win32/shell32/shell32_main.cpp:22:
/reactos/lib/atl/atlcom.h: In instantiation of 'static HRESULT
ATL::CComCreator<T1>::CreateInstance(void*, const IID&, void**) [with
T1 = ATL::CComObjectCached<ATL::CComClassFactory>, HRESULT = long int,
IID = _GUID, LPVOID = void*]':
/reactos/dll/win32/shell32/shell32_main.cpp:1273:1: required from here
/reactos/lib/atl/atlcom.h:253:5: warning: deleting object of
polymorphic class type 'ATL::CComObjectCached<ATL::CComClassFactory>'
which has non-virtual destructor might cause undefined behaviour
[-Wdelete-non-virtual-dtor]
/reactos/lib/atl/atlcom.h: In instantiation of 'ULONG
ATL::CComObjectCached<Base>::Release() [with Base =
ATL::CComClassFactory, ULONG = long unsigned int]':
/reactos/dll/win32/shell32/shell32_main.cpp:1478:1: required from here
/reactos/lib/atl/atlcom.h:304:4: warning: deleting object of
polymorphic class type 'ATL::CComObjectCached<ATL::CComClassFactory>'
which has non-virtual destructor might cause undefined behaviour
[-Wdelete-non-virtual-dtor]
/reactos/drivers/wdm/audio/backpln/portcls/miniport_dmus.cpp: In
member function 'virtual ULONG CMiniportDMusUART::Release()':
/reactos/drivers/wdm/audio/backpln/portcls/miniport_dmus.cpp:114:20:
warning: deleting object of polymorphic class type 'CMiniportDMusUART'
which has non-virtual destructor might cause undefined behaviour
[-Wdelete-non-virtual-dtor]
/reactos/drivers/wdm/audio/backpln/portcls/miniport_dmus.cpp: In
member function 'virtual ULONG CMiniportDMusUARTStream::Release()':
/reactos/drivers/wdm/audio/backpln/portcls/miniport_dmus.cpp:239:20:
warning: deleting object of polymorphic class type
'CMiniportDMusUARTStream' which has non-virtual destructor might cause
undefined behaviour [-Wdelete-non-virtual-dtor]
/reactos/drivers/wdm/audio/backpln/portcls/miniport_dmus.cpp: In
function 'NTSTATUS NewMiniportDMusUART(IMiniport**, const CLSID&)':
/reactos/drivers/wdm/audio/backpln/portcls/miniport_dmus.cpp:1274:16:
warning: deleting object of polymorphic class type 'CMiniportDMusUART'
which has non-virtual destructor might cause undefined behaviour
[-Wdelete-non-virtual-dtor]
Windows cmake builder is running new BE since yesterday. First thing that i noticed, is the increase of buildtime. Previous version was consistent around 5 minutes, the new candidate - more than 7. I doublechecked it by swapping BE's back and forth.
This might look not serious, but if this problem scales up, we are talking about 35 minutes of buildtime for someone who needed 25 minutes previously.
--
With best regards
Caemyr
Hi,
small note to inform people who were having issues connecting to secured IServ services due to wrong SSL certificate (issued for the wrong address) that the certificate has been renewed today and the issues are gone.
Regards,
Pierre
Sorry but these kinds of fixes are not "readability fixes", in fact they
make things more obtuse.
(*MdlPages << PAGE_SHIFT)) could be interpreted as
*(MdlPages << PAGE_SHIFT).
while
((*MdlPages) << PAGE_SHIFT)
Makes it clear what is happening.
In general, all operations affecting the contents of a *dereference should
be in parens.
Best regards,
Alex Ionescu
On Sun, Sep 11, 2011 at 7:47 AM, <tfaber(a)svn.reactos.org> wrote:
> - ((*MdlPages) << PAGE_SHIFT));
> + (*MdlPages << PAGE_SHIFT));
>
Hi all,
Andrey Karpov of "SiProVer" Ltd (www.viva64.com/ ), the authors of
PVS-Studio, a
statical source code analyzer/checker wrote (in Russian, this
translation is conducted by me):
"Have checked source code of ReactOS with PVS-Studio, I fulfilled
three wishes of mine at once:
Firstly, for a long time I wanted to write an article about ordinary
project. It
is not so interesting to check source code of such projects as Chromium,
It is of too high quality and resources are spending for keeping this level of
quality, resources which are unavailable to ordinary projects.
Secondly, ReactOS appears to be a good example of project, for which high
need of statical analysis of source code can be shown, especially as project
being developed with distributed team of developers with diversely
different experience.
Thirdly, I got confirmation of PVS-Studio getting better and better
and more useful
all along the way..."
Full text of original Russian article is here:
http://habrahabr.ru/blogs/os/127493/
titled on Russian as "PVS-Studio: analysing ReactOS operating system
source code".
Evgeniy Ryzhkov of "SiProVer" adds:
"Soon we will translate and publish article on English. But if you
have questions now
- we are ready for discussion.
If some of English-speaking comrades of ReactOS would like to work
with errors list,
generated with PVS-Studio we have prepared for them translation of
errors explanations, here it is:
http://www.viva64.com/external-pictures/txt/PVS-Studio-vs-ReactOS-en-unicod…
".
Original article refers to long list of generated errors with manually
added explanations for errors
found by their static checker, so this is translated version of that list.
---
Looking backward to few applied patches, it turns out that not all of
them were absolutely useful,
some patches were reversed, etc. But nevertheless, I think it makes
sense to use this tool. They
promised to donate some version of PVS-Studio to project, and it is to
ROS developers to decide is it worth of taking.
What I would suggest: anybody working with some module or part of code
can take corresponding part
of messages (or in future, possibly check with tool only these parts
of interest) and work with them.
Also Karpov gave good advise to check newly written code, since it is
still of interest to developer:
write and time for time test with it.
P.S. Disclaimer: I am not in any connection with "SiProVer"
Regards,
M.A.
Nice work guys.
It was great to watch you pull this together as a team.
Hopefully there's more to come :)
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of akhaldi(a)svn.reactos.org
Sent: 09 September 2011 11:55
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [akhaldi] 53653: [SHELL32] * Reintegrate the c++ shell32 branch. Exemplary team-work.. kudos ! * Better code quality, more tests run with less failures... and more. * Dedicated to everyone who help...
Author: akhaldi
Date: Fri Sep 9 10:55:09 2011
New Revision: 53653
URL: http://svn.reactos.org/svn/reactos?rev=53653&view=rev
Log:
[SHELL32]
* Reintegrate the c++ shell32 branch. Exemplary team-work.. kudos !
* Better code quality, more tests run with less failures... and more.
* Dedicated to everyone who helped ;)
Le 23/08/2011 10:58, tkreuzer(a)svn.reactos.org a écrit :
> Author: tkreuzer
> Date: Tue Aug 23 08:58:15 2011
> New Revision: 53399
>
> URL: http://svn.reactos.org/svn/reactos?rev=53399&view=rev
> Log:
> [VMWINST] Fix amd64 build
>
What about :
[VMWINST] Get rid of this useless relic.
I mean it's something we have to maintain, it was written for
antediluvian vmware versions, and I see no reason to have such a thing.
I may as well write an application to install specific ATI card drivers,
or intel chipset drivers...
Hello Claudiu!
I notice some weird tab/spaces modifications here.
Regards.
Jérôme.
Le 03/09/2011 16:20, cmihail(a)svn.reactos.org a écrit :
> Author: cmihail
> Date: Sat Sep 3 14:20:03 2011
> New Revision: 53543
>
> URL: http://svn.reactos.org/svn/reactos?rev=53543&view=rev
> Log:
> [shell32.dll]
> - Fix bug related to correct error code returning in delete_files. The value of 1026 was revealed to be returned by windows 2003 server. Score several passed winetests.
> - Fix a bug in ShellLink::SetShowCmd and score one more passed winetest
>
> Modified:
> branches/shell32_new-bringup/dll/win32/shell32/shelllink.cpp
> branches/shell32_new-bringup/dll/win32/shell32/shlfileop.cpp
>
>
Am 03.09.2011 02:08, schrieb cmihail(a)svn.reactos.org:
> Author: cmihail
> Date: Sat Sep 3 00:08:11 2011
> New Revision: 53537
>
> URL:http://svn.reactos.org/svn/reactos?rev=53537&view=rev
> Log:
> [shell32.dll]
> [FORMATTING]
> - Format the code to a more acceptable level. This is just for my sanity while sifting through it.
> /* skip the remaining spaces */
> - while (*cs==0x0009 || *cs==0x0020) {
> + while (*cs==0x0009 || *cs==0x0020)
> + {
> cs++;
> }
> if (*cs==0)
>
Please don't mix tabs and spaces or we'll end up looking like GNU style ;-)
Since the file already uses spaces (as we use almost everywhere), please
stick to that here.
Regards,
Timo
Hey again,
On 2011-09-01 15:18, dchapyshev(a)svn.reactos.org wrote:
> --- trunk/reactos/dll/win32/netshell/lanstatusui.c [iso-8859-1] (original)
> +++ trunk/reactos/dll/win32/netshell/lanstatusui.c [iso-8859-1] Thu Sep 1 13:18:22 2011
> @@ -179,7 +179,7 @@
> pContext->Status = 3;
> }
> }
> - else if (IfEntry.dwOperStatus == MIB_IF_OPER_STATUS_UNREACHABLE || MIB_IF_OPER_STATUS_DISCONNECTED)
> + else if (IfEntry.dwOperStatus == MIB_IF_OPER_STATUS_UNREACHABLE | MIB_IF_OPER_STATUS_DISCONNECTED)
> {
> if (pContext->Status != 4)
> {
>
this should more likely be
else if (IfEntry.dwOperStatus == MIB_IF_OPER_STATUS_UNREACHABLE ||
IfEntry.dwOperStatus == MIB_IF_OPER_STATUS_DISCONNECTED)
Some nice fixes right there by the way. :)
*hopes this might fix some evil bugs that have been lurking* ;)
Thanks,
Tom
Funny how Windows works without these hacks.
Let's hide more bugs :D
Best regards,
Alex Ionescu
On Tue, Aug 30, 2011 at 12:01 PM, <tkreuzer(a)svn.reactos.org> wrote:
> Author: tkreuzer
> Date: Tue Aug 30 12:01:01 2011
> New Revision: 53496
>
> URL: http://svn.reactos.org/svn/reactos?rev=53496&view=rev
> Log:
> [HAL]
> We cannot make any assumptions about the latency whith which the timer
> interrupt fires after a rollover, since VBox (other VMs probably as well)
> doesn't always meet this. Add another check to KeQueryPerformanceCounter
> that gracefully handles missing interrupts. Also raise to DISPATCH_LEVEL,
> since the function is not reentrant.
>
> Modified:
> trunk/reactos/hal/halx86/generic/timer.c
>
> Modified: trunk/reactos/hal/halx86/generic/timer.c
> URL:
> http://svn.reactos.org/svn/reactos/trunk/reactos/hal/halx86/generic/timer.c…
>
> ==============================================================================
> --- trunk/reactos/hal/halx86/generic/timer.c [iso-8859-1] (original)
> +++ trunk/reactos/hal/halx86/generic/timer.c [iso-8859-1] Tue Aug 30
> 12:01:01 2011
> @@ -253,6 +253,7 @@
> {
> LARGE_INTEGER CurrentPerfCounter;
> ULONG CounterValue, ClockDelta;
> + KIRQL OldIrql;
>
> /* If caller wants performance frequency, return hardcoded value */
> if (PerformanceFrequency) PerformanceFrequency->QuadPart =
> PIT_FREQUENCY;
> @@ -262,6 +263,10 @@
>
> /* Check if interrupts are disabled */
> if(!(__readeflags() & EFLAGS_INTERRUPT_MASK)) return HalpPerfCounter;
> +
> + /* Raise irql to DISPATCH_LEVEL */
> + OldIrql = KeGetCurrentIrql();
> + if (OldIrql < DISPATCH_LEVEL) KfRaiseIrql(DISPATCH_LEVEL);
>
> do
> {
> @@ -287,13 +292,21 @@
> /* Add the clock delta */
> CurrentPerfCounter.QuadPart += ClockDelta;
>
> - /* This must be true unless HalpPerfCounter has changed sign,
> - which takes approximately 245,118 years */
> - ASSERT(CurrentPerfCounter.QuadPart >= HalpLastPerfCounter.QuadPart);
> + /* Check if the value is smaller then before, this means, we somehow
> + missed an interrupt. This is a sign that the timer interrupt
> + is very inaccurate. Probably a virtual machine. */
> + if (CurrentPerfCounter.QuadPart < HalpLastPerfCounter.QuadPart)
> + {
> + /* We missed an interrupt. Assume we will receive it later */
> + CurrentPerfCounter.QuadPart += HalpCurrentRollOver;
> + }
>
> /* Update the last counter value */
> HalpLastPerfCounter = CurrentPerfCounter;
>
> + /* Restore previous irql */
> + if (OldIrql < DISPATCH_LEVEL) KfLowerIrql(OldIrql);
> +
> /* Return the result */
> return CurrentPerfCounter;
> }
>
>
>
Hi,
I am the maintainer of uranos (http://uranos.sf.net) and want to
implement the unattended setup of ReactOS into uranos. I read that you
have implemented a answer file into ReactOS.
Because of uranos does all the parts which is done by the txtinstaller
from ReactOS (partition disk, write mbr, copy files and so on) from a
linux boot environment - I want to know if it is possible to place the
unattended.inf into the filesystem so the ReactOS is read the file in
the first GUI boot.
Thank you! Cheers mario
I want to do some testing on physical machines until now was doing the
vbox will charge the machine a good desepenho
memory and I'll need to spend sitema ospedeiro vbox and the problem
and that the machines do not have a serial port
was taking a look at these wiki but did not see exact references on
how to get the debug log on the cable network
vbox but works well for the network that will be with you
http://www.reactos.org/wiki/Debugginghttp://www.reactos.org/wiki/ReactOS_Remote_Debugger#TCP.2FIP_.28QEMU_only.29
I obeservado that companies have made the opening of perfius on
social sites like orkte, face buk to have a closer contacts with its
customers
Suggestions
Taves Foce the time to develop a page-pink similar to orkut only for
pelomenos emvolvidos list of ros-dev communicate mellhor we take for
example the option orkut This allows you to replaying a message to the
entire group or just for some or open a profile but it would be the
maintainer of the profile to select some options
has some social networks that desacoselho to be very open but
partially open orkut and where he has partial control of where and
where does the information would be very nice to have something in
ros.org or maybe opening a profile on some these social networks
a method would be to discuss and APREDE programs in a more dynamic
A Matter discursoes saw some about the future of Roses
A sugentao as a powerful gaming machine MaxiVista server and at the
same time continue the development of financial markets and earn some
cash to the developers and everyone involved in the project we will
take as examples the maximum this game is notable that the projects do
not get for the day for the night
When complete the installation of the driver placa GF8200A shipeset
8200 Through the message that the dll not found Wow32.dll
MainFrameBase::OpenShellFolders():parent_pidl=C:\Documents and
Settgs\Administrator\Desktop
MainFrameBase::OpenShellFolders(): pidl_abs=(null)
(drivers\filesystems\cdfs\create.c:148) Status c0000013
(drivers\filesystems\cdfs\create.c:148) Status c0000013
(drivers\flesystems\cdfs\common.c:196) STATUS_VERIFY_REQUIRED
(drivers\filesystems\cdfs\fsctl.c:590) CDFS: IRP_MN_VERIFY_VOLUME
(drivers\filesystems\cdfs\fsctl.c:467) CdfsVerifyVolume() called
(drivers\filesystems\cdfs\fsctl.c:494) Deviceobject B1285A48 Device
to verify B1285A48
(drivers\filesystems\cdfs\devctrl.c:34) FIXME: CdfsDevieControl called
without FileObjec!
(drivers\filesystems\cdfs\fsct.c:511) Different volume!
(drives\filesystems\cdfs\fsctl.c:518) OenFile \ RefCount 1
(drivers\fiesystems\cdfs\fsctl.c:518) OpenFie \loader RefCount 0
(drivers\flesystems\cdfs\fsctl.c:518) OpenFile \reactos RefCount 0
(drivers\filesystems\cdfs\fsctl.c:518) OenFile \reactos\system32 RefCoun 0
(drivers\filesystems\cdfs\common.c203) IoVerifyVolume() returned
(Status c0000012)
(drivers\filesysems\cdfs\create.c:148) Status 8000016
MainFrameBase::OpenShellFolders():parent_pidl=(null)
MainFrameBase:OpenShellFolders(): pidl_abs=D:\
MDIMainFrame PM_OPEN_WINDOW: pat=D:\
MainFrameBase::OpenShellFolders():rent_pidl=D:\
(lib\rtl\path.c:256) don't keep the directory handl open on removable media
(dll\ntdll\ldr\utils.c:2301) Faile to create or open dll section
of'WOW32.DLL' (Status c0000135)
(d\ntdll\ldr\utils.c:1512) failed tload WOW32.DLL
(subsystems\win32csrss\csrsrv\api\wapi.c:115) CSR:received hard error c0000135
WARNING: MmLockPageableDataSectio at ntoskrnl\mm\ARM3\drvmgmt.c:62s
UNIMPLEMENTED!
WARNING: MmUnlockPageableImageSecon at ntoskrnl\mm\ARM3\drvmgmt.c: is
UNIMPLEMENTED!
(ntoskrnl\se\semgr.c:299) SidInTok Calls: 30000
2011/8/26, ros-dev-request(a)reactos.org <ros-dev-request(a)reactos.org>:
> Send Ros-dev mailing list submissions to
> ros-dev(a)reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.reactos.org/mailman/listinfo/ros-dev
> or, via email, send a message with subject or body 'help' to
> ros-dev-request(a)reactos.org
>
> You can reach the person managing the list at
> ros-dev-owner(a)reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Debug Buildslave Maintenance (caemyr(a)myopera.com)
> 2. Re: Debug Buildslave Maintenance (Eric Kohl)
> 3. Re: [ros-diffs] [fireball] 53446: [NTDLL/LDR] - Fix wrong
> loop condition which would often lead to heap underread. - Fix
> wrong subkey string length calculation, which would result in an
> incorrect string being used... (Ged Murphy)
> 4. Re: [ros-diffs] [fireball] 53446: [NTDLL/LDR] - Fix wrong
> loop condition which would often lead to heap underread. - Fix
> wrong subkey string length calculation, which would result in an
> incorrect string being used... (Aleksey Bragin)
> 5. Re: Debug Buildslave Maintenance (Aleksey Bragin)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 25 Aug 2011 23:29:55 +0200
> From: caemyr(a)myopera.com
> Subject: Re: [ros-dev] Debug Buildslave Maintenance
> To: "ReactOS Development List" <ros-dev(a)reactos.org>
> Message-ID:
> <1314307795.18690.140258133790149(a)webmail.messagingengine.com>
> Content-Type: text/plain; charset="us-ascii"
>
> @Eric
>
> http://reactos.org/testman/compare.php?ids=7429,7579
> http://reactos.org/testman/detail.php?id=2639952
>
> Please find that the crash is not CMake related, and CMake build is not
> inherently broken.
>
> On Thu, 25 Aug 2011 23:03 +0200, "Pierre Schweitzer"
> <pierre.schweitzer(a)reactos.org> wrote:
>> Hi,
>>
>> finally.
>> Colin and I are pleased to announce you that ReactOS Linux KVM tests are
>> back online and working. You can find the first tests results (on r53383)
>> sent tonight by the testbot on testman: http://www.reactos.org/testman/.
>>
>> Regards,
>> Pierre.
>>
>> ReactOS Development List <ros-dev(a)reactos.org> wrote on Sat, August 20th,
>> 2011, 4:24 PM:
>> > Timo Kreuzer <timo.kreuzer(a)web.de> wrote:
>> > > What about fixing release buildbot first?
>> >
>> > It's still a private machine owned and administered solely by Christoph.
>> >
>> > As long as I can't even reach him by phone, we can only wait.
>> >
>> >
>> > > And is there a chance, maybe in the future, to switch buildbots more
>> > > easily, to have a backup solution running?
>> >
>> > First of all, we hope that we can get the same reliability as our other
>> > servers after reinstalling the server OS, giving more ReactOS admins
>> > access to the machine and adding monitoring.
>> > The current OS was meant to be reinstalled for quite a long time, but up
>> >
>> > to now, nobody with physical access to the machine had any time to do
>> > it.
>> >
>> > If such problems continue to exist afterwards, we can try to set up a
>> > fallback system, but this would require an equally configured and
>> > powerful Linux machine first.
>> >
>> >
>> > > One week without debug builds is a serious thing.
>> >
>> > I hope you're aware that builds are still properly uploaded, it's only
>> > the testing step which fails.
>> >
>> >
>> > - Colin
>> >
>> > _______________________________________________
>> > Ros-dev mailing list
>> > Ros-dev(a)reactos.org
>> > http://www.reactos.org/mailman/listinfo/ros-dev
>>
>> _______________________________________________
>> Ros-dev mailing list
>> Ros-dev(a)reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
> With best regards
> Caemyr
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 26 Aug 2011 01:01:40 +0200
> From: Eric Kohl <eric.kohl(a)t-online.de>
> Subject: Re: [ros-dev] Debug Buildslave Maintenance
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <4E56D454.6060606(a)t-online.de>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Olaf,
>
> I am already investigating the services test issues. One of my first
> findings is that the current widl seems to mess up value ranges in some
> cases. This is the cause of the following errors:
> err:(dll/win32/rpcrt4/ndr_marshall.c:6496) value exceeded bounds: 918,
> low: 0, high: 514
>
> <rant>
> It is pretty annoying that jgardou updated rpcrt4, widl and other
> components without proper testing. At least he should have posted a bug
> list BEFORE he comitted the new stuff.
> </rant>
>
> Regards
> Eric
>
>> @Eric
>>
>> http://reactos.org/testman/compare.php?ids=7429,7579
>> http://reactos.org/testman/detail.php?id=2639952
>>
>> Please find that the crash is not CMake related, and CMake build is not
>> inherently broken.
>>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 26 Aug 2011 09:05:21 +0100
> From: "Ged Murphy" <gedmurphy.maillists(a)gmail.com>
> Subject: Re: [ros-dev] [ros-diffs] [fireball] 53446: [NTDLL/LDR] - Fix
> wrong loop condition which would often lead to heap underread. - Fix
> wrong subkey string length calculation, which would result in an
> incorrect string being used...
> To: <ros-dev(a)reactos.org>
> Message-ID: <004201cc63c6$e7a44a40$b6ecdec0$(a)gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> fireball(a)svn.reactos.org wrote:
>
>> - Use Zw* functions instead of Nt* where necessary in
>> LdrQueryImageFileKeyOption().
>
> 'where necessary'm I don't understand this change.
> People prefer (and Microsoft recommend) that Nt* is used in usermode.
> Nt and Zw APIs point to the same address in usermode, so why is it
> necessary?
>
> Ged.
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 26 Aug 2011 12:13:26 +0400
> From: Aleksey Bragin <aleksey(a)reactos.org>
> Subject: Re: [ros-dev] [ros-diffs] [fireball] 53446: [NTDLL/LDR] - Fix
> wrong loop condition which would often lead to heap underread. - Fix
> wrong subkey string length calculation, which would result in an
> incorrect string being used...
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <7766A32C-3CB0-446A-96F4-4EDC73BC3A29(a)reactos.org>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
>
> On Aug 26, 2011, at 12:05 PM, Ged Murphy wrote:
>
>> fireball(a)svn.reactos.org wrote:
>>
>>> - Use Zw* functions instead of Nt* where necessary in
>>> LdrQueryImageFileKeyOption().
>>
>> 'where necessary'm I don't understand this change.
>> People prefer (and Microsoft recommend) that Nt* is used in usermode.
>> Nt and Zw APIs point to the same address in usermode, so why is it
>> necessary?
>
> This was a test for attention, and so far I got a few notices in IRC
> and one in ros-dev. Good!
>
> Seriously, the change slipped through because I was editing source
> code of both RTL (which works both at umode and kmode) and NTDLL/LDR
> (which is only umode) a while ago. Of course, Nt is "preferable" in
> usermode because there is just no reason to use Zw there.
>
>
> WBR,
> Aleksey Bragin.
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 26 Aug 2011 12:15:24 +0400
> From: Aleksey Bragin <aleksey(a)reactos.org>
> Subject: Re: [ros-dev] Debug Buildslave Maintenance
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <1F3FEE77-59BC-4D24-83A9-5D280FB45966(a)reactos.org>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
>
> On Aug 26, 2011, at 3:01 AM, Eric Kohl wrote:
>
>> <rant>
>> It is pretty annoying that jgardou updated rpcrt4, widl and other
>> components without proper testing. At least he should have posted a
>> bug list BEFORE he comitted the new stuff.
>> </rant>
> I also ranted about that. In fact that's why I stopped syncing rpcrt4
> some time ago - because new version always gave problems. So I wanted
> to solve problems first and only then commit.
>
> But, OK, as Olaf said - if something needs to be done, let's simply
> do that and fix everything which broke ;).
>
> WBR,
> Aleksey.
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> End of Ros-dev Digest, Vol 84, Issue 22
> ***************************************
>
When complete the installation of the driver placa GF8200A shipeset
8200 Through the message that the dll not found Wow32.dll
2011/8/26, ros-dev-request(a)reactos.org <ros-dev-request(a)reactos.org>:
> Send Ros-dev mailing list submissions to
> ros-dev(a)reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.reactos.org/mailman/listinfo/ros-dev
> or, via email, send a message with subject or body 'help' to
> ros-dev-request(a)reactos.org
>
> You can reach the person managing the list at
> ros-dev-owner(a)reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Debug Buildslave Maintenance (caemyr(a)myopera.com)
> 2. Re: Debug Buildslave Maintenance (Eric Kohl)
> 3. Re: [ros-diffs] [fireball] 53446: [NTDLL/LDR] - Fix wrong
> loop condition which would often lead to heap underread. - Fix
> wrong subkey string length calculation, which would result in an
> incorrect string being used... (Ged Murphy)
> 4. Re: [ros-diffs] [fireball] 53446: [NTDLL/LDR] - Fix wrong
> loop condition which would often lead to heap underread. - Fix
> wrong subkey string length calculation, which would result in an
> incorrect string being used... (Aleksey Bragin)
> 5. Re: Debug Buildslave Maintenance (Aleksey Bragin)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 25 Aug 2011 23:29:55 +0200
> From: caemyr(a)myopera.com
> Subject: Re: [ros-dev] Debug Buildslave Maintenance
> To: "ReactOS Development List" <ros-dev(a)reactos.org>
> Message-ID:
> <1314307795.18690.140258133790149(a)webmail.messagingengine.com>
> Content-Type: text/plain; charset="us-ascii"
>
> @Eric
>
> http://reactos.org/testman/compare.php?ids=7429,7579
> http://reactos.org/testman/detail.php?id=2639952
>
> Please find that the crash is not CMake related, and CMake build is not
> inherently broken.
>
> On Thu, 25 Aug 2011 23:03 +0200, "Pierre Schweitzer"
> <pierre.schweitzer(a)reactos.org> wrote:
>> Hi,
>>
>> finally.
>> Colin and I are pleased to announce you that ReactOS Linux KVM tests are
>> back online and working. You can find the first tests results (on r53383)
>> sent tonight by the testbot on testman: http://www.reactos.org/testman/.
>>
>> Regards,
>> Pierre.
>>
>> ReactOS Development List <ros-dev(a)reactos.org> wrote on Sat, August 20th,
>> 2011, 4:24 PM:
>> > Timo Kreuzer <timo.kreuzer(a)web.de> wrote:
>> > > What about fixing release buildbot first?
>> >
>> > It's still a private machine owned and administered solely by Christoph.
>> >
>> > As long as I can't even reach him by phone, we can only wait.
>> >
>> >
>> > > And is there a chance, maybe in the future, to switch buildbots more
>> > > easily, to have a backup solution running?
>> >
>> > First of all, we hope that we can get the same reliability as our other
>> > servers after reinstalling the server OS, giving more ReactOS admins
>> > access to the machine and adding monitoring.
>> > The current OS was meant to be reinstalled for quite a long time, but up
>> >
>> > to now, nobody with physical access to the machine had any time to do
>> > it.
>> >
>> > If such problems continue to exist afterwards, we can try to set up a
>> > fallback system, but this would require an equally configured and
>> > powerful Linux machine first.
>> >
>> >
>> > > One week without debug builds is a serious thing.
>> >
>> > I hope you're aware that builds are still properly uploaded, it's only
>> > the testing step which fails.
>> >
>> >
>> > - Colin
>> >
>> > _______________________________________________
>> > Ros-dev mailing list
>> > Ros-dev(a)reactos.org
>> > http://www.reactos.org/mailman/listinfo/ros-dev
>>
>> _______________________________________________
>> Ros-dev mailing list
>> Ros-dev(a)reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
> With best regards
> Caemyr
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 26 Aug 2011 01:01:40 +0200
> From: Eric Kohl <eric.kohl(a)t-online.de>
> Subject: Re: [ros-dev] Debug Buildslave Maintenance
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <4E56D454.6060606(a)t-online.de>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Olaf,
>
> I am already investigating the services test issues. One of my first
> findings is that the current widl seems to mess up value ranges in some
> cases. This is the cause of the following errors:
> err:(dll/win32/rpcrt4/ndr_marshall.c:6496) value exceeded bounds: 918,
> low: 0, high: 514
>
> <rant>
> It is pretty annoying that jgardou updated rpcrt4, widl and other
> components without proper testing. At least he should have posted a bug
> list BEFORE he comitted the new stuff.
> </rant>
>
> Regards
> Eric
>
>> @Eric
>>
>> http://reactos.org/testman/compare.php?ids=7429,7579
>> http://reactos.org/testman/detail.php?id=2639952
>>
>> Please find that the crash is not CMake related, and CMake build is not
>> inherently broken.
>>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 26 Aug 2011 09:05:21 +0100
> From: "Ged Murphy" <gedmurphy.maillists(a)gmail.com>
> Subject: Re: [ros-dev] [ros-diffs] [fireball] 53446: [NTDLL/LDR] - Fix
> wrong loop condition which would often lead to heap underread. - Fix
> wrong subkey string length calculation, which would result in an
> incorrect string being used...
> To: <ros-dev(a)reactos.org>
> Message-ID: <004201cc63c6$e7a44a40$b6ecdec0$(a)gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> fireball(a)svn.reactos.org wrote:
>
>> - Use Zw* functions instead of Nt* where necessary in
>> LdrQueryImageFileKeyOption().
>
> 'where necessary'm I don't understand this change.
> People prefer (and Microsoft recommend) that Nt* is used in usermode.
> Nt and Zw APIs point to the same address in usermode, so why is it
> necessary?
>
> Ged.
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 26 Aug 2011 12:13:26 +0400
> From: Aleksey Bragin <aleksey(a)reactos.org>
> Subject: Re: [ros-dev] [ros-diffs] [fireball] 53446: [NTDLL/LDR] - Fix
> wrong loop condition which would often lead to heap underread. - Fix
> wrong subkey string length calculation, which would result in an
> incorrect string being used...
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <7766A32C-3CB0-446A-96F4-4EDC73BC3A29(a)reactos.org>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
>
> On Aug 26, 2011, at 12:05 PM, Ged Murphy wrote:
>
>> fireball(a)svn.reactos.org wrote:
>>
>>> - Use Zw* functions instead of Nt* where necessary in
>>> LdrQueryImageFileKeyOption().
>>
>> 'where necessary'm I don't understand this change.
>> People prefer (and Microsoft recommend) that Nt* is used in usermode.
>> Nt and Zw APIs point to the same address in usermode, so why is it
>> necessary?
>
> This was a test for attention, and so far I got a few notices in IRC
> and one in ros-dev. Good!
>
> Seriously, the change slipped through because I was editing source
> code of both RTL (which works both at umode and kmode) and NTDLL/LDR
> (which is only umode) a while ago. Of course, Nt is "preferable" in
> usermode because there is just no reason to use Zw there.
>
>
> WBR,
> Aleksey Bragin.
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 26 Aug 2011 12:15:24 +0400
> From: Aleksey Bragin <aleksey(a)reactos.org>
> Subject: Re: [ros-dev] Debug Buildslave Maintenance
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <1F3FEE77-59BC-4D24-83A9-5D280FB45966(a)reactos.org>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
>
> On Aug 26, 2011, at 3:01 AM, Eric Kohl wrote:
>
>> <rant>
>> It is pretty annoying that jgardou updated rpcrt4, widl and other
>> components without proper testing. At least he should have posted a
>> bug list BEFORE he comitted the new stuff.
>> </rant>
> I also ranted about that. In fact that's why I stopped syncing rpcrt4
> some time ago - because new version always gave problems. So I wanted
> to solve problems first and only then commit.
>
> But, OK, as Olaf said - if something needs to be done, let's simply
> do that and fix everything which broke ;).
>
> WBR,
> Aleksey.
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> End of Ros-dev Digest, Vol 84, Issue 22
> ***************************************
>
Hello all,
The Debug Buildslave will be down for maintenance throughout the next
week. We hope to have it fully working again by next weekend.
In the process of this maintenance, the OS will be reinstalled to match
the one we already use on our other servers. Besides, more of our
administrators will get access to the machine, so that further problems
can be debugged more easily.
- Colin
fireball(a)svn.reactos.org wrote:
> - Use Zw* functions instead of Nt* where necessary in LdrQueryImageFileKeyOption().
'where necessary'm I don't understand this change.
People prefer (and Microsoft recommend) that Nt* is used in usermode.
Nt and Zw APIs point to the same address in usermode, so why is it necessary?
Ged.
Hi,
this is a reminder about the Status meeting, which is to happen
tomorrow, 25th of August at 19:00 UTC. Please don't miss it.
Proposed agenda for the meeting:
1. Arwinss adoption voting.
2. CMake adoption voting.
3. Release preparation status report, deciding on the next release date.
4. Driver signing. Discussing possible threats and deciding on an
official position wrt driver signing in future.
4. Party related to GSoC results.
I propose to move individual devs status reports to ros-dev mailing
list, because there is no reason to just sit in the irc channel and
listen to them for hours.
List of participants:
- Giannis Adamopoulos (smiley1_)
- Johannes Anderwald (janderwald)
- Javier Agustìn Fernàndez Arroyo (elhoir)
- Maciej Bialas (niski)
- Jan Blomqvist-Kinander (JaixBly)
- Aleksey Bragin (abragin)
- Thomas Faber (ThFabba)
- Colin Finck (Colin_Finck)
- Jérôme Gardou (zefklop)
- Danny Götte (dangerground)
- Cameron Gutman (aicom)
- Ziliang Guo (ZWabbit)
- Rafal Harabien (rafalh)
- Andrew Hill (ash77)
- Kamil Hornicek (Pigglesworth)
- Gabriel Ilardi (gabriel_it)
- Alex Ionescu (Alex_Ionescu)
- Amine Khaldi (AmineKhaldi)
- Igor Koshpaev (tower)
- Timo Kreuzer (tkreuzer)
- Matthias Kupfer (Collibri)
- Michael Martin (mjmartin)
- Victor Martinez (vicmarcal)
- Roel Messiant (Mephisto)
- Claudiu Mihail (KlausM)
- Andrew Munger (WaxDragon)
- Ged Murphy (GedMurphy)
- Igor Paliychuk (igorko)
- Sylvain Petreolle (Usurp)
- Hervé Poussineau (hpoussin)
- Daniel Reimer (dreimer)
- Pierre Schweitzer (HeisSpiter)
- Samuel Serapion (encoded)
- Olaf Siejka (Caemyr)
- James Tabor (jimtabor)
- Christoph von Wittich (Christoph_vW)
- Art Yerkes (arty)
WBR,
Aleksey Bragin.
r53425 broke CMake build. To make the things worse, this is our only working test\iso provider at the moment. I would reckon fixing it a priority.
CMakeFiles/hal.dir/generic/halinit.c.obj: In function `HalInitSystem@8':
P:/Trunk_slave/x86_CMake/build/hal/halx86/generic/halinit.c:116: undefined reference to `HaliInitPnpDriver@0'
collect2: ld returned 1 exit status
--
With best regards
Caemyr
LwIP is in the final stage of testing, pending one bug fix before all known bugs are fixed. I would greatly appreciate everyone to try it and reply to this email with the results of your tests. I've already tried many apps including telnetd, chargen, and abyss web server, samba tng, and Opera 9.6. During my testing, the lwIP implementation performed flawlessly. It handled several chargen sessions while serving web pages and servicing open telnet sessions plus being probed by nmap. The only thing that finally killed the server was a pool leak that caused a win32k assert failure. I also ran a BitTorrent download and it peaked at 2.3 MB/s down. Web browsing is an absolute pleasure on lwIP. It really feels like I'm browsing on the host system directly. There are no more stutters like oskit had. I'd encourage everyone to try it. It's surprising how well it works especially since I thought oskit was fairly good. My testing on lwIP has been perfect and I hope everyone else has a similar experience. Please only report bugs that don't also happen with oskit. Happy testing!
LwIP ISO Link: http://www.mediafire.com/?d6j4qwz8vgabj9i
Thanks in advance,
Cameron
LinkedIn
------------
Eu gostaria de adicioná-lo à minha rede profissional no LinkedIn.
-dimas
dimas francisco
Profissional de Serviços da informação
São Paulo e redondezas, Brasil
Confirme que você conhece dimas francisco
https://www.linkedin.com/e/-w5xu2x-gre1loc3-34/isd/3867275872/u_LdDFjC/
--
(c) 2011, LinkedIn Corporation
And, you have, of course, confirmed that this piece of kernel code is wrong,
and that DevMgr/Cfgapi/SetupApi are doing the right thing, right?
So if I was to reverse engineer ntoskrnl I wouldn't discover that it was
actually doing the same thing as the un-"fixed" code, right?
Best regards,
Alex Ionescu
On Sun, Aug 14, 2011 at 10:44 AM, <cgutman(a)svn.reactos.org> wrote:
> Author: cgutman
> Date: Sun Aug 14 14:44:34 2011
> New Revision: 53232
>
> URL: http://svn.reactos.org/svn/reactos?rev=53232&view=rev
> Log:
> [NTOSKRNL]
> - Fix NULL termination of strings in IoGetDeviceProperty
> - Fixes garbage displayed in the Enumerator field of the device manager
> property page
>
> Modified:
> trunk/reactos/ntoskrnl/io/pnpmgr/pnpmgr.c
>
> Modified: trunk/reactos/ntoskrnl/io/pnpmgr/pnpmgr.c
> URL:
> http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/pnpmgr/pnpmgr.…
>
> ==============================================================================
> --- trunk/reactos/ntoskrnl/io/pnpmgr/pnpmgr.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/io/pnpmgr/pnpmgr.c [iso-8859-1] Sun Aug 14
> 14:44:34 2011
> @@ -3467,6 +3467,8 @@
> NTSTATUS Status = STATUS_BUFFER_TOO_SMALL;
> GUID BusTypeGuid;
> POBJECT_NAME_INFORMATION ObjectNameInfo = NULL;
> + BOOLEAN NullTerminate = FALSE;
> +
> DPRINT("IoGetDeviceProperty(0x%p %d)\n", DeviceObject, DeviceProperty);
>
> /* Assume failure */
> @@ -3517,7 +3519,10 @@
> /* Get the name from the path */
> EnumeratorNameEnd = wcschr(DeviceInstanceName,
> OBJ_NAME_PATH_SEPARATOR);
> ASSERT(EnumeratorNameEnd);
> -
> +
> + /* This string needs to be NULL-terminated */
> + NullTerminate = TRUE;
> +
> /* This is the format of the returned data */
> PIP_RETURN_DATA((EnumeratorNameEnd - DeviceInstanceName) *
> sizeof(WCHAR),
> DeviceInstanceName);
> @@ -3567,7 +3572,10 @@
> /* It's up to the caller to try again */
> Status = STATUS_BUFFER_TOO_SMALL;
> }
> -
> +
> + /* This string needs to be NULL-terminated */
> + NullTerminate = TRUE;
> +
> /* Return if successful */
> if (NT_SUCCESS(Status))
> PIP_RETURN_DATA(ObjectNameInfo->Name.Length,
>
> ObjectNameInfo->Name.Buffer);
> @@ -3633,15 +3641,14 @@
> else if (NT_SUCCESS(Status))
> {
> /* We know up-front how much data to expect, check the caller's
> buffer */
> - *ResultLength = ReturnLength;
> - if (ReturnLength <= BufferLength)
> + *ResultLength = ReturnLength + (NullTerminate ?
> sizeof(UNICODE_NULL) : 0);
> + if (*ResultLength <= BufferLength)
> {
> /* Buffer is all good, copy the data */
> RtlCopyMemory(PropertyBuffer, Data, ReturnLength);
>
> - /* Check for properties that require a null-terminated string
> */
> - if ((DeviceProperty == DevicePropertyEnumeratorName) ||
> - (DeviceProperty ==
> DevicePropertyPhysicalDeviceObjectName))
> + /* Check if we need to NULL-terminate the string */
> + if (NullTerminate)
> {
> /* Terminate the string */
> ((PWCHAR)PropertyBuffer)[ReturnLength / sizeof(WCHAR)] =
> UNICODE_NULL;
>
>
>
Never depend on this!
Depending on funcs.h including types.h of the same module is fine, but you
should not depend on rtlfuncs dependong on pstypes.
Best regards,
Alex Ionescu
On Sun, Aug 14, 2011 at 8:57 AM, <akhaldi(a)svn.reactos.org> wrote:
> #define NTOS_MODE_USER
> -#include <ndk/pstypes.h>
> #include <ndk/rtlfuncs.h>
>
Maybe you could add all the other changes with checkin comments such
as "this should be sent upstream to wine" to that plan too :)
That practice has become quite common these days.
Ged.
Sent from my Windows Phone From: Jérôme Gardou
Sent: 09 August 2011 22:32
To: ros-dev(a)reactos.org
Subject: Re: [ros-dev] [ros-diffs] [jgardou] 53152: [RPCRT4] - restore
lost ros specific change. Thanks Vic.
Don't worry, it's part of the plan!
Le 09/08/2011 23:29, Ged Murphy a écrit :
> Call me nuts, but why don't you add a ros_diff patch so it doesn't get
> lost again???
> From: jgardou(a)svn.reactos.org
> Sent: 09 August 2011 18:43
> To: ros-diffs(a)reactos.org
> Subject: [ros-diffs] [jgardou] 53152: [RPCRT4] - restore lost ros
> specific change. Thanks Vic.
> Author: jgardou
> Date: Tue Aug 9 17:43:37 2011
> New Revision: 53152
>
> URL: http://svn.reactos.org/svn/reactos?rev=53152&view=rev
> Log:
> [RPCRT4]
> - restore lost ros specific change.
> Thanks Vic.
>
> Modified:
> trunk/reactos/dll/win32/rpcrt4/ndr_marshall.c
>
> Modified: trunk/reactos/dll/win32/rpcrt4/ndr_marshall.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/rpcrt4/ndr_marsh…
> ==============================================================================
> --- trunk/reactos/dll/win32/rpcrt4/ndr_marshall.c [iso-8859-1] (original)
> +++ trunk/reactos/dll/win32/rpcrt4/ndr_marshall.c [iso-8859-1] Tue Aug
> 9 17:43:37 2011
> @@ -6159,6 +6159,7 @@
> case RPC_FC_WCHAR:
> case RPC_FC_SHORT:
> case RPC_FC_USHORT:
> + case RPC_FC_ENUM16:
> {
> USHORT d;
> align_pointer(&pStubMsg->Buffer, sizeof(USHORT));
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
Call me nuts, but why don't you add a ros_diff patch so it doesn't get
lost again???
From: jgardou(a)svn.reactos.org
Sent: 09 August 2011 18:43
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [jgardou] 53152: [RPCRT4] - restore lost ros
specific change. Thanks Vic.
Author: jgardou
Date: Tue Aug 9 17:43:37 2011
New Revision: 53152
URL: http://svn.reactos.org/svn/reactos?rev=53152&view=rev
Log:
[RPCRT4]
- restore lost ros specific change.
Thanks Vic.
Modified:
trunk/reactos/dll/win32/rpcrt4/ndr_marshall.c
Modified: trunk/reactos/dll/win32/rpcrt4/ndr_marshall.c
URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/rpcrt4/ndr_marsh…
==============================================================================
--- trunk/reactos/dll/win32/rpcrt4/ndr_marshall.c [iso-8859-1] (original)
+++ trunk/reactos/dll/win32/rpcrt4/ndr_marshall.c [iso-8859-1] Tue Aug
9 17:43:37 2011
@@ -6159,6 +6159,7 @@
case RPC_FC_WCHAR:
case RPC_FC_SHORT:
case RPC_FC_USHORT:
+ case RPC_FC_ENUM16:
{
USHORT d;
align_pointer(&pStubMsg->Buffer, sizeof(USHORT));
Hello everybody,
Due to a mistake from my side, the uploaded BuildBot 7zipped ISO files
in the revision range from 53120 to 53127 as created by the Debug
Buildslave contained the very same ISO of revision 53119. This has been
fixed in the meantime, the faulty files have been removed from the
server and at least the 7-Zip archive of revision 53127 has been recreated.
On the other hand, Olaf and I have finally enabled his server to upload
ISOs to http://iso.reactos.org. These ISOs are built by his Buildslave
running under Windows, already using the new CMake buildsystem and
incorporating our regression tests and the Gecko CAB file.
I might have time to add another filter to http://reactos.org/getbuilds
soon, so that everybody can download the new ISOs easily.
- Colin
Am 05.08.2011 21:35, schrieb jgardou(a)svn.reactos.org:
> Author: jgardou
> Date: Fri Aug 5 19:35:54 2011
> New Revision: 53087
>
> URL: http://svn.reactos.org/svn/reactos?rev=53087&view=rev
> Log:
> [PSDK]
> - do not redefine UNICODE_STRING and NTSTATUS if wintrnl.h has already been included
...
> -#if !defined(_NTDEF_)
> +#if !defined(_NTDEF_)&& !defined(__WINE_WINTERNL_H)
> typedef LONG NTSTATUS, *PNTSTATUS;
> #endif
Thats disgusting!
Why do we need this? I hate hacking headers because of crap elsewhere.
Regards,
Timo
Hi everybody,
As promised, here are the status updates of several ReactOS people based
on the texts I received after our failed meeting a week ago.
Thomas Faber has reported that the Kernel-Mode Test Framework is pretty
much standing, together with extensive tests for Spin Locks, Executive
Resources and IRQ-Level functions. Additional "comfort" functions might
be added as the need arises.
Basic tests also exist for Singly and Doubly Linked Lists, Hard Error
Messages, Deferred Procedure Calls and Asynchronous Procedure Call
Disabling. Furthermore, applicable tests have been ported from the old
"kmtests" module.
Thomas is currently working on tests for Events, Fast and Guarded
Mutexes as well as basic I/O functionality (Driver/Device Objects,
app-driver communication). Latter ones are partly based on the
"not-applicable" old tests. More tests concerning Object Referencing,
Singly and Doubly Linked Lists and Sequenced lists are going to follow.
Even more may follow afterwards based on his personal function list or
current requirements. Finally, the integration with our automated
testing tools has to be tested.
Colin Finck did not have much time for ReactOS in the last month, so he
could just assist Pierre Schweitzer with setting up the Icinga
monitoring solution.
Claudiu Mihail has integrated lwIP into the tcpip.sys driver. The
library has also been updated to the most recent version (1.40), which
required no changes to the interface code. On top of this, the speed
issue has been resolved, so the performance of our lwIP-based stack is
on par with our existing OSKitTCP-based stack now.
The new network stack has been tested by replacing the tcpip.sys of a
regular Trunk build with the lwIP-based one. This posed no problems, so
merging the new stack back to Trunk should work nicely. According to
Claudiu, initial testing using applications such as Opera, Firefox and
BitTorrent shows very promising results in terms of stability and
performance.
In the short term future, he plans to conduct more testing to fix any
outstanding bugs in the implementation. Besides, he plans to optimize
some aspects of the implementation, especially regarding memory usage,
together with Art Yerkes and Cameron Gutman.
For the long-term future, which also includes the time after GSoC, he
thinks about moving more TCP/IP functionality to lwIP such as UDP.
Pierre Schweitzer has been setting up an Icinga solution for monitoring
all our physical servers and VMs, including the services running on
them. This will allow the project to have a higher quality of service,
and let ReactOS sysadmins be aware quicker about issues raising on the
servers.
He also announced that he is leaving ReactOS development and only
focuses on sysadmin work for the project.
- Colin
Hello all,
Today's planned meeting has been postponed to the 25th August (the time
of the next regular meeting) based on a voting of the participants
present at 19:39 UTC. These were:
* Giannis Adamopoulos
* Javier Agustìn Fernàndez Arroyo
* Maciej Bialas
* Thomas Faber
* Colin Finck
* Ziliang Guo
* Cameron Gutman
* Rafal Harabien
* Timo Kreuzer
* Matthias Kupfer
* Igor Paliychuk
* Sylvain Petreolle
* Daniel Reimer
* Pierre Schweitzer
* Samuel Serapion
* Olaf Siejka
○ Result:
[19:44] <VoteBot> Question: Please vote for a date for postponing
this meeting.
[19:44] <VoteBot> Answers:
[19:44] <VoteBot> Abstention - 7 votes
[19:44] <VoteBot> 11th August (in 2 weeks) - 3 votes
[19:44] <VoteBot> 25th August (in 4 weeks, regular next meeting) -
6 votes
[19:44] <VoteBot> Total number of votes: 16
○ Main reasons were that the following people were still not present
at the time of voting:
* Aleksey Bragin (supposed meeting leader and key person in the
Arwinss and Release preparation agenda points)
* Amine Khaldi (supposed backup meeting leader and key person in the
CMake agenda point)
* Ged Murphy (key person in the GSoC and Driver Signing agenda
points)
○ Unfortunately, nobody has been prepared for this kind of situation,
so a lot of time has been wasted and confusing decisions might have
been made.
○ Postponing the points also gives Aleksey time to prepare a new
Arwinss build and the Build Environment guys (Daniel, me, anybody
wants to join?) time to prepare a final CMake version of RosBE, which
might be a factor when deciding about doing the migration to CMake.
○ The IRC Server has been closed at 20:03 UTC.
To allow the participants to get an unbiased idea about today's meeting,
I will post the original IRC log by the server to ros-priv. Would
actually like to make it public on ros-dev as well, but will abstain
from doing so until Ged's confusion about the openness of our meetings
is cleared.
If people have already prepared texts for this meeting (status updates,
whatever else you wanted to say), please send them to my E-Mail address
within the next 3 days and I'll compose a summary out of them, which I
will send to ros-dev.
If you think that these texts don't just deserve a simple summary, keep
them for the next meeting or do whatever you want about them.
And finally a personal note: Please keep in mind that it was not an easy
decision for me to just close the IRC Server after I believed that main
discussions were over. If I had left it running, it would have
invalidated the voting (again) and participants would have treated the
meeting even more as a joke. By closing it, I obviously received
complaints from people who had prepared stuff for this meeting and
wanted to revive it.
In good hopes,
Colin
Hello,
Let me invite you to the monthly status meeting taking place last thursday
of this month, 28th of July, 19:00 UTC.
The meeting will be at irc://fezile.reactos.org (Port 6667, no SSL) in the
channel #meeting. Note that the IRC service will only be started shortly
before the meeting. Everyone is invited to listen, and active community
members have their passwords so that they can participate in the discussion.
If someone doesn't have a password - please don't hesitate to email Colin to
get one. Colin - would you publish the most up-to-date list of participants?
Proposed agenda for the meeting:
1. Arwinss adoption voting.
2. CMake status report?. (Do we need to decide anything? If not, then let's
move discussion to the mailing list)
3. Release preparation status report. (Decide when to do winesyncs and
branch off the release)
More suggestions are welcome.
With the best regards,
Aleksey Bragin.
Hi,
Several times now cmake build has been broken. Time for some action!
Last meeting I asked everyone to test/use cmake. It was also mentioned
that if questions arise, we (Amine and me) would be happy to help out. I
can't remember anyone has asked how it works, so I assume noone had any
problems. There's also a pretty good wiki entry describing the whole
procedure for n00bs.
Now people tell me it's complicated, people are complaining that its
ridiculous to have 2 build systems, etc.
And probably noone has ever tried it.
We really need to move on.
I don't like having 2 build systems as well.
Current blocker is the debugging which has some issues, Arty is working
on that. Another problem is a boot problem on real hardware, but no I
don't know on which configuration it doesn't work, so we need more
people testing it on their real hardware setup and report any issues.
Here's a list with current issues:
http://www.reactos.org/wiki/CMake_Todo
So please:
If you are missing something, let us know.
If you like to make it better, make suggestions.
But stop ignoring cmake!
If noone cares and everyone just thinks he can give a s^Z damn until we
officially switch, then we can as well delete all cmake stuff and keep
rbuild. It has a lot of awesome advantages, like you only have to type
one command to build everything and you don't need to install cmake and
you can export whatever you want from kernel32 even if the functions
don't exist. Also you can enjoy the rbuild-loop again and again.
Or we can do it the hard way and delete rbuild, so people are forced to
use cmake. I'm sure this approach would be *really* appreaciated.
Thanks,
Timo
This won't work, since new Fibers, created with CreateFiber(Ex) don't
push a "return address" on the stack, but set the Eip member to
BaseFiberStartup.
Am 23.07.2011 14:08, schrieb ion(a)svn.reactos.org:
> Author: ion
> Date: Sat Jul 23 12:08:36 2011
> New Revision: 52807
>
> URL: http://svn.reactos.org/svn/reactos?rev=52807&view=rev
> Log:
> [KERNEL32]: Optimize SwitchToFiber to simply use "ret" to jump between fibers, instead of saving EIP and doing a JMP.
> Bug #50: SwitchToFiber needs to check if FXSR is *NOT* present in order to skip using ldmxcsr/stmxcsr. Previously, it would check if it's unsupported, and jump past the instruction if it was (resulting in invalid opcode instructions on older systems)
> 50 bugs. Penance has been paid.
>
> Modified:
> trunk/reactos/dll/win32/kernel32/client/i386/fiber.S
>
> Modified: trunk/reactos/dll/win32/kernel32/client/i386/fiber.S
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/kernel32/client/…
> ==============================================================================
> --- trunk/reactos/dll/win32/kernel32/client/i386/fiber.S [iso-8859-1] (original)
> +++ trunk/reactos/dll/win32/kernel32/client/i386/fiber.S [iso-8859-1] Sat Jul 23 12:08:36 2011
> @@ -26,20 +26,16 @@
> mov [eax+FIBER_CONTEXT_EDI], edi
> mov [eax+FIBER_CONTEXT_EBP], ebp
>
> - /* Save the return address */
> - mov ebx, [esp]
> - mov [eax+FIBER_CONTEXT_EIP], ebx
> -
> /* Check if we're to save FPU State */
> cmp dword ptr [eax+FIBER_CONTEXT_FLAGS], CONTEXT_FULL OR CONTEXT_FLOATING_POINT
> jnz NoFpuStateSave
>
> /* Save the FPU State (Status and Control)*/
> fstsw [eax+FIBER_CONTEXT_FLOAT_SAVE_STATUS_WORD]
> - fstcw [eax+FIBER_CONTEXT_FLOAT_SAVE_CONTROL_WORD]
> + fnstcw [eax+FIBER_CONTEXT_FLOAT_SAVE_CONTROL_WORD]
>
> /* Check if the CPU supports SIMD MXCSR State Save */
> - cmp byte ptr ds:[PROCESSOR_FEATURE_FXSR], 0
> + cmp byte ptr ds:[PROCESSOR_FEATURE_FXSR], 1
> jnz NoFpuStateSave
> stmxcsr [eax+FIBER_CONTEXT_DR6]
>
> @@ -103,7 +99,7 @@
> ControlWordEqual:
>
> /* Load the new one */
> - cmp byte ptr ds:[PROCESSOR_FEATURE_FXSR], 0
> + cmp byte ptr ds:[PROCESSOR_FEATURE_FXSR], 1
> jnz NoFpuStateRestore
> ldmxcsr [ecx+FIBER_CONTEXT_DR6]
>
> @@ -121,7 +117,8 @@
> mov [edx+TEB_FLS_DATA], eax
>
> /* Jump to new fiber */
> - jmp dword ptr [ecx+FIBER_CONTEXT_EIP]
> + mov esp, [ecx+FIBER_CONTEXT_ESP]
> + ret 4
> +END
>
> -END
> /* EOF */
>
>
>
Am 23.07.2011 14:05, schrieb ion(a)svn.reactos.org:
> Author: ion
> Date: Sat Jul 23 12:05:38 2011
> New Revision: 52806
>
> URL: http://svn.reactos.org/svn/reactos?rev=52806&view=rev
> Log:
> [KERNEL32]: Implement BaseFiberStartup in ASM, just like the thread/process thunks, so we get a "naked" thunk without any compiler-generated crap.
I don't see the point in this change.
That "crap" is setting up a stack frame, which is pretty useful for
debugging. It consists of 3 instructions:
push ebp
mov ebp, esp
sub esp, 8
Your change also broke compilation with MSVC (the END directive is only
at the end of the file!) and deleted the function for amd64.
The function is not performance critical and the asm code doesn't really
add any performace gain anyway.
So why are we going back?
I'm asking, because I've been working on converting more asm code to C
code and IMO thats the way to go.
Regards,
Timo
Am 07.07.2011 21:19, schrieb dgorbachev(a)svn.reactos.org:
> Author: dgorbachev
> Date: Thu Jul 7 19:19:44 2011
> New Revision: 52557
>
> URL: http://svn.reactos.org/svn/reactos?rev=52557&view=rev
> Log:
> [FREELDR]
> - Move read-only data into data section (allows to boot with GRUB again).
> - Discard .drectve sections.
> - Silence "set but not used" warnings.
I assume this is for rbuild. Did you check cmake builds, too?
-----Original Message-----
From: ion(a)svn.reactos.org
Sent: Sunday, July 10, 2011 6:14 AM
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [ion] 52596: [NTDLL]: More attempts at fixing up the
loader, this time in the PE side of things.
Author: ion
Date: Sun Jul 10 02:14:29 2011
New Revision: 52596
/* Check if we got at least one */
- if (BoundEntry || ImportEntry)
+ if ((BoundEntry) || (ImportEntry))
Could you enlighten me why do you add these redunandant braces?
WBR,
Aleksey.
June Meeting Minutes
2011-06-28
19:05 UTC
Fezile IRC Server, #meeting
Participants
=============
- Jan_Blomqvist_Kinander
- Igor_Paliychuk
- MfldElton
- Usurp
- Aleksey_Bragin
- Thomas_Faber
- Giannis_Adamopoulos
- Thomas_Faber
- Johannes_Anderwald
- Timo_Kreuzer
- Olaf_Siejka
- Jerome_Gardou
- Gabriel_Ilardi
- Andrew_Green
- Javier_Fernandez
- Victor_Martinez
- Amine_Khaldi
- Claudiu_Mihail
- Colin_Finck
- Rafal_Harabien
- Sylvain_Petreolle
- Matthias_Kupfer
- Danny_Goette
- Maciej_Bialas
- Ged_Murphy
- Ziliang_Guo
- Art_Yerkes
- Cameron_Gutman
- Neeraj_Yadav
- Herve_Poussineau
- Daniel_Reimer
- James_Tabor
- Olaf_Siejka
- Samuel_Serapion
- Pierre_Schweitzer
- Alex_Ionescu
- Gabriel_Ilardi
Proceedings
============
○ Meeting called to order at 19:05 UTC by Aleksey Bragin.
○ ReactOS Project coordinator Aleksey Bragin listed the points of the proposed agenda for June meeting:
1. Cmake switching
2. Next ReactOS release
3. Website revamp status
4. GSoC status
5. Developers status reports
The Minute Taker rol was given to Victor_Martinez for this meeting.
○ Point 1: CMake switching
--------------------------------------------
■ The ReactOS developer Timo gave a quick sum up about CMake status:
He reported that the CMake build is more or less ready, currently missing rosapps. He stated that rosapps are not a major problem as they're rarely used, and cmake files for them can be done if needed.
He also mentioned a problem, confirmed by Igor_Paliychuk, related to booting in real hardware, in addition to the winmm:mci regression.
The problem detected in real hardware is very specific to the hardware combination thus hard to test.
■ Amine mentioned that several comparative tests have been done through buildbot/testman between the rbuild build and the CMake build, showing no measurable differences. He also stated that the CMake port shouldn't be considered done yet, as it still lacks many planned features.
He highlighted some of the CMake patches,made by Jerome, to be sent upstream, like the PCH support and its related dependency tracking, and also the benefits of using CMake to compile ros, like the improved performance, the small disk space needed for builds (half of what the rbuild builds require) and the cool new kdbg features.Gabriel_Ilardi expressed his concers about merging more code in the current trunk situation. Timo replied that no code merge is needed,in case of switching to Cmake.
■ Timo, Colin and Aleksey asked about measuring the CMake build performance over the rbuild build in numbers. Jerome performed a quick benchmark:
First test: makex ntoskrnl (all clean, toold already built). Cmake: 04:06 , Rbuild: 04:55 (17% faster)
Second test: rebuild (only dependencies check). Cmake: 0:28 , Rbuild: 1:04 (56% faster)
The benchmark shows Cmake is faster not only for a full compilation but also recompiling (ntoskrnl) modules.
■ The ReactOS Cmake Team suggested to begin using Cmake with current RosBE to compile ReactOS ISOs in order to assure they are as good as Rbuild’s.
A "How to compile with Cmake" tutorial can be found in the following wikipage: http://reactos.org/wiki/Cmake
Summing up, the Cmake switch will bring better dependency checking, fast rebuild of single modules and much better symbols support in kdbg according to the ReactOS Cmake Team
The technical description was left to be discussed in #reactos-dev, if anyone was interested.
○ Point 2 : Next ReactOS release
--------------------------------------------------------
¦ReactOS release was the 2nd point of the June meeting agenda.
■ Gabriel_Ilardi and Victor_Martinez were asked to report current trunk state from Compatibility/Stability point of view.
Accordingly to forum threads, Bugzilla new entries, and Own testing,Gabriel and Victor said important regressions have been introduced due the latest changes, and mainly the LDR rewrite.
Wrong icons, impossibility to shutdown, AC97 hang, several installers/apps failing are some of those important regressions.
■ Art_Yerkes has been giving a look at the AC97 bug, he was able to gather a lot of information about the regression and asks for collaboration to fix it.
■ Aleksey_Bragin, as the author of the LDR rewrite, stated that he knew the new LDR could introduce regressions but that it is a big step forward.
The top priority is fixing those LDR regressions, instead of reverting, as the old LDR was indeed worse.
Aleksey remarks that he needs every dev to take a look at the LDR bugs and try to fix them.
The LDR regressions should be really easy to fix thanks to the rewrite, he said.
■ Amine_Khaldi suggested to decide when it is time to release performing bugfixing and full regression testing.
■ The idea of performing full regression tests now was inmediatly rejected by Colin_Finck and Olaf_Siejka since bug reports are currently showing that our trunk is in a really bad shape. Due to this, the Release discussion will be on hold until the next meeting.
During this month ReactOS devs are suggested to focus in bugfixing mainly the LDR code.
As these bugs are critical and able to hide other minors regressions, a special call is being made:
****************Special Call****************
"Please pick a bug from the linked ones in http://reactos.org/bugzilla/show_bug.cgi?id=6346 "
****************Special Call****************
○ Point 3 : Website Revamp Status
-------------------------------------------------------
¦ Thanks to Colin's help, a new playground with correct permissions and tied to an SVN branch has been created.
■ Niski and aross, main webrevamp developers, have been focused on Bugzilla and Mediawiki integration, compatdb drupal port, and forum.
Forum will have new features as "the best answer" and "karma" modules which will improve forum users experience.
■ Niski has completed the work on Bugzilla and Mediawiki while aross is working on compatdb and the new forum.
■ Right now, Amine said, a design/layout work is needed in parallel.
■ Colin_Finck stated that finding a designer among ReactOS developers is more difficult than findind a developer so he offered himself to help with the design/layout.
○ Point 4: Gsoc status
-------------------------------------------------------------------
■ AndrewGreen is currently cleaning a mixture of explorer_new, atl com and browseui code. The resultant code will be commited afterwards.
Although he recognizes his project is behind schedule, after apologizing he says he’s confident to meet the goals by midsemester evaluation.
Ged_Murphy cpp shell32 code will allow him to use atl com for everything shell related.
Colin_Finck and Olaf_Siejka discussed the best way to test the new implementation to check for any possible regressions, due to the fact that Ged was not around the discussion was postponed.
Jerome_Gardou asked Andrew about the WINE Shell32 Gsoc project but accordingly to Olaf, Wine has refused to cooperate regarding those.
Status: Behind Schedule.
■ Giannis_Adamopoulos was too busy with exams so his project was parked a little. His commits will raise up when the last exam is done.
Status: On time
■ Claudiu_Mihail thanked the great help of Cameron_Gutman and Art_Yerkes. The project is set to meet the deadlines for midterm.
There are still two problems remaining: browsers don't work(it will be solved by midterms), slowness of the lwIP implementation.
He has followed the test approach using several simple test apps and fixing revealed bugs.
After finishing his thesis project, which is highly related to his Gsoc project,he will start commiting again.
■ Neeraj_Yadav has divided his sound project in 5 parts.
1.[Finished] Writing a skeleton server which can hold the audio converter modules and the mixer modules ...This server should be capable of insertion in the reactos audio chain [4 weeks]
2.[Now] Writing mixer modules [2 weeks]
3.Writing audio converter [ 4 weeks]
4.Inserting this audio server in the reactos audio chain [1 week]
5.testing/styling/documentation [1 week]
He expects to finish the 2nd step in midterm evaluation.
Alex_Ionescu and Giannis_Adamopoulos asked for a way to test Neeraj code.
If anyone is interested, this is the best way:
1)make audsrv && make audclient
2)run audsrv -n in one console
3)run audclient in other
4)open as many audclients as you want
5)the server should play a mixed sound
Status: On time
■ Thomas_Faber is finishing the main framework needed to run the tests. Most of the old tests have been ported and now he is currently working on getting special-purpose drivers and usermode test parts up and running.
Lately he has been quite busy with a university project but he expects to commit the framework in these days.
Status: On time
■ Timo_Kreuzer has finished the font driver loading and now he is working on the font mapper, which is complex and needs a good design.
Status: Ahead of time
○ Point 5: Developers status reports
-------------------------------------------------------------------
■ Alex_Ionescu will help Aleksey commit his scater/gather DMA patch.
■ Alex_Bragin is working on remaining LDR code and afterwards he'll take part in processing bugzilla patches.
■ Amine_Khaldi is focused in cmake and the website revamp.
■ Art_Yerkes made some improvements to symbol handling in the cmake branch and now he’s working with Claudiu.
■ Colin_Finck has been trying the KDUSBCOM idea (KD DLL for debugging over an USB-to-Serial adapter), and he’s moving now to help with the website layout.
■ Daniel_Reimer is playing with Gcc builds and updating RosBE.He added Cmake support a while ago and he is still battling with GCC 4.6 and Wine RC files.
■ Gabriel_Ilardi is focused in mantaining Bugzilla and the forum and he’s performing some testing in his few spare time.
■ Ged_Murphy is helping with shell32 c++ fixup
■ Herve_Poussineau is currently inactive on ReactOS
■ James_Tabor is still working on bug report issues.
■ Jan_Blomqvist_Kinander will move the Fezile server to the concrete bunker creating a LAN behind Fezile to get automated tests on real hardware.
■ Johannes Anderwald will work in HID (Human Interface Devices for USB) support during the summer, a hard task as it is completly undocumented.
■ Maciej_Bialas is working on mediawiki integration for the new revamped site.
■ Matthias_Kupfer has been bugfixing and commiting some patches.
■ Pierre_Schweitzer has no time nor willingness right now. Once time will be back,he'll invest it in his summer student.Once willingness will be back, he'll keep on his current ReactOS work and help with the ReactOS infrastructure
■ Olaf_Siejka is waiting for Aleksey to finish the LDR code so he can team up with him to solve the remaining issues of sysreg4. After finishing the utf-8 resource conversion, he will get more involved in testing. He will also help with the hardware testbot from the buildbot side.
■ Sylvain_Petreolle is working on French translations.
■ Timo_Kreuzer is working on MSVC builds fixing several bugs that prevent ReactOS to reach the desktop.
■ Victor_Martinez has finished his exams recently and now he’s preparing a forum team to test the revision before the LDR rewrite and the one after it, this way it'll be easier to find regressions. Also he will help with the revamp webpage.
○ Point 6: Suggestions
---------------------------
■ Jan_Blomqvist_Kinander suggested to create a ReactOS annual bootcamp with devs, testers and fanatics plus having a look at SAMBA 4 - ROS port
○ Meeting closed at 22:08 UTC by Colin Finck on behalf of Aleksey Bragin.
○ Minutes written by Víctor Martínez.
○ Reviewed by Amine_Khaldi, and Gabriel_Ilardi
Hi!
Sadly the hosting that I was providing for free will be suspended in the next 24 hours. I was totally fed up with these iPage guys so decided to move everything out.
The website and all the content in the folders will be removed. I will keep the myreactos.com domain for a year or maybe I will remove it too.If anyone is interested please contact me.
If anyone is still using the hosting, please back your files up.
WBR,
Víctor Martínez
That was there on purpose really, because the error had to be ignored. I
will get back to this tomorrow to review, so just "marking" this revision
that way.
WBR,
Aleksey.
-----Original Message-----
From: cgutman(a)svn.reactos.org
Sent: Monday, July 04, 2011 12:16 AM
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [cgutman] 52522: [LDR] - "Just to be sure" is no reason
to overwrite a potential DLL load failure status
Author: cgutman
Date: Sun Jul 3 20:16:12 2011
New Revision: 52522
URL: http://svn.reactos.org/svn/reactos?rev=52522&view=rev
Log:
[LDR]
- "Just to be sure" is no reason to overwrite a potential DLL load failure
status
Modified:
trunk/reactos/dll/ntdll/ldr/ldrapi.c
Modified: trunk/reactos/dll/ntdll/ldr/ldrapi.c
URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/dll/ntdll/ldr/ldrapi.c?rev…
==============================================================================
--- trunk/reactos/dll/ntdll/ldr/ldrapi.c [iso-8859-1] (original)
+++ trunk/reactos/dll/ntdll/ldr/ldrapi.c [iso-8859-1] Sun Jul 3 20:16:12
2011
@@ -345,9 +345,6 @@
DllName,
BaseAddress,
TRUE);
-
- /* Set it to success just to be sure */
- Status = STATUS_SUCCESS;
/* Restore the old TLD DLL */
LdrpTopLevelDllBeingLoaded = OldTldDll;
Why do you have to be this way? I gave you a link to 3 PDFs and our
own Wiki that explain these functions. Did you even read them?
Don't be an asshole just for fun.
Best regards,
Alex Ionescu
On Sun, Jul 3, 2011 at 1:11 AM, <tkreuzer(a)svn.reactos.org> wrote:
> Author: tkreuzer
> Date: Sat Jul 2 23:11:06 2011
> New Revision: 52507
>
> URL: http://svn.reactos.org/svn/reactos?rev=52507&view=rev
> Log:
> [NTOSKNRL]
> - Change an ASSERT to a KeBugCheck, since the assertion can fail for any invalid memory access and this is not an internal Mm failure.
> - Remove 2 cases, that "Should NEVER happen on ARM3!!!", but can very well happen.
> - Do NOT make the code cleaner, by releasing the PFN lock in the same function that acquires it, but keep it 2 functions down. This is because it *SHOULD* be that way, since some internal undocumented functions, that we do not implement but that are (theoretically) called from here, also do release the PFN lock. Thanks Alex for explaining this.
>
> Modified:
> trunk/reactos/ntoskrnl/mm/ARM3/pagfault.c
>
> Modified: trunk/reactos/ntoskrnl/mm/ARM3/pagfault.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/ARM3/pagfault.…
> ==============================================================================
> --- trunk/reactos/ntoskrnl/mm/ARM3/pagfault.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/mm/ARM3/pagfault.c [iso-8859-1] Sat Jul 2 23:11:06 2011
> @@ -583,10 +583,19 @@
> }
>
> //
> - // The PTE must be invalid, but not totally blank
> + // The PTE must be invalid
> //
> ASSERT(TempPte.u.Hard.Valid == 0);
> - ASSERT(TempPte.u.Long != 0);
> +
> + /* Check if the PTE is completely empty */
> + if (TempPte.u.Long == 0)
> + {
> + KeBugCheckEx(PAGE_FAULT_IN_NONPAGED_AREA,
> + (ULONG_PTR)Address,
> + StoreInstruction,
> + (ULONG_PTR)TrapInformation,
> + 2);
> + }
>
> //
> // No prototype, transition or page file software PTEs in ARM3 yet
> @@ -727,11 +736,6 @@
> // Writing to a read-only page (the stuff ARM3 works with is write,
> // so again, moot point).
> //
> - if (StoreInstruction)
> - {
> - DPRINT1("Should NEVER happen on ARM3!!!\n");
> - return STATUS_ACCESS_VIOLATION;
> - }
>
> //
> // Otherwise, the PDE was probably invalid, and all is good now
> @@ -776,11 +780,6 @@
> // Writing to a read-only page (the stuff ARM3 works with is write,
> // so again, moot point.
> //
> - if (StoreInstruction)
> - {
> - DPRINT1("Should NEVER happen on ARM3!!!\n");
> - return STATUS_ACCESS_VIOLATION;
> - }
>
> /* Release the working set */
> MiUnlockWorkingSet(CurrentThread, WorkingSet);
>
>
>
Hello,
Last thursday of this month is quite close, 30th of June, 20:00 UTC
I'm awaiting you all for the monthly status meeting. Colin said that
our private irc server is going to be ready by that date, so if
that's still true, Colin - could you please provide details for those
who don't remember where to connect?
Proposed agenda is:
1. New release of ReactOS
2. Website work status
3. GSoC status
4. Developers status.
With the best regards,
Aleksey Bragin.
I'm definitely not sure that the header[1] added to all converted files was absolute necessity.
AFAIK, that's SVN logs purpose...
Unless someone has a real justification to such line?
Many files even don't have a translator copyright but this line... Weird!
[1]: /* UTF-8 Conversion: Elton Chung aka MfldElton <elton328(a)gmail.com> (June, 2011) */
Hi Erik,
The NDK is for *undocumented* types. These flags are documented.
--
Best regards,
Alex Ionescu
On 2011-06-26, at 7:29 AM, ekohl(a)svn.reactos.org wrote:
> CM_RESOURCE_INTERRUPT_LEVEL_SENSITIVE
Hello,
as all of you could notice, I committed the LDR rewrite recently. I
tried to get rid of as much regressions as possible (any rewrite
should introduce improvements of course, rewrites are not done to
introduce regressions, however there is no rewrite without some
particulars problems).
So, dear developers, I need your help. Gabriel did a very nice work
and bugzilled all kinds of problems which new LDR introduced. Here is
the meta-bug:
http://www.reactos.org/bugzilla/show_bug.cgi?id=6346
Please look into the bugs, check something and add your findings to
bugzilla. The new LDR code is perfectly organized, very well
documented, so most of those bugs should be quite simple to fix, but
my time is not infinite, so I'm asking for collaboration. I'm always
available via IRC for any questions about the new code, so feel free
to ask.
Put away your usual stuff for an hour or for a day and look into
those. It would help greatly and motivate me to finish other parts of
the rewrite quicker.
Thanks,
Aleksey Bragin.
Hi sir_richard and welcome back!
Just to make sure you know, it seems this commit introduces a regression, ros hangs while loading ndis.sys, see testbot logs:
http://build.reactos.org/builders/Windows_AMD64_1%20VBox-Test/builds/1342/s…
I've filed http://www.reactos.org/bugzilla/show_bug.cgi?id=6292
Could you please take a look?
Thanks.
> Date: Sun, 5 Jun 2011 20:48:34 +0000
> To: ros-diffs(a)reactos.org
> From: sir_richard(a)svn.reactos.org
> Subject: [ros-diffs] [sir_richard] 52098: [FREELDR]: Some ARM architectures do not necessarily have CS0_BASE at 0x00000000, for example, most Ti OMAP Platforms have DDR at 0x80000000. The current FreeLDR algorithms wou...
>
> Author: sir_richard
> Date: Sun Jun 5 20:48:34 2011
> New Revision: 52098
>
> URL: http://svn.reactos.org/svn/reactos?rev=52098&view=rev
> Log:
> [FREELDR]: Some ARM architectures do not necessarily have CS0_BASE at 0x00000000, for example, most Ti OMAP Platforms have DDR at 0x80000000. The current FreeLDR algorithms would build FreeLDR "page entries" for every page from 0 to 0x7FFF0000 and mark it as unusable, then build the actual valid entries from 0x80000000 -> end of RAM, thus resulting in large memory consumption (and in the bloat of the PFN database later once NTOS loads) and boot time. Therefore, the algorithm is changed to start the PFN database at the lowest valid RAM page described by the Firemware descriptors, and entries therefore will be offset. This means a 128MB embedded system no longer appears to have 2048+128MB of RAM worth of PFN entries.
> NOTE: Windows does not do this, opting instead to force manufacturers/use pull-up resistors/reconfigure the ARM Bus to map RAM at 0x00000000. For wider portability, I believe it makes more sense to simply do this "trick" in the boot loader.
>
> Modified:
> trunk/reactos/boot/freeldr/freeldr/arcemul/mm.c
> trunk/reactos/boot/freeldr/freeldr/mm/meminit.c
>
Hi,
I'd like to change the Vtbl based architecture of freeldr into a normal
function call system.
Currently we have stuff like
#define MachHwDetect() MachVtbl.HwDetect()
MachVtbl.HwDetect = PcHwDetect;
This is IHO simply useless, since these functions don't change. I
suggest simply renaming PcHwDetect to MachHwDetect and do that will all
of those and get rid of the MachVtbl.
Any objections?
Regards,
Timo
gedmurphy(a)svn.reactos.org wrote:
> +// WIDL temp hack : [...]
Even though we all like to see a full MSVC build in the future, does
this really justify such an even bigger hack on top of the existing
ones? Would a proper fix really require that much more time?
If we don't want to end up in a new mess, this pretty much forces
someone to fix it in the coming days or the hack/commit will be
forgotten again. I'm certain about this, because nobody on #reactos-dev
really knew the reason behind the older __ROS_LONG64__ hack either.
Alternatively, you could open a detailed bug report about this issue and
assign some CMake people to it. But in any case, such hacks should be
tracked in our Bugzilla, in particular when more information about a
solution is known already.
- Colin
Hello all,
Edijus from #reactos has just tried ReactOS on his system, but the boot
process got stuck at "usbdriver.sys". When reading his notice, I was
wondering why we still include this ancient driver in every ReactOS build.
As far as I know ...
* it has never worked for us
* it is incomplete and not well-tested
* it has obvious code bugs (e.g. just look in ehci.c:3465 how it
enumerates more PCI devices and functions than possible,
consequently enumerating the first function twice due to bitshifts)
* better USB work by Johannes and Michael is progressing well
Although it might be useful as a testcase for the legacy HAL functions
(like HalAssignSlotResources), it should still be removed from the build
process for now.
If there are no objections, I'll do this change on the weekend.
- Colin
Hi,
While taking a short break from my GSOC work, I like to do some work on
freeldr.
Final goal is to make it work with MSVC, but first I'd like to do a
little cleanup, since its a bit messy.
First I'd like to know how the state of the old bootcode is and if we
still need it and whats left to do to get rid of it.
Then I'd suggest to remove the code that draws purple unicorns like it
was done for ARM (afaik, we don't use it anyway)
I'd also like to fix formatting (tabs -> spaces)
Any remarks, objections, wishes, doubts?
Regards,
Timo
Thanks for being that efficient for reverting.
Less than two days after message on ML. Congratz.
Next time I take days off, I won't take four days any longer, in case you would question some other of my patches.
I'll also send you my next patches, that way you'll be able to commit them, or just to skip them to prevent any revert.
Hi all,
I write this mail with great sadness, but I've recently been informed
that Ge Van Geldorp, one of the original and important contributers to
the ReactOS project has recently passed away.
Having met up with him personally, I can say with some confidence that
he was not only blessed with an impressive skill in the hobby /
industry we all love, but was also a man of great integrity.
Being one of my original mentors in reactos, and having spent time
busting our guts at various linux projects with him trying to convince
the unix fanatics of the merits of NT, I can assure you that this he
was both a great colleague and friend. I'm sure all the old school
reactos devs would more than agree.
I propose we have some sort of eulogy on our homepage. I'd be more
than willing to compose something.
If people would like to send their thoughts, wishes or memories, I'd
be more than happy to compile them.
Ged.
Hiya
Managed to find Greg brother's letter to Wine, with bit more details regarding this tragedy. Since GvG was also our man, not only Wine's, perhaps some collaborative effort could be set to commemorate him.
With best regards
Caemyr
-------- Original Message --------
Subject:
Date:
From:
To: RE: Ge van Geldorp
Thu, 9 Jun 2011 23:05:46 +0200
Erven Gé van Geldorp <erven.van.geldorp <at> gmail.com>
'Paul Vriens' <paul.vriens.wine <at> gmail.com>
Hi all,
My name is Arno van Geldorp. I’m the brother of Gé (Greg) van Geldorp. I’m very sorry that I have to inform you that Greg has passed away almost 3 weeks ago. 2 Months earlier he was diagnosed with cancer in a very aggressive form.
I know he made his contribution to the Wine project. And that one of them is the WineTestBot. His passing away went so fast that he didn’t have the time to inform me all about it. What he did ask me is to make sure that the server where the WineTestBot is running on will be hosted for at least 2 more years. So we will take care of that. But I don’t know if anyone took over the administration off the server.
If anyone took over the administration from Greg could you please contact me at erven.van.geldorp at gmail.com
Kind regards,
Arno van Geldorp
Am 09.06.2011 15:56, schrieb tkreuzer(a)svn.reactos.org:
> Author: tkreuzer
> Date: Thu Jun 9 13:56:44 2011
> New Revision: 52156
>
> URL: http://svn.reactos.org/svn/reactos?rev=52156&view=rev
> Log:
> [BOOTSECTOR]
> - export obj2bin on gcc builds, too
> - Add new macro CreateBootSectorTarget2, which uses portable assembly and use it with isoboot.S. I will replace all bootsectors with the new code one at a time, and in the end we can eventually drop nmake
> - add wrapper isobtrt.S, which defines ROS_REGTEST and includes isoboot.S
>
I mean of course "drop nasm" not "drop nmake"
The notification routine can change the list, as there is no lock involved.
Therefore, you should grab the next entry before notifying the driver, to maintain a consistent list state.
--
Best regards,
Alex Ionescu
On 2011-06-02, at 1:43 PM, pschweitzer(a)svn.reactos.org wrote:
> + DriverNotificationRoutine(DeviceObject, TRUE);
> +
> + /* Go to the next entry */
> + ListEntry = ListEntry->Flink;
Hiya
The today's failure of my slaves can be explained two-way.
First, buildslaves (windows ones especially, but not only) seem to be very vulnerable to ping dropouts. A single icmp drop is resulting in build interruption.
Second, the hetzner.de hosting is dropping packets from my provider (atman.pl) all the way from teleport to reactos host, at a rate of one every few minutes or even more.
Combined those two, any build started at the moment is dropped after 2-3 minutes of runtime.
I have no idea if the network issue is temporary or not, thus no chance to predict when we will continue with runtime, Any ideas?
With best regards
Caemyr