#Deluxpaint on a2000
11 messages in this thread
The problem is due to the external A2000 drive being DF2: instead of DF1:, plus
some not-too-clever programming in DPII. There are many ways around this:
1. Start up DP II from the internal drive. The load requester
always goes to the drive that DP II started from first.
2. Before running DP II, perform an "assign df1: ram:". This
will xfer references to ram: so at least the requesters can
be used. DON'T follow Steve Ahlstrom's "assign df1: df2:"
suggestion; this does a hard-assignment to the particular
DISK in drive DF2:, NOT to the drive itself.
3. Find a copy of the public-domain program "ASSIGNDEV". This is
a device-reassignment utility that WILL allow you to do
a "AssignDev DF1: DF2:" and effectively divert all refs to
DF1: over to DF2:.
4. Use a file hex-editor like FileZap or NewZap to search through
DP II and change all occurrences of DF1: to DF2:. Do this
ONLY on a copy of course! And this will permanently alter it
and cause problems with machines that have a real DF1: so
keep that in mind.
–apl
One other thing- i've found that ASSIGNDEV is fatal if you are using the Bridge
board (in my case, I also had a 5 1/4 hanging off the Bridge). Anyone else have
this experience??
Miles
Miles,
I've had no problems with ASSIGNDEV and the Bridgeboard. The disk drives
connected to the Bridge are totally separate from the Amiga drives, and don't
know of any way to get them confused. Haven't been using assigndev lately,
though, since I decided to hang my external 3.5" from the bridge, since I don't
need the floppy storage on the Ami side.
..Bob
Bob,
I'll give it another try, but when I removed ASSIGNDEV from my startup, I
never had any more crashes. I have had one other peculiarity with my Bridge,
which was my external 5 1/4 floppy having problems formatting on certain
sectors. It's annoying, but everything else works better than I had
anticipated.
Miles
Miles,
I do recall a problem at times with AssignDev – generally with programs that
access the drive at a lower level than the file-system. Also, ran into
problems with things like the key-disk scheme in DPaint, if I had both DF1: and
DF2: known to the system. This latter was easy to resolve, all I did was add
an "assigndev df2:" command, which caused the device entry for DF2: to be
deleted (after it was cloned as DF1:).
..Bob
Bob,
That's a good idea… I never reassigned DF2: – thanks for the input!
Miles
Not at all. I typically AssignDev df1: df2:, then AssignDev df2:, in my
startup-sequence. The bridge card is installed, though I never tried to do
anything with the two together; are you dying when you try to AREAD or AWRITE
to the AssignDeved device? It's possible that there's some brain damaged code
somewhere in the PC interface stuff that assumes that DF1: will be on unit 1.
No one should ever assume this.
-Dave
Dave,
No, the times I died were just doing random Amiga things… resizing a
window, entering a CLI command. Nothing spectacular. It never happened after
I got rid of AssignDev, so maybe I'm just being superstitious. Also. realize
that I am running BlitzFonts, Conman, ARP, and PopCLI. It may be that
AssignDev was confusing one or more of THEM. But since I never used AssignDev
until I had my 2000 with my old 1000's 3 1/4 drive, I tended to think that the
Bridge was involved…. but I am admitting ignorance on the subject of the real
culprit, and have learned to live with DF2:, obviating any fire I may have had
to hunt down the scoundrel.
Miles
Thanks for the suggestions. Can I find the assigndev program in any of the
DL's in the AMIGAFORUM?
Shalom
Shalom, DL9 ASSIDE.ARC
Thanks Marlene. I'll give it a try.
Shalom