And you said you were too busy with school...... :p
Ged
-----Original Message-----
From: ion(a)svn.reactos.com [mailto:ion@svn.reactos.com]
Sent: 15 April 2005 07:25
To: ros-svn(a)reactos.com
Subject: [ros-svn] [ion] 14625: Implemented Guarded Mutex, a drop-in
replacement for Fast Mutex (the correct one, not the one ROS incorrectly
implements) on NT 5.2. Not fully tested yet, so nothing switched to it and
probably not usable. Also made KeGetCurrentThre
Implemented Guarded Mutex, a drop-in replacement for Fast Mutex (the correct
one, not the one ROS incorrectly implements) on NT 5.2. Not fully tested
yet, so nothing switched to it and probably not usable. Also made
KeGetCurrentThread/Irql become inlined, since this should create quite a
speed boost. Made KeLeaveCriticalRegion deliver APCs if possible, and made
Crit regions macros usable from outside ntoskrnl thanks to a new NT 5.2 API
(KiCheckForKernelApcDelivery). Guarded Mutex code based on Filip Navara.
Updated files:
trunk/reactos/drivers/storage/diskdump/diskdump.c
trunk/reactos/hal/hal/hal.c
trunk/reactos/hal/halx86/generic/fmutex.c
trunk/reactos/hal/halx86/generic/irql.c
trunk/reactos/include/ddk/kedef.h
trunk/reactos/include/ddk/kefuncs.h
trunk/reactos/include/ddk/ketypes.h
trunk/reactos/ntoskrnl/Makefile
trunk/reactos/ntoskrnl/ex/i386/interlck.c
trunk/reactos/ntoskrnl/include/internal/i386/ke.h
trunk/reactos/ntoskrnl/include/internal/i386/ps.h
trunk/reactos/ntoskrnl/include/internal/ke.h
trunk/reactos/ntoskrnl/include/internal/ps.h
trunk/reactos/ntoskrnl/ke/apc.c
trunk/reactos/ntoskrnl/ke/gmutex.c
trunk/reactos/ntoskrnl/ntoskrnl.def
trunk/reactos/ntoskrnl/ps/thread.c
trunk/reactos/w32api/include/ddk/winddk.h
_______________________________________________
Ros-svn mailing list
Ros-svn(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-svn
************************************************************************
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
I've just managed to get hold of a copy of VMWare 5.0 through work.
I'll install a copy tonight and see how that goes.
Ged.
-----Original Message-----
From: ea [mailto:ea@iol.it]
Sent: 14 April 2005 23:18
To: Jason Filby; ReactOS Development List
Subject: Re: [ros-dev] crash on ROS vmware install
On the 13th, in QEmu I had a stop due to serial.sys
http://users.libero.it/ea/ros/qemu-ros-200504130002.jpg
On IRC, Hervé said he's working on it.
Jason Filby wrote:
>Hi
>
>I'm getting a similar crash under QEmu.
>
>Cheers
>Jason
>
>On 4/14/05, Gedi <gedi(a)ntlworld.com> wrote:
>
>
>>Source taken from HEAD just before Casper took it down for the rebuild.
>>
>>Initially it was hanging just after the splash so I rebuilt with DGB to
>>see if I could glean more info.
>>
>>Now it crashes upon install, just before it goes to the GUI config.
>>
>>Here is a sceenshot of the crash
>>http://homepage.ntlworld.com/gedmurphy/crash.jpg
>>
>>I have attached the map files for smss. I would have stuck on one for
>>ntoskrnl too, but it's a little large.
>>
>>
The map file is for the production SM: the one in the blue screen is the
1st stage (text) setup program (in the boot disk it get renamed to be
run by ntoskrnl with no changes).
Emanuele
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev
************************************************************************
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
Since two days I released the RC2 to sf.net
What's our plan for the next release (candidate)?
As you may see, I went to RAR concerning sources and map files. I don't
know whether this is such a good idea. At least the size relation
convinced me. Map: 17MB vs. 30MB or Src: 15MB vs. 27MB
I think for people still working with modem this is an advance (even if
they have to search to unrar). The difference in sizes seems to me is
the solid kind of archive. Thus tarbz2 should do the same
Comments?
Thanks Dmitry, I'm cc'ing our dev team on this :)
Cheers
Jason
On 4/13/05, Dmitry Viktorovich Long <dvd.long(a)gmail.com> wrote:
> Yes.
> ReactOS is the most f**king BEST product I've ever seen. Great thanks
> to all of you. Do not ever stop, don't even think it.
>
> Best regards, ReactOS fan.
>
I've been doing a bit of work on the usetup code and came to realize
that we have a bit of a widespread problem in a lot of code. There is a
great deal of code that looks basically like this pseudo code:
NSTATUS DoSomething()
{
NSTATUS Status;
...
Status = NtXXX();
if( !NT_SUCCESS( Status ) )
return Status;
Status = NtYYY();
if( !NT_SUCCESS( Status ) )
{
cleanupXXX();
return Status;
}
Status = NtZZZ();
if( !NT_SUCCESS( Status ) )
{
cleanupYYY();
cleanupXXX();
return Status;
}
// yay, everything worked
cleanupZZZ();
cleanupYYY();
cleanupXXX();
return STATUS_SUCCESS;
}
This type of error handling is absolutely horrible. Just look at all of
the duplicate code! There are 3 different return points and each one
duplicates all of the code from the previous, and adds one more line.
Maintaining code like this becomes very hard, and it produces a larger,
slower executing binary.
Now ideally all of those NtXXX functions would be throwing a SEH
exception on failure instead of returning the failure code, and we could
just write that code like so:
void do_something()
{
__try {
NtXXX();
NtYYY();
NtZZZ();
// manipulate the stuff you allocated
}
__finally {
cleanupZZZ();
cleanupYYY();
cleanupXXX();
}
}
But sadly, I don't think that is ever going to happen. Instead, I
propose that we use goto to eliminate the duplicate points of return,
and wrap the goto in a nice macro. So far I've come up with this macro:
#define NTCALL(target, function) if( Status = function ) goto target;
And you use it like this:
NTSTATUS do_something()
{
NTSTATUS Status;
NTCALL( done, NtXXX(...) );
NTCALL( cleanXXX, NtYYY(...) );
NTCALL( cleanYYY, NtZZZ(...) );
// manipulate x, y, and z here
cleanZZZ:
cleanupZZZ();
cleanYYY:
cleanupYYY();
cleanXXX:
cleanupXXX();
done:
return Status;
}
Now that code is more compact and maintainable than the original, and
will produce a leaner binary. I'm still trying to improve on it a bit
but I like this basic idea, so I'm throwing it out for comments. Last
night I came up with this macro and in about 10 minutes I rewrote the
file copy routine in usetup to use memory mapping instead of allocating
a huge buffer, reading in the source file, then writing it out to the
destination. The new code involves making several more system calls
than the old code, but since the error handling has been greatly cleaned
up, the new code is more compact and easier to maintain.
Hi all.
On 13.04.2005 at about 09:00 CET, I'll be taking svn.reactos.com down for reconfiguration of RAID and installation of Service Pack
1.
I expect the repository to be operational within 8 hours.
Casper
hey arty,
seems you forgot to commit one file :
rosdhcp_public.h
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
Hi,
today I was pointed to an article in the austrian newspaper named "Der
Standard" about ReactOS:
http://derstandard.at/?id=2010724
It's quite short, but what if not even heise.de reports?
Hi,
why do you change this file? Alloca.c isn't used and should be removed.
If we have an alloca function somewhere in our source, it must be
completely written in assembler because the stack layout and the using
of ebp depends on the compilers optimisation.
- Hartmut
arty(a)svn.reactos.com wrote:
>Commit for blight: fix stack alignment.
>
>
>Updated files:
>trunk/reactos/lib/crtdll/stdlib/alloca.c
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
>
--- Phillip Susi <psusi(a)cfl.rr.com> wrote:
> Steven Edwards wrote:
> > We have PSEH which can be used.
> >
> > Thanks
> > Steven
>
> PSEH?
We have a macro based SEH implementation we are using in ReactOS called PSEH for Portable SEH.
Hyperion wrote it and it seems to work with almost ever compiler thrown at it. It is not syntax
compatible with MS-SEH but some people have been working to develop p(retty)pseh which should be.
Look in reactos/lib/pseh and grep the source tree. Its used in ntoskrnl, win32k, afd?, and others.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
NTSTATUS DoSomething()
{
NSTATUS Status;
...
Status = NtXXX();
if (!NT_SUCCESS(Status))
goto done;
Status = NtYYY();
if (!NT_SUCCESS(Status))
goto cleanXXX;
Status = NtZZZ();
if (!NT_SUCCESS(Status))
goto cleanYYY;
cleanZZZ:
cleanupZZZ();
cleanYYY:
cleanupYYY();
cleanXXX:
cleanupXXX();
done:
return Status;
}Thomas
NTSTATUS DoSomething()
{
NSTATUS Status = NtXXX();
if (NT_SUCCESS(Status)) {
Status = NtYYY();
if (!NT_SUCCESS(Status))
cleanupXXX();
Status = NtZZZ();
if (!NT_SUCCESS(Status))
cleanupYYY();
}
return Status;
}
i think thats the most simple and easy to read
but in the end is´ent it not a littel waste of time
discusse old functions their need rewrite anyway..?
Thomas
Hi,
--- Phillip Susi <psusi(a)cfl.rr.com> wrote:
> How is it not readable? I think it is MUCH better than the original
> code. You don't have a half dozen lines of (mostly duplicated) cleanup
> code after every call, but what you're calling and what you're passing
> to it are still quite clear. Like I said though, it still isn't as
> ideal as SEH, but it's not the terrible mess the original code was. If
> you have any suggestions on how to make it even more clean, I'm all ears.
We have PSEH which can be used.
Thanks
Steven
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail
Hi,
with my last changes it is possible to install ros from the boot cd and
select the floppy as boot device. Currently there exist three problems.
After selecting the floppy as boot medium it is shown a dialog box which
does mean, there is no disk inserted. A second try detect the disk. The
installer copies all files to the floppy disk. After trying to restart
the computer, ros hangs. I must manually reset the pc. The floppy disk
is still inserted at this point. The pc does boot up, accessing the
floppy disk, shows 'Loading FreeLoader...' and shows 'Disk error \nPress
any key". Pressing a key results in the same message. If I remove and
insert the disk again, I can load freeloader from the floppy disk and it
does boot reactos. It seems, that the bios isn't able to initialize the
floppy controller correctly after reactos was running. I've added a
shutdown procedure in floppy.sys which resets the floppy controller over
the DSR register, but this doesn't help. Has anyone an idea what is
wrong?
- Hartmut
Well, I finally solved my problems with getting freeldr to boot from a
hard drive. The first is a problem with fat.bin itself. Early during
it's execution it checks to see if the boot sector header specifies a
device ID of 0xff, and if so, it uses the device ID the bios passes in
CL when it invokes the boot sector, otherwise it uses the device ID in
the boot sector header. The device ID field of the boot sector is
inherently unreliable and should NEVER be used. In my case mtools was
leaving it as it was in fat.bin, which is 0, so it was trying to access
the floppy instead of the hard disk. I have fixed this by removing the
check to see if the field is 0xff, so the code will always use the
device passed by the bios.
The second problem was far more stupid. mtools was not specifying
O_BINARY when opening the boot sector template file, and as a result,
cygwin was translating newlines, so it clobbered the boot sector.
I'm all set to check in the fix to fat.asm, but I was never asked by
subversion ( tortoise client ) to log in, so I assume it just used anon
or something. How do I tell subversion to log me in as me?
A simpler fix would be to a change of the BootDrive value to 0xFF.
As you said, the current value is 0,
but thats by design,
since all the values have been filled for a 1.44M diskette.
Even the File System ID could have been set differently,
since the neutral value 'FAT ' is allowed here.
--- Phillip Susi <psusi(a)cfl.rr.com> wrote:
> Well, I finally solved my problems with getting freeldr to boot from a
> hard drive. The first is a problem with fat.bin itself. Early during
> it's execution it checks to see if the boot sector header specifies a
> device ID of 0xff, and if so, it uses the device ID the bios passes in
> CL when it invokes the boot sector, otherwise it uses the device ID in
> the boot sector header. The device ID field of the boot sector is
> inherently unreliable and should NEVER be used. In my case mtools was
> leaving it as it was in fat.bin, which is 0, so it was trying to access
> the floppy instead of the hard disk. I have fixed this by removing the
> check to see if the field is 0xff, so the code will always use the
> device passed by the bios.
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
phreak(a)svn.reactos.com wrote:
>Fixed freeldr fat16 boot sector to use the bios provided boot device number instead of the ( usually invalid ) one in the boot sector header.
>
>
Could you please fix that also in the fat32 bootsector?
Best Regards,
Thomas
I had the same problem on real hardware.
I removed serenum & serial.sys and the system could boot again.
I dont know if the problem is into serenum or serial though.
hpoussin, it seems the solution is in your hands ;)
--- Saveliy Tretiakov <saveliyt(a)mail.ru> wrote:
> revision 14561 can't boot on vmware 4.5
> debug output is attached
> > _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
Some bioses set numlock to on at startup.
Since ReactOS is setting it to off state,
the LED status must be set accordingly.
Attached patch fixes it.
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
Hi,
I am currently entering the last 5 weeks of school of my last year, so
I'm going to be focusing on that instead of ReactOS. Lately, I've tried
to work on both, but this has delayed my code as well as hurt my grades.
I intend to be back around the week of May 10th.
In the meanwhile, I would kindly like to ask developers to e-mail me if
they have any plans to touch the following:
- Kernel Scheduler, Thread Creation, Context Switching, System
Initialization. I have re-written everything for a faster and more
complete system based on NT semantics. Includes everything from realtime
support, proper dynamic and static priorities, real system thread
support, much faster scheduling, pre-emption, removal of the PEB/TEB 64K
block hack and ros-only members, better organized code and Mm routines
for manipulating kernel stack/teb/peb, etc...
- Pushlocks. I have almost all the necessary support code written and
I'm only missing one function.
- IRQL management in HAL and Spinlocks. I have highly modified the IRQL
routines for a large increase in speed, as well as made spinlocks faster
on UP and non-debug builds. I have also corrected some IRQL routines to
use the proper KPCR members for the IRR and others.
- Object Manager. I have a complete re-write in progress which uses
public NT structures instead of our internal ones, adds more security,
and corrects some missing features and adds some. Majorly changes some
aspects of the Ob (for example regarding on the status of handle/pointer
count after creating an object, and the work of ObCreate/ObInsertObject,
which is totally different in ROS vs NT. See blog article for more
info). However, any bugs that are easy to fix should still be fixed in
the current Ob. The new one is months away.
- Queued Spin Locks, KGATES, Guarded Mutex. I already know Filip is
working on this and I was planning on collaborating with him. Unlike the
previous things, I haven't actually *coded* anything regarding these,
but I have the design in my head and would like to work on it, so I
would love to share what I know if anyone is actively interested in
working on it.
Once again, to clear up any misconceptions, I'm asking an email to know
if anyone plans to work on this for the purposes of:
1) Not duplicating work
2) Sharing what information/code I might have written.
In any case, I'll be back in exactly one month, so I don't think it'll
matter. You guys keep focusing on PnP and other stuff meanwhile, okay?
*joke*
Best regards,
Alex Ionescu
Hi all.
This is my changes :)
serialui
- Started serialui dll
- Implemented drvCommConfigDialogA and drvCommConfigDialogW
kernel32.diff
- Implemented CommConfigDialogA and CommConfigDialogW
- Removed @unimplemented comments for some implemented functions
include.diff
- Add missing ioctls to ntddser.h:
IOCTL_SERIAL_GET_COMMCONFIG and IOCTL_SERIAL_SET_COMMCONFIG
btw.
Screenshot is here:
http://www.ljplus.ru/img2/drg4njubas/commdlg.JPG
Hi,
it'd be nice if something like
r14554: Delete riched20
r14555: Copy riched20
can be avoided in preference of the *cause* the required the changes above.
Everybody can see that riched20 was deleted and added afterwards but you
cannot see *why* this has been done.
Regards,
Mark
I'm not sure what the current state of ReactOS' GDIPLUS.DLL implementation
is, and I know it's just a case of downloading the DLL from Microsoft for
the functionality, but I've been recently looking into making a mini GUI
API for a program I'm working on, and the author informed me someone is
making a GDIPLUS.DLL clone, using Anti-Grain:
www.antigrain.com
I'm unsure what the URL was for the project as I'm not at home at the
moment, but I figured if GDIPLUS.DLL needs some work in ReactOS, it would
be a good starting point to use the one based on Anti-Grain, as apparently
the one from MS is slower and has a few glitches (see the demos on the
Anti-Grain site - specifically the one with the arrows pointing at the
different blobs.)
Just thought it might be worth a mention :)
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .
--- Mark Junker <mjscod(a)gmx.de> wrote:
> r14554: Delete riched20
> r14555: Copy riched20
>
> can be avoided in preference of the *cause* the required the changes above.
>
> Everybody can see that riched20 was deleted and added afterwards but you
> cannot see *why* this has been done.
This was because it was a merge from the trunk and when importing Wine code on the trunk you have
to delete the existing copy and import from the vendor branch.
Please read
http://reactos.com/wiki/index.php/Using_code_from_other_projects
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
I can imagine the News:
BIG CORPORATION SUES A GROUP OF COLLEGES FOR
DEVELOPING A NEW WINDOWS.
MICROSOFT THREATENS A LITTLE NON PROFIT PROYECT!
MICROSOFT AGAINST LIBRE SOFTWARE!
This has the chance to make microsoft more damage than
you think they can do to ReactOS, unless they feel
really threatened i doubt there will be any microsoft
legal atack unless you use clearly microsoft code in
the near or intermediate time.
>
----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 7 Apr 2005 13:31:19 -0700 (PDT)
> From: Steven Edwards <steven_ed4153(a)yahoo.com>
> Subject: Re: [ros-dev] ReactOS Foundation 501c3
> Status - Approved
> To: ReactOS Development List <ros-dev(a)reactos.com>
> Message-ID:
> <20050407203119.68427.qmail(a)web21121.mail.yahoo.com>
> Content-Type: text/plain; charset=us-ascii
>
> Hi James,
>
> --- James Tabor
> <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net>
> wrote:
> > Paying developers? Hum?
> >
> > I don't want to be the bad guy here, but this
> could push people away from the project. It would
> > be
> > like going back to five years ago when ROS had no
> GUI just a command console. Everyone will wait
> > for five or so developers to fix things, and trust
> me it does happen that way in the real world.
> > The back log will kick their asses.
>
> See the other thread. I don't think paying
> developers as full time workers is a good idea. I
> think
> Contracts or bounties on certain projects are.
>
> > Now I have to ask, where does the money come from?
> If the ORG has no money, I guess it should
> > produce a competing distribution CD. This could
> make M$ happy, so M$ would have a target to
> > sue at. Also everyone on the board would become a
> target as well.
>
> I was wrong in the other email. I forgot we have $25
> in the general fund atm which was raised at
> LinuxWorld. I expect we can make quite a bit selling
> CDs, T-Shirts, Etc, if we want as well as
> just accepting donations. As for the fear of
> lawsuit, the idea behind the foundation was that it
> was better the foundation get sued and try to have
> some cash for legal defence rather than some
> poor developer in school. Everybody here knows the
> risk from Microsoft....
>
> Thanks
> Steven
>
______________________________________________
Renovamos el Correo Yahoo!: ¡250 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
Someway i can not avoid thinking this looks like the
milk jug tale, you have 0 income at the moment, and is
much improbable you will get a stable income till the
OS is quite more mature, so why worry with payings?
If you get some money, probably not much at the
moment, you could use for hardware upgrades in the
server if needed, hosting and expo attendance (and in
the last point i would encourage people to share
resources as places to stay where the expo takes place
if someone lives there, attendance of people near to
that world area). I really doubt that 30$ bounty will
atract new developers to implement a feature.
Also i have to point you need a way to get that
income, best from private donations, i sugest
implementing two ways:
- Send a check or paper money to a Fisical Mail
Direction.
- Using PayPal and credicards.
-Direct bank transference.
>From the three i would use the first :) ...i am
quite paranoid with credit cards and the transference
expenses would cost more than the transference.
Best regards,
Lucio Diaz.
PD: If someday you want to make a ReactOS conference
in a paradise island, e-mail me...
______________________________________________
Renovamos el Correo Yahoo!: ¡250 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
--- Jonathan Wilson <jonwil(a)tpgi.com.au> wrote:
> The way to avoid being sued by microsoft (or at least sucessfully sued) is
> not to violate microsoft Copyrights, Trademarks or Patents. (we have to be
> especially carefull what with large chunks of windows out there in the form
> of the leaked NT4 and 2000 source dumps)
> And not to use any information obtained from microsoft under NDA.
Try writting a hello world program in any sort of modern language and you might violate a patent.
Thanks
Steven
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
I don't see how this is even possible considering that IntCreateDevice
sets various members of DriverObject... any ideas?
Assertion DriverObject failed at io/irp.c:198
Frames:
ntoskrnl: io/irp.c:200 IofCallDriver
win32k: eng/device.c:62 EngDeviceIoControl
framebuf.dll: surface.c:49 DrvEnableSurface
win32k: objects/dc.c:663 IntCreatePrimarySurface
win32k: ntuser/winsta.c:351 IntInitializeDesktopGraphics
win32k: ntuser/guicheck.c:57 AddGuiApp
win32k: ntuser/guicheck.c:92 IntGraphicsCheck
win32k: objects/dc.c:748 IntGdiCreateDC
win32k: ntuser/windc.c:135 DceAllocDCE
win32k: ntuser/windc.c:494 NtUserGetDCEx
win32k: ntuser/windc.c:115 NtUserGetDC
ntoskrnl: KiSystemService
user32: windows/dc.c:44 GetDC()
Hi all,
Just thought I would post a few screens. The installer for AIM runs
up until the point that it actually copies files, at which point it
gracefully crashes and exits. Probably not too much more work to get it
working :-) .
Regards,
Nate DeSimone
I downloaded the mingw gcc 3.4.2 from mingw.org and it seems that it's
specs/linker script is messed up. By default g++ should link to
libstdc++.a shouldn't it? Well this thing isn't. Now I don't really
understand how the gcc specs file works, but I think that is where it
should be telling g++ to link to libstdc++.a, so if anyone else has any
idea how that file works and might point out where I need to add the
command to link in libstdc++.a, I'd appreciate it.
Hi,
Just to let everyone know we are now approved to be a 501c3 org in the United States meaning that
we can give a tax deduction for any contributions received for donations to the Foundation. I am
in process of trying to get my paperwork together now to come up with a plan to move forward as I
have never done this before and its been a learning process. Sorry its taken so damn long......
I would like to propose that we get something up rather quickly on foundation.reactos.org and
review/amend the draft bylaws as needed as well as have our first real meeting after Jason and I
have discussed off list drafting a new budget plan for the following expenses.
Bounty System
Retainer for Legal and Accounting
Supplementation of Hosting Costs
Administrative Assistant
Reserve Fund
Just to give you a idea I am wanting to budget whatever income we might have in the following way
80% developers/bounties
5% reserve fund (Mutual Funds, Savings, Etc)
5% legal reserve and retainer costs
5% supplement hosting and misc expenses (expos etc)
5% part-to-full time administrative assistant to help me manage paper work as I suck at it.
Prior board meetings mainly consisted of me telephoning each board member upon the initial
incorporation and we have not really moved forward since that time. Now that we are all nice and
legal its time to hit the ground running. Currently our board of directors consists of long time
developers to ReactOS and Wine
Steven Edwards, Jason Filby, Alexandre Julliard, Brian Palmer and Rex Jolliff.
I would like to get community feedback as part of our bylaw amending process on the current status
of the board and when/if we should hold elections and restructure. Also from people that agreed to
be on the board. Do you still want to do it? Does anyone else? Etc....
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
Hi,
--- ea <ea(a)iol.it> wrote:
> first of all, thank you for all the time you spent on the Foundation thing.
> This is and has always been a big issue (or big fear?): how is this
> handled on the Wine side? The only rational reason for a lawsuit is
> Microsft suspects ROS has some stolen code in it that belongs to them
> (see SCO versus Linux). We must therefore be sure our code is clean.
> There could be some funds for paying a code analysis performed by a
> third party (of course we can not ask a MS coder nor a ROS coder to look
> at their code and at ours and say if they differ).
Well so far one thing that has helped is the fact that there is no central authority that owns the
code. Jason and I discussed this when we wanted to create the foundation and it was decided that
if someone wants to turn code over to the foundation they can however in any case we will work to
provide legal defence. Another thing Wine and ReactOS has going for them is the new Software
Freedom law center http://www.softwarefreedom.org/. They are helping out with the Wine project so
we get some level of protection from the amount of code we share with Wine. The real issue comes
in on the kernel and driver side.
I need to email them and discuss a working relationship with the foundation. That is soon on my
todo list.
Thanks
Steven
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
Hi James,
--- James Tabor <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net> wrote:
> Paying developers? Hum?
>
> I don't want to be the bad guy here, but this could push people away from the project. It would
> be
> like going back to five years ago when ROS had no GUI just a command console. Everyone will wait
> for five or so developers to fix things, and trust me it does happen that way in the real world.
> The back log will kick their asses.
See the other thread. I don't think paying developers as full time workers is a good idea. I think
Contracts or bounties on certain projects are.
> Now I have to ask, where does the money come from? If the ORG has no money, I guess it should
> produce a competing distribution CD. This could make M$ happy, so M$ would have a target to
> sue at. Also everyone on the board would become a target as well.
I was wrong in the other email. I forgot we have $25 in the general fund atm which was raised at
LinuxWorld. I expect we can make quite a bit selling CDs, T-Shirts, Etc, if we want as well as
just accepting donations. As for the fear of lawsuit, the idea behind the foundation was that it
was better the foundation get sued and try to have some cash for legal defence rather than some
poor developer in school. Everybody here knows the risk from Microsoft....
Thanks
Steven
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
--- Royce Mitchell III <royce3(a)ev1.net> wrote:
> I think it's important to draw a clear line as to the responsibilities
> of the board as opposed to things that should be decided by all
> commiters ( vs things that the community at large should be invited into ).
I agree. As far as I see it the board should just control the books and thats about it.
> Basically there would be two types of bounties:
>
> 1) "Directed" bounties: If someone donates money towards the completion
> of a purpose, the money must be made available for that purpose.
>
> 2) "General Funds" bounties: These are bounties created from the budget
> above. The way I propose this should work is as follows: Anyone with
> commit access can "propose" a bounty. The board would be responsible for
> reviewing the bounty, and if it looks good to them ( possibly amending
> it some ), they would submit it to the body of commiters for approval.
> Obviously the board would be responsible for reigning in the bounties
> from going over budget.
Thats roughly the idea though you have put it in to much better words then I could have.
> I would like to be involved in the by-law development process, or at
> least be able to review them and give some feedback. I would be willing
> to serve on the board, if I'm wanted.
Join the foundation list and we can move forward with a real plan this time.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
--- Alex Ionescu <ionucu(a)videotron.ca> wrote:
> Two issues I see here:
>
> 1) Developers. Do you mean that each developer will be paid? How will
> this be done? equally shared? Not to sound like an ass, but there may be
> times when a developer does absolutely nothing (read: me for the next
> month), while someone else is hacking away 100KLOC of code. Or someone
> that generally only does little fixes (which can be really useful, and
> is all the useful time he can offer due to work/family/school) versus
> someone which already has assured income and spends 24 hours a day
> working on Reactos. Would it be fair to pay everyone the same amount of
> money? Sorry if I'm misunderstanding the issue, but I just want to be
> fair. Besides, I'm sure many developers might want to refuse getting
> paid. Working for free is sometimes a personal choice, and the offers
> certain tangible and psycoligcal advantages. I don't know about others,
> but I myself would feel bad in many ways to receive money by working on
> ReactOS. I would feel as if any bugs ormistakes that I make now have
> monetary losses associated with them.
The idea is to start with the ReactOS Foundation does two things in terms of paying developers.
1. Offers bounties for certain features or bugs in bugzilla. Call them 1 time cash prizes.
2. Acts as a escrow or broker for third parties wanting to offer a bounty. (see 1)
I don't think this will discourage development. There are tons of little features I would like to
see that no one is working on atm where a bounty system would be nice. If I had $500 spare I would
put up a bounty for the 3com driver or for the NMake backend for the xmlbuildsystem. Also single
user contributions could be pooled for a bug. NOTE: I DO NOT WANT A PLEDGE SYSTEM. THEY DON'T
WORK.
IF YOU REALLY WANT TO CONTRIBUTE MONEY TO A BUG THEN THIS WILL BE THE BEST WAY!
Think about the following
-------------------------------------------
Steven Edwards Enters bug #311337
"Make ReactOS have a 3com Vortext (959/930) driver"
Alex gives $50 earmarked bug #311337
Steven gives $100 to bug #311337
Some random user throws in $200 for bug #311337
Someone decides "hey $350 will pay for a nice weekend at the beach! I'll take it!"
And they start coding. They get a working driver and it passes QA so it goes in SVN.
The ReactOS Foundation then writes a check for $350 to said developer.
-------------------------------------------
> 2) I think expos should get more then 5%. An expo of 4 people would cost
> around 2000$ (assuming 150$/night * 3 nights, plus food and other needs,
> *4 people). Now at minimum we'll probably want to attend a North
> American and a European conference, meaning 4000$. The European one is
> bound to have more then 4 people anyways, so with 6 people, it'll up the
> cost to 6000$. 5% means that we would need 80 000$ in donations. Seems a
> lot to me at this stage. Then again, we probably won't want to pay the
> full cost of an expo at this point, but whatever, I'm just giving ideas
> and I hope they help!
Nothing is set in stone as we have $0 cash flow atm. It will be up to the board to decide on a
final budget. I just want to have a rough plan in place as I am going to start soliciting help for
funding.
> I would love to be on the board. I think I have some pretty good ideas
> for moving forward, and it'll be a good short break from coding when
> I'll happen.
I want to get something up on foundation.reactos.org and then have a discussion on the
ros-foundation list on what needs to be ammended in the bylaws and we can vote on restructure,
memebers, etc.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
Hi all,
Buiding Reactos on a Win98 machine does noy work anymore ( at least for
me) . It was working several ago.
The make clean fails as well with these error messages :
-----------------------------
netstat: [CLEAN]
ping: [CLEAN]
route: [CLEAN]
telnet: [CLEAN]
whois: [CLEAN]
regtests: [CLEAN]
tshared: [CLEAN]
RM] /include/roscfg.h
trop de paramètres - buildno.exe
==== Too many parameters
fichier introuvable
=== File not found
trop de paramètres - wine2ros.exe
trop de paramètres - winebuild.exe
trop de paramètres - bin2res.exe
wpp: [CLEAN]
unicode: [CLEAN]
C:\Svn\reactos>mingw32-make
--------------------------------
Anybody may confirm ?
Thanks
Gerard
Then this is a make.exe bug, which should use %COMSPEC%...
--- Hartmut Birr <hartmut.birr(a)gmx.de> wrote:
> The windows 98 problem has nothing to do with a bug in binutils.
> Make.exe uses cmd to process all pipe commands on windows, but windows
> 98 doesn't have a cmd program. You should copy command.com to cmd.com or
> cmd.exe.
>
> - Hartmut
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
Hi!
This was not unexpected. I noticed last night csrss was over 11000K bytes in size.
The memory leak in csrss is handles, some of them do not close. So the number goes
from ~80 to 2000+ after two days of building ros over and over. You can try to close
the windows but the handle count is the same so~~~~~.
Thanks,
James
(KERNEL32:mem/global.c:412) Memory Load: 59
(KERNEL32:mem/global.c:412) Memory Load: 59
(mm/npool.c:1626) Trying to allocate 16 bytes from nonpaged pool - nothing suita
ble found, returning NULL
KeBugCheck at mm/rmap.c:382
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
The bug code is undefined. Please use an existing code instead.
Technical information:
*** STOP: 0x00000000 (0x00000000,0x00000000,0x00000000,0x00000000)
Frames:
<ntoskrnl.exe:dbe3 (ke/bug.c:459 (KeBugCheckEx))>
<ntoskrnl.exe:dc03 (ke/bug.c:479 (KeBugCheck))>
<ntoskrnl.exe:87911 (mm/rmap.c:382 (MmInsertRmap))>
<ntoskrnl.exe:740aa (mm/anonmem.c:385 (MmNotPresentFaultVirtualMemory))>
<ntoskrnl.exe:7e8f8 (mm/mm.c:387 (MmNotPresentFault))>
<ntoskrnl.exe:befc (mm/i386/pfault.c:66 (MmPageFault))>
<ntoskrnl.exe:1927 (ke/i386/exp.c:543 (KiTrapHandler))>
<ntoskrnl.exe:399d (/tmp/ccc7YZmh.s:235 (KiTrapProlog))>
<ntdll.dll:24118 (/tmp/ccuotceE.s:35 (memset))>
Entered debugger on embedded INT3 at 0x0008:0x800064be.
kdb:>
Lock up no keyboard!
royce(a)svn.reactos.com wrote:
>patch by kjk::hyperion, fix syntax of gcc inline asm
>
>
>Updated files:
>trunk/reactos/hal/halx86/include/hal.h
>
>
This is not acceptable solution IMHO...there are problems with certain
GCC versions assigning AMD64 registers on i386. See revision 13587 and
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10153.
- Filip
essentially, I've tracked down the problem to SerialPnpStartDevice()
being called with ResourceList == NULL.
Here's the details, if ya want 'em:
serial.sys
exception not handled
stop 1e ( c0000005, 9d2f9019, 0, 0 )
serial.sys address 9d2f9019 base 9d2f6000
page fault 14(0)
cs:eip 8:9d2f9019 <serial.sys: 3019> pnp.c:168
cr2 0 cr3 27000 proc: 8084ad00 Pid: 4 <System> Thrd: 8084b828 Tid: 0
DS,ES,GS=10 FS=30
eax 808a7660
ebx 0
ecx 808a7580
edx 808a7828
ebp 800bc9b4
esi 808a77b8
esp 800be808
edi 0
eflags 00210292
kesp 800be808
kernel stack base 800bd000
frames:
<serial.sys: 352b> pnp.c:341, SerialPnP() calling SerialPnpStartDevice()
<ntoskrnl.exe: 329c5> io/irp.c:212, IofCallDriver() calling indirect
<ntoskrnl.exe: 329e1> io/irp.c:226, IoCallDriver() calling IofCallDriver()
<ntoskrnl.exe: 34975> io/pnpmgr.c:665, IopInitiatePnpIrp() calling
IoCallDriver()
<ntoskrnl.exe: 2d151> io/device.c:78, IopInitializeDevice() calling
IopInitiatePnpIrp()
<ntoskrnl.exe: 2fa9d> io/driver.c:1890, NtLoadDriver() calling
IopInitializeDevice()
<ntoskrnl.exe: 318b> ke/i386/syscall.S:178
<ntoskrnl.exe: 2536d> ex/zw.S:771, ZwLoadDriver()
<ntoskrnl.exe: 2efa1> io/driver.c:1378, IopInitializeSystemDrivers()
calling IopLoadDriver()
<8007cc61> ??? only possibility is: IoInit3() calling
IopInitializeSystemDrivers()
<8007d7ac> ??? only possibility is: ExpInitializeExecutive() calling
IoInit3()
<ntoskrnl.exe: d04c> ke/main.c:104, KiSystemStartup() calling
ExpInitializeExecutive()
<80079290> ke/main.c:283, _main() calling KiSystemStartup();
<ntoskrnl.exe: 104b> ke/i386/main.S:51
now, serial.sym:
13019: 8b 07 mov (%edi),%eax
C:\cvs\reactos\drivers\dd\serial>addr2line -e serial.nostrip.sys 13019
C:/cvs/reactos/drivers/dd/serial/pnp.c:168
C:/cvs/reactos/drivers/dd/serial/pnp.c:168:
for (i = 0; i < ResourceList->Count; i++)
notice edi is NULL, which is holding the value of ResourceList, which
traces it's origin back to:
IoGetCurrentIrpStackLocation(Irp)->Parameters.StartDevice.AllocatedResources
which in turn comes from:
DeviceNode->BootResources at ntoskrnl/io/device.c:68 in
IopInitializeDevice()
there's a FIXME on the line above:
/* FIXME: Should be DeviceNode->ResourceList */
hpoussin, or anybody else? should serial.sys handle a NULL ResourceList
gracefully ( imho it should probably have some SEH in there ), or is it
a bug for it to be getting a NULL ResourceList?
Hi,
--- Robert K�pferl <rob(a)koepferl.de> wrote:
> it might seem stupid or girlish, but I want to invite any of you to
> visit me in Vienna (wien.AT) for a couple of days. I would like to just
> see some of these people (and of course have freeky kernel talks) who
> make up this project. Get to know personally. Don't be shy and have a
> try with my private email. (possibly use gpg/x.509).
> If you think this Vienna is too far away - maybe next year I live less
> far away from you.
Some of us will be meeting at WineConf at the end of the month.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
Hi!
hbirr(a)svn.reactos.com wrote:
> Initialize the maximum length of the device description to allocate more than map register.
>
>
>
> Updated files:
> trunk/reactos/drivers/storage/floppy/floppy.c
>
Does this fix floppy support? I haven't had floppy working for 6+ months!
ha! floppy working!
James
hbirr(a)svn.reactos.com wrote:
> - Use IoBuildAsynchronousFsdRequest instead IoBuildSynchronousFsdRequest in NtRead/WriteFile.
> - Guard the calls to IoBuildAsynchronousFsdRequest with an exception frame.
>
> Modified: trunk/reactos/ntoskrnl/io/rw.c
I dont understand these changes... Why did you change from sync. to
asycn. version, and whats the point with try/except around
IoBuildAsynchronousFsdRequest???
Gunnar
http://reactos.com:8080/archives/public/ros-svn/2005-April/002066.html
or run
"ARCH=i386 make bootcd"
--- ea <ea(a)iol.it> wrote:
> Hi all,
>
> I can't build the bootable cd image.
> Is it just my local repository broken (14488)?
>
> ---
> 3: directory ./../bootcd/disk\reactos\system32\
> 3: file ./../bootcd/disk\reactos\system32\ntdll.dll
> 3: file ./../bootcd/disk\reactos\system32\smss.exe
> Can't open ./../bootcd/disk/../isoboot.bin
>
> make: *** [bootcd_makecd] Error 1
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
>
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
Hi all,
I can't build the bootable cd image.
Is it just my local repository broken (14488)?
---
3: directory ./../bootcd/disk\reactos\system32\
3: file ./../bootcd/disk\reactos\system32\ntdll.dll
3: file ./../bootcd/disk\reactos\system32\smss.exe
Can't open ./../bootcd/disk/../isoboot.bin
make: *** [bootcd_makecd] Error 1
Hi Robert:
Yes 7Zip compresses sometimes (most of the times) more than WinRAR. In fact as far as I know they both use the same algorithm for text compression. 7Zip has 3 compression algorithms so you could try all and see for yourself. It also supports streams so you can compress things from the output of one of the algorithms and make it the input of the other. For example to compress executables you could use jcc and it´s output pass it to LZMA. It also provides larger dictionaries if you want. WinRAR´s maximun size is 4 MB so usually WinRaR files are larger. When it comes about speed WinRAR is faster. But I guess that´s irrelevant right now. On the other side I think that sourceforge someday should be enhanced to give users the option to download the files in the selected format, maybe providing a link to the decompressor. Maybe I fill someday the feature request form for sourceforge It will save us and maybe will save them some time.
Best Regards
Waldo
________________________________
From: ros-dev-bounces(a)reactos.com on behalf of Robert Köpferl
Sent: Sun 4/3/2005 5:08 PM
To: ReactOS Development List
Subject: Re: [ros-dev] Ros 0.2.6-RC2 on sf.net
Having read your comments, I came to this conclusion:
I'll have a try with 7zip and if it compresses slightly less or better
than rar, I'll use 7zip (because it is free). For a test period I'll
provide both, zip and 7zip/rar and the user may decide which one will
win. Additionally I'll provide a file 'how to decompress.txt' in every
release. Wheras I think, people who come to download an OS know enough
to find one theirselves. Making exe-files is still an option but I
don't like it. So you have to convince me.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev
Hi,
it might seem stupid or girlish, but I want to invite any of you to
visit me in Vienna (wien.AT) for a couple of days. I would like to just
see some of these people (and of course have freeky kernel talks) who
make up this project. Get to know personally. Don't be shy and have a
try with my private email. (possibly use gpg/x.509).
If you think this Vienna is too far away - maybe next year I live less
far away from you.
With svn 14668 , Ros bugchecks when I click on the "my computer " icon
and o then on the "C" disk drive icon as per debug messages below.
This is a regression and it is always reproductible .
I cannot say exactly when it has been broken.
Any idea ?
-----------------------------
PM_OPEN_WINDOW: path=C:\
KeBugCheckWithTf at ke/catch.c:237
A problem has been detected and ReactOS has been shut down to prevent
damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
KMODE_EXCEPTION_NOT_HANDLED
Technical information:
*** STOP: 0x0000001E (0xc0000005,0x8004773e,0x00000000,0x00000006)
*** ntoskrnl.exe - Address 0x8004773e base at 0x80000000, DateStamp 0x0
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:8004773e <ntoskrnl.exe:4773e (io/mdl.c:130
(IoFreeMdl))>
cr2 6 cr3 d896000 Proc: 80d46990 Pid: f0 <explorer> Thrd: 80d50a68 Tid: f4
DS 10 ES 10 FS 30 GS 23
EAX: 00000000 EBX: 8004635f ECX: 00000003
EDX: 00000002 EBP: a1f76a88 ESI: 007ecdd8 ESP: a1f769d8
EDI: a1f76d74 EFLAGS: 00010282 kESP a1f769d8 kernel stack base a1f74000
Frames:
<ntoskrnl.exe:3c7d0 (io/cleanup.c:112 (IoReadWriteCompletion))>
<ntoskrnl.exe:3c8e0 (io/cleanup.c:211 (IoSecondStageCompletion))>
<ntoskrnl.exe:4694d (io/irp.c:498 (IofCompleteRequest))>
<vfatfs.sys:c65c (rw.c:775 (VfatRead))>
<vfatfs.sys:dcc9 (misc.c:110 (VfatDispatchRequest))>
<vfatfs.sys:de94 (misc.c:168 (VfatBuildRequest))>
<ntoskrnl.exe:4627d (io/irp.c:211 (IofCallDriver))>
<ntoskrnl.exe:46293 (io/irp.c:226 (IoCallDriver))>
<ntoskrnl.exe:4e6b0 (io/rw.c:154 (NtReadFile))>
<ntoskrnl.exe:38f2 (C:\DOCUME~1\home\LOCALS~1\Temp/ccucbaaa.s:178
(KiSystemService))>
<kernel32.dll:278f6 (file/rw.c:154 (ReadFile))>
Reaards
Gerard
Hi,
--- Phillip Susi <psusi(a)cfl.rr.com> wrote:
> Are you talking about being able to create usable ram disks at runtime
> and use them for general file storage instead of holding the system
> volume? I don't really see any use for ram disks other than holding the
> system volume so the media used to boot the system can be removed.
Yes thats the idea. We tend to get requests for one every so often though I don't know what people
use them for. There is a example driver with source code on support.microsoft.com that I always
point people to.
Thanks
Steven
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
--- Phillip Susi <psusi(a)cfl.rr.com> wrote:
> I seem to remember you added a special multiboot header to the kernel
> image but it looks to me like ntoskrnl.exe has a standard PE image header.
Alex changed this. ntoskrnl now is PE loaded from freeldr. I think it was needed for dynamic ACPI
and 3GB support.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
hbirr(a)svn.reactos.com wrote:
>- Fixed ExTimerRundown.
>
>
Hi,
Can you please explain some of your changes? You have introduced several
changes that I don't understand, such as cancelling the timer's APC
without actually making sure that it has an APC associated, as well as
slowing down the path and forcing additionnal locking of the DB lock by
using KeCancelTimer (which also uselessly checks if the timer is
inserted -- we are sure it already is).
Apart from that, thanks for fixing the silly bugs!
Best regards,
Alex Ionescu
Hey Brian, I've been having all kinds of weird problems getting
freeloader installed and working in a boot drive image for qemu. I seem
to remember you used to have to build it with djgpp instead of mingw for
some odd reason. I think it had something to do with mingw's ld
clobbering something up when you asked it to output a binary flat file
instead of a PE image. Is this still the case? Was that issue never
resolved?
Hello,
--- ea(a)svn.reactos.com wrote:
> Updated files:
> trunk/reactos/lib/wintrust/wintrust.def
Tappak if you are watching can you relicense wintrust as BSD v2 or LGPL/GPL? If not it will have
to be removed from SVN as it has a BSD 1 license header which is GPL incompatible. Same thing with
the wintrust.h
Thanks
Steven
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
sedwards(a)svn.reactos.com wrote:
>__USE_W32API
>
>
>Added files:
>trunk/reactos/lib/msgina/makefile
>
>Updated files:
>trunk/reactos/lib/msgina/msgina.c
>trunk/reactos/lib/msgina/stubs.c
>
>Deleted files:
>trunk/reactos/lib/msgina/Makefile
>
>
This library should probably be moved to reactos/subsys because it is
loaded exclusively by winlogon.
It seems that Longhorn drops the GINA. Is it confirmed? Is it due to a
broken (=insecure) design that can not be fixed? If so, should we spend
time implementing GINA?
Emanuele
mingw32-linux is not setting ARCH=i386,
this breaks make bootcd for it.
(although there is an easy workaround)
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
--- Richard Campbell <eek2121(a)comcast.net> wrote:
> *faints*
*grabs the smellinbg salts for Richard and waves hi to Phillip.
Phillip, welcome back! I was looking at some of your code a while back (RAM Disk Driver) and was
wondering if we should add support to it to be a general purpose RAM driver while keeping suppport
for loading from bochs images as it does now.
Thanks
Steven
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
Hi,
it seems we have now a file en.rc and En.rc. This will not work on windows.
- Hartmut
weiden(a)svn.reactos.com wrote:
>corrected file name so it matches the include in slayer.rc
>
>
>Added files:
>trunk/reactos/lib/shellext/slayer/En.rc
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
>
On Mar 30, 2005 12:49 PM, James Dodd <admin(a)doddnetwork.co.uk> wrote:
> I think people are right with the about page.
The whitepaper and FAQ will answer more than enough. The entire first
set of links at the top links to various 'about' topics.
> I've also moved the language bar to the top of the screen...
That I like.
> Even these companies are moving away from this and creating a more user
> friendly approach to their sites which intern represents their OS.
Yes, those *companies*. Apache.org seems to be doing fine with their
minimalist design.
> The new site at the moment does seem more appropriate to developers as
> apposed to attracting new audiences.
What new audiences? Developers are really what is most important to
this project right now. I'm going to stop short of chanting
"developers! developers! developers!" ;)
Cheers
Jason
Hi all
Jh sent me a better look: http://reactos.com/newsite/reactos_index.html
I think it looks better!
I've also reworded our slogan at the top to read what Steven suggested.
Magnus: I'm sorry but your critism is not constructive! Which links do
you want on the frontpage that aren't already there? You cannot link
to everything on the frontpage either!
Cheers
Jason
And needs an SVN account ;)
I'm glad to see everyone kept the project going without me, I am
impressed with the progress!
Hopefully now I can get back to contributing.
--- Robert K�pferl <rob(a)koepferl.de> wrote:
> I can think of an infrasturcture where one could update a list and
> gather packageinformation from all over the internet and install random
> apps hosted by theirs creators or sf.net
Yeah thats kinda my thinking. We maintain a database of all of the free Win32 software on
SourceForge and try to get them all to use MSI or NSIS to package them.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Sports - Sign up for Fantasy Baseball.
http://baseball.fantasysports.yahoo.com/
Hi,
--- Maarten Bosma <maarten.paul(a)bosma.de> wrote:
> As you might remember firk85 and me have started coding a package
> manager for ReactOS. More information and a download linkcan be found on
> the wiki on http://wiki.reactos.com/PackageManager .
>
> Since it is now so far that it is at least a bit useful, I'd like to ask
> what you think of adding it to the svn-tree ?
MSI already does everything you want to do. Add support for loading MSI packages by developing
your application on Windows and then it should work in ReactOS as we share msi.dll and msiexec
with wine. Vendors can already use Wix to package thier applications. For bonus points make it tie
in nicely with NSIS.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
Hi,
--- Maarten Bosma <maarten.paul(a)bosma.de> wrote:
> I missed to introduce a concept of the package manager here. Packages
> are not a Archive file with an instruction for installing like apt
> packages. The more an instruction to download the program, that might be
> running the setup with a special parameter or downloading an arrive
> file with the binaries. That is a little bit of BSD ports or Gentoo Emerge.
>
> This is why I think MSI files aren't the right think to replace the
> basic based scripts, that are used at the moment. It simply not what
> they have been made for. But if the vendor of the application provides a
> msi file of cause it can be used; with a "msi"-script-command.
I think the idea of a central repository containting information on Free(Open) Win32 is a good
idea.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
Hi,
--- Jonathan Wilson <jonwil(a)tpgi.com.au> wrote:
> Why not?
> Its perfectly possible to include a CPL program on the same CD or zip file
> as a GPL program as long as they dont directly mix code (IANAL but this is
> what I understand). Linux distributions mix and match code of all different
> licences and get away with it.
Because we have developed this project like Debian or FreeBSD though we have a "Unspoken Social
Contract" GPL incompatible software will not be mixed in the same package or on the same medium as
GPL compatible software. I am perfectly happy to have WiX or any other OSS package shipped with
ReactOS on a Non-Free CD. It does not mean that I view the CPL as Non-Free, far from it, but in
the GPLs current incarnation it has been deamed GPL-incompatible. Maybe the GPL v3 will address
these issues and we can even ship WiX in the same package/cd as ReactOS but I still would rather
not have ReactOS become dependant on code developed by Microsoft as it may make them rethink the
idea of Freeing other packages in the future.
I would rather link, provide downloads to (apart from the main ReactOS package), and ship it on a
"extras" CD.
Thanks
Steven
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
--- Maarten Bosma <maarten.paul(a)bosma.de> wrote:
> If I understood you correctly you said that there is no need for
> developing a compleatly new system, a Packagemanager only had to provide
> a interface for the msi files.
Right, You can interface directly to the MSI database in the registry.
> First of all, I have to say that I don't know much about that msi stuff.
> So my question is how would the msi file and the program communicte ?
> The point with a packagemanager is that you choose to install lots of
> packages and leave your PC alone. So the package manager had to send the
> dessions of the user to the msi file and then the msi file had to do
> it's operations senlitly. And send reports to the package manager from
> time to time. And if something went wrong, it has to send a compleate
> error report.
Well MSI packages have a lot of options, more so than are used by most people. Most people just
write a Install Shield wizard and have the software packaged in a msi but it can do self-repair
and modification and all sorts of cool stuff. Most third partys now ship apps as MSI as its what
Microsoft supports or they use NullSoft Install System so making a easy to use interface to both
of them will win the most support. Its like a mini-sql database so you can even use XML to mess
with it in your Package Manager. If I understand correctly the Microsoft tool for creating MSI
packages "WiX", uses a xml file for input. The only problem is that WiX is CPL and not GPL so we
cannot ship it with ReactOS unless we make it a seperate download.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
NTFS is an important feature of Windows NT, it is one of the most
advanced file systems devised. It contains many security devices that
makes Windows NT secure. It is much more reliable than FAT.
Perhaps instead of waiting for someone to make complete NTFS support
in ReactOS (not that it shouldn't be done), we may make a filesystem
of our own that is designed with NTFS features in mind
(http://linux-ntfs.sf.net/ntfs/), but since we make it we have
complete support for it. I was thinking of the name MUSCLE, a pun of
FAT. I'm not exactly sure if the letter mean anything yet, but they
could be in the future ;)
--
Mike
Hallo,
As you might remember firk85 and me have started coding a package
manager for ReactOS. More information and a download linkcan be found on
the wiki on http://wiki.reactos.com/PackageManager .
Since it is now so far that it is at least a bit useful, I'd like to ask
what you think of adding it to the svn-tree ?
Maarten Bosma
Hello,
After doing some research, I've decided to go ahead and start a port of
ReactOS to Xen. For those in the Xen community not familiar with ReactOS:
it's an open-source (GPL) re-implementation of the Microsoft Windows
NT-based line of operating systems, aiming to provide binary compatibility
for both applications and drivers
(http://www.reactos.com). For those in the ReactOS community not familiar
with Xen: it's an open-source (GPL) virtual machine monitor that supports
execution of multiple guest operating systems with unprecedented levels of
performance and resource isolation
(http://www.cl.cam.ac.uk/Research/SRG/netos/xen/index.html).
Initially I'll focus on getting ReactOS running as a guest OS. This should
benefit ReactOS primarily, since this will make it possible to develop large
parts of ReactOS (everything except for hardware drivers and some low-level
memory management) inside Xen. It will also give ReactOS access to some
hardware not natively supported yet (by using the Linux driver). The benefit
for Xen at this stage would be the development of ReactOS device drivers for
interfacing
with Xen, which could also be used for a Windows XP port. On the longer
term, I see no reason why ReactOS couldn't function as a driver domain. As
driver compatibility improves in ReactOS, this could provide Xen guests
access to hardware for which the manufacturer provides only Windows drivers
(due to Xens nature, not every driver
could be used this way, but I bet a large percentage of the drivers depend
on the kernel to do the really low-level stuff).
All in all, it seems a win-win proposition for both projects. And even more
importantly, I think it's a cool project :-)
I've made a branch in ReactOS svn, svn://svn.reactos.com/branches/xen, for
this port. Of course, the goal is to merge the changes into trunk
eventually. I expect the port to take at least a few months, my initial
feeling is that it should be done by the end of the year (there's lots of
other stuff in ReactOS I want to work on too). The wiki page at
http://wiki.reactos.com/Xen_port will be used to keep track of progress. The
game plan is just start working from the boot code, until a problem is hit.
Fix that problem and continue until the next problem.
Any support and help from the Xen and ReactOS communities are of course
greatly appreciated.
Gé van Geldorp.
I was doing some changes to RtlCreateUserProcess and saw the strage
rotuine SmCreateUserProcess:
http://svn.reactos.com/viewcvs/trunk/reactos/subsys/smss/smapiexec.c?rev=14…
It has several bugs/problems/confusions:
1) RtlDestroyProcessParameters is not called if RtlCreateUserProcess failed.
2) If WaitForIt is TRUE and you specify a timeout, the caller in not
notified if SmCreateUserProcess returned due to timeout. The process
will stay running forever.
3) If TerminateIt is TRUE, handles are closed. This is wrong/confusing.
Closing the handles does not terminate the process (wrong name?).
4) If you dont pass a UserProcessInfo and TerminateIt is FALSE,
it will leak thread/process handles.
5) If you pass UserProcessInfo and TerminateIt is TRUE, the
thread/process handles in UserProcessInfo will be invalid.
etc.etc.
VERY confusing and bug prone:
SmCreateUserProcess is used once in the end of this file and it pass
FALSE for TerminateIt and pass no UserProcessInfo thus the
thread/process handles will never be closed.
I should have fixed it myself if i just understod how this routine is
_supposed_ to work:-D
Regards
Gunnar
Following some discussion with Art Yerkes via email, I've been toying
around with a resource editor and shifted XP's network connection
configuration dialog around:
www.furrybeans.co.uk/stuff/netdlg.jpg
Note that this will not be the final dialog, nor will that exact one be
used - I'm using a resource editor just so I don't have to painstakingly
recreate each control just to see what it looks like. It's just
convenient for laying out a prototype.
Ignore the image at the top left - that was there already.
Compare with XP or 2000's dialog and let me know what improvements you
can think of.
-Andrew
--- Mike Swanson <mikeonthecomputer(a)gmail.com> wrote:
> Hacking an existing *nix filesystem to work on ReactOS just doesn't
> seem right, nor does it seem very practical.
Some of us primarly run Linux and I host mine on ext3 partitions so having the ext2fsd working
under ReactOS helps with the testing and migration path.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
What I strongly suspect happens is this:
1.The themes service is always loaded and running and holds the theme data
(and it contains details of which .msstyles file to use)
2.At some point (either at startup if the changes are global or when an app
loads if the changes are app specific, I cant find where this bit happens
but I suspect the themes service does this) control passes to ordinal 34 in
uxtheme.dll (aka ThemeHooksInstall acording to uxtheme.pdb). This function
calls an undocumented function in user32 called RegisterUserApiHooks (which
appears to be taylor made for uxtheme to do what it needs to do).
The function hooks:
GetScrollInfo
SetScrollInfo
EnableScrollBar
SetWindowRgn
DefWindowProcW
DefWindowProcA
PreWndProc (probobly stuff that happens internally before the window
procedure gets called)
PostWndProc (probobly stuff that happens internally after the window
procedure gets called)
PreDefDlgProc (probobly connected to dialog boxes)
PostDefDlgProc (probobly connected to dialog boxes)
GetSystemMetrics
SystemParametersInfoA
SystemParametersInfoW
DrawFrameControl
DrawCaption
MDIRedrawFrame (probobly related to MDI frame windows)
This is what causes all apps (including non-theme-aware ones) to get themed
non-client areas (window borders etc)
3.Apps that are theme aware have a manifest, load comctl32.dll 6.0 and
probobly have to call InitCommonControlsEx (although I think some of the
code in the dllmain for comctl32.dll 6.0 may also end up calling
InitCommonControlsEx). This causes new versions of the stock classes
(button, list box, edit, combo box etc etc etc) to be created and
registered. A cursory examination of some of these classes shows that they
dont seem to "pull code" from the stock implementation in user32.dll (i.e.
anything they dont themselves handle goes back to DefWindowProc). In
particular, it doesnt appear as though they have any knowledge of the
classes or window procedures contained in user32.dll.
then 4.Apps that need to do something extra call into functions exported by
uxtheme.dll to do whatever they need to do.
user32.dll seems to have no knowledge whatsoever about themeing and
uxtheme. All that user32 has is RegisterUserApiHooks (and the matching
UnregisterUserApiHooks) that uxtheme uses to hook into user32.dll and do stuff.
Exactly how the theme service and theme engine works "under the hood"
doesnt matter.
But for ReactOS and WINE purposes, I suggest we implement the following:
1.A function similar to RegisterUserApiHooks/UnregisterUserApiHooks (either
reverse engineer the MS function or write our own). This will allow uxtheme
to hook into the global drawing for things like window borders without
user32 needing to care about uxtheme and what uxtheme does (just like how
MS hooks into user32 that way)
2.Whatver code is necessary to get the hooks installed right so that all
apps get the "global" theming like on real windows
3.Support to read the manifest and load a new comctl32.dll that would be
like the version 6 from microsoft (and would contain complete theme-aware
implementations of the stock controls just like MS comctl32.dll 6.0 does)
and 4.All the needed uxtheme exports to make stuff run
This would be the same way Microsoft does things.
User32.dll would have no idea whatsoever about uxtheme and theming
All apps would get non-client-area themeing like on windows.
And only theme aware apps would get themed controls etc (the rest would get
"stock" windows controls)
Oh and btw, if this "reverse engineering" is not "clean room" enough for
WINE and ReactOS, let me know and I will stop posting it :)
Alex,
I managed to shave off another comparison in favor of a shift:
int highest_bit ( int i )
{
int ret = 0;
if ( i > 0xffff )
i >>= 16, ret = 16;
if ( i > 0xff )
i >>= 8, ret += 8;
if ( i > 0xf )
i >>= 4, ret += 4;
if ( i > 0x3 )
i >>= 2, ret += 2;
return ret + (i>>1);
}
FWIW, rdtsc reports that compile for speed is 2x as fast as compile for
size.
I've thought about ways to possibly optimize pipeline throughput for
this, but too many of the calculations depend on results of immediately
previous calculations to get any real advantage.
Here's updated micro-code for BSR, if you really think AMD & Intel will
actually do it...
IF r/m = 0
THEN
ZF := 1;
register := UNDEFINED;
ELSE
ZF := 0;
register := 0;
temp := r/m;
IF OperandSize = 32 THEN
IF (temp & 0xFFFF0000) != 0 THEN
temp >>= 16;
register |= 16;
FI;
FI;
IF (temp & 0xFF00) != 0 THEN
temp >>= 8;
register |= 8;
FI;
IF (temp & 0xF0) != 0 THEN
temp >>= 4;
register |= 4;
FI;
IF (temp & 0xC) != 0 THEN
temp >>= 2;
register |= 2;
FI;
register |= (temp>>1);
FI;
Hi all
A new proposed frontpage for reactos.com can be found here:
http://reactos.com/newsite/reactos_index.html
None of the links go anywhere yet. ezPublish will be phased out and
most of the content hosted in a wiki (editable only by people trusted
in the project).
The wiki/forums/blogs would require a bit of a face-lift so as to look similar.
Comments?
Cheers
Jason
In ca. 16 h I will do SVN update again for the build 0.2.6 RC2
So think about, wether your patch should be submittet now or later.
How about your feelings? Will RC2 be == final actually RC2
---------
So this is what I wanted to send yesterday. However my smtp-provider
didn't work as I would have liked to. Thus I'm doing the LABEL now.
__now
--- Eric Kohl <eric.kohl(a)t-online.de> wrote:
> IMHO, adding missing features to WIDL and fixing resulting bugs in
> rpcrt4 is much more important right now. Access to remote machines, new
> transports (tcp, udp, http, etc.) and a dynamic endpoint mapper (aka
> rpcss) is not that important.
Would it be possible to go ahead and port some of the Wine advapi32 SCM code? Its able to install
and run services such as the Windows Installer so that might solve a few problems we are facing
with the Msi service and CoLinux.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Can't that one be transformed to do a Bit Scan Reverse? I guess there are alogorithms for it too. Try near the link I provided. Or try the Angner Fog's optimization manual. If that does not works you could try SuperOptimizer. Is a program that finds algorithms in assembler for some arch (x86 included of course) by means of trying instructions using bruteforce (you can use several computers if you want), usually can be converted back to a HLL. This function is little enought to let superoptimizer work. Find it, is open source software, a little complex and MACROfied piece of code but somehow modifiable to suit your needs.
Best Regards
Waldo Alvarez
________________________________
From: ros-dev-bounces(a)reactos.com on behalf of Royce Mitchell III
Sent: Fri 3/25/2005 4:19 PM
To: ReactOS Development List
Subject: Re: [ros-dev] ping Alex regarding log2() for scheduler
Waldo Alvarez Cañizares wrote:
>but if you are searching a fast BSF replacement...
>
>
Unfortunately we have no need of BSF :(
Is there a similar algo for BSR, which is what we need?
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev
Hi!
Sorry if I sound a little harsh, but I am upset by the fact that i don't
understand what has driven someone to change the style of a file when
adding one line of code from the old (whatever) style to ms style (where
'{' and '}' are on the same line as the if/else keywords - that makes
multiline if/else blocks unreadable to me, I esp. dislike it when the
if-expression is also multiline - like
if (some_very_long_expression_which_does &&
not_fit_onto_a_signle_line) {
...
}
)
I am not sure, but I think it was Alex.
Would you please tell me why you changed the style of the file? I am
pretty much used to the old style, esp. if i have been working on the
file before it's strange for me to see the syntax changed in a way which
i dislike as much as the ms style or whatever it is.
:-/
> > Taking credits for others work is not a nice thing to todo (Thx Alot)..
> > but you made it worse anyway so no hard feelings :-)
> What is it about? Can you point me to time/date/subject you refer to.
Just Wierd that i make one implention of taskmgr their where better than the previous then
some just take some of the work modify it and credit themself.. i where planning of release the
version today with network status and user tab also an vc++ comp. but can see it dont matter.. :-)
> > To talk about something else i start a new projekt called CubeOs
> > and i would like to know if their are any special copyrights in reactos..?
> Just curious: what is the project about?
Its an Reactos Clone did alot of work my self and with some developers not to make a competition
but to make an alternativ with some of my ideas and visions it has allways been my dream... hope
its okay with the reactos team..
By the way thx for your german translation its a littel useless now on reactos but will be very
happy to use it on CubeOS
Greetz Thomas
Hi,
--- Royce Mitchell III <royce3(a)ev1.net> wrote:
> Part of the reason he's bringing this up is because I was asking what
> was necessary to get working before we could dynamically load drivers
> through SCM. I'm working on learning driver development, but want to do
> it in ReactOS.
>
> Anyways, these functions look most necessary...
>
> OpenSCManager
> CreateService
> ControlService
> OpenService
> CloseServiceHandle
> DeleteService
> QueryServiceStatus
> EnumServicesStatus
Yes those are most of the functions I need for CoLinux and the Windows Installer service. Wine has
a good bit of that implemented using a pipe for communitcation but I assume on Windows its all
LPC/RPC to support "net start servicename". Anyway if no one objects I will look at importing the
hackish Wine code and see if I can make it work.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Just Mean that it is not fair when i uploade taskmgr
with alot of bugfixes and translation and then someone
just modify the code and take the credits
but now ill just use my version on my new project on CubeOs so
its okay but cant see why its done..
But thx about the license stuff
Greetz Thomas
Hi all!
Just reporting some strange things with explorer. When Start->Browse Files->Drives->
(E:), this happens;
(KERNEL32:mem/global.c:412) Memory Load: 17
(MSVCRT:io/open.c:103) not valid fd 0, g_fdend 5, fdinfo 7802d2f0, bucket 7802d2
f0, fdflags 0
(MSVCRT:io/open.c:700) _setmode: inval fd (0)
(cm/ntfunc.c:1438) ObReferenceObjectByHandle() failed with status c0000008
(cm/ntfunc.c:1438) ObReferenceObjectByHandle() failed with status c0000008
(cm/ntfunc.c:1438) ObReferenceObjectByHandle() failed with status c0000008
(KERNEL32:mem/global.c:412) Memory Load: 17
(KERNEL32:mem/global.c:412) Memory Load: 17
(MSVCRT:io/open.c:103) not valid fd 0, g_fdend 5, fdinfo 7802d2f0, bucket 7802d2
f0, fdflags 0
(MSVCRT:io/open.c:700) _setmode: inval fd (0)
(shellole.c:237:SHELL32_DllGetClassObject) failed for CLSID=
{645ff040-5081-101b-9f08-00aa002f954e} (unknown)
(shellole.c:167:SHCoCreateInstance) LoadFromShell failed for CLSID=
{645ff040-5081-101b-9f08-00aa002f954e} (unknown)
(shellole.c:237:SHELL32_DllGetClassObject) failed for CLSID=
{645ff040-5081-101b-9f08-00aa002f954e} (unknown)
(shellole.c:167:SHCoCreateInstance) LoadFromShell failed for CLSID=
{645ff040-5081-101b-9f08-00aa002f954e} (unknown)
E_ACCESSDENIED - WIN32 access denied error
Context: ShellFolder::ShellFolder(IShellFolder*, LPCITEMIDLIST)
Location: utility/shellclasses.cpp:280
Context Trace:
- ShellFolder::ShellFolder(IShellFolder*, LPCITEMIDLIST)
- ShellDirectory::read_directory()
- Entry::read_directory_base()
- Entry::smart_scan()
- explorer_main
- WinMain()
- main
mm/mm.c:337
Unhandled exception
Address:
467ae6 C:\ReactOS\explorer.exe
CS:EIP 1b:467ae6
DS 23 ES 23 FS 3b GS 23
EAX: 00000000 EBX: 00a88f58 ECX: 007fe234
EDX: 00a88f28 EBP: 007fe404 ESI: 007ff6ac ESP: 007fe3fc
EDI: 007ff638 EFLAGS: 00010202
Frames:
400000+3aeae C:\ReactOS\explorer.exe
400000+7d49f C:\ReactOS\explorer.exe
400000+13aa5 C:\ReactOS\explorer.exe
400000+bed0 C:\ReactOS\explorer.exe
400000+c467 C:\ReactOS\explorer.exe
400000+295a9 C:\ReactOS\explorer.exe
400000+29262 C:\ReactOS\explorer.exe
400000+3e258 C:\ReactOS\explorer.exe
900000+12a8f C:\ReactOS\system32\user32.dll
900000+13a6e C:\ReactOS\system32\user32.dll
7c900000+9ea2 C:\ReactOS\system32\ntdll.dll
(ntuser/class.c:114) Failed to lookup class atom!
(ntuser/class.c:114) Failed to lookup class atom!
(ntuser/class.c:114) Failed to lookup class atom!
(ntuser/class.c:114) Failed to lookup class atom!
(ntuser/class.c:114) Failed to lookup class atom!
(ntuser/class.c:114) Failed to lookup class atom!
(KERNEL32:mem/global.c:412) Memory Load: 17
(KERNEL32:mem/global.c:412) Memory Load: 17
(cm/registry.c:885) Hive is still in use (hc 18, rc 10623)
(cm/ntfunc.c:2370) CmiDisconnectHive() failed (Status c0000001)
(profile.c:899) RegUnLoadKeyW() failed (Error 31)
ex/power.c:90
Drive E is HD vfat32, D is HD ext2 ( no problem there ), I can select F
and G w/o any problems (Zip Drives)
Just logs out and blue screens when selecting E.
James
frik85(a)svn.reactos.com wrote:
> Remove all hardcode english phrases from the source code and add the phrases to the resource file.
>
>
> Updated files:
> trunk/reactos/subsys/system/taskmgr/De.rc
> trunk/reactos/subsys/system/taskmgr/En.rc
> trunk/reactos/subsys/system/taskmgr/affinity.c
> trunk/reactos/subsys/system/taskmgr/applpage.c
> trunk/reactos/subsys/system/taskmgr/column.c
> trunk/reactos/subsys/system/taskmgr/debug.c
> trunk/reactos/subsys/system/taskmgr/endproc.c
> trunk/reactos/subsys/system/taskmgr/priority.c
> trunk/reactos/subsys/system/taskmgr/resource.h
> trunk/reactos/subsys/system/taskmgr/run.c
> trunk/reactos/subsys/system/taskmgr/taskmgr.c
> trunk/reactos/subsys/system/taskmgr/trayicon.c
>
Hi,
The tabs list only ones and the process list is all zero's. The
columns tags in the process list have no data at all. Everything
else is okay.
James
In ca. 16 h I will do SVN update again for the build 0.2.6 RC2
So think wether your patch should be submittet now or later.
How about your feelings? Will RC2 be == final actually RC2
Please don't do this. shell32 is a component shared with Wine. I'd very much
prefer to get the new icons into Wine. If that's not possible at least
follow the way Wine does things (i.e. ascii-encoding the .ico files in the
.rc), as it will make the job of keeping ReactOS and Wine in sync easier.
Thanks, Gé van Geldorp.
-----Original Message-----
From: ros-diffs-bounces(a)reactos.com [mailto:ros-diffs-bounces@reactos.com]
On Behalf Of greatlrd(a)svn.reactos.com
Sent: Monday, March 28, 2005 18:51
To: ros-diffs(a)reactos.com
Subject: [ros-diffs] [greatlrd] 14366: did foget the icon form mf
did foget the icon form mf
Added: trunk/reactos/lib/shell32/res/folder.ico
Added: trunk/reactos/lib/shell32/res/folder_open.ico
Added: trunk/reactos/lib/shell32/res/mycomputer.ico
Hi,
I would like it if I can build ros outside from the source tree. This
makes it possible to build ros with different configurations from the
same (highly modified) source tree.
- Hartmut
Hi. This is what I've changed:
1. Implement ClearCommError. I din't test it too much, but it should be ok.
I've reveresed WinXP's ClearCommError to ensure that my
implementation is correct :)
2. Correct badly implemented apis. For Example:
ClearCommBreak(HANDLE hFile)
{
BOOL result = FALSE;
DWORD dwBytesReturned;
if (hFile == INVALID_HANDLE_VALUE) {
return FALSE;
}
result = DeviceIoControl(hFile, IOCTL_SERIAL_SET_BREAK_OFF, NULL, 0,
NULL, 0, &dwBytesReturned, NULL);
return TRUE;
}
Check for INVALID_HANDLE_VALUE is not needed here. I removed all these
checks from
everywhere in comm.c. Function will return TRUE even if DeviceIoControl
fails. This is wrong.
Modified functions:
ClearCommBreak, EscapeCommFunction, GetCommMask, GetCommModemStatus
GetCommState, GetCommTimeouts, PurgeComm, SetCommBreak, SetCommMask,
SetCommTimeouts, SetCommState, SetupComm, TransmitCommChar, WaitCommEvent
Hi,
in a documentation I saw that I probably had a bug in the patch for the
serial port type detection. The attached patch should fix the problem.
This comment in this patch also explains what is/was my problem with the
value(s) specified in the documentation.
Regards,
Mark
Index: drivers/dd/serial/legacy.c
===================================================================
--- drivers/dd/serial/legacy.c (revision 14297)
+++ drivers/dd/serial/legacy.c (working copy)
@@ -62,7 +62,11 @@
{
case 0x00:
return Uart16450;
+ case 0x40:
case 0x80:
+ /* Not sure about this but the documentation says that 0x40
+ * indicates an unusable FIFO but my tests only worked
+ * with 0x80 */
return Uart16550;
}
Hi,
in KeRundownThread is an ASSERT statement. What is the reason for that?
ApcDisable is never changed. It is always 1 for mutex objects and always
0 for mutant objects. If a mutant object is on the list, ros does crash.
- Hartmut
Index: ntoskrnl/ke/kthread.c
===================================================================
--- ntoskrnl/ke/kthread.c (revision 14297)
+++ ntoskrnl/ke/kthread.c (working copy)
@@ -360,7 +360,7 @@
/* Get the Mutant */
Mutant = CONTAINING_RECORD(CurrentEntry, KMUTANT, MutantListEntry);
- ASSERT(Mutant->ApcDisable);
+// ASSERT(Mutant->ApcDisable);
--- Jason Filby <jason.filby(a)gmail.com> wrote:
> None of the links go anywhere yet. ezPublish will be phased out and
> most of the content hosted in a wiki (editable only by people trusted
> in the project).
>
> The wiki/forums/blogs would require a bit of a face-lift so as to look similar.
>
> Comments?
I like it except I think the description of what ReactOS is needs to say something like "A effort
to create a FreeSoftware replacement for Microsoft Windows(TM) that is compatbile with existing
hardware and software". It does not violate trademark as we are describing what we do.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
hbirr(a)svn.reactos.com wrote:
>- Guarded the calls to IoSetCancelRoutine with IoAcquireCancelSpinLock/IoReleaseCancelSpinLock.
>- Used a fastmutex as lock for the data queue.
>- Used paged pool for the data buffers.
>- Allowed the server to read (and to wait) on a listening pipe.
>- Implemented the non blocking read operations.
>
>Updated files:
>trunk/reactos/drivers/fs/np/create.c
>trunk/reactos/drivers/fs/np/fsctrl.c
>trunk/reactos/drivers/fs/np/npfs.c
>trunk/reactos/drivers/fs/np/npfs.h
>trunk/reactos/drivers/fs/np/rw.c
>
>
This change seems to break RPC connection reads. I'm currently busy
working on other things so I can't look at the problem. Any help is
appreciated... (little test application attached, source available on
request or in PSDK examples)
- Filip
Hi,
Am I correct in understanding we are going to need a real rpc implementation to correctly support
Plug and Play as well as Services, DCOM and SMB related stuff? I know the Wine DCOM and Service
Code does everything over named pipes on the local system but I assume we want to do things
"properly". Should we look at doing a mingw build of FreeDCE or the DEC-RPC? I am happy to try and
help import any code if it will help.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
--- Filip Navara <xnavara(a)volny.cz> wrote:
> Just to let you know, there's no need to change the wide-character
> string literals. You can use the -fshort-wchar GCC switch to get the
> desired behaviour without touching the sources...
I was under the impression short-wchar could differ depending on the platform and thats why
wide-characters were a no-no in wine. Or is it that only newer gcc's support this option?
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Hi Royce:
int highest_bit ( int i )
{
int ret = 0;
if ( i > 0xffff )
i >>= 16, ret = 16;
if ( i > 0xff )
i >>= 8, ret += 8;
if ( i > 0xf )
i >>= 4, ret += 4;
if ( i > 0x3 )
i >>= 2, ret += 2;
return ret + (i>>1);
}
Guys I think I have one of those optimizations manuals for asm that actually use only one multiplication
by a called ¨magic number¨ to get the first bit set. I actually don´t want to trace this code in my head
but if you are searching a fast BSF replacement... It was tested using brute force for the 2^32 possible values
on the argumment. Maybe you could check the internet for ¨Agner Fog optimization¨. I have a very bad
memory so maybe the name is wrong. This is all the info I can give until
I get home. Ohh well i can do it myself: http://www.df.lth.se/~john_e/gems/gem0039.html It was Harley´s magic number.
so I wasn´t that far.
or you can read it here... I have a c version but I guess you don´t need that :)
----------------------------------------------------------------------------------------------------------
Fast BSF replacement ASM/80386
Macro EMBSF5 emulates the BSF instruction for non-zero argument <------------------------------------ remember to test for this!!!!!!!
This macro utilizes an algorithm published in the news group comp.arch by Robert Harley in 1996. The algorithm converts the general problem of finding the position of the least significant set bit into a special case of counting the number of bits in a contiguous block of set bits. By computing x^(x-1), where x is the original input argument, a right-aligned contiguous group of set bits is created, whose cardinality equals the position of the least significant set bit in the original input plus 1.
The input x is of the form (regular expression): {x}n1{0}m. x-1 has the form {x}n{0}(m+1), and x^(x-1) has the form {0}n{1}(m+1). This step is pretty similar to the one used by macro PREPBSF <http://www.df.lth.se/~john_e/gems/gem002e.html> , only that PREPBSF <http://www.df.lth.se/~john_e/gems/gem002e.html> creates a right-aligned group of set bits whose cardinality equals exactly the position of the least significant set bit.
Harley's algorithm then employs a special method to count the number of bits in the right-aligned contiguous block of set bits. I am not sure upon which number theoretical argument it is founded, and it wasn't explained in the news group post.
According to Harley, if a 32-bit number of the form 00...01...11 is multiplied by the "magic" number (7*255*255*255), then bits <31:26> of the result uniquely identify the number of set bits in that number. A 64 entry table is used to map that unique result to the bit count. Here, I have modified the table to reflect the bit position of the least significant set bit in the original argument, which is one less than the bit count of the intermediate result.
I have tested the macro EMBSF5 exhaustively for all 2^32-1 possible inputs, i.e. for all 32-bit numbers except zero.
Place the following table in the data segment:
table db 0, 0, 0,15, 0, 1,28, 0,16, 0, 0, 0, 2,21,29, 0
db 0, 0,19,17,10, 0,12, 0, 0, 3, 0, 6, 0,22,30, 0
db 14, 0,27, 0, 0, 0,20, 0,18, 9,11, 0, 5, 0, 0,13
db 26, 0, 0, 8, 0, 4, 0,25, 0, 7,24, 0,23, 0,31, 0
And here follows the actual macro:
;
; emulate bsf instruction
;
; input:
; eax = number to preform a bsf on ( != 0 )
;
; output:
; edx = result of bsf operation
;
; destroys:
; ecx
; eflags
;
MACRO EMBSF5
mov edx,eax ; do not disturb original argument
dec edx ; n-1
xor edx,eax ; n^(n-1), now EDX = 00..01..11
IFDEF FASTMUL
imul edx,7*255*255*255 ; multiply by Harley's magic number
ELSE
mov ecx,edx ; do multiply using shift/add method
shl edx,3
sub edx,ecx
mov ecx,edx
shl edx,8
sub edx,ecx
mov ecx,edx
shl edx,8
sub edx,ecx
mov ecx,edx
shl edx,8
sub edx,ecx
ENDIF
shr edx,26 ; extract bits <31:26>
movzx edx,[table+edx] ; translate into bit count - 1
ENDM
Note: FASTMUL can be defined if your CPU has a fast integer multiplicator, like the AMD. The IMUL replacement should run in about 8-9 cycles.
Gem writer: Norbert Juffa <mailto:norbert.juffa@amd.com>
last updated: 1999-09-02
----------------------------------------------------------------------------------------------------------
>> updated micro-code << Wow where I can get this?
Do you have an assembler/disassembler?
I once asked Tigran Aizvian but he told me not to have the information at all.
With that I could save myself some time reversing it by trial and error using the black box approach.
Someday. As far as I know still Intel CPUs microcode updates are not digitally signed
so it could be reprogrammed.
Here's updated micro-code for BSR, if you really think AMD & Intel will
actually do it...
IF r/m = 0
THEN
ZF := 1;
register := UNDEFINED;
ELSE
ZF := 0;
register := 0;
temp := r/m;
IF OperandSize = 32 THEN
IF (temp & 0xFFFF0000) != 0 THEN
temp >>= 16;
register |= 16;
FI;
FI;
IF (temp & 0xFF00) != 0 THEN
temp >>= 8;
register |= 8;
FI;
IF (temp & 0xF0) != 0 THEN
temp >>= 4;
register |= 4;
FI;
IF (temp & 0xC) != 0 THEN
temp >>= 2;
register |= 2;
FI;
register |= (temp>>1);
FI;
In copyright law it's the result that matter, not the process. To be
protected by copyright law, it must be in tangible form. Looking at
disassembled code is permitted by copyright law so it's only a problem
if the person doing it lacks self-discipline and uses the disassembled
code in a way that violates copyright law.
That said, I don't believe there is a need for reverse engineering
methods for implementing the majority of ReactOS and WINE. Our goal
is to run Windows software on ReactOS and other free operating systems.
We have some smart people on these projects. If the Windows software
vendors could figure out how to use the interfaces using the public
available documentation, then we can certainly implement the interfaces
from that same information. If there is an interface that isn't
documented, then certainly most Windows software won't use it
and there is no need to implement the interface at all.
Casper
References:
>From http://www.nus.edu.sg/intro/slides/021111_1_Wilson%20Wong.ppt
What is protectable?
Functionality?
- not protected
- must be an "expression...of a set of instructions"
- Autodesk Inc v Dyason (Aust): copying function of AutoCAD lock but not code (no infringement)
Program Structure?
- (cf: plot elements in literary/dramatic works capable of protection)
- eg. structural arrangements of modules and subroutines
- yes if expression of idea, & no if ideas or functions: difficult line to draw
- yes if organisation, sequence, arrangement or compilation
- not protectable: elements of software which are:
* ideas;
* dictated by efficiency or external factors (eg h/w) specs, compatibility reqms, industry standards; or
* public domain
- not if similarity is due only to similar subject matter
* analogy: drawing of a hand
* eg any 2 word processors will have some structural similarities
> -----Original Message-----
> From: wine-devel-admin(a)winehq.org [mailto:wine-devel-admin@winehq.org] On Behalf Of Mike McCormack
> Sent: 25. marts 2005 10:39
> To: Jonathan Wilson
> Cc: wine-devel(a)winehq.org; ros-dev(a)reactos.com
> Subject: Re: I think I know how uxtheme works...
>
>
> Jonathan Wilson wrote:
> > What I am doing here is clean-room reverse engineering.
>
> There's no reason that we need to expose ourselves to any legal risk at
> all. It may be your opinion that reading assembly code and describing
> it is legal and safe, but I don't agree and I'm sure others who work on
> Wine don't either.
>
> The original IBM BIOS was clean room reverse engineered because there
> was not enough documentation available for it. We have MSDN, which is
> not 100% complete, but is good enough for most purposes. Other things
> can be deduced from test programs. Information that cannot be deduced
> by a test program is irrelevant.
>
> Reverse engineering does not help Wine. Casual observers will assume
> that Wine is the result of reverse engineering by disassembly, which is
> incorrect and harmful.
>
> Mike
gvg(a)svn.reactos.com wrote:
>Build freeldr as elf executable, initial Xen support
>
>Added files:
>...
>
>Updated files:
>...
>branches/xen/reactos/boot/freeldr/freeldr/fs/ntfs.c
>...
>
>
Just to let you know, there's no need to change the wide-character
string literals. You can use the -fshort-wchar GCC switch to get the
desired behaviour without touching the sources...
- Filip
Hi Hartmut,
--- Hartmut Birr <hartmut.birr(a)gmx.de> wrote:
> with my last changes (r14296), coLinux does start and does mount the
> root partition. It exist an second problem. The coLinux window is only
> shown for a very short time. I'm not so familiar with the gdi, user and
> win32k code. I cannot fix the second problem.
Nice! I will svn update, rebuild and test tommrow.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
What I am doing here is clean-room reverse engineering.
Essentially it involves taking existing binary modules and sources of
information and writing up what they do in a way that isnt violating the
copyright on the origonal (IANAL but I dont think what I posted violates
the copyright on the windows binaries).
Then it involves someone else who hasnt seen the origonal copyrighted
source using the resulting information to re-implement whatever the
information describes.
As long as the person who origonally did the reverse engineering never
contributes anything to the resulting code, it is (AFAIK, IAMAL) perfectly
legal (after all, this is exactly what was done when the first clone PC
bios was written, one group disassembled the origonal IBM BIOS and wrote up
documents on how it works and how to talk to it. Then another group not
connected to the people who did the origonal reverse engineering took the
documentation and re-implemented the BIOS from just the documentation
without looking at the orgininal IBM implementation)
I never had any plans to actually write code for this (since doing so is
out of my skill range) and as long as I never do so in the future (thus
"tainting" the code I write as being a potential Derived Work of the
microsoft code I looked at), I dont see any way that the results of this
investigation could be considered a derived work of any microsoft code.
Although if I have a mis-understanding of this situation, please point out
what I am doing that would make code written by someone else using the
information in my posts a Derived Work of microsofts origonal binaries.
Hello,
I'd like to provide a small VS.NET project file with 5 different tests.
- 46ffffe9 tells everything is alright with the function calculation
- times are measured with QueryPerformanceCounter
- loop run cnt: 0x2ffffff
result orig function 46ffffe9
it took 1491052
result orig function inlined 46ffffe9
it took 1035547
result second proposal inlined 46ffffe9
it took 1244434
result optimized asm 46ffffe9
it took 1338367
result debug asm 46ffffe9
it took 8774815
The second proposal is the original proposal but more shifts - still slower
tho.
Interesting is the inlined version generated by MSVC, shaving off almost 1/3
of the overall time.
Also stared as "optimized asm" - no gurantee on register safety tho ;)
For portability and performance sake it should be considered to create a
compiler macro.
This function is terribly small, any optimisations inside are outweighted by
the calling overhead in this case.
The most impressive one is the original function inlined, althought the ASM
would only work on x86.
Please do not think about using 64k tables, thats what, 1/2 of a Sempron L2
cache?
It would really really trash performance.
Available at: <a href="http://hackersquest.org/kerneltest.html"
title="Kernel Test Emulator">Kernel Test</a>
<a
href="http://wohngebaeudeversicherung.einsurance.de/">http://wohngebaeudeversicherung.einsurance.de</a>
Hi
Why not create two diffrent changelog for each release.
one that contain all svn commit msg
next one is what is benefit for the user.
I think this is good idea. ´Then the user
can read what new for them. If some want really
know what we have done. Then they can read all
commit msg. I think this is good idea, and will benfit
alot of people.
I would think that ReactOs is not anywhere near being ready for themeing partially because it needs to write much more of the system software. Themeing can always be an option later. I have mentioned an alternate filesystem, and other services, but since I have not submitted code, people on the mailing list think i can not program something of the sort. I think it is great that people are wanting to understand the process of themeing but keep in mind that loading a theme may cut down on the resources available to the opertating system or may interfere with someone elses environment.
>
> From: Jonathan Wilson <jonwil(a)tpgi.com.au>
> Date: 2005/03/23 Wed PM 09:19:23 EST
> To: wine-devel(a)winehq.org, ros-dev(a)reactos.com
> Subject: [ros-dev] I think I know how uxtheme works...
>
> What I strongly suspect happens is this:
> 1.The themes service is always loaded and running and holds the theme data
> (and it contains details of which .msstyles file to use)
> 2.At some point (either at startup if the changes are global or when an app
> loads if the changes are app specific, I cant find where this bit happens
> but I suspect the themes service does this) control passes to ordinal 34 in
> uxtheme.dll (aka ThemeHooksInstall acording to uxtheme.pdb). This function
> calls an undocumented function in user32 called RegisterUserApiHooks (which
> appears to be taylor made for uxtheme to do what it needs to do).
> The function hooks:
> GetScrollInfo
> SetScrollInfo
> EnableScrollBar
> SetWindowRgn
> DefWindowProcW
> DefWindowProcA
> PreWndProc (probobly stuff that happens internally before the window
> procedure gets called)
> PostWndProc (probobly stuff that happens internally after the window
> procedure gets called)
> PreDefDlgProc (probobly connected to dialog boxes)
> PostDefDlgProc (probobly connected to dialog boxes)
> GetSystemMetrics
> SystemParametersInfoA
> SystemParametersInfoW
> DrawFrameControl
> DrawCaption
> MDIRedrawFrame (probobly related to MDI frame windows)
> This is what causes all apps (including non-theme-aware ones) to get themed
> non-client areas (window borders etc)
> 3.Apps that are theme aware have a manifest, load comctl32.dll 6.0 and
> probobly have to call InitCommonControlsEx (although I think some of the
> code in the dllmain for comctl32.dll 6.0 may also end up calling
> InitCommonControlsEx). This causes new versions of the stock classes
> (button, list box, edit, combo box etc etc etc) to be created and
> registered. A cursory examination of some of these classes shows that they
> dont seem to "pull code" from the stock implementation in user32.dll (i.e.
> anything they dont themselves handle goes back to DefWindowProc). In
> particular, it doesnt appear as though they have any knowledge of the
> classes or window procedures contained in user32.dll.
> then 4.Apps that need to do something extra call into functions exported by
> uxtheme.dll to do whatever they need to do.
>
> user32.dll seems to have no knowledge whatsoever about themeing and
> uxtheme. All that user32 has is RegisterUserApiHooks (and the matching
> UnregisterUserApiHooks) that uxtheme uses to hook into user32.dll and do stuff.
>
> Exactly how the theme service and theme engine works "under the hood"
> doesnt matter.
> But for ReactOS and WINE purposes, I suggest we implement the following:
> 1.A function similar to RegisterUserApiHooks/UnregisterUserApiHooks (either
> reverse engineer the MS function or write our own). This will allow uxtheme
> to hook into the global drawing for things like window borders without
> user32 needing to care about uxtheme and what uxtheme does (just like how
> MS hooks into user32 that way)
> 2.Whatver code is necessary to get the hooks installed right so that all
> apps get the "global" theming like on real windows
> 3.Support to read the manifest and load a new comctl32.dll that would be
> like the version 6 from microsoft (and would contain complete theme-aware
> implementations of the stock controls just like MS comctl32.dll 6.0 does)
> and 4.All the needed uxtheme exports to make stuff run
>
> This would be the same way Microsoft does things.
> User32.dll would have no idea whatsoever about uxtheme and theming
> All apps would get non-client-area themeing like on windows.
> And only theme aware apps would get themed controls etc (the rest would get
> "stock" windows controls)
>
> Oh and btw, if this "reverse engineering" is not "clean room" enough for
> WINE and ReactOS, let me know and I will stop posting it :)
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
>
Hi,
with my last changes (r14296), coLinux does start and does mount the
root partition. It exist an second problem. The coLinux window is only
shown for a very short time. I'm not so familiar with the gdi, user and
win32k code. I cannot fix the second problem.
- Hartmut
On 24-28 of March, between 05:00 and 08:00 CET, svn.reactos.com may be unavailable
for a duration of up to 1 hour each day due to maintenance work at the hosting center.
Sorry for the inconvenience,
Casper
Hi,
--- Boaz Harrosh <boaz(a)hishome.net> wrote:
> How is ReactOS's current (future) system?
I think ReactOS's registry is binary compatible with NT4. It and the windows 2000 format was
documented/reversed for samba and the linux ntchpwd bootdisk projects. If I remeber right Eirc
Kohl offered to release some of his work to Wine for the binary format so you might want to ping
him about the implementation details.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Hi Emanuele,
--- ea <ea(a)iol.it> wrote:
> I tested twice fresh builds before committing and the 3rd time right now
> with local repository at revision 14248. For me it compiles, installs
> and boots correctly (qemu 0.6.1). Can you tell me more about the lock? I
> can't rollback right now because I am going out to work in a few
> seconds. Feel free to restore subsys/csrss and subsys/smss to 14243 if
> you feel this is a blocking bug for you.
Sorry, its not your problem. I rm -fr'd my reactos tree and did a clean CVS checkout and things
are cool now. I guess the current build system left some crap around that caused problems. Nice
work btw on the smss stuff. How much trouble do you think it would be possible to make a native
mode console application in smss like the Windows recovery console? I have been thinking about
doing this for the boot CD for a while but would like to make it more powerful than the Windows
recovery console.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
James Hawkins wrote:
>>Nobody's working on it, so it won't be supported until someone cares
>>enough to do it. I encouraged a few people to start working on it but
>>nobody did, so taking out the existing support is a way to provide
>>more encouragement. If that's not enough then the feature simply won't
>>be supported anymore.
>>
>>
I started toying around the current and old code, Gathering knowledge
and ideas. What I think of doing is:
keep the boot registry as is (more less). Put in on wine/wine/config a
key system that enables a "plugin" system of registry loaders/savers.
Builtin plugins are current format and Windows binary format. Other
formats could be easily implemented; candidates could be XML, MySQL etc...
The system I thought of would also save the hives and sub trees, to the
files/plugins it was loaded from. Each plugin could also implement a
write behind so Data don't get lost in case of a crash or power lost.
Good point with the on demand-loading/cache of keys. It should be done
this way. So in summary:
1. Implement a Memory registry with plugin drivers and mount semantics.
This driver goes here, that driver mounts there.
2. Implement 2 basic drivers: Wine builtin format, Windows binary format.
3. Enable dynamic load of external drivers.
The Initial registry system is always loaded from system.reg builtin
format which is also the "fstab" file of the registry. At minimum every
thing is exactly like now one (two) files builtin format, and that's it.
At the maximum it can be highly object oriented with per user, per
application, per group management.
Please tell me what you think.
Any libraries I should look into?
How is ReactOS's current (future) system?
Free Life
Boaz
Hi,
--- ea(a)svn.reactos.com wrote:
> trunk/reactos/subsys/smss/initss.c
"Debug Windows" fails to be registered causing it to not boot the Win32 subsystem and hard lock.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250
Hi,
I just finished uploading the RC1 to sf.net
The last build worked quite well, but improvements to the branch are
welcome. If no major issues occour, we may perhaps advance to Release as
next step, already.
BTW: RosApps is from 2003, still.
They are already in the installation, aren't they?
So should they be hidden?
Hi,
I am running clean on the trunk and I am getting this error.
[CC] pnp_c.c
pnp_c.c: In function `PNP_GetVersion':
pnp_c.c:72: error: syntax error before '%' token
pnp_c.c:83: warning: use of cast expressions as lvalues is deprecated
make: *** [pnp_c.o] Error 1
My gcc is a cross-compiler 3.3.4
My pnp_c.c has the following at line 72
NdrGetBuffer(
(PMIDL_STUB_MESSAGE)&_StubMsg,
_StubMsg.BufferLength,
%_Handle);
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Hi,
is there a requirement for the serial port IRQ detection? This was also
part of my old sources but currently I simply don't know how to do it
inside the ReactOS serial driver.
BTW: How does the "serenum" stuff works?
Regards,
Mark
--- art yerkes <ayerkes(a)speakeasy.net> wrote:
> We need a convenient way to report a different version on a per application
> basis. I think there's some code to do this but I could not determine
> whether it works (despite several people telling me how to do it). While
> we're at it, can we verify that this code works and post a howto about
> reporting a specific windows version to an application?
I don't know much about it but it is supposed to be possible. There is a app compatiblity shell
extention that Thomas wrote that is supposed to do it under Windows. Anyone know if this really
works under ReactOS?
Thanks
Steven
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
Hi,
I found some old sources from me where I detect the IRQ and the type
(8250, 16450, 16550, 16550A) of a COM port. I converted the type
detection sources to C.
The detection if there is a COM port at all is made by inverting all
bits of the LCR twice. All chips > 8250 have a scratch pad and all
16550A+ have a usable FIFO.
I attached the diff for reactos/drivers/dd/serial/legacy.c.
BTW: I'm sorry about it but my editor always changes TABs to spaces ...
Regards,
Mark
Index: drivers/dd/serial/legacy.c
===================================================================
--- drivers/dd/serial/legacy.c (revision 14202)
+++ drivers/dd/serial/legacy.c (working copy)
@@ -1,72 +1,101 @@
/* $Id:
*
* COPYRIGHT: See COPYING in the top level directory
* PROJECT: ReactOS kernel
* FILE: drivers/bus/serial/legacy.c
* PURPOSE: Legacy serial port enumeration
*
* PROGRAMMERS: Hervé Poussineau (poussine(a)freesurf.fr)
*/
#define NDEBUG
#include "serial.h"
+#define SER_TYPE_NONE 0
+#define SER_TYPE_8250 1
+#define SER_TYPE_16450 2
+#define SER_TYPE_16550 3
+#define SER_TYPE_16550A 4
+
+static BYTE
+DetectPortType(PUCHAR BaseAddress)
+{
+ BYTE Lcr, TestLcr;
+ BYTE OldScr, Scr5A, ScrA5;
+ BOOLEAN FifoEnabled;
+ BYTE NewFifoStatus;
+
+ Lcr = READ_PORT_UCHAR(SER_LCR(BaseAddress));
+ WRITE_PORT_UCHAR(BaseAddress, (BYTE) (Lcr ^ 0xFF));
+ TestLcr = (BYTE) (READ_PORT_UCHAR(SER_LCR(BaseAddress)) ^ 0xFF);
+ WRITE_PORT_UCHAR(BaseAddress, Lcr);
+
+ /* Accessing the LCR must work for a usable serial port */
+ if (TestLcr!=Lcr)
+ return SER_TYPE_NONE;
+
+ /* Ensure that all following accesses are done as required */
+ READ_PORT_UCHAR(SER_RBR(BaseAddress));
+ READ_PORT_UCHAR(SER_IER(BaseAddress));
+ READ_PORT_UCHAR(SER_IIR(BaseAddress));
+ READ_PORT_UCHAR(SER_LCR(BaseAddress));
+ READ_PORT_UCHAR(SER_MCR(BaseAddress));
+ READ_PORT_UCHAR(SER_LSR(BaseAddress));
+ READ_PORT_UCHAR(SER_MSR(BaseAddress));
+ READ_PORT_UCHAR(SER_SCR(BaseAddress));
+
+ /* Test scratch pad */
+ OldScr = READ_PORT_UCHAR(SER_SCR(BaseAddress));
+ WRITE_PORT_UCHAR(SER_SCR(BaseAddress), 0x5A);
+ Scr5A = READ_PORT_UCHAR(SER_SCR(BaseAddress));
+ WRITE_PORT_UCHAR(SER_SCR(BaseAddress), 0xA5);
+ ScrA5 = READ_PORT_UCHAR(SER_SCR(BaseAddress));
+ WRITE_PORT_UCHAR(SER_SCR(BaseAddress), OldScr);
+
+ /* When non-functional, we have a 8250 */
+ if (Scr5A!=0x5A || ScrA5!=0xA5)
+ return SER_TYPE_8250;
+
+ /* Test FIFO type */
+ FifoEnabled = (READ_PORT_UCHAR(SER_IIR(BaseAddress)) & 0x80)!=0;
+ WRITE_PORT_UCHAR(SER_FCR(BaseAddress), SR_FCR_ENABLE_FIFO);
+ NewFifoStatus = READ_PORT_UCHAR(SER_IIR(BaseAddress)) & 0xC0;
+ if (!FifoEnabled)
+ WRITE_PORT_UCHAR(SER_FCR(BaseAddress), 0);
+ switch (NewFifoStatus) {
+ case 0x00:
+ return SER_TYPE_16450;
+ case 0x80:
+ return SER_TYPE_16550;
+ }
+
+ /* FIFO is only functional for 16550A+ */
+ return SER_TYPE_16550A;
+}
+
static BOOLEAN
SerialDoesPortExist(PUCHAR BaseAddress)
{
- BOOLEAN Found;
- BYTE Mcr;
- BYTE Msr;
-
- Found = FALSE;
-
- /* save Modem Control Register (MCR) */
- Mcr = READ_PORT_UCHAR(SER_MCR(BaseAddress));
-
- /* enable loop mode (set Bit 4 of the MCR) */
- WRITE_PORT_UCHAR(SER_MCR(BaseAddress), 0x10);
-
- /* clear all modem output bits */
- WRITE_PORT_UCHAR(SER_MCR(BaseAddress), 0x10);
-
- /* read the Modem Status Register */
- Msr = READ_PORT_UCHAR(SER_MSR(BaseAddress));
-
- /*
- * the upper nibble of the MSR (modem output bits) must be
- * equal to the lower nibble of the MCR (modem input bits)
- */
- if ((Msr & 0xf0) == 0x00)
- {
- /* set all modem output bits */
- WRITE_PORT_UCHAR(SER_MCR(BaseAddress), 0x1f);
-
- /* read the Modem Status Register */
- Msr = READ_PORT_UCHAR(SER_MSR(BaseAddress));
-
- /*
- * the upper nibble of the MSR (modem output bits) must be
- * equal to the lower nibble of the MCR (modem input bits)
- */
- if ((Msr & 0xf0) == 0xf0)
- {
- /*
- * setup a resonable state for the port:
- * enable fifo and clear recieve/transmit buffers
- */
- WRITE_PORT_UCHAR(SER_FCR(BaseAddress),
- (SR_FCR_ENABLE_FIFO | SR_FCR_CLEAR_RCVR | SR_FCR_CLEAR_XMIT));
- WRITE_PORT_UCHAR(SER_FCR(BaseAddress), 0);
- READ_PORT_UCHAR(SER_RBR(BaseAddress));
- WRITE_PORT_UCHAR(SER_IER(BaseAddress), 0);
- Found = TRUE;
- }
- }
-
- /* restore MCR */
- WRITE_PORT_UCHAR(SER_MCR(BaseAddress), Mcr);
-
- return Found;
+ BYTE Type;
+
+ Type = DetectPortType(BaseAddress);
+ if (Type==SER_TYPE_NONE)
+ return FALSE;
+
+ if (Type==SER_TYPE_16550A) {
+ /*
+ * setup a resonable state for the port:
+ * enable fifo and clear recieve/transmit buffers
+ */
+ WRITE_PORT_UCHAR(SER_FCR(BaseAddress),
+ (SR_FCR_ENABLE_FIFO | SR_FCR_CLEAR_RCVR | SR_FCR_CLEAR_XMIT));
+ WRITE_PORT_UCHAR(SER_FCR(BaseAddress), 0);
+ }
+
+ READ_PORT_UCHAR(SER_RBR(BaseAddress));
+ WRITE_PORT_UCHAR(SER_IER(BaseAddress), 0);
+
+ return TRUE;
}
NTSTATUS
Hi,
Most of the dev team seems to be in agreement with bumping the reported version number to Win2k
but if anyone has any objections speak now or forever maintain a patch. I need Win2k to be
reported as the version number as many newer applications such as Office 2003 will not install
unless that is the latest version. If you find any places where a function, resource or anything
reports a value as NT4 or something ReactOS dependant please change it to match Windows 2000
behavior. Also I propose we just report Service Pack 4.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Hi all
Currently when running a BootCD, if I ask to format the partition, I'm
told that the setup could not complete. This is on trunk, not sure
about the 0.2.6 build; can anyone confirm?
Thanks
Jason
This is the text of the final few seconds before the compilation ran out of
steam. The compiler is the standard MinGW32-gcc plus MinGW-g++, etc, in the
MinGW-3.1.0-1.exe package; the computer's a Compaq 4000 Deskpro; the OS is MS
Win95, bog-standard as far as I know.
Wesley Parish
C:/MINGW/include/c++/3.2.3/bits/stl_tree.h:1068: instantiated from
`std::_Rb_t
ree_iterator<_Val, _Val&, _Val*> std::_Rb_tree<_Key, _Val, _KeyOfValue,
_Compare
, _Alloc>::insert_unique(std::_Rb_tree_iterator<_Val, _Val&, _Val*>, const
_Val&
) [with _Key = String, _Val = std::pair<const String, ICON_ID>, _KeyOfValue =
st
d::_Select1st<std::pair<const String, ICON_ID> >, _Compare =
std::less<String>,
_Alloc = std::allocator<std::pair<const String, ICON_ID> >]'
C:/MINGW/include/c++/3.2.3/bits/stl_map.h:262: instantiated from
`std::_Rb_tre
e<_Key, std::pair<const _Key, _Tp>, std::_Select1st<std::pair<const _Key, _Tp>
>
, _Compare, _Alloc>::iterator std::map<_Key, _Tp, _Compare,
_Alloc>::insert(std:
:_Rb_tree<_Key, std::pair<const _Key, _Tp>, std::_Select1st<std::pair<const
_Key
, _Tp> >, _Compare, _Alloc>::iterator, const std::pair<const _Key, _Tp>&)
[with
_Key = String, _Tp = ICON_ID, _Compare = std::less<String>, _Alloc =
std::alloca
tor<std::pair<const String, ICON_ID> >]'
C:/MINGW/include/c++/3.2.3/bits/stl_map.h:225: instantiated from `_Tp&
std::ma
p<_Key, _Tp, _Compare, _Alloc>::operator[](const _Key&) [with _Key = String,
_Tp
= ICON_ID, _Compare = std::less<String>, _Alloc =
std::allocator<std::pair<cons
t String, ICON_ID> >]'
explorer.cpp:398: instantiated from here
C:/MINGW/include/c++/3.2.3/bits/stl_pair.h:88: invalid use of undefined type `
struct String'
utility/utility.h:737: forward declaration of `struct String'
make[1]: *** [explorer.o] Error 1
make: *** [explorer] Error 2
--
Clinersterton beademung, with 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.
same problem here using trunk revision 14208.
tested on qemu using blank and already formated image.
--- Jason Filby <jason.filby(a)gmail.com> wrote:
> Hi all
>
> Currently when running a BootCD, if I ask to format the partition, I'm
> told that the setup could not complete. This is on trunk, not sure
> about the 0.2.6 build; can anyone confirm?
>
> Thanks
> Jason
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
Hi,
I think the affects both the branch and the trunk. At the end of stage 2 setup I get a crash in
ntoskrnl: 319b and 6760c
According to my map.
8006760c <_NtAdjustPrivilegesToken@24+0xbc>
Is called in a few places and 319b is
/* Do the System Call */
call *%eax
80003199: ff d0 call *%eax
movl %eax, KTRAP_FRAME_EAX(%ebp)
8000319b: 89 45 44 mov %eax,0x44(%ebp)
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
.\lib\rtl\largeint.c
There's a sutraction performed in your implementation. But actually it's a
logical negation (asm -> NEG; C -> ~) in this function of the low and high
part:
RtlLargeIntegerNegate()
Oliver
PS: I have no CVS access, so anyone here having it should fix this.
I created bug 585 for a blocking bug in LPC message queueing.
It seams I can't fix it. :(
There is something wrong in lpc/queue.c.
New SM that loads subsystems reading the registry config and CSR that
registers are attached to 585 (code *not* commited yet).
If fixing the LPC bug is not possible easily, I'll change SM to use a
scond thread to avoid cross calling from the same thread.
ea
Hi,
--- ea <ea(a)iol.it> wrote:
> maybe that is what I reported on the irc a few days ago (installing in
> QEMU061/Win32). Thomas could not reproduce it.
If I go through stage 2 setup quickly then it will crash. If I wait and go slowly over each page
ReactOS will not crash.
THanks
Steven
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
I'd like to close this discussion with a vote.
Should we allow branches (other than trunk) with mixed new development and bugfixes
unrelated to the new development that is on the branch (miscelanea branches) ?
[ ] Yes, do allow miscelanea branches
[ ] No, don't allow miscelanea branches
Casper
Hi,
currently the free handle entry list is a lifo list. This is not a good
solution for process and thread ids because a id from a currently
deleted process or thread is valid again after a very short time. I
would like it to change the free list to a fifo list by using a double
linked list. The u2 part of an entry has enough room for a list entry
instead an index.
- Hartmut
Hi.
I tested a new serial driver in a vmware with 4 serial ports.
It creates only one serial device and a symbolic link to it ("COM3");
When I write to "COM3" output goes to COM1 and mix with debug output there.
This is a bug imho.
This problem prevents ros from deleting a file/directory (observed while
running wine kernel32 reg. tests with param "path")
around line 295 in vfat\finfo.c: (svn blame says Hartmut made the last
changes around here)
------------------------------------------------
if (DispositionInfo->DeleteFile)
{
if (MmFlushImageSection (FileObject->SectionObjectPointer,
MmFlushForDelete))
{
if (FCB->OpenHandleCount > 1)
{
DPRINT1("%d %x\n", FCB->OpenHandleCount,
CcGetFileObjectFromSectionPtrs(FileObject->SectionObjectPointer));
Status = STATUS_ACCESS_DENIED;
}
else
{
FCB->Flags |= FCB_DELETE_PENDING;
FileObject->DeletePending = TRUE;
}
}
else
{
------------------------------------------------
Why deny deletion with STATUS_ACCESS_DENIED if FCB->OpenHandleCount > 1
??????
Gunnar
Hi:
>It is true that a filesystem that has a usermode component
>can not be used as a boot driver
I beleive this is not true. There are operating systems (at least I could name one) with all the drivers running in user mode leaving only a minimal kernel. Is sort of a client-server model, and yes with protection for file/folders. Now the ROS boot loader first loads kernel-hal-fat driver-... It has to, otherwise how would you load the filesystem driver? Now switching ring 0 <-> ring 3 with that in RAM... If you also load ntdll that way. Hmmm Why not? I beleive that is enought to read/write something to disk.
Regards
Waldo
--- Steven Edwards <steven_ed4153(a)yahoo.com> wrote:
>
> --- Sylvain Petreolle <spetreolle(a)yahoo.fr> wrote:
> > we can use ext2ifs, which is GPL and works under NT4, 5, 5.1, 5.2
> > http://uranus.it.swin.edu.au/~jn/linux/ext2ifs.htm
>
> We have the ex2fsd in a branch. It much better than this driver.
>
Sorry for that , but Jakob asked for "something for NT" on *ros-dev*.
If he wrote on ros-general, I know the ext2 branch is here
(and I tested your patches in october)
To avoid this
- in trunk : we should empty the drivers/fs/ext2 and|or #error it, refering to the ext2 branch.
- Fill the ext2 web page in Wiki.
Dedicated to Arty:
no need to answer 3 times, I'm susbscribed to ros-dev :))
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
>
> Is there no ext2 driver or something for NT we can use?
>
>
> regards,
> Jakob
we can use ext2ifs, which is GPL and works under NT4, 5, 5.1, 5.2
http://uranus.it.swin.edu.au/~jn/linux/ext2ifs.htm
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
--- Sylvain Petreolle <spetreolle(a)yahoo.fr> wrote:
> we can use ext2ifs, which is GPL and works under NT4, 5, 5.1, 5.2
> http://uranus.it.swin.edu.au/~jn/linux/ext2ifs.htm
We have the ex2fsd in a branch. It much better than this driver.
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Is it alright if i incorporate a database filesystem and a port of project looking glass into ReactOS. I really would like to see looking glass as an interface to ReactOS, as well as a database file system. I have been working on this filesystem for about a year now, and it is working on my windows 2000 and xp boxes. But it requires a service to start called windbfs.exe, and i know that reactos doesn't include support for services as well as it would like. The database file system is based off of mysql, tcl, and maxdb.
Please respond with comments and opinions....
Hi,
while looking for the console closing problem, I've seen that win2k
calls PsLookupProcessByProcessId very often with a id of 0xffffffff.
- Hartmut
(ex/handle.c:721) Looking up invalid handle 0xffffffff
Frames:
<ntoskrnl.exe:26f2d (ex/handle.c:722 (ExpLookupHandleTableEntry))>
<ntoskrnl.exe:275ce (ex/handle.c:919 (ExMapHandleToPointer))>
<ntoskrnl.exe:74af8 (ps/cid.c:106 (PsLookupCidHandle))>
<ntoskrnl.exe:7c6d5 (ps/process.c:2709 (PsLookupProcessByProcessId))>
<win32k.sys:45c16 (objects/gdiobj.c:1219 (GDIOBJ_SetOwnership))>
<win32k.sys:6840 (eng/surface.c:466 (EngDeleteSurface))>
<win32k.sys:52456 (objects/text.c:1922 (NtGdiExtTextOut))>
<win32k.sys:539ef (objects/text.c:2770 (NtGdiTextOut))>
<ntoskrnl.exe:3fb2 (D:\DOKUME~1\hb\LOKALE~1\Temp/ccgPaaaa.s:178
(KiSystemService))>
<gdi32.dll:99bc (objects/text.c:45 (TextOutW))>
I would like to see the project could you mail it or some..?
i think it sounds great.. but what i cant see/try i cant comment..
Gratz Thomas
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Let's keep this on the ros-dev ML please.
On Thu, 17 Mar 2005 09:57:07 -0800 (PST), Thomas Larsen
<sikker2004(a)yahoo.com> wrote:
> The bug until now is
>
> In my windows 2003 Enterprise Server
>
> 1. The resize bug you talk about.
>
> 2. Layout Problems but microsoft allso have that in theirs taskmgr they just try to hide it
> because the tab control get white color from uxtheme and the other controls are gray or alike and
> cant be transparant
>
> 3. A bug in the application view when trying to close task it dont refresh (Fixed)
>
> 4. When open Run Dialog and click on browse (the application use 8MB of mem) the resource dont
> "free up mem" even when unloading lib but the problem er allso in winxp and windows 2003 server
> editon and must be a shell32 bug dont know if this happens in reactos
>
> 5. Folders and zip folders do not reply (dont know how to fix this)
>
> /////////////
>
> What i did until now
>
> Correct "Getting Procesor" Bugs on windows server and some memory leaks
>
> The Hardcoded strings are now loaded from ressource and can all be translatet (Danish and English
> is done).
>
> The Run Dialog are from shell32 now and use the translation from their to save some mem.
>
> The About Dialog are from shell32 (Reactos allready implentet the LPGL license in their) to save
> some mem
>
> Removed Tabs and update processor information struct from zw.h
>
> Functions are optimized and dublicatet code are removed and replaced by one function
>
> Loops are decreed instead of increed (to hopefully make it faster should be faster when decreed).
>
> Use of shell32 is now 100% dynamic and are loaded when needed (Cant delay comdlg32 yet in reactos
> else this should be pretty fast to load)
>
> French are included from wine and are testet and modifed by using reshacker to see if the strings
> fit (they did not)
>
> Spain,deutch,english,france are modifed to fit in the dialogs
>
> Top Headers are modified to the new style in ntoskrnl (waste of space to include the license).
>
> Scroolbar are createtet by createwindow instead of createscroolwindows (microsoft will remove this
> call later or.. Information from msdn)
>
> added missing test flags to processor if failures
>
> Msgbox are allso loading from res
>
> All rc files are modified to use same style and comments
>
> Added Version Flag to TrayIcons
>
> Use InitCommonControlsEx Instead of outdatet function (MSDN)
>
> comparing with null instead this is the right to do
>
> removed some reg code creating the software useless and dont allocate strings
>
> Using RtlZeroMemory instead of memset
>
> Comparing with (sizeof(szTemp) / sizeof (tchar) when loading strings by security reasons allso in
> the old string code
>
> zero out all handles before using
>
> removed old ressourcer
>
> using manifest.xml in res and set the bitmaps and icons to natural
>
> added UNREFERENCED_PARAMETER when parameters are not used
>
> out comment unused loops and test code completely by using if 0 / endif
>
> and some minor fixes
>
> ///////////////////////////
>
> What im working on now is to get the right processor usage
> And the resize bug
> sorting the items in process
> network information tab
> user information tab
> additional information on processes when right and clik on details (what dlls are used and so on).
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business - Try our new resources site!
> http://smallbusiness.yahoo.com/resources/
>
--
The cheese stands alone.
ion(a)svn.reactos.com wrote:
> Dispatching & Queue Rewrite II:
>
> - Rewrote wait code. It is now cleaner, more optimized and faster. All waiting
> functions are now clearly differentiated instead of sharing code.
Imo, sharing the wait code is cleaner... (I remember the time i merged
the old wait code into one routine, heh)
These functions
> are called up to a dozen times a second, so having dedicated code for each of
> them is a real boost in speed.
> - Fixed several queue issues, made a dedicated queue wait/wake function (you are not
> supposed to use KeWaitFor on a queue,
I used KeWaitXxx in the queue impl. because i thought it was good to
have the wait code in one place only. Thou others find speed more
important:-D
Hi,
--- Damjan Jovanovic <dj015(a)yahoo.com> wrote:
> I am working on adding STI into the Wine project, and
> I thought that since ReactOS would probably benefit
> from it as well, you people could help me out.
>
> I need the STIUSD.H header file that should part of
> the Windows DDK, and seeing as I don't have the DDK
> and you guys should, maybe you can send it to me, and
> I can add STI support to ReactOS?
Sorry at this time we don't have this header in our DDK.
> STI is a still image API that lets you use scanners,
> cameras and the like in Windows.
>
> By the way, ReactOS looks interesting, when I have
> some time I'd like to work on it.
That would be nice. Feel free to ask any question here or mail
one of us directly.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
I need a tester for taskmgr.exe a improved version of mine
Don�t got a running version of reactos and need to test this app on other platforms than
windows 2003 server
Just send a mail and i send the source to you..
Thanks
Thomas
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Hi
I am working on adding STI into the Wine project, and
I thought that since ReactOS would probably benefit
from it as well, you people could help me out.
I need the STIUSD.H header file that should part of
the Windows DDK, and seeing as I don't have the DDK
and you guys should, maybe you can send it to me, and
I can add STI support to ReactOS?
STI is a still image API that lets you use scanners,
cameras and the like in Windows.
By the way, ReactOS looks interesting, when I have
some time I'd like to work on it.
Bye
Damjan
__________________________________
Do you Yahoo!?
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250
This is my changes to serial driver:
- Fixed bug: only one file may be open on a port at any given time.
- Implemented IOCTL_SERIAL_GET_STATS and IOCTL_SERIAL_CLEAR_STATS.
Small test program included
The 'Standard' PC serial ports are as follows:
COM1 (address 3F8-3FF) and COM3 (address 3E8-3EF) share IRQ4.
COM2 (address 2F8-2FF) and COM4 (address 2E8-2EF) share IRQ3.
I remember from my DOS days that you can add more serial cards into the
system just as long
as you kept the address's from overlapping, and your software was configured
correctly.
As far as I'm aware the BIOS data area only has place for 4 port addresses:
0000:0400 COM1 address
0000:0402 COM2 address
0000:0404 COM3 address
0000:0406 COM4 address
-----Original Message-----
From: Royce Mitchell III [mailto:royce3@ev1.net]
Sent: Thursday, 17 March 2005 12:04 p.m.
To: ReactOS Development List
Subject: Re: [ros-dev] serial driver bug
Robert Köpferl wrote:
> Be aware that it makes a difference wether you have got a so called
> multi serial card or several plain old serial HW. I may be wrong, but
> isn't 4 the limit. Due to 'reserved' ports for that kind of HW?
>
It's a multi-serial card. The 4 limit for plain serial is due to
reserved/limited irq if I understand correctly.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev
This communication is confidential and may contain privileged material.
If you are not the intended recipient you must not use, disclose, copy or retain it.
If you have received it in error please immediately notify me by return email
and delete the emails.
Thank you.
arty(a)svn.reactos.com wrote:
>consw has not been needed for a long time.
>
>
>
Actually, that was never needed. It was there for a planned extended
feature of our Win32 emulator: the possibility to switch back to text
mode on the active desktop belonging to the winstation attached to the
primary console.
Still getting it: Unhandled UserMode exception, terminating thread.
Jason
On Wed, 16 Mar 2005 19:30:11 +0200, Jason Filby <jason.filby(a)gmail.com> wrote:
> I wanted that record ;)
> Great to know though!
>
> Cheers
> Jason
>
> On Wed, 16 Mar 2005 18:15:50 +0100, Filip Navara <xnavara(a)volny.cz> wrote:
> > Jason Filby wrote:
> >
> > >Hi all
> > >
> > >Loading up the OpenOffice.org 1.1.2 Setup no longer works; the initial
> > >progress bar completes and then nothing happens. I'm sure I've seen
> > >this bug before! Any help welcome.
> > >
> > >
> > Just for the record, today I successfully installed OOo 1.1.1, ROS SVN
> > revision 14087.
> >
> > - Filip
> >
> >
>
Hi!
I switch to an older serial driver, BTW the new one set the baud to 19.2k.
(KERNEL32:mem/global.c:412) Memory Load: 8
CSR: NtOpenProcess() failed for handle duplication
Failed to tell csrss about new process. Expect trouble.
(KERNEL32:mem/global.c:412) Memory Load: 8
Funny debug message,
James
Alex's patches are in, and I saw him call for 0.2.6 on irc, but
there have been a few regressions discovered. Do we need to have a
bughunt / regression test / code freeze? The last couple of releases
(that I have been around for) we have created the branch, then applied
bugfixes against it, then backported to HEAD. Is this the way we
should do this? Should we "freeze" HEAD and then branch?
I found that vncviewer no longer starts for me, and Alex said that
Abiword doesn't work for him. The wallpaper was reported to have
regressed also. I personally will test the wallpaper and all the
other things I care about tonight. Maybe we should have others check
over things too..
Just curious,
WD
--
The cheese stands alone.
Hi all
Loading up the OpenOffice.org 1.1.2 Setup no longer works; the initial
progress bar completes and then nothing happens. I'm sure I've seen
this bug before! Any help welcome.
Thanks
Jason
--- James Tabor <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net> wrote:
> We don't have this yet? Is there a plan to include this in our
> code tree?
According to Thomas and Dmitry's tests its not correct so we are waiting to
see if someone comes up with a better implementation.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Hi Steven,
Steven Edwards wrote:
> Changelog:
> Christoph von Wittich <Christoph(a)ApiViewer.de>
> Implement GetComboBoxInfo
>
>
>
We don't have this yet? Is there a plan to include this in our
code tree?
Looks great!
James
ReactOS will not build on Windows with the latest version of Nasm (
0.98.39 ), because at least some public releases of that version ( I
just downloaded the official from sourceforge.net ), do not support long
file names, and we have a long file name in PSEH.
We can just shorten that asm's file name, but we could also configure
the build system to reject that version.
I don't feel like dealing with it, so I thought I would just send a
head's up here :)
--- Alex Ionescu <ionucu(a)videotron.ca> wrote:
> This goes beyond debug information. This is reproduceable behaviour that
> probably any driver developper out there knows. Checked builds are
> builds recommended for testing your driver for bugs. If you call that
> function with a Queue Object, you WILL see that assert line-by-line on
> your screen. From that point on, one should stich his eyes out for
> having seen it, and shoot himself for knowing this behaviour?
So fix a ReactOS driver to match this behavior and work under Windows and
then you will have justification for making related changes in the kernel.
> Notwithstanding that they cannot sue the project, and that they would
> not sue you. This was a public comment to a friend... why would they sue
> Steven when Alex said what he said? And yes, I cannot wait to be sued...
> I can see the headlines -- Driver Developer sued for being aware of
> Windows Assertion --. I hope they also go after Mark Russinovich for
> having used the checked build to generate a tree of the Windows Source
> code!!
The last time I looked Mr Russinovich was not try to make a replacement
for Windows but rather provide more information people wanting to use
Windows.
> If you aren't, then why am I always the one being targeted with such
> comments. There are functions in ROS which are almost copies of their
> binary versions. There are structures in ROS which look like clones of
> the Windows ones (undocumented ones). There is functionality that was
> directly reversed engineered so that it would be compatible.
Yes we have reverse engineered quite a bit but the question is what methods
are being used to reverse certain behavior. We cannot help but be compatible
with the structures in Windows and take any means needed to be compatible.
> Yet, nobody says a word; everyone goes after Alex for having a
> conversation with a friend and mentionning a reproducible fact in every
> driver developer's life -- you do not KeWaitXxx on a Queue.
> Probably as much as jumping on a guy who has written some of the highest
> quality and most useful code in the OS for the fact he used public
> information during an argument.
You stated the other day there were regressions that were only found by
developing test cases. You would have a lot more good will from developers
on this project if you committed test cases for some of the patches you develop
and commit them to rosapps/tests or write a dummy driver to show the behavior
rather than than pointing to checked builds.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail
Hi,
--- Mike Swanson <mikeonthecomputer(a)gmail.com> wrote:
> Just put a trademark on the name but allow it to be used on
> derivations on the circumstance that it clearly shows that it is not
> _the_ ReactOS.
I have looked in to this a bit with the legal council I have on retainer as part of the ReactOS
Foundation work. I think it is around $250 to file in a state and around $1000 to file the federal
paperwork. I will call the lawyer this week and get numbers and a timeframe on what it would take
to make it happen.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
--- Alex IoIonescuioionucuivideotrona> wrote:
> This climate of paranoia is getting to my nerves.
You could at least try to be civil in your discussion. Some of us have spent more than a few years
on this project and have a right to be a little paranoid about if our lives work might be put in
to danger.
> As for Steven... WINE, ROS, and any other compatibility product out there is not 100% clean
> room. It has never been, will never be, cannot be. Especially if we consider debug information
> as being "dirty". Reminds me of people freaking out when I added functions that were in the IFS
> -- you'd hope people would've grown up by now--.
Still it depends on the source of the information. We have discussed in private my views on using
the debug information. I will publicly state I think the law is ambiguous at best and the debug
information should be a valid source given Microsoft position of being a monopoly as found by
Anti-trust proceedings. That being said a court might not agree with me so any behavior must be 1.
Reproduceable or 2. Documented.
> I could make a list of over 25 parts of ReactOS Which are not 100% clean. But I won't, because
> that would tarnish our image. I would appreciate if you'd stop tarnishing mine and making
> accusations.
I am not trying to trash your image. I am simply mentioning the truth that everyone already knows
but could be deadly to this project and others in a kangaroo court in the US. When your source of
information comes from documentation or a third part program exhibiting certain behavior then
there is not a legal question as to if a reimplementation is a original work. If you are basing
your implementation of a feature only on the debug information then clearly, at least in my mind
it runs the danger being found a derived work and everytime you do so it at the very least
tarnishes ReactOS's image.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
--- Alex Ionescu <ionucu(a)videotron.ca> wrote:
> What the fsck are you implying.
Its hard to claim our implementation is "clean room" if you are basing your implementation on
debug information rather than reverse enginered behavior. I am not opposed to observing the
implementation via debug information and then writting tests to match behavior but there is a fine
line...
Thanks
Steven
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
What if winlogon.exe is run by csrss.exe and not by smss.exe?
A winlogon process, in its own desktop, is needed for each Win32 session.
If we make csrss.exe multiuser, it must create session 0 (console) or
die and therefore run winlogon in it.
This change shouldn't have any effect on compatibility with Windows NT.
smss will assume only csrss is critical.
ea
Wow!
Current SVN (Head)!
Used memory 1015744Kb
(mm/mminit.c:375) Kernel Stack Limits. InitTop = 0x80133000, Init = 0x80130000
(mm/virtual.c:214) FIXME: MEMORY_AREA_SYSTEM case incomplete (or possibly wrong)
for NtQueryVirtualMemory()
(ke/bug.c:56) Found Bugcheck Resource Data!
(ke/bug.c:67) Got Pointer to Bugcheck Resource Data!
(ke/clock.c:80) KiInitializeSystemClock()
(ke/clock.c:99) Finished KiInitializeSystemClock()
No current process
Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0x9c could not be read: Page not present.
No current process
KeBugCheckWithTf at ke/catch.c:224
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
KMODE_EXCEPTION_NOT_HANDLED
Technical information:
*** STOP: 0x0000001E (0xc0000005,0x8002f410,0x00000000,0x00000018)
*** ntoskrnl.exe - Address 0x8002f410 base at 0x80000000, DateStamp 0x0
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:8002f410 <ntoskrnl.exe:2f410>
cr2 18 cr3 26000 Proc: 0
DS 10 ES 10 FS 30 GS 10
EAX: 00000000 EBX: 00000680 ECX: 00026000
EDX: 00000064 EBP: 8013245c ESI: 80132834 ESP: 801323ac
EDI: 80132be0 EFLAGS: 00210046 kESP 801323ac Frames:
<ntoskrnl.exe:300fc>
<ntoskrnl.exe:de31>
<ntoskrnl.exe:1285>
<ntoskrnl.exe:1aff>
<ntoskrnl.exe:382d>
<ntoskrnl.exe:c4a3e>
<46C>
KeBugCheckWithTf at ke/catch.c:224
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
KMODE_EXCEPTION_NOT_HANDLED
Technical information:
*** STOP: 0x0000001E (0x80000003,0x80005c47,0x00000000,0x00000000)
*** ntoskrnl.exe - Address 0x80005c47 base at 0x80000000, DateStamp 0x0
Hi Hartmut,
> I'm not sure but a native application can only import ntdll.dll. If you
> enable the code, smss will import smdll.dll.
You are probably right. It is the time to make smdll static.
Thank you.
Emanuele
____________________________________________________________
Navighi a 2 MEGA e i primi 3 mesi sono GRATIS.
Scegli Libero Adsl Flat senza limiti su http://www.libero.it
I was wondering if there was a project that would be doing a binary compatible OS X system. What reactos does for windows maybe this project can do for OS X. I was just wondering. I know that pearpc emulates a ppc processor, but wether or not a full os exists is the question. I know also that some versions of linux exist for ppc.
Thanks
Also - is reactos going to do a mips, ppc, arm, ia64 system?
weiden(a)svn.reactos.com wrote:
>Alex Ionescu <ionucu(a)videotron.ca>
>
> Dispatcher Objects Rewrite (minus Queues, coming in next patch).
>
>
>
There is now only one large patch left + a smaller one related to it,
which will complete the Dispatcher fixes. After those two patches,
everything in my branch will have been committed. The branch will be
destroyed and I will create the Winsock branch on which Arty and I will
work.
Best regards,
Alex Ionescu
Hi,
Right now, someone has set up an XDCC IRC bot to distribute copies of
ReactOS. While I welcome the move, it raises a question on who is
responsible for the quality of those files. Even if the person means no
harm, the files can get corrupted/infected by the following events:
1) Download corruption
2) Viral infection
3) Hard-disk damage
And perhaps many more. In all cases, this would result in unusable,
dangerous or even damaging releases of ReactOS, which we could not
control. As such, I propose a vote:
[ ] Yes, allow 3rd-party distribution of the OS through the #ros-xdcc
channel and ROS-XDCC-001 bot. (support and encourage this distribution)
[ ] Yes, allow 3rd-party distribution of the OS, but it must clearly
distance itself from officially supported releases (tolerate but do not
support this distribution)
[ ] No, only sourceforge and other official ReactOS distribution points
should be used.
Myself I vote for the first choice, but I would like the following to be
done:
1) Create MD5 Hashes to verify authenticity
2) Set up official communications with the bot's maintainer and
establish a set of guidelines.
Best regards,
Alex Ionescu
screens? :P
greatlrd(a)svn.reactos.com wrote:
>GetDeviceData
>fix the choppy mouse in UT and fix some other small bugs.
>I can now use the mouse with out any problem in UT
>
>
>
>
>Updated files:
>trunk/reactos/lib/dinput/mouse.c
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
Hi,
--- Jason Filby <jason.filby(a)gmail.com> wrote:
> Another question is: can we really say limit people from
> redistributing ReactOS? I don't think that our license(s) prohibit
> this.
>
> Perhaps some guidelines for such people are all that is needed.
I think we should allow use of the name in limited situations. As another poster stated having a
"Dropline ReactOS" is not a bad thing provided that we setup standards on what has the right to be
called "ReactOS" and what does not. If anyone making or distributing a custom version of ReactOS
violates the standards we set forth then we have the right to refuse use of the name.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Feel free to reread LGPL 2.1 here :
http://svn.reactos.com/viewcvs/trunk/reactos/LGPL.txt
--- Magnus Olsen <magnus(a)itkonsult-olsen.com> wrote:
> ReactOS are not a LPGL but GPL
> it is big diffrent in the licen type
>
> ----- Original Message -----
> From: "Sylvain Petreolle" <spetreolle(a)yahoo.fr>
> To: "ReactOS Development List" <ros-dev(a)reactos.com>
> Sent: Sunday, March 13, 2005 8:39 PM
> Subject: Re: [ros-dev] Vote: Allow 3rd-party distribution of ROS through
> XDCCBot.
>
>
> > If all legal conditions are fulfilled :
> > - give link to the source
> > - (alex's idea) provide md5sum of the file(s)
> >
> > As some people already said, 3d point cant exist.
> > (ros is a LGPL system, some magazines already distribute it, etc.)
> > > [ ] Yes, allow 3rd-party distribution of the OS through the #ros-xdcc
> > > channel and ROS-XDCC-001 bot. (support and encourage this distribution)
> > >
> > > [X] Yes, allow 3rd-party distribution of the OS, but it must clearly
> > > distance itself from officially supported releases (tolerate but do not
> > > support this distribution)
> > >
> > > [ ] No, only sourceforge and other official ReactOS distribution points
> > > should be used.
> >
> >
> > Kind regards,
> >
> > Usurp (aka Sylvain Petreolle)
> >
> > humans are like computers,
> > yesterday the BIOS was all
> > - today its just a word
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.com
> > http://reactos.com:8080/mailman/listinfo/ros-dev
>
>
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
chorns(a)svn.reactos.com wrote:
>* GNU make don't support depending on a directory, so simulate the dependency using a file
>
How not? It works on my box as well as on arty's. :(
There is a little piece of code I left in reactos/subsys/smss/initss.c
that looks like harmless, but that actually crashes smss.exe and
therefore the whole system. The code is in the function
SmpRegisterSmss/0. I can't find myself the bug. The code is currently
wrapped by a #if 0 ... #endif but it is needed to make the SM self
register (to avoid other processaes claim they are the SM). Any hint is
welcome!
Emanuele
WARNING: This e-mail has been altered by MIMEDefang. Following this
paragraph are indications of the actual changes made. For more
information about your site's MIMEDefang policy, contact
MIMEDefang Administrator <mimedefang(a)deos.tudelft.nl>. For more information about MIMEDefang, see:
http://www.roaringpenguin.com/mimedefang/enduser.php3
An attachment of type message/rfc822, named [ros-svn] [hbirr] 13963: Lock the kernel address space instead the process'one, if the pages are located in kernel space. was removed from this document as it
constituted a security hazard. If you require this document, please contact
the sender and arrange an alternate means of receiving it.
> Let me make it clear that the vote is about wether or not to allow
> a particular type of branch which have some bad consequences. Not
> branches in general. See
> http://reactos.com:8080/archives/public/ros-dev/2005-March/002083.html
> for a description of the common branch types.
I did read it (otherwise I wouldnt vote)
"Bugs that that could have been fixed on trunk are annoying to trunk
developers. The bugfixes that go only to the branch are not in trunk (until
merged there from the branch"
=> trunk developers are free to ask for a merge or use ros-diffs to speed up the merge process.
"* Risk of duplicating work. We'll have more branches to track bugfixes on
so it's harder to know which bugs has been fixed and which hasn't."
you can use ros-svn to track it. And you can fix bugs in bugzilla too.
"Fixed in branch my_branch, feel free to merge."
>
> Do you have commit access?
>
> Casper
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
If all legal conditions are fulfilled :
- give link to the source
- (alex's idea) provide md5sum of the file(s)
As some people already said, 3d point cant exist.
(ros is a LGPL system, some magazines already distribute it, etc.)
> [ ] Yes, allow 3rd-party distribution of the OS through the #ros-xdcc
> channel and ROS-XDCC-001 bot. (support and encourage this distribution)
>
> [X] Yes, allow 3rd-party distribution of the OS, but it must clearly
> distance itself from officially supported releases (tolerate but do not
> support this distribution)
>
> [ ] No, only sourceforge and other official ReactOS distribution points
> should be used.
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
Hi!
hbirr(a)svn.reactos.com wrote:
> Added a keep-alive reference to each key object.
> Lock the registry while accessing sub keys of a key object.
> Implemented a worker thread which removes all unused key objects.
> Fixed a bug which shows keys twice if a key is already opened.
>
>
>
> Updated files:
> trunk/reactos/ntoskrnl/cm/cm.h
> trunk/reactos/ntoskrnl/cm/ntfunc.c
> trunk/reactos/ntoskrnl/cm/registry.c
> trunk/reactos/ntoskrnl/cm/regobj.c
>
ntoskrnl: [CC] cm/regobj.c
cm/regobj.c: In function `CmiObjectParse':
cm/regobj.c:244: error: parse error before '<<' token
cm/regobj.c:763: error: parse error at end of input
cm/regobj.c:23: warning: `CmiGetLinkTarget' declared `static' but never defined
make[1]: *** [cm/regobj.o] Error 1
make: *** [ntoskrnl] Error 2
8^),
James
--- Casper Hornstrup <ch(a)csh-consult.dk> wrote:
> I'd like to close this discussion with a vote.
>
> Should we allow branches (other than trunk) with mixed new development and bugfixes
> unrelated to the new development that is on the branch (miscelanea branches) ?
>
> [X] Yes, do allow miscelanea branches
>
> [ ] No, don't allow miscelanea branches
>
> Casper
>
Have an svn branch gives a nice way to revert/update
and permits others to work with a different POV on the project.
Even if only some are using it, it can help ros a lot.
(look at the xmlbuildsystem branch that speeds up the compilation a lot)
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
I don't think we've ever formalised our voting procedures.
All I seem to remember about this is that committers can vote.
I've drafted an initial version here:
http://reactos.com/wiki/index.php/Voting
Please comment on that.
Casper
--- Alex Ionescu <ionucu(a)videotron.ca> wrote:
> [ ] Yes, allow 3rd-party distribution of the OS through the #ros-xdcc
> channel and ROS-XDCC-001 bot. (support and encourage this distribution)
>
> [X] Yes, allow 3rd-party distribution of the OS, but it must clearly
> distance itself from officially supported releases (tolerate but do not
> support this distribution)
Yes but only if they are using a binary published by reactos.org or a core ReactOS developer such
as Thomas's nightly builds. If they are not doing so then my vote is no. At the first offence we
should warn them and then at the 2nd offence we should deny the use of the ReactOS name
> [ ] No, only sourceforge and other official ReactOS distribution points
> should be used.
We cannot stop distrabution of the OS. Only the use of the name.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Hi Royce,
royce(a)svn.reactos.com wrote:
> -Wall -Werror and fix warnings
>
>
> Updated files:
> trunk/reactos/tools/widl/Makefile
> trunk/reactos/tools/widl/hash.c
> trunk/reactos/tools/widl/write_msft.c
>
> _______________________________________________
> Ros-svn mailing list
> Ros-svn(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
More crazy Linux port problems, in /reactos/tools/widl,
write_msft.c: In function `ctl2_write_chunk':
write_msft.c:2189: warning: implicit declaration of function `write'
write_msft.c:2190: warning: implicit declaration of function `close'
write_msft.c: In function `save_all_changes':
write_msft.c:2284: warning: implicit declaration of function `creat'
make: *** [write_msft.o] Error 1
It works when removing -Werror -Wall from the Makefile. BTW io.h
is in the /usr/mingw32/include directory.
Thanks,
James
hbirr(a)svn.reactos.com wrote:
>Use only one access to the spinlock in the assertion, because the value may change between two access' on smp machines.
>
>
You implementation is better, no doubt, but it wouldn't have mattered to
read it twice or more. I mean, it's re-read again down in the
InterlockedExchange call, there's a possibility it might have been
changed in the meantime as well. But it really wouldn't matter ;)
Best Regards,
Thomas
Hello,
Retransmission of this message sent to Harmut , to Ros-Dev list
following error in the mail address of Ros list
---------------------------------------------
Harmut ,
I do not know if this commit is related to the Bug #512 ( Colinux fails
to load in MM/MDL ) but more debug messages are displayed now.
I have updated Bugzilla with these debug messages.
Best regards
Gerard
Subject:
[ros-svn] [hbirr] 13963: Lock the kernel address space instead the
process' one, if the pages are located in kernel space.
From:
<hbirr(a)svn.reactos.com>
Date:
Sat, 12 Mar 2005 10:14:38 +0100
To:
<ros-svn(a)reactos.com>
Lock the kernel address space instead the process' one, if the pages are
located in kernel space.
Unlock the address space on error.
Hi,
--- Eric Kohl <eric.kohl(a)t-online.de> wrote:
> I read the wine-devel list archive a few days ago and relized that
> Alexandre rejected the last patch. I want to split the last patch into
> more 'atomic' parts tomorrow. Is that OK?
Sure thats what I was going to do next. I am going through SVN right now and extracting each
atomic commit and manually applying them to my winehq tree. I can send each patch from each atomic
commit but its going to take me quite a while to resolve conflicts.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250
weiden(a)svn.reactos.com wrote:
>Thomas Weidenmueller <w3seek(a)reactos.com>
>- Fix various security structures and constants
>- Add code to capture quality of service structures and ACLs
>- Secure buffer access in NtQueryInformationToken, NtSetInformationToken, NtNotifyChangeDirectoryFile and NtQueryDirectoryFile
>
>
For the sake of review/auditing, it should be important to mention this
is yet-another-alex_devel_branch-merge. Thomas wrote 100% of it, I'm
just mentionning this as a progress report and historical/bookkeeping
reason.
Best regards,
Alex Ionescu
To clarify i mean OS X and perhaps even os 9. I know about darwin but i was wondering if there was an os x clone out there. Reactos is a version of windows as this clone will be an open-source version of os x or os 9.
>
> From: "Klemens Friedl" <klemens_friedl(a)gmx.net>
> Date: 2005/03/12 Sat AM 10:42:17 EST
> To: ReactOS Development List <ros-dev(a)reactos.com>
> Subject: Re: [ros-dev] Mac OS X clone???
>
> > I was wondering if there was a project that would be doing a binary
> > compatible OS X system. What reactos does for windows maybe this project
> can do
> > for OS X. I was just wondering. I know that pearpc emulates a ppc
> processor,
> > but wether or not a full os exists is the question. I know also that some
> > versions of linux exist for ppc.
>
> Do you mean MacOS X?
>
> Darwin has been the open-source OS technology underlying Apple's Mac OS X
> operating system, with all development being managed and hosted by Apple:
> -> http://developer.apple.com/darwin/
> -> http://www.opendarwin.org/
>
>
>
> -- Klemens Friedl
>
> --
> SMS bei wichtigen e-mails und Ihre Gedanken sind frei ...
> Alle Infos zur SMS-Benachrichtigung: http://www.gmx.net/de/go/sms
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
>
Hi Eric,
How much more work is going to be needed in WIDL? There are quite a lot of changes and I have
fallen behind on merging to Winehq.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail
> >
> > [ ] Yes, do allow miscelanea branches
> >
> > [ ] No, don't allow miscelanea branches
> >
> > [X] Clearly define feature vs mscelanea branches.
I don't mind Alex having a remote branch to be able to maintain
a public backup of his work. In fact I think all of the ReactOS
developers should have public branches but I think that anytime
a feature is implemented in a remote branch and another developer
is blocked by said feature then the remote branch has to be merged
with the trunk. For people like me that contribute little or no code
other than minor bugfixes this may be overkill.
This whole problem is that much of the development switched to his branch
when it should have been merged to the trunk. Alex has admitted this and I
think we have reached a middle ground.
Thanks
Steven
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
navaraf(a)svn.reactos.com wrote:
>Alex Ionescu <ionucu(a)videotron.ca>
>Various bugcheck code improvements:
>- Fix bugcheck code and make debugging easier for unhandled exceptions/spinlocks.
>- Fix a race condition with TAB+B,
>- Fix irql to be high_level.
>- Fix calling unsafe function by caching bugcode data.
>- Fix support for smp by using IPI.
>- Fix not-breakpointing when no debugger is there.
>- Implement KeBugCheck callbacks with reason.
>- Fix callbacks not being called.
>- Fix proper breakpoint during bugcheck.
>Filip Navara <xnavara(a)volny.cz>
>- Move the bugcheck initialization code into Ke (was in Ex on Alex's branch).
>
This doesn't look correctly:
>+ ASSERT(*SpinLock == 0 || 1);
>
>
Can you fix it, Alex?
- Filip
It seems there are more bugs in ld or anywhere. Some relocation entries
points to an address, which must not relocated. This entries starts
always in the upper range of the text section. Ntoskrnl does also
contain relocation entries for the bss section.
- Hartmut
navaraf(a)svn.reactos.com schrieb:
>Don't use intermediate objects linked with "ld -r". There's a bug in binutils that causes the data section relocations to be stripped.
>
>
>Updated files:
>trunk/reactos/ntoskrnl/Makefile
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
>
What you're saying is true however let me bring forth few points:
1. MUI only works one some Windows versions - true. However it runs
basically on all Windows versions available today (Windows 98/Me is not
your target) and Windows XP Home Edition as we all know is binary
compatible with Windows XP so the limitation is only in version check.
2. You cannot get it free - true. But is this important? You cannog get
Windows for free as well and still you're trying to clone it (rather
succesfully).
3. Are you sure the API is not available? I believe it would be fairly easy
to reasearch it even if it wasn't.
4. "So I think reactos must support least 2 langues at fly." Why limit
yourself to 2 only? Why not 3 or 4?
5. "But why not deside which langues it will support when it compile." In
my opinion this is answered very easily:
a. Because you do not want to create ReactOS for power-users who are keen
to compile stuff. If you need to compile it you'll scare newbies who just
want the simplicity of their old Windows for free.
b. Because it contradicts your initial requirement: "If you look at Amiga
OS (Workbench 2.0 or higher) you can change the hole os langues when it was
running."
All in all: I think the M$ approach is really good one: scalable and easy
to use. If you don't want to clone the API for whatever reason, clone the
principle...
Best regards
Radovan Skolnik
"Magnus Olsen" <magnus(a)itkonsult-olsen.com>
Sent by: ros-dev-bounces(a)reactos.com
12.03.2005 14:57
--------------------------------------------------------------------------------
Please respond to ReactOS Development List
--------------------------------------------------------------------------------
To
"ReactOS Development List" <ros-dev(a)reactos.com>
cc
bcc
Subject
Re: [ros-dev] Idea to save time in future - Language Support AndUse
inReactos
The MUI only work on some windows version and you can not geting it free.
or even the api. So I think reactos must support least 2 langues at fly.
But why not deside which langues it will support when it compile.
if you only want example english and french example you got it
or you want all langues. you got it instead. when reactos are beign compile
?
I have done a copy and paste from ms site
http://www.microsoft.com/globaldev/DrIntl/faqs/MUIFaq.mspx#MUIques1
read it about it here.
What versions of Windows are supported by MUI?
MUI was introduced in the Windows 2000 timeframe and is available for:
a.. Windows 2000 Professional
b.. Windows 2000 Server Family - often implemented in a Terminal Services
environment
c.. Windows XP Professional
d.. Windows XP for Tablet PC
e.. Windows Server 2003 Family
f.. Windows XP Embedded
MUI is not supported on consumer versions of Windows such as Windows 9x,
Windows Me, and Windows XP Home Edition.
What are the system requirements of Windows MUI?
MUI is an add-on to the English version of Windows XP Professional and
Windows 2000 family of operating systems, and will not install on localized
versions of Windows XP/2000 or on Windows XP Home Edition. Every additional
language installed will require approximately 115 MB extra disk space for
Windows XP, 45MB for Windows 2000; East Asian language support requires an
additional 250 MB.
How can I acquire Windows MUI?
The Windows XP/2000 MUI is sold only through Volume Licensing programs such
as the Microsoft Open License Program (MOLP / Open), Select, and Enterprise
agreement (or with a new computer as an OEM version at customer request).
It
is not available through retail channels.
----- Original Message -----
From: "Radovan Skolnik" <Radovan_Skolnik(a)tempest.sk>
To: <ros-dev(a)reactos.com>
Sent: Saturday, March 12, 2005 1:40 PM
Subject: RE: [ros-dev] Idea to save time in future - Language Support
AndUse
inReactos
> Hello guuys (and girls if any out there)!
>
> Until now I have been watching the development of ReactOS with great
> interest but as a not-so-great C/C++ programmer (especially for kernel
> stuff) I felt no urge to add my (for you would be worthless) comments :-)
> However the discussion about localizing ReactOS struck me because I think
> there's one thing in/for M$ Windows/Office you probably don't know about
> that already handles this. It is called MUI (Multilingual User Interface
> Pack) - read about it here:
> http://www.microsoft.com/globaldev/DrIntl/faqs/MUIFaq.mspx What it does
is
> that it adds another combo box to Regional Settings in Control Panel and
> each user can choose language to its liking (from those installed of
> course). I can have a look at install media for few languages but as far
as
> I remember it is only bunch of .inf & .dll (probably resources) files. So
I
> believe there is indeed an API to achieve this. So if you're aiming for
> maximum compatibility with original Windows (whatever version) you should
> probably consider this approach. I'm home and sick now with flu but when
I
> get well I'll research the MUI media in more detailed way and let you
> know...
>
> Best regards
>
> Radovan Skolnik
>
> ----- Original Message -----
> From: Magnus Olsen magnus at itkonsult-olsen.com
>
> I want see driffnet langues in the dll and change langues on fly
> instead compile a dll file for each langues. I am mising that feturtuer
in
> windows.
> If you look at Amiga OS (Workbench 2.0 or higher) you can change the hole
> os
> langues
> when it was running. in windows you are stuck with one langues.
>
> So I think it is good idea to compile all langues into all dll file.
> then select in the os wich langues you want use.
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev