jms@antares.UUCP (joe smith) (09/03/88)
Both people that said KickStart doesn't clear all of RAM were running ASDG's VD0 software on ASDG's RAM hardware. The ASDG memory board has a write-protect circuit that prevents KickStart from destroying the VD0 ram disk. If you use the recoverable RAM disk software on a non-ASDG memory board, there is nothing to prevent KickStart from clearing VD0. -- +-----------------------------------------------------------------------------+ | TYMNET: JMS@F29 UUCP: {ames|pyramid}oliveb!tymix!antares!jms | | INTERNET: JMS%F29.Tymnet@Office-1.ARPA PHONE: Joe Smith @ (408)922-6220 | +-----------------------------------------------------------------------------+
limonce@pilot.njin.net (Tom Limoncelli) (09/04/88)
In article <144@antares.UUCP> jms@antares.UUCP (joe smith) writes: > Both people that said KickStart doesn't clear all of RAM were running > ASDG's VD0 software on ASDG's RAM hardware. The ASDG memory board has > a write-protect circuit that prevents KickStart from destroying the > VD0 ram disk. If you use the recoverable RAM disk software on a non-ASDG > memory board, there is nothing to prevent KickStart from clearing VD0. Really? I never heard that one. In all my years of using ASDG boards and software I never remember hearing that. Could someone from ASDG please make a statement about that? IMHO, it doesn't sound too real. Tom -- Tom Limoncelli -- Drew University, Box 1060, Madison, NJ 07940 TLimonce@Drew.Bitnet -- limonce@pilot.njin.net -- VoiceMail (201)408-5389 Drew College of Liberal Arts: male/female ratio: 2:3 student/pc ratio: 1:1 "The opinions expressed are mine... just mine."
stellrec@deneb.cis.ohio-state.edu (barry stellrecht) (09/07/88)
I have also use ASDG's VD0: with a Micron chassis & 2Meg ram board, and it has survived changekick every time I did it. (The Micron does have a write protect _jumper_ but that is only for a memory test program, and I've never used it)
vkr@osupyr.mast.ohio-state.edu (Vidhyanath K. Rao) (09/08/88)
Re VD0: included with the Micron board: is this the original or a modified version? For example, this seems to avoid using $C00000-memeory if I do FastMemFirst.
mlelstv@faui44.informatik.uni-erlangen.de (Michael van Elst ) (09/09/88)
In article <21346@tut.cis.ohio-state.edu> stellrec@deneb.cis.ohio-state.edu (barry stellrecht) writes: > >I have also use ASDG's VD0: with a Micron chassis & 2Meg ram board, and it has >survived changekick every time I did it. (The Micron does have a write protect >_jumper_ but that is only for a memory test program, and I've never used it) Hello netpeople, there is a simple explanation for this effect. A kickstart change does always a coldstart of exec. Then chip-memory is cleared during the memory test. Chip-memory is too partially overwritten at boot time because you need some chip-memory buffer for the disk and some memory for the system stack. Ranger-Memory (addresses $c00000 up to $dbffff) are not cleared on coldstart but I have not seen a memory expansion there for the A1000. With other memory expansions you are always 'expansion-memory' (addresses $200000 up to $9fffff). Simple expansion cards (added with AddMem or a similar program) are not cleared at all except for the AddMem program that might write into this memory to check if the memory is available. I know of a version of AddMem that does this type of destructive memory test. Autoconfiguration cards may have a selftest program in an EPROM that clears memory but I haven't seen anyone. When VD0: is startet, that is after a MOUNT and the first access to it, all free memory is searched for valid data and then allocated (I think via AllocAbs call). If something has overwritten part of the VD0-Disk you get a clean one. So all is lost. Conclusion, usually VD0: survives everything if it is located in external memory and is started as the first command in your startup- sequence. VD0: in CHIP only survives warm starts (i.e. ExecBase is not corrupted). Michael van Elst E-mail: UUCP: ...seismo!unido!fauern!faui44!mlelstv E-mail: UUCP: ...uunet!unido!fauern!faui44!mlelstv <- when seismo ceases operation
mp1u+@andrew.cmu.edu (Michael Portuesi) (09/21/88)
mlelstv@faui44.informatik.uni-erlangen.de (Michael van Elst ) writes: > Ranger-Memory (addresses $c00000 up to $dbffff) are not cleared on coldstart > but I have not seen a memory expansion there for the A1000. The A1000 I am typing this message on contains an Aminetics "Squeeze-RAM" board that contains 1 meg of memory at $C00000. The Michigan Software "Insider" board also does the same thing. I don't recommend any type of expansion device that fits inside a 500 or 1000. I am living in mortal fear that the hard disk interface I purchase in the future won't work with the Squeeze-RAM board due to freaky timing problems similar to Leo's problems with his Ronin accelerator card. --M