Page 1 of 6

Progress to 0.3.8 and beyond...

Posted: Thu Dec 11, 2008 5:26 am
by nute
How is the work to squash the video bugs that plague Firefox and Thunderbird coming along?

What will 0.3.8 have that 0.3.7 doesn't have?

Maybe it's too early to tell.

When will newsletter 50 come out?

Freedos has free defrag that is supposed to be Fat32 compatible, can that be ported to ReactOS?

Re: Progress to 0.3.8 and beyond...

Posted: Thu Dec 11, 2008 1:04 pm
by The123king
nute wrote:Freedos has free defrag that is supposed to be Fat32 compatible, can that be ported to ReactOS?
http://en.wikipedia.org/wiki/UltraDefrag
http://ultradefrag.sourceforge.net/
Any good? I'll test it on my ReactOS install tonight.

EDIT: causes BSoD. As useful as a chocolate fireguard ATM :|

Re: Progress to 0.3.8 and beyond...

Posted: Thu Dec 11, 2008 1:27 pm
by Blackcrack
Hy,

http://sourceforge.net/projects/opendefrag/

humm... take a look here: jkDefrag
and many Gui's jkDefrag Gui's , Portable , Gui too , jkdefragstarter , JkDefragTWGUI

and this is intresting too : S.M.A.R.T. = smart.exe
whant be cool to have more informations on Driveinformations :mrgreen: only 32K !!
or some crewl informations klick me

and i think, this Link whant be nice for the Developers

best regards
Blacky

Re: Progress to 0.3.8 and beyond...

Posted: Thu Dec 11, 2008 4:17 pm
by Elledan
Depending on when 0.3.8 will be released there'll be (partial) USB support.

Re: Progress to 0.3.8 and beyond...

Posted: Thu Dec 11, 2008 6:50 pm
by Blackcrack
Hy Elledan,

thank you very mutch for you info :D

best Regards
Blacky

Re: Progress to 0.3.8 and beyond...

Posted: Fri Dec 12, 2008 4:18 am
by nute
I couldn't get ultradefrag to work either. I wonder when the storage implementation will be compatible with it?

Re: Progress to 0.3.8 and beyond...

Posted: Fri Dec 12, 2008 7:01 pm
by Haos
@nute

When someone makes it compatible. Got any volounteers?

Re: Progress to 0.3.8 and beyond...

Posted: Sun Dec 14, 2008 1:03 am
by nute
I've tried ultradefrag in SVN release, the last one being 38039-dbg, no luck.
This last round it complained about a memory access error. Is someone
working on filesystem support in ReactOS?

Re: Progress to 0.3.8 and beyond...

Posted: Sun Dec 14, 2008 1:44 am
by hto
nute wrote:Is someone working on filesystem support in ReactOS?
Yes!

Re: Progress to 0.3.8 and beyond...

Posted: Sat Dec 27, 2008 5:06 am
by nute
I've found that installing SVN releases without formatting allows for a sort of upgrade to 0.3.7.
Still, even applying today's SVN release the video bugs in Thunderbird and Firefox are still
very apparent. I assume that ultradefrag still doesn't work. What is the ETA on being able
to defragment fat on ReactOS? What is the ETA on squashing these video bugs?
By ReactOS 0.3.8, wil these problems be addressed or not? If not by 0.3.8, when will
the video corruption issue and problems using ultradefrag be resolved?

Re: Progress to 0.3.8 and beyond...

Posted: Mon Dec 29, 2008 1:25 am
by Haos
No. I havent seen any ultradefrag bug in bugzilla. Dont expect any bug being fixed before bug report is submitted. As for progress, how many bugs did you submitted? Do you really expect everyone will run and look for stuff you havent even bothered to report? As for me, i dont use (nor want to use) TB or ultradefrag, so i dont care if it works or not. You want something to be done? Contribute instead whining on forums, as you usually do.

Re: Progress to 0.3.8 and beyond...

Posted: Mon Dec 29, 2008 1:32 am
by Z98
Haos, civility. I do NOT want to deal with another fight on the forum.

nute, it should be pretty evident by now that asking for ETAs won't get you an actual answer. No one is going to actually offer a date.

Re: Progress to 0.3.8 and beyond...

Posted: Mon Dec 29, 2008 6:53 am
by nute
First off, I don't see how asking if anyone has an ETA, estimated
time of arrival, for a fix is whining.

Second off, I don't want to report a bug that has potentially already been
reported. I have screenshots of ultradefrag being manuevered to and
failing, but I don't want to post them in a bug report if someone else has
already done so.

As far as asking for an estimate, I'm worried about how long these
bugs are going to stick around. For example, if 0.4 comes out after
0.3.8, does that mean that the video bugs will be squashed? Could
it be possible for these bugs tol be around till 0.5.0?

There's no road map anymore to go by. There's nothing to go by.
I could get really patient and forget about ReactOS for 6 months.
Will these issues be resolved by then? I have no idea.

I'm assuming that the video bugs are caused by problems
in the memory manager which apparently needs to be rewritten.
I read in newsletter 50 that a rewrite is being avoided. Is that
sensible?

I've tried to look into SVN to see what is being fixed and what
problems are being found, easier said than done.

I wish I could help. I have formal training in C and C++
programming.

As far as Haos's, "I don't care if Ultradefrag works," that is a ludicrous
comment. Defragmenting the file system is a fundamental operation.
Surface scanning for bad sectors is also a fundamental operation that
an OS needs to support. Both of these file system activities fall under
maintenance and optimization.

Re: Progress to 0.3.8 and beyond...

Posted: Mon Dec 29, 2008 8:46 am
by hto
nute wrote: Second off, I don't want to report a bug that has potentially already been reported. I have screenshots of ultradefrag being manuevered to and failing, but I don't want to post them in a bug report if someone else has already done so.
Do not hesitate to file bug reports. If the same bug was already reported, one simply will be marked as a duplicate of other.

But please first search through existing bugs before filing a new one.

Add information which you think is relevant. Versions of software, screenshots, debug logs. Be prepared to provide more info at request. Do not report several different bugs in one report.

http://www.reactos.org/wiki/index.php/File_Bugs
As far as asking for an estimate, I'm worried about how long these bugs are going to stick around. For example, if 0.4 comes out after 0.3.8, does that mean that the video bugs will be squashed? Could it be possible for these bugs tol be around till 0.5.0?
Some bugs remain unfixed for years. Generally, nobody can tell in advance how long it will take to fix a particular bug.
There's no road map anymore to go by. There's nothing to go by. I could get really patient and forget about ReactOS for 6 months. Will these issues be resolved by then? I have no idea.
Remember that ReactOS is developing by volunteers in their free time.
I'm assuming that the video bugs are caused by problems in the memory manager which apparently needs to be rewritten. I read in newsletter 50 that a rewrite is being avoided. Is that sensible?

[…]

Defragmenting the file system is a fundamental operation. Surface scanning for bad sectors is also a fundamental operation that an OS needs to support.
Do not think that the developers are dumb asses. :) They probably know better what they should do.
I wish I could help. I have formal training in C and C++ programming.
Thanks. The help is always needed.

Re: Progress to 0.3.8 and beyond...

Posted: Tue Dec 30, 2008 12:04 am
by Heis Spiter
nute wrote:Defragmenting the file system is a fundamental operation.
Surface scanning for bad sectors is also a fundamental operation that
an OS needs to support. Both of these file system activities fall under
maintenance and optimization.
Tell that to extX users...

Anyway, about defragmentation, it's not yet possible in ReactOS, and won't be before a while (IMO) because it needs advanced features (from the FSD) and our fastfat driver isn't advanced enough (IIRC). But maintenance must be already possible, with the work Aleksey did with vfatlib.