Here you can discuss ReactOS related topics.
Moderator: Moderator Team
Yeah! No more hiding this by putting a fully blue background without wallpapergabrielilardi wrote:Commit by rharabien :: r51322 reactos/dll/win32/shell32/ (desktop.c shlview.c): (link)
Return 1 in WM_ERASEBKGND when desktop is painted
Fix background for desktop icons and their labels
Moreover fixes explorer_new background
Maybe not extremely important but the visual impact is immense, it is that step from windows 9x to XP all over again.
Personally I'll add here what I think end users will notice most. Latest commits don't fall into that category imo.aerospaced wrote:has everyone quit on this? I do not see any really new post.
ReactOS is a living creature, rather, it's a baby, as all the little ones, it changes all the time, it grows and matures every day some days more some days less. You can follow the SVN activity in the homepage or the ros-diff mailing list to see all the work that's being done behind the scenes.
Update: I forgot, SafeMode (F8 at startup) has been implemented with a patch made by AdamEvil in revision 52132. Also, recently, aicom has been working hard on Plug and Play (this will help memory mass storage support once USB branch will be merged back) and network fixes (more stability).
I think Windows XP uses PAE support, even though it has the 4GB barrier for compatibility, just so it can use the hardware buffer overrun protection (No Execute). One thing I would love to see would be maybe a registry switch (once PAE is written) that could be used to open up more of the memory. I imagine there are some well-behaved drivers and adapters out there.gabrielilardi wrote:Commit by rharabien :: revision 52234 reactos/boot/freeldr/freeldr/ (6 files in 4 dirs): (link)
Return const pointers instead of converting them
Fix MemoryMapSizeInPages calculation
Don't use pages after 4GB limit on x86 (PAE is not supported yet)
Should fix starting ROS on 4GB machines See issue bug 6031 for more details.
Anyway, I assume these changes above will improve stability and being able to run on machines it is hanging on.
Maybe with these updates you could give a short one-sentence summary of why it's a good fix?gabrielilardi wrote:Commit by cgutman :: revision 52278 reactos/lib/fslib/vfatlib/vfatlib.c: (link)
Determine the correct FAT type based on the size and offset of the partition if the current type is not a FAT type (another FS type or unformatted)
Formatting a floppy, blank partition, or other non-FAT formatted partition from within ROS no longer fails
I think this one is pretty obvious: If you have a NTFS, EXT2, EXT3 or any other partition now you can format it to FAT. Until now You could just format a FAT partition, since now you can format ANY partition to a FAT partition.FlyingIsFun1217 wrote:Maybe with these updates you could give a short one-sentence summary of why it's a good fix?
Please if you have suggestions or doubts, open a thread, but keep this one just for "Fix of the Week" commits.
Users browsing this forum: Google [Bot] and 3 guests