dillon@CORY.BERKELEY.EDU (Matt Dillon) (01/28/88)
>I am having slightly different problems with VD0:. When runing with 2.5M >I set vd0: size to 2M then fill it most of the way up. Everything works fine >but VD0: does not survive a warm boot. Anyone out there have any experience >with this?? Simply because the OS sticks stuff in FAST memory on boot. VD0: will use only FAST memory or only CHIP memory. Thus, when you fill up VD0: almost to the brink you are filling up just about ALL your fast memory. On reboot the stuff near the beginning gets overrun. Solution (as per Perry's instructions... amazing how many people didn't read them!): Make VD0: smaller ... as in 1.5 Megs. -Matt
cjp@antique.UUCP (Charles Poirier) (01/30/88)
>In article <1335@cg-atla.UUCP> nelson@cg-atla.UUCP (Blake Nelson X7083) writes: >>I am having slightly different problems with VD0:. When runing with 2.5M >>I set vd0: size to 2M then fill it most of the way up. Everything works fine >>but VD0: does not survive a warm boot. Anyone out there have any experience >>with this?? >> >>Never had any problems using 1M VD0: Here's the scoop. 1) Never use FastMemFirst (was called SlowMemLast) when you plan to use VD0:. A2000's, A500's with the plug-in RAM/clock, and certain "inside"- type memory boards have memory which starts at address C00000 hex. Exec's method of recognizing whether the system contains C00000 memory (after certain types of crash - "recoverable alert" I think it is) involves changing some bytes in that memory. VD0: uses last mem first, thus you need fast mem last, so VD0: won't get stepped on during warm boot. 2) Don't request the full amount of expansion mem for VD0:. You have to leave enough (120K or so) for the operating system to load into. It uses mostly FAST mem when it is available. If you request more FAST mem than is actually free, the spillover (when needed) will either come from C00000 mem (if present) which is a no-no, or from CHIP mem. Mixing CHIP and FAST mem in VD0: doesn't work, for as-yet-unrevealed reasons. 3) If all you have is CHIP mem or CHIP mem plus SLOW mem, you have to settle for mem type 3 (CHIP). Of course this eats up your supply of chip mem. Expansion memory is highly recommended by most who have tried it. 4) Make sure that enough free memory is really available in the system when you put things in VD0:. AmigaDOS somehow fails to notice VD0:'s error indication if it couldn't alloc enough memory, thus your file will be silently truncated. 5) Observe these warnings, and VD0: should give you trouble-free service. Of course it's possible for runaway processes to trash any region of memory, but what do you want for $10 (suggested donation)? Bearing no commercial affiliation with anybody, -- Charles Poirier (decvax,ihnp4,attmail)!vax135!cjp "Docking complete... Docking complete... Docking complete..."