| Title: | AMIGA NOTES |
| Notice: | Join us in the *NEW* conference - HYDRA::AMIGA_V2 |
| Moderator: | HYDRA::MOORE |
| Created: | Sat Apr 26 1986 |
| Last Modified: | Wed Feb 05 1992 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5378 |
| Total number of notes: | 38326 |
Hi all,
I have an unusual problem which I was wondering if anyone has
seen before. Briefly when I boot the system it boots fine and my
two st-type hard disks seem to be fine. My startup-sequence program on
floppy is very short ie;
BINDDRIVERS
DH0:C/CD DH1: /* To recognize the second HD */
/* This line is new. */
DH0:C/EXECUTE DH0:S/STARTUP-SEQUENCE
DH0:C/ENDCLI > NL: ( I am not sure about the last one as
I am at work now )
The only new line in this is the "DH0:C/CD DH1:".
For background this problem started when I installed my second
internal 3.5 hard disk.
I have;
Amiga 2000
A2090 Hardisk controller
Micro way flicker-fixer
Supra 8 meg memory board populated to 4 meg.
2 Miniscribe 3.5 8045's 20 meg each.
I had to disassemble most of my Amiga to install the second disk. The
installation went fine and I formatted the second hard disk. I then
rebooted the system and transferred some directories to the second hard drive,
it being almost midnight I decided to retire for the evening and backup
the new hard disk this week sometime.
Last night was the first time I have gotten back to the system
since last Saturdays installation, and I saw the following sequence;
1. I booted the system as usual.
2. I ran my home accounting package "Phasar" and entered
some new financial data.
3. I exited Phasar and then attempted to backup the data file
to floppy, as I always do after making changes.
4. At this point I removed the boot floppy from DF0: and the
disk icon did not disappear from the screen! I pop'ed up
a CLI and executed the INFO command and it showed DF0: as
empty and WB 1.2 (The boot floppy) as an available volume
which was not mounted. At certain times the system asked
me to put back WB 1.2 in any drive but would only accept
it in DF0:
5. The boot floppy icon (WB 1.2) would not go away no matter
how long I waited and even if I refreshed the display.
6. Additionally any disk placed in DF1: now brings up an icon
labeled DF1:Bad.
7. Since the system wanted "WB 1.2" in DF0: no other disk can be
placed in that drive.
Any suggestions? I am going to take the machine apart tonight and
check all the connections however this make no sense to me.
Thanks in advance for any help.
Harry Arendt
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5036.1 | A few questions | KAOFS::J_DESROSIERS | Lets procrastinate....tomorrow | Wed Sep 11 1991 13:54 | 12 |
1- How many partitions on the first HD?
2- What are they named?
3- Did you change the unit select jumpers on the second HD?
4- Did the prep go OK?
5- How many partitions did you make on the second HD?
Jean
| |||||
| 5036.2 | Check your ASSIGNments... | HSSTPT::WILSONTL | Lead Trumpet (Read that...LEED!) | Wed Sep 11 1991 14:24 | 7 |
If you follow the same steps, particularly using PHA$AR, you'll probably find an ASSIGNment that references DF0 somehow. That is why your icon did not go away and why it wanted WB back in DF0. I don't know why you got a DF1:BAD requestor. Tony | |||||
| 5036.3 | re the last two | CAMONE::ARENDT | Harry Arendt CAM:: | Wed Sep 11 1991 16:49 | 32 |
Re .1
>1- How many partitions on the first HD?
1
>2- What are they named?
Phred
>3- Did you change the unit select jumpers on the second HD?
No. The controller cable swapped lines 26 & 28 which are the
Unit selects.
>4- Did the prep go OK?
Went perfectly.
>5- How many partitions did you make on the second HD?
1
>Jean
Re .2
I will check the assignments to see if I am referencing it.
| |||||
| 5036.4 | Check the floppy cabling | CSC32::K_APPLEMAN | Wed Sep 11 1991 17:49 | 9 | |
Check your cabling for the second floppy disk. I ran into a similar
problem with my old A500 after connecting the external drive with
power applied. It blew some lines on the CIA chip that runs the
floppies. This produced the exact same symptoms you described. I
believe that removing the second floppy solved the problem until I
could get the CIA chip replaced.
Ken
| |||||
| 5036.5 | A few things to check | SDOGUS::WILLIAMS | TOPGUN | Wed Sep 11 1991 19:50 | 22 |
Check to see that you placed the jumper IN that says that you have an
internal second drive (J301?).
Check as .4 says that you have the cable well seated.
Check that pins 1-34 on your second floppy are in the same location
as pins 1-34 of the original floppy (i.e. you may have the connector
upside down [not all floppy manufacturers and not all models within
a manufacturer's line are the same]).
When do you assign SYS: to DH0: or DH1:? You must assign SYS:, C:, S:,
L:, LIBS:, FONTS: and DEVS:, and infact any assign that you have made
to DF0: or the DF0: icon will NEVER leave your screen.
Check to see that the current path does NOT include df0:
or an assign to df0: or AmigaDOS will always re-request df0:
to try to satisfy the path request.
Be sure that you have Changed Directories to something other than
DF0: so the current directory isn't being looked for on the floppy.
Clark
| |||||
| 5036.6 | Case is solved! | CAMONE::ARENDT | Harry Arendt CAM:: | Fri Sep 13 1991 09:08 | 21 |
Thanks for the good advice! I have solved the problem. Drive DF0
had a problem because I altered the DH0:s/startup-sequence and
removed the assignment of SYS: to DH0: and it then defaulted to
DF0:. When I changed it I rememeber thinking "What the heck is this
for anyway." Well that goes to show you the power of using comments
in the code.
The second drive was an unusual hardware problem. I have mounted
2 3.5 inch hard disks in the 5.25 internal bay by modifying the bay
and mounting them sideways. This meant that the power cables for the
second drive were exactly under the second floppy and they were
touching the rotor under the drive and slowing it down enough so
that it was unreadable.
Thank you for your help!!
Harry Arendt
| |||||