Welcome, Guest. Please login or register.

Author Topic: A1200 + GVP 1291 SCSI issues after SetPatch  (Read 191 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline techhuskyTopic starter

  • Newbie
  • *
  • Join Date: Oct 2025
  • Posts: 10
  • Gender: Male
    • Show only replies by techhusky
A1200 + GVP 1291 SCSI issues after SetPatch
« on: May 09, 2026, 06:08:10 AM »
Hi all,

I have an A1200 running OS 3.2.2 with a GVP 1230 Turbo+ II 68030 accelerator with an attached 1291 SCSI controller.  The 1291 provides an external DB25 connector for external SCSI devices.  I've been trying to get it to work with a ZuluSCSI Pico Slim for weeks.  The GVP driver kept reporting any device configured (HDD or CD-ROM) on the ZuluSCSI as a tape drive.  Some debugging showed that the device inquiry data was not being properly reported by the gvpscsi.device driver (version 5.3), even though the ZuluSCSI was returning it properly.  I'm not sure why I didn't think of this sooner, but just today, I finally decided to try booting without a startup-sequence.  The ZuluSCSI worked perfectly.  I was able to narrow the failing point down to the SetPatch call during startup.  I am assuming after patching something is either stomping on the gvpscsi.device or has changed a dependent driver or library enough to break it.

Any suggestions for workarounds for this type of situation?  OS 3.9 SetPatch has the ability to SKIPROMUPDATES for certain devices and libraries.  I don't see similar capability on OS 3.2.2.

Thanks,

-Jeremy
 

Offline Boing-ball

Re: A1200 + GVP 1291 SCSI issues after SetPatch
« Reply #1 on: May 10, 2026, 01:33:38 AM »
Hi all,

I have an A1200 running OS 3.2.2 with a GVP 1230 Turbo+ II 68030 accelerator with an attached 1291 SCSI controller.  The 1291 provides an external DB25 connector for external SCSI devices.  I've been trying to get it to work with a ZuluSCSI Pico Slim for weeks.  The GVP driver kept reporting any device configured (HDD or CD-ROM) on the ZuluSCSI as a tape drive.  Some debugging showed that the device inquiry data was not being properly reported by the gvpscsi.device driver (version 5.3), even though the ZuluSCSI was returning it properly.  I'm not sure why I didn't think of this sooner, but just today, I finally decided to try booting without a startup-sequence.  The ZuluSCSI worked perfectly.  I was able to narrow the failing point down to the SetPatch call during startup.  I am assuming after patching something is either stomping on the gvpscsi.device or has changed a dependent driver or library enough to break it.

Any suggestions for workarounds for this type of situation?  OS 3.9 SetPatch has the ability to SKIPROMUPDATES for certain devices and libraries.  I don't see similar capability on OS 3.2.2.

Thanks,

-Jeremy

Have you tried the following after backing up your current configuration

1).. Installing ThorsMMU libs in expert mode. As this has configurable options for Phase 5, ACA and GVP accelerators

2j.. Why still on AOS 3.2.2 when 3.2.3 upgrade is available. May have a fix for SetPatch there.

https://www.hyperion-entertainment.com/


« Last Edit: May 10, 2026, 01:36:10 AM by Boing-ball »
 

Offline techhuskyTopic starter

  • Newbie
  • *
  • Join Date: Oct 2025
  • Posts: 10
  • Gender: Male
    • Show only replies by techhusky
Re: A1200 + GVP 1291 SCSI issues after SetPatch
« Reply #2 on: May 12, 2026, 03:05:14 AM »
Thanks for the reply.  Much appreciated.

I purchased the system with OS 3.2.2 ROMs and the OS installed, so I didn't have a registered version to get the 3.2.3 upgrade.  I threw some coin at Hyperion and purchased the digital version of OS 3.2 yesterday.  I then mimicked my A1200 + GVP A1230/1291 OS 3.2.2 setup with UAE.  Running on UAE shows the exact same problem.  I pulled down and installed the 3.2.3 update and ROMs on my UAE image and still no luck.  I'm going to try installing on real hardware after I burn the new set of 3.2.3 ROMs.  I'm not hopeful, though.

MuLibs is configured to execute GVPInit.  Unfortunately, it also does not resolve the issue.

The same setup with OS 3.1, 3.5, and 3.9 all work flawlessly on UAE.  I may go back to 3.1 ROMs and OS 3.9 on the real hardware until this issue is resolved or a workaround can be found.

I reached out to Hyperion support but haven't gotten a response.