On 7/2/07, greatlrd(a)svn.reactos.org <greatlrd(a)svn.reactos.org> wrote:
> Author: greatlrd
> Date: Mon Jul 2 23:47:58 2007
> New Revision: 27364
>
> URL: http://svn.reactos.org/svn/reactos?rev=27364&view=rev
> Log:
> experiment code
> adding DirectX opengl warper that using opengl lcd driver. it is Parallels modify source code of wine d3d for it.
> can not be compile in ReactX branch yet.
I've already fixed this locally to compile with mingw using dsw2mak if
anyone wants my hacky diff and some makefiles. Contact me privately
off the list and I can send you what I have thus far...wined3d.dll and
d3d8.dll everything else should build as well but I have no futher
need to work on this.
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Hi people,
Im receiving password reminders for the ros-dev list.
Problems :
- I didnt ask for it,
- The password sent is not mine,
- My password has been reset to the password sent in the reminder
Feel free to say if you have similar problems
& thanks for any help.
Kind regards,
Sylvain Petreolle (aka Usurp)
----- Message d'origine ----
De : "ros-dev-bounces(a)reactos.org" <ros-dev-bounces(a)reactos.org>
À : spetreolle(a)yahoo.fr
Envoyé le : Samedi, 30 Juin 2007, 16h40mn 54s
Objet : Ros-dev(a)reactos.org mailing list reminder
You, or someone posing as you, has requested a password reminder for
your membership on the mailing list ros-dev(a)reactos.org. You will
need this password in order to change your membership options (e.g. do
you want regular delivery or digest delivery), and having this
password makes it easier for you to unsubscribe from the mailing list.
You are subscribed with the address: spetreolle(a)yahoo.fr
Your Ros-dev password is: <removed>
Hello,
I did some testing/bug fixing into RegEdit.
Bug #982: some languages still had this bug. Now seems fixed.
Bug #997: In my opinion it happened because it tried to process an encoded UTF-16 registry file. Now if an UNICODE .reg file is detected, it won't be processed by ascii functions.
Bug #1008: It doesn't happen into Microsoft WinXP, so it seems a bug of the edit control into ReactOS.
Bug #1009: Fixed.
Other bug fixes are:
* Now the horizontal scrollbar is shown.
* Fixed several bugs/memory leaks/destroying action into listview code.
* Into the Listview, only the variable name is shown, without its entire path.
* When importing a file, the handle was left open. Now it's fixed.
The attached patch includes all these changes.
Sincerely,
Carlo Bramini
------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode di Wind
http://i-mode.wind.it/
I have the lastest thunk, it updated some files, but it doesn't work yet.
In addition to this trouble, in makefile.auto there is also an error into lines like these ones:
$(OUTPUT)\livecd\Profiles\Default\ User\My\ Documents: | $(OUTPUT)\livecd\Profiles\Default\ User
$(ECHO_MKDIR)
${mkdir} $@
The rule must be:
$(OUTPUT)\livecd\Profiles\Default\\ User\My\\ Documents: | $(OUTPUT)\livecd\Profiles\Default\\ User
with two backslash otherwise the escape sequence won't work.
Sincerely,
Carlo Bramini.
---------- Initial Header -----------
>From : ros-dev-bounces(a)reactos.org
To : "ReactOS Development List" ros-dev(a)reactos.org
Cc :
Date : Tue, 26 Jun 2007 10:04:23 +0200
Subject : Re: [ros-dev] Error at compiling ReactOS
> Be sure you use the latest trunk. Weiden has fixed compilation problems.
> So, update, clean, and it should work.
>
> ----- Original Message -----
> From: "carlo.bramix" <carlo.bramix(a)libero.it>
> To: "ros-dev" <ros-dev(a)reactos.org>
> Sent: Tuesday, June 26, 2007 9:39 AM
> Subject: Re: [ros-dev] Error at compiling ReactOS
>
> Hello,
> It looks like there is a bug somewhere.
> I launched with "ROS_RBUILD_FLAGS=-v" and I got this output:
>
> [CC] tools/wpp/ppy.tab.c
> [AR] output-i386/tools/wpp/libwpp.a
> [LD] output-i386/tools/widl/widl.exe
> [WIDL] obj-i386\include\psdk\wtypes.h
> Could not open includepsdkwtypes.idl
> make[1]: *** [obj-i386\include\psdk\wtypes.h] Error 2
>
> Then I open makefile.auto and I manually patched '\' to '/' but just for
> "wtypes".
> I got this output:
>
> [WIDL] obj-i386/include/psdk/wtypes.h
> [WIDL] obj-i386\include\psdk\exdisp.h
> Could not open includepsdkexdisp.idl
> make: *** [obj-i386\include\psdk\exdisp.h] Error 2
>
> Sincerely,
>
> Carlo Bramini.
>
> ---------- Initial Header -----------
>
> >From : ros-dev-bounces(a)reactos.org
> To : "ReactOS Development List" ros-dev(a)reactos.org
> Cc :
> Date : Mon, 25 Jun 2007 17:12:33 +0200
> Subject : Re: [ros-dev] Error at compiling ReactOS
>
> > Hi,
> >
> > it's not important to have the latest versions, you've got to have the
> > "right" versions.
> >
> > You seem to be using windows, just download the RosBE, the official
> > ReactOS Build Environment.
> >
> > This should give you a start:
> > http://www.reactos.org/wiki/index.php/RosBE-step-by-step
> >
> > Greets,
> >
> > David Hinz
> >
> > carlo.bramix schrieb:
> > > Hello,
> > > I can use a powerful PC for some days, so I downloaded latest ReactOS's
> > > sources and I tried to compile them.
> > > But after a short while, it appear this message:
> > >
> > > [WIDL] obj-i386\include\psdk\wtypes.h
> > > Could not open includepsdkwtypes.idl
> > > make: *** [obj-i386\include\psdk\wtypes.h] Error 2
> > >
> > > In your opinion, what's wrong?
> > > It happens into the CMD box and into MSYS too.
> > > I'm sure that "Mingw & co." tools are the latest versions.
> > >
> > > Sincerely,
> > >
> > > Carlo Bramini.
> > >
> > >
> > > ------------------------------------------------------
> > > Leggi GRATIS le tue mail con il telefonino i-modeTM di Wind
> > > http://i-mode.wind.it/
> > >
> > >
> > > _______________________________________________
> > > Ros-dev mailing list
> > > Ros-dev(a)reactos.org
> > > http://www.reactos.org/mailman/listinfo/ros-dev
> > >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
>
> ------------------------------------------------------
> Leggi GRATIS le tue mail con il telefonino i-modeT di Wind
> http://i-mode.wind.it/
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode di Wind
http://i-mode.wind.it/
Hello,
It looks like there is a bug somewhere.
I launched with "ROS_RBUILD_FLAGS=-v" and I got this output:
[CC] tools/wpp/ppy.tab.c
[AR] output-i386/tools/wpp/libwpp.a
[LD] output-i386/tools/widl/widl.exe
[WIDL] obj-i386\include\psdk\wtypes.h
Could not open includepsdkwtypes.idl
make[1]: *** [obj-i386\include\psdk\wtypes.h] Error 2
Then I open makefile.auto and I manually patched '\' to '/' but just for "wtypes".
I got this output:
[WIDL] obj-i386/include/psdk/wtypes.h
[WIDL] obj-i386\include\psdk\exdisp.h
Could not open includepsdkexdisp.idl
make: *** [obj-i386\include\psdk\exdisp.h] Error 2
Sincerely,
Carlo Bramini.
---------- Initial Header -----------
>From : ros-dev-bounces(a)reactos.org
To : "ReactOS Development List" ros-dev(a)reactos.org
Cc :
Date : Mon, 25 Jun 2007 17:12:33 +0200
Subject : Re: [ros-dev] Error at compiling ReactOS
> Hi,
>
> it's not important to have the latest versions, you've got to have the
> "right" versions.
>
> You seem to be using windows, just download the RosBE, the official
> ReactOS Build Environment.
>
> This should give you a start:
> http://www.reactos.org/wiki/index.php/RosBE-step-by-step
>
> Greets,
>
> David Hinz
>
> carlo.bramix schrieb:
> > Hello,
> > I can use a powerful PC for some days, so I downloaded latest ReactOS's sources and I tried to compile them.
> > But after a short while, it appear this message:
> >
> > [WIDL] obj-i386\include\psdk\wtypes.h
> > Could not open includepsdkwtypes.idl
> > make: *** [obj-i386\include\psdk\wtypes.h] Error 2
> >
> > In your opinion, what's wrong?
> > It happens into the CMD box and into MSYS too.
> > I'm sure that "Mingw & co." tools are the latest versions.
> >
> > Sincerely,
> >
> > Carlo Bramini.
> >
> >
> > ------------------------------------------------------
> > Leggi GRATIS le tue mail con il telefonino i-modeTM di Wind
> > http://i-mode.wind.it/
> >
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode di Wind
http://i-mode.wind.it/
I first saw this project in 2005, and today, in order to have a rough
idea of Windows Cache Manager, I want to download the Ros source code to
see if it is something alike and whether it can help me.
Regards,
Fan Decheng 2007-06-26
+#if 0 //FIXME: Investigate why it's reported that Geode does not support
this.
if (!(KeFeatureBits & KF_CMPXCHG8B))
{
/* Copy the vendor string */
@@ -475,6 +476,7 @@
Vendor[1],
Vendor[2]);
}
+#endif
Umm, because it doesn't.
--
Best regards,
Alex Ionescu
Hello,
I can use a powerful PC for some days, so I downloaded latest ReactOS's sources and I tried to compile them.
But after a short while, it appear this message:
[WIDL] obj-i386\include\psdk\wtypes.h
Could not open includepsdkwtypes.idl
make: *** [obj-i386\include\psdk\wtypes.h] Error 2
In your opinion, what's wrong?
It happens into the CMD box and into MSYS too.
I'm sure that "Mingw & co." tools are the latest versions.
Sincerely,
Carlo Bramini.
------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode di Wind
http://i-mode.wind.it/
Hello,
Hopefully, at work I have Windows XP and at home I have Win9x.
This gave me great chances of testing when I develop a software.
I was just guessing if the autoplay nightmare could be disabled in a more user-friendly way and natively into the configuration of the explorer into ReactOS.
Sincerely,
Carlo Bramini.
---------- Initial Header -----------
>From : ros-dev-bounces(a)reactos.org
To : "ReactOS Development List" ros-dev(a)reactos.org
Cc :
Date : Thu, 21 Jun 2007 12:10:47 -0600
Subject : Re: [ros-dev] Autoplay configuration.
> On 6/21/07, carlo.bramix wrote:
> >
> > I didn't use Vista yet, but I wouldn't like to decided every time the
> > actions to do.
> > Usually, when I double-click on the CD/DVD icon, I would like to explore
> > the content of the disk.
> > I don't want to see something asking me "explore disk? autoplay disk? play
> > disk?", I just want to see the directory structure.
>
>
> Haha, I wasn't saying that it should ask you every time you double click the
> drive icon. I was talking about when you actually put in the disc or
> connect a device.
>
>
> I already solved this little need my Win9x platforms with a very little C
> > programme.
> > Personally, I can't see a valid reason for not putting this little thing
> > (enable/disable autoplay features) somewhere.
>
>
> Things have changed a lot with autoplay from earlier Windows versions to XP,
> and even more from XP to Vista. Vista even has a section in the control
> panel for autoplay configuration:
> http://img160.imageshack.us/img160/6287/windowsvistaautoplayjs2.png (169 KB)
>
> Also, you have brought up a good point. Besides those parts of the autoplay
> configuration, ReactOS should have an additional option to specify whether
> to just view the contents of the drive with no autoplay prompts when you
> double-click a drive or open up the autoplay options when you double click
> the drive -- that is, if it will even support opening that up at all when
> double-clicking a drive, which if it doesn't that's fine, too, as long as
> the option is at least there when right-clicking the drive.
>
> -ShadowFlare
>
>
> Sincerely,
> >
> > Carlo Bramini
> >
> >
> > ---------- Initial Header -----------
> >
> > >From : ros-dev-bounces(a)reactos.org
> > To : "ReactOS Development List" ros-dev(a)reactos.org
> > Cc :
> > Date : Tue, 19 Jun 2007 17:05:13 -0600
> > Subject : Re: [ros-dev] Autoplay configuration.
> >
> > > On 6/19/07, carlo.bramix wrote:
> > > >
> > > > Hello,
> > > > I would like to suggest the addition of a little feature into ReactOS.
> > > > Here there is a little reference to be read near my suggestion:
> > > >
> > > >
> > > >
> > http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentr…
> > > >
> > > > Autorun could be useful, but sometimes it's very annoying.
> > > > So: what about adding a little page somewhere for configuring it?
> > > > Into Win9x it was partially configurable on CD/DVD units, but newer
> > > > versions of Windows lost completely this ability.
> > > > I think that a little page with some check-boxes:
> > > >
> > > > [ ] Disables Autoplay on removable drives
> > > > [X] Disables Autoplay on fixed drives.
> > > >
> > > > ..etc
> > > > would be really cool because it fixes a mess into modern Microsoft's
> > > > products.
> > > > I think it can be done in 100 lines of code (perhaps even less).
> > > > If we decide that it can be added, we just need to decide where we
> > could
> > > > put them.
> > > >
> > > > I know that ReactOS haven't autoplay feature yet, but adding its
> > > > configuration isn't too difficult.
> > > > Where can it be placed?
> > > > Personally, I wouldn't add a new applet into the control panel only
> > for
> > > > it.
> > > > Or if you don't want it at all, or you don't want it for now, it's ok
> > too.
> > > >
> > > > Sincerely,
> > > >
> > > > Carlo Bramini.
> > > >
> > > > _______________________________________________
> > > > Ros-dev mailing list
> > > > Ros-dev(a)reactos.org
> > > > http://www.reactos.org/mailman/listinfo/ros-dev
> > > >
> > >
> > > Personally, I think Windows Vista's autorun/autoplay options are great,
> > and
> > > it does have a place to change the configuration for them easily. In my
> > > opinion, Microsoft finally got it right on that version. It even asks
> > > whether you want the run the program from autorun.inf, so no more
> > holding
> > > shift while inserting CDs. :) It also gives the other usual autoplay
> > > options even on CDs that do have a program specified in autorun.inf.
> > >
> > > In my opinion, ReactOS should do it the same way, at least as far as
> > asking
> > > whether to run the program or not when you insert a CD or plug in a
> > drive.
> > >
> > > -ShadowFlare
> > >
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
I didn't use Vista yet, but I wouldn't like to decided every time the actions to do.
Usually, when I double-click on the CD/DVD icon, I would like to explore the content of the disk.
I don't want to see something asking me "explore disk? autoplay disk? play disk?", I just want to see the directory structure.
I already solved this little need my Win9x platforms with a very little C programme.
Personally, I can't see a valid reason for not putting this little thing (enable/disable autoplay features) somewhere.
Sincerely,
Carlo Bramini
---------- Initial Header -----------
>From : ros-dev-bounces(a)reactos.org
To : "ReactOS Development List" ros-dev(a)reactos.org
Cc :
Date : Tue, 19 Jun 2007 17:05:13 -0600
Subject : Re: [ros-dev] Autoplay configuration.
> On 6/19/07, carlo.bramix wrote:
> >
> > Hello,
> > I would like to suggest the addition of a little feature into ReactOS.
> > Here there is a little reference to be read near my suggestion:
> >
> >
> > http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentr…
> >
> > Autorun could be useful, but sometimes it's very annoying.
> > So: what about adding a little page somewhere for configuring it?
> > Into Win9x it was partially configurable on CD/DVD units, but newer
> > versions of Windows lost completely this ability.
> > I think that a little page with some check-boxes:
> >
> > [ ] Disables Autoplay on removable drives
> > [X] Disables Autoplay on fixed drives.
> >
> > ..etc
> > would be really cool because it fixes a mess into modern Microsoft's
> > products.
> > I think it can be done in 100 lines of code (perhaps even less).
> > If we decide that it can be added, we just need to decide where we could
> > put them.
> >
> > I know that ReactOS haven't autoplay feature yet, but adding its
> > configuration isn't too difficult.
> > Where can it be placed?
> > Personally, I wouldn't add a new applet into the control panel only for
> > it.
> > Or if you don't want it at all, or you don't want it for now, it's ok too.
> >
> > Sincerely,
> >
> > Carlo Bramini.
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
> Personally, I think Windows Vista's autorun/autoplay options are great, and
> it does have a place to change the configuration for them easily. In my
> opinion, Microsoft finally got it right on that version. It even asks
> whether you want the run the program from autorun.inf, so no more holding
> shift while inserting CDs. :) It also gives the other usual autoplay
> options even on CDs that do have a program specified in autorun.inf.
>
> In my opinion, ReactOS should do it the same way, at least as far as asking
> whether to run the program or not when you insert a CD or plug in a drive.
>
> -ShadowFlare
>
> Personally, I think Windows Vista's autorun/autoplay options are great,
and
> it does have a place to change the configuration for them easily. In my
> opinion, Microsoft finally got it right on that version.
I hate autorun and always disable it. I always hate that menu where you can
choose what to do with CD/connected storage device/camera etc.
I`d love to see ROS silent or at least being allowed to disable all those
unneeded extras.
Regards
Caemyr
>People developing ReactOS also usually join our IRC-channel #reactos
>on freenode.
>If you become a steady ReactOS developer, somebody will offer you SVN
>write access so you don't need to submit everything to bugzilla, but
>that will take a while...
If you think you can participate in develompent of any particular
subsystem/part of Ros you should speak with Fireball on #reactos. He may
designate you to some specified field. This could speed up the joining
process, but do it only if you feel experienced enough.
Regards
Caemyr
Hi,your mailling system showed me to send you this mail so you can get the decision on accepting me to join the development-team of ReactOSKind regards,Fatih Yedikapi** Greating from best friend, Fatih Yedikapi **
_________________________________________________________________
Via je PC gratis je vrienden hun PC bellen
http://get.live.com/messenger/overview
Hi I am trying to use the cmd.exe of reactos (on Windows!) with redirected
stdin/out/err. What I try to make is a remote shell application over
internet, and this is an important requirement for me, that it will work
with reacto's cmd.exe.
I have build a test program that will redirect locally. open the process (
cmd.exe at least for now) and will forward output on a EditBox. The whole
process works quite well with the cmd.exe of M$ Windows but its buggy with
the cmd.exe of reactos. More specifically when I start the redirection I
just get the current path and ">" usual prompt, but after that, the
communication gets unresponsive. Whatever I send, there will be no return
messages.
I attached the test project, and I would like to advice me if there is a
better approach that will work for ROS cmd.exe too.
>Hi I am trying to use the cmd.exe of reactos (on Windows!) with redirected
>stdin/out/err. What I try to make is a remote shell application over
>internet, and this is an important requirement for me, that it will work
>with reacto's cmd.exe.
>I have build a test program that will redirect locally. open the process
>(cmd.exe at least for now) and will forward output on a EditBox. The whole
>process works quite well with the cmd.exe of M$ >Windows but its buggy with
>the cmd.exe of reactos. More specifically when I start the redirection I
>just get the current path and ">" usual prompt, but after that, the
>communication gets unresponsive. >Whatever I send, there will be no return
>messages.
>I attached the test project, and I would like to advice me if there is a
>better approach that will work for ROS cmd.exe too.
What you have proposed is basically telnet.
Extremely insecure.
You really should consider using SSH or similar.
Also it looks like you are using pipes to do the transferring from the code
(but I could have misread it), and they only traverse local networks. You'd
be better off with netcat or similar (if you're OK with low security).
You could just use a command line like:
netcat | cmd | netcat
JGR
_________________________________________________________________
MSN Music http://music.msn.no Finn din favorittmusikk blant nesten 1 million
låter
Hello,
I would like to suggest the addition of a little feature into ReactOS.
Here there is a little reference to be read near my suggestion:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentr…
Autorun could be useful, but sometimes it's very annoying.
So: what about adding a little page somewhere for configuring it?
Into Win9x it was partially configurable on CD/DVD units, but newer versions of Windows lost completely this ability.
I think that a little page with some check-boxes:
[ ] Disables Autoplay on removable drives
[X] Disables Autoplay on fixed drives.
..etc
would be really cool because it fixes a mess into modern Microsoft's products.
I think it can be done in 100 lines of code (perhaps even less).
If we decide that it can be added, we just need to decide where we could put them.
I know that ReactOS haven't autoplay feature yet, but adding its configuration isn't too difficult.
Where can it be placed?
Personally, I wouldn't add a new applet into the control panel only for it.
Or if you don't want it at all, or you don't want it for now, it's ok too.
Sincerely,
Carlo Bramini.
So the reason you noticed this was wrong wasn't because DRIVERS SHOULDN'T IMPORT USER-MODE WIN32 DLLS... but because someone else was already exporting it. Sweet.
Hint: Try including #intrin.h next time.
--
Best regards,
Alex Ionescu
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of spetreolle(a)svn.reactos.org
Sent: Saturday, June 16, 2007 5:45 AM
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [spetreolle] 27203: revert previous r27194 ntoskrnl already exports InterlockedDe/Increment spotted by hpoussin still fails to link, thans to heisspiter for win32 test
Author: spetreolle
Date: Sat Jun 16 16:45:02 2007
New Revision: 27203
URL: http://svn.reactos.org/svn/reactos?rev=27203&view=rev
Log:
revert previous r27194
ntoskrnl already exports InterlockedDe/Increment
spotted by hpoussin
still fails to link,
thans to heisspiter for win32 test
Modified:
trunk/reactos/drivers/wdm/audio/backpln/portcls/portcls.rbuild
Modified: trunk/reactos/drivers/wdm/audio/backpln/portcls/portcls.rbuild
URL: http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/wdm/audio/backpln/…
==============================================================================
--- trunk/reactos/drivers/wdm/audio/backpln/portcls/portcls.rbuild (original)
+++ trunk/reactos/drivers/wdm/audio/backpln/portcls/portcls.rbuild Sat Jun 16 16:45:02 2007
@@ -8,7 +8,6 @@
<library>ntoskrnl</library>
<library>ks</library>
<library>drmk</library>
- <library>kernel32</library>
<file>dll.c</file>
<file>adapter.c</file>
I neved did and never intend to merge hacks from branches into the
trunk.
I don't know where from you are referring to "I'm afraid that
fireballs sollution is merged into trunk in some time"?!
I commented out almost all freeldr's bootsector boot stub in the
branch, does that mean it will somewhen be merged in trunk? Obviously
the answer is no.
I don't know what do you smoke to think it will :-).
WBR,
Aleksey Bragin.
On Jun 16, 2007, at 6:07 AM, Michael Fritscher wrote:
> The problem: the new bootvid needs vga, which the olpc doesn`t have...
> For the other problem (freeloader import problem): He can't press
> enter on
> this machine because of the bios.
> Perhaps that could be better solved by a new option in freeldr,
> which make
> disappear all messages in say 3-5 seconds.
>
> I'm afraid that fireballs sollution is merged into trunk in some time,
> which would hide this problem indead.
Are you allright, Alex? :-)
This is in a branch, OLPC ("branches/olpc/").
I had to disable critical warnings in freeldr so I don't have to do a
BIOS-less keyboard support in olpc-freeldr in order to just hit ENTER
one time during the bootup.
And certainly, when trunk's bootvid has VGA dependency coded into the
very heart of it, I had to get old bootvid so that I could do the
framebuffer support (no VGA bios in OLPC hardware). Also in that same
branch.
As for hto's (Dmitry) patches - there are controversial opinions, but
I'm trying to review and discuss commits he is doing.
WBR,
Aleksey Bragin.
On Jun 15, 2007, at 10:51 PM, Alex Ionescu wrote:
> Screwing up compatibility continues! Here's an idea, let's rename
> all the kernel exports!
>
> -----Original Message-----
> From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-
> bounces(a)reactos.org] On Behalf Of fireball(a)svn.reactos.org
> Sent: Friday, June 15, 2007 3:59 AM
> To: ros-diffs(a)reactos.org
> Subject: [ros-diffs] [fireball] 27186: - Resurrect "old" bootvid.
> The plan is to * make it working in trunk * add framebuffer support
> for olpc and xbox kind of devices.
>
> Author: fireball
> Date: Fri Jun 15 14:58:37 2007
> New Revision: 27186
>
> URL: http://svn.reactos.org/svn/reactos?rev=27186&view=rev
> Log:
> - Resurrect "old" bootvid. The plan is to
> * make it working in trunk
> * add framebuffer support for olpc and xbox kind of devices.
>
> Added:
> branches/olpc/drivers/base/bootvid/bar.bmp
So the new ReactOS is all about adding hacks to the kernel and hiding existing bugs instead of finding solutions. Cool beans. Maybe you should also comment out other DPRINTs. I mean, if a critical warning that a driver wasn't properly loaded because FreeLDR doesn't process import tables and that thus the device won't work right is annoying, maybe stuff like "File not found" should also be removed and return success instead.
I can't wait 6 months from now when everyone wonders how come some driver doesn't load in ReactOS. Are you and hto actually the same person?
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of fireball(a)svn.reactos.org
Sent: Friday, June 15, 2007 3:27 AM
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [fireball] 27185: - Set esp in the beginning to freeldr's stack, fixes a crash during a call to the kernel's entrypoint. - Comment out some annoying / unnecessary dprints (including messagebox about not resolved imports for pciide).
Author: fireball
Date: Fri Jun 15 14:27:27 2007
New Revision: 27185
URL: http://svn.reactos.org/svn/reactos?rev=27185&view=rev
Log:
- Set esp in the beginning to freeldr's stack, fixes a crash during a call to the kernel's entrypoint.
- Comment out some annoying / unnecessary dprints (including messagebox about not resolved imports for pciide).
Modified:
branches/olpc/boot/freeldr/freeldr/arch/i386/arch.S
branches/olpc/boot/freeldr/freeldr/arch/i386/loader.c
branches/olpc/boot/freeldr/freeldr/arch/i386/macholpc.c
Modified: branches/olpc/boot/freeldr/freeldr/arch/i386/arch.S
URL: http://svn.reactos.org/svn/reactos/branches/olpc/boot/freeldr/freeldr/arch/…
==============================================================================
--- branches/olpc/boot/freeldr/freeldr/arch/i386/arch.S (original)
+++ branches/olpc/boot/freeldr/freeldr/arch/i386/arch.S Fri Jun 15 14:27:27 2007
@@ -395,7 +395,7 @@
//movw %dx,%fs
//movw %dx,%gs
//movw %dx,%ss
- //movl $STACK32ADDR,%esp
+ movl $STACK32ADDR,%esp
//movl $mb_info,%ebx
/* See if the boot device was passed in */
Modified: branches/olpc/boot/freeldr/freeldr/arch/i386/loader.c
URL: http://svn.reactos.org/svn/reactos/branches/olpc/boot/freeldr/freeldr/arch/…
==============================================================================
--- branches/olpc/boot/freeldr/freeldr/arch/i386/loader.c (original)
+++ branches/olpc/boot/freeldr/freeldr/arch/i386/loader.c Fri Jun 15 14:27:27 2007
@@ -487,7 +487,7 @@
}
else
{
- DbgPrint("Don't yet support loading new modules from imports\n");
+ //DbgPrint("Don't yet support loading new modules from imports\n");
Status = STATUS_NOT_IMPLEMENTED;
}
}
Modified: branches/olpc/boot/freeldr/freeldr/arch/i386/macholpc.c
URL: http://svn.reactos.org/svn/reactos/branches/olpc/boot/freeldr/freeldr/arch/…
==============================================================================
--- branches/olpc/boot/freeldr/freeldr/arch/i386/macholpc.c (original)
+++ branches/olpc/boot/freeldr/freeldr/arch/i386/macholpc.c Fri Jun 15 14:27:27 2007
@@ -253,7 +253,7 @@
BOOLEAN OlpcDiskGetDriveGeometry( ULONG DriveNumber, PGEOMETRY DriveGeometry )
{
- ofwprintf("GetGeometry(%d)\n", DriveNumber);
+ //ofwprintf("GetGeometry(%d)\n", DriveNumber);
DriveGeometry->BytesPerSector = 512;
DriveGeometry->Heads = 16;
DriveGeometry->Sectors = 63;
@@ -262,7 +262,7 @@
ULONG OlpcDiskGetCacheableBlockCount( ULONG DriveNumber )
{
- ofwprintf("GetCacheableBlockCount\n");
+ //ofwprintf("GetCacheableBlockCount\n");
return 1;
}
Hi,
> -----Message d'origine-----
> De : ros-diffs-bounces(a)reactos.org
> [mailto:ros-diffs-bounces@reactos.org] De la part de
> dgorbachev(a)svn.reactos.org
> Envoyé : jeudi 14 juin 2007 18:42
> À : ros-diffs(a)reactos.org
> Objet : [ros-diffs] [dgorbachev] 27174: - Hackish solution of
> issue #2062. - Turn off title change, as it can cause a deadlock.
>
> Author: dgorbachev
> Date: Thu Jun 14 20:41:55 2007
> New Revision: 27174
>
> URL: http://svn.reactos.org/svn/reactos?rev=27174&view=rev
> Log:
> - Hackish solution of issue #2062.
> - Turn off title change, as it can cause a deadlock.
>
> Modified:
> trunk/reactos/subsystems/win32/csrss/win32csr/conio.c
> trunk/reactos/subsystems/win32/csrss/win32csr/dllmain.c
> trunk/reactos/subsystems/win32/csrss/win32csr/guiconsole.c
>
Why hiding the real cause of bug 2062 by a hack, as you already did in
r27107 for bug 2151?
See desktop icons in explorer bar. They are not correct and I know when it
appeared and I known how to hack a solution. But I won't do it because I
don't want to hide the real problem. IMO, you should do the same thing and
search the root problem or leave the effect visible, so it won't be
forgotten.
If you really need to add a hack in the code, please add a comment in the C
code linking to bugzilla, and add a comment in BZ saying "hackish solution
committed in rXXXXX"
Hervé
Unfortunately, I'm not able to compile myself.
So I download the SVN ISO images for testing.
I was just wondering if it could be possible to reduce a bit my download times by including that flag into the REL builds.
I also agree that it's better to leave the DEB builds without that flag.
Thanks anyways, if it's not possible I can still download compressed ISO files at their current sizes.
Sincerely,
Carlo Bramini
---------- Initial Header -----------
>From : ros-dev-bounces(a)reactos.org
To : "ReactOS Development List" ros-dev(a)reactos.org
Cc :
Date : Mon, 11 Jun 2007 14:28:37 +0400
Subject : Re: [ros-dev] Smaller SVN REL ISO?
> It is possible to compile with this flag, but you need to build it
> yourself then. Official ISOs are compiled with leanandmean set to no.
>
>
> WBR,
> Aleksey Bragin.
>
> On Jun 11, 2007, at 1:06 PM, carlo.bramix wrote:
>
> > Is the SVN REL Live CD compiled with "set ROS_LEAN_AND_MEAN = yes"?
> > If not, is it possible to compile it with this flag?
> > For other purposes beside the normal user testing, we have the SVN
> > DEB Live CD image.
> >
> > Sincerely,
> >
> > LDChen
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode di Wind
http://i-mode.wind.it/