Aitor Santamaría Merino wrote:
Hi there,
I have been listing and analyzing the bugzilla bug list, or at least,
until bug 1916, and I'd like to share this information with you. I have
grouped the bugs, and will expose them in three mails.
In this first mail I'd like to write about two groups of bugs: one,
the bugs that have been already fixed somewhere, or they are to be
fixed with the versions in CVS or devel (or even inlined in the
bugtrack). Alternatively, some of them would need to be CLOSED because
of not being true bugs.
Provided that all of the developers should “FLUSH” the CVS and devel
environments before 1.0, I’d say these bugs can be closed.
I’d like to ask for these bugs to be CLOSEd, or alternatively, could you
please explain if there’s a good reason not to?
FreeCOM: 595, 1687, 1773,
can be closed once FreeCom 0.84 is officially released (or sooner I
suppose since the fixes are committed and will be in next release).
>1720,
looks like its not fully fixed yet
>1849,
not strictly a FreeCom bug and the kernel aspect is a work in progress
>1886 (fixed in bugzilla),
need to spend some quality time FreeCom and commit this along with
several other patches before closing
>1905
a kernel bug, definitely fixed in dev branch, need to verify that stable
either doesn't have the bug or fix committed there as well before closing
>1859,
this bug needs to stay open until we are sure there are no remaining
device driver loading issues, and based on reports from Bernd, this is
not the case -- the actual reported bug is fixed, but the driver loading
issue may be a related/similar type of issue
Kernel: 1049, 1758, 1814, 1821, 1828,
needs re-testing or at least updated to reflect current status; but if
fixed/works can be closed
>1768, 1813, 1826,
can be closed, though I'm waiting until merged into stable to do so
>1874, 1879
can be closed as I believe both are currently resolved
FDISK: 1195, 1827
looks fixed and closable unless someone has more to add or Brian wants
them still open for some reason
INSTALL: 1293,
I would have to check latest candidate release, but for what I want, I
don't think its implemented; but this is not a blocker bug only an
enhancement reminder
1915
no idea, I think Bernd has a better understanding if this bug can be
closed or not
EMM386: 1891
EDIT: 1892
????
Secondly, there's a large list of bugs that were found or tested with
very old versions of the components (mainly Kernel, FreeCOM, INSTALL and
EMM386), or perhaps there was a partial/total fix, and it was never
re-tested. In some cases, the person who opened the bug is unreachable.
I would like to ask here (and in freedos-user) where you can have a look
with the LATEST versions of everything, and see if the bug confirms, or
gets closed.
Any information you could provide is welcome, otherwise I'll give a
couple of days, and pass the list to FreeDOS User's list, to give the
chance for someone to say something about them. Here it goes:
423: KERNEL: Failure to notice write failure, on quicken 3.5 for DOS
998: FORMAT: Format drives >4GB
1076: FreeCOM: PowerBasic IDE 3.5 having troubles with environment
variables
1538: INSTALL: Is this still true several versions later?
1658: KERNEL: Problem with the file browser of a very specific Norton
GHOST version
1672: FreeCOM: Distinction of grey/non-grey arrow keys in FreeCOM
(however they should behave all the same?) MORE INFO REQUIRED
1689: FDXMS: ver 0.92 not loading properly? (can someone confirm?)
1706: KERNEL: Indenture game and problem with keys: seems to be a
non-FreeDOS bug?
1738: KERNEL: Drive Z: not being possible, a problem to occur with the
rest in such a case
1753: KERNEL (EMM386 involved?): Invalid opcode when logging to Netware
16-bit client
1755: INSTALL?: Problem when booting, possibly metakern involved (?)
1778: EDIT: Edit to close too many windows without confirmation
1779: FreeCOM: Graphical corruption with DJGPP, possibly a non-FreeDOS
bug (?)
1786: INSTALL: In some circumstances, Install abort may lead to
inconsistencies, some core files copied but not unzipped…
1788: FDXMS286: lockup on application exit
1791: EMM386: behaves badly under WirtualPC. Seems to be related with
tuning up EMM386 correctly, so perhaps it has been fixed with the newest
version of EMM386
1793: KERNEL: Problem executing GREP from RHIDE/DJGPP (system lock)
1797: KERNEL: Crashes running in ontracked HDs without ontrack, but
unknown wether other DOSes do. I’d say not a FreeDOS bug
1800: SYS: ATA systems with 16MB flash memory, crash at boot (in the
bugtrack mentioned to be possibly a SYS bug)
1806: EMM386: Problem with Game Wizard 32 Pro (probably EMM386 not
correctly tuned)
1810: Kernel: cannot boot from partition made with Ranish Partition
Manager. I seem to recall having this problem in the past too, but not
related to FreeDOS, but the way Ranish Partition Manager creates the
partition. I would say a non-FreeDOS bug
1811: INSTALL/UDMA: Crashes with divide by 0, in all options except for
2. Probably fixed in UDMA, anyway installation has changed a lot, and we
are now using XDMA. After checking it has been fixed in UDMA, we could
simply close this bug
1825: Kernel: Problems with file sizes and clusters on OrCAD SDT 386 1.21
1830: SHSUCDX: File corruption on read from partly unreadable cdrom
without error message, already fixed in SHSUCDX?
I would really appreciate if anyone who could would test and report if
any of the above are still valid.
1842: FreeCOM: problem with DOS=UMB, probably lately fixed
need to examine this one more
1845: Kernel: disk access failure on ultimatebootcd
1847: EDIT: Small bugs, do these occur in the lastest version (Eric’s)
that is being distributed?
still valid? I don't know
1854: Kernel: TurboC++ fails to run
I can test this one, just haven't yet. Maybe I'll finally put a
debugger on my test computer (you can do a lot with well placed printfs :-)
1869: EMM386: Problems with SECOND REALITY
1870: SYS: disk drive not recognized and hanging GRUB
1873: EMM386: Just another possible mis-tune of EMM386 with Stargunner
???
1900: FreeCOM: Out of memory loading STRINGS
I never could reproduce except when I had corrupted my system, so
problem a symptom of some sort of corruption, but I can't say if it
is/was kernel/FreeCom and if it is fixed or masked
1916: EDIT: Some weird problem on key combinations, present in latest
Eric’s version?
haven't had a chance to test this one
That was all for the time being, relpies? :-)
Aitor
Jeremy
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
