hello David, thanks for your response.
David O'Shea schreef:
Having all of my notes on a web page that everyone can see,
and using a tool which is very quick to edit those nodes so that I am
more likely to keep them up-to-date, will be of great benefit to
everyone when I suddenly disappear from the community :)
But the page doesn't show any download link, CVS snapshots or whatever.
Ofcourse I'm having the same issue, but I don't intend to upload 1.44MB
(diskette) or 11MB every time I make a change.
Another suggestion, but probably too difficult to implement,
is to get the versions from loaded programs.
This means
'drivername in memory --> find binary --> find version string'
most programs can be run with '/?' and will show a string then.
either look for a line with 'version' or with %name_of_program%
I guess finding the binary isn't too bad, but getting the
version string would be quite hard? I think that lots of *nix-like
applications that are in CVS often have a string in them like "$Id:
..$", but even if all of the FreeDOS tools had that, it would not be
possible to read it due to the use of UPX. I guess if we added UPX
de-compression code to MEM it would cause a bit of bloat and then
folks would be unhappy about that :)
Not needed I think, see above. Also, not all drivers use UPX. Common
examples are HIMEM and EMM386, which are both a commandline program and
driver at the same time, and therefore are incompatible with UPX.
Michael and Tom use Tom's 'SY3PACK' compressor instead of UPX
@echo off
date /d > report.txt
time /t >> report.txt
VER /R >> report.txt
SET >> report.txt
ALIAS >> report.txt
for %%x in ( config.sys fdconfig.sys autoexec.bat ) do if exist \%%x
type \%%x >> report.txt
for %%x in ( himem.exe emm386.exe ) do %%x /? >> report.txt
mem /c /d /x >> report.txt
pcisleep.com -L >> report.txt
echo Report file "report.txt" created in current directory.
I guess that having the version information is useful when
people are asking for support, though, as you could see what versions
of some drivers/TSRs they had loaded. Unfortunately although MEM
shows the versions of HIMEM and EMM386 which are both pretty important
ones, we don't actually get the real version numbers :) Perhaps we
could include in the distribution a batch file which gathers
information useful for providing technical support, e.g.:
having the version number of the freedos distribution should be
sufficient, but to my knowledge we don't keep info of "which version of
which program went into FreeDOS distro named 'X', released at date 'Y'"
I'm not sure VER /R is able to retrieve the kernel string (including
version number and compile date).
I would appreciate an interim non-public release of MEM to test things.
My batchcode and experiments often have the habit of exposing
bugs/issues in programs by accident.
Bernd
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
