| Title: | AMIGA NOTES |
| Notice: | Join us in the *NEW* conference - HYDRA::AMIGA_V2 |
| Moderator: | HYDRA::MOORE |
| Created: | Sat Apr 26 1986 |
| Last Modified: | Wed Feb 05 1992 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5378 |
| Total number of notes: | 38326 |
Does anyone who has an Amiga 500 have the ASDG-Ram working correctly?
i.e. recovers from soft boot! I've read the documentaion and tried
everything I could think of but to know avail! I have an Amiga 500
with the A-501 option. It never seems to see that VD0:c already
exsists! H E L P!
Tom
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 960.1 | Works fine | OASIS2::BERNARD | John Bernard DTN 288-6622 | Thu Dec 10 1987 18:27 | 22 |
YUP! I have an A500 with 1 meg using the ASDG recoverable Ram. Did you put the ASDG.Ram.Device in Devs:, Place VD0: in the mountlist, actually MOUNT VD0:, to recognize the c: directory on VD0: after a reboot I use, within startup-sequence, ;------------ VD0: -------------------------------------- MOUNT VD0: ; mount the device PATH VD0: Add ; add to search list CD VD0: ; make it current dir for now IF EXISTS VD0:C ; Check to see if VD0:C exists PATH VD0:C Add ; if it does, add to search path END IF ;-------------------------------------------------------- If you're still having trouble, I'll post my mountlist, startup-sequence and a cmd file that creates/loads the VD0:C directory. -john- | |||||
| 960.2 | HPSTEK::SENNA | Thu Dec 10 1987 19:03 | 10 | ||
My sequence is not exactly the same, but I used a workbench disk
that someone else has and works fine on his system.... But his system
is a 1000. Could this be a source of the problem??
I'll try loading the command files down to my workbench along with
ASDG stuff to see if it makes a difference!
Thanks!
| |||||
| 960.3 | make sure size set properly in the mountlist!!! | MVCAD3::BAEDER | Thu Dec 10 1987 21:03 | 13 | |
check the size of the ramdisk...if its not set right, this could
be the answer...ie does the 100 (which you got it from) have more
than 1 meg of ram!!! There are some pretty explicit directions
on setting the size...if they are not followed, you can corupt the
"magic bits" that say everything in vd0: is a-ok, and cause it to
be re-built...this is the way the deleteramdisk function does its
thing...it just munges the bits...
so...check out the instructions...ie RTFM..;-) (i know, that takes
all the fun out of it....
good luck....scott.
| |||||