Welcome, Guest. Please login or register.

Author Topic: Help with amiga 500 ram issue, please.  (Read 1444 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline mkarateTopic starter

  • Newbie
  • *
  • Join Date: Oct 2005
  • Posts: 11
    • Show only replies by mkarate
Help with amiga 500 ram issue, please.
« on: October 16, 2005, 07:15:22 PM »
Hey everyone new to this board but wondered if anyone could help me.  I have a stock amiga 500 with a A501 512k expansion and a dataflyer plus 2.3 sidecar.  Everthing was working fine with it until I bought the dataflyer ram board and added it to the dataflyer unit.  It now boots but then hangs while loading WB1.3  I can either cold boot or do a warm reset and then it will continue to WB and does see all 8 meg I have on the board.  Can anyone tell me why this now hangs on bootup.  Also after adding this board I can no longer run directory Opus, When you start it it gives a guru mediation error while without the ram board it runs just fine.  Any help would be greatly appreciated.  Thanks.
 

Offline amiga4001

  • Hero Member
  • *****
  • Join Date: Sep 2004
  • Posts: 537
    • Show only replies by amiga4001
Re: Help with amiga 500 ram issue, please.
« Reply #1 on: October 16, 2005, 08:00:15 PM »
Try it without the 501.
Believe max ram voor 500 is 8MB?
Seems like it is conflicting.
 

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show only replies by Zac67
Re: Help with amiga 500 ram issue, please.
« Reply #2 on: October 16, 2005, 09:01:16 PM »
A501 is Ranger/Chip mem, shouldn't be any conflict with the RAM card. Max for A500 is 10.8 MB: 1 MB Chip, 1.8 pseudo Fast (Ranger), 8 MB real Fast (Zorro II)

I'd test the RAM very well, first without the A501 to make sure. Maybe one of the chips is flakey.
 

Offline mkarateTopic starter

  • Newbie
  • *
  • Join Date: Oct 2005
  • Posts: 11
    • Show only replies by mkarate
Re: Help with amiga 500 ram issue, please.
« Reply #3 on: October 17, 2005, 06:17:17 AM »
It seems that I have tracked it down to the fastmemfirst command.  If I take it out of startup-sequence then it boots fine but after one boot then the system goes corrupt from it not being there.  Any ideas?