Where is my Server core style command prompt login? Screw explorer. Oh,
and I want RDP. ;0p
On Oct 27, 2010 4:18 PM, "Adam Kachwalla" <geekdundee(a)gmail.com> wrote:
We need to first fix up the logon screen. I have tried this, except the
problem lies with CreateDesktop() not wanting to create more than one
desktop within the Winlogon process.
At this stage, the logon/logoff functionality does not work at all, and some
processes still linger about.
It appears explorer shell is one of them.
On Thu, 28 Oct 2010 02:22:36 +1100, Javier Agustìn Fernàndez Arroyo <
elhoir(a)gmail.com> wrote:
> H...
--
Give a man a fish and he will eat for a day.
Teach a man to fish and he will eat for a lifetime.
Give a man religion and he will die praying for a fish.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://ww...
Hello, devs!
ok, lets stop flaming and lets do anything useful 3:>
For the future:
will ReactOS support "true" multiuser sessions (that is, *simultaneously*)?
Is it possible?
that would be a big enhancement over Windows :)
I think that Wine Gecko should be integrated in the ReactOS releases. It
is needed IIRC for things like Winhlp32 (I think) and HTML Help
(defiitely) and applications which use IE browser controls.
Hi ReactOS friends and colleagues.
There have been exciting years, I first started to have an eye on the
freewin95 project. When I first found the ReactOS project and saw
that they actually gave away free zip-files with files to try it out
I was eager to test it my self, I first downloaded my first
“bochs-1.3-reactos-images.zip” the third april 2002, and it worked! I
was amazed, so I downloaded and tested everything that I could test.
A long time has gone since that time and I have seen a lot of
progress during the years, however it's a lot of years, for me about
nine years of downloading, compiling, testing and reading svn-
messages. For many people it has been too many years and many have
fallen away, now however we are close to something that can actually
be used, the kernel is pretty stable other parts of the OS is
improving and getting there too.
During the last many years we have had about 100 individuals in the
IRC channel at all time, it indicates in my mind that we attract as
many people as we loose, I guess that is kind of the status for our
project, we should be able to change that in a short while I think.
If we can release a some real-life applications for our OS we could
draw some attention that could be permanent and the project could
really start to grow for real.
I and Aleksey met in Björkvik, Sweden for a discussion on how to get
the ball rolling, we have some suggestions that could serve as step
stones for such development. The key is to release a package of the
project and see to that it can really do that but not everything
else, for example, a web server, it doesn't need all the OS but the
ones it needs it has to do really good.
Even with this in mind ReactOS isn't well suited for many real
applications, so we just looked at a few to see if it would be a way
to go, you could perhaps suggest some more, and we would welcome
that, we only have to ensure there isn't too much work to actually
come to the finish line. Here we present some ideas and what needs to
get in place to actually make it work.
Webserver
- Network subsystem (mainly tcpip.sys driver, and some winsock
improvement)
- VNC support (future RDP support)
- Apache/MySQL/PHP support
- XAMPP with toolbox
- WEBMIN
Thin Client (LiveCD or BootCD)
- Re-port our MSTSC.EXE
- Local printing (USB/LPT printer support?)
Please give us your opinion and please also add possible ideas that
you have and think through what needs to get in place to see it come
to pass.
Yours sincerely,
Aleksey & Jan (Jaix)
through Jan
Am 26.10.2010 18:01, schrieb jgardou(a)svn.reactos.org:
> +#ifdef __GCC__
> /* Note: this should return a CLIENT_CALL_RETURN, but calling convention for
> * returning structures/unions is different between Windows and gcc on i386. */
> LONG_PTR RPC_VAR_ENTRY
> @@ -659,6 +663,13 @@
> NdrAsyncClientCall( PMIDL_STUB_DESC pStubDescriptor, PFORMAT_STRING pFormat, ... );
> LONG_PTR RPC_VAR_ENTRY
> NdrDcomAsyncClientCall( PMIDL_STUB_DESC pStubDescriptor, PFORMAT_STRING pFormat, ... );
> +#else
> +CLIENT_CALL_RETURN RPC_VAR_ENTRY NdrClientCall2(
> + PMIDL_STUB_DESC pStubDescriptor,
> + PFORMAT_STRING pFormat,
> + ...
> +);
> +#endif
>
Is this hack even neccessary? I couldn't see any difference between gcc
and msvc with the correct prototype.
Both return the result in eax.
Hi,
good to see the branch work back in trunk, I suspected this work would be
left to rot and finally be forgotten (like in most other experimental
branches). Altogether this looks like a huge step forward, got to test those
mode switches it once I have enough time.
One thing I noticed from the diffs is the eng/mem.c file, which exceeded my
EVIL / HACK threshold. Is this supposed to stay - especially in the context
of ARM3's to be proven awesomeness?
--- snippet ---
EngSecureMem(PVOID Address, ULONG Length)
{ return (HANDLE)-1; // HACK!!! }
EngUnsecureMem(HANDLE Mem)
{ if (Mem == (HANDLE)-1) return; // HACK!!! }
--- snippet ---
Good work anyway, thanks to the people involved!
Regards,
Gregor
You could always run two installs in different directories.
On Oct 25, 2010 10:51 AM, "Bernd Blaauw" <bblaauw(a)home.nl> wrote:
Op 25-10-2010 16:09, Fan Zhang schreef:
>
> Thanks. But I don't know if i run ReactOS, how could I replace the kernel
file, such as ntoskrl...
So basicly running a ReactOS installation with RosBE installed as
application, sources downloaded and modified, and then you want a way to
update files from this ReactOS installation itself?
As long as ReactOS installs only on FAT filesystem, I guess you could use a
DOS bootdisk/installation to overwrite any files. It's not entirely
convenient.
Is there basicly a set of lists of ReactOS files for the following:
* which ReactOS files can be overwritten by a new file while you're still
running in ReactOS? .inf files? small games like solitaire?
* which ReactOS files can be overwritten, but require a reboot to be
properly noticed? some drivers perhaps?
* which ReactOS files require you to be outside of ReactOS in order to
replace them? ntoskrnl comes to mind, explorer I guess
All in all, mr Fan Zhang might be asking for some kind of update mechanism.
If you had an old machine which you run ReactOS on, together with same
casual data (audio files perhaps), do you need to reformat the disk to
update ReactOS? or only remove the installation directory? or pick a
different installation directory? or same directory? After all, you don't
want to lose any user data.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://ww...
Hi guys,
I want to know how do you debug ReactOS. For example, when I change the
code, I used to execute 'Make bootcd'. After that, I will install the
ReactOS system by ReactOS.iso. So I'm confused if I have to install the whoe
system after compiling. Do you have some easy way?
Thanks.
Fan
Hi,
I thought I would drop a line here finally :)
My name is Oleg, I am from Russia (some 180km from Moscow :)). I worked with
Aleksey many years ago on some kernelmode networking-related tasks for
Windows NT 4.0 and later Windows 2000. Your recent 0.3.12 release news was
all over the place here on Russian news sites, my congratulations! ReactOS
is a great project, though I never had enough time to actually start
hacking, but recent achievements seems to motivate me more.
What is situation with networking in ReactOS? I think this could be my main
direction of work. I would glad if someone writes a current state of
networking in ROS, so I would know where to start.
// Oleg Baikalow.