| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2095.1 | Can't figure out all the examples | DECEAT::LANDINGHAM | Guy M., BXB1-1/F11,293-5297 | Mon Jan 09 1989 16:45 | 14 |
| This puzzled me also; I haven't tried it yet, but I've read through
the examples in the 1.3 manual, and none of them seem to explicitly
state that you have to do an install on the RAD:. The first example,
for systems with 2MB or more of ram, does a diskcopy of the Workbench
disk to RAD:, which I assume copies the DOS tracks also so a separate
install isn't necessary.
But the second example, which they describe as a minimal autobooting
RAD: device holding just enough to transfer control to a hard disk,
doesn't use diskcopy or install. They do state that you won't need to
insert your Workbench disk when doing a warm boot, but I don't see
where the DOS code gets put into RAD: anywhere in the example, at
least explicitly. Is it done implicitly perhaps?
|
| 2095.2 | -< THEY ARE CONFUSING >- | COMET::MCGEE | | Tue Jan 10 1989 01:06 | 9 |
| PAGE 5-7 OF THE 1.3 MANUAL APPEARS TO BE WHERE THE FILES REQUIRED
ARE COPIED TO RAD: AFTER CONTROL IS PASSED TO THE HARD DISK.
JUST A NOTE, I FOUND THAT THE MANUAL APPEARS TO HAVE AN ERROR IN
THAT USE THE IF STATEMENTS AS SHOWN RESULTS IN AN ERROR DUE TO "NO
ENDIF" AND DUMPS THE WARM BOOT TO A "DUMB" CLI VS THE EXPECTED REBOOT.
THIS APPEARS TO BE CORRECTED BY NOT NESTING THE IF STATEMENTS AS
SHOWN.
|
| 2095.3 | It's implicit | DECEAT::LANDINGHAM | Guy M., BXB1-1/F11,293-5297 | Tue Jan 10 1989 11:27 | 10 |
| Out of curiosity mostly, I tested this. I created a RAD: with a
high cylinder number of 7, put what I thought were the necessary
files there to transfer control to my hard drive, and tried rebooting.
If the Workbench disk was in df0:, my machine booted off that; if
I removed the Workbench disk from df0:, it apparently tried to boot
from RAD:. I say "tried" because it only got as far as the initial
CLI screen, then crashed. Perhaps I didn't copy all of the necessary
files. At any rate it appears that the boot code gets put into
RAD: automatically.
|
| 2095.4 | Guru | CIMAMT::CROMACK | | Tue Jan 10 1989 13:02 | 5 |
| Did you get a CLI window or the workbench screen?
I got the workbench screen and then a guru.
Dean Cromack
|
| 2095.5 | VD0: survives where RAD: dies
| AITG::WISNER | Paul Wisner | Fri Jan 13 1989 17:28 | 19 |
| I had a different problem using RAD:
I am developing a video game on a single-floppy 2.5meg A1000. In the past, I
set up my environment by copying everything to VD0: (compiler, include files,
lib, c: directory, and my source files). In df0: I keep a bootable floppy
that mounts vd0: then does "EXECUTE VD0:s/startup-sequence". I have kept this
setup running for weeks and have never had VD0: become corrupted. My video
game has caused some harse system crashes, especially doing BitBlt's using
bad destination bitmap plane pointers, or buggy clipping routines. Incredibly
VD0: never failed.
When I got 1.3, I setup my system using RAD:. RAD: seemed like a dream come
true... very quick reboots, which are important to me because I have to reboot
ALOT. And EMACS 1.3 under NEWCON: s lightning fast. Then I rebooted (after
DeluxePaint's file-requester caused a GURU) and RAD: was gone.......
....and that was enough to put me back on VD0:.
|