Hi
it is working now after alot of hours down.
so we are back at freenode.net
I sugest if some thing happen to freenode.net
we meetings in efnet until freenode.net is working again
what do people think of that backup plan
He's on Linux, so RosBE is no use.
If someone could just initialise that pointer to NULL it would fix it for
him.
I would do it, but I don't have access to the tree until I get home from
work.
Cheers,
Ged.
p.s. I've no http access at the mo, hence the reply to ros-dev ;)
-----Original Message-----
From: ReactOS.Bugzilla(a)reactos.org [mailto:ReactOS.Bugzilla@reactos.org]
Sent: 23 June 2006 08:33
To: ros-bugs(a)reactos.org
Subject: [ros-bugs] [Bug 1618] internettime.c broken, lpAddress possibly
uninitialized in "InetTimePageProc"
http://www.reactos.org/bugzilla/show_bug.cgi?id=1618
hpoussin(a)reactos.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Comment #3 from hpoussin(a)reactos.org 2006-06-23 09:33 CET -------
Works for me with official ReactOS build environment (GCC 3.4.2, ld 2.16.91)
See
http://www.reactos.org/wiki/index.php/HOWTO/setup_a_build_environment_for_Wi
ndows#ReactOS_Build_Environment_.28RosBE.29
for more details
--
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Ros-bugs mailing list
Ros-bugs(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-bugs
I know I've mentioned this before, but I'll do it officially now :)
Can we change the text format svn-diff sends its messages In from rich text
to plain text?
Every diff I read, I have to click 'reply' first in order for it to be
readable. (my client changes to plain text when replying)
Diff's in rich text are pretty ugly and difficult to follow.
Cheers,
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
Hi all!
I've installed 0.3RC1 on HD. Besides that it didn't overwrite
the MBR, the install went fine.
* FireFox 1.5.0.4 doesn't install correctly - XUL error window
pops up at startup.
* when dragging and dropping a file in explorer from CD to the
desktop, it immediately shut down the box, just like pulling
the plug. Later drag/drop in explorer didn't work at all.
* when trying to install other progs (clicking on the install
EXE) nothing happens - not even an error dialog
* tried to install the Java Runtime - installation went fine,
but there are no java related files anywhere, except
Program Files\Java\jre1.5.....\COPYRIGHT
Let me know if you want some details and how I can provide them.
I'm primarily a linux geek ;-)
Best regards,
Hannes.
Since our MmNotPresentFault handler and kin need to lock the
associated MADDRESS_SPACE, we often need to lock an address space
when it's already been locked. Until now, this has caused a
recursive acquisition of a kernel mutex.
The current kernel bugchecks for me when running the wget binary
here:
http://www.superheterodyne.net/reactos/mm_edit/wget.exe
So I've added a boolean to MADDRESS_SPACE to specify that it's been
locked and propogated its use (and also disentangled this flag from
the one specifying that pages are locked in various cases).
The patch is here:
http://www.superheterodyne.net/reactos/mm_edit/mm.diff
There's a sore spot in section.c at line 684 where I got a bugcheck,
but it was easy enough to check for a NULL region. This probably
isn't right however.
jimtabor was seeing bugchecks at startup that are at least
apparently solved by this patch, but I'm sure that those more in
tune with the kernel can weigh in on whether we should do something
like this or whether the real problem is deeper or different.
--
Discordant is the murmur at such treading down of lovely things while
god's most lordly gift to man is decency of mind. Call that man only
blest who has in sweet tranquility brought his life to close.
If only I could act as such, my hope is good.
-- Aeschylus' Agamemnon (translated by H. W. Smyth)
sata harddisk support needed
2006/6/20, ros-dev-request(a)reactos.org <ros-dev-request(a)reactos.org>:
>
> Send Ros-dev mailing list submissions to
> ros-dev(a)reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.reactos.org/mailman/listinfo/ros-dev
> or, via email, send a message with subject or body 'help' to
> ros-dev-request(a)reactos.org
>
> You can reach the person managing the list at
> ros-dev-owner(a)reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-dev digest..."
>
>
> Today's Topics:
>
> 1. 0.3.0 RC1 Update (Brandon Turner)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 19 Jun 2006 12:48:35 -0400
> From: Brandon Turner <turnerb7(a)msu.edu>
> Subject: [ros-dev] 0.3.0 RC1 Update
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <4496D563.5090201(a)msu.edu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I have added a debug bootcd build of RC1 to sourceforge. So anyone out
> there looking to get there hands one for troubleshooting 0.3.0 can hop
> on there and grab it.
>
> Brandon
>
>
> ------------------------------
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> End of Ros-dev Digest, Vol 22, Issue 23
> ***************************************
>