Welcome, Guest. Please login or register.

Author Topic: GVP Binddrivers Causes Black Screen  (Read 3387 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Pat the Cat

Re: GVP Binddrivers Causes Black Screen
« on: July 20, 2017, 02:45:30 PM »
Binddrivers expects all drivers loaded to be compatible with the Kickstart versions.

You can patch 3.1 to have 64 bit support for big partitions (over 2GB) BUT YOU CANNOT BOOT OFF SUCH A DEVICE.

Try a boot partition of 1GB on the card. 3.1 is 32 bit only, can't boot off big partitions.
 
 EDIT: 4.15 also expect a different version of gvpscsi.device from what I understand here, direct download is 2nd link
 
 
 http://babel.de/amiga.html
 
http://babel.de/download/gvpscsi4.tar.bz2
« Last Edit: July 20, 2017, 02:51:33 PM by Pat the Cat »
"To recurse is human. To iterate, divine."

A1200, Vanilla, Surf Squirrel, SD Card, KS 3.0/3.z, PCMCIA dev
A500, Vanilla, A570, Rev 5, KS 1.2/1.3 Testbench system
Rasp Pi, UAE4ARM, 3D laser scanner, experimental, hoping for AmigaOS4Arm, based on Watterott Fabscan Pi
 

Offline Pat the Cat

Re: GVP Binddrivers Causes Black Screen
« Reply #1 on: July 21, 2017, 02:41:00 PM »
Quote from: madgrizzle;828450
Using KS3.1 from AmigaKit. It won't "completely" boot (as described above) from floppy with Ralph's 4.15 Binddrivers (gvpscsi.device / gvpscsi.info) installed in the expansion directory of an OS3.9 Emergency Boot Disk and the GVP ROM is disabled. The computer, when the the GVP ROM is enabled, will boot from the same floppy (I assume because it's not using the binddrivers but rather the drivers provided by the ROM??) This is the point I want to confirm, can I have a v3.12 ROM in the GVP, disable it, but boot from a floppy with v4.15 binddrivers. Forget the PCD-50B for now.. just trying to get the 4.15 firmware/drivers to work the the GVP Combo card.

Maybe they switch it back for 3.5 and 3.9, but AFAIK from KS 2 onwards, you have to put devices in devs drawer the your boot disk, not expansion drawer. That was for KS and Workbench 1.3, for adding hardware.

If PATH has been added for Expansion drawer, I would guess binddrivers would find the device anyway (it would search every PATH'd directory for all .device files). But if the gvpscis.device is in the wrong drawer and binddrivers can't find it, that would be an issue.

Isnt there a handler file as well that has to go in L drawer of boot disk? I don't seem to recall one for GVP hard disks. Again, more of a old school hard drive problem rather than the later ones, GVP much more plug and play.
"To recurse is human. To iterate, divine."

A1200, Vanilla, Surf Squirrel, SD Card, KS 3.0/3.z, PCMCIA dev
A500, Vanilla, A570, Rev 5, KS 1.2/1.3 Testbench system
Rasp Pi, UAE4ARM, 3D laser scanner, experimental, hoping for AmigaOS4Arm, based on Watterott Fabscan Pi