Could Someone with autorization to edit the
Reactos.com Web page look at my FAQ and Howto, to
decide if he/she likes it and what have to be changed
so it could be in the web page.
I think it is a improvement over the actual texts. The
texts i did are thought for everybody, even with
screenshots to guide the people with little
experience.
Thankyou,
Lucio Diaz.
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
>While attempting to guess the location isn't going to
>be successful
>100%
>of the time, it would probably be better then the 99%
>incorrect that
>you
>get with always defaulting to 1 set zone.
>Also, are there any other user-set preferences that
>come before the
>date/time page (How do you call the different parts
of >Setup?) that
>might help determining location?
It seems a pain in the @ss to code the whole thing,
taking in acount ALL the countries and their probable
timezones(countries with diferent timezone areas) for
something as easy to the user as to look at his watch
and set the time. I dont mind what standard (if GMT -8
or GMT 0) you chose, but i believe that making it more
elaborate does not worth today when many other things,
quite more important, are waiting to be implemented
(like Networking). I am sure that time will come for
those details.
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
Hi!
I have written a tool to configure the ReactOS source tree (customize
the build) It builds a GUI interface from an XML file which lists all
the possible options and how they are "realized" (in which file a value
has to be changed to make the build-system do what is wanted, i.e. set
KDBG in config to 1)
I would like to add the possibility of configuring things like
WHOLE_PAGE_ALLOCATIONS or TAG_STATISTICS_TRACKING (from ntoskrnl/mm/npool.c)
It would be good if such defines were moved into a file like
ntoskrnl/include/config.h which is then included by ntoskrnl.h and looks
like this:
/* Enable tracking of statistics about the tagged blocks in the pool */
#undef TAG_STATISTICS_TRACKING
/*
* Put each block in its own range of pages and position the block at the
* end of the range so any accesses beyond the end of block are to invalid
* memory locations.
*/
#undef WHOLE_PAGE_ALLOCATIONS
I don't want to make the tool edit the C files directly.
If anybody is against this please let me know, otherwise I will do it.
(Note: The tool is written in python and will thus not be allowed into
the reactos tree but I will provide it for whomever is interested)
Thanks,
blight
>The most intelligent solution is to stick to GMT 0.
>Best regards,
>Alex Ionescu
I agree, is both the easier and the most logic option
(also i live at GMT 0 ;)
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
Hi Hartmut!
You have changed the w32 callback to save the FPU state, this is wrong I
think!
I was wondering too wether it should be saved so GvG suggested to check
myself and I modified our winhello app...
It prints out the FPU control word, calls CreateWindow and printf the
FPU control word again.
In the callback for the WM_CREATE message (produced by CreateWindow) it
also prints the control word, then modifies it (and prints the modified one)
This is the output on windows2000:
Original FPU control word: 0x8001f
WM_CREATE: Original FPU control word: 0x8001f
WM_CREATE: Modified FPU control word: 0xa001f
FPU control word after CreateWindow: 0xa001f
Of course I have attached the program.
I am not sure but I think in the KiClearFloatingPointState which you
have added you have to set KPCR->NpxThread to NULL if it's CurrentThread
before you do the fn/xsave because it could raise a delayed FPU
exception (which will be ignored when KPCR->CurrentThread is NULL and be
delivered when the saved FPU state is restored for the thread)
I think I have made the same mistake in tskswitch.S - I am pretty sure
it has to be fixed there because we don't want a FPU exception to be
raised while we are in a cli/sti block and switching to another task.
- blight
Hi Thomas:
There are some parts of your e-mail that I can't understand but I believe you try to give some kind of solution. And yes I think is correct at some point, I was wondering once about that, to do the same with native applications as for example what is done with java applets running in the browser. Containing them to some set of files. I think that yes it would be good to prevent applications corrupting other files and such things. And in fact could be great for advanced users But ...
1 - That is not a solution for viruses, there are kernel mode virus and trojans I wonder how that can get there. At the end human intelligence can't be stopped that easy and of course the opposite also happens, ignorance could be huge. I wonder how a virus like the I love you that can be written in a couple of minutes could spread that far. Believe me that won't work.
2 - That should not be enabled by default, sometimes if you present a password to users they will get lost. That happened to some users that switched from win98 to an NT based one. That was news, and was true. With the solution you propose there will be a lot that will press the Yes. Eh I even know ppl that click whatever they please when a message box appears.
Regards
Waldo
________________________________
De: ros-dev-bounces(a)reactos.com en nombre de Thomas Larsen
Enviado el: jue 11/25/2004 12:42
Para: ReactOS Development List
Asunto: RE: [ros-dev] ReactOS and Viruses
Hi why would it be a could a idea simply becures we eliminate a lot of old viruses but we could
allso make a function theire hold all exe files from execute when they contain some strange
command f.eks the delete or format funtion or some other stuff or some kind of database and the
send a signal out
Maybe
Reactos->MaybeVirusFile(Filename,Path);
VirusApps<-TestingFile(Filename,Path);
Ekstra Idea:
And a funtion to Stop new apps from run (REGEDIT RUNAPPS etc.)
Some New viruses use that way to start all the time and the user could be asked
NEW APP STARTING UP
RUN THE APP [X] DISMISS THE APP [ ] VIRUS TEST APP [ ]
Information about file
NEWER SHOW AGAIN [X]
And then make a group of apps that run i secure mode FOLDER SECURERUN
and then make a group of apps that run i unsecure mode FOLDER UNSECURERUN
So those in SECURE can´t change the reg and delete file e.g.
don´t know just and idea
but think people should care more about getting reactos to work...
Thomas
>>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 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
Waldo
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev
Please add the following files to the bootcd:
lib\dnsapi\dnsapi.dll 1
lib\iphlpapi\iphlpapi.dll 1
lib\rpcrt4\rpcrt4.dll 1
lib\ole32\ole32.dll 1
This fixes the reboot loop FloFri was seeing with current cvs bootcds.
(ntuser/desktop.c:499) CreateDesktop: Screen-Saver
(NTDLL:ldr/utils.c:2018) Failed to create or open dll section of
'dnsapi.dll' (Status c0000135)
(NTDLL:ldr/utils.c:1357) failed to load dnsapi.dll
(NTDLL:ldr/utils.c:1819) failed to load dnsapi.dll
(NTDLL:ldr/utils.c:2085) LdrFixupImports failed for ws2_32.dll, status=c0000135
(NTDLL:ldr/utils.c:1357) failed to load ws2_32.dll
(NTDLL:ldr/utils.c:1819) failed to load ws2_32.dll
(NTDLL:ldr/utils.c:2085) LdrFixupImports failed for iphlpapi.dll,
status=c0000135
(NTDLL:ldr/utils.c:1357) failed to load iphlpapi.dll
(NTDLL:ldr/utils.c:1819) failed to load iphlpapi.dll
(NTDLL:ldr/utils.c:2085) LdrFixupImports failed for rpcrt4.dll, status=c0000135
(NTDLL:ldr/utils.c:1357) failed to load rpcrt4.dll
(NTDLL:ldr/utils.c:1819) failed to load rpcrt4.dll
(NTDLL:ldr/utils.c:2085) LdrFixupImports failed for ole32.dll, status=c0000135
(NTDLL:ldr/utils.c:1357) failed to load ole32.dll
(NTDLL:ldr/utils.c:1819) failed to load ole32.dll
(NTDLL:ldr/utils.c:1941) LdrFixupImports() failed for setup.exe
(NTDLL:ldr/startup.c:441) Failed to initialize image
--
The cheese stands alone.