26 Jul
2007
26 Jul
'07
10:05 a.m.
Dave Dunfield said:
A few days back I posted ImageDisk 1.17 to the site,
and it's just
been reported (and confirmed) that it had a bug which causes it to
write images incorrectly (fortunately it appears to read them
correctly).
I've corrected the problem and updated the package - if you have
downloaded 1.17 before today, please download it again.
I've also restored Imagedisk 1.16 to the site, listing it as the
last known stable release, so that people won't be left hanging if
(when) something like this happens again.
...snip...
It's annoying to invest time to do someone a favor (that they asked for) only
to find out that they consider their own time too valuable to follow up their
part - I'm sure Chuck will tell me that this is one of the reasons he finally
told people to shove Teledisk beyond the reach of solar illumination...
</rant>
If anyone can help check out 1.17, that would be much appreciated.
I for one am mighty grateful for the actual usefulness of IMageDisk and want to just
through my .02 cents into the hat. It's a shame that your recent 'extra'
efforts weren't/aren't properly acknowledged, and that the follow-through from the
other side hasn't +happened.
Still, please regard me as an appreciative user of IMageDisk. In recent months, I have
processed nearly 450 floppies from my old MS-DOS days, as well as a set of CP/M and other
development tools for my quite obscure, but not particularly noteworthy, Novell Data
Systems 2010, a Z80A-based machine. I was becoming very, very nervous about the stability
of those old NDS 2010 diskettes (not used since c.1982), and breathed a huge sigh of
relief when I got all of those floppies imaged and burned to CD-ROM.
Unfortunately, I've just finished my 'imaging project' using IMD 1.16, so I
don't have much to test with 1.17. Still, my hand is extended to you for producing,
*and maintaining*, such a useful tool for vintage collectors. Many thanks!
- Jared