@lassy:
would ROS run in my OMAP850 @ 200 MHz PDA? :P
On Fri, Nov 19, 2010 at 8:18 PM, Ros Arm wrote:
> http://img209.imageshack.us/img209/5379/stuff0.png
>
> -r
>
>
> > http://img824.imageshack.us/img824/734/stuffy.png
> >
> > -r
> >
> >
> > ___
> >
It would be great to see the "ReactOS" logo at airports. Of course, let's not limit this to trying to install it native on the GameBoy Color :POn Sat, 20 Nov 2010 23:55:42 +1100, Javier Agustìn Fernàndez Arroyo wrote:@lassy:would ROS run in my OMAP850 @ 200 MHz PDA? :POn Fri, Nov 19, 2010 at 8
Hi,
finally this commit won't be reverted (unless someone explicitly asks for it)
as it brings testman back and shows quite important bugs.
Feel free to find a nice bugfix instead.
WBR,
P. Schweitzer
___
Ros-dev mailing list
Ros-dev@reactos.org
http:/
Great work, one more driver incompatibility away!
WBR,
Aleksey Bragin.
On Nov 20, 2010, at 1:42 AM, ek...@svn.reactos.org wrote:
Author: ekohl
Date: Fri Nov 19 22:42:53 2010
New Revision: 49646
URL: http://svn.reactos.org/svn/reactos?rev=49646&view=rev
Log:
[NPFS]
- Rename DEVICE_EXTENSION to
Hi,
Considering that:
- The code to throw out INIT sections isn't in trunk, so _nothing happens_ when
a function is made INIT or not.
- There were already many INIT functions in NTOSKRNL and the kernel worked fine
- 49463 only added INIT_FUNCTION to the HAL
- A later revision by Timo added INIT_
Hi,
I know that r49463 only added INIT_FUNCTION to HAL, but I reverted both, just
to be sure. I can get back ntoskrnl as they don't seem to be concerned.
Now, on other remarks, considering that:
- This has never be presented as a fix (but as a test)
- Win32k INIT_FUNCTION is not defined for GCC
Hi,
It appears your arguments are because you don't seem to understand what you
have done wrong.
Let me spell it out:
" I know that r49463 only added INIT_FUNCTION to HAL, but I reverted both, just
to be sure. I can get back ntoskrnl as they don't seem to be concerned."
ie:
"I know that my f
Hi
Please try the correct address: http://build.reactos.org:8010/
2010/11/20 Ros Arm
> Hi,
>
> I can't seem to access builds.reactos.org to check, but I think this
> argument really nails it: you really don't get it (you don't get the
> scientific method).
> Ros-dev mailing list
> Ros-dev@react
Hi,
Oops! Google Chrome could not connect to build.reactos.org:8010
It was a typo in my e-mail. I've used this website fine in the past before.
-r
> Hi
>
> Please try the correct address: http://build.reactos.org:8010/
>
> 2010/11/20 Ros Arm
>
> > Hi,
> >
> > I can't seem to access builds.r
Who the hell do you think you are?! The day I'll need lesson, don't worry I
know who you are and where to find you.
I won't waste my time answering. Understand whatever you want, imagine whatever
you want.
Just for your information:
http://svn.reactos.org/svn/reactos/trunk/reactos/subsystems/win
I even misread the header. I could have reverted win32k as well.
Luckily!
> Who the hell do you think you are?! The day I'll need lesson, don't worry I
> know who you are and where to find you.
> I won't waste my time answering. Understand whatever you want, imagine
> whatever you want.
> Just f
Hiya
Looks like i can confirm this issue. I`ll ask Chris to look into it. IE9
Beta is also having problems. For now you can use:
http://reactos.ath.cx:8081/waterfall
but only for compilation issues. I still await for Aleksiej to finish up
vbox sysreg so we can duplicate winetest automation.
Rega
Hiya
It looks like buildbot has crashed or been shut down. I restarted the master
but have no access to slaves. It will at least gather the build requests,
but the missing ones since last 6 hours need to be forced manually.
Christoph, could you take a look at the slaves??
Regards
___
Am 20.11.2010 18:13, Ros Arm wrote:
> Hi,
>
> It appears your arguments are because you don't seem to understand what you
> have done wrong.
Let me add my portion here as well.
Despite the fact that the scientific method doesn't seem to apply to
reactos coding (if you have evaluated all possibili
14 matches
Mail list logo
