Ros-dev

ros-dev@reactos.org

5790 discussions

[Fwd: [ros-general] BIOS]
by David Hinz 18 Nov '05

18 Nov '05

jh schrieb: > From dev mailing list archive > >> From bblaauw at home.nl Thu Nov 17 16:09:23 2005 >> From: bblaauw at home.nl (Bernd Blaauw) >> Date: Thu Nov 17 16:12:08 2005 >> Subject: [ros-dev] 0.3 release plan - Again >> >> Would "USB working" also mean "boot from USB" ? Not even MS allows this. >> Sadly no PC BIOS supports "boot from FireWire", like Apples do. Guess >> we'd need LinuxBIOS for that, as current motherboard manufacturers don't >> want to pay AMI/Phoenix/Award for including the "boot from firewire" >> >module. >> >> Bernd >> > > Would these be of any interest. > > http://freebios.sourceforge.net/ > > http://www.openbios.info/ > > I am not subscribed to the dev mailing list, so does anyone want to > pass this on. > > Regards, > jh > _______________________________________________ > ros-general mailing list > ros-general(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-general >

1 0

Re: [ros-svn] [sedwards] 19259: created crt public headers directory. Moved excpt.h there
by Thomas Weidenmueller 18 Nov '05

18 Nov '05

sedwards(a)svn.reactos.com wrote: > created crt public headers directory. Moved excpt.h there > > > Added files: > trunk/reactos/w32api/include/crt/ > trunk/reactos/w32api/include/crt/excpt.h > > Updated files: > trunk/reactos/ReactOS.xml > > Deleted files: > trunk/reactos/w32api/include/excpt.h This change or r19260 causes compiling with GCC4 to fail: [CC] apps\utils\ps\ps.c In file included from include/ndk/ntndk.h:52, from apps\utils\ps\ps.c:28: include/ndk/rtltypes.h:544: error: conflicting types for 'PEXCEPTION_HANDLER' w32api/include/crt/excpt.h:56: error: previous declaration of 'PEXCEPTION_HANDLER' was here mingw32-make: *** [obj-i386\apps\utils\ps\ps.o] Error 1 - Thomas

2 1

RE: [ros-dev] Re: [ros-diffs] [gedmurphy] 19312: Improve stopping control of the service
by Murphy, Ged (Bolton) 18 Nov '05

18 Nov '05

> -----Original Message----- > From: Thomas Weidenmueller [mailto:w3seek@reactos.com] > Sent: 18 November 2005 12:03 > To: ReactOS Development List > Subject: Re: [ros-dev] Re: [ros-diffs] [gedmurphy] 19312: > Improve stopping control of the service > > > Murphy, Ged (Bolton) wrote: > > This function is new to me. > Now that you're writing multithreaded code it's about time to learn > about these functions ;) > > > I'm just doing a bit of research on it now to better > understand it, but > > could you just give me a bit of background of the > difference between this, > > and using something like a mutex or CS, and why it's better in this > > scenario? > Of course you can use mutexes or critical sections, but for > this purpose > interlocked operations are much more lightweight because with > mutexes or > critical sections you'd have to protect the read operation as > well. The > Interlocked* functions basically guarantee that a certain > operation on a > variable shared by multiple threads is performed in an atomic > matter. I > probably should mention that reads are always atomic, so reading a > variable with the size smaller or equal as the size of a > general purpose > register does not need to be protected, writes however have > to be protected. > > You should read the following articles: > http://msdn.microsoft.com/library/default.asp?url=/library/en- > us/dllproc/base/interlocked_variable_access.asp > http://blogs.msdn.com/oldnewthing/archive/2004/09/15/229915.aspx Thanks for the info, much appreciated. I've been reading up on Interlocked Variable Access this morning and have now implemented it into the code. Ged. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

1 0

RE: [ros-dev] Re: [ros-diffs] [gedmurphy] 19312: Improve stopping control of the service
by Murphy, Ged (Bolton) 18 Nov '05

18 Nov '05

> -----Original Message----- > From: Thomas Weidenmueller [mailto:w3seek@reactos.com] > Sent: 17 November 2005 23:38 > To: ReactOS Development List > Subject: Re: [ros-dev] Re: [ros-diffs] [gedmurphy] 19312: > Improve stopping control of the service > > > Ged Murphy wrote: > > Could you explain what you mean? > As you want to change the value of the variables which are used in a > multithreaded environment you need to used the Interlocked* > functions to > ensure an atomic change in all environments (UP, MP, ...), and also to > make sure it's portable. > > > Those variables are only modified within the base thread, all other > > threads just check the value and act upon it. > > Why would that not be thread safe? > You're assuming the code will only run on a x86 system. In > fact, as long > as the variables are aligned properly it is an atomic operation. But > don't forget the other architectures and possibly upcoming > technologies > based on x86 that could void this assumption. > > I have to admit that the code wouldn't break, even in circumstances > where the operation wouldn't be atomic, but technically the code still > isn't thread-safe this way. > > - Thomas This function is new to me. I'm just doing a bit of research on it now to better understand it, but could you just give me a bit of background of the difference between this, and using something like a mutex or CS, and why it's better in this scenario? Thanks, Ged. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

2 1

RE: [ros-dev] Microsoft Office files in the trunk
by Murphy, Ged (Bolton) 18 Nov '05

18 Nov '05

Mike Swanson wrote: > In the branch of press-media, there are two documents currently. An MS > Word and MS PowerPoint document. > > I'm calling for SVN committers for _no more_ MS Office documents. They > are a proprietary format, of which not all the features are currently > known. I recommend instead the use of OASIS OpenDocument. Not only > does it save much space, but it also does not contain any secrets in > which need to be reverse engineered to discover. > [...] > > Please, for the good of the project, use the free OpenDocument format. > If not for the reason of being open or free, but simply for the fact > that it ensures that everybody will be able to view such documents (no > need to buy any pricey office suites here!). I disagree with this. I don't know how to use oo.o or variants, and I don't intend on learning something I have no interest in. I'm currently putting together a presentation for the speeches I have coming up on ReactOS. If a rule was put in place where we could only commit OpenDocument files, I would simply not put it into the repository and would instead share it with anyone who wanted it via email. This isn't because I'm being awkward, it's because I have no time or interest to learn a new office suite .... and I certainly don't want to install oo.o on my machine. I suppose it's this attitude which keeps MS Office up as a monopoly, which now make me realise why they don't want to support OpenDocument. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

6 7

Re: [ros-diffs] [gedmurphy] 19312: Improve stopping control of the service
by Thomas Weidenmueller 17 Nov '05

17 Nov '05

gedmurphy(a)svn.reactos.com wrote: > Improve stopping control of the service > > @@ -137,14 +137,14 @@ > > { > case SERVICE_CONTROL_SHUTDOWN: /* fall through */ > case SERVICE_CONTROL_STOP: > > - bShutDownFlag = TRUE; > > + bShutDown = TRUE; > > UpdateStatus(SERVICE_STOP_PENDING, -1); > break; > case SERVICE_CONTROL_PAUSE: > > - bPauseFlag = TRUE; > > + bPause = TRUE; > > break; > case SERVICE_CONTROL_CONTINUE: > > - bPauseFlag = FALSE; > > + bPause = FALSE; You might want to use InterlockedExchange to make it thread-safe. - Thomas

2 2

RE: [ros-svn] [gvg] 19303: Wine-0_9_1 vendor import
by Ge van Geldorp 17 Nov '05

17 Nov '05

> From: gvg(a)svn.reactos.com > > Wine-0_9_1 vendor import "svn update" will probably fail, you'll need to delete lib\dplay + lib\dplayx and do a second "svn update". Sorry about this, there seems to be no way around it. GvG

4 5

Freeldr Question
by Alex Ionescu 17 Nov '05

17 Nov '05

Hi, Freeldr currently contains an ugly (imo) wrapper around the GUI where every drawing operation is supposed to have multiple "modes" (some fancy 3d gizmo whizmo GUI and the normal text-mode interface). I would really like to simply this interface and make the drawing operations much simpler and just draw, instead of going through all the hoops they do now. But before I do, does anyone have any objections? Is anyone working on fancy 3D GUI for Freeldr, or can I go ahead with my changes? Note nothing would change to the user, everything will look and act the exact same way as it does now. Best regards, Alex Ionescu

4 14

CodePage Reg Key Error at Boot
by James Tabor 17 Nov '05

17 Nov '05

Hi, I'm getting "Couldn't open CodePage registry key. With OK". I copied freeldr.sys and the rest and reinstall everything, including config files from hives. Installs and go. 1st install system, 2nd reboot ok run fine, and 3rd reboot and get the above error at freeldr. Revision: 18820 Node Kind: directory Schedule: normal Last Changed Author: cwittich Last Changed Rev: 18820 Thanks, James

3 9

Re: [ros-diffs] [cwittich] 19291: implemented CreateServiceA
by Thomas Weidenmueller 17 Nov '05

17 Nov '05

cwittich(a)svn.reactos.com wrote: > implemented CreateServiceA This implementation theoretically is wrong, at least in windows this is also done using RPC (see the .idl file, there should be methods for ansi and unicode). - Thomas

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev