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.
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.
Thanks
Jason
--- James Tabor <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net> wrote:
> We don't have this yet? Is there a plan to include this in our
> code tree?
According to Thomas and Dmitry's tests its not correct so we are waiting to
see if someone comes up with a better implementation.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Hi Steven,
Steven Edwards wrote:
> Changelog:
> Christoph von Wittich <Christoph(a)ApiViewer.de>
> Implement GetComboBoxInfo
>
>
>
We don't have this yet? Is there a plan to include this in our
code tree?
Looks great!
James
ReactOS will not build on Windows with the latest version of Nasm (
0.98.39 ), because at least some public releases of that version ( I
just downloaded the official from sourceforge.net ), do not support long
file names, and we have a long file name in PSEH.
We can just shorten that asm's file name, but we could also configure
the build system to reject that version.
I don't feel like dealing with it, so I thought I would just send a
head's up here :)
--- Alex Ionescu <ionucu(a)videotron.ca> wrote:
> This goes beyond debug information. This is reproduceable behaviour that
> probably any driver developper out there knows. Checked builds are
> builds recommended for testing your driver for bugs. If you call that
> function with a Queue Object, you WILL see that assert line-by-line on
> your screen. From that point on, one should stich his eyes out for
> having seen it, and shoot himself for knowing this behaviour?
So fix a ReactOS driver to match this behavior and work under Windows and
then you will have justification for making related changes in the kernel.
> Notwithstanding that they cannot sue the project, and that they would
> not sue you. This was a public comment to a friend... why would they sue
> Steven when Alex said what he said? And yes, I cannot wait to be sued...
> I can see the headlines -- Driver Developer sued for being aware of
> Windows Assertion --. I hope they also go after Mark Russinovich for
> having used the checked build to generate a tree of the Windows Source
> code!!
The last time I looked Mr Russinovich was not try to make a replacement
for Windows but rather provide more information people wanting to use
Windows.
> If you aren't, then why am I always the one being targeted with such
> comments. There are functions in ROS which are almost copies of their
> binary versions. There are structures in ROS which look like clones of
> the Windows ones (undocumented ones). There is functionality that was
> directly reversed engineered so that it would be compatible.
Yes we have reverse engineered quite a bit but the question is what methods
are being used to reverse certain behavior. We cannot help but be compatible
with the structures in Windows and take any means needed to be compatible.
> Yet, nobody says a word; everyone goes after Alex for having a
> conversation with a friend and mentionning a reproducible fact in every
> driver developer's life -- you do not KeWaitXxx on a Queue.
> Probably as much as jumping on a guy who has written some of the highest
> quality and most useful code in the OS for the fact he used public
> information during an argument.
You stated the other day there were regressions that were only found by
developing test cases. You would have a lot more good will from developers
on this project if you committed test cases for some of the patches you develop
and commit them to rosapps/tests or write a dummy driver to show the behavior
rather than than pointing to checked builds.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail
