Hi Arty!
On Sun, Feb 15, 2009 at 4:52 PM, <arty(a)svn.reactos.org> wrote:
> URL: http://svn.reactos.org/svn/reactos?rev=39613&view=rev
> Log:
> Fix loopback adapter locking and make traffic work consistently.
> Fix zero-address binding.
> Local tcp services should work now.
I take this to mean telnetd should be talking on the network now?
Hello remote process control and the 1980's!
Thanks a lot of looking in to this. When I have time I am going to do
further cleanup of telnetd and move it in to the ReactOS tree proper.
Next on my list is a tftp server I found which I will attempt to get
license clarification on, cleanup and add to ReactOS so that we can
look in to using ReactOS tftpd to support kickstart like deployment
with netboot.
Thanks
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Hi,
I know this is in a branch, but~
WINAPI
DdUnlock(LPDDHAL_UNLOCKDATA Unlock)
{
+ /* Fixme for opengl hel emulations */
+ HEL_OGL_STUB;
+#if 0
/* Call win32k */
return NtGdiDdUnlock((HANDLE)Unlock->lpDDSurface->hDDSurface,
(PDD_UNLOCKDATA)Unlock);
+#endif
}
It is a direct call and this is correct. Why if it out? Don't add non
standard functionality to the gdi interface unless this is a upgrade
from XP.
Thanks,
James
Hello everyone,
A new release of RosBE-Unix is finally available.
It mostly features updated build tools compatible to the versions used in
RosBE-Windows 1.4 and initial multi-architecture support through additional
RosBE-Unix packages (which still don't exist though :P)
I highly recommend the update, because our previous binutils contains a
critical bug in dlltool. (see
http://sourceware.org/bugzilla/show_bug.cgi?id=9766 for details)
Some components affected by that bug were our msvcrt*.dll and mapi32.dll.
The new release is now available from SourceForge, just like RosBE-Windows
(https://sourceforge.net/project/showfiles.php?group_id=6553&package_id=3084
58)
Best regards,
Colin
Hello everyone,
Recently, the problem came up that Wine's spoolss.dll tries to forward its
"EnumPortsW" function to the similar function in winspool.drv.
Wine added a forward entry "winspool.drv.EnumPortsW" for this reason.
Unfortunately, such forwarders weren't supported by binutils, thus Christoph
opened this bug for them:
http://sourceware.org/bugzilla/show_bug.cgi?id=9811
The provided patch now makes such entries possible in the .def file, but
that still doesn't help as Windows' and ReactOS' ntdll both forward to .dll
files only.
So after all, this non-dll forwarding thing seems to be a Wine invention we
cannot support and have to avoid when importing Wine stuff.
Additionally, the proposed patch on the binutils Bugzilla won't find its way
into RosBE now.
Best regards,
Colin
Considering about 6 of you went to FOSDEM, is anyone actually gonna release
any info about what happened?
If I am completely unaware, I can imagine how expectant users feel
Communication is really terrible.
Ged.
Please add a standard header, with license information.
On Feb 11, 2009, at 11:37 PM, tkreuzer(a)svn.reactos.org wrote:
> Author: tkreuzer
> Date: Wed Feb 11 14:37:25 2009
> New Revision: 39558
>
> URL: http://svn.reactos.org/svn/reactos?rev=39558&view=rev
> Log:
> Implement hpp - the header preprocessor
> It can parse headers and create new headers from them based on a
> simple prepreprocessing language that's compatible with the C
> preprocessor, so the source file stays a valid header. It works,
> but doesn't yet support different folders.
>
> Added:
> trunk/reactos/tools/hpp/ (with props)
> trunk/reactos/tools/hpp/hpp.c (with props)
> trunk/reactos/tools/hpp/hpp.rbuild (with props)
>
> Propchange: trunk/reactos/tools/hpp/
> ----------------------------------------------------------------------
> --------
> svn:mergeinfo =
>
> Added: trunk/reactos/tools/hpp/hpp.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/tools/hpp/
> hpp.c?rev=39558&view=auto
> ======================================================================
> ========
> --- trunk/reactos/tools/hpp/hpp.c (added)
> +++ trunk/reactos/tools/hpp/hpp.c [iso-8859-1] Wed Feb 11 14:37:25
> 2009
> @@ -1,0 +1,509 @@
> +#include <stdio.h>
fireball(a)svn.reactos.org wrote:
> Author: fireball
> Date: Fri Feb 13 05:20:59 2009
> New Revision: 39578
>
> URL: http://svn.reactos.org/svn/reactos?rev=39578&view=rev
> Log:
> Igor Koshpaev <tower(a)reactos.org>
> - Include missing modules into bootcd
>
...
> +modules\rostests\apitests\w32kdll\w32kdll_2k3sp2\w32kdll_2k3sp2.dll 1 optional
> +modules\rostests\apitests\w32kdll\w32kdll_2ksp4\w32kdll_2ksp4.dll 1 optional
> ...
> +modules\rostests\apitests\w32kdll\w32kdll_xpsp2\w32kdll_xpsp2.dll 1 optional
>
These make no sense on reactos. They only work on the respective OS.
Does the pspec here use Winebuild? Sorry I can't check at the moment.
If it does, the current winebuild allows you to specify exports for a
given arch by passing
-arch=cpu
in the spec file.
On Tue, Feb 10, 2009 at 10:15 AM, <tkreuzer(a)svn.reactos.org> wrote:
> Author: tkreuzer
> Date: Tue Feb 10 09:15:07 2009
> New Revision: 39533
>
> URL: http://svn.reactos.org/svn/reactos?rev=39533&view=rev
> Log:
> x64 version of ntoskrnl doesn't export ExInterlockedAddLargeStatistic
>
> Modified:
> branches/ros-amd64-bringup/reactos/ntoskrnl/ntoskrnl.pspec
>
> Modified: branches/ros-amd64-bringup/reactos/ntoskrnl/ntoskrnl.pspec
> URL: http://svn.reactos.org/svn/reactos/branches/ros-amd64-bringup/reactos/ntosk…
> ==============================================================================
> --- branches/ros-amd64-bringup/reactos/ntoskrnl/ntoskrnl.pspec [iso-8859-1] (original)
> +++ branches/ros-amd64-bringup/reactos/ntoskrnl/ntoskrnl.pspec [iso-8859-1] Tue Feb 10 09:15:07 2009
> @@ -104,7 +104,9 @@
> @ stdcall ExInitializeRundownProtectionCacheAware(ptr long)
> @ stdcall ExInitializeZone(ptr long ptr long)
> @ stdcall ExInterlockedAddLargeInteger(ptr long long ptr)
> +#ifndef __x86_64__
> @ fastcall ExInterlockedAddLargeStatistic(ptr long)
> +#endif
> @ stdcall ExInterlockedAddUlong(ptr long ptr)
> #ifndef __x86_64__
> @ fastcall ExInterlockedCompareExchange64(ptr ptr ptr ptr)
>
>
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Folks,
I don't know where to ask this question, So decided to ask it on Dev mailing
list.
I am new to ReactOS and installed it on VMWare workstation and really loved
it.
It's behavior look and feel is like Windows and I really appreciate it
(although there is long way to for it)
Few of my questions are below:--
1) Is there any development kit for developing applications for ReactOS?
2) If not, Will Applications developed using Windows SDK (not .net
framework and all, just plain SDK) will work on ReactOS?
3) If Apps developed on Windows works on ReactOS, Are libraries developed
for Windows (which just depend on kernel32, user32 and other system dlls)
will work on ReactOS?
I am planning to use ReactOS for one of my custom device (using x86 based
processor) and want to develop some applications on top of it.
Regards
Deepak
Hi,
I am currently having a small problem on the x64 branch, maybe someone
can help me.
In wdm.h there's the following declarations:
#if defined (_WIN64)
#if defined(_NTDRIVER_) || defined(_NTDDK) || defined(_NTIFS_) || \
defined(_NTHAL_) || defined(_NTOSP_)
NTKRNLAPI
USHORT
ExQueryDepthSList(IN PSLIST_HEADER Listhead);
#else
FORCEINLINE
USHORT
ExQueryDepthSList(IN PSLIST_HEADER Listhead)
{
return (USHORT)(ListHead->Alignment & 0xffff);
}
#endif
#else
#define ExQueryDepthSList(listhead) (listhead)->Depth
#endif
So when compiling ntoskrnl, ExQueryDepthSList is not inlined. Later in
wdm.h (currently in our winddk.h, but to be moved to wdm.h)
ExQueryDepthSList is used in ExFreeToNPagedLookasideList inline function.
But I want ExQueryDepthSList to be inlined from within ntoskrnl. The
question is how can I achieve this?
If I #define it to be inline in ntoskrnl's private headers, it will not
affect ExFreeToNPagedLookasideList.
When I declare it as an inline function after the header is included, I
get a warning that it was declared inline after being used and that a
static declaration follows a non-static. (Does anyone know hoe to
disable these stupid warnings?)
Declaring it inline before including wdm.h doesn't work, as the needed
declaration for SLIST_HEADER is missing.
Anyone got any other idea? I'd like to avoid hacking our public headers,
to keep them as compatible to ms headers as possible.
Regards,
Timo
Forwarded to ReactOS mailing list. (using correct address this time :)
----- Message d'origine ----
> De : Anthony Liguori <anthony(a)codemonkey.ws>
> À : qemu-devel(a)nongnu.org
> Envoyé le : Jeudi, 29 Janvier 2009, 22h55mn 12s
> Objet : Re: [Qemu-devel] Virtio ballon device always loaded ?
>
> Sylvain Petreolle wrote:
> > Testing ReactOS in qemu made it always asking drivers for a RAM Controller.
> >
> > Looking at "info pci" output and hw/pc.c, I see that the Virtio balloon device
> is always loaded in an x86/64 target.
> > Is that a wanted feature ?
> >
>
> Sure, as I see no harm in not enabling it by default. ReactOS doesn't
> just ignore unknown PCI devices? That's strange because Windows seems to.
>
> Regards,
>
> Anthony Liguori
>
> > I also notice that hw/virtio-balloon.c header refers to the Virtio Block
> Device.
> >
> > Kind regards,
> > Sylvain Petreolle
> >
> >
> >
> >
"Please test them, especially with the applications in Downloader, and write
your results to
http://www.reactos.org/wiki/index.php/Tests_for_0.3.8"
I have a suggestion - we should limit the amount of people that are allowed
to actually write the results to some designated people and let everyone
pass the results to them.
Hello everybody (and especially the testers),
After nobody complained about branching 0.3.8 from trunk now, I took the
initiative today and prepared the branch with our usual customizations and
hacks.
It's now again the time for application testing. Therefore I uploaded Boot
CD and Live CD of the current branch to http://reactos.colinfinck.de/
Please test them, especially with the applications in Downloader, and write
your results to http://www.reactos.org/wiki/index.php/Tests_for_0.3.8
I especially write this now, because we want the release to be ready some
days before FOSDEM.
Andrew wants to start burning the CDs for FOSDEM soon, so it would be great
if we could get the entire release done till *next Monday*.
Best regards,
Colin
I've been using the Winetests in Windows quite a lot recently, both XP and
Vista, and I've noticed that a lot of the tests fail in Windows.
For anyone using the Winetests in reactos to fix our code, it's worth
testing if these functions pass or fail in Windows first as we might be
breaking reactos to pass the winetests.
Also, one of the problems I've noticed is that some tests fail on XP but
pass in Vista, and vice versa.
Does anyone know Wine's target OS? It seems that more tests are passing in
Vista than XP these days, so maybe they've moved to a more recent target?
I think the best way to move forward with this is to find out what version
Wine target, fix any broken tests we come across and submit them to Wine.
I don't envisage any problem with Wine accepting fixed test cases, even from
the most hated of reactos devs.
Anyway, I just wanted to make people aware, _don't blindly trust Winetests
when fixing reactos_
Ged.
If you are going to do more work on rbuild, I'd suggest doing it in a
branch to avoid clean rebuilds every few revisions.
Timo
hyperion(a)svn.reactos.org schrieb:
> Author: hyperion
> Date: Mon Jan 26 08:26:15 2009
> New Revision: 39111
>
> URL: http://svn.reactos.org/svn/reactos?rev=39111&view=rev
> Log:
> Begin moving rules out of modulehandler.cpp and into makefile include rules.mak, where they will be more readable and manageable. Currently implemented: target C compiler and target C++ compiler rules. Please do a clean build if possible. Testing with unusual output paths appreciated
>
>
Hi,
The TEB in psdk/winternl.h does not match with the correct one in
ndk/pstypes.h. Does anyone else see that as a problem or is it just
me? If it is for wine, then it is wrong, need to implement it as it is
in the SDK. Use it for the Tls fields only......
Thanks,
James
A general remark for this revision and r39033.
FsRtlNotifyInitializeSync and CcInitializeCacheMap both raise exception in case of failure, instead of returning a status. Should we consider adding PSEH support and usage to the new driver?
P. Schweitzer
> Date: Fri, 23 Jan 2009 12:18:39 +0000
> To: ros-diffs(a)reactos.org
> From: pschweitzer(a)svn.reactos.org
> Subject: [ros-diffs] [pschweitzer] 39040: Added notifications stuff to VCB
>
> Author: pschweitzer
> Date: Fri Jan 23 06:18:38 2009
> New Revision: 39040
>
> URL: http://svn.reactos.org/svn/reactos?rev=39040&view=rev
> Log:
> Added notifications stuff to VCB
>
> Modified:
> trunk/reactos/drivers/filesystems/fastfat_new/fat.c
> trunk/reactos/drivers/filesystems/fastfat_new/fatstruc.h
>
_________________________________________________________________
Téléphonez gratuitement à tous vos proches avec Windows Live Messenger ! Téléchargez-le maintenant !
http://www.windowslive.fr/messenger/1.asp
Hi,
I am working on a project to parse the Windows image file. To do that,
I must understand the structure of some Windows components, like
_EPROCESS. So I took some headers from ReactOS, and write *userland*
code like below:
----
#include <pstypes.h>
#include <stdio.h>
int main()
{
printf("size of EPROCESS: %d\n", sizeof(struct _EPROCESS));
return 0;
}
----
The I got the problem: g++ reported that _EPROCESS is incomplete.
Clearly this means it doesnt see the structure _EPROCESS, so I took a
closer look, and found that _EPROCESS is not defined in user-mode
(NTOS_MODE_USER). I tried to fix it by putting
#undef NTOS_MODE_USER
in front of #include <pstypes>, but that doesnt help.
Anybody please tell me if there is any way to fix this?
I think I can fix that by modifying the original headers. but that is
way too ugly.
Many thanks,
Jun
sginsberg(a)svn.reactos.org wrote:
> Author: sginsberg
> Date: Sun Jan 18 17:31:26 2009
> New Revision: 38922
>
> URL: http://svn.reactos.org/svn/reactos?rev=38922&view=rev
> Log:
> - Fix more InterlockedCompareExchangePointer warnings in crypt32 -- this to Wine, too
>
> Added:
> trunk/reactos/dll/win32/crypt32/warningfixes.diff
This is a bad idea.
It's painful enough keeping wine libs in sync without adding to the complexity with non-needed warning fixes.
Ged.
hyperion(a)svn.reactos.org schrieb:
> Author: hyperion
> Date: Sun Jan 18 00:25:43 2009
> New Revision: 38872
>
>
...
> Introduce new define __ROS_LONG64__ ("assume 64-bit long"), to use int instead of long in typedefs of 32-bit integers
> __ROS_LONG64__ automatically defined if __WINESRC__ is defined. No, __WINESRC__ alone is not enough
>
If it's defined automatically, why isn't __WINESRC__ alone enough? And
when it's not enough anyway, why define __ROS_LONG64__ automatically at
all?
...
> #else /* !_WIN64 */
> +#if !defined(__ROS_LONG64__)
> typedef int INT_PTR, *PINT_PTR;
> typedef unsigned int UINT_PTR, *PUINT_PTR;
> +#else
> +typedef long INT_PTR, *PINT_PTR;
> +typedef unsigned long UINT_PTR, *PUINT_PTR;
> +#endif
>
If we assume a 64bit long, why define INT_PTR to long on 32 bit target?
> From: Hauke Goos-Habermann <HHabermann(a)pc-kiel.de>
> Date: January 12, 2009 4:53:40 PM GMT+03:00
> To: aleksey(a)reactos.org
> Subject: ReactOS booth/speech at Linux days in Kiel?
>
> Hi Aleksey,
>
> for the Linux days in Kiel in Germany we are searching for
> interesting OSS
> projects. Can you tell me if there are members of ReactOS that may be
> interested in a booth or/and giving a presentation? The "Kieler
> Linux- und
> -OpenSource Tage" will be at 2nd and 3rd of october.
>
> Additional information (in German only) can be found at: www.kieler-
> linuxtage.de
>
> PS. Please forward the mail to interested members.
>
> Cu Hauke
>
> --
>
> Stoppt Softwarepatente, sonst wird Softwareentwicklung in Europa
> für die meisten
> illegal!
> Patentfrei sichert IT-Arbeitsplätze (www.patentfrei.de)
> Sorry I didn't quite get it. ;-) What is ok atm? How are we going to
> handle it?
Extern inline is ok atm. ;-)
I mean that it works well now. And when its behavior will be changed,
gnu_inline attribute can be used to get old (i.e., present) behavior.
> Well that was a workaround, because of "static declaration follows non
> static declaration".
> Then it needs to be done differently. But I don't see any good solution
> that doesn't require lot's of hacks atm, except disabling that warning.
It's ok atm. Attribute gnu_inline can be used to get old inline semantics.
Hi All!
Just letting everyone know that a partial fix has been found by Dmitry
aka Lentin, it is Dmitry? Well, I updated the bug report and the patch
works to a point. FF does try to minimize and there is a hook bug
exposed. Yes, not everything is fixed, since we use wine code, this
was the reason for the patch. It corrects most of the message bugs
related to wine tests. So this patch is going in soon and we need to
cleanup the related code. I have a synced User32 Mdi.c that might
require this patch to work. Just about the rest of the changes needed
are wine sync/ports to user32/win32k. I would hope that everyone can
help Dmitry/Lentin out and fix the rest of the SetWindowPos bugs. Some
window position code in User32 still needing to be updated.. ;^)
Thanks,
James
Ref:
http://www.reactos.org/bugzilla/show_bug.cgi?id=2451
There's a constant for this INVALID_HANDLE_VALUE...
On 10-Jan-09, at 7:33 AM, dchapyshev(a)svn.reactos.org wrote:
> case 0xFFFFFFFF: /* File does not exist */
Best regards,
Alex Ionescu
Hi!
Why to use extern inline there, FORCEINLINE macro uses static. Extern
inline — GCC extension — does not work as needed in c99/gnu99 mode
(non-inline functions are emitted as well). GCC documentation says it
will be the default in the future.
Since Arty just mentioned GIT, I think it's about time to uncover a
ReactOS GIT mirror I've been setting up recent couple of weeks.
It works pretty good so far, autoupdates every 10 minutes, so it
stays quite up-to-date.
URLs:
git://git.reactos.org/ - for git cloning.
http://git.reactos.org - for web viewing.
As for branches, it was actually my main intention in using a DVCS,
because SVN branches are greatly uncomfortable to develop anything
because of the need to keep the branch up-to-date.
But, to prevent any gossips, SVN stays as our main repository, and
GIT mirror is just for exploration of new possibilities, and for
comfortability of working with branches - if someone wants to try
that out. Usual SVN branches are still permitted.
WBR,
Aleksey Bragin.
Hello,
I recently spent some time experimenting with various Cc rewrites we
have in our tree, and before that I extensively tested our fastfat
driver in a real NT environment (MS Windows 2003).
The conclusion of the above work is that our fastfat driver either
needs serious bugfixing, or a rewrite is needed. It corrupts
directory tables in a real NT, leads to unusual behaviour of cc-
rewrite branch, and may have side effects on arty's newcc.
Before this is done (bugfixing or rewriting, developing and testing
against a Windows 2003 at least, not ReactOS), it's meaningless to
continue any other work on Cc and related Mm parts.
WBR,
Aleksey Bragin.
Hi all!
Here is the test program provided by BugBoy. It also shows another
bug, see bug 3971. Please test before and after the patch.
Thanks,
James
PS
Good Job, Michael!
Hi,guys
I'm just a fan of ReactOS,now I have two questions.
1, Is(or will be) there an disk management utility for ReactOS, or in
another way, will we make an implementation of Microsoft diskmgmt.msc?
2, Will ReactOS group make an implementation of Microsoft Management
Console for ReactOS?
Thank you!
Yeah, sorry, the target device should be used to send a
TARGET_DEVICE_CUSTOM_NOTIFICAITON of type GUID_IO_VOLUME_CHANGE at the
end of the function (IoReportTargetDeviceChange).
FYI, Pierre, when you implement the notification system.
On 4-Jan-09, at 5:12 AM, fireball(a)svn.reactos.org wrote:
> Author: fireball
> Date: Sun Jan 4 04:12:38 2009
> New Revision: 38552
>
> URL: http://svn.reactos.org/svn/reactos?rev=38552&view=rev
> Log:
> - Revert changes to NtSetVolumeInformationFile made in 38550, it
> should indeed use IoGetRelatedDeviceObject, not target device.
>
> Modified:
> trunk/reactos/ntoskrnl/io/iomgr/iofunc.c
>
> Modified: trunk/reactos/ntoskrnl/io/iomgr/iofunc.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/iofunc.c…
> =
> =
> =
> =
> =
> =
> =
> =
> ======================================================================
> --- trunk/reactos/ntoskrnl/io/iomgr/iofunc.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/io/iomgr/iofunc.c [iso-8859-1] Sun Jan 4
> 04:12:38 2009
> @@ -3307,8 +3307,7 @@
> }
>
> /* Get the device object */
> - Status = IoGetRelatedTargetDevice(FileObject, &DeviceObject);
> - if (!NT_SUCCESS(Status)) return Status;
> + DeviceObject = IoGetRelatedDeviceObject(FileObject);
>
> /* Clear File Object event */
> KeClearEvent(&FileObject->Event);
>
Best regards,
Alex Ionescu
Hi,
the declaration of FsRtlNotifyReportChange was correct, even if this function is now deprecated (that's why it doesn't need to be in DDK).
WBR,
P. Schweitzer
_________________________________________________________________
Inédit ! Des Emoticônes Déjantées! Installez les dans votre Messenger !
http://www.ilovemessenger.fr/Emoticones/EmoticonesDejantees.aspx
Why do you need to start on real hardware?
This is fairly unsupported at the moment, so you’re really in no-mans-land here.
I’d suggest a virtual machine until you become more familiar with it.
Anyway, looking at your hardware spec I don’t see any untoward.
Continuing down the real hardware path, your next step is to obtain debug output.
The only current method to do this is via a null-modem cable, as specified in the link I gave you.
Ged.
From: James Muthee [mailto:jsoftpacks@yahoo.co.uk]
Sent: 31 December 2008 09:12
To: Ged
Subject: RE: [ros-dev] Problems installing REACTOS
Hello Ged.
Thanks for the prompt reply.
First, I need to test the software on a real machine. No Virtualization, no support form any other OS.
As for the exact configuration of the system, I am forwarding the entire report from the windows system info.
I know its lengthy but, then again you would be looking for someting specific.
My disks are FAT32
Please help.
Thanks
James I. M.
--- On Tue, 30/12/08, Ged <gedmurphy(a)gmail.com> wrote:
From: Ged <gedmurphy(a)gmail.com>
Subject: RE: [ros-dev] Problems installing REACTOS
To: jsoftpacks(a)yahoo.co.uk, "'ReactOS Development List'" <ros-dev(a)reactos.org>
Date: Tuesday, 30 December, 2008, 1:59 PM
It could be a whole range of things.
Without having your hardware spec and debug output, it’s impossible to tell.
If you just want to test it, it’s better to run it in a virtual machine.
If you’re insistent on running it on hardware, then you’ll need to start by supplying your hardware details.
If that doesn’t show any obvious problems (e.g. SATA, NTFS, etc) then you will need to grab debug output via a null cable modem <http://www.reactos.org/wiki/index.php/Debugging#Real_computer:_Physical_ser…> http://www.reactos.org/wiki/index.php/Debugging#Real_computer:_Physical_ser…
Good luck.
Ged.
From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of James Muthee
Sent: 30 December 2008 11:21
To: ros-dev(a)reactos.org
Subject: [ros-dev] Problems installing REACTOS
Hello.
Having downloaded the software (I was amazed it was less than 40MB), I wrote the ISO on a CD and started the installation.
0.3.7 failed to install completely, stopping dead just after loading the initial files.
I downloaded the 0.3.6 and tried again. This time, I was able to install the first portion (copying the textmode installation to the hard disk and modifying the MBR).
On restart, A GUI window flashed then a blue screen with a single line about the Build, and that was the end.
What am I doing wrong?
I would appreciate any help. I really want to test drive this software.
James I. M.
Just wanted to tell this is a great work, and with such test suite we
will always notice if something breaks.
WBR,
Aleksey Bragin.
On Dec 30, 2008, at 7:04 AM, hyperion(a)svn.reactos.org wrote:
> Author: hyperion
> Date: Mon Dec 29 22:04:51 2008
> New Revision: 38461
>
> URL: http://svn.reactos.org/svn/reactos?rev=38461&view=rev
> Log:
> modified tests/pseh2/psehtest.c
> finally_13 test re-enabled, as it doesn't crash anymore
> finally_14 test fixed. Now we know how exceptions thrown in a
> __finally are supposed to be handled
> PSEH test suite now has 91 tests and passes all of them with
> both GCC and Visual C++
Hello.
Having downloaded the software (I was amazed it was less than 40MB), I wrote the ISO on a CD and started the installation.
0.3.7 failed to install completely, stopping dead just after loading the initial files.
I downloaded the 0.3.6 and tried again. This time, I was able to install the first portion (copying the textmode installation to the hard disk and modifying the MBR).
On restart, A GUI window flashed then a blue screen with a single line about the Build, and that was the end.
What am I doing wrong?
I would appreciate any help. I really want to test drive this software.
James I. M.
Hi,
I imported function ReplaceFileW from Wine, but it do not work in ReactOS.
RepleceFileW there do not pass 11 tests (kernel32_winetest file). I think,
that a problem in call MoveFileEx. Somebody can help with it?
Function in Wine: http://www.reactos.org/paste/index.php/2745/
Patch for ReactOS: http://www.reactos.org/paste/index.php/2744/
--
WBR,
Dmitry Chapyshev
Hi ALL!
Okay, not sure what is going on but here is the original output:
Unhandled exception
ExceptionCode: c0000005
Faulting Address: 682000
Address: 7c91e6ae C:\ReactOS\system32\ntdll.dll
CS:EIP 1b:7c91e6ae
DS 23 ES 23 FS 3b GS 0
EAX: 011f0020 EBX: 011f0020 ECX: 090b071d
EDX: 242c2c64 EBP: 008afc54 ESI: 00681ffe ESP: 008afc4c
EDI: 011f1010 EFLAGS: 00010212
Frames:
77e30000+211d2 C:\ReactOS\system32\user32.dll
77e30000+21365 C:\ReactOS\system32\user32.dll
77e30000+20c56 C:\ReactOS\system32\user32.dll
400000+892c C:\ReactOS\user32_crosstest.exe
400000+8e73 C:\ReactOS\user32_crosstest.exe
400000+a3ab C:\ReactOS\user32_crosstest.exe
400000+b4ac8 C:\ReactOS\user32_crosstest.exe
400000+b4c56 C:\ReactOS\user32_crosstest.exe
400000+1247 C:\ReactOS\user32_crosstest.exe
400000+1298 C:\ReactOS\user32_crosstest.exe
7c700000+218e4 C:\ReactOS\system32\kernel32.dll
(subsystems/win32/csrss/api/wapi.c:115) CSR: received hard error c0000144
(subsystems/win32/csrss/win32csr/dllmain.c:528) The instruction at
"0x7c91e6ae" referenced memory at "0x00682000". The memory could not
be "read".
After patch:
We have a thread overrun, these are already freed! pi -> 18808864 bi -> 6819854
We have a thread overrun, these are already freed! pi -> 18808864 bi -> 6819854
Than, get two exit strings at the command console.
bi -> 6819854 (0x68100E) is the one and it is from MapViewOfFile. The
difference from 0x682000 is 4082.... Well with in the normal page but
why is 0x68100E the start address and not 0x681000?
It could be just simply bad math being used in LoadBitmapImage. Wine
does use the same code in user32 from gdi32 to handle bitmap and
friends.
Thanks,
James
Hi rosdevs!
This is an issue I've been working on for a while on the Wine side of
things and now they have initial support for it. If any of you
Win32k/GDI hackers are interested in making ReactOS look a bit better
on LCDs please enable support in freetype and review the following
Wine patch to get an idea of the requirements.
Thanks
http://source.winehq.org/git/wine.git/?a=commitdiff;h=028617b90ba586bdb3072…
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Hi,
Mozilla Firefox 2.0: install it, run it, then quit - total hang
without KDBG or any exception, TAB+K doesn't work.
Then, reboot - try to navigate via Start Menu to Applications ->
Mozilla Firefox. Explorer will die with exception in dll/win32/user32/
misc/exticon.c:88 (find_entry_by_id). Maybe due to files corruption.
WBR,
Aleksey.
tkreuzer(a)svn.reactos.org wrote:
> For some unknown reason wmc likes to include string.h from the wine folder
and we cannot link it on linux hosts. This hack should hopefully resolve the
issue.
Not that mysterious actually.
The "include/reactos/wine" directory is shared among Wine host and target
tools while "include/crt" contains target-only headers and thus it's only
available for target components.
Therefore #include_next cannot find any other "string.h" file, when you use
it inside host tools. Furthermore, #include_next is a GCC-only thing, so we
should avoid it wherever possible.
To circumvent these problems and remove the hacks from the actual CRT/PSDK
headers, I propose we i.e. add '#include <reactos/wine/string.h>' to the CRT
"string.h" and do the appropriate thing for other files.
This is the prettiest solution I can think of without editing a bunch of
Wine files.
Best regards,
Colin
Sooner or later, this problem should be solved somehow. And not only for
Armenians, but also for other peoples of the world, who live without code
pages.
I concur with James.
Eric, I think what you meant to say is you don't have time to work on
ReactOS in its current state -- ie: the slow, time-consuming
procedures and behaviors that take up more than 50% of your free time.
What if ReactOS provides you with your own branch, and the ReactOS
project assumes the responsibility of merging your changes to trunk,
performing the testing and regression testing. You might be afraid
that your code will "rot" and that it would never make it inline, but
I'm sure the people respect your work as much as I do and would make
sure that things stay up to date (much like we sync with Wine).
This would allow you to keep committing code, have your own branch
which at least works for you, and we'd take care of merging. Your only
real responsibility would be to "sync up" with trunk every once in a
while -- could even be only ever 3 months, or if you notice something
obvious that might affect you (RPC changes, WIDL changes, SCM etc).
I know this may sound unfair to other developers, but as James pointed
out, you deserve everyone's time, considering how much you've put in
all this time.
On 19-Dec-08, at 9:22 PM, James Tabor wrote:
> Hi Eric!
> Eric Kohl wrote:
>> Hi!
>>
>> Effective immediately I am taking a break from working on ReactOS
>> for an
>> undetermined period of time. It may even be the end of my involvement
>> with ReactOS.
>>
>> There are several reasons for me to quit but the most important one
>> is
>> lack of time. I have a pretty exhausting job and spend more than 2
>> hours
>> a day to commute so there is not much time left to spend on ReactOS.
>> So working on ReactOS happened on weekends only.
>>
>> After my latest patch was partially reverted, I decided that I am not
>> willing to create and maintain a development branch for
>> improvements to
>> LSA and SAM. I am not willing to spend an hour or two each weekend
>> for
>> branch maintenance and debugging and another two or three hours for
>> developing new code. It just does not make sense to me.
>>
>> Maybe I will be back one day, maybe I will not. Time will tell.
>>
>> Over and out!
>> Eric
>>
> Your resignation is disapproved! You are an integral part of this
> project.
>
> You are the last of the root members of this project. We need your
> help
> and if that means breaking ReactOS truck that is your right to do
> so. We will
> learn to live with it. I have followed your work for years and I
> would like
> to see you more. Based on your tenure with this project, this gives
> you
> rights, influences and guidance to this project.
>
> Please recommence with your changes,
> James
> _______________________________________________
> Ros-general mailing list
> Ros-general(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-general
Best regards,
Alex Ionescu
Hi,
we are a software development company that develops and maintains a
Linux-based server solution called IServ, designed for use in schools.
We are in business since 2003, and there are currently about 370 schools
in Germany using IServ as their portal server.
One feature that we would like to integrate into our product is the
possibility to customize the ntconfig.pol file. This file, located on
the server's netlogon share, can deploy registry settings to Windows
clients - it is especially important because it can deploy
HKEY_LOCAL_MACHINE settings. This file is a binary registry hive. At the
moment, we have to create this file manually with poledit.exe.
We need a Linux program which can automatically generate this file.
1) It should read plain text files as input, for example an INF file.
2) The resulting policy file must work with Windows 2000 and XP x86
clients. It should be possible to easily test this by using the command
"Load Hive" in Regedit.
3) The preferred programming language is Perl, C/C++ is also OK. Other
languages should also be possible, but only after prior consultation
(just to make sure nobody comes up with Java ;) ).
4) The resulting source code should be released as open source, e.g.
under the GPL.
We would like the program being finished in one month. We will pay you
EUR 300 for it. If the program is very much work and you feel you need
more money, submit us an offer.
A Perl library to dump binary registry files to plain text:
http://search.cpan.org/~jmacfarla/Parse-Win32Registry-0.30/
Attachments:
ntconfig.pol - Our current policy. This must be generated automatically.
ntconfig.pol.dump - Plain text dump of that file, generated with
Parse::Win32Registry.
winnt.adm - Template to edit our policy file with poledit.exe.
Our homepage: http://iserv.eu (only in German, though)
--
Yours sincerely,
Martin v. Wittich
IServ
Falk & Ludwig GbR
Rebenring 33
38106 Braunschweig
Germany
Telephone: +49 531 380 4450
E-Mail: martin.von.wittich(a)iserv.eu
Internet: http://www.iserv.eu
hi, i'm a newbie of ReacOS.
I looked a piece of code in syscall.S which is come from 0.2.7 edtion.
/* Raise IRQL to APC_LEVEL */
movl $1, %ecx
call @KfRaiseIrql@4
could anybody help me explain why the function is decorated by @ in the head?
and why transfer argument by ecx?
Thank you
___________________________________________________________
好玩贺卡等你发,邮箱贺卡全新上线!
http://card.mail.cn.yahoo.com/
Hi,
Guys(and Girls) did you heard about a program called "stress prime"?
It was developed to calculate prime numbers. And it is very sensitive
to small errors.
Since it has some kinda detecting errors, many overclockers are using
it to confirm overclocked H/W stability.
Yes, I tried to run this program, just for fun, and surprise! The
system is not overclocked, nor has problem when running stressprime on
WindowsXP.
The rounding error amount was huge. I saw the source code of the
stress prime and I'm sorry it was assembly language, so I couldn't
check what could make such prolem under ReactOS. It was all about the
math, and I'm not good at both(asm,math)
But, one thing sure, is something is not working properly(maybe
kernel?) and it is affecting ReactOS stability.
What is your opinion? any comments?
--
Regards,
Ashuaria Lee
Hi,
Alex Ionescu wrote:
> You should always use memset and void HEAP_ZERO_MEMORY.
Could you please tell why HEAP_ZERO_MEMORY should not be used?
It is used in many places, so if something wrong with RtlAllocateHeap, maybe
better to fix it?
Thanks,
Dmitry
hi,guys:
I don't know if it is proper to ask such a question here. I'm sorry if
I break some rules.
why IOCTL_DISK_GET_DRIVE_GEOMETRY_EX fail in windows 2000 and succeed in
windows xp and greater version?
or how can I get a disk(whatever,ATA,SCSI,USB )'s real size(including
additional sectors) in a easy way in windows 2000, just like there is such a
function,
__int 64GetDiskRealSize(HANDLE hDisk);
Could anybody help me?
Waiting for reply.
Thank you!
On Tue, Dec 9, 2008 at 12:58 AM, <jimtabor(a)svn.reactos.org> wrote:
> Author: jimtabor
> Date: Mon Dec 8 23:58:23 2008
> New Revision: 37952
>
> URL: http://svn.reactos.org/svn/reactos?rev=37952&view=rev
> Log:
> - Add CP_UNIXCP for CP_ACP, this will help cross tests.
>
> Added:
> trunk/reactos/include/reactos/wine/winnls.h (with props)
> +#ifndef __WINE_WINNLS_H
> +#define __WINE_WINNLS_H
> +
> +#define CP_UNIXCP CP_ACP
Rather than keep the include_next brokeness, perhaps we should add the
define to wine/port.h and include that in any offending source file.
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Hi folks,
yesterday a user shows me a program what is working properly under windows,
but not working under reactos. It was an open source program and it was easy
to figure out the problem. It was an invalid win-api-call (wrong parameter
value). Due to this situation I would like to ask one question. How
compatible reactos should be? Even fault compatible?
Matthias
--
Matthias Kupfer Telefon +49 (0) 371 236 46 52
Wilhelm-Firl-Straße 21 Mobil +49 (0) 160 859 43 54
09122 Chemnitz
Steven Edwards wrote:
> We discussed something like this years ago. It would be nice if every sort
> of legacy API that has any sort of hacks for brokeness as part of its
> implementation, could be isolated and a simple recompile with something
> like a #define NO_LEGACY_WIN32 so you could recompile without the hacks.
> Not really that useful for the real world as you need the backward
> compatibility but it is a nice idea for embedded or non-normal windows
> targets like ARM.
I think this is like compiler warnings. Some checks are disabled by default
as they would cause more harm than good. But there is an option to enable
them. It will help to catch bugs in software.
>> It was already broken in r37496.
> Gdi is right Win32k is wrong.
I mean that GCC (by default) silently discards code like
if (i < 0) { ... }
where i is unsigned. So there was a bug in GDI...
Now that Stefan has cleaned up some stuff in the ddk headers, maybe we
should think of some additional design fixes here.
We currently have ntddk.h include "per version" headers: winxp.h,
win2k.h, winnt4.h. These contain very few stuff.
My suggestion is to merge them into winddk.h. We could also merge
winddk.h and ntddk.h
It might make sense to split wdm.h and ntddk.h into architecture
specific files
Layout suggestion:
- ntddk.h: includes wdm.h and contains arch-independent definitions
currently in winddk.h/win2k.h/winnt4.h
- wdm.h: includes arch-dependent headers, contains arch-independend wdm
definitions
- ddk_x86.h / ddk_x64.h, ddk_arm.h, ddk_ppc.h / ddk_mips.h:
arch-dependent definitions for both wdm.h and ntddk.h definitions
(#ifdef _NTDDK_ ...)
Comments appreciated.
Timo
What's the reason to copy & paste comments from ms headers?
Please remember: Interfaces are not copyrighted, header files (including
the comments) are!
> +//
> +// Types to use to contain PFNs and their counts.
> +//
> +typedef ULONG PFN_COUNT;
> typedef ULONG PFN_NUMBER, *PPFN_NUMBER;
> +typedef LONG SPFN_NUMBER, *PSPFN_NUMBER;
>
Hi! I'm sorry I broke the trunk.
About "extra" comma within braces, it is not a mistake. It is allowed.
There is a fragment of C grammar:
initializer
: assignment_expression
| '{' initializer_list '}'
| '{' initializer_list ',' '}'
;
Hello,
booting bootcd leads to a stackfault of VMWare, build server
experiences similar problems.
Trunk is locked with write access available to Dmitry Gorbachev to
fix the issue, and to anyone by request who has the fix.
WBR,
Aleksey Bragin.
On Dec 3, 2008, at 8:34 PM, dgorbachev(a)svn.reactos.org wrote:
> Author: dgorbachev
> Date: Wed Dec 3 11:34:49 2008
> New Revision: 37830
> -static FREELDR_SETTINGS Settings = { 0, {0}, 0 };
> +static FREELDR_SETTINGS Settings = { 0, { 0, }, 0, 0, FALSE };
I suspect there is a typo in the above line ("extra" comma within
braces, should've been something like 0, {0, 0}, 0, FALSE instead
probably).
WBR,
Aleksey.
Hi Eric,
Just wanted to tell you that your patch is correct and the Release
Buildslave is failing as you can see from its log. For some reason, it
stopped cleaning properly today and also has weird file deletion issues
sometimes.
But as long as the patch builds on the Debug slave, it's correct in 99% of
all cases.
Wanted to finish this mail before you reverted in r37802, but I was too
slow. :-(
So, it's safe for you to reapply r37801 and it's here to stay!
Best regards,
Colin
On Nov 30, 2008, at 10:19 PM, gschneider(a)svn.reactos.org wrote:
> Author: gschneider
> Date: Sun Nov 30 13:19:45 2008
> New Revision: 37774
> - if (!(tmp = (char*)und_alloc(sym, len))) return NULL;
> + if (!(tmp = und_alloc(sym, len))) return NULL;
You might want to keep these when syncing, it reduces compiler warnings.
Hello, everyone.
Since I'm new to this mailing list, I may ask stupid questions, so
don't be mad at me. ;-)
I was trying to get the status of east asian language support, but
couldn't find it in the wiki.
Could someone tell me some brief status about east asian support?
--
Regards,
Ashuaria Lee
On Sat, Nov 29, 2008 at 2:35 PM, <sginsberg(a)svn.reactos.org> wrote:
> Author: sginsberg
> Date: Sat Nov 29 13:35:04 2008
> New Revision: 37739
>
> URL: http://svn.reactos.org/svn/reactos?rev=37739&view=rev
> Log:
> - Kill off ramdrv, it is deprecated since a long time ago.
> See issue #3422 for more details.
The problem was as far as I can tell not ramdrv but ramdrv/minix. I
really think you should revert part of this.
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Hi Team!
First, here is my personal list of last years goals for the rewrite.
Most of you already know what I had plan for last year so please bare
with me.
___
December 2007:
End of previous year rewrite of definition files and structure
integration with updates to ntgdibad.h. Housekeeping, test and verify.
Add previous years loose ends and carryovers.
Thomas help with user window handle support is a great bonus to the
year end progress toward win32k rewrite. Timo win32k cross tests.
Magnus integration of DDxD support is still in progress and ticking
along nicely.
January 2008:
Miscellaneous Gdi adds, fix ups and cleanup.
February 2008:
Integration and implementation of Enhanced/Meta/Dc/File support.
This is a wine sync/port that I have started during the beginning of
the rewrite. Delayed and carryover.
May 2008:
Gdi/User Win32k DCE cleanup and fixes.
90% complete. One unique test case needing to be integrated in code base.
June 2008:
Gdi cleanup and verify testing. Integrate simple multi display
support. DC and PDEV integration and cleanup.
Partial DC and PDEV structures are supported and minor cleanup and
testing was meant. No multi display add ons are included. Delayed and
carryover.
July 2008:
Start prerewrite of User32/Win32k. Cleanup headers and add new types
and structures.
Started and carryover.
September 2008:
Housecleaning, Gdi testing and verifying.
Still in progress.
November 2008:
Start User32/Win32 Menu rewrite.
Still in progress, new structure support is in and working in test tree.
December 2008:
End of year housekeeping with cross test and verify. Add previous
years loose ends and carryovers.
Slow integration of known gdi structures have been completed.
Attribute support is only for DC's, investigating a more conservative
process of allocation and utilization of Brush/Pen /Regon and Font
attribute support that is compatible with gdi. Carryover and finish up
window handle and integration support. Timo started integration of
user process/thread structures and support, leaving win32k
initialization bug open for more investigation. Magnus DDxD is back on
track. Stefan cleanup of win32 functions was completed.
January 2009:
Add new members to the rewrite team, start training and information
exchange. Setup freelance hacker member list which would include just
about everyone with commit access.
--------
This is my personal list and included comments about team members
progress. I'll add more after January for 2009.
Side Note: Please do not post here if you are interested in joining
the rewrite team. If you have commit access you are already in. We
need to know your specialties, interests and goals which include what
you want to learn so this can be carried into your next career. Resume
stuffer for the next job and what knots.
Thanks,
James
On Thu, Nov 27, 2008 at 3:52 PM, <gschneider(a)svn.reactos.org> wrote:
> Author: gschneider
> Date: Thu Nov 27 14:52:01 2008
> New Revision: 37695
>
> URL: http://svn.reactos.org/svn/reactos?rev=37695&view=rev
> Log:
> Update gdi32 winetests, so we don't run out of things to fix.
Best commit message ever.
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Hi folks,
due to the perpetual problems with utf-16 files I recommend to change the
handling in the following way as long as we don't have another working
translation system (mui) and we want to keep a win32 compatible inf file:
We should store the files in subversion as utf-8 and convert during make and
rbuild in utf-16 (e.g. via small c-programm or new rbuild-command), so we can
edit and make diffs in an easy way.
Comments are very welcome
Matthias
--
Matthias Kupfer Telefon +49 (0) 371 236 46 52
Wilhelm-Firl-Straße 21 Mobil +49 (0) 160 859 43 54
09122 Chemnitz
Hi!
I have a linking error because GCC-4.4 inserts calls of
___enable_execute_stack() into functions which use PSEH. It seems that this
behavior cannot be changed without changing the GCC itself. Or maybe I
should provide an empty ___enable_execute_stack() function just to satisfy
the linker.
> This is already done, most files which have Wine code are labeled so atop
> of the file ("Some parts are taken from Wine project..."). What I see is
> that Dmitry Timoshkov says this is not enough.
It should be enough if the original copyright notices are kept. No need to
research origins of every piece of code.
LGPL 2.1:
> 1. You may copy and distribute verbatim copies of the Library's complete
> source code as you receive it, in any medium, provided that you
> conspicuously and appropriately publish on each copy an appropriate
> copyright notice and disclaimer of warranty; keep intact all the notices
> that refer to this License and to the absence of any warranty; [...]
> 2. You may modify your copy or copies of the Library or any portion of
> it, thus forming a work based on the Library, and copy and distribute such
> modifications or work under the terms of Section 1 above, [...]
GPL-HOWTO:
> If you have copied code from other programs covered by the same license,
> copy their copyright notices too. Put all the copyright notices together,
> right near the top of each file.
On Fri, Nov 21, 2008 at 2:23 PM, <sginsberg(a)svn.reactos.org> wrote:
> URL: http://svn.reactos.org/svn/reactos?rev=37523&view=rev
> Log:
> - winternl.h is deprecated since the NDK was invented, don't use
I am sure there are some wine sources somewhere that we have the make
use of it but perhaps we could add some sort of check like
#ifndef __WINESRC__
#error Don't use winternl.h!
#endif
or something similar.
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Replying to myself...
> (sent to AROS (please forward, I'm not on the dev list), ReactOS,
> Syllable, CCed to Haiku)
Moved from ros-general to ros-dev as the former seems very quiet...
>
> Hello,
> I'm a Haiku developer, <http://haiku-os.org>
> and I would like to propose sharing a devroom, eventually a booth at
> FOSDEM with some other FOSS OS projects.
As I've been told by the orga,
other projects should also book the devroom officially:
http://fosdem.org/2009/call_for_devrooms_and_stands
Just add you are ok to share it.
The official deadline is tomorrow...
>
> I sent to the mailing lists as I couldn't identify a specific
> contact,
> and I don't know how much centralized each project is.
>
> Last year we had our own booth at FOSDEM (we it shared with an ERP
> software),
> I really enjoyed the event, and would like to also get a devroom this
> year.
> But I'm not sure we will have enough people to animate it all the
> time
> (currently 3 or 4), plus we'd still have a stand to look after.
>
> http://www.haiku-os.org/blog/mmu_man/2008-02-25/hello_from_fosdem
>
> I know we shared a booth at last LinuxWorld with ReactOS and I heard
> it
> was interesting:
> http://www.haiku-os.org/blog/umccullough/2008-08-06/day_1_at_linuxworld_200…
> > http://www.haiku-os.org/blog/umccullough/2008-08-07/day_2_at_linuxworld_200…
> >
> As the deadline for booth and devroom application approaches (it's
> before 22 nov.), I was thinking about sharing a devroom that could be
> called "alternative OSes", "grep -v GNU/Linux" or alike, with other
> projects.
> This way we could all get a devroom with fewer people to man it.
>
> As for our project, we could have talks and hacking sessions on many
> subjects, from architecture and design to installation, and specific
> things like the using the FreePascal port, porting applications,
> using
> replicants (like NetSurf).
>
> We could also have common talks, about the platforms we support, our
> design and goals.
>
> And if needed we could probably also share a booth with another
> project
> I suppose, last year we shared with a totally different software.
>
> I'll be mailing a booth and devroom request tomorrow precising it,
> before it's too late.
>
> François.
>
Ok,marc ;)
I have sent u a mail to: marc.piulach(at)live.com. Sure it will be clasified as Spam so give a look there.I have sent the email in perfect Spanish(i guess u are from Spain,or at least you understand Spanish).
There are at least 2 Reacters in Seville with time to show Reactos in Imaginatica.Also some other spanish people have shown some interest to help with it.
You can contact with me in vicmarcal(at)hotmail.com, so we can begin (if u want) to prepare this Event.
Thanks Marc.
_________________________________________________________________
Los más de lo más, Especial Rankings
http://events.es.msn.com/dinero/listas/default.aspx
Hi Victor,
I haven't done any special "negotiations" mainly because anyone expressed interest on participating in the event. In case you or anyone else want to participate feel free to contact me and maybe we can workout something
Regards,
/Marc
From: victor martinez
Sent: Thursday, November 20, 2008 4:01 PM
To: ros-dev(a)reactos.org
Subject: [ros-dev] Re: Event invitation [jornadas Imaginática 2009]
Hi All,I have been contacted/invited to participate and give a talk about ReactOS in an event organized by the university of Seville, spain (very beautiful city!) on 2-6 March 2009. It would be great if some of the other spanish based members are also interested on participate, I have been disconnected from the project lately due to offline life but would be willing to participate in this event and help to spread the word about reactos in academic circles.More information here (in spanish): http://imaginatica.org/2009/descargas/Dossier.pdfRegards,/MarcHi Marc, there are spanish people in Seville interested in Imaginatica Event. Does the invitation still available?How goes the "negotiations"?are they still counting on us being at Imaginatica?Thanks in advance. This event mix the most important IT companies,and also there are a lot of skilled developers.This is one of the most important Event in Spain (since SIMO has been cancelled).So being in Imaginatica must be a priority ;)VicmarcalSeville
--------------------------------------------------------------------------------
No te aburras más, engánchate a los Juegos de Messenger
--------------------------------------------------------------------------------
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
Hi All,
I have been contacted/invited to participate and give a talk about ReactOS in an event organized by the university of Seville, spain (very beautiful city!) on 2-6 March 2009. It would be great if some of the other spanish based members are also interested on participate, I have been disconnected from the project lately due to offline life but would be willing to participate in this event and help to spread the word about reactos in academic circles.
More information here (in spanish): http://imaginatica.org/2009/descargas/Dossier.pdf
Regards,
/Marc
Hi Marc, there are spanish people in Seville interested in Imaginatica Event. Does the invitation still available?How goes the "negotiations"?are they still counting on us being at Imaginatica?
Thanks in advance. This event mix the most important IT companies,and also there are a lot of skilled developers.This is one of the most important Event in Spain (since SIMO has been cancelled).
So being in Imaginatica must be a priority ;)
Vicmarcal
Seville
_________________________________________________________________
Los más de lo más, Especial Rankings
http://events.es.msn.com/dinero/listas/default.aspx
Has anybody considered to use the openwatcom compiler for ReactOS?
http://www.openwatcom.org/index.php/Main_Page
At least it provides a proper native SEH implementation and is as free
as the GCC is.
➧ Marcin Dalecki ❖
These are correct changes.
On Tue, Nov 18, 2008 at 10:34 AM, Aleksey Bragin <aleksey(a)reactos.org> wrote:
> May I ask why those if (!Info) checks are required? To me it makes no
> sense to call those APIs with the cruicial, mandatory working (and in
> one case the only) parameter being NULL, and I would put an ASSERT
> (Info) there to catch bad callers and fix them.
>
> WBR,
> Aleksey.
>
> On Nov 18, 2008, at 8:36 AM, jimtabor(a)svn.reactos.org wrote:
>
>> Author: jimtabor
>> Date: Mon Nov 17 23:36:19 2008
>> New Revision: 37436
>>
>> UINT
>> FASTCALL
>> DIB_BitmapMaxBitsSize( PBITMAPINFO Info, UINT ScanLines )
>> {
>> UINT MaxBits = 0;
>> +
>> + if (!Info) return 0;
>>
>>
>> +UINT
>> +FASTCALL
>> +DIB_BitmapBitsSize( PBITMAPINFO Info )
>> +{
>> + UINT Ret;
>> +
>> + if (!Info) return 0;
>
gedmurphy wrote:
> Let's say you implement a function in our win32k, based on Wine code. How
> exactly would you realistically discover which Wine dev wrote that
> function, and if the function was merely _based_ on wine code, which parts
> of the function would you attribute credit to, and how would you do it?
I think if the dev is not known, then all authors should be credited. I.e.:
"Parts of this file are Copyright (C) ... ". Or: to gather the original Wine
copiright notices into a separate file and put a pointer to it in any file
which is based on Wine.
Dmitry,
On Tue, Nov 18, 2008 at 2:22 AM, Dmitry Timoshkov
<dmitry(a)codeweavers.com> wrote:
> http://www.reactos.org/archives/public/ros-diffs/2008-November/027021.html
>
> Please stop copying Wine code without any copyright and source
> reference into reactos. This became very bad practice from your
> side during last years.
I have no power with the ReactOS project other than to ask and try to
get policy changed in a democratic manner. I've made the case for the
ReactOS to do a better job at proper attribution in code that is
imported based on feedback from you in the past. In fact, just
yesterday I replied to ros-dev proposing some guidelines for how to
handle code imported from Wine. There is nothing more I can do.
I have CC'd Alexandre and Jeremy for there thoughts on the subject. I
welcome feedback from the Software Freedom Law Center or the FSF with
reguards to this issue because on one hand I understand the
attribution is important but on the other hand ReactOS is persona
non-grata with Wine. Given Wine's reluctance to accept any
contributions from ReactOS developers, totally based on guilt by
assocation I think its in your best interested not to be credited. The
Software is still being released under the terms you granted so I
don't see a major violation.
>From the LGPL preamble:
"...Also, if the library is modified by someone else and passed on,
the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others."
Clearly the ReactOS developer is doing you a favor by not hurting your
reputation if ReactOS is as Toxic as Wine makes it out to be.
Thanks
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
So we've been invited to SCALE and I'm wondering whether any of the devs can
actually make it. Arty is a logical choice because he's so close and we
might be able to pull in some community members who are close by if we can
only get one dev there. We'd get a booth on the show floor which includes
table, chairs, power, ethernet drop, and 3-5 passes to the show. Are we
going to be able to make it this year at all?
May I ask why those if (!Info) checks are required? To me it makes no
sense to call those APIs with the cruicial, mandatory working (and in
one case the only) parameter being NULL, and I would put an ASSERT
(Info) there to catch bad callers and fix them.
WBR,
Aleksey.
On Nov 18, 2008, at 8:36 AM, jimtabor(a)svn.reactos.org wrote:
> Author: jimtabor
> Date: Mon Nov 17 23:36:19 2008
> New Revision: 37436
>
> UINT
> FASTCALL
> DIB_BitmapMaxBitsSize( PBITMAPINFO Info, UINT ScanLines )
> {
> UINT MaxBits = 0;
> +
> + if (!Info) return 0;
>
>
> +UINT
> +FASTCALL
> +DIB_BitmapBitsSize( PBITMAPINFO Info )
> +{
> + UINT Ret;
> +
> + if (!Info) return 0;
This is just getting repetitive:
[WIDL] obj-i386\include\reactos\idl\lsa_c.c
include\reactos\idl\lsa.idl:17: Error: NTSTATUS: redefinition error;
original definition was at ( ť:
21
mingw32-make: *** [obj-i386\include\reactos\idl\lsa_c.c] Error 1
mingw32-make: *** Waiting for unfinished jobs....
[WIDL] obj-i386\include\reactos\idl\eventlogrpc_c.c
include\reactos\idl\eventlogrpc.idl:7: Error: NTSTATUS: redefinition error;
original definition was
at Ş■.:21
mingw32-make: *** [obj-i386\include\reactos\idl\eventlogrpc_c.c] Error 1
With all due respect, Eric, would you be so kind and test your commits on
more OS than your PC/buildbot???
Is it not time to start getting rid of IsBadWritePtr and friends?
I don't see a good reason for these in our own code, especially when we can just use SEH directly.
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of greatlrd(a)svn.reactos.org
Sent: 13 November 2008 19:52
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [greatlrd] 37343: Bugfix : Do not link to LPDDRAWI_DIRECTDRAW_INT->lpLink when we do not have any LPDDRAWI_DIRECTDRAW_INT->lpLcl
Author: greatlrd
Date: Thu Nov 13 13:52:20 2008
New Revision: 37343
URL: http://svn.reactos.org/svn/reactos?rev=37343&view=rev
Log:
Bugfix : Do not link to LPDDRAWI_DIRECTDRAW_INT->lpLink when we do not have any LPDDRAWI_DIRECTDRAW_INT->lpLcl
Modified:
branches/reactx/reactos/dll/directx/ddraw/startup.c
Modified: branches/reactx/reactos/dll/directx/ddraw/startup.c
URL: http://svn.reactos.org/svn/reactos/branches/reactx/reactos/dll/directx/ddra…
==============================================================================
--- branches/reactx/reactos/dll/directx/ddraw/startup.c [iso-8859-1] (original)
+++ branches/reactx/reactos/dll/directx/ddraw/startup.c [iso-8859-1] Thu Nov 13 13:52:20 2008
@@ -33,8 +33,8 @@
This = (LPDDRAWI_DIRECTDRAW_INT)*pIface;
- /* fixme linking too second link when we shall not doing it */
- if (IsBadReadPtr(This,sizeof(LPDIRECTDRAW)))
+ if ( (IsBadWritePtr(This,sizeof(LPDDRAWI_DIRECTDRAW_INT)) != 0) ||
+ (IsBadWritePtr(This->lpLcl,sizeof(LPDDRAWI_DIRECTDRAW_LCL)) != 0) )
{
/* We do not have a DirectDraw interface, we need alloc it*/
LPDDRAWI_DIRECTDRAW_INT memThis;
Since revisions 37313-37314 i observe repetitive problems with WIDL. Every
time WIDL is called by our BE, it throws an exception:
Faulting application widl.exe, version 0.0.0.0, time stamp 0x491c610d,
faulting module widl.exe, version 0.0.0.0, time stamp 0x491c610d, exception
code 0xc0000005, fault offset 0x00005f0a, process id 0x17f8, application
start time 0x01c945b3aefa8530.
> [WIDL] obj-i386\include\reactos\idl\svcctl_s.c
> [WIDL] obj-i386\include\reactos\idl\svcctl_s.h
> mingw32-make: *** Waiting for unfinished jobs....
> mingw32-make: *** [obj-i386\include\reactos\idl\svcctl_s.h] Error
-1073741819 (0xC0000005)
> mingw32-make: *** [obj-i386\include\reactos\idl\svcctl_s.c] Error
-1073741819 (0xC0000005)
Reverting revisions 37313 and 37314 fixes this problem. Apart from me, this
issue been noted by dreimer, encoded and Christoph_vW. Dunno about
Christoph, but me, dreimer and encoded are using Vista/2008. I couldnt
replicate this issue on XP/2003 though.
Hi folks,
during the development of the 1st-stage-GUI-setup I experienced some problems
with physical drive detection with reactos api (because it's fairly
incomplete - it works under windows). To continue the development and to
bring more benefits I want to make following suggestion. Sooner or later we
need a drive/volume/partition management tool, so i will continue with this
basing on the usetup code and replaced later by working reactos api calls.
So we can use this tool to determine the current harddisk(s) layout(s),
create/delete partitions, format with different file systems and
show/install/configure the current boot loader. Later I can use this
functions to handle the drives during installation process in a similiar way.
What do you think about this plan?
Matt
--
Matthias Kupfer Telefon +49 (0) 371 236 46 52
Wilhelm-Firl-Straße 21 Mobil +49 (0) 160 859 43 54
09122 Chemnitz
Hi,
> Todo: Get it at the end of the executable, so we can safely remove it.
I think it can be safely removed from inside of the executable — just
wasting some address space.
On Mon, Nov 10, 2008 at 9:25 AM, <gschneider(a)svn.reactos.org> wrote:
> Author: gschneider
> Date: Mon Nov 10 08:25:24 2008
> New Revision: 37281
>
> URL: http://svn.reactos.org/svn/reactos?rev=37281&view=rev
> Log:
> Implement ConvertSecurityDescriptorToStringSecurityDescriptorW based on Wine code.
Please add the appropriate copyright headers to the source file
stating the original author when implementing code based on third
party sources.
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Hi,
I have recently been working on getting SEH into the x64 port. This
covers several parts. One of them is compiler support.
On x64 SEH is table based rather than code based, that means it needs
tables of unwind data. These can be generated from DWARF unwind info -
which gcc generates - and that's what I'm working on.
The x64 version of rsym shall parse the DWARF unwind data and convert it
into Windows compatible unwind data.
Now there is a problem. While older versions of mingw64 used the
".debug_frame" section, the newer versions use the ".eh_frame" section.
That is good and bad at the same time. What does that mean? What's the
difference?
The .eh_frame section isn't part of the DWARF 2 or 3 specification, it's
a GNU extension / part of the LSB-Core specification. Documentation was
hard to find, but google is your friend and it seems there's only one
major difference to the debug_frame section and that is relative
addressing rather than absolute. This is actually very good and saves
the day for all modules that live in kernel space, because the addresses
are only 32 bits.
There is still a problem left. While the .debug_frame section is by
default put into the output executable as a seperate section, the
.eh_frame section isn't. The default linker script puts it into the
".rdata" section. But there it's kinda lost and I don't want to keep it
anyway.
With ntoskrnl there's no problem as it uses it's own linker script
anyway. I can change it, so the .eh_frame section is put at the end of
the executable. But how do I do this for the other modules? Do i need to
provide a new default linkerscript for all other modules? Can I "fix"
this behavior in RosBE64 (the files in lib/ldscripts seem to be unused)?
Or does anyone know a command line option to change this default behavior?
Regards,
Timo
On Nov 7, 2008, at 11:31 PM, cgutman(a)svn.reactos.org wrote:
> Author: cgutman
> Date: Fri Nov 7 14:31:34 2008
> New Revision: 37248
>
> URL: http://svn.reactos.org/svn/reactos?rev=37248&view=rev
> Log:
> - Check the status of IPSendDatagram
> - Validate the protocol
> - Use the hash value of the NCE address to get the lock
> - Simplify TCPAbortListenForSocket
> - Hardcode the length of the array
>
> + HashValue = *(PULONG)(&NCE->Address.Address);
> + HashValue ^= HashValue >> 16;
> + HashValue ^= HashValue >> 8;
> + HashValue ^= HashValue >> 4;
> + HashValue &= NB_HASHMASK;
It's used at least three times in the source code, I would do an
inline hash-calculating function for that.
On Fri, Nov 7, 2008 at 4:54 AM, Aleksey Bragin <aleksey(a)reactos.org> wrote:
> I highly doubt they work, in fact I'm sure they won't work at all.
> But their only duty is to allow building unmodified rpcrt4 from Wine.
> I still have a hope, somewhere very very deep in my soul, that Wine
> will stop using linux-specific APIs in DLLs.
You can hope and dream.
One of the problems we saw, such as in the case of wininet, using unix
sockets instead of winsock gave something like a 20% speedup in
performance. Another issue was that select on linux (thanks to glibc)
fixes FD_SETSIZE at 1024 so the solution was to move to using poll().
The poll/select thing is not that big of a deal as it can be wrapped
but fixing the winsock performance issues may require someone to
dedicate a lot of time profiling. If you can fix all of the issues so
that performance will be the same with pure win32, then I am sure
Alexandre will accept it.
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Hi,
LOL, Wine code does not work at all.... I tested Area.exe with the
latest head and it dies and the application continues to work with out
drawing the PATH figures.
ReactOS:
(subsystems/win32/win32k/objects/gdiobj.c:544) Object->cExclusiveLock = 1
(subsystems/win32/win32k/objects/path.c:1911) BeginPath 1 0xbc07024b
(subsystems/win32/win32k/objects/path.c:1936) BeginPath 2 h 0xbd07024b
p 0x8d9b4830
(subsystems/win32/win32k/objects/path.c:2022) EndPath 0xbd07024b
(ntoskrnl/mm/rpoolmgr.h:820) Trying to allocate 8192 bytes from paged
pool - nothing suitable found, returning NULL
(subsystems/win32/win32k/objects/path.c:1609) Should never happen
(subsystems/win32/win32k/objects/path.c:1609) Should never happen
(subsystems/win32/win32k/objects/path.c:1609) Should never happen
(subsystems/win32/win32k/objects/path.c:1609) Should never happen
(subsystems/win32/win32k/objects/path.c:1609) Should never happen
(subsystems/win32/win32k/objects/path.c:1612) Got path flag
(ntoskrnl/mm/rpoolmgr.h:820) Trying to allocate 4096 bytes from paged
pool - nothing suitable found, returning NULL
<snip>
(ntoskrnl/mm/rpoolmgr.h:820) Trying to allocate 11264 bytes from paged
pool - nothing suitable found, returning NULL
(subsystems/win32/win32k/objects/gdiobj.c:544) Object->cExclusiveLock = 1
(subsystems/win32/win32k/objects/path.c:1911) BeginPath 1 0xbd07024b
(subsystems/win32/win32k/objects/path.c:1936) BeginPath 2 h 0xbe07024b
p 0x8d9b4830
(subsystems/win32/win32k/objects/path.c:2022) EndPath 0xbe07024b
(ntoskrnl/mm/rpoolmgr.h:820) Trying to allocate 2048 bytes from paged
pool - nothing suitable found, returning NULL
<snip>
(ntoskrnl/mm/rpoolmgr.h:820) Trying to allocate 2400 bytes from paged
pool - nothing suitable found, returning NULL
Entered debugger on last-chance exception (Exception Code: 0xc0000005)
(Page Fault)
Memory at 0x000004B0 could not be written: Page not present.
kdb:> bt
Eip:
<win32k.sys:84c9c (subsystems/win32/win32k/objects/bezier.c:160
(GDI_InternalBezier@20))>
Frames:
<win32k.sys:84dfd (subsystems/win32/win32k/objects/bezier.c:178
(GDI_InternalBezier@20))>
<win32k.sys:84deb (subsystems/win32/win32k/objects/bezier.c:178
(GDI_InternalBezier@20))>
<win32k.sys:84dfd (subsystems/win32/win32k/objects/bezier.c:178
(GDI_InternalBezier@20))>
<win32k.sys:84deb (subsystems/win32/win32k/objects/bezier.c:178
(GDI_InternalBezier@20))>
<win32k.sys:84dfd (subsystems/win32/win32k/objects/bezier.c:178
(GDI_InternalBezier@20))>
<win32k.sys:84deb (subsystems/win32/win32k/objects/bezier.c:178
(GDI_InternalBezier@20))>
<win32k.sys:84deb (subsystems/win32/win32k/objects/bezier.c:178
(GDI_InternalBezier@20))>
<win32k.sys:84dfd (subsystems/win32/win32k/objects/bezier.c:178
(GDI_InternalBezier@20))>
<win32k.sys:85008 (subsystems/win32/win32k/objects/bezier.c:216
(@GDI_Bezier@12))>
<win32k.sys:a1760 (subsystems/win32/win32k/objects/path.c:988
(@PATH_AddFlatBezier@12))>
<win32k.sys:a286a (subsystems/win32/win32k/objects/path.c:1019
(@PATH_FlattenPath@4))>
<win32k.sys:a295e (subsystems/win32/win32k/objects/path.c:1514
(NtGdiWidenPath@4))>
<NTOSKRNL.EXE:a145a (ntoskrnl/ke/i386/trap.s:244 (KiFastCallEntry))>
<ntdll.dll:5f1e>
<Area.exe:35ad>
<04ec8353>
Couldn't access memory at 0x56E58959!
kdb:>
The problem is in IntCreatePolyPolygonRgn, it is based on Xorg
mipolygen.c. The figure is some what complex and this old Xorg code
seems to become over whelmed by it. IntCreatePolyPolygonRgn calles
REGION_InsertionSort hundreds or even thousands of times. Using Qemu
you will sit there all night and that is the reason for using hardware
for this test. The first figure was 3 polygons with a total of 516
points. Question is, why is that so hard to map and sort? I assume the
next three figures have the same or close to the same amount of
points. Since they do look and draw about the same.
The bug report has GDI_InternalBezier faulting out the kernel, well
since there is no more PagedPool available so it returned a NULL
without faulting.
I'm looking into alternative methods that are much simpler than the
Xorg code for mapping and filling regions. My best one is from
Graphapp, it is a modified variation of the same Xorgs poly code. This
means more time I do not have to work out a hypothesise and rewrite
all of the region code.
FYI: Our Xorg code is the same Xorg code that is in wine....... I
assume wine code breaks and bombs out when the memory pool empties.
Which is not avalid excuse not to draw.
Thanks,
James
On Thu, Nov 6, 2008 at 7:05 AM, Aleksey Bragin <aleksey(a)reactos.org> wrote:
> How does this code work in Wine without this change?
>
> WBR,
> Aleksey.
>
How does this code work in Wine without this change?
WBR,
Aleksey.
On Nov 6, 2008, at 2:55 PM, jimtabor(a)svn.reactos.org wrote:
> Author: jimtabor
> Date: Thu Nov 6 05:55:08 2008
> New Revision: 37223
>
> URL: http://svn.reactos.org/svn/reactos?rev=37223&view=rev
> Log:
> - Fix WidenPath. Now Area.exe runs and crashes when using real
> hardware. That is a good thing. We now know our Xorg based region
> code has problems. It allocates all the memory building PolyPolygon
> region data.
Hi guys,
After a lot of requests from people in ReactOS, I have decided to
continue my work on USB support, the new bootloader and eventually
Firewire and audio support. Making use of the freedom within the project
I'll use my own, fully spec'ed and documented working methods, attract
devs to work for me when I deem necessary and rally for donations for a
speedy completion of those tasks.
Since there's no roadmap or central goals I'll also set those for myself
and my team(s). I'll provide regular updates on all activities inside
those projects on an as of yet unknown location (ReactOS wiki?) and use
a central repository for all documentation and specification produced by
these projects.
Maya
Hi all,
Fixing GetDeviceCaps exposed a thread process shared memory issue with
WinLogon and Gimp.... Gimp bug, been around and the crash does not
make sense until you see where the fault was located. Where? In client
thread share memory. So, we need help and soon I will revert the hack
in GetDeviceCaps. Maybe we are not passing everything to User32 that
is needed.
Thanks,
James
Gentlemen,
If you don't mind me intruding, I'd like to propose some things I think
may ease life for us poor ROS devs, existing and new ones :)
First of all, I'd like to suggest 'apprenticeship programming', also
known by other names, but which commonly involves having one seasoned
programmer in charge of a particular (sub-)project and one or more
programmers following his lead. These latter programmers would be less
experienced but could work on relatively advanced stuff due to the lead
of the seasoned programmer. This model is commonly used in companies
already and if adapted for ROS it should make it much easier for
'newbie' devs to get started, pick up experience and become seasoned
devs themselves.
My own experience with picking up the USB subproject reflect this as
well. It's hard to get started without much of a lead, especially when
one's experience with the NT subsystems is limited. This is also where
documentation would have helped, bringing me to my second point:
Whenever I start a new project or implementation I first write a
technical specification detailing the exact layout, APIs and
implementation. I've heard that this is common practice in professional
programming as well as other areas. Benefits include having a good
overview of the project before one starts on it, being able to pick out
obvious oversights before writing a single line of code, having a
central place of reference (code does _not_ work for this), allows one
to quickly pick up on things during maintenance sessions (many months
later...). It'd also enable the apprentice programming system and make
it easy for the central project leader(s) to get an overview of the
progress being made.
Documentation and specifications are often ignored by programmers
because they're not deemed 'time-efficient', preferring to start
programming right away instead. In my experience and those of everyone
in high-level jobs involving anything from programming to hardware
design (like my housemate who is a senior engineer in a Dutch company
which designs chips for the telecom industry), specifications and
documentation are the lifeblood of any project.
I have elected to use both the apprentice method as well as the
documentation approach in my work on the new installer, bootloader and
USB stack for ReactOS, attracting two relatively inexperienced but
highly motivated devs for the installer (RI2, or ROSE) project already.
They have expressed interest in helping me with further projects in ROS
as well, even more low-level things. I think that this is a good example
of the future ROS should be heading towards.
So yeah, that's my rant I guess :)
*ducks and runs for cover*
Maya Posch
You're obliged to keep it up-to-date now :-), so it doesn't become
like VFAT "documentation".
On Oct 31, 2008, at 2:26 PM, janderwald(a)svn.reactos.org wrote:
> Author: janderwald
> Date: Fri Oct 31 06:26:23 2008
> New Revision: 37110
>
> URL: http://svn.reactos.org/svn/reactos?rev=37110&view=rev
> Log:
> - Add Documentation for netshell
>
> Added:
> trunk/reactos/dll/win32/netshell/README (with props)
On Wed, Oct 29, 2008 at 9:19 AM, <hyperion(a)svn.reactos.org> wrote:
> Author: hyperion
> Date: Wed Oct 29 08:19:21 2008
> New Revision: 37054
>
> URL: http://svn.reactos.org/svn/reactos?rev=37054&view=rev
> Log:
> deleted wine/mmsystem.h
> deleted wine/prsht.h
> deleted wine/winbase.h
> deleted wine/winnetwk.h
> deleted wine/winnt.h
> deleted wine/winuser.h
> Our SDK is in good enough shape to compile Wine: drop the #include_next hacks
> Wine compatibility fixes should go either in the SDK headers themselves or in the Wine porting SDK
This is a little late but I wanted to let you know that I love you and
want to bear your children!
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Hello,
On Thu, Oct 30, 2008 at 9:33 AM, <jimtabor(a)svn.reactos.org> wrote:
> URL: http://svn.reactos.org/svn/reactos?rev=37099&view=rev
> Log:
> Implement GetFontUnicodeRanges, port from wine. Tested with wine gdi32 font crosstests.
If your using enough of the original implementation to credit Wine
then to me that means someone else at least partly own copyright to
these functions. Could you please use git blame or git web and see who
the author was of the original implementation from Wine and credit
them appropriately in the header? From time to time when someone says
'foo from wine' I get pinged from wine developers who's code is
appropriated and they ask for proper attribution. If we don't do it
right the first time, then at some point another audit of each commit
from SVN will have to happen and we will have to go back and add those
copyright holders to the files license header.
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Hello,
I would like to create a /media/graphics directory in trunk to store the
template files for graphics we want to use in altered versions or different
resolutions. I start with the replacement for the explorere shutdown icon and
a question mark for message dialogs. Due to problems with drawing this icons
at the moment I store the templates only, later we can create the icons from
the templates and include in the resource files.
I suggest to store all selfmade graphics (in alterable formats, e.g. svg) in
this directory (if there is no other source).
What do you think about the change of the message dialogs icons to the tango
project icons and the question mark icon i provide, instead of the current
icon set?
Matthias
--
Matthias Kupfer Telefon +49 (0) 371 236 46 52
Wilhelm-Firl-Straße 21 Mobil +49 (0) 160 859 43 54
09122 Chemnitz
Hello,
trunk has been frozen until 0.3.7 blockers are fixed.
Bugfix team having commit access for this freeze: Colin, Herve,
Johannes, me.
With the best regards,
Aleksey Bragin.
Hi,
I've tooled up libm from http://www.netlib.org/fdlibm/ and a hacked
floatlib.c in lib/3rdparty. With -msoft-float added in win32k.rbuild,
it works. I built the lib separate on XP mingw build environment and I
compiled and ran a fp test program (tst-ieee754.c) than compared the
results with standard gcc. The results are almost the same. The thing
even boots and draws okay. Floatlib.c is very old and I will soon
start testing with SoftFloat to replace the gcc soft float math.
So,,,,, is it posiable to build our build environment (RosBE) to
support full soft-float? So we can avoid more source in ReactOS.....
Well, except libm.a ~ 93k.
or,,,
Just support the hardware floating point and move on........
Thanks,
James
> If the current tree really builds 100% with GCC 4.3.2 or you (or someone
> else) could provide patches for getting it to work, the update should be
> done as soon as possible (but after 0.3.7 :P)
I use GCC 4.3.2 and new binutils for about a month without difficulties; if
you need any patches then please email me.
Of course, I do not insist on including it in RosBE.
Best wishes,
Dmitry
> Because it would fully break the possibility to build older revs. I dont
> know if this counts as argument.
With such an argument upgrade will never come...
I have to disagree with this binutils revert.
If we aren't prepared to keep our tools up to date, then we'll have to resort to dropping RosBE and updating our tools manually.
Build tools should _always_ be kept up to date.
Ged
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of dreimer(a)svn.reactos.org
Sent: 25 October 2008 22:39
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [dreimer] 36968: ok, Binutils and ccache reverted.
Author: dreimer
Date: Sat Oct 25 16:39:26 2008
New Revision: 36968
URL: http://svn.reactos.org/svn/reactos?rev=36968&view=rev
Log:
ok, Binutils and ccache reverted.
Modified:
trunk/tools/RosBE/RosBE-Windows/Root/ChangeLog.txt
trunk/tools/RosBE/RosBE-Windows/RosBE.nsi
Modified: trunk/tools/RosBE/RosBE-Windows/Root/ChangeLog.txt
URL: http://svn.reactos.org/svn/reactos/trunk/tools/RosBE/RosBE-Windows/Root/Cha…
==============================================================================
--- trunk/tools/RosBE/RosBE-Windows/Root/ChangeLog.txt [iso-8859-1] (original)
+++ trunk/tools/RosBE/RosBE-Windows/Root/ChangeLog.txt [iso-8859-1] Sat Oct 25 16:39:26 2008
@@ -5,15 +5,12 @@
- Updated: NSIS to 2.40 (Daniel Reimer)
- Updated: Subversion to 1.5.3 (Daniel Reimer)
- Updated: GDB to 6.8-3 (Daniel Reimer)
-- Updated: Binutils 2.18.50 Build 20080109. (Daniel Reimer)
- Updated: MingW32 Make 3.81-3 (Daniel Reimer)
- Updated: MingW32 Runtime DLL 3.15.1 (Daniel Reimer)
- Other small Fixes here and there (Daniel Reimer)
- Added: Basic PowerShell Version of RosBE (Daniel Reimer)
- Added: YASM 0.72, which supports 64 bit asm too. (Daniel Reimer)
- Added: Update command (Daniel Reimer)
-- Added: A way to include rosapps and rostests into the build and ssvn script by modifying
- one var. Add this var to options.exe (Maciej Bialas and slight changes by me)
- Added: nostrip function (Christoph von Wittich)
- Added: RosBE Debugging Feature which disables the @echo off. just set
_ROSBE_DEBUG=1 (Daniel Reimer)
Modified: trunk/tools/RosBE/RosBE-Windows/RosBE.nsi
URL: http://svn.reactos.org/svn/reactos/trunk/tools/RosBE/RosBE-Windows/RosBE.ns…
==============================================================================
--- trunk/tools/RosBE/RosBE-Windows/RosBE.nsi [iso-8859-1] (original)
+++ trunk/tools/RosBE/RosBE-Windows/RosBE.nsi [iso-8859-1] Sat Oct 25 16:39:26 2008
@@ -201,6 +201,7 @@
SetOutPath "$INSTDIR\4.1.3\bin"
SetOverwrite try
File /r Components\Tools\ccache.exe
+ File /r Components\Tools\cygwin1.dll
SectionEnd
Section "GDB - The GNU Project Debugger" SEC07
I'd like to bring attention to this change, I think it's a rather
interesting one.
So now, for example, if you have a static library A which uses
something from a few small libraries B, C, D, you don't have to
specify in every module that you link with A, B, C and D - you can
just specify once that library A always goes with B,C,D and then link
only to library A in your modules.
WBR,
Aleksey Bragin.
On Oct 25, 2008, at 6:52 AM, hyperion(a)svn.reactos.org wrote:
> Author: hyperion
> Date: Fri Oct 24 21:52:24 2008
> New Revision: 36929
>
> URL: http://svn.reactos.org/svn/reactos?rev=36929&view=rev
> Log:
> modified tools/rbuild/backend/mingw/modulehandler.cpp
> Allow static libraries to "link" to other static libraries
> Removed some dead code
>
> modified dll/nls/normaliz_redist/normaliz_redist.rbuild
> modified dll/win32/kernel32/kernel32.rbuild
> No need to specify icu4ros explicitely anymore, thanks to the
> rbuild changes
> Make kernel32_base include normalize, rather than linking it as
> an external dependency of kernel32
Hello,
I would like to announce, that the call for papers/lectures for the Chemnitz
linux days (Chemnitz LinuxTage) has been started some days ago and will end
at january 5th 2009. If one of you (or the devs in whole) want to present
reactos in any kind (e.g. demonstration, lecture) please let me know. If
there is no other developer, I would be glad to present the project instead
of you, but i'm interested in more involved developers as well. AFAIK in
special cases it's possible to get additional money for travel if necessary,
but bear in mind - it's a non-commercial event. For the German(-speaking)
developers I recommend the website for the event for more details (sorry,
germyn only): http://chemnitzer.linux-tage.de/2009/info/
Comments are very welcome!
Matthias
P.S. I think such events are well suited for recruiting new developers.
--
Matthias Kupfer fon +49 (0) 371 236 46 52
Wilhelm-Firl-Straße 21 mobile +49 (0) 160 859 43 54
09122 Chemnitz
--
Matthias Kupfer Telefon +49 (0) 371 236 46 52
Wilhelm-Firl-Straße 21 Mobil +49 (0) 160 859 43 54
09122 Chemnitz
I would like to hear if this change is agreed with Herve or not, and
if not, what's his opinion about it.
On Oct 22, 2008, at 5:59 PM, sginsberg(a)svn.reactos.org wrote:
> Author: sginsberg
> Date: Wed Oct 22 08:59:01 2008
> New Revision: 36894
>
> URL: http://svn.reactos.org/svn/reactos?rev=36894&view=rev
> Log:
> - Notify umpnpmgr about logon after the shell has initialized
> - This makes it possible to progress if userinit crashes due to
> heavy debug output (due to timing issues in its communication with
> umpnpmgr), which would leave you stranded with no shell. Not really
> a hack, as it doesn't hide or fix the crash -- just limits it to a
> missing "Pending device installations" prompt in case there are any
> pending. Also, it appears to be done the same way on Windows.
Hi there,
I've been snooping into the internals of Win XP and have setup a win32sys SDT
hook on the NtUserCreateWindowEx function.
I'd written sometime back to the list stating that the x,y,nWidth and nHeight
parameters were showing values I couldn't understand - negative values et al.
Since then I realized that this had to do with the fact that the parameter
positions in the prototype I was using seemed to be in a different order
(discovered a window.c file from this project on koders.com and was using
this prototype). I think this could possibly be because maybe the ros team
has been looking at a version of windows that isn't XP (possible??)..dunno
Anyways the parameter ordering I've deduced seems to be :
NtUserCreateWindowEx(DWORD dwExStyle,PUNICODE_STRING
UnsafeClassName,PUNICODE_STRING UnsafeWindowName,DWORD dwUnknown1,DWORD
dwStyle,LONG x, LONG y,LONG nWidth, LONG nHeight,HWND
hWndParent,HMENU,hMenu,HINSTANCE hInstance,LPVOID lpParam,DWORD
dwShowMode,DWORD dwUnknown2)
This seems to be correct with regards the
dwExStyle,dwStyle,x,y,nWidth,nHeight,hWndParent.hMenu,hInstance,lpParam
arguments.
I'm still not able to verify the rest. My immediate concern though are the
UnsafeClassName and UnsafeWindowName arguments.
I'm trying to print out these values...or test out what these values
hold...but can't seem to get anywhere....don't even know for sure if these
are UNICODE_STRING structure vals or LPCTSTR.
I'd like to be able to retrieve/interpret the ClassName and
WindowName......any help would be appreciated.
Bye for now
"It's like NT does" isn't an advantage... cloning *build methods* of
the Core OS Division at Microsoft doesn't do anything positive (nor
negative) to the quality and reliability of the code. You have to look
at *what* the method involves and analyze that way.
Your other argument applies: building RTL multiple times reduces the
need for the small support library ReactOS uses and gives one
consistent place for RTL code.
Disadvantages:
- Building RTL up to 4 times, increasing build time substantially (rtl
is a pretty big library).
- Quadruple-conditional compilation...meaning people will have to test
their rtl changes by BUILDING FOUR TIMES with different conditionals.
Will people really remember to do this? Will people really write code
knowing exactly what do ifdef and where, and how?
- To do this right, you'll need a host-rtl too. Have fun writing one.
- Right now the commit did only half the work -- now compile time is
doubled, but libsupp is still there, making the situation even worse.
The commiter made the assumption "other people" will pick up the
slack, which probably won't happen, and this will rot forever.
Best regards,
Alex Ionescu
On Wed, Oct 15, 2008 at 2:41 PM, Aleksey Bragin <aleksey(a)reactos.org> wrote:
> I knew about this post-factum, so let's gather opinions.
>
> Advantage: It's like NT does, less hacks, possible removal of libsupp
> stuff in ntoskrnl, freeldr, ntdll, etc (which I actually thought
> would be done in the same commit).
>
> Disadvantage: To be proper, you need a bootloader RTL too, otherwise
> RTL will still contain "necessitating hacks" aka libsupp stuff. This
> is gonna make at least 3x time RTL compilation. (thankfully / sadly
> we don't test it directly).
>
>
> WBR,
> Aleksey.
>
>
>
> On Oct 15, 2008, at 10:02 PM, Alex Ionescu wrote:
>
>> Well, you just removed the one thing ReactOS did different from NT and
>> that I thought was really revolutionary and innovative, because it
>> saves on compile time. It's funny, because I've been trying to sell
>> this as a better approach to building RTL (It's built at least 4 times
>> in the real NT tree, I think -- loader, user-mode tools/testing,
>> kernel, user-mode).
>>
>> Best regards,
>> Alex Ionescu
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
Good old patch seems ok to me.
Kind regards,
Sylvain Petreolle
Support artists, not multinationals - http://Iwouldntsteal.net
Supportez les artistes, pas les multinationales - http://Iwouldntsteal.net
----- Message d'origine ----
> De : Pierre SCHWEITZER <heis_spiter(a)hotmail.com>
> À : ReactOS Development List <ros-dev(a)reactos.org>
> Envoyé le : Vendredi, 17 Octobre 2008, 14h37mn 51s
> Objet : Re: [ros-dev] [ros-diffs] [pschweitzer] 36771: Apply fix at the right place.......
>
>
> Shamefully, yes.
> I didn't find good programme to do it under Linux. Speaking of that, if someone
> using Linux could give me some pieces of advice about GUI svn clients under
> Linux, I would be glad :).
> TIA,
> Pierre
> ----------------------------------------
> > From: aleksey(a)reactos.org
> > Date: Fri, 17 Oct 2008 10:44:46 +0400
> > To: ros-dev(a)reactos.org
> > Subject: Re: [ros-dev] [ros-diffs] [pschweitzer] 36771: Apply fix at the
> right place.......
> >
> > Are you merging manually?
> >
> > On Oct 16, 2008, at 10:21 PM, pschweitzer(a)svn.reactos.org wrote:
> >
> >> Author: pschweitzer
> >> Date: Thu Oct 16 13:21:05 2008
> >> New Revision: 36771
> >>
> >> URL: http://svn.reactos.org/svn/reactos?rev=36771&view=rev
> >> Log:
> >> Apply fix at the right place.......
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> _________________________________________________________________
> Inédit ! Des Emoticônes Déjantées! Installez les dans votre Messenger !
> http://www.ilovemessenger.fr/Emoticones/EmoticonesDejantees.aspx
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
Are you merging manually?
On Oct 16, 2008, at 10:21 PM, pschweitzer(a)svn.reactos.org wrote:
> Author: pschweitzer
> Date: Thu Oct 16 13:21:05 2008
> New Revision: 36771
>
> URL: http://svn.reactos.org/svn/reactos?rev=36771&view=rev
> Log:
> Apply fix at the right place.......
Why do you need to publically state it was broken and who broke it?
Does it make you feel more important and help to boost your ego?
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of sginsberg(a)svn.reactos.org
Sent: 16 October 2008 21:02
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [sginsberg] 36773: - Unbreak GetTextFaceA/W, broken since 28730 by GreatLord
Author: sginsberg
Date: Thu Oct 16 15:02:22 2008
New Revision: 36773
URL: http://svn.reactos.org/svn/reactos?rev=36773&view=rev
Log:
- Unbreak GetTextFaceA/W, broken since 28730 by GreatLord
Modified:
trunk/reactos/dll/win32/gdi32/objects/text.c
Modified: trunk/reactos/dll/win32/gdi32/objects/text.c
URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/gdi32/objects/te…
==============================================================================
--- trunk/reactos/dll/win32/gdi32/objects/text.c [iso-8859-1] (original)
+++ trunk/reactos/dll/win32/gdi32/objects/text.c [iso-8859-1] Thu Oct 16 15:02:22 2008
@@ -358,20 +358,24 @@
* @implemented
*/
INT
-STDCALL
+WINAPI
GetTextFaceW(HDC hDC,
- int nCount,
- LPWSTR lpFaceName)
-{
- INT retValue = 0;
- if ((!lpFaceName) || (nCount))
- {
- retValue = NtGdiGetTextFaceW(hDC,nCount,lpFaceName,0);
+ INT nCount,
+ PWSTR pFaceName)
+{
+ INT retValue;
+
+ if ((pFaceName && nCount) ||
+ !(pFaceName && nCount))
+ {
+ retValue = NtGdiGetTextFaceW(hDC, nCount, pFaceName, 0);
}
else
{
SetLastError(ERROR_INVALID_PARAMETER);
- }
+ retValue = 0;
+ }
+
return retValue;
}
Isnt that condition always true ?
+ if ((pFaceName && nCount) ||
+ !(pFaceName && nCount))
Kind regards,
Sylvain Petreolle
Support artists, not multinationals - http://Iwouldntsteal.net
Supportez les artistes, pas les multinationales - http://Iwouldntsteal.net
Well, we can't actually delete ncpa, it just needs to be rewritten to use the netshell library instead.
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of janderwald(a)svn.reactos.org
Sent: 15 October 2008 18:21
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [janderwald] 36762: - Implement Advanced Status IP Information Dialog - Import language strings from netcfgx - Add icon group (32x32) - ncpa is now a candidate for deletion
- ncpa is now a candidate for deletion
If i may say anything, I dont think its a good idea to force NET 3.5
dependency. It`ll reduce the software usability range as not everyone is
willing to upgrade from NET 2.0
Date: Mon, 13 Oct 2008 11:11:16 +0100
From: "gedmurphy" <gedmurphy(a)gmail.com>
Subject: Re: [ros-dev] [ros-diffs] [gschneider] 36737: RosDbg Part
3/3: - Named pipe implementation based on .net namespace IO.Pipes
with
support of threads - Previous win32 test version would strip random
characters from debug messages and crash on entering kdbg
(related t
To: <ros-dev(a)reactos.org>
Message-ID: <001901c92d1c$083d7770$18b86650$@com>
Content-Type: text/plain; charset="utf-8"
I'd originally refrained from doing it this way, using pinvoke instead to
keep .net 2.0 compatibility.
Using classes such as NamedPipeServerStream forces a .net 3.5 dependency. Is
this ok with everyone?
Ged.
Colin wrote:
>The name "Rtlp..." already says it: This is a private function only
used
>internally by ntdll.
To elaborate: if the name has a "p" in it after the "namespace" name
(here Rtl), it usually means "private".
--
Mike
hi, guys!
How and when should I use this function(lib\rtl\critical.c, line 222) ?
In fact,I can not find such a fuction in the export table of ntdll(XP sp2).
hi..
I tried the latest WDK provided by Micrsoft -
http://download.microsoft.com/download/9/0/f/90f019ac-8243-48d3-91cf-81fc40…
It was attached to Qemu as a CDROM. It did boot showing the D:\ But I
couldnt install it. I tried installing via wine in Lenny.That too didnt
work. Any help.. Can i get an alternative older one that works with ROS?
--
Mahesh M
Happy hacking...
, ,
/ \
((__-^^-,-^^-__))
`-_---' `---_-'
`--|o` 'o|--'
\ ` /
): :(
:o_o:
"-"
Commit
by gedmurphy :: r36658
reactos/base/shell/explorer/shell/ (mainframe.cpp mainframe.h):
Remove
the address and command windows from the bottom of the file browser. They're
buggy and they're not too pretty
Hi everyone,
Even though explorer looks nicer indeed with this change, bear in mind that you can't use the internal web browser anymore (you can't type any web address).
Regards,
Gabriel.
_________________________________________________________________
Stanco della solita finestra? Personalizza la tua Hotmail!
http://www.messenger.it/personalizza.html#sfondi
----- Message d'origine ----
> De : Christoph von Wittich <Christoph(a)apiviewer.de>
> À : ReactOS Development List <ros-dev(a)reactos.org>
> Envoyé le : Lundi, 6 Octobre 2008, 16h35mn 25s
> Objet : Re: [ros-dev] Re : [gedmurphy] 36658: Remove the address and command windows from the bottom of the file browser. They're buggy and they're not too pretty
>
>
> > iexplore doesnt compile now :
> > shdocvw's IEWinMain is still a stub for now (shdocvw synced to 0.9.5 according
> to README.WINE)
> >
> > Kind regards,
> > Sylvain Petreolle
> >
> >
>
> Here is a patch to sync shdocvw - it builds - but Explorer crashes on
> "Web" without any debug output.
>
> http://iso.reactos.org/temp/shdocvw_patch.diff
>
> Regards,
> Christoph von Wittich
With that patched shdocvw and wine msimtf (attached in msimtf.zip), you can run iexplore without problem.
In iexplore_mozillaactivex.zip :
1/winemshtml.reg adds needed registry keys for mshtml in order load gecko.
2/put version in mozilla activex directory (mshtml checks for it).
Last: regsvr32 msimtf.
Screenshots:
Reactos Home
http://img234.imageshack.us/my.php?image=iexploremozillaactivexzg8.png
Maximized(better)
http://img444.imageshack.us/my.php?image=iexploremaximzedbetterwq8.png
Acid3 test :)
http://img397.imageshack.us/my.php?image=iexploreacid3id3.png
Hi All,
I have been contacted/invited to participate and give a talk about ReactOS in an event organized by the university of Seville, spain (very beautiful city!) on 2-6 March 2009. It would be great if some of the other spanish based members are also interested on participate, I have been disconnected from the project lately due to offline life but would be willing to participate in this event and help to spread the word about reactos in academic circles.
More information here (in spanish): http://imaginatica.org/2009/descargas/Dossier.pdf
Regards,
/Marc
----- Message d'origine ----
> De : Steven Edwards <winehacker(a)gmail.com>
> À : ReactOS Development List <ros-dev(a)reactos.org>
> Envoyé le : Lundi, 6 Octobre 2008, 13h55mn 01s
> Objet : Re: [ros-dev] [gedmurphy] 36658: Remove the address and command windows from the bottom of the file browser. They're buggy and they're not too pretty
>
> On Mon, Oct 6, 2008 at 7:23 AM, gedmurphy wrote:
> > I'll put an address bar in, along with a few other changes.
> > Just remind me so I don't forget.
>
> Could you look at whats required or left to get iexplore working? The
> Wine import of all of the dlls is done and it should download the wine
> gecko package if you start it but I believe someone was having
> problems when they tried to install/run it, under Wine there is a
> registry key we set in the wine.inf that stores the gecko download url
> so maybe that is whats needed. Just enable iexplore in
> reactos/base/applications and try to run it under ReactOS. If it works
> we could ship it with the wine gecko binary as part of the release
> process.
>
> --
> Steven Edwards
iexplore doesnt compile now :
shdocvw's IEWinMain is still a stub for now (shdocvw synced to 0.9.5 according to README.WINE)
Kind regards,
Sylvain Petreolle
Using "latest-X.0" looks more correct than specifying exact version
number two times.
WBR,
Aleksey.
On Oct 4, 2008, at 5:00 PM, cfinck(a)svn.reactos.org wrote:
> Author: cfinck
> Date: Sat Oct 4 08:00:33 2008
> New Revision: 36643
>
> URL: http://svn.reactos.org/svn/reactos?rev=36643&view=rev
> Log:
> Update some links properly and update the description of Opera
> (sounds stupid to use the same for Firefox and Opera)
>
> Modified:
> trunk/rosapps/applications/downloader/downloader.xml
>
> Modified: trunk/rosapps/applications/downloader/downloader.xml
> URL: http://svn.reactos.org/svn/reactos/trunk/rosapps/applications/
> downloader/downloader.xml?rev=36643&r1=36642&r2=36643&view=diff
> ======================================================================
> ========
> --- trunk/rosapps/applications/downloader/downloader.xml
> [iso-8859-1] (original)
> +++ trunk/rosapps/applications/downloader/downloader.xml
> [iso-8859-1] Sat Oct 4 08:00:33 2008
> @@ -12,13 +12,13 @@
> <licence>MPL/GPL/LGPL</licence>
> <version>2.0.0.17</version>
> <description>The most popular and one of the best free Web
> Browsers out there.</description>
> - <location>http://releases.mozilla.org/pub/mozilla.org/firefox/
> releases/latest-2.0/win32/en-US/Firefox%20Setup%202.0.0.17.exe</
> location>
> + <location>http://releases.mozilla.org/pub/mozilla.org/firefox/
> releases/2.0.0.17/win32/en-US/Firefox%20Setup%202.0.0.17.exe</
> location>
> </application>
> <application name="Opera">
> <regname>Opera</regname>
> <licence>Freeware</licence>
> <version>9.26</version>
> - <description>The most popular and one of the best free Web
> Browsers out there.</description>
> + <description>The popular Opera Browser with many advanced
> features and including a Mail and BitTorrent client.</description>
> <location>http://mirror.nwps.ws/opera/win/926/en/
> Opera_9.26_Classic_Setup.exe</location>
> </application>
> <application name="Thunderbird 1.5">
> @@ -26,20 +26,20 @@
> <licence>MPL/GPL/LGPL</licence>
> <version>1.5.0.14</version>
> <description>The most popular and one of the best free Mail
> Clients out there.</description>
> - <location>http://releases.mozilla.org/pub/mozilla.org/
> thunderbird/releases/latest-1.5/win32/en-US/Thunderbird%20Setup%
> 201.5.0.14.exe</location>
> + <location>http://releases.mozilla.org/pub/mozilla.org/
> thunderbird/releases/1.5.0.14/win32/en-US/Thunderbird%20Setup%
> 201.5.0.14.exe</location>
> </application>
> <application name="Thunderbird 2.0">
> <regname>Mozilla Thunderbird (2.0.0.16)</regname>
> <licence>MPL/GPL/LGPL</licence>
> <version>2.0.0.16</version>
> <description>The most popular and one of the best free Mail
> Clients out there.</description>
> - <location>http://releases.mozilla.org/pub/mozilla.org/
> thunderbird/releases/latest-2.0/win32/en-US/Thunderbird%20Setup%
> 202.0.0.16.exe</location>
> + <location>http://releases.mozilla.org/pub/mozilla.org/
> thunderbird/releases/2.0.0.17/win32/en-US/Thunderbird%20Setup%
> 202.0.0.17.exe</location>
> </application>
> <application name="SeaMonkey">
> <regname>SeaMonkey (1.1.9)</regname>
> <version>1.1.9</version>
> <description>Mozilla Suite is alive. This is the one and only
> Browser, Mail, Chat, and Composer bundle you will ever need.</
> description>
> - <location>http://releases.mozilla.org/pub/mozilla.org/seamonkey/
> releases/1.1.9/seamonkey-1.1.9.en-US.win32.installer.exe</location>
> + <location>http://releases.mozilla.org/pub/mozilla.org/seamonkey/
> releases/1.1.12/seamonkey-1.1.12.en-US.win32.installer.exe</location>
> </application>
> <application name="Mozilla ActiveX Control">
> <regname>Mozilla ActiveX Control v1.7.12 (ReactOS special)</
> regname>
>
Please show me where the developers of this code agreed to having
their code GPL V3 licensed.
I would like to see a full trail of every developer that wrote this
code, as well as written permission from them for you to slap on this
license.
Thank you.
On 23-Sep-08, at 7:45 AM, fireball(a)svn.reactos.org wrote:
> + * LICENSE: GPL v2 or later - See COPYING in the top level
> directory
Best regards,
Alex Ionescu
Pasting gpl notices in every file of a project,
takes up space. better to put in license.txt in project root
to encompass all source files. but most that don't like a license
will refuse to use it and just copy paste the code anyways, and
not say where they got it. (happens all the time). kinda makes
me wonder why we got licenses for software in the first place,
seems to be silly constructs of obstructionism.
GPLv3 don't allow you to control the software
that runs
on the custom hardware, inability to link to the code with out
upsetting the original author.
ce
From: James Tabor <jimtabor.rosdev(a)gmail.com>
To: ReactOS Development List <ros-dev(a)reactos.org>
Sent: Saturday, October 4, 2008 12:38:23 AM
Subject: Re: Reformat to the kernel coding style.
1st: No to v3!
2nd: No to v3!
3rd: No to v3!
On Fri, Oct 3, 2008 at 11:44 PM, Alex Ionescu <ionucu(a)videotron.ca> wrote:
> You basically assumed that a header from another file (probably copy-
> pasted) applies to the file you modified.
>
> While I'm certainly being pedantic, and I admit it -- this shouldn't
> be a change to brush over.
>
> Someone needs to figure out if the devs agree with v3 or not -- I
Why wrap into #ifdefs? I thought it's supposed to be runtime, not
compile time.
WBR,
Aleksey.
On Oct 1, 2008, at 3:54 PM, hyperion(a)svn.reactos.org wrote:
> Author: hyperion
> Date: Wed Oct 1 06:54:29 2008
> New Revision: 36610
>
> URL: http://svn.reactos.org/svn/reactos?rev=36610&view=rev
> Log:
> modified ke/i386/cpu.c
> Added CMPXCHG8B enabling/detection code for TransMeta, Centaur
> and Rise (source: <URL: http://www.geoffchappell.com/notes/windows/
> kernel/cpu/cx8.htm>). Code dead until each vendor will be
> officially supported
> Alex and others: please review
I was asked on IRC to add support for non-Intel and AMD CPUs to the kernel.
Obviously I can't do that -- but I mentioned that some special "magic
tricks" need to be done to enable support for the instruction on other
CPUs, which is why I made the kernel bugcheck.
Thankfully, someone documented the steps required, so I won't get in
trouble for pointing out this link for you:
http://www.geoffchappell.com/notes/windows/kernel/cpu/cx8.htm.
I can confirm that's what the kernel does. Do that too, and you can
then support Transmeta/Rise/VIA CPUs.
Best regards,
Alex Ionescu
James, if it's undocumented, please don't add it to the SDK headers.
On 29-Sep-08, at 8:27 PM, jimtabor(a)svn.reactos.org wrote:
> WM_POPUPSYSTEMMENU
Best regards,
Alex Ionescu
It's going (if not already) to overflow the baseaddress range given
to it, thus making ntdll.dll relocated, which leads to obvious problems.
WBR,
Aleksey.
On Sep 29, 2008, at 2:39 AM, hyperion(a)svn.reactos.org wrote:
> Author: hyperion
> Date: Sun Sep 28 17:39:45 2008
> New Revision: 36586
>
> URL: http://svn.reactos.org/svn/reactos?rev=36586&view=rev
> Log:
> modified dll/win32/kernel32/kernel32.def
> modified dll/win32/kernel32/kernel32.rbuild
> added dll/win32/kernel32/misc/icustubs.cpp
> Export NormalizeString and IsStringNormalized from kernel32.dll.
> This (finally) makes normaliz.dll (50%) functional.
> Link kernel32.dll to ICU. Finally. Binary size increased by
> about 300 KB on a debug build (this is only the beginning).
> Umpteenth copy of C++ and Win32 stubs required to get ICU to
> link properly added to kernel32.dll.
> This commit dedicated to Timo Kreuzer. <3.
Hi,
I am doing a project on "Implementation of VFS in ReactOS". What I am
doing is extract the VFS layer from Linux Kernel and create a driver to ROS
kernel. I am aware of the Installable FS but I feel that VFS is a better
option. I would like to request for suggestions and help on the same.
--
Mahesh M
Happy hacking...
, ,
/ \
((__-^^-,-^^-__))
`-_---' `---_-'
`--|o` 'o|--'
\ ` /
): :(
:o_o:
"-"
That's probably because FsRtlIsNameInExpression is not really used
that much in the 1st stage, but in the 2nd stage it's used to load
fonts (*.ttf from the media fonts, resulting in quite a few calls to
this FsRtl function).
WBR,
Aleksey.
On Sep 27, 2008, at 12:05 AM, pschweitzer(a)svn.reactos.org wrote:
> Author: pschweitzer
> Date: Fri Sep 26 14:50:39 2008
> New Revision: 36539
>
> URL: http://svn.reactos.org/svn/reactos?rev=36539&view=rev
> Log:
> Get rid off recursive FsRtlIsNameInExpression once again.
> Fix a typo in iterative function that fixes it properly. We now get
> ReactOS up to 2nd stage with that fix. 2nd stage is broken...
Hello everyone,
Aleksey suggested that I discuss this here, on the mailing list.
First and foremost, these are enhancements to do for later, much later (what
I would want for the next release is support for RAID / SCSI controllers).
But I know that a developer doesn't actually keep something in his plans
unless he's figured out a way to do it.
I will paste and add additional comments to each of my suggestions.
1. Compatibility with every version of Windows, from Vista until Windows 3.1/
3.11
That means applications written for 3.1 should work flawlessly on ReactOS,
just like apps written for any other Windows. This is probably not hard, as
at least XP does the same thing.
However, drivers for Windows 3.1 most probably do not work. If the user
actually has hardware that was left unsupported since 3.1, he should be able
to use it.
The same goes for the combination Vista-only driver / old Windows '95 or
Windows 3.1 application.
oiaohm said it's not really possible because VxD drivers are not well
documented. So, maybe in the distant future, maybe when Linux devs will have
reversed VxD's on their own. Just don't forget this.
2. Compatibility with DOS**
This will probably not mean DOS drivers, as probably any hardware with DOS
drivers also has some sort of Windows drivers. It would only mean
application compatibility. However, applications with direct access to
hardware will probably have to remain used from within DOS (e.g. BIOS update
software). The major thing are games here. The ideal way to run DOS games
is:
- anything requested by the game is interpreted and passed on to the ROS API
- Glide commands are interpreted and passed on to OpenGL or Direct3D,
resulting in maybe a better image quality, via the use of features OpenGL
has and Glide doesn't.
- software rendering requested by games should be interpreted and passed on
to OpenGL or Direct3D, again resulting in a better image quality.
Of course, this will probably result in a compatibility layer, like you
suggested.
- redbook audio commands should be passed on to ReactOS, who will read in
analog mode or digital mode, depending on what the ROS global settings are
for that specific optical drive.
My own thing about Descent, quickly: the game tries to access file " 1.midi"
but ReactOS plays "1.mp3". I have all the mp3's and will provide them
whenever needed in order to make this happen. This will transform the old
Descent for DOS in the CD version, that had redbook audio tracks.
Such enhancements were also created for Tomb Raider 1, by Paul that created
Glidos ( www.glidos.net ). Please see
http://www.glidos.net/retext.html?lang=en and
http://www.glidos.net/audio.html?lang=en
Whenever Tomb Raider 1 asked for certain textures / audio data, it was
"hijacked" or "redirected" to the better textures or audio files.
Certainly, this DOS compatibility layer would probably need a Glidos-like
application to control various specific settings from various DOS
applications.
Another DOS related thing would be a command prompt (terminal?) in ReactOS
that has drag'n'drop, copy and paste functionality.
Still oiaohm: for the distant future. Got it, understood it, I just want to
convince you to keep it in your plans. oiaohm even said a compatibility
layer already exists.
3. Processors as a devices, in Device Manager *
*
For example, let's say a PC has a Pentium 4 at 3 GHz, with HyperThreading.
Windows XP reports this processor as two identical ones in Device Manager.
ReactOS should also do that. Apart from Windows, if the user does a
right-click on a processor as a device, in the Device Manager tree, and
chooses the Properties page of the processor device, that page should also
mention the SPEED of the processor. More than that, it would be a blessing
to also see the L1, L2 and L3 cache size, FSB and multiplier, like those
SiSoft Sandra / Everest applications report. Maybe even further, the
instruction sets supported - MMX, 3DNow!, SSE, etc.
oiaohm again: can be done, but not right now. Stability and usability beat
extra information. Got it, too. Bug 2644.
4. Clustering
I discussed this with oiaohm and he said it's doable, as soon as ROS gets
Active Directory Server. Only clustered in terms of processing power, the
user has more machines in a cluster and he still sees ROS the normal way, it
just works faster because there are more processors available. No hard
drives in some sort of JBOD, and 3D data is only handled by the "master"
machine(otherwise you need about 10 GB/sec between machines), the one the
user actually interacts with. This is what he said would be the limitations.
I have other details for this, but since it's very far away, it wouldn't
make sense to bring them up right now.
5. Driver extraction tool
I already got one, DoubleDriver, that backs up the drivers for devices in
the device manager. I was thinking about the hardware that only gets drivers
from Windows Publisher (like my MSI Starkey 2.0). Users would need one.
Again, oiaohm said replicating a freeware tool is not high on the list. I'm
fine with that.
6. A Windows Media Center equivalent
**WMC doesn't do much. Just lists program schedules, can do scheduled
recordings, is able to duplicate streams so that you may record whatever
you're watching. It stops suddenly while doing a "record once" capture, when
it should have waited for the user to say stop (it happened on Vista Home
Premium, on a HP laptop). It has a "touchscreen" kind of interface, that
would probably be great on an actual touchscreen, works ok when using a PC
remote control, but is kind of stupid when using the mouse. It can record
from one channel and let you watch another channel if you have at least two
TV tuners in your computer. Naturally, ROS should do this with "n" TV
tuners.
It doesn't have composite or S-video capturing, like the vast majority of TV
tuner software out there. It only captures in Microsoft's special "Microsoft
recorded TV Show" format, extension .dvr-ms I think (no AVI capture, no mpg
capture). It won't let you specify how the tuner provides sound from the
antenna/cable signal to the sound card (PCI audio, internal cable, external
cable, and if any of the last two, what sound card channel it is). While
watching, it should be easier to find out what channel you're on, and what
the time is, via some sort of OSD (on-screen display) that appears when you
move the mouse or something, just like in WMC. The recording should not be
affected by this (i.e. the OSD shouldn't show up on the recording if you
moved the mouse, again just like in WMC). While watching, it's not possible
(or at least not easy) to jump directly to a specific channel, it may only
be used as a TV (next channel, next channel...). If the user tries to switch
channels while recording, he gets "warning, you're recording, if you switch
channels it's going to stop, you want that?" It should just stop, or at
least let the user specify that he doesn't want to see that message again
somehow. It doesn't let the user specify exactly the framerate, video size,
video standard...just the country of origin. And, as an example,
Romaniaofficially uses the PAL D standard on "air" broadcast, that you
can get with
an antenna. But cable providers use PAL B, which is the German official
standard. So, in WMC a guy with cable from Romania must say he's from
Germany or else he won't hear anything!
All of these should be properly implemented in ReactOS Media Center. Apart
from them, "ROSMC" should have all the deinterlacing options and
deinterlacing-method autodetection routines from Dscaler. That program also
offers a whole lot of other image improvement things, like a good enough TV
station logo killer and image de-noising that actually works. Even better
than Dscaler, REMEMBER the settings the next time the user runs the program.
Maybe also provide the user with basic video editing functionality, meaning
most of the features from VirtualDub (the one I find most important is the
ability to edit a film with "direct stream copy", meaning it just copies the
video and/or audio stream, it doesn't re-encode it. Edit as in cutting parts
of the film. In this scenario, the ability to go frame by frame is also very
useful).
And since it's the Media Center and not the Media Player, this should be the
application that rips audio cd's or audio dvd's.
Most of all, it should be "cluster-aware." Regardless of ROS being cluster
aware or not, this one should be.
oiaohm said this is not your job, but a job for other projects. He pointed
me to MediaPortal. I e-mailed all of them (Virtualdub, Dscaler and
MediaPortal) but I doubt they'll combine the three projects. Still, that's
why John User still buys Windows. Linux is all over the Internet (docs all
over forums, drivers all over sites, applications all over sites as well).
Instead, Linux has "cool" stuff like "mousespedometa" (measures the speed
with which you move the mouse). Some people don't even have Internet to get
what they need (X servers, for instance). To be a Windows alternative, it
should contain a lot of things Windows has.
7. Running on 16-bit systems like 286/386/486 in a "ReactOS Essentials"
(equivalent to a stripped-down XP) mode *
*
It should be the same operating system, but in 16-bit mode only. That's an
ideal scenario and I'm sure it cannot be done no matter how good the
programmers are. So, what can someone do on a 286 ? Listen to mp3's ? No
way. Listen to audio CD's, yes, and hopefully digital playback, too. Watch
TV ? Yes, if the user can find an ISA TV tuner (ATI made such tuners, but
they required a PCI ATI video card, and if you have PCI why not get a better
tuner?). Record TV shows ? Not on that kind of computer. Browse the internet
? That may be possible, with some really outdated, 16-bit browser, like the
Internet Explorer for Windows 3.1. And I don't know how many sites will work
on it. Play games ? Yes, either old DOS or Windows 3.1 ones or the ones that
come with ReactOS, written in 16-bit especially for this mode. Join a hive
as either master or slave ? Hopefully it will be possible, but probably in
the year 2015 at least. Use office applications ? Sure, if the user can find
that last Microsoft Office or maybe Microsoft Works version compatible with
Windows 3.1. Run a web server ? I know a guy who had a server running on a
386 system, on Windows 3.11. So yes, it is possible, only I don't know what
software he used to actually serve the data. Act as a router ? Again,
hopefully. That is, if the entire network is on 10 megabit, because I don't
think there are ISA 100 megabit network cards (ISA bandwith is not enough).
2D graphics ? It was possible in Windows 3.1, why not ? Maybe the first
Photoshop versions actually were 16-bit. 3D graphics ? The first 3D Studio
Max (that is, 3D Studio) was for DOS only. That probably means 16-bit right
from the start, and that should mean yes, you can do it, with the DOS
compatibility layer. Web design ? If you can find a 16-bit application, yes.
A separate ReactOS for 16-bit only, or just all the 16-bit functionality
included in the normal ReactOS ? Things look better when it works out of the
box, but it's a waste of space to include applications written for 16-bit
only. People that really need the 16-bit version will not mind paying extra
attention to actually download this one and not the normal one. Besides
that, ReactOS is free. And the presence of such a version would mean a
selfless devotion to people. An act of charity for real. Allowing people to
use their computers and do as many modern things as possible on them.
An open source Windows 3.11 with better compatibility and adherence to
standards. Compatible with all the 9x and ME. Has been tried in Free Win 95,
oiaohm said "dead and staying that way" about it, but maybe VxD
documentation and whatever else you would need will appear (or be reverse
engineered by someone). Once a bigger effort will be done, the missing info
is probably easier to uncover.
Those are my suggestions. They are not for now, they are not easy to do,
etc. Just don't discard them, please.
Alex
Hi,
First, I'd like to apologize since what I'm asking doesn't directly relate to
ReactOS however I'm hoping someone here might be able to shed some light.
I've built a rudimentary win32k profiler and I've hooked the win32k SDT and
hooked onto the NtUserCreateWindowEx function in the hope of studying values
returned by it. I see some strange (to me) values for the x and y
coordinates - values such as 1547372 etc. I'm not sure how to interpret these
values and convert them into pixel units or traditional coordinate
mechanisms. I first thought there must be something wrong with my code
however I'm not so sure anymore.
Would someone here be able to guide me on how to interpret these values???
Thanks and sorry again
Bye for now
> > 7. Running on 16-bit systems like 286/386/486 in a "ReactOS Essentials"
> > (equivalent to a stripped-down XP) mode *
> > It should be the same operating system, but in 16-bit mode only. That's
> > an ideal scenario and I'm sure it cannot be done no matter how good the
> > programmers are. So, what can someone do on a 286 ? Listen to mp3's ? No
Safe Mode. Just load Video, File and network drivers and allow direct access to int13
so fdisk and format can run so user can diag/fix it.
Curious if ReactOS has a an Emergency Boot Disk
system that it can make ? Perhaps, keep a Freedos 1.44m
disk image and allow suer to rawrite it when needed. Or even a
dual bootable Freedos partition (FAT16) with the appropriate recovery tools on it.
--chris
1-916-410-7677
http://nxdos.sourceforge.net/http://bbx.flnet.org/http://teknopup.angelfire.com/
For consistency, I would think OB, IO, PS and other modules having
such tracing system should be turned off by default then too.
WBR,
Aleksey.
On Sep 23, 2008, at 11:54 PM, sginsberg(a)svn.reactos.org wrote:
> Author: sginsberg
> Date: Tue Sep 23 14:54:13 2008
> New Revision: 36436
>
> URL: http://svn.reactos.org/svn/reactos?rev=36436&view=rev
> Log:
> - Attempt to satisfy Alex
There is a big problem with this change, originally this was added
only for "our own" .spec files, which don't have comments starting
with #.
Wine .spec files have such comments, and thus will be preprocessed
incorrectly.
WBR,
Aleksey.
On Sep 21, 2008, at 6:34 PM, tkreuzer(a)svn.reactos.org wrote:
> Author: tkreuzer
> Date: Sun Sep 21 09:34:48 2008
> New Revision: 36379
>
> URL: http://svn.reactos.org/svn/reactos?rev=36379&view=rev
> Log:
> preprocess all spec files
>
> Modified:
> branches/ros-amd64-bringup/reactos/tools/rbuild/backend/mingw/
> modulehandler.cpp
>
> Modified: branches/ros-amd64-bringup/reactos/tools/rbuild/backend/
> mingw/modulehandler.cpp
> URL: http://svn.reactos.org/svn/reactos/branches/ros-amd64-bringup/
> reactos/tools/rbuild/backend/mingw/modulehandler.cpp?
> rev=36379&r1=36378&r2=36379&view=diff
Hi,
I just joined in the mail list and I want to ask a question.
I have a question about scsiport module. I have seen the code
scsiport.c and tried to find where it create the physical device
object for scsi disk however I didn't find it. I just saw the
function SpiScanAdapter which would send inquiry scsi command to scsi
miniport driver.
So I want to know who create the pdo for scsi disk?
Gang Chen
I think if it's a generic buffer-allocating function, its callers
should not rely on the memory being zeroed. (like they don't rely on
pool and heap allocations, unless called with zero-heap flag).
At least the comments to the function does not say "it returns a
zeroed buffer".
WBR,
Aleksey.
On Sep 20, 2008, at 4:31 AM, cgutman(a)svn.reactos.org wrote:
> Author: cgutman
> Date: Fri Sep 19 19:31:02 2008
> New Revision: 36337
>
> URL: http://svn.reactos.org/svn/reactos?rev=36337&view=rev
> Log:
> - Zero the memory after we allocate it
>
> Modified:
> branches/aicom-network-fixes/drivers/network/tcpip/tcpip/pool.c