Hi Gregor,
I've some problems with your changes. On my smp machine I get an assertion
from fpu.c line 452. I think, it isn't possible to use
KPCR.PrcbData.NpxThread on a smp machine. With your first patch I don't have
any problems.
- Hartmut
Hi got a problem i Reactos
The Kernel32.Def File
LIBERY KERNEL32.DLL
EXPORTS
NTDLL.RTLALLOCHEAP
And all the other def files where HAL.Somefunction NTDLL.Somefunction etc are in
I know that NTDLL.DLL IMPORTS "RtlAllocateHeap etc." those funktions from a lib in rtl.lib but
don�t know if thats the
problem becures SCSIPORT.SYS allso import some HAL.somefunction witch allso are broke
The tool DependX86 a tool use to find broke link in files can�t either find them and it a littel
strange problem …
[View More]becures i should work microsoft allso do that kind of linking against files and
allso use lib files to import
Use the most recent CVS of Reactos and the newest edition of MingGW
Allso tried differet option and differt compilere versions but seems to me theire must lay a
strange problem in reactos og MingGw Simpl don�t support that...
Crashlist of Files:
Kernel32.dll depend on NTdll.dll
User32.dll depend on kernel32.dll
Atapi.sys depend on Scsiport.sys depend on HAL.DLL
The Subsystem CRSS
And Many more
Anybody Help Me Please
Thomas
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - What will yours do?
http://my.yahoo.com
[View Less]
Hi Rick:
Well I don't believe that would be a protection at all against viruses. Why?
If I where to write a virus and knowing that reactos has such protection that would not stop me at all. I could simply write a function to calculate the hash in the virus (or simply tell the OS to do it for me) and update such database. Look at windows file protection, virus laugh at it. I think the verification of the PE checksum is enough to tell if a file is corrupt and would be faster wich means a …
[View More]faster load. If you want to know some more about viruses look for the e-zines of 29A on the internet to find out more about the subject. Their articles are as advanced as those in phrack (the latest). I think there is not solution for viruses, users will always do insecure things and viruses will be there waiting for them to do it.
Regards
Waldo
________________________________
De: ros-dev-bounces(a)reactos.com en nombre de Rick Langschultz
Enviado el: Lun 11/22/2004 11:25 p.m.
Para: ReactOS Development List
Asunto: [ros-dev] ReactOS and Viruses
Sun will be releasing Solaris 10 shortly as a commercial product available for purchase. There is a new file system that is 128-bit, and is protected by md5 checksums, I think this is a great idea for reactos. I think before a program executes there should be a binary verifier that checks this checksum and then allows the program to run. This would help in deterring Windows viruses from attaching themselves to reactos binaries. Since ReactOS is open source it will be harder to protect a binary if there is an attack and a malicious user replaces a dll or an exe. Perhaps this can be done using a small xml file or a txt file called md5sums or something. Please let me know what you think.
[View Less]
I noticed yesterday while installing ros from a locally generated
bootcd that pcnet.sys is not included. Could someone add it to
reactos.dff? Thanks!
Andrew
--
The cheese stands alone.
Sun will be releasing Solaris 10 shortly as a commercial product
available for purchase. There is a new file system that is 128-bit, and
is protected by md5 checksums, I think this is a great idea for reactos.
I think before a program executes there should be a binary verifier that
checks this checksum and then allows the program to run. This would help
in deterring Windows viruses from attaching themselves to reactos
binaries. Since ReactOS is open source it will be harder to protect a
binary …
[View More]if there is an attack and a malicious user replaces a dll or an
exe. Perhaps this can be done using a small xml file or a txt file
called md5sums or something. Please let me know what you think.
[View Less]
With the issue of Ekush talking about sending us patches once they
publish thier code and what not I as many of you are worried about being
tainted, I have an idea, but I don't know how safe it is from a GPL
stand point (I know nothing of the GPL) here's the idea, when we get
patches that are questionable from *any* source, we send MS a copy of
the suggested patch, and request they compare it with thier code to see
if it is differant or the same as thier Windows code, if MS comes …
[View More]back
and says it's teh same we delete the patch and move on...
I know this idea sounds bad but we need to discuss a plan for any
potential tainting and how we'd deal with it, please if you don't like
my idea then please by all means suggest something else.
[View Less]
Hello people,
can you post some sources (links etc.) where I can find some info about
internal NT kernel structure/architecture/whatever suitable for lamers
and newbs like me?
I don't know if anyone has been to ekush.com recently:
> " We are also decided to remove all the non-GPL'd code from our source tree and re-publishing the project based on React OS and Wine. All the Ekush sources will be merged to the React OS tree; sources and binary both will be published accordingly under the GNU GPL and EKUSH.COM will be the official web home for Ekush OS. Hope it will eliminate all the confusion and misunderstanding regarding Ekush Operating System. "
Hi,
Does anyone object agains:
-moving every NtXxx functions into new files under ntoskrnl\nt?
-moveing functions related to ob managed types into new files (thrdobj.c,
procobj,c, eventobj.c, fileobj.c etc)?
This will make it clearer where the functions are and what they do.
Gunnar