#Computer Basics
7 messages in this thread
Did they give you any reason why you have to do this warm boot?
I got an A4000 with the original 120mb and a 240mb and the system booted just
fine. Then, I replaced the 120 with a Western Digital 750mb hard drive as the
unit 0 drive. I have to do two warm boots to get my system to come up. If you,
or anyone else has the solution, please email or relate here.. Thanks, Brian
Brain,
The reason I was given for doing a warm boot, was that the computer comes on
line faster than the large hard drive comes up to speed.
So, by the time the hard drives is up and running, the computer has already
booted and during the boot did not find the OS file on the hard drive, since
the hard drives wasn't ready at that time.
I'm supprised that you have to go through two warm boots. Maybe you should wait
a few seconds before you do the first boot.
Someone here sent me a message about a program, a guess it is a utility, that
will delay the computer for a few seconds until the hard drive has had enough
time to come up to speed. But, he indicated that the program could also cause
some problems or was tricky to use, or some reference to that effect.
If you are interested in the utility, I'll go through my messages and find the
information for you. Or maybe the person how gave me that information will
respond to this message faster than I can find the info.
It is a nusense, but since I've been running the Flyer, I've done more warm
boots than I did the entire time I've owned the Amiga. So, I hardly notice it.
Fred
Fred,
I don't know why you'd need a utility to slow down the boot. You should
be able to just put a "WAIT n" statement in your startup sequence prior to
mounting the drive.
Generally, modifying the startup sequence is frowned upon, but this should
be pretty minor.
Then again, I could be wrong. <g>
Kent
Kent,
For the boot sequence to execute the wait, it must read the
Startup-Sequence. Since the drive is not to speed and the boot sequence
has not found a suitable bootable device, the sequence puts out the insert
floppy request and waits. What you would need is a way for the hardware
boot sequence to keep checking the drives until the bootable one is ready.
Hank
Videology, Inc. Where you get P.O.M.P. under
all circumstances
Hmm.
Okay, catch-22. It has to read the drive before it can be told to wait
before mounting the drive. I should've caught that.
I may have been thinking that it wasn't the boot drive, but a second
drive. Or (more probably) I'm chewing on my foot. <g> Oh well, it's not
the first time.
Could you make a boot floppy with the wait on it, and then run the user
startup from the HD after it spins up? 'course, that may be more trouble
than a reboot.
Reminds me why I'm a lurker.
Kent
Interesting –
That might work, but then the boot floppy would have to transfer all
system functions to the harddrive after it's up, since assigns would only
work with the harddrives in the system.
Since I've seen this on several A4000's, I keep feeling their is a better
fix.
Guess we'll keep looking. :v(
Hank
Videology, Inc. Where you get P.O.M.P. under
all circumstances
Brian,
I found the message about slowing down the bootup of the Amiga.
If it is still on the board it is message 101554 and it came from Trent K.
Johnson.
I'll see if I can just send it to you.
Fred