4000 freezes

[TUBbrain]

Hi all,

I need some help because i've got some troubles with my A4000/040 16Mb, Retina Z3 and Indivision 4000.
Since I put kickstart 3.1 40.70 roms and I installed WB3.9...
Now, each time I start the machine, The 4000 does'nt boot until I press the Ctrl+A+A to reset it. And sometimes, the Amiga start with a power-led flash and the guru...
When I try to boot on my install of WB39, it takes a few minutes to freezes (on AGA mode or In picasso96 modes). And sometimes after 3 ou 4 resets, it works well...

I precise that when I succesfully start the amiga and I play, no freeze occures...

I decided to put a fan on the cpu and one on the chip in the retina thinking that was a heat problems... but its awlays freeze....

I know that I put the BoigBall 1 and 2 updates, It asked me that if I wanted to put the know Rom and I say yes... Its seems to be with that new rom ans my kickstarts that is no dealing good....
May I do something with the new kickstart ? or maybe the chips are broken ?

Best regards,

 

[fitzsteve]

KS 40.70 is for A4000T and also contains the A4000T's 2nd SCSI Device but lacks the Workbench.library so you need to have that in 'Libs'

This probably explains your problems, you should try and find 40.68

Steve.

 

[bdb]

Start at beginning -- These are common Amiga problems

Start at beginning -- These are common Amiga problems

If FitzSteve's suggestions don't work, try:

1) The BB2 added a new set of "ROM" modules, but it will work without these; try both ways: Try with normal BB2 SetPatch (which loads the "DEVS:Amiga OS ROM Update") vs. "Setpatch NOROMUPDATE" will not load it.
2) Try finishing out with BB3 & BB4; they update many other files.
3) Simplify S:S-S by assigning ENV:, +/- Setpatch, IPrefs, LoadWB and any Assigns. Leave out anything that does get you up and running a basic system. Often I find that some irrelevent program causes issues. More often it is a Setpatch conflict; next most common a WBStartup issue -- use "LoadWB SKIP" to bypass those.
4) Try adding check points with the ECHO command: ECHO "Successfully loaded SetPatch," or "Got past IPrefs" and such. Along those lines comment out the QUIET as in, C:SetPatch ;QUIET This will let Setpatch give full information.
5) Once you get either a successful CLI or Workbench, start adding backwards until you find what crashes the system. Don't forget "pre-boot" programs, like the MAPROM/NOMAPROM option on accelerator boards.
6) Keep in mind that loading the "DEVS:Amiga OS ROM Update" causes a reboot (a flash of the power light) and takes a bit of time as the machine wants to wait AGAIN for the HDD's to "spin up."
7) Amiga's do this; they either do it to force thread posts on web sites like this, to frustrate their owners (I keep Ibuprofen on my desk for such occasions), or to help their owners learn more about a 20 year old system. In the later case, if you find a solution to a problem, then please post it. Others may have only Aspirin on their desks.

Once you clarify an issues, post back here.

 

[TUBbrain]

Yeaaaah !
the problems is deleted when I put setPatch NOROMUPDATE
The amiga boot at first power on
Thank you the the advice
I did'nt know BB3 et 4, so I'll download and install them...

for the cdrom on the second 4000 ide slot, must I use scsi.device or atapi.device
both work and maybe one is better than another ?

it seems to be more stable with NOROMUPDATE (less freeze etc...) but no SFS partition are visible... what the BB rom update really brings ?


best regards

 

[fitzsteve]

The OS update gives you an updated SCSI Device which supports larger drives hence why your partitions are missing without the update.

You could use Loadmodule to patch the SCSI Device with a latter version instead.

You still may have issues using the wrong Roms though.

The best option is to burn a custom Rom with the modules you need or use a Kickflash such as that found in the Deneb to load the custom modules and thus avoiding the OS update/reboot

All the best,

Steve.

 

[bdb]

Since not all of us have Deneb's and Willem EPROM programmers (weirdly I have both....Hey, did someone call me "Nerd?") you can use BlitzKick to pop those modules into your system. You may want to score the correct ROMs or use the SetPatch SKIPROMMODULES / DISABLEROMMODULES TO bypass the offending module(s). You see usage of these option on the install of BB 3 and 4.

 

[rkauer]

Another elegant way to resolve the problem:

1-Download and install on the Amiga the REMUS & ROMSPLIT packages from Doobrey (Google for it);

2-Install both in your Amiga in a partition that is recognized skipping the updates;

3-Using REMUS, extract the workbench.library from the AmigaOSROMUpdate file in the DEVS: drawer. Place the obtained library in LIBS: ;

4-boot with ROM updates normally from now on.

5-Send me a package of the best beer of your country in recognition. :mrgreen:

 

[bdb]

Yes, that is a deft and elegant way to collect just the modules you want. There is a reference online about making a OS 3.9 kernel ROM and burning it to firmware. However there is no need to burn an EPROM for this; just decide on what modules you want loaded for use, and get the up there the way you feel is best. I use ARTM to check if the right version is loaded.