cc100jr@gitpyr.UUCP (03/08/86)
Scenario:
User places Workbench diskette into df0: and hits Ctrl-Amiga-Amiga.
His faithful Amiga responds as predicted (is it wise to predict any female?)
by performing a soft reboot. *flash* *whirrrrrr* . The screen refreshes and
the usual intro message appears.
Copyright c 1985 Commadore-Amiga, Inc.
All rights reserved
Release 1.1
Unknown command prompt
1>
Huh? Unknown command prompt? What do you mean "Unknown command prompt"?
(Asside: the first command in this user's startup-sequence is prompt)
User decides to look for himself and types "dir c". Amiga returns
with the following:
Unknown command dir
1>
Well, things are definately getting interesting here. Being a veteran
of diskette problems (curses to you OPUS) on Amiga, our brave user pops the
diskette release withdraws Workbench from the slot and slides in another
bootable disk with the system commands on it. *flash* *whirrrrrrr* and once
again the Amiga reboots (softly mind you). Unfortunately, the problem seems
to have migrated. Along with the usual logon display comes, "Unknown command
prompt" again.
Now this user is getting just a little worried. Ah..... yes! Let's
try a hard reboot and reload Kickstart! As you have probably guessed by now,
it was a nogo. Amiga was simply refusing to execute any system commands. So,
user turns off Amiga. "Let's give 'er a rest", he says, "she must be tired."
After waisting an hour and a half on some meaningless TV drivel, user
has worked up enough courage to turn Amiga back on. Of course, nothing has
miraculously fixed itself while he was gone. So, out of despiration, he
decides to see if any of the executable programs still work. User types in
the file name that contains his terminal program and voila! It works just fine!
After killing the terminal program, he decides to investigate. User types in
"c/dir". The familiar disk whirrrings occur and a directory listing appears.
Well, obviously, something is messed up with the logical device assignment of
C:. User types "c/assign c: c". The following message appears:
Can't cancel c
1>
Folks, this user is mystified. Is this a hardware problem or a software
one? On the one hand, it would seem that the problem is software related.
Yet, why should it occur on every bootable disk this user possesses? Does
anyone out there in Netland have any ideas? Are you there Amiga? Help!
User Getting Hysterical
Joel Rives
Georgia Insitute of Technology, Atlanta Georgia, 30332
...!{akgua,allegra,amd,hplabs,ihnp4,seismo,ut-ngp}!gatech!gitpyr!cc100jr
"Remember, no matter where you go, there you are!"
<< Buckaroo Banzai >>