Ros-dev November 2005

ros-dev@reactos.org

64 participants
176 discussions

DeviceCreateHardwarePage and control panel applets

by Sebastian Gąsiorek

Hi! I would like to work on DeviceCreateHardwarePage from devmgr.dll and then implement Hardware pages in Mouse and Keyboard Control panel applet. Can I do that or maybe there is somebody who is working on than already? thanks, Sebastian

19 years, 1 month

RE: [ros-bugs] [Bug 957] Build 19052 - Installation fails with 'A llocConsole() failed (Status=0x90000001)'

by Murphy, Ged (Bolton)

> -----Original Message----- > From: ReactOS.Bugzilla(a)reactos.org > [mailto:ReactOS.Bugzilla@reactos.org] > Sent: 08 November 2005 05:10 > To: ros-bugs(a)reactos.com > Subject: [ros-bugs] [Bug 957] Build 19052 - Installation > fails with 'AllocConsole() failed (Status=0x90000001)' > > > http://www.reactos.org/bugzilla/show_bug.cgi?id=957 > > > paniq(a)paniq.org changed: > > What |Removed |Added > -------------------------------------------------------------- > -------------- > Severity|normal |critical > > > > > ------- Additional Comments From paniq(a)paniq.org 2005-11-08 > 06:10 CET ------- > this one is actually critical. i'm a bit reluctant to call it > critical because > it has a workaround, but not everybody possesses a failsafe > ps/2 keyboard > (unless you happen to own an intel usb onboard chip... do you > have any idea how > often these chips crash?) > This isn't critical, nor is it a bug, nor is it a a chip crashing. There is no support for USB yet. This is already documented in bugzilla ************************************************************************ 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

19 years, 1 month

Re: [ros-svn] [OTAnn] Feedback

by TwoTailedFox

I've seen this on the VLC-SVN and Ros-SVN Mailing Lists. What exactly *is* this spam? On 11/7/05, shenanigans <maillist(a)roomity.com> wrote: > I was interested in getting feedback from current mail group users. > > We have mirrored your mail list in a new application that provides a more > aggregated and safe environment which utilizes the power of broadband. > > Roomity.com v 1.5 is a web 2.01 community webapp. Our newest version adds > broadcast video and social networking such as favorite authors and an html > editor. > > It?s free to join and any feedback would be appreciated. > > S. > > > > ---------------------------------------------------------------------------------------------------------------------------------------------- > Broadband interface (RIA) + mail box saftey = > React_OS_SVN_Commits_List.roomity.com > *Your* clubs, no sign up to read, ad supported; try broadband internet. > ~~1131397873209~~ > ---------------------------------------------------------------------------------------------------------------------------------------------- > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-svn > > -- "I had a handle on life, but then it broke"

19 years, 1 month

Can I use 'distcc' to compile ReactOS?

by Andrew "Silver Blade" Greenwood

I just discovered distcc. For those who don't know, distcc is a distributed compiler utility that interfaces with gcc on Linux (and compatible platforms.) It comes as a daemon and a client - the daemon is run on each machine you wish to include in the "compiler farm" (so to speak), and the client is told which servers to use (via an environment variable.) When you run distcc it just acts like gcc/g++, and distributes the file to be compiled to each of the hosts. It doesn't need the headers or libraries on the hosts - the output of the preprocessor is passed to each host. Anyway... As I have a second machine which usually runs Windows solely for when I wish to make music, it's ideal for running a small Linux installation, aimed at running distcc/gcc etc. and not much else. All is well, except I cannot configure ReactOS to make use of distcc :( The standard usage for distcc (according to the authors site) is: make -j8 distcc The only way I even got close to compiling ReactOS using distcc was to hack the main Makefile and replace "gcc" with "distcc", and "g++" with "distcc g++" (to specify the compiler to use on each host.) This works perfectly... for the initial make tasks (building the build system?) but after this distcc is completely ignored. Is there a way to allow distcc to work? Ideally the Makefile should take note of the CC variable, I guess? As I have a laptop and 2 desktop machines at my disposal (plus - as I'm staying at a friends house at present - his experimental 3 GHz server box), I'd like to make use of distcc so I don't have to make so much coffee ;) Any ideas?

19 years, 1 month

reactos: uncompilable

by Damjan Jovanovic

I don't know how you guys develop or release ReactOS, but I have never gotten a single release to compile cleanly. First I tried 0.2.6, and I had to edit GCC inline assembly to get it to compile, and use various hacks to get it to work. Last night I tried 0.2.7, which I had to force to compile with multiple declarations (by editing C++ files in tools/rbuild to disable the -Werror flag), force to link by 'make VERBOSE=full' and then manually copying the command line and adding 'obj-i386/hal/hal/libhal.a', and then after a few more hours, ntoskrnl.exe would not link (several thousand missing symbols). I'm gonna get 0.2.8 now and try again, with the Windows version of mingw (been using Linux so far). Just in case, would someone explain to me how you guys get it to compile? And how do you expect anyone to develop an OS that is practically uncompilable? Damjan __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com

19 years, 1 month

Piles upon piles of regressions

by Alex Ionescu

Hi, I realize maybe some of you are aware of these, but it seems that we just keep adding more and more regressions and there hasn't really been an effort to fix them... We don't have a TC anymore and now the tree is becoming as bad as before, which just proves the point of how badly this project needed a TC. I've just booted ROS for the first time in a month and I'm surprised at the number of new things that have cropped up. The start menu became huge, the registry is not cleanly dereferenced at shutdown (causing it to get damaged and that makes freeldr display the "Codepage error"), dhcp still crashes on first-boot since networking isn't installed, the 16x16 icons look like crap since alphablending was implemented, all sorts of drivers "fail to load' on startup, RPC displays messages about "Buffer overflows", umpnpmgr tries to copy invalid drivers, shutdown still doesn't work on my QEMU,... and this is only what I've noticed after 2 minutes. Anyways, I don't want to nitpick, just to bring these issues up to attention in case noobdy is aware of them. Best regards, Alex Ionescu

19 years, 1 month

install problem

by Hartmut Birr

Hi, since some time, I'm not able to install ReactOS on real hardware. Freeldr fails at the first boot after the second stage setup. The error message is 'Couldn't open CodePage registry key'. I've add some debug messages to freeldr. Freeldr isn't able to open the key '\Registry\Machine\SYSTEM\CurrentControlSet'. If I rename umpnpmgr.exe between usetup and the second stage setup, ReactOS boots without any problems. If I rename umpnpmgr.exe back, ReactOS fails on the second boot with umpnpmgr.exe. - Hartmut

19 years, 1 month

Where to commit?

by Brandon Turner

I have interesting in working on the following programs: C:\WINDOWS\system32\tree.exe C:\WINDOWS\system32\gettype.exe(win2k3) C:\WINDOWS\system32\findstr.exe C:\WINDOWS\system32\w32tm.exe and if I'm feeling extra fiesty maybe C:\WINDOWS\system32\osk.exe Now my question is where i should put these, rospapps or maybe reactos\subsys\system\ ? Brandon

19 years, 1 month

[ros-dev] RE:[blight] 19008: Implement (Int)EngAlphaBlend and 8, 16, 24 and 32 bpp DIB AlphaBlend functions. AlphaBlend()should work now.

by Ge van Geldorp

> From: blight(a)svn.reactos.com > > Implement (Int)EngAlphaBlend and 8, 16, 24 and 32 bpp DIB > AlphaBlend functions. AlphaBlend() should work now. Great work. Not sure if you realized it, but this helps Firefox a lot. Screenshot with these changes applied: http://www.reactos.nl/pics/ff2.png (the "before" screenshot is at http://www.reactos.nl/pics/ff1.png see the difference in the toolbars) Thanks again, Gé.

19 years, 1 month

NPFS problems

by Ge van Geldorp

After changes r18883/r18912 umpnpmgr.exe (and eventlog.exe) don't start anymore. The problem is that they try to connect to the service control manager using a named pipe (advapi32/service/sctrl.c function ScConnectControlPipe). Before opening the pipe, a call is made to WaitNamedPipe() to see if the pipe exists. This call currently fails, resulting in failure of ScConnectControlPipe(), resulting in failure of umpnpmgr.exe, resulting in network drivers not being installed, resulting in no network connectivity. WaitNamedPipe() NtOpenFile()s the pipe and then issues a FSCTL_PIPE_WAIT ioctl. The problem is that this end of the pipe is now connected to the server end (which is already listening) during the call to NtOpenFile() (in function NpfsCreate(), setting the PipeStatus to FILE_PIPE_CONNECTED_STATE. NpfsWaitPipe first checks the PipeStatus and bails out if it's not 0 (passive waiting state). So, in our case NpfsWaitPipe fails, 'cause the pipe is already connected. The patch below just makes NpfsWaitPipe return success in case it's already connected, which solves the umpnpmgr problem. However, I don't think it's the correct solution, after the FSCTL_PIPE_WAIT ioctl returns WaitNamedPipe() will close its end, so the server end sees an unexpected close. I have no clue how to proceed, and to be honest I'm not interested in solving it myself. I'd rather see the author of the original patch take his responsibility and fix the regression he introduced. GvG.

19 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev November 2005