[Coco] Mess and 242 error

[Dean Leiber]

>Robert and I came to a similar conclusion.  I've run more traces than I
>can count and the orders to corrupt the sector definitely appear to be
>issued by the RBF module.  Apparently, somehow these corruptions occur
>because a sector gets written to but is somehow incorrectly cached and
>subsequently written to the disk.
>
>> I'll try grabbing an older version of Nitros and see if it goes away.
>
Well since the Nitros stuff has been moved from sourceforge and hasn't 
appeared at the Nitros page yet, I'm outta luck there. However I got 
NitrOS to work well enough to create a OS-9 LVII boot disk from various 
patched modules I had on disks. Don't ask what kind of frankenstein this 
must be, however I could get it to boot. I haven't tried the disk to disk 
copy since I've been more interested in getting the Virtual HD to work, 
but I was still getting 242 errors. 

The problem as it seems to me, is that the VHD is a small empty file and 
expands as you write to it. For some reason when I try to write to the 
VHD I get 242 errors and bad files. After I delete them and try again 
they appear to copy correctly because the file size of the VHD has 
already been increased by the first copy. If you do a format of the VHD 
and request a physical verification it works ok for a few sectors and 
then you get 242 errors, but it does increase the VHD file size (makes 
sense.) I only let it get to 26M before I stopped it and reformatted with 
no physical verification (which has no problems.) Now, I no longer get 
the 242 errors when I copy files over to the VHD, but I suspect if I get 
over the 26M, the problem will return. This could be a MESS problem, 
however I suspect it is some kind of interaction with MacOS (9.x). Maybe 
its the way the cooperative multitasking on MacOS works, possibly some 
extension, or the phase of the moon ;-) Does anyone else using MESS on 
Win or unix have this problem? Any Mac users have this problem? Maybe its 
just my setup?

Dean