Casper Hornstrup wrote:
>
> Is there an interrest in generating a draft version of the ChangeLog
automatically from the
> commit logs?
How would you control if there were then changes to changes?
There are changes made in the mailing list that are then altered again and
again, or reverted completely.
e.g.
- Add notepad to the bootcd
- @changelog Included Notepad on the bootable CD
If then at a later date it was decided that was a bad idea, you would have:
- Remove notepad from bootcd
- @changelog Removed Notepad from the bootable CD.
Gedi.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Looking to the change made to usetup/bootsup.c,
I see we already have a TimeOut definition at line 61,
but this one is #ifed and therefore disabled by default.
You should remove it since it is now useless.
=====
Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net)
humans are like computers,
yesterday the BIOS was all
- today its just a word
Hi,
--- gdalsnes(a)cvs.reactos.com wrote:
> CVSROOT: /CVS/ReactOS
> Module name: reactos
> Repository: reactos/lib/wininet/
> Changes by: gdalsnes(a)mok.osexperts.com 04/12/15 19:00:08
>
> Modified files:
> reactos/lib/wininet/: stubs.c wininet.def
>
> Log message:
> add InternetOpenUrlA/W stubs
Don't worry about doing to much stuff to this as I have ported wininet from wine to the MSVC+PSDK
here and will be sending a patch to winehq and importing it in to ReactOS soon.
Thanks
Steven
__________________________________
Do you Yahoo!?
Send a seasonal email greeting and help others. Do good.
http://celebrity.mail.yahoo.com
> > Why would you want us to change from a very flexible debug
> > logging system to a less flexible one?
> >
> > Rob
>
> I would vote for using the WINE system in this case as it is more flexible.
Is the Wine debug logging system documented somewhere?
____________________________________________________________
Libero ADSL: 3 mesi gratis e navighi a 1.2 Mega, senza costi di attivazione.
Abbonati subito su http://www.libero.it
> > This will work on Linux and Windows
> > static const WCHAR KeyW[] = {'S','o','f','t','w','a','r','e','\\',
> > 'M','i','c','r','o','s','o','f','t','\\',
>
> Aiee! That looks painful. Is there nothing that can be done on WINE's
> side to make this easier? I suppose not or they would have done it
> already.
>
> Are there any objections to the above changes from anyone?
Let me ask a question. Is this piece of code
static const WCHAR KeyW = L"Software\\Microsoft\\";
a Microsoft C language extension or does it conform to a public C language
standard (C89, C99 et c.)?
____________________________________________________________
Libero ADSL: 3 mesi gratis e navighi a 1.2 Mega, senza costi di attivazione.
Abbonati subito su http://www.libero.it
Oh, well, can't win 'em all!
Just for the record, one major reason why I'm with the ReactOS project is
because I have to maintain a network of virus-traps going by the name of
Microsoft Windows 98, and I dream of replacing the wretched stuff by a
superior system.
Keep it up.
--
Wesley Parish
* * *
Clinersterton beademung - in all of love. RIP James Blish
* * *
Mau e ki, "He aha te mea nui?"
You ask, "What is the most important thing?"
Maku e ki, "He tangata, he tangata, he tangata."
I reply, "It is people, it is people, it is people."
> I had an idea about this....
>
> ExRosSetDebugLevel() and ExRosGetDebugLevel() can be ntdll umode
> syscalls into ntoskrnl. We should shadow the debug level in umode so
> that ExRosGetDebugLevel() doesn't have to jump to kmode every time we
> query it.
ExWineSetDebugLevel()
ExWineGetDebugLevel()
____________________________________________________________
Libero ADSL: 3 mesi gratis e navighi a 1.2 Mega, senza costi di attivazione.
Abbonati subito su http://www.libero.it
Hi All,
We have been invited to attend LinuxWorld in Boston on February 15-17, 2005. If anyone is
interested in attending please let me know. Arty and I may be going.
Thanks
Steven
__________________________________
Do you Yahoo!?
Send a seasonal email greeting and help others. Do good.
http://celebrity.mail.yahoo.com
Again I must say that I don't like this. Taking code from wine and then
changing it on purpose goes agains my beliefs that wine/ros should share
as much as possible and that changes should go _both_ ways. My hope for
the future of ros/wine is that ros/wine spesific stuff is placed into
seperate files/libraries/etc. to make merging/sharing possible/easier.
This would probably mean that most ros umode dlls eventually will be
completely wineismed, but if that means we can share more code, i
couldn't care less.
Gunnar
ekohl(a)cvs.reactos.com wrote:
> CVSROOT: /CVS/ReactOS
> Module name: reactos
> Repository: reactos/lib/kernel32/misc/
> Changes by: ekohl(a)mok.osexperts.com 04/12/13 13:16:28
>
> Modified files:
> reactos/lib/kernel32/misc/: profile.c
>
> Log message:
> - Remove Wine-isms from the profile code.
> - Wrap single-line if-statements.
> - Cleanup the indentation.
>
> _______________________________________________
> Ros-cvs mailing list
> Ros-cvs(a)reactos.com
> http://reactos.com/mailman/listinfo/ros-cvs
>
>
>
>
Hi,
--- Jason Filby <jason.filby(a)gmail.com> wrote:
> Out of interest, does WINE have a spacing standard, and if so where
> can I read about it?
Its mostly free form with a few exceptions. Its not really documented. You can read about it here
http://www.kerneltraffic.org/wine/wn20020530_124.html#3http://www.winehq.com/hypermail/wine-devel/2002/11/1340.html
> Sounds good; why not change to WINEs macros everywhere in ReactOS?
I am not opposed to it, I just don't know how we would support debugging
a driver vs a dll if we had support to toggle the messages. I guess it
could be done with little trouble everywhere.
> Aiee! That looks painful. Is there nothing that can be done on WINE's
> side to make this easier? I suppose not or they would have done it
> already.
The problem is in GCC on *nix. I don't think there is much we can do about
it short of fixing GCC. If we ever do a ELF building using gcc on linux to
build ReactOS for another CPU then we will have the same issue.
Thanks
Steven
__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com
Hi
On Tue, 14 Dec 2004 09:54:32 -0800 (PST), Steven Edwards
<steven_ed4153(a)yahoo.com> wrote:
> Also I am not talking about issues like tabs and spaces. That can be debated all day
> long.....
Out of interest, does WINE have a spacing standard, and if so where
can I read about it?
> DPRINT and DPRINT1 really need to go and we could just standise on using the Wine
> macros in our Win32 system, FIXME, WARN, ERR, etc. It reduces the diff and if we ever
> get support for switching the debug channels then it will make life less of a pain.
Sounds good; why not change to WINEs macros everywhere in ReactOS?
> This will work on Linux and Windows
> static const WCHAR KeyW[] = {'S','o','f','t','w','a','r','e','\\',
> 'M','i','c','r','o','s','o','f','t','\\',
Aiee! That looks painful. Is there nothing that can be done on WINE's
side to make this easier? I suppose not or they would have done it
already.
Are there any objections to the above changes from anyone?
Cheers
Jason
gdalsnes(a)cvs.reactos.com wrote:
> -NtSetInformationToken: lie and say we succeded
>
>
>
It would be nice to say what apps take advantage of this change, or why
it was done? What app now works because of this?
And in either case, this function is extremly easy to implement...
Best regards,
Alex Ionescu
Couldnt we do like some software do today ? (like Wine ? :))
make depends && make
--- Ge van Geldorp <ge(a)gse.nl> a écrit :
> I agree, but it's a bit of a chicken-and-egg problem. The Makefiles include
> the dependency files which refer to the now-removed header. To regenerate
> the dependency files we have to run make, which uses the Makefiles...
>
> Gé van Geldorp.
>
> > -----Original Message-----
> > From: Syl_sf [mailto:spetreolle@users.sourceforge.net]
> > Sent: Thursday, December 09, 2004 23:34
> > To: Ge van Geldorp; spetreolle(a)users.sourceforge.net;
> > 'ReactOS Development List'
> > Subject: RE: [ros-dev] Problem in dependancies
> >
> >
> > Actually I was already doing it to have a successful
> > compilation. But I dont think running 'make clean' after
> > every commit is the best thing to do.
> >
> > My "aclui" choice was totally random, but no file was changed
> > in the aclui CVS since 7 weeks. (It doesnt use mmsystem nor
> > imports it)
> >
> > Many thanks for your help.
> >
=====
Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net)
humans are like computers,
yesterday the BIOS was all
- today its just a word
Hi!
I asked on #ReactOS and ros-general, but received no answer. So I'm
asking for help here. How to fix this error? Can anybody at least give
ma a hint what files am I missing, please?
WinME, GCC 3.3.1, fresh sources.
[DEPENDS] i386/.setjmplongjmp.d
[DEPENDS] .rosglue.d
[RC] freetype.rc
[CC] rosglue.c
[AS] i386/setjmplongjmp.s
[AR] freetype.a
ar: objs/*.o: No such file or directory
MAKE.EXE: *** [freetype.a] Error 1
I saw Steven doing some dewineism commits also.
But why remove wineism?
It will be much easier to see differences with wine code when fixing
bugs etc. if the code in question was taken from wine and wine for
example has fixed a bug we are hunting. In kernel32 there are some files
that i have taken from wine and the only thing changed is the include
files, to make it possible to merge wine changes back.
> CVSROOT: /CVS/ReactOS
> Module name: reactos
> Repository: reactos/lib/advapi32/crypt/
> Changes by: ekohl(a)mok.osexperts.com 04/12/12 07:16:27
>
> Modified files:
> reactos/lib/advapi32/crypt/: crypt.c crypt.h crypt_des.c
> crypt_lmhash.c crypt_md4.c
> crypt_md5.c crypt_sha.c
>
> Log message:
> - Remove Wine-isms from advapi32 because it's a ReactOS DLL!
"because it's a ReactOS DLL"? So if we have to change one file out of
many to adapt a wine dll as ours, we have to dewineism all other files
also?
> - Enforce a consistent coding style.
> - Remove -D__REACTOS__
>
> _______________________________________________
> Ros-cvs mailing list
> Ros-cvs(a)reactos.com
> http://reactos.com/mailman/listinfo/ros-cvs
>
>
>
>
weiden(a)cvs.reactos.com wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/subsys/win32k/stubs/
>Changes by: weiden(a)mok.osexperts.com 04/12/11 17:40:44
>
>Modified files:
> ./: config
> reactos/include/napi/: win32.h
> reactos/include/win32k/: bitmaps.h brush.h dc.h gdiobj.h kapi.h
> ntuser.h pen.h region.h text.h
> reactos/lib/user32/include/: user32.h window.h
> reactos/lib/user32/misc/: dllmain.c stubs.c
> reactos/lib/user32/windows/: defwnd.c
> reactos/subsys/win32k/eng/: bitblt.c clip.c mouse.c objects.h
> surface.c xlate.c
> reactos/subsys/win32k/include/: cursoricon.h dce.h inteng.h
> intgdi.h mouse.h object.h
> palette.h tags.h
> reactos/subsys/win32k/main/: dllmain.c
> reactos/subsys/win32k/: makefile w32k.h
> reactos/subsys/win32k/misc/: object.c
> reactos/subsys/win32k/ntddraw/: ddraw.c
> reactos/subsys/win32k/ntuser/: desktop.c input.c misc.c stubs.c
> windc.c window.c winpos.c
> winsta.c
> reactos/subsys/win32k/objects/: bitmaps.c brush.c cliprgn.c
> color.c dc.c dib.c fillshap.c
> gdiobj.c line.c palette.c pen.c
> print.c region.c text.c
> reactos/subsys/win32k/stubs/: stubs.c xpstubs.c
>Added files:
> reactos/subsys/win32k/include/: intddraw.h
> reactos/subsys/win32k/ntuser/: cursoricon.c
> reactos/subsys/win32k/objects/: stockobj.c
>Removed files:
> reactos/subsys/win32k/eng/: clip.h handle.c handle.h
> reactos/subsys/win32k/objects/: cursoricon.c
>
>Log message:
> 1. remove mouse cursor hacks from eng/mouse
> 2. implemented more win2k-like gdi handle table (handle entry lookup is not yet optimized/cached!)
> 3. moved cursoricon.c from objects to ntuser as it's part of the user api and not of the gdi
> 4. get rid of the eng handle table
> 5. minor fixes
>
>
I'm not sure if it's exactly this commit, but Miranda IM now crashes
win32k badly. Also the mouse cursor hacks had a reason... if you remove
them, please fix the problem different way. Now there is no cursor set
during the startup and so when Explorer tries to revert the hourglass
cursor to a normal one, the call just fails.
Regards,
Filip
While trying to install a current CVS (both freeldr and reactos)
bootcd on real hardware, I was greeted with a DIVIDE BY ZERO
exception. After asking some people on IRC and poking around in
Bugzilla, It turned out I was not getting all the output I needed, due
to what seems to be doublespaced output..
Screenshot: http://waxdragon.homeip.net/~ford/freeldr_crash.png
After poking around a bit, I rolled i386trap.S back to rev 1.5 and
then I got the second half of the output. I stared at i386trap.S for
a while, and cannot figure out where the problem is.
FreeLoader gurus, can you help me, please? ;0)
WD
--
The cheese stands alone.
Hi all!
weiden(a)cvs.reactos.com wrote:
> CVSROOT: /CVS/ReactOS
> Module name: reactos
> Repository: reactos/lib/advapi32/sec/
> Changes by: weiden(a)mok.osexperts.com 04/12/10 16:21:34
>
> Modified files:
> reactos/lib/advapi32/: advapi32.def advapi32.h makefile
> reactos/lib/advapi32/misc/: sysfunc.c
> reactos/lib/advapi32/token/: token.c
> Added files:
> reactos/lib/advapi32/crypt/: .cvsignore crypt.c crypt.h
> crypt_des.c crypt_lmhash.c
> crypt_md4.c crypt_md5.c crypt_sha.c
> reactos/lib/advapi32/sec/: trustee.c
>
> Log message:
> port crypt and trustee support from Wine. Patch by Steven Edwards.
I'm getting this,
[CC] crypt/crypt.c
In file included from crypt/crypt.c:28:
../../include/wine/port.h:248: error: parse error before "pread"
../../include/wine/port.h:248: warning: type defaults to `int' in declaration of `pread'
../../include/wine/port.h:248: warning: data definition has no type or storage class
../../include/wine/port.h:252: error: parse error before "pwrite"
../../include/wine/port.h:252: warning: type defaults to `int' in declaration of `pwrite'
../../include/wine/port.h:252: warning: data definition has no type or storage class
make: *** [crypt/crypt.o] Error 1
Good port, we need it for AbiWord 2.2.1,
James
Hello,
I was just looking on how to add FreeDOS to the ReactOS loader,
just as I did for NT bootmenu and Syslinux bootmenu
(both should be working by now)
There's one problem:
I need to update one section "[Operating Systems]" with something like:
FreeDOS="FreeDOS (Beta Distribution)"
and add a section (that's the easy part, and same as for boot.ini),
which I use the following (ASM) program for:
http://www.coli.uni-sb.de/~eric/stuff/soft/specials/text-tool-iniadd.zip
[FreeDOS]
Description="FreeDOS Beta"
BootType=Bootsector
Bootsector=C:\FREEDOS.BSS
I was wondering if you could not remove the [Operating Systems] section
(all it does is provide a label/section description), and do the
following (add description):
[ReactOS]
Description="ReactOS"
BootType=ReactOS
SystemPath=multi(0)disk(0)rdisk(0)partition(1)\ReactOS
[ReactOS_DebugCom1]
"ReactOS (Debug, COM1)"
BootType=ReactOS
SystemPath=multi(0)disk(0)rdisk(0)partition(1)\ReactOS
Options=/DEBUGPORT=COM1
*****instead of:************
[Operating Systems]
ReactOS="ReactOS"
ReactOS_DebugCom1="ReactOS (Debug, COM1)"
[ReactOS]
BootType=ReactOS
SystemPath=multi(0)disk(0)rdisk(0)partition(1)\ReactOS
[ReactOS_DebugCom1]
BootType=ReactOS
SystemPath=multi(0)disk(0)rdisk(0)partition(1)\ReactOS
Options=/DEBUGPORT=COM1
It would require to read the entire freeldr.ini for non-standard
sections ([FREELDR] and [DISPLAY]) like for example [REACTOS]
by the way, sample freeldr.ini does not show how to use Bootsector,
I'll guess I'll just have to install ReactOS over FreeDOS then to figure
this out.
Final request: add a small delay on the LiveCD, so someone can boot to
A: for example from the FreeLDR which is used on cdrom (boot to C: is
already taken care of through cdrom bootsector).
Bernd
Hi!
I was playing around with the output of our build system a bit... I very
much like the way Linux-2.6 does it - it looks like this:
[RC] ntoskrnl.rc
[AS] ke/i386/multiboot.S
[PCH] include/ntoskrnl.h
[CC] ex/i386/interlck.c
[CC] ke/i386/exp.c
...
[CC] inbv/inbv.c
[AR] ntoskrnl.a
[LD] ntoskrnl.nostrip.exe
[RSYM] ntoskrnl.sym
[OBJDUMP] ntoskrnl.map
[LD] ntoskrnl.exe
ntoskrnl.exe was successfully built.
I think everybody will like this output - my question is wether
1) it should become the default (if VERBOSE is unset) and the old output
can be produced if VERBOSE=yes
or
2) the old output should stay the default and the fancy one should be
used if VERBOSE=half or something like this
- blight
winlogin from Windows 2000 and XP creates desktops:
application desktop, winlogon desktop (only winlogon can access this
desktop) and a screen saver desktop.
ReactOS only has one desktop at the moment (correct me if I am false). I
know many security features like login are not implemented. But for a future
release (0.4) ...
Klemens Friedl <frik85>
--
NEU +++ DSL Komplett von GMX +++ http://www.gmx.net/de/go/dsl
GMX DSL-Netzanschluss + Tarif zum superg�nstigen Komplett-Preis!
