Ros-dev

ros-dev@reactos.org

5791 discussions

Need some help
by Richard Campbell 08 Dec '05

08 Dec '05

A few weeks (months?) ago i sent a message to the list stating I had lost my commit password. Shortly after someone sent me that password my windows installation (along with the drive it was on) went up in smoke (literally) before i could write it down. I now have the system up and running, and i was wondering if i could get it one more time. I won't ask for it again I swear! :P Richard

1 0

MySQL Bug in RosCMS
by TwoTailedFox 08 Dec '05

08 Dec '05

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /web/reactos.org/htdocs/roscms/inc/admin_dyncontent.php on line 304 Got this error when attempting to retrieve Dynamic Content listings from the CMS. -- "I had a handle on life, but then it broke"

1 0

Project Status - What everyone is up to
by Steven Edwards 07 Dec '05

07 Dec '05

Hi, I am working to put together the first quarterly project status updates. Could everyone that has commit access or works on the web and translation teams could email me privately about what they are currently working on as well as what they think they may hack on over the next few months? Thanks -- Steven Edwards - ReactOS and Wine developer "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo

1 0

Build is Broken
by James Tabor 06 Dec '05

06 Dec '05

Hi all, Make clean etc.. .. 8^) James darkstar:/home/ros/rosbackup# make [LD] output-i386/lib/ntdll/ntdll.dll ntdll.temp.exp:fake:(.edata+0xdd8): undefined reference to `__allshr' ntdll.temp.exp:fake:(.edata+0xde8): undefined reference to `__aullshr' ntdll.temp.exp:fake:(.edata+0xdf0): undefined reference to `__fltused' collect2: ld returned 1 exit status make: *** [output-i386/lib/ntdll/ntdll.dll] Error 1

3 4

Linux Build is Broken.
by James Tabor 06 Dec '05

06 Dec '05

Hi all! Did a "make clean && svn up" 4 hours ago and it work fine. So? Both of my trees are doing it. Reactos and rosbackup. I keep two trees just for this reason. darkstar:/home/ros/rosbackup# rm -rf out* darkstar:/home/ros/rosbackup# rm -rf obj* darkstar:/home/ros/rosbackup# make clean [MKDIR] obj-i386/tools [MKDIR] obj-i386/tools/rbuild [MKDIR] obj-i386/tools/rbuild/backend [MKDIR] obj-i386/tools/rbuild/backend/mingw [CC] tools/rbuild/backend/mingw/mingw.cpp [CC] tools/rbuild/backend/mingw/modulehandler.cpp [CC] tools/rbuild/backend/mingw/proxymakefile.cpp [MKDIR] obj-i386/tools/rbuild/backend/devcpp [CC] tools/rbuild/backend/devcpp/devcpp.cpp [MKDIR] obj-i386/tools/rbuild/backend/msvc [CC] tools/rbuild/backend/msvc/genguid.cpp [CC] tools/rbuild/backend/msvc/msvc.cpp [CC] tools/rbuild/backend/msvc/msvcmaker.cpp [CC] tools/rbuild/backend/msvc/vcprojmaker.cpp [CC] tools/rbuild/backend/backend.cpp [CC] tools/rbuild/global.cpp [CC] tools/rbuild/automaticdependency.cpp [CC] tools/rbuild/bootstrap.cpp [CC] tools/rbuild/cdfile.cpp [CC] tools/rbuild/compilationunit.cpp [CC] tools/rbuild/compilationunitsupportcode.cpp [CC] tools/rbuild/compilerflag.cpp [CC] tools/rbuild/configuration.cpp [CC] tools/rbuild/define.cpp [CC] tools/rbuild/directory.cpp [CC] tools/rbuild/exception.cpp [CC] tools/rbuild/filesupportcode.cpp [CC] tools/rbuild/include.cpp [CC] tools/rbuild/installfile.cpp [CC] tools/rbuild/linkerflag.cpp [CC] tools/rbuild/linkerscript.cpp [CC] tools/rbuild/module.cpp [CC] tools/rbuild/project.cpp [CC] tools/rbuild/stubbedcomponent.cpp [CC] tools/rbuild/syssetupgenerator.cpp [CC] tools/rbuild/testsupportcode.cpp [CC] tools/rbuild/wineresource.cpp [CC] tools/rbuild/rbuild.cpp [CC] tools/ssprintf.cpp [CC] tools/xml.cpp [MKDIR] obj-i386/lib/inflib_host [CC] lib/inflib/infcore.c [CC] lib/inflib/infget.c [CC] lib/inflib/infput.c [CC] lib/inflib/infhostgen.c [CC] lib/inflib/infhostget.c [CC] lib/inflib/infhostglue.c [CC] lib/inflib/infhostput.c [MKDIR] output-i386/tools [MKDIR] output-i386/tools/rbuild [LD] output-i386/tools/rbuild/rbuild [CC] tools/bin2c.c [LD] output-i386/tools/bin2c [MKDIR] obj-i386/tools/bin2res [CC] tools/bin2res/bin2res.c [CC] tools/bin2res/mkstemps.c tools/bin2res/mkstemps.c:34:21: process.h: No such file or directory make: *** [obj-i386/tools/bin2res/mkstemps.o] Error 1

2 1

Re: [ros-svn] [weiden] 19919: disable the device if the user selects "Do not show this dialog anymore". However, this doesn't work at the moment because disabling devices isn't implemented. Once it works, umpnpmgr shouldn't display the device install
by TwoTailedFox 05 Dec '05

05 Dec '05

For some reason, when I was running 19899 yesterday, the dialog boxes kept showing on every boot On 12/5/05, weiden(a)svn.reactos.com <weiden(a)svn.reactos.com> wrote: > disable the device if the user selects "Do not show this dialog anymore". However, this doesn't work at the moment because disabling devices isn't implemented. Once it works, umpnpmgr shouldn't display the device installation wizard for disabled devices anymore. > > > Updated files: > trunk/reactos/lib/newdev/newdev.c > trunk/reactos/lib/newdev/newdev.h > > _______________________________________________ > 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"

2 1

Re: [ros-dev] My attitude
by Brian 05 Dec '05

05 Dec '05

I guess that would be good, a backer like IBM, but you need to look for companies that would benefit from open source, or else, 9 times out of 10, your gonna get a big, fat 'NO'. ps: you all changed subject *pritty fast*!

2 1

Re: [ros-dev] My attitude
by David Hinz 05 Dec '05

05 Dec '05

Who says, they've got to opensource their drivers? I think it could be a big help, if they would help us with implementing the apis their drivers are úsing, so that their closed-source drivers work fine. Greets, David Hinz Alex Buell schrieb: > On Mon, 5 Dec 2005, Jonathan Andrews wrote: > >>> What I'd really like to see are Hardware Manufacturers getting behind >>> us. Realtek, nVIDIA, ATi, Intel, AMD, VIA, etc, could all be >>> approached, and ask for collaboration on writing GPL Drivers >>> (Although nVIDIA is notoriously skeptical about open-source) >> >> Im sorry, snot came out of my nose laughing when I read this...... If >> you think ANY Manufacturer is going to back an open source windows >> clone when they wont even touch a FreeBSD, let alone a Liux then you >> are not living in the real world. >> >> If you want pure GPL then it is best NOT to contact these people and >> ask, if by some miracle they sent you any data you would probably find >> that you are in breech of NDA if you use it. >> >> Out of your list only VIA will give out data on request, and thats >> only data for devices that don't do multimedia. > > One word: DRM. That's why the likes of NVidia won't give out information > on how their devicess works. >

1 0

RE: [ros-dev] Freeze the trunk and release
by Murphy, Ged (Bolton) 05 Dec '05

05 Dec '05

Murphy, Ged (Bolton) wrote: > > -----Original Message----- > > From: WaxDragon [mailto:waxdragon@gmail.com] > > Sent: 02 December 2005 01:02 > > To: ReactOS Development List > > Subject: Re: [ros-dev] Freeze the trunk and release > > > > > > In my 19792, I have a working dhcp client, and can access the cdrom > > drive, under vmware.. I haven't had a chance to try Firefox. > > > > I'm for a freeze, but against a release at this time. > > > > I think a freeze would lead directly onto a release as all > the critical bugs > should be fixed in the freeze period. > What's happening with this? IIRC, either WD calls for a trunk freeze, or Brandon branches for a release. Neither have happened yet ?? I think we should progress in some way or we'll never see 0.3.0 ************************************************************************ 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

8 12

Language selection in textmode part of setup
by David Hinz 05 Dec '05

05 Dec '05

When I just looked for something to translate, I updated the translation of syssetup (trunk\reactos\lib\syssetup). While I read through the file, I recognized, that I newer saw this before. When I checked the setup, I found out, that until all steps of the setup are done, everything is in english. Can't we extend the first part of the setup, so that you select your language at the beginning of setup (the way nearly every Linux-distributor is doing it...) so that people who don't understand english very good are able to install ReactOS? Wouldn't this be nice for 0.3.0? Greets, David Hinz

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev