[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

3939.0. "A2091 and setcpu" by STAR::SLACK () Thu Jul 19 1990 21:35

I couldn't find an answer to this in the notes file.
GVP didn't have the answer but said they'd love to get it if I find out.
Commodore said to ask BIX but I'm not a member of that service.
The following letter explains all. Commodore hasn't replied.
Can anyone help?

    Thanks.

    Bill Slack

                                                             14 June 1990

Ms. Susan Wagner
Customer Relations
CBM
1200 Wilson
West Chester PA 19380

Dear Ms. Wagner:

I have been  unable  to  find  the  information I need regarding my 2091
Controller, so I am  bouncing  it  back  to  you as per our recent phone
conversation. The problem is as follows:

I have  an  A2000-HD (2091 controller with Quantum 40Meg drive).  In the
processor slot is  a  GVP 3001 card with 28MHz 68030 and 68882, 4Megs of
80ns 32 bit RAM.    Everything  works  fine.  I use Dave Haynie's SetCPU
program to map the Kickstart  ROM into the 32 bit RAM.  Works fine, just
a matter of using the FastROM  option  of  SetCPU.    I  would  like  to
similarly map the ROM from the 2091  controller  into  the 32 bit memory
using the CardROM option of SetCPU.  But the only example I have for the
CardROMList is for the 2090A controller.  Not surprisingly,  it  doesn't
work with my configuration.  Can you get me the  appropriate CardROMList
entry for the 2091?  The file entry format is as  follows  (entries in C
language hex format except for the text string):

entry                                 value for the 2090A
-----                                 -------------------

- device's manufacturer code          0x202

- product code                        0x01

- device's size (in bytes)            0x10000

- the ROM's offset from the           0x8000
  configured board's base
  address (in bytes)

- the size of the ROM area to be      0x4000
  translated

- text string to identify the         CBM_2090A_Disk_Controller
  device; displayed by "verbose"
  option of SetCPU
 
The  above is only for the 2090A;  I need the corresponding  values  for
the 2091. Your early reply will be really appreciated.


                                                              Sincerely,




                           
T.RTitleUserPersonal
Name
DateLines
3939.1Try poking at the hardware....FENRYS::mwmMike (Selling Real Amigas) MeyerThu Jul 19 1990 21:456
I've seen at least one utility that will go out and extract that information
from devices on the bus. Possibly it's built into ARTM or Xoper. I'll try
and remember to look tonight, and see what I can find (though I can't
check the 2091 for you, as I don't have one...).

	<mike
3939.2ARTM?STAR::SLACKFri Jul 20 1990 00:115
    re .1
    I didn't see anything obvious in the docs for xoper 2.0;
    what is ARTM? 
    
    bill
3939.3SHOWCARDSTLE::RMEYERSRandy MeyersFri Jul 20 1990 01:424
Try the following program from tape::user2:[upload]SHOWCARDS.LZH;1.

I believe it lists the appropriate information for every expansion
card in your machine.
3939.4UsenetREAD::POMEROYFri Jul 20 1990 11:3810
    If that doesn't work, can you read/write on USENET. I left a message
    here yesterday, and also (through VNews) on comp.sys.amiga and
    comp.sys.amiga.tech on USENET. I had three replies from people at
    Commodore when I came in this morning. Peter Cherna and Dave Haynie
    help people out all the time in those confs.
    
    					Bob Pomeroy
    					REFINE::POMEROY
    
    
3939.5looking goodSTAR::SLACKFri Jul 20 1990 12:1012
    I downloaded Showcards and ran it this AM on both my A1000 and the
    A2000. Itseems to put out just the right data, even in the right
    format. It seems to have properly mapped the card but I didn't have
    time to really test it. Will do it tonite. 
    
    Of course, a reply from Dave Haynie would really be welcome. Anyone
    know hoe I can get those usenet replies (I've been off the net for
    awhile and forget the drill).
    
    Many thanks to all.
    
    Bill
3939.6ARTM >> Xoper...FENRYS::mwmMike (Selling Real Amigas) MeyerFri Jul 20 1990 17:509
ARTM is the Amiga Real Time Monitor. Does the same kinds of things as Xoper,
only ever so much more so. I prefer it.

You can find it on fish disk 327.

And "showcards" was the tool I was thinking about. Glad someone else knew
where to find it.

	<mike
3939.7oh boy, another goody!AJAX::SLACKFri Jul 20 1990 18:264
    ARTM sounds worth checking out .
    Thanx again.
    
    bill
3939.8I found ARTM guru'd to often.MEO78B::MANDERSONPhotographers do it in dark roomsSat Jul 21 1990 02:389
    I have stopped using ARTM as my system was consistantly crashing! It was
    more common when I would use the [mount] gadget, and a few others.
    
    I even tried removing the 68010 and retrying the 68000 - no change.
    
    Anybody else have this problem.
    
    regards
    kevin
3939.9ARTM(bugs)>>Xoper(bugs) ;-)FROCKY::BALZERChristian Balzer DTN:785-1029Mon Jul 23 1990 06:389
    Re: .6, .8
    
    Yup, ARTM _looks_ nicer than Xoper, but is definitivly more buggy than
    Xoper. While the latest Xoper still has a bug or two, I learned to
    avoid the problem areas. But I found ARTM to crash on me even when I
    wasn't activly using it.
    And what can I tell ya, Xoper even works under 2.0...
    
    <CB>
3939.10WJG::GUINEAUMon Jul 23 1990 12:505
I like XOPER for that same reason - ARTM always crashes on me!

I like the %cpu time display in Xoper as well...

john
3939.11ARTM worked fine for me..FENRYS::mwmMike (Selling Real Amigas) MeyerMon Jul 23 1990 17:207
Even under 2.0, though there are a few things you can do that'll crash the
system in that case.

Of course, I only run it when chasing problems, and not as a regular fixture
of the system.

	<mike
3939.12%CPU Time & VirusXCSCOAC::KENDRIX_JTue Jul 24 1990 02:138
    re:.10
     
    Speaking of %CPU time display, take a look at the numbers which Virus X
    4.0 chews up!  A few of us told Steve about it, to no avail.  He pretty
    much said that it was Xoper's miscalculation.  I don't think so...
     
    JK