screens? :P
greatlrd(a)svn.reactos.com wrote:
>GetDeviceData
>fix the choppy mouse in UT and fix some other small bugs.
>I can now use the mouse with out any problem in UT
>
>
>
>
>Updated files:
>trunk/reactos/lib/dinput/mouse.c
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
Hi,
--- Jason Filby <jason.filby(a)gmail.com> wrote:
> Another question is: can we really say limit people from
> redistributing ReactOS? I don't think that our license(s) prohibit
> this.
>
> Perhaps some guidelines for such people are all that is needed.
I think we should allow use of the name in limited situations. As another poster stated having a
"Dropline ReactOS" is not a bad thing provided that we setup standards on what has the right to be
called "ReactOS" and what does not. If anyone making or distributing a custom version of ReactOS
violates the standards we set forth then we have the right to refuse use of the name.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Feel free to reread LGPL 2.1 here :
http://svn.reactos.com/viewcvs/trunk/reactos/LGPL.txt
--- Magnus Olsen <magnus(a)itkonsult-olsen.com> wrote:
> ReactOS are not a LPGL but GPL
> it is big diffrent in the licen type
>
> ----- Original Message -----
> From: "Sylvain Petreolle" <spetreolle(a)yahoo.fr>
> To: "ReactOS Development List" <ros-dev(a)reactos.com>
> Sent: Sunday, March 13, 2005 8:39 PM
> Subject: Re: [ros-dev] Vote: Allow 3rd-party distribution of ROS through
> XDCCBot.
>
>
> > If all legal conditions are fulfilled :
> > - give link to the source
> > - (alex's idea) provide md5sum of the file(s)
> >
> > As some people already said, 3d point cant exist.
> > (ros is a LGPL system, some magazines already distribute it, etc.)
> > > [ ] Yes, allow 3rd-party distribution of the OS through the #ros-xdcc
> > > channel and ROS-XDCC-001 bot. (support and encourage this distribution)
> > >
> > > [X] Yes, allow 3rd-party distribution of the OS, but it must clearly
> > > distance itself from officially supported releases (tolerate but do not
> > > support this distribution)
> > >
> > > [ ] No, only sourceforge and other official ReactOS distribution points
> > > should be used.
> >
> >
> > Kind regards,
> >
> > Usurp (aka Sylvain Petreolle)
> >
> > humans are like computers,
> > yesterday the BIOS was all
> > - today its just a word
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.com
> > http://reactos.com:8080/mailman/listinfo/ros-dev
>
>
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
chorns(a)svn.reactos.com wrote:
>* GNU make don't support depending on a directory, so simulate the dependency using a file
>
How not? It works on my box as well as on arty's. :(
There is a little piece of code I left in reactos/subsys/smss/initss.c
that looks like harmless, but that actually crashes smss.exe and
therefore the whole system. The code is in the function
SmpRegisterSmss/0. I can't find myself the bug. The code is currently
wrapped by a #if 0 ... #endif but it is needed to make the SM self
register (to avoid other processaes claim they are the SM). Any hint is
welcome!
Emanuele
WARNING: This e-mail has been altered by MIMEDefang. Following this
paragraph are indications of the actual changes made. For more
information about your site's MIMEDefang policy, contact
MIMEDefang Administrator <mimedefang(a)deos.tudelft.nl>. For more information about MIMEDefang, see:
http://www.roaringpenguin.com/mimedefang/enduser.php3
An attachment of type message/rfc822, named [ros-svn] [hbirr] 13963: Lock the kernel address space instead the process'one, if the pages are located in kernel space. was removed from this document as it
constituted a security hazard. If you require this document, please contact
the sender and arrange an alternate means of receiving it.
> Let me make it clear that the vote is about wether or not to allow
> a particular type of branch which have some bad consequences. Not
> branches in general. See
> http://reactos.com:8080/archives/public/ros-dev/2005-March/002083.html
> for a description of the common branch types.
I did read it (otherwise I wouldnt vote)
"Bugs that that could have been fixed on trunk are annoying to trunk
developers. The bugfixes that go only to the branch are not in trunk (until
merged there from the branch"
=> trunk developers are free to ask for a merge or use ros-diffs to speed up the merge process.
"* Risk of duplicating work. We'll have more branches to track bugfixes on
so it's harder to know which bugs has been fixed and which hasn't."
you can use ros-svn to track it. And you can fix bugs in bugzilla too.
"Fixed in branch my_branch, feel free to merge."
>
> Do you have commit access?
>
> Casper
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
If all legal conditions are fulfilled :
- give link to the source
- (alex's idea) provide md5sum of the file(s)
As some people already said, 3d point cant exist.
(ros is a LGPL system, some magazines already distribute it, etc.)
> [ ] Yes, allow 3rd-party distribution of the OS through the #ros-xdcc
> channel and ROS-XDCC-001 bot. (support and encourage this distribution)
>
> [X] Yes, allow 3rd-party distribution of the OS, but it must clearly
> distance itself from officially supported releases (tolerate but do not
> support this distribution)
>
> [ ] No, only sourceforge and other official ReactOS distribution points
> should be used.
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
Hi!
hbirr(a)svn.reactos.com wrote:
> Added a keep-alive reference to each key object.
> Lock the registry while accessing sub keys of a key object.
> Implemented a worker thread which removes all unused key objects.
> Fixed a bug which shows keys twice if a key is already opened.
>
>
>
> Updated files:
> trunk/reactos/ntoskrnl/cm/cm.h
> trunk/reactos/ntoskrnl/cm/ntfunc.c
> trunk/reactos/ntoskrnl/cm/registry.c
> trunk/reactos/ntoskrnl/cm/regobj.c
>
ntoskrnl: [CC] cm/regobj.c
cm/regobj.c: In function `CmiObjectParse':
cm/regobj.c:244: error: parse error before '<<' token
cm/regobj.c:763: error: parse error at end of input
cm/regobj.c:23: warning: `CmiGetLinkTarget' declared `static' but never defined
make[1]: *** [cm/regobj.o] Error 1
make: *** [ntoskrnl] Error 2
8^),
James
--- Casper Hornstrup <ch(a)csh-consult.dk> wrote:
> I'd like to close this discussion with a vote.
>
> Should we allow branches (other than trunk) with mixed new development and bugfixes
> unrelated to the new development that is on the branch (miscelanea branches) ?
>
> [X] Yes, do allow miscelanea branches
>
> [ ] No, don't allow miscelanea branches
>
> Casper
>
Have an svn branch gives a nice way to revert/update
and permits others to work with a different POV on the project.
Even if only some are using it, it can help ros a lot.
(look at the xmlbuildsystem branch that speeds up the compilation a lot)
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
I don't think we've ever formalised our voting procedures.
All I seem to remember about this is that committers can vote.
I've drafted an initial version here:
http://reactos.com/wiki/index.php/Voting
Please comment on that.
Casper
--- Alex Ionescu <ionucu(a)videotron.ca> wrote:
> [ ] Yes, allow 3rd-party distribution of the OS through the #ros-xdcc
> channel and ROS-XDCC-001 bot. (support and encourage this distribution)
>
> [X] Yes, allow 3rd-party distribution of the OS, but it must clearly
> distance itself from officially supported releases (tolerate but do not
> support this distribution)
Yes but only if they are using a binary published by reactos.org or a core ReactOS developer such
as Thomas's nightly builds. If they are not doing so then my vote is no. At the first offence we
should warn them and then at the 2nd offence we should deny the use of the ReactOS name
> [ ] No, only sourceforge and other official ReactOS distribution points
> should be used.
We cannot stop distrabution of the OS. Only the use of the name.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Hi Royce,
royce(a)svn.reactos.com wrote:
> -Wall -Werror and fix warnings
>
>
> Updated files:
> trunk/reactos/tools/widl/Makefile
> trunk/reactos/tools/widl/hash.c
> trunk/reactos/tools/widl/write_msft.c
>
> _______________________________________________
> Ros-svn mailing list
> Ros-svn(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
More crazy Linux port problems, in /reactos/tools/widl,
write_msft.c: In function `ctl2_write_chunk':
write_msft.c:2189: warning: implicit declaration of function `write'
write_msft.c:2190: warning: implicit declaration of function `close'
write_msft.c: In function `save_all_changes':
write_msft.c:2284: warning: implicit declaration of function `creat'
make: *** [write_msft.o] Error 1
It works when removing -Werror -Wall from the Makefile. BTW io.h
is in the /usr/mingw32/include directory.
Thanks,
James
hbirr(a)svn.reactos.com wrote:
>Use only one access to the spinlock in the assertion, because the value may change between two access' on smp machines.
>
>
You implementation is better, no doubt, but it wouldn't have mattered to
read it twice or more. I mean, it's re-read again down in the
InterlockedExchange call, there's a possibility it might have been
changed in the meantime as well. But it really wouldn't matter ;)
Best Regards,
Thomas
Hello,
Retransmission of this message sent to Harmut , to Ros-Dev list
following error in the mail address of Ros list
---------------------------------------------
Harmut ,
I do not know if this commit is related to the Bug #512 ( Colinux fails
to load in MM/MDL ) but more debug messages are displayed now.
I have updated Bugzilla with these debug messages.
Best regards
Gerard
Subject:
[ros-svn] [hbirr] 13963: Lock the kernel address space instead the
process' one, if the pages are located in kernel space.
From:
<hbirr(a)svn.reactos.com>
Date:
Sat, 12 Mar 2005 10:14:38 +0100
To:
<ros-svn(a)reactos.com>
Lock the kernel address space instead the process' one, if the pages are
located in kernel space.
Unlock the address space on error.
Hi,
--- Eric Kohl <eric.kohl(a)t-online.de> wrote:
> I read the wine-devel list archive a few days ago and relized that
> Alexandre rejected the last patch. I want to split the last patch into
> more 'atomic' parts tomorrow. Is that OK?
Sure thats what I was going to do next. I am going through SVN right now and extracting each
atomic commit and manually applying them to my winehq tree. I can send each patch from each atomic
commit but its going to take me quite a while to resolve conflicts.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250
weiden(a)svn.reactos.com wrote:
>Thomas Weidenmueller <w3seek(a)reactos.com>
>- Fix various security structures and constants
>- Add code to capture quality of service structures and ACLs
>- Secure buffer access in NtQueryInformationToken, NtSetInformationToken, NtNotifyChangeDirectoryFile and NtQueryDirectoryFile
>
>
For the sake of review/auditing, it should be important to mention this
is yet-another-alex_devel_branch-merge. Thomas wrote 100% of it, I'm
just mentionning this as a progress report and historical/bookkeeping
reason.
Best regards,
Alex Ionescu
To clarify i mean OS X and perhaps even os 9. I know about darwin but i was wondering if there was an os x clone out there. Reactos is a version of windows as this clone will be an open-source version of os x or os 9.
>
> From: "Klemens Friedl" <klemens_friedl(a)gmx.net>
> Date: 2005/03/12 Sat AM 10:42:17 EST
> To: ReactOS Development List <ros-dev(a)reactos.com>
> Subject: Re: [ros-dev] Mac OS X clone???
>
> > I was wondering if there was a project that would be doing a binary
> > compatible OS X system. What reactos does for windows maybe this project
> can do
> > for OS X. I was just wondering. I know that pearpc emulates a ppc
> processor,
> > but wether or not a full os exists is the question. I know also that some
> > versions of linux exist for ppc.
>
> Do you mean MacOS X?
>
> Darwin has been the open-source OS technology underlying Apple's Mac OS X
> operating system, with all development being managed and hosted by Apple:
> -> http://developer.apple.com/darwin/
> -> http://www.opendarwin.org/
>
>
>
> -- Klemens Friedl
>
> --
> SMS bei wichtigen e-mails und Ihre Gedanken sind frei ...
> Alle Infos zur SMS-Benachrichtigung: http://www.gmx.net/de/go/sms
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
>
Hi Eric,
How much more work is going to be needed in WIDL? There are quite a lot of changes and I have
fallen behind on merging to Winehq.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail
> >
> > [ ] Yes, do allow miscelanea branches
> >
> > [ ] No, don't allow miscelanea branches
> >
> > [X] Clearly define feature vs mscelanea branches.
I don't mind Alex having a remote branch to be able to maintain
a public backup of his work. In fact I think all of the ReactOS
developers should have public branches but I think that anytime
a feature is implemented in a remote branch and another developer
is blocked by said feature then the remote branch has to be merged
with the trunk. For people like me that contribute little or no code
other than minor bugfixes this may be overkill.
This whole problem is that much of the development switched to his branch
when it should have been merged to the trunk. Alex has admitted this and I
think we have reached a middle ground.
Thanks
Steven
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
navaraf(a)svn.reactos.com wrote:
>Alex Ionescu <ionucu(a)videotron.ca>
>Various bugcheck code improvements:
>- Fix bugcheck code and make debugging easier for unhandled exceptions/spinlocks.
>- Fix a race condition with TAB+B,
>- Fix irql to be high_level.
>- Fix calling unsafe function by caching bugcode data.
>- Fix support for smp by using IPI.
>- Fix not-breakpointing when no debugger is there.
>- Implement KeBugCheck callbacks with reason.
>- Fix callbacks not being called.
>- Fix proper breakpoint during bugcheck.
>Filip Navara <xnavara(a)volny.cz>
>- Move the bugcheck initialization code into Ke (was in Ex on Alex's branch).
>
This doesn't look correctly:
>+ ASSERT(*SpinLock == 0 || 1);
>
>
Can you fix it, Alex?
- Filip
It seems there are more bugs in ld or anywhere. Some relocation entries
points to an address, which must not relocated. This entries starts
always in the upper range of the text section. Ntoskrnl does also
contain relocation entries for the bss section.
- Hartmut
navaraf(a)svn.reactos.com schrieb:
>Don't use intermediate objects linked with "ld -r". There's a bug in binutils that causes the data section relocations to be stripped.
>
>
>Updated files:
>trunk/reactos/ntoskrnl/Makefile
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
>
What you're saying is true however let me bring forth few points:
1. MUI only works one some Windows versions - true. However it runs
basically on all Windows versions available today (Windows 98/Me is not
your target) and Windows XP Home Edition as we all know is binary
compatible with Windows XP so the limitation is only in version check.
2. You cannot get it free - true. But is this important? You cannog get
Windows for free as well and still you're trying to clone it (rather
succesfully).
3. Are you sure the API is not available? I believe it would be fairly easy
to reasearch it even if it wasn't.
4. "So I think reactos must support least 2 langues at fly." Why limit
yourself to 2 only? Why not 3 or 4?
5. "But why not deside which langues it will support when it compile." In
my opinion this is answered very easily:
a. Because you do not want to create ReactOS for power-users who are keen
to compile stuff. If you need to compile it you'll scare newbies who just
want the simplicity of their old Windows for free.
b. Because it contradicts your initial requirement: "If you look at Amiga
OS (Workbench 2.0 or higher) you can change the hole os langues when it was
running."
All in all: I think the M$ approach is really good one: scalable and easy
to use. If you don't want to clone the API for whatever reason, clone the
principle...
Best regards
Radovan Skolnik
"Magnus Olsen" <magnus(a)itkonsult-olsen.com>
Sent by: ros-dev-bounces(a)reactos.com
12.03.2005 14:57
--------------------------------------------------------------------------------
Please respond to ReactOS Development List
--------------------------------------------------------------------------------
To
"ReactOS Development List" <ros-dev(a)reactos.com>
cc
bcc
Subject
Re: [ros-dev] Idea to save time in future - Language Support AndUse
inReactos
The MUI only work on some windows version and you can not geting it free.
or even the api. So I think reactos must support least 2 langues at fly.
But why not deside which langues it will support when it compile.
if you only want example english and french example you got it
or you want all langues. you got it instead. when reactos are beign compile
?
I have done a copy and paste from ms site
http://www.microsoft.com/globaldev/DrIntl/faqs/MUIFaq.mspx#MUIques1
read it about it here.
What versions of Windows are supported by MUI?
MUI was introduced in the Windows 2000 timeframe and is available for:
a.. Windows 2000 Professional
b.. Windows 2000 Server Family - often implemented in a Terminal Services
environment
c.. Windows XP Professional
d.. Windows XP for Tablet PC
e.. Windows Server 2003 Family
f.. Windows XP Embedded
MUI is not supported on consumer versions of Windows such as Windows 9x,
Windows Me, and Windows XP Home Edition.
What are the system requirements of Windows MUI?
MUI is an add-on to the English version of Windows XP Professional and
Windows 2000 family of operating systems, and will not install on localized
versions of Windows XP/2000 or on Windows XP Home Edition. Every additional
language installed will require approximately 115 MB extra disk space for
Windows XP, 45MB for Windows 2000; East Asian language support requires an
additional 250 MB.
How can I acquire Windows MUI?
The Windows XP/2000 MUI is sold only through Volume Licensing programs such
as the Microsoft Open License Program (MOLP / Open), Select, and Enterprise
agreement (or with a new computer as an OEM version at customer request).
It
is not available through retail channels.
----- Original Message -----
From: "Radovan Skolnik" <Radovan_Skolnik(a)tempest.sk>
To: <ros-dev(a)reactos.com>
Sent: Saturday, March 12, 2005 1:40 PM
Subject: RE: [ros-dev] Idea to save time in future - Language Support
AndUse
inReactos
> Hello guuys (and girls if any out there)!
>
> Until now I have been watching the development of ReactOS with great
> interest but as a not-so-great C/C++ programmer (especially for kernel
> stuff) I felt no urge to add my (for you would be worthless) comments :-)
> However the discussion about localizing ReactOS struck me because I think
> there's one thing in/for M$ Windows/Office you probably don't know about
> that already handles this. It is called MUI (Multilingual User Interface
> Pack) - read about it here:
> http://www.microsoft.com/globaldev/DrIntl/faqs/MUIFaq.mspx What it does
is
> that it adds another combo box to Regional Settings in Control Panel and
> each user can choose language to its liking (from those installed of
> course). I can have a look at install media for few languages but as far
as
> I remember it is only bunch of .inf & .dll (probably resources) files. So
I
> believe there is indeed an API to achieve this. So if you're aiming for
> maximum compatibility with original Windows (whatever version) you should
> probably consider this approach. I'm home and sick now with flu but when
I
> get well I'll research the MUI media in more detailed way and let you
> know...
>
> Best regards
>
> Radovan Skolnik
>
> ----- Original Message -----
> From: Magnus Olsen magnus at itkonsult-olsen.com
>
> I want see driffnet langues in the dll and change langues on fly
> instead compile a dll file for each langues. I am mising that feturtuer
in
> windows.
> If you look at Amiga OS (Workbench 2.0 or higher) you can change the hole
> os
> langues
> when it was running. in windows you are stuck with one langues.
>
> So I think it is good idea to compile all langues into all dll file.
> then select in the os wich langues you want use.
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev