CompuServe Messages

John, Welcome to the Land of the Confused (and frustrated). I'm glad it wasn't something stupid I was doing (unless we both are!), and that you can duplicate the results: "like a balloon that expands but never contracts". Exactly. I'm not able to go back to 1.3 like you. Oops! Wait a minute!! <forgot I had a 1.3 1000 setup next to me> The 1000's VD0: under 1.3 works the way I remember my 2000 setup working for years (the way we thought it would). But the filesize on the asdg.vdisk.device is 6040, and is the one I had been using until I saw an upload stating that a new device called vdisk.device of 2724 bytes was to be used after a 2.04 upgrade. I noticed that you renamed this to asdg.vdisk.device but as long as your mountlist agrees, it's probably irrelevent. I'm beginning to think that the problem is a combination of 2.04 and this newer vdisk, though I don't have any better luck with the older, 6040-byte, one. I also think, that like you, it started doing this as soon as I installed 2.04, but I wasn't looking carefully at memory useage (until I was checking the amount of ADPro's initial gobble). What's left, though, is your assertion that it doesn't behave on your 1.3 version either – I can't repeat that. [I just tried the 2724 file on the 1.3 1000, and it works OK too.] Unless there's still something in my system I haven't isolated, it must be an effect of 2.04. I wish the doc file with the 2724-vdisk archive had a signature; it claims that it fixes 2.04 compatibility problems. But I think there's one or two left. On the one hand, I'm desperate to get my VD0: back. I use it constantly, and it's clearly the best utility I've ever owned. On the other hand, I understand Perry's dumping it to the public domain, so he doesn't have to answer endless questions about it. At least, that's why I'D have done it! Lemme know if you think of anything else.