BigRamPlus?

[danbeaver]

Answer #1, yes I've used a ZorRAM and a BigRam+ in A4000T & D's (even an A3000D) and they work fine.  When used with a Mediator (which can grab 512 MB of Z3 address space) one has to be careful with the way the Z3 address space (1 GB) is allocated; if you do it incorrectly you will run out of address space.  For example, the ZorRAM 128MB allocates 256 MB of space thus wasting 128 MB of address space.  The two ram boards are otherwise identical except for the layout: the BigRam+ has all its RAM on 1 side, and only comes in 256 MB (the amount it allocates).  Otherwise the parts and firmware are the same.

Answer #2,  Sorry 442 or is it 455? Both are Z3 (32-bit boards) and lay outside the Z2 24-bit address space; so a A2000 can't see it.

[danbeaver]

Yeah, that is why 32-bit RAM had to be put on the accelerator board itself when used in an A2000 (but boy, those 040's and 060's would make an A2000 fly)...

[danbeaver]

BigRAM+ is NOT guarantied to work in a A4000 with third-party BusBoards! Because of bad Z3 - termination! It is only guarantied in original Commdore Busboards or Tower-Models!

You don't say!

[danbeaver]

So BigRam wont work with a Mediator 4000 or in most cases it will?
ZorRam says it does work with the Mediator however AmigaKit does not have any available for sale right now.

It does work with the Mediator, but certain "add on" boards that give Zorro slots to tower systems (to the best of my knowledge these are for adding Z3 to an A1200) don't work.  Those machine that already have Z3 slots (A3000D/T and A4000D/T) with expanded Z3 slots (Mediator) work fine; I'm sure those who write aggressively with excessive punctuation will follow up this post with specific examples of boards that don't work well due to "poor Z3 slot Termination." Although the only A4000D towered model I had in the past, did work with a BigRam+.

I believe iComp.de (https://icomp.de/shop-icomp/en/shop/product/bigramplus.html) and  Vesalia.de (http://www.vesalia.de/e_bigramplus.htm) has BigRam+ boards.  The ZorRam boards are not listed on AmigaKit's site.

[danbeaver]

You should start a new thread for this and explain what you are trying to do and where you need help.

[danbeaver]

OK, I see the connection between the BigRam+ and the OS, but if the board is available in 3.1, then it is working; if unavailable in 3.5, then there is a bad install or something similar going on; I can't figure out how a HDD mask (using default settings) would affect an autoconfig device already in place by the time the HDD is initiated.

[danbeaver]

The BigRam+ autoconfigures for KS 2.04 and up, so it should be available before KS turns over control the a boot floppy or HDD.

So I vote to ditch 3.5 and do a fresh install of 3.9 as Mike says.  OS3.9 updates a lot of drivers and with the evolving Boing Bag #4 is being updated by concerned citizens of Amiga township.

At the least work in sequence: Do a fresh HDD install of 3.1 to see if it works, then an Clean upgrade to OS3.5, and finally upgrade to 3.9.

[danbeaver]

It works in a normal install of OS3.5, no additions needed.

Try the suggestions Mike and I have suggested.

In addition, the startup text you posted is for a floppy based WorkBench; try:

C:SetPatch QUIET
C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21

C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ

Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE

Assign >NIL: ENV: RAM:ENV
Assign >NIL: T: RAM:T
Assign >NIL: CLIPS: RAM:Clipboards
Assign >NIL: REXX: S:
Assign >NIL: PRINTERS: DEVS:Printers
Assign >NIL: KEYMAPS: DEVS:Keymaps
Assign >NIL: LOCALE: SYS:Locale
Assign >NIL: LIBS: SYS:Classes ADD
Assign >NIL: HELP: LOCALE:Help DEFER

BindDrivers ;really unneeded if no drivers in SYS:Expansion
C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)

IF EXISTS DEVS:Monitors
  IF EXISTS DEVS:Monitors/VGAOnly
    DEVS:Monitors/VGAOnly
  EndIF

  C:List >NIL: DEVS:Monitors/~(#?.info|VGAOnly) TO T:M LFORMAT "DEVS:Monitors/%s"
  Execute T:M
  C:Delete >NIL: T:M
EndIF

SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart

C:AddDataTypes REFRESH QUIET

C:IPrefs

C:ConClip

Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities

  Execute S:User-Startup

Resident Execute REMOVE
Resident Assign REMOVE

C:LoadWB SKIP ;Skips cuts out any WBStartup items
EndCLI >NIL:

[danbeaver]

I may be grasping at straws as well, but have you thought that a bad "setpatch + ROM update" is changing your vectors and a clean ipartition with a fresh install might fix it?  At least disable the ROM update by renaming it or "C:Setpatch NOROMUPDATE" in your S:S-S file.