paulm@cbnewsj.att.com (paul.j.maioriello) (10/11/90)
As a 2000 to 3000 upgrader, I was looking forward to using my existing Zorro II cards in my 3000. Well the 2088 memory expansion board works great!! 4 megs of memory is real nice. My a2090, however is a different story. I had two st-506 drives hanging off it in the 2000. I can't get BindDrivers to work on the 3000 whenever I put the hdisk file in the expansion drawer. BindDrivers does make a disk access, but it never returns. This is the case regardless of whether I use 1.3 or 2.0. I know the a2090 was much maligned and SCSI drives are much nicer (I really like the quantum in the 3000) but what am I going to do with my 506's?? Are there any known problems with using them with an A2090 on a 3000? I have tried setting things up several different ways but the BindDrivers always fails to return. As a final resort, I reran the install script from the disk that came with the A2090. When the script hung up, I took a look at the offending line and sur enough it was a BindDrivers. Does anyone have any ideas on this???? On a different note, my 3000 came sans AmigaVision OR a card to get it. I have my dealer looking into it, but I dont hold out much hope for help from him. I was his first educational program customer. It took me while to convince him that the 3000 was part of the plan. Lest, this note sound too negative, let me say that I love the 3000. I hate having to even turn it off (unless its to install more goodies). Thanks for any help Paul Maioriello lzatt!pjm
daveh@cbmvax.commodore.com (Dave Haynie) (10/16/90)
In article <1990Oct11.004827.24144@cbnewsj.att.com> paulm@cbnewsj.att.com (paul.j.maioriello) writes: >My a2090, however is a different story. I had two st-506 drives >hanging off it in the 2000. I can't get BindDrivers to work >on the 3000 whenever I put the hdisk file in the expansion >drawer. BindDrivers does make a disk access, but it never >returns. This is the case regardless of whether I use >1.3 or 2.0. You can probably trick the A2090 into working. The problem is in software. The A2090 device driver, like many Zorro II drives, never considered the possibility of Fast memory it can't DMA into being available at boot or BindDrivers time. Before the 3000, you had to AddMem such memory, but now it's automatic and it gets added before the A2090 is initialized. The A2090, with the proper MountLists, can avoid DMA into this 32 bit memory in normal operation, but not at boot time. So if you run the "NoFastMem" program and then mount the A2090, it will get it's buffers in Chip RAM rather than the 32 bit Fast RAM, and run good. It would, of course, be much better to have that stuff out in 16 bit Fast memory, if you have any. No so much for speed, but because the Chip memory is a more limited resource. Unfortunately, there's no supplied program that does this. A revised device driver for the A2090 would be the ideal fix. >Are there any known problems with using them with an A2090 on a 3000? That's the situation. I don't know of any other problems; it should work for certain under 1.3 on a 3000 if the 32 bit Fast memory can be switched off. >Paul Maioriello -- Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests" {uunet|pyramid|rutgers}!cbmvax!daveh PLINK: hazy BIX: hazy Standing on the shoulders of giants leaves me cold -REM