CompuServe Messages

I was vaguely aware that something like this remapping by the drive could happen but kinda hoped there was an easy way around it. As it turns out, I got lucky. The problem appears not to have been hardware but with the utility I was using. See if this makes sense to you. I'm doing a copy using UtilMaster (v.66) and it bombs out with and address error on a very long pathname (I'm now able to duplicate this back on the 506 so the SCSI is cleared). ..Now comes the disturbing part.. IF I'm doing some other disk operation in another task (like an unzip), Sometimes the disk gets left in a state that won't validate on reboot. I just ran your HDTest and found 0 errors which is nice since as I previously indicated the SFMT routine did not work with my 2090A/Quantum105. This UtilMaster problem is avoidable and generally recoverable so I'm breathing easier again but I'm left a bit worried that this disk is that susceptible to software problems. Oh and one last related question. On hard power up (external switch to entire bench) the DH2 partition of the SCSI isn't mounting but on a reboot it comes up fine. Do these SCSI drives take that long to register and should I somehow/where slow down my startup sequence to give it time to do so? Thanks for all the help again. lGlamb