Forum unknown
· Programming
#arc & startup
7 messages in this thread
can anyone tell me what might be wrong with my startup sequence? I'm using
Byte by Byte's 2 meg ram expantion on a A-500 and I have been getting
software failures left and right..Also is there an arc program that will
let me select which files I want to arc by selecting them with the mouse
instead of typing in each and every file. It needs to arc 50 or more files
at once( for investment downloads that get put up on our board).Am I asking
too much,If so,let me know. I can do 12 at a time with diskman but that
becomes a bit time consuming…..
if exists c:FACCII
if exists c:runback
runback -5 c:FACCII 256
else
run FACCII 256
if exists c:wait
wait 5
endif
endif endif if EXISTS sys:system
path sys:system add endif if EXISTS sys:utilities
path sys:utilities add endif mount VD0: if exists VD0:lastboot endif
LoadWb failat 30 cd s: runback clock cd c: SetClock >NIL: Opt load Date
setmap usa1 endcli > nil:
I have been using Access 1.29 most of the time along with diskman if that
helps. It would be nice to have 3 meg of reliable ram….
Kurt, first of all….place the MOUNT VD0: at the top of your
startup-sequence, ie: the first command. That will ensure a non-corrupted
VD0:. If you want to ARC many files, you can do a few things. You can
list all the files you want to ARC on the command line. This is tedious
when you have many files though. IF all the files you are going to ARC are
in their own directory, you can "ARC a File.ARC dfx:[path/]#?". If the
files are in the root directory of a device, you would use "ARC a File.ARC
dfx:#?", if in a sub-directory then "ARC a File.ARC dfx:Dirname/#?", where
dfx: is the device, Dirname is the directory name, and #? is a match for
any file. You can use any pattern matching wild card, I used the #?
because it is all encompasing.
Thank you, thank you thank you!!!!!!!!!! That is when everything seemed to
go down is one I was using Vd0:… And yes everything is in its own dir
with the same .dat This is great getting an answer to our somewhat stupid
questions so fast love these Amiga's…..By they way, whose winning the
os/9 vs. amy os war looks like they both have alot to offer from our end,
BUT it will be a cold day in H**l before a rad shack machine is sitting on
my desk
Great Kurt, glad I was of help! But, never feel tat your questions are any
bit stupid. There are no stupid questions, and never feel intimidated. All
of us are here to learn, and help others. If you have any questions at all,
don't hesitate to ask! 🙂
Great Kurt, glad I was of help! But, never feel tat your questions are any
bit stupid. There are no stupid questions, and never feel intimidated. All
of us are here to learn, and help others. If you have any questions at all,
don't hesitate to ask! 🙂
Thank you, thank you thank you!!!!!!!!!! That is when everything seemed to
go down is one I was using Vd0:… And yes everything is in its own dir
with the same .dat This is great getting an answer to our somewhat stupid
questions so fast love these Amiga's…..By they way, whose winning the
os/9 vs. amy os war looks like they both have alot to offer from our end,
BUT it will be a cold day in H**l before a rad shack machine is sitting on
my desk
Kurt, first of all….place the MOUNT VD0: at the top of your
startup-sequence, ie: the first command. That will ensure a non-corrupted
VD0:. If you want to ARC many files, you can do a few things. You can
list all the files you want to ARC on the command line. This is tedious
when you have many files though. IF all the files you are going to ARC are
in their own directory, you can "ARC a File.ARC dfx:[path/]#?". If the
files are in the root directory of a device, you would use "ARC a File.ARC
dfx:#?", if in a sub-directory then "ARC a File.ARC dfx:Dirname/#?", where
dfx: is the device, Dirname is the directory name, and #? is a match for
any file. You can use any pattern matching wild card, I used the #?
because it is all encompasing.