[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

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

5339.0. "Adding 2090 & ST506 to GVP combo 2000 system?" by KAOOA::TRIMBLE (Compiling finished: 65535 ERRORS!) Mon Jan 13 1992 01:55

    Help!
    
    	I just purchased an old 2090 controller card with a 20Mb ST506
    drive.  Here's my problem:
    
    	The drive works perfectly if I attach it to the first 20 pin
    connector and access it as DH0:  BUT I must have nothing else in my
    system.  
    
    	Here's my situation:  I have a GVP 22Mhz combo board with a Quantum
    105S attached to it as DH0:.  
    
    	The catch:  AS long as my GVP card is active, the ST506 drive
    cannot be seen at all.  I have tried to attach the 20 pin connector to
    the second set of pins and access it as DH1:, but it doesn't like it. 
    When I go to PREP it, it says drive not prep'd.  The drive light does
    go on however so it is being seen!  
    
    	My question:  Can the ST506 drive be used as DH1: with the 2090
    controller?  I have nothing else connected to the controller.  As I
    said before, the Quantum is hooked up to the GVP card.  
    
    	What should I do?  Try to set the Quantum as DH1: and the ST506 as
    DH0:?  How would I do such a thing?  Would it involve setting the SCSI
    ID of the Quantum to something other than 0?
    
    	Can anyone help me?  
    
    
    					Many thanks,
    
    						Jason

T.R	Title	User	Personal Name	Date	Lines
5339.1	may have to boot gvp then mount st506?	SALEM::LEIMBERGER		`Mon Jan 13 1992 06:17`	11
	While I don't have an answer to your problem, I have some thoughts on the topic. Renaming the devices should have nothing to do with the problem. I would assume you need a mountlist for the 20 meg drive that is available to the system when it boots the GVP. I just sat in on an install with a GVP, 2091a this past weekend and all the parts worked well. The scsi ID of the GVP should have nothing to do with seing the 2090. You may have to boot the GVP, and then mount the drive on the 2090 card. I am sure you will find many people that will know what is happening here. I plan on putting a 40mhz 030 gvp on my system very soon, but I have a GVP scsi controller now so I expect no problems. bill
5339.2		KAOFS::J_DESROSIERS	Lets procrastinate....tomorrow	`Mon Jan 13 1992 12:21`	7
	I seem to remember when I had a similar setup (Hardframe + A2090A) I had TWO dh0! To format the drive connected to the A2090A, I HAD to remove the hardframe. When they were both formatted correctly, Amiga DOS would see both DH0s and could differienciate (sp??) the two. Jean
5339.3	Re: .1 Thanx for the input! :-)	KAOOA::TRIMBLE	Compiling finished: 65535 ERRORS!	`Tue Jan 14 1992 22:51`	14
	re: .1 Thank you for your input. I just called GVP today and they said to reconfigure my memory layout so that not all of the 32 bit RAM is extended memory or something like that. I guess the problem lies in the fact that the controller (hddisk.device) is being loaded into 32 bit RAM and it doesn't like that. So I'm going to try what he suggested and see what happens. We'll have to see. Thanx again for the reply. Jason
5339.4	Solved The problem... sort of...	KAOOA::TRIMBLE	Compiling finished: 65535 ERRORS!	`Tue Jan 21 1992 06:02`	10
	Well the problem is somewhat solved. The thing was the device driver did not like 32 bit RAM. So what I did was to run NOFASTMEM just before I ran binddrivers and then everything worked fine! I could see the disk no problem and even formatted it. But I hate to think of the awefull transfer rates I'm going to get by routing all the data through that slow chip RAM!!! :-( Jason
5339.5	Try MEMPRI	ARRODS::GOLDSTEIN	Steve G. DTN: 847-5401	`Tue Jan 21 1992 07:30`	15
	Have you thought of trying to use the program MemPri... This might help... If you set the 16-Bit memory at a higher priority then run BINDDRIVERS Then set back the memory to normal... I thought that if you use nofastmem you loose all but CHIP memory what a waste.. Steve G
5339.6	Thanx! I'll try to find that program!	KAOOA::TRIMBLE	Compiling finished: 65535 ERRORS!	`Fri Jan 24 1992 01:52`	11
	re: -.1 Thank you for the hint! I don't have MemPri, but I do have TASKX which will allow me to change the task priorities, but that probably won't change memory priorities eh? I'll have to find this MemPri program somewheres.... I wonder if it's available via UseNet Mailservers... Jason
5339.7	It's all here	FROCKY::BALZER	Christian Balzer DTN:785-1029	`Fri Jan 24 1992 04:55`	10
	Re: .6 MEMPRI.LZH has been in EOT::AMIGA:[UPLOAD] for quite a while now. ;-) It won't help you under 2.04 with adjacent 16/32 bit memory spaces, since they get merged automagically... Cheers, <CB>
5339.8	Don't have access to EOT:	KAOOA::TRIMBLE	Compiling finished: 65535 ERRORS!	`Sat Jan 25 1992 03:53`	13
	re: -.1 Unfortunately that doesn't do me any good. I have no access to EOT: (I can't get it off the system). What can I use with 2.04 then??? What do you mean when you say that they get merged ??? Thanx, Jason
5339.9	Huh?	FROCKY::BALZER	Christian Balzer DTN:785-1029	`Mon Jan 27 1992 04:49`	18
	Re: .8 > Unfortunately that doesn't do me any good. I have no access to > EOT: (I can't get it off the system). What do you mean by that? Your're on the EasyNet, so you have access to the EOT::AMIGA[UPLOAD] directory, not including broken systems or obsolete DECnet databases. What kind of error do you get? > What can I use with 2.04 then??? What do you mean when you say > that they get merged ??? There's nothing you can do about, once 2.04 merged the memory blocks. And I mean just that, my A2620's 4MB 32bit memory and my A2052's 2MB 16bit memory appear as an 6MB chunk (interestingly most tools believe this all to be 32bit memory... ;-) Cheers, <CB>
5339.10	I mean I don't have a dialin...	KAOOA::TRIMBLE	Compiling finished: 65535 ERRORS!	`Tue Jan 28 1992 12:52`	19
	Re: -.1 I mean that I don't have a dialin. But I am getting a dialin, so I will be able to get stuff off of the system now. Before I could get it to my account, but there was no way to get it to my Amiga. Now I can. :-) So what you are saying is that if I run under 2.04, all of my memory just looks like one big block, and I can't load things anywhere I want? There must be some way to change the priority of the 16 bit expansion RAM to be greater than the 32 bit, so I can at least get some speed out of the 2090. Not that I've even been able to get it to work with the chip RAM as of yet.... :-( Thanx for you replies, Jason
5339.11	Toaster & A3000T	DNEAST::PARENT_TODD		`Tue Jan 28 1992 16:02`	4
	Can anyone tell me if the Toaster will work with the A300T? -Todd
5339.12	The Visible Computer Model Kit	TLE::RMEYERS	Randy Meyers	`Tue Jan 28 1992 16:52`	18
	Re: .11 > Can anyone tell me if the Toaster will work with the A300T? The Toaster works as well in the A3000T as a normal 3000. You can plug it in and it runs, but you can't close the box. I was at the Boston Computer Society A3000T introduction. Someone asked Dave Haynie about the Toaster. He repeated the story about NewTek didn't follow the rules for physical size of their boards, and so it doesn't fit. Personally, if I was in charge at Commodore, I would have relaxed the tolerances on the A3000T so that the Toaster fit. I've heard that NewTek will give out instructions on how to hack a 3000 case to fit in a toaster. Perhaps they also have instructions for hacksawing a 3000T case.