leue@galen.steinmetz (05/17/89)
I've noticed what appears to be an ugly bug in the "Disk Tools" application that comes with the Semantec Utilities for Macintosh (SUM) product. (Sorry, I don't have the version number with me, but I just bought it a month or so ago.) If you use the "Read Absolute Sector" menu item while editing a Volume and type in a sector number greater than 32767, you get an "I/O Error", with a negative sector number. Clearly, someone used a 16-bit integer to store the sector number. Ouch!! My puny little 30-meg HD has more than 64,000 sectors. This would be a good one to fix, if anyone from Semantec is listening. BTW, Other disk editors (Fedit +, etc.) have no problem reading sectors past 32767. -Bill Leue
steve@violet.berkeley.edu (Steve Goldfield) (05/17/89)
In article <13816@steinmetz.ge.com> leue@crd.ge.com writes:
#>I've noticed what appears to be an ugly bug in the "Disk Tools"
#>application that comes with the Semantec Utilities for Macintosh (SUM) product.
#>(Sorry, I don't have the version number with me, but I just bought it a
#>month or so ago.) If you use the "Read Absolute Sector" menu item
#>while editing a Volume and type in a sector number greater than 32767,
#>you get an "I/O Error", with a negative sector number. Clearly, someone
#>used a 16-bit integer to store the sector number. Ouch!! My puny little
#>30-meg HD has more than 64,000 sectors.
#>
#>This would be a good one to fix, if anyone from Semantec is listening.
#>BTW, Other disk editors (Fedit +, etc.) have no problem reading sectors
#>past 32767.
#>
#>-Bill Leue
I've found Symantec very forthcoming in fixing bugs. I had
a version with bugs in the installation procedure; they
sent out corrected disks right away. Have you tried phoning
their support number?
Steve Goldfield