CompuServe Thread

#RAM CRASHES AMI1000

3 messages in this thread
#97141From: brian jayneDec 7, 1987 9:39 AM
I own an AMI1000 which I use primarily as a component in a small home music studio. Only recently I upgraded to 1.2 kick & boot, and after doing so, I began to have problems copying data in and out of ram: If I type "copy ram:#? df1:" I get "Unrecognised command copy", and subsequently, any command I type is unrecognised. I have to reboot. This never happened under 1.1, btu perhaps I have a bad chip, and the purchase of the 1.2 software was only coincidental timing? Anyone have similar experience?
#97168From: Don Curtis/SYSOPDec 7, 1987 2:34 PM
Brian, Have you assigned C: anywhere, and is the COPY command in that place? If not, does the copy command work anywhere? Don
#97671From: Marlene ZenkerDec 10, 1987 3:37 PM
Brian, somewhere along the way you've assigned copy to a place that copy doesn't reside. For eg. if in your startup-sequence you've copied df0:c/copy ram: then you need to assign ram: as the place to look for the copy command. You may be doing the assign to ram: before the acutal copy of the 'copy' command to ram: and now DOS can't find it. If you are creating a ramdisk or a recoverable ramdisk like VD0: in your startupsequence do something like the following: makedir ram:c copy df0:c/copy ram:c assign c: ram:c copy all other c commands to ram:c that you use frequently. The reason for copying 'copy' first to ram: then assigning the c directory to ram: is so that you don't have to keep accessing the c directory on your workbench disk to load the copy command and it speeds up the copying procedure. Marlene