Ros-dev

ros-dev@reactos.org

5790 discussions

RE: [ros-diffs] [arty] 20055: A little library for making it easier toget to PASSIVE_LEVEL. Just contains
by Casper Hornstrup 11 Dec '05

11 Dec '05

We don't have the REVISIONS section anymore and a copyright notice is missing. Casper _____ From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of arty(a)svn.reactos.com Sent: 11. december 2005 09:26 To: ros-diffs(a)reactos.com Subject: [ros-diffs] [arty] 20055: A little library for making it easier toget to PASSIVE_LEVEL. Just contains _____ Added: trunk/reactos/drivers/lib/chew/workqueue.c --- trunk/reactos/drivers/lib/chew/workqueue.c 2005-12-11 08:11:21 UTC (rev 20054) +++ trunk/reactos/drivers/lib/chew/workqueue.c 2005-12-11 08:26:16 UTC (rev 20055) @@ -0,0 +1,101 @@ +/* + * COPYRIGHT: See COPYING in the top level directory + * PROJECT: ReactOS TCP/IP protocol driver + * FILE: tcpip/main.c + * PURPOSE: Common Highlevel Executive Worker + * PROGRAMMERS: Art Yerkes + * REVISIONS: + * CSH 10/12-2005 Created + */

1 0

Boch 2.2.1 keyboard buffer overflow with React OS 0.2.8
by Jerry 11 Dec '05

11 Dec '05

I tried to run both the live ISO and the intstall ISO (reactos 0.2.8) in bochs 2.2.1 and I got a keyboard buffer overflow. I don't know what is wrong. Here is apart of the Bochs core dump: 00117791507e[KBD ] keyboard disabled & send of byte f2 to kbd 00117791507i[KBD ] identify keyboard command received 00118580248e[KBD ] keyboard disabled & send of byte f2 to kbd 00118580248i[KBD ] identify keyboard command received 00119368173e[KBD ] keyboard disabled & send of byte f2 to kbd 00119368173i[KBD ] identify keyboard command received 00120156914e[KBD ] keyboard disabled & send of byte f2 to kbd 00120156914i[KBD ] identify keyboard command received 00120946888e[KBD ] keyboard disabled & send of byte f2 to kbd 00120946888i[KBD ] identify keyboard command received 00121734813e[KBD ] keyboard disabled & send of byte f2 to kbd 00121734813i[KBD ] identify keyboard command received 00121734813i[KBD ] internal keyboard buffer full, ignoring scancode.(ab) 00121734813i[KBD ] internal keyboard buffer full, ignoring scancode.(41) 00122523554e[KBD ] keyboard disabled & send of byte f2 to kbd 00122523554i[KBD ] identify keyboard command received 00122523554i[KBD ] internal keyboard buffer full, ignoring scancode.(fa) 00122523554i[KBD ] internal keyboard buffer full, ignoring scancode.(ab) 00122523554i[KBD ] internal keyboard buffer full, ignoring scancode.(41) 00123313528e[KBD ] keyboard disabled & send of byte f2 to kbd 00123313528i[KBD ] identify keyboard command received 00123313528i[KBD ] internal keyboard buffer full, ignoring scancode.(fa) 00123313528i[KBD ] internal keyboard buffer full, ignoring scancode.(ab) 00123313528i[KBD ] internal keyboard buffer full, ignoring scancode.(41) 00124101453e[KBD ] keyboard disabled & send of byte f2 to kbd 00124101453i[KBD ] identify keyboard command received 00124101453i[KBD ] internal keyboard buffer full, ignoring scancode.(fa) 00124101453i[KBD ] internal keyboard buffer full, ignoring scancode.(ab) 00124101453i[KBD ] internal keyboard buffer full, ignoring scancode.(41) 00124891427e[KBD ] keyboard disabled & send of byte f2 to kbd 00124891427i[KBD ] identify keyboard command received 00124891427i[KBD ] internal keyboard buffer full, ignoring scancode.(fa) 00124891427i[KBD ] internal keyboard buffer full, ignoring scancode.(ab) 00124891427i[KBD ] internal keyboard buffer full, ignoring scancode.(41) 00125680168e[KBD ] keyboard disabled & send of byte f2 to kbd 00125680168i[KBD ] identify keyboard command received 00125680168i[KBD ] internal keyboard buffer full, ignoring scancode.(fa) 00125680168i[KBD ] internal keyboard buffer full, ignoring scancode.(ab) 00125680168i[KBD ] internal keyboard buffer full, ignoring scancode.(41) 00126470143e[KBD ] keyboard disabled & send of byte ed to kbd 00126470143p[KBD ] >>PANIC<< internal keyboard buffer full (imm)

2 2

RE: [gvg] 20024: Work around lack of MSG_PEEK
by Ge van Geldorp 10 Dec '05

10 Dec '05

With r20024 I can get ibrowser to actually download the Mozilla webbrowser control. It usually takes a few tries, often the download hangs halfway through. I have the feeling that it helps if you move the mouse constantly during download, but that could just be my imagination. To install the control, you will need a copy of MSVCP60.DLL, which the author forgot to include in the install image (Wine has the same problem). So first copy MSVCP60.DLL from your Windows installation to \ReactOS\System32, then start ibrowser, download the control and install it. After that ibrowser (and the "Web" button in ROSExplorer) becomes functional. GvG

4 5

Industry support
by David Hinz 10 Dec '05

10 Dec '05

When I first throw in the idea, that we could try to get some big companys supporting us, I was amazed by the huge response. A lot of people seem to be very interested in this, but after some days, I noticed that there are nearly no devs who replied to my mail, or the numerous replies on it. So what I'm asking for is how the devs and especially our PC Steven Edwards think about asking some companys like IBM, Intel, AMD, nVIDIA, ATI, Dell,... to support our project. There are a lot of ways, they could support us, either by money, or by developers, or by knowledge/documentations. Every of the mentioned companys would be able to support us, but I think the only person who has the right to ask any of them is our PC, or maybe somebody he authorized to do so. I'm waiting for your replies. Greets, David Hinz BTW, the mail I mentioned above is http://www.reactos.org/archives/public/ros-dev/2005-December/006645.html

5 7

Re: [ros-svn] [gvg] 20026: reactos.org is the preferred name these days
by TwoTailedFox 10 Dec '05

10 Dec '05

Does this fix the reference to 'reactos.com' with the 'ver' command, in the Command Interpreter? On 12/9/05, gvg(a)svn.reactos.com <gvg(a)svn.reactos.com> wrote: > reactos.org is the preferred name these days > > > > Updated files: > trunk/reactos/subsys/system/explorer/shell/mainframe.cpp > > _______________________________________________ > 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"

3 2

Compilation error
by David Hinz 09 Dec '05

09 Dec '05

When I try to compile ReactOS on Windows, I get the following error: ./subsys/win32k/objects/path.c: In function `PATH_PathToRegion': ./subsys/win32k/objects/path.c:1024: warning: 'hrgn' might be used uninitialized in this function mingw32-make[1]: *** [obj-i386\subsys\win32k\objects.o] Error 1 Important: I'm compiling with optimisations for amd64 and dbg and kdbg=0. Revision is 20025 If I'm not the only one with these problems, I hope you get that fixed soon, I don't think this is because if my platform optimizations. Greets, David Hinz

1 0

process token problem
by Hartmut Birr 09 Dec '05

09 Dec '05

Hi, after compiling ros on ros, I see over 45000 memory blocks with the tags TOKd, TOKp, TOKu and TOKp. It seems, something is wrong with the referencing/dereferencing of tokens. I've add some debug code in SeDeassignPrimaryToken (only called by PspDeleteProcess), which prints the ref count of the token object. It is always greater than 1. The process token is never deleted. - Hartmut

1 0

[Vote] Top-level source header
by Casper Hornstrup 09 Dec '05

09 Dec '05

The discussion is located here: http://www.reactos.org/archives/public/ros-dev/2005-October/005671.html I will create a vote with the options below. Proposal A from Ged Murphy: /* * ReactOS <place holder> * Copyright (C) 2005 ReactOS Foundation * * LICENCE: <place holder> * PROJECT: <place holder> * FILE: <place holder> * PURPOSE: <place holder> * PROGRAMMERS: <place holder> * REVISIONS: * <place holder> * */ Proposal B from Alex Ionescu: /* * PROJECT: ReactOS Kernel * LICENSE: GPL - See COPYING in the top level directory * FILE: ntoskrnl/ex/mutant.c * PURPOSE: section of the kernel * PROGRAMMERS: Alex Ionescu (alex at reactos.org) * David Welch (welch at cwcom.net) */ Proposal C from Casper Hornstrup/Gé van Geldorp: /* * PROJECT: ReactOS Kernel * LICENSE: GPL - See COPYING in the top level directory * COPYRIGHT: Copyright 2004-2005 John Doe * Copyright 2005 Jane Doe */

12 19

Feature Request
by Rick Langschultz 09 Dec '05

09 Dec '05

XML is actively becoming part of technology and programming. Every major development company has embraced some form of XML in one product or another. I was wondering if ReactOS would be interested in developing some form of application to handle XML-based applications. These applications would be written in XML and bundled in a ZIP file much like the ODF formats that OpenOffice 2.0 is using. XML applications would be allowed to communicate with some processing application protocols and functions. I think something like this would be a great feature that would quickly allow novice programmers to quickly develop applications for ReactOS and share them on the website. Think of it, no compilation time. That would be great. I will try to write a proof-of-concept application for Windows XP and 2000 for trial and testing. My main question is: If something like this is wanted/needed/or if ReactOS members finds interesting would ReactOS think about supporting it in the first production release. Which is still far off, I would imagine.

7 8

RE: [ros-dev] Top-level source header
by Murphy, Ged (Bolton) 09 Dec '05

09 Dec '05

Ge van Geldorp wrote > So in our case something like > > /* > * COPYRIGHT: Copyright 2005 Alex Ionescu (alex(a)reactos.org) > * Copyright 2005 Filip Navara (navaraf(a)reactos.org) > */ I agree with this. We don't have to do another vote though, do we. Can we just agree to this one over the mailing list please? ************************************************************************ 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

4 3

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