Welcome, Guest. Please login or register.

Author Topic: The Os 3.1.4 Thread  (Read 239782 times)

Description:

0 Members and 3 Guests are viewing this topic.

Offline kirk_m

Re: The Os 3.1.4 Thread
« on: October 08, 2018, 03:57:08 AM »
I purchased this for my A1200, and want to write the ROMs.  I know I need 27C400 EPROMs to do this, but, is there anything more "modern" to use than a UV-erase EPROM?  I know I can still get the UV-erase EPROMs, but, they are likely used and in need of erasure, but, I do not own a UV-based eraser.
-/- A500 & ACA500 & ACA1233n -/- A500 Tower & VAMPiRE II 500+ -/- A2000 & BLiZZARD 2060 -/- A3000 & CYBERSTORM MKII 040 -/- A1200 & BLiZZARD 1230 MK IV -/- A1200 & BLiZZARD 1260 -/- A4000 & 3640 -/-
 

Offline kirk_m

Re: The Os 3.1.4 Thread
« Reply #1 on: May 20, 2019, 08:24:57 PM »
Has anyone encountered any issues with SCSI drives no longer working after installing 3.1.4 on an A2000 that has a Blizzard 2060 accelerator card?  I swapped out my 3.1 ROMs for 3.1.4 yesterday, and, now the SCSI drives do not show up in the early startup, or, anywhere else for that matter.  The IDE drives are still visible, as I was able to install 3.1.4 onto a drive connected to the Buddha IDE controller.

If I reinsert the 3.1 ROMs, my SCSI devices (SCSI2SD and CDROM) are again visible and usable (indeed, the SCSI2SD is my 3.9 boot drive on this computer).
-/- A500 & ACA500 & ACA1233n -/- A500 Tower & VAMPiRE II 500+ -/- A2000 & BLiZZARD 2060 -/- A3000 & CYBERSTORM MKII 040 -/- A1200 & BLiZZARD 1230 MK IV -/- A1200 & BLiZZARD 1260 -/- A4000 & 3640 -/-
 

Offline kirk_m

Re: The Os 3.1.4 Thread
« Reply #2 on: May 21, 2019, 03:07:35 AM »
Thomas,

The HD activity light stays illuminated on the 2000, as well as the LED on the SCSI2SD when the 3.1.4 ROM is installed.  Also, 2060scsi.device shows up nowhere in the list of devices that are currently active on the system.  If I plug the 3.1 ROM back, all of this comes back, and, the LEDs behave as they should.   Also, reinstalling the 3.1 ROM makes everything work again -- all drives appear, I can boot from the SCSI drive, etc.  As soon as I put the 3.1.4 back, it disappears.

Does this steadily illuminated LED indicate anything?

Also what version firmware is on your 2060's ROM?  Sysinfo reports v8.2 on mine.  It seems that 8.5 is the last version made (at least according to the archive on A1K).  Does this make any difference?


Gizmo:

No, I don't have one of them there fancy card-readers :)
« Last Edit: May 21, 2019, 03:12:16 AM by kirk_m »
-/- A500 & ACA500 & ACA1233n -/- A500 Tower & VAMPiRE II 500+ -/- A2000 & BLiZZARD 2060 -/- A3000 & CYBERSTORM MKII 040 -/- A1200 & BLiZZARD 1230 MK IV -/- A1200 & BLiZZARD 1260 -/- A4000 & 3640 -/-
 

Offline kirk_m

Re: The Os 3.1.4 Thread
« Reply #3 on: May 21, 2019, 08:18:27 PM »
Has anyone encountered any issues with SCSI drives no longer working after installing 3.1.4 on an A2000 that has a Blizzard 2060 accelerator card?

Same setup here! No problems and I am using a scsi2SD V5.....

Funny you should reply... I got my 2060 from you :)
-/- A500 & ACA500 & ACA1233n -/- A500 Tower & VAMPiRE II 500+ -/- A2000 & BLiZZARD 2060 -/- A3000 & CYBERSTORM MKII 040 -/- A1200 & BLiZZARD 1230 MK IV -/- A1200 & BLiZZARD 1260 -/- A4000 & 3640 -/-
 

Offline kirk_m

Re: The Os 3.1.4 Thread
« Reply #4 on: May 22, 2019, 04:56:51 PM »
It all works  now.  Very strange.  I messed with it a little more,   unplugging and plugging cables from the SCSI2SD itself, as well as reinstalling the ROM, and, then it booted from the SCSI2SD.  Maybe a bad connection.
-/- A500 & ACA500 & ACA1233n -/- A500 Tower & VAMPiRE II 500+ -/- A2000 & BLiZZARD 2060 -/- A3000 & CYBERSTORM MKII 040 -/- A1200 & BLiZZARD 1230 MK IV -/- A1200 & BLiZZARD 1260 -/- A4000 & 3640 -/-
 

Offline kirk_m

Re: The Os 3.1.4 Thread
« Reply #5 on: June 15, 2019, 03:23:32 PM »
I have encountered the following issue after installing 3.1.4 on a bog-standard A3000 16MHz (no expansion cards, 2mb fast, 2mb chip).

When setpatch runs after first reboot, the computer hangs with a purple screen if all caches are not disabled from early startup.  Commenting setpatch out allows the system to run if you haven't disabled the caches.  Using NODATACACHE NODATABURST NOCACHE NOBURST  in the startup sequence does not prevent the lockup -- all caches have to be disabled in the BOOT OPTIONS of early startup menu.

I have installed MMULIB to get the 68030.library for the install, same result.

I've run out of ideas now on how to get things working properly.  Any help is appreciated.
-/- A500 & ACA500 & ACA1233n -/- A500 Tower & VAMPiRE II 500+ -/- A2000 & BLiZZARD 2060 -/- A3000 & CYBERSTORM MKII 040 -/- A1200 & BLiZZARD 1230 MK IV -/- A1200 & BLiZZARD 1260 -/- A4000 & 3640 -/-
 

Offline kirk_m

Re: The Os 3.1.4 Thread
« Reply #6 on: June 16, 2019, 02:02:29 AM »
I figured it out.  The 3000 had 2mb of fast ram, all ZIPs.  They were all fast page mode, so I swapped them out for Static Column zips and now burst works, since FPM memory and burst are incompatible.
-/- A500 & ACA500 & ACA1233n -/- A500 Tower & VAMPiRE II 500+ -/- A2000 & BLiZZARD 2060 -/- A3000 & CYBERSTORM MKII 040 -/- A1200 & BLiZZARD 1230 MK IV -/- A1200 & BLiZZARD 1260 -/- A4000 & 3640 -/-