On 2014-09-29 19.00, ros-dev-request(a)reactos.org wrote:
> w0000t
> natively? via an emulator???
> what the....
> \o/
@ Javier
I just stumbled by and saw it..
Выглядит безумно, но я установил и запустил ReactOS через обертку
Qemu - Limbo ARM 7 на своем Samsung Galaxy S III mini.
It looks crazy, but I installed and started the ReactOS through wrapper
Qemu - Limbo ARM 7 on your Samsung Galaxy S III mini.
//
It might be interesting to try wedging an ARM build into the S3 though.
I was mulling over the possibility to squeeze it into an Maple Native..
Love
Hey,
On 2014-10-31 10:22, akhaldi(a)svn.reactos.org wrote:
> @@ -90,6 +91,7 @@
> //Invalid parameter detected
> if (AllocAndLoadString(&lpIllegalMsg, GetModuleHandle(NULL), IDS_ILLEGAL_PARAM))
> _putts(lpIllegalMsg);
> + LocalFree(lpIllegalMsg);
> return FALSE;
> }
> }
>
This needs braces. Both puts and LocalFree should only be executed if
AllocAndLoadString succeeds (but return FALSE in either case).
Thanks!
Hi all,
As you can see in project-tools SVN, I've improved our Bash scripts for
Buildslaves. They're now also usable under Windows (in a Cygwin
environment) and I'm already doing this on our new Windows Buildslave
Carrier-Win7.
Bash on Windows may look hacky at first, but it's definitely more
comfortable than Batch! Moreover, we now only have a single version of
build scripts to maintain for all our Buildslaves!
This also involved some naming changes on the existing slaves to
maintain a consistent scheme. Tell me if anything broke.
Bringing all desired Windows builders back will still take some time.
I've only started with a RosBE-Windows based one right now and I need
your help here:
For some reason, VirtualBox 4.3.18 (used for reg-testing) doesn't want
to run headless. I can do a 'runas /user:buildbot VBoxManage controlvm
"ReactOS Testbot" poweroff' in a CMD and it will work well. The very
same command executed through BuildBot ends with:
====================================================================
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code E_ACCESSDENIED (0x80070005) - General access
denied error (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not
running or failed to start.
====================================================================
See
http://build.reactos.org/builders/Carrier-Win7%20VBox-Testbot/builds/6/step…
VBoxSVC.log isn't touched when BuildBot tries this command, so I have no
additional information.
Haven't found a solution yet, so I'm asking here if any of the VBox
experts know what could be going wrong.
Cheers,
Colin
Hello,
Let me invite you to the monthly status meeting taking place 30th of
October, 19:00 UTC (that's tomorrow!).
IRC service will only be started shortly before the meeting. Your
participation passwords and server address will be emailed to you
shortly before the meeting starts, and they are going to be different
once again as they are not stored in any database. Hopefully it's not
much of inconvenience.
If someone still is not getting passwords sent before a meeting - please
email Pierre before the meeting started to get one.
Please send agenda proposals to me before the meeting, so that we can
start with a proposed agenda.
Regards,
Aleksey Bragin