#Hard Drive Help
16 messages in this thread
Please explain to me what I have done. I have a 1200 with an 81 meg
Maxtor drive. I did a reformat and repartition and now I have a problem.
If I have a RAD mounted the computer tries to boot from the RAD and since
it fails that, it kicks out the startup and reverts to a ROM prompt. If I
do not have a RAD mounted, the CTRL Amiga-Amiga sequence boots normally.
I suspect that I have done something to the boot block. How do I correct
this situation. Thanks for any help.
-John-
via AutoPilot
I don't think there is any problem with your hard drive…
All you have to do is add this line to you RAD: mountfile –
Bootpri = -127
Bob Comer — Flying high and fast with my A1200HD'030 on Autopilot!
From Cheyenne, Wyoming U.S.A.
Bob,
Thanks, I found the Bootpri tooltype in the manual. Using -129 makes the
RAD nonbootable. What was throwing me initially was that the tool didn't
need to be in the Devices drawer. Just living in Storage was enough to
cause trouble.
-John-
via AutoPilot
Cool, glad you got it fixed…
Bob Comer — Flying high and fast with my A1200HD'030 on Autopilot!
From Cheyenne, Wyoming U.S.A.
It almost seems as if you have a bad bootblock on the RAD: drive. Have
you done an install on the Boot partition of your hard drive after you did
a format? Did anything unusual happen at that time?
— John A. Toebes, VIII — Obvious Implementations Corp.
— Internet: toebes@oic.com
John,
Nothing unusual happened during install. I do remember this problem
happening when I first got the computer. I did check an old backup and
found that the tooltype Bootpri needs to be set to -129 in order to make
the rad: non bootable and non automatically mounted.
-John-
via AutoPilot
A BootPri of -127, would make RAD automount, but not autoboot…
Bob Comer — Flying high and fast with my A1200HD'030 on Autopilot!
From Cheyenne, Wyoming U.S.A.
That's good to know. I don't wish it to automount, though. I am
using its existence as a flag for a program to recognize a reboot
from a software cue versus a reboot after a power off condition.
Thanks for the tip.
I've done pretty much the same here too, at one time or another…
I'm curious as to why you don't want it to automount? (I always let
it automount, then I check for the existence of something in RAD, to
see if it was a warm boot.)
Well…that makes just as much sense. I am doing a similar thing by
looking for a small 1 byte flag in ram:. Never thought about putting
the flag in RAD:. The code for the ram:flag was always there so I
didn't change it, just "booleaned" another test.
I understand. (Makes sense to! But on those same lines, isn't there a
vector you could check that's unique on a warm start?)
Guess it all depends on what you want to know about a warm boot… (I
usually wanted to know if I needed to load something into RAD:)
Bob Comer — Flying high and fast with my A1200HD'030 on Autopilot!
From Cheyenne, Wyoming U.S.A.
Vector checking is outside of the scope of how I was programing. I was
trying to do everything from an ADOS script. All I needed to know was if
there was a brownout, cold boot from a power failure, or a warm boot
caused remotely by me.
-John-
via AutoPilot
Thanks! That's given me some ideas about some other things I want to do!
Bob Comer — Flying high and fast with my A1200HD'030 on Autopilot!
From Cheyenne, Wyoming U.S.A.
John: It sounds like your boot priority for the RAD: device is higher than
your hard drive. What you need to do is edit your RAD: mountlist which
should be contained in either the DEVS/DOSDRIVERS drawer or
STORAGE/DOSDRIVERS drawer. Add this line (or change it if it's already
there:
BootPri = -128
That should keep your Amiga from trying to boot from RAD:.
//
\X/ John – (TechnoJunkie at heart)
Interesting, why does it cause the symptoms that he explained? I
understand the priority choosing which drive to boot from, but the result
of going to the rom level prompt is what throws me off. Curious minds
want to know.
— John A. Toebes, VIII — Obvious Implementations Corp.
— Internet: toebes@oic.com
John,
Actually, changing the Bootpri entry in the Mountlist did nothing. The
tooltype in the RAD: icon is the key. Thanks for your input.
-John-
via AutoPilot