I've implemented GUI consoles in CSRSS, see attached screenshot. If you
do nothing special, you're still launched into a text-mode console, the
blue screen we all know and love. If you rename
/ReactOS/system32/drivers/blue.sys to blue.sys.save you will be launched
into a graphical console.
There are still loads of problems. The biggest is that keyboard focus is
not restored when a program exits. So, from the GUI console you can
start e.g. winhello, but when you close winhello you won't be able to
type anything else in the console window. Activating windows by clicking
on them is also not implemented yet. You can't close a graphical console
by clicking on the "X", it doesn't know how to terminate the processes
running inside it yet.
The console code is a bit of a mess and needs to be cleaned up, it's
also one of the worst offenders with respect to indenting.
Gé van Geldorp.
It's now possible to change the screen resolution of the VMware virtual
display driver. You need to change some values in bootdata/hivesys.inf
(go to the vmx_svga section, there are some instructions at the bottom
of that section) and rebuild the system registry ("make registry" and
then copy the system hive to /reactos/system32/config).
Gé van Geldorp.
This is a patch to let more use the window size instead of the buffer
size. I'm planning to do some more work on the cmd utils, should I
integrate some of them in cmd.exe (as in 4nt) or leave them as separate
programs.
Timothy
Index: more.c
===================================================================
RCS file: /CVS/ReactOS/rosapps/cmdutils/more.c,v
retrieving revision 1.5
diff -u -p -r1.5 more.c
--- more.c 24 Feb 2003 23:16:13 -0000 1.5
+++ more.c 20 Oct 2003 09:36:52 -0000
@@ -5,6 +5,8 @@
*
* 26 Sep 1999 - Paolo Pantaleo <paolopan(a)freemail.it>
* started
+ * Oct 2003 - Timothy Schepens <tischepe at fastmail dot fm>
+ * use window size instead of buffer size.
*/
#include <windows.h>
@@ -29,11 +31,9 @@ GetScreenSize (PSHORT maxx, PSHORT maxy)
CONSOLE_SCREEN_BUFFER_INFO csbi;
GetConsoleScreenBufferInfo (hStdOut, &csbi);
+ *maxx = csbi.srWindow.Right;
+ *maxy = csbi.srWindow.Bottom;
- if (maxx)
- *maxx = csbi.dwSize.X;
- if (maxy)
- *maxy = csbi.dwSize.Y;
}
@@ -126,7 +126,7 @@ int main (int argc, char **argv)
{
ch_count=0;
line_count++;
- if (line_count == maxy-1)
+ if (line_count == maxy)
{
line_count = 0;
WriteFile(hStdOut,&buff[last], i-last+1, &dwWritten, NULL);
When i enter bugzilla, in upper menu first option proposed is "logout()" even
if i'm not logged in, more, sometimes, if i press on it, login page is not
displayed at all ...
Alex
Hi,
As GPLed Linux-NTFS still has no NTFS r/w capability I completed the project
for reliable r/w access in Wine way by using MS-Windows ntfs.sys driver.
Captive-NTFS
http://www.jankratochvil.net/
My project is GPL-2.0 and it incorporates ReactOS kernel sources currently also
carrying GPL-2.0 license. There are rumours GPL may be problem for linking with
proprietary code (ntfs.sys&ntoskrnl.exe). I interpret it as GPL only affects
_distribution_ of the program while no proprietary code is distributed with my
package. Proprietary code is only run-time linked by the end-user.
In a GPL-related discussion here two monts ago ReactOS developers were open for
reusal of existing proprietary drivers for ReactOS as one of the significant
feature of ReactOS. I would like an affirmation from the major ReactOS
developers they are not going to try to sue me for releasing Captive NTFS.
Thanks,
Jan Kratochvil
I've been taking a break from working on sound support under ReactOS
recently, for various reasons.
Mainly, I'm waiting for Steven Edwards to port winmm.dll from WINE over.
Once this is ported, I can implement a couple of stub drivers for audio and
MIDI, and then flesh out my Sound Blaster drivers. I'm still unsure if I
should incorporate both audio and MIDI handling into a single driver or not,
since I read something about IRQs for Sound Blaster cards and it confused me
(MIDI uses IRQ 2 while audio uses IRQ 5, usually, but the MS driver does
some weird stuff with the interrupt handler...)
Another reason is just because I've been having personal issues I've had to
deal with recently, so I haven't been getting as much done as I normally
would, and I've got other things I need to be doing.
But eventually I hope to get sound working under ReactOS, even if it is just
a command-line program to play WAV and MID files!
-Andrew
Hi,
Can we use the ros-desktop.bmp (copy the Reactos splash) as the logo for
the start menu side bar? It would look better than the ReactOS in baby
blue.
Thanks,
James
After tomorrow night I will no longer be recieving mail from the list.
I am moving from Swartz Creek Michigan to Dana Point California. I will
have internet access when i get there and will get back on the lists as
soon as i can.
Once i complete my move to california and get a job, i intend to resume
coding on ReactOS. In particular i'd like to get winrar, winzip, and
other utilities to work
I would like to take some time and modify the apps in the ros-apps
repository to use the latest stable build of mingw + the latest stable
build of w32api instead of the reactos build system, is this okay or is
there a reason that we are using the ReactOS build system?
So i'll see everybody soon!
Regards,
Richard
