I need a tester for taskmgr.exe a improved version of mine
Don�t got a running version of reactos and need to test this app on other platforms than
windows 2003 server
Just send a mail and i send the source to you..
Thanks
Thomas
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Hi
I am working on adding STI into the Wine project, and
I thought that since ReactOS would probably benefit
from it as well, you people could help me out.
I need the STIUSD.H header file that should part of
the Windows DDK, and seeing as I don't have the DDK
and you guys should, maybe you can send it to me, and
I can add STI support to ReactOS?
STI is a still image API that lets you use scanners,
cameras and the like in Windows.
By the way, ReactOS looks interesting, when I have
some time I'd like to work on it.
Bye
Damjan
__________________________________
Do you Yahoo!?
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250
This is my changes to serial driver:
- Fixed bug: only one file may be open on a port at any given time.
- Implemented IOCTL_SERIAL_GET_STATS and IOCTL_SERIAL_CLEAR_STATS.
Small test program included
The 'Standard' PC serial ports are as follows:
COM1 (address 3F8-3FF) and COM3 (address 3E8-3EF) share IRQ4.
COM2 (address 2F8-2FF) and COM4 (address 2E8-2EF) share IRQ3.
I remember from my DOS days that you can add more serial cards into the
system just as long
as you kept the address's from overlapping, and your software was configured
correctly.
As far as I'm aware the BIOS data area only has place for 4 port addresses:
0000:0400 COM1 address
0000:0402 COM2 address
0000:0404 COM3 address
0000:0406 COM4 address
-----Original Message-----
From: Royce Mitchell III [mailto:royce3@ev1.net]
Sent: Thursday, 17 March 2005 12:04 p.m.
To: ReactOS Development List
Subject: Re: [ros-dev] serial driver bug
Robert Köpferl wrote:
> Be aware that it makes a difference wether you have got a so called
> multi serial card or several plain old serial HW. I may be wrong, but
> isn't 4 the limit. Due to 'reserved' ports for that kind of HW?
>
It's a multi-serial card. The 4 limit for plain serial is due to
reserved/limited irq if I understand correctly.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev
This communication is confidential and may contain privileged material.
If you are not the intended recipient you must not use, disclose, copy or retain it.
If you have received it in error please immediately notify me by return email
and delete the emails.
Thank you.
arty(a)svn.reactos.com wrote:
>consw has not been needed for a long time.
>
>
>
Actually, that was never needed. It was there for a planned extended
feature of our Win32 emulator: the possibility to switch back to text
mode on the active desktop belonging to the winstation attached to the
primary console.
Still getting it: Unhandled UserMode exception, terminating thread.
Jason
On Wed, 16 Mar 2005 19:30:11 +0200, Jason Filby <jason.filby(a)gmail.com> wrote:
> I wanted that record ;)
> Great to know though!
>
> Cheers
> Jason
>
> On Wed, 16 Mar 2005 18:15:50 +0100, Filip Navara <xnavara(a)volny.cz> wrote:
> > Jason Filby wrote:
> >
> > >Hi all
> > >
> > >Loading up the OpenOffice.org 1.1.2 Setup no longer works; the initial
> > >progress bar completes and then nothing happens. I'm sure I've seen
> > >this bug before! Any help welcome.
> > >
> > >
> > Just for the record, today I successfully installed OOo 1.1.1, ROS SVN
> > revision 14087.
> >
> > - Filip
> >
> >
>
Hi!
I switch to an older serial driver, BTW the new one set the baud to 19.2k.
(KERNEL32:mem/global.c:412) Memory Load: 8
CSR: NtOpenProcess() failed for handle duplication
Failed to tell csrss about new process. Expect trouble.
(KERNEL32:mem/global.c:412) Memory Load: 8
Funny debug message,
James
Alex's patches are in, and I saw him call for 0.2.6 on irc, but
there have been a few regressions discovered. Do we need to have a
bughunt / regression test / code freeze? The last couple of releases
(that I have been around for) we have created the branch, then applied
bugfixes against it, then backported to HEAD. Is this the way we
should do this? Should we "freeze" HEAD and then branch?
I found that vncviewer no longer starts for me, and Alex said that
Abiword doesn't work for him. The wallpaper was reported to have
regressed also. I personally will test the wallpaper and all the
other things I care about tonight. Maybe we should have others check
over things too..
Just curious,
WD
--
The cheese stands alone.
