| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2979.1 | Maybe this info will help | HPSCAD::GATULIS | Frank Gatulis | Wed Oct 04 1989 11:00 | 21 |
|
I don't understand exactly how Autoboot works so I won't try to
explain it but I have some emperical knowledge that might help.
1. You can do a lot to minimize the time it takes to transfer the
boot process from floppy to HD. As I recal, my boot floppy is
almost empty and I think there are only 3 lines in the startup
sequence on the floppy (if you like, I'll look, and tell you
how mine is set up).
2. I measured the difference in time it took to autoboot with the
1.3 kickstart rom/HD vs. the 1.2 rom/floppy/HD combination and the
autoboot was only 7 seconds faster. I feel this improvement was
almost insignificant. I ceratinly wouldn't buy the 1.3 rom for
the sole reason of speeding up MY boot time.
I realize boot time varies according to how complex your startup
sequence gets but in my case, the difference is whether or not
my system boots in 28 or 35 seconds.
Frank
|
| 2979.2 | | RBW::WICKERT | MAA USIS Consultant | Mon Oct 09 1989 17:02 | 6 |
|
I'd be interested in finding out how you've set up your floppy... I have
a feeling mine is a little long-winded...
Thanks,
Ray
|
| 2979.3 | re .2 | HPSCAD::GATULIS | Frank Gatulis | Mon Oct 09 1989 19:41 | 17 |
|
Ray,
Here's the startup-sequence on my floppy which transfers me quickly
to DH0:
Bind Drivers
DH0:c/assign T: RAM:
DH0:c/cd RAM:
DH0:/execute DH0:s/HDstartup-continue
That's it. Couldn't get much simpler (that's not a challenge!)
Frank
|
| 2979.4 | OOPS! | HPSCAD::GATULIS | Frank Gatulis | Mon Oct 09 1989 19:43 | 8 |
|
correction ... in .3
that's "BindDrivers" not "Bind Drivers"
Frank
|
| 2979.5 | Avoid nested EXECUTEs | TLE::RMEYERS | Randy Meyers | Wed Oct 11 1989 22:15 | 17 |
| Re: .3
If you change :
DH0:c/execute DH0:s/HDstartup-continue
to
DH0:C/RUN DH0:c/execute DH0:s/HDstartup-continue
The system will not fill obligated to make a copy of the
execute script in T: before executing it.
The execute command writes out a copy of the script into
T: if the script takes arguments or it is a nested execute.
Beats me why nesting causes it to make a copy of the
script.
|