FYI that I've done a little reordering in the 'dos/debug' directory on
Ibiblio. We actually have three versions of DEBUG here, so I wanted to
make clear which was which:


The change: Because it was the "original" FreeDOS DEBUG, we had each
version of Vojta's DEBUG as a separate directory under
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/debug/

These are the DEBUGversions:
> 0.95  1.01  1.06  1.08  1.10  1.12  1.14  1.16  1.18  1.20  1.22  1.24
> 0.98  1.02  1.07  1.09  1.11  1.13  1.15  1.17  1.19  1.21  1.23  1.25

And because Debug/X picked up where Vojta's DEBUG left off, we tracked
each version in the same directory at
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/debug/

These are the Debug/X versions:
> 1.27  1.28  1.29  2.0  2.01  2.02

And because lDebug was a variation from Debug/X, I originally put them
in a subdirectory at
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/debug/ldebug/

These are the lDebug releases:
> rel1  rel2  rel3  rel4  rel5  rel6  rel7


But I wanted to make clear which versions were which. Specifically, it
seemed unclear (to me) to have Vojta's DEBUG and ecm's Debug/X "mixed"
in the same directory, but not lDebug. So I made a new directory for
'vojta' and 'debugx'. So now each variation on DEBUG has its own
directory:


*"parent" directory:
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/debug/

vojta - Paul Vojta's original DEBUG, the original FreeDOS DEBUG
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/debug/vojta/

debugx - Japheth's Debug/X, based on Vojta's DEBUG
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/debug/debugx/

ldebug - ecm's lDebug, based on Debug/X
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/debug/ldebug/



I'll add a text file in the "parent" directory to clarify which is which.


Jim


_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to