Ros-dev

ros-dev@reactos.org

5790 discussions

Re: [ros-dev] USB mouse support
by reactos 30 Jul '05

30 Jul '05

You used the BIOS USB to PS/2 bridge, not a USB driver. Yours sincerely, Jaix Bly ----Ursprungligt meddelande----- From: TwoTailedFox twotailedfox(a)gmail.com Date: Sat, 30 Jul 2005 17:52:59 +0200 To: Andrew Murphy andrewm1986(a)gmail.com Subject: Re: [ros-dev] USB mouse support > Oddly enough, I used 0.2.6 with a USB Mouse on my P4 System. The > cursor did appear, but the mouse sensitivity was way off. I could > roughly get it where I wanted to by moving very, very slowly, but this > wasn't practical, so I switched back to my USB-to-PS/2 way of using > the mouse. > > Good to hear it's near to being useable. > > On 7/30/05, Andrew Murphy <andrewm1986(a)gmail.com> wrote: > > > > > > On 30/07/05, Jonathan Wilson <jonwil(a)tpgi.com.au> wrote: > > > Good to hear. > > > > > > Working support for my Microsoft Optical Intellimouse Explorer USB Optical > > > Mouse is one of the 2 things I want before I will try ROS on real hardware > > > again. (the other is support for my Belikn Wireless Network Card and > > > software and enough networking support so I can talk to the wireless > > router > > > and from there to the internet) > > > > > > > > > _______________________________________________ > > > 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 > > > > > > > -- > "I had a handle on life, but then it broke" > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev

1 0

Re: [ros-diffs] [hbirr] 16901: If a mutex already exist, open it instead of create.
by Joseph Galbraith 30 Jul '05

30 Jul '05

Are you sure that we should be acquiring the mutex in the open case? MSDN says: bInitialOwner [in] Specifies the initial owner of the mutex object. If this value is TRUE and the caller created the mutex, the calling thread obtains ownership of the mutex object. Otherwise, the calling thread does not obtain ownership of the mutex.... Thanks, Joseph hbirr(a)svn.reactos.com wrote: > If a mutex already exist, open it instead of create. > Modified: trunk/reactos/lib/kernel32/synch/mutex.c > Modified: trunk/reactos/lib/kernel32/synch/mutex.c > --- trunk/reactos/lib/kernel32/synch/mutex.c 2005-07-30 19:00:33 UTC (rev 16900) > +++ trunk/reactos/lib/kernel32/synch/mutex.c 2005-07-30 19:03:34 UTC (rev 16901) > @@ -92,10 +92,24 @@ > MUTEX_ALL_ACCESS, > &ObjectAttributes, > (BOOLEAN)bInitialOwner); > + if (Status == STATUS_OBJECT_NAME_COLLISION) > + { > + Status = NtOpenMutant(&MutantHandle, > + MUTEX_ALL_ACCESS, > + &ObjectAttributes); > + if (NT_SUCCESS(Status)) > + { > + if(bInitialOwner) > + { > + WaitForSingleObject(MutantHandle, INFINITE); > + } > + SetLastError(ERROR_ALREADY_EXISTS); > + } > + } > if (!NT_SUCCESS(Status)) > { > - SetLastErrorByStatus(Status); > - return NULL; > + SetLastErrorByStatus(Status); > + return NULL; > } > > return MutantHandle;

1 0

rbuild: module attributes
by Emanuele Aliberti 30 Jul '05

30 Jul '05

Hi all, I think the *module* node needs two more attributes - *subsystem* and *windows* - because at present module type and module subsystem are merged in the *type* attribute and its values are a bit confusing to me; also cui/gui information is hidden into value names. I don't know the rbuild code and I can't therefore say if it is an easy task splitting the logic behind the *type* attribute into tree attributes whitout affecting the whole program logic. A short rationale follows. ___ Valid values for the *type* attribute should be: - library (static) - hal - driver - program - dll Valid values for the *subsystem* attribute should be: - none - native - windows - posix - os2 - vms (default "windows"; "none" required for type "library"; "native" required for types "hal", "driver") Valid values for the *windows* attribute should be: - no - yes (default "no"; "no" required for types "library", "hal", "driver") ___ Examples: *ntdll.dll* <module name="ntdll" type="dll" ...> note that, at present, it is incorrectly described this way <module name="ntdll" type="dll" subsystem="native" ...> *ntoskrnl.exe* <module name="ntoskrnl" type="program" subsystem="native" ...> *atapi.sys* <module name="atapi" type="driver" subsystem="native" ...> -- :Emanuele Aliberti

2 4

Reactos.com problems
by Ge van Geldorp 30 Jul '05

30 Jul '05

There are pretty strong indications that the reactos.com box was cracked. It took part in a DDoS attack. As a consequence, it was isolated from the network. Unfortunately, I'm on vacation right now so I don't have physical access to the box and am unable to fix/reinstall. For the moment, I've moved the mailing lists to a backup box. I am not moving the website, since it seems the attack was carried out via the website (a vulnerability in one of the php script packages we use). I'll put up a dummy page informing visitors. Not sure how far along the release of 0.2.7 is, but I'd like to suggest to put it off for at least another week, until I'm back and can sort things out. Apologies for the inconvenience, Ge van Geldorp.

4 5

[Fwd: Re: [ros-dev] Regression in 15402 - fix in 16860
by Gge 30 Jul '05

30 Jul '05

Svn 16860 has fixed this problem (drivers\net\ndis\ndis\io.c:824)(NdisMRegisterInterrupt) Called. InterruptVector (0x9) InterruptLevel (0x9) SharedInterrupt (1) InterruptMode (0x0) (drivers\net\ndis\ndis\io.c:843)(NdisMRegisterInterrupt) Connecting to interrupt vector (0x49) Affinity (0xFFFFFFFF). (drivers\net\ndis\ndis\io.c:848)(NdisMRegisterInterrupt) Leaving. Status (0x0). I'll test again "ping" command with head Regards Gerard

1 0

Re: [ros-dev] USB mouse support
by reactos 30 Jul '05

30 Jul '05

Hello mr. Wilson and all others who is interested in USB mouse & keyboard. USB mouse and keyboard is being worked on right now, and it will be ready before 0.3.0 and probably after 0.2.7. We are talking weeks not months. Then again, this will be the USB Key and mouse driver, so expect some time for it to mature. Keyboard drivers is probably to be released first because this driver doesn't need HID stack, then the mouse driver will be developed, but there is a need there if some one could find a USB mouse driver C source that doesn't use a HID stack it will be done a lot faster. One interesting detail is that the development will be tested on XBox hardware which will make the XBox-port usable as a development platform. Yours sincerely, Jaix Bly ----Ursprungligt meddelande----- From: Jonathan Wilson jonwil(a)tpgi.com.au Date: Sat, 30 Jul 2005 02:21:02 +0200 To: ReactOS Development List ros-dev(a)reactos.com Subject: [ros-dev] USB mouse support > How far away is support for USB mice? > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev

4 3

RE: [ros-svn] [sedwards] 16887: dos line endings
by Casper Hornstrup 30 Jul '05

30 Jul '05

Put svn:eol-style = native on them, then the svn client will take care of it: svn propset -R svn:eol-style "native" dosfsck Casper > -----Original Message----- > From: ros-svn-bounces(a)reactos.com [mailto:ros-svn-bounces@reactos.com] On Behalf Of > sedwards(a)svn.reactos.com > Sent: 30. juli 2005 01:04 > To: ros-svn(a)reactos.com > Subject: [ros-svn] [sedwards] 16887: dos line endings > > dos line endings > > > Updated files: > trunk/rosapps/sysutils/dosfsck/boot.c > trunk/rosapps/sysutils/dosfsck/boot.h > trunk/rosapps/sysutils/dosfsck/byteorder.h > trunk/rosapps/sysutils/dosfsck/byteswap.h > trunk/rosapps/sysutils/dosfsck/byteswap1.h > trunk/rosapps/sysutils/dosfsck/check.c > trunk/rosapps/sysutils/dosfsck/check.h > trunk/rosapps/sysutils/dosfsck/common.c > trunk/rosapps/sysutils/dosfsck/common.h > trunk/rosapps/sysutils/dosfsck/compiler.h > trunk/rosapps/sysutils/dosfsck/dosfsck.c > trunk/rosapps/sysutils/dosfsck/dosfsck.h > trunk/rosapps/sysutils/dosfsck/fat.c > trunk/rosapps/sysutils/dosfsck/fat.h > trunk/rosapps/sysutils/dosfsck/file.c > trunk/rosapps/sysutils/dosfsck/file.h > trunk/rosapps/sysutils/dosfsck/getopt.c > trunk/rosapps/sysutils/dosfsck/io.c > trunk/rosapps/sysutils/dosfsck/io.h > trunk/rosapps/sysutils/dosfsck/lfn.c > trunk/rosapps/sysutils/dosfsck/lfn.h > trunk/rosapps/sysutils/dosfsck/msdos_fs.h > trunk/rosapps/sysutils/dosfsck/swab.h > trunk/rosapps/sysutils/dosfsck/version.h > trunk/rosapps/sysutils/dosfsck/vfat.h > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-svn

2 1

Wallpaper and Registry Keys
by James Tabor 30 Jul '05

30 Jul '05

Hi all! In Mastering, Win 2K Registry, Sybex books, Pages 282-285. We need some registry fixup to save the wallpaper. HKEY_USERS\.DEFAULT\Control Panel\Desktop, entry Wallpaper, type REG_SZ and value: fully qualified bitmap image filename, entry WallpaperStyle, type REG_SZ and value: 0, entry TileWallpaper, type REG_SZ and value: 0, and on... Same with Mastering, Win XP Registry, Sybex books, Pages 230-231, nothing changed. Is there a problem with implementing some of these? What was the show stopper? Thanks, James

2 1

USB mouse support
by Jonathan Wilson 30 Jul '05

30 Jul '05

How far away is support for USB mice?

1 0

RE: [ros-svn] [gdalsnes] 16793: my 1st
by Murphy, Ged (Bolton) 29 Jul '05

29 Jul '05

gdalsnes(a)svn.reactos.com wrote: > my 1st > > > Added files: > branches/hardons1stbranch/ > > Updated files: > branches/hardons1stbranch/kapi.h branches/hardons1stbranch/ntuser.h > > Deleted files: > branches/hardons1stbranch/debug.h branches/hardons1stbranch/debug1.h Hi Hardon. Out of interest, what's the purpose of this branch? (probably been discussed in IRC, but I missed it) 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

10 17

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