Not sure if this is being handled in another way; noticing that the Release 0 section links to the Dev 1 iso image. When d/l-g the iso image it can take about 3 days on a 56k connection. It would be possible that the iso image might be changed during this time, so the final d/l would be corrupted. Perhaps atleast two versions of the iso image can be made available, the latest one and the previous one. Then if a 56k d/l is in progess, the iso image it accesses will hopefully remain valid until the d/l completes.
Also can a checksum be made available for checking the extensive iso d/l hasn't been corrupted during d/l (since it otherwise requires burning to CD before any verification can be done).
On another matter, perhaps a comment can be made in 'Readme-news-virtuallinux.txt' about how the iso image was burnt to CD, in case there might be technical requirements for producing a runable CD ?
Again, nice work with the V-Linux; the above comments are really just for icing on the cake.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi !
Ummm, i dont think this is any real problem ..
I usually don't change the iso at all, before i release a new version that is ...
So, download it and hopefully enjoy it .. :)
One other side of it, is that i dont think sourceforge would like me to put another up there, its really big you know ..
The misleading link is only a crashed upload, i cant remove it either, something is wrong with the upload page, so i get errors every time i try .. sorry ..
CrIxZ, Vl developer
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I already posted this by mistake in another thread, but this one seems more releveant. Can you post the MD5SUM for the ISO file. I managed to download it finally, but it gives a boot error, and there really is no way of checking if the file is OK. MD5Sums please.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nice work with the V-Linux.
Not sure if this is being handled in another way; noticing that the Release 0 section links to the Dev 1 iso image. When d/l-g the iso image it can take about 3 days on a 56k connection. It would be possible that the iso image might be changed during this time, so the final d/l would be corrupted. Perhaps atleast two versions of the iso image can be made available, the latest one and the previous one. Then if a 56k d/l is in progess, the iso image it accesses will hopefully remain valid until the d/l completes.
Also can a checksum be made available for checking the extensive iso d/l hasn't been corrupted during d/l (since it otherwise requires burning to CD before any verification can be done).
On another matter, perhaps a comment can be made in 'Readme-news-virtuallinux.txt' about how the iso image was burnt to CD, in case there might be technical requirements for producing a runable CD ?
Again, nice work with the V-Linux; the above comments are really just for icing on the cake.
Hi !
Ummm, i dont think this is any real problem ..
I usually don't change the iso at all, before i release a new version that is ...
So, download it and hopefully enjoy it .. :)
One other side of it, is that i dont think sourceforge would like me to put another up there, its really big you know ..
The misleading link is only a crashed upload, i cant remove it either, something is wrong with the upload page, so i get errors every time i try .. sorry ..
CrIxZ, Vl developer
I already posted this by mistake in another thread, but this one seems more releveant. Can you post the MD5SUM for the ISO file. I managed to download it finally, but it gives a boot error, and there really is no way of checking if the file is OK. MD5Sums please.