GVP a500+ HD8+

25 February 2007, 00:13

Using an amiga 500 and the GVP a500+ HD8+

I connected a scsi cdrom to the GVP and I can only use disc's that
Have less than 80 megs of data on them. Is that supposed to be that way?Amiga won't recognize any disc with more than 80mb

Also,
I Hooked up a iomega zipcd to same GVP and I can only access disc's
That are partition at 48mb or less. Any partition larger and amiga won't recognize it.

Any suggestion??

Zetr0 · 25 February 2007, 00:22

heys webfuzz

welcome to the EAB, i am sure you will like it here,

your problem sounds very similar to another on here that uses an identical device.

I belive that to configure your hard disks properly using HDTools BOX you are required to to put the gvp.device in the tool types of HDToolBox.

i will see if i can find the thread for you.

Zetr0 · 25 February 2007, 00:24

aha!

heres the thread

http://eab.abime.net/showthread.php?...hlight=gvp+500

hope this helps.

25 February 2007, 07:50

Close but no cigar. <g>

I have these limitations that just don't make sense.

also

I noticed in my mountlist that my cdrom refers to "scsi.device" I have
no file anywhere named scsi.device. Is "scsi.device" really a file or
just a reference to internal code??

Jope · 25 February 2007, 09:53

It should be gvpscsi.device in your case .. that's the name the driver shows up as in memory, but it can also be a file in devs:

You can use for example sysinfo to view all the devices you have.

02 March 2007, 08:25

Ok. it's a memory thing. I renamed the mountlist and every scsi device works, but again.. cdroms only 80mb. also can't read a zipdisk unless it's
partitioned to 48 megs. if i try to format a zipdisk for the full 95 mb about
1/2 way the scsi drive just starts clicking and never stops!
even tried a clean boot 2.x disk and same thing. that's why I am lead to believe that this is a GVP HD8+ issue. still... doesn't make sense!!!!

coze · 02 March 2007, 13:39

you can use memcheck to test your memory. also what version gvp scsi rom do you have ? (version gvpscsi.device) a newer version may fix problems (last one is version 4.15).

02 March 2007, 16:38

i never found a gvpscsi.device driver. the only thing i could find is something that I need to burn to rom (which i can't do). so I'm using all scsi devices with orginal gvpscsi.device found in memory (not a device file).
so using this method, i have no need for a mountlist. i did try the mountlist way with a gvp mountlist entry for cdrom's that i found on the net. Worked! but made no difference. Mountlist entry or no Mountlist entry made no difference at all. Both ways worked the same.

does anyone have the 4.15 gvpscsi.device driver?

coze · 02 March 2007, 16:54

here. I think you'll want the binddrivers driver.

02 March 2007, 17:07

tried that already. it's a .hex file. have no clue what to do the the gvpscsi4.hex file!

coze · 03 March 2007, 05:37

No' not the hexfile. You need the BindDrivers driver and put it into expansion drawer and boot workbench (or something like this)

whiteb · 03 March 2007, 08:34

Quote:

Originally Posted by webfuzz

i never found a gvpscsi.device driver. the only thing i could find is something that I need to burn to rom (which i can't do). so I'm using all scsi devices with orginal gvpscsi.device found in memory (not a device file).
so using this method, i have no need for a mountlist. i did try the mountlist way with a gvp mountlist entry for cdrom's that i found on the net. Worked! but made no difference. Mountlist entry or no Mountlist entry made no difference at all. Both ways worked the same.

does anyone have the 4.15 gvpscsi.device driver?

gvpscsi.device is contained in the HD8+'s ROM, not anywhere on Harddisk.

coze · 03 March 2007, 09:09

Yes, you can't find it on the HD. Just type "version gvpscsi.device" on the shell and tell us the result.

08 March 2007, 05:00

Hmmm.. I learned something new.. didn't know you could do that. anyways..... it says version 3.7

Also, I installed 3.1 roms today and still the same.

coze · 08 March 2007, 07:51

that's a pretty old version. (3.7) you should get yourself at least something over 4.5 I guess. Or, alternately you can boot from a workbench floppy with gvp binddrivers driver in the expansion drawer. Then it should load it from the disk, and not use the 3.7 rom you have on board. You can check if it works with the version command. Or you can find ppl on ebay offering these roms. The 3.1 rom you mentioned is probably your amiga kickstart, which is irrelevant with the gvpscsi.device.

whiteb · 08 March 2007, 07:54

Quote:

Originally Posted by webfuzz

Hmmm.. I learned something new.. didn't know you could do that. anyways..... it says version 3.7

Also, I installed 3.1 roms today and still the same.

Of course it hasnt altered it, gvpscsi.device is stored in the HD8+'s own EEPROM, which is loaded to system memory at boot for execution.

11 March 2007, 01:56

No..No.. I didn't install/upgrade to rom 3.1 to fix the gvp problem. Ha ha I just happend to get a switchable 2.04 and 3.1 rom. (ebay)

Ok. this is what I did:
1. downloaded this file: http://babel.org/download/2/gvpscsi4.tar.bz2
2. unpacked it. got 2 files: gvpscsi and gvpscsi.info
3. copied both files to dh0:expansion
4. rebooted amiga and checked version by: version gvpscsi.device
and it still says verion 3.7

5. even tried clicking on the gvpscsi icon in expansion and still says version 3.7

To be honest.. i'm beginning to think that there's something wrong with my gvp A500+. Even with version 3.7 I should be able to access cdroms over 80 megs!?

11 March 2007, 03:04

this is my cd0 file in wbstartup directory:

/* $VER: CD0 2.40 (14.12.97)
*
* CD-ROM filesystem mount entry
* amicdfs or cdfilesystem or fastfilesystem
*/

Device = gvpscsi.device
Unit = 0000000001 (this is for my Pioneer 604x drive)
FileSystem = L:AmiCDFS (i d/l this from aminet. should i use it?)
Flags = 0
BlocksPerTrack = 32
BlockSize = 2048
Reserved = 0
LowCyl = 0
HighCyl = 11000
Surfaces = 1
Buffers = 64
BufMemType = 1
Mask = 0x7fffffff
GlobVec = -1
Priority = 10
DosType = 0x43444653
StackSize = 600
Mount = 1

Control = "LC BL=8 FB=32"

/* Control field template:
*
* LC=LOWERCASE/S,CS=CASESENSE/S,
* HF=HFSFIRST/S,LN=LONGNAMES/S,TD=TRACKDISK/S,
* BL=BUFFERLINES/K/N,FB=FILEBUFFERS/K/N,
* DC=DISKCHANGE/K/N,MT=MOTORTIME/K/N,
* SD=STARTDELAY/K/N,TDC=TDCHANGE/S,
* TOSHIBA/S,OLDMODE/S
*/

alexh · 11 March 2007, 11:31

The file needs to be in SYS:Expansion (which may be dh0:expansion)

Do you have a "binddrivers" line in your s:startup-sequence?

It is useless having the files in SYS:Expansion without that line in your startup-sequence.

alexh · 13 March 2007, 10:32

Quote:

Originally Posted by Ralph Babel

> It is useless having the files in SYS:Expansion
> without that line in your startup-sequence.

... or with the ROM driver still active.

It looks like you have to disable the ROM inorder to use the binddrivers version.

I think (not 100% sure) it means you have to sacrifice auto-booting (unless you can find a way to unload the SCSI ROM driver after boot and before binding.

Try the switch in the other position, boot from floppy disk and try bind drivers?

25 February 2007, 00:13	#1
webfuzz Posts: n/a	GVP a500+ HD8+ Using an amiga 500 and the GVP a500+ HD8+ I connected a scsi cdrom to the GVP and I can only use disc's that Have less than 80 megs of data on them. Is that supposed to be that way?Amiga won't recognize any disc with more than 80mb Also, I Hooked up a iomega zipcd to same GVP and I can only access disc's That are partition at 48mb or less. Any partition larger and amiga won't recognize it. Any suggestion??

11 March 2007, 11:31	#19
alexh Thalion Webshrine Join Date: Jan 2004 Location: Oxford Posts: 14,448	The file needs to be in SYS:Expansion (which may be dh0:expansion) Do you have a "binddrivers" line in your s:startup-sequence? It is useless having the files in SYS:Expansion without that line in your startup-sequence. Last edited by alexh; 11 March 2007 at 11:46.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
a500 hd8+ gvp and MO scsi drive	tekopaa	support.Hardware	12	08 February 2013 20:58
For Sale : GVP A500-HD8+ Series II	jonmoss	MarketPlace	3	23 August 2011 12:36
GVP Impact A500 HD8+ dead HD	Lobotomika	support.Hardware	5	06 June 2011 07:30
Mint A500+ with GVP HD8	Torch500+	MarketPlace	22	18 January 2011 14:03
A500 gvp hd8+ install	paulcan	support.Hardware	3	08 July 2009 00:07

25 February 2007, 00:22	#2
Zetr0 Ya' like it Retr0? Join Date: Jul 2005 Location: United Kingdom Age: 49 Posts: 9,768	heys webfuzz welcome to the EAB, i am sure you will like it here, your problem sounds very similar to another on here that uses an identical device. I belive that to configure your hard disks properly using HDTools BOX you are required to to put the gvp.device in the tool types of HDToolBox. i will see if i can find the thread for you.

25 February 2007, 00:24	#3
Zetr0 Ya' like it Retr0? Join Date: Jul 2005 Location: United Kingdom Age: 49 Posts: 9,768	aha! heres the thread http://eab.abime.net/showthread.php?...hlight=gvp+500 hope this helps.

25 February 2007, 07:50	#4
webfuzz Posts: n/a	Close but no cigar. <g> I have these limitations that just don't make sense. also I noticed in my mountlist that my cdrom refers to "scsi.device" I have no file anywhere named scsi.device. Is "scsi.device" really a file or just a reference to internal code??

25 February 2007, 09:53	#5
Jope - Join Date: Jul 2003 Location: Helsinki / Finland Age: 43 Posts: 9,900	It should be gvpscsi.device in your case .. that's the name the driver shows up as in memory, but it can also be a file in devs: You can use for example sysinfo to view all the devices you have.

02 March 2007, 08:25	#6
webfuzz Posts: n/a	Ok. it's a memory thing. I renamed the mountlist and every scsi device works, but again.. cdroms only 80mb. also can't read a zipdisk unless it's partitioned to 48 megs. if i try to format a zipdisk for the full 95 mb about 1/2 way the scsi drive just starts clicking and never stops! even tried a clean boot 2.x disk and same thing. that's why I am lead to believe that this is a GVP HD8+ issue. still... doesn't make sense!!!!

02 March 2007, 13:39	#7
coze hastala vista winny vista Join Date: Feb 2006 Location: mt fuji Age: 46 Posts: 1,335	you can use memcheck to test your memory. also what version gvp scsi rom do you have ? (version gvpscsi.device) a newer version may fix problems (last one is version 4.15).

02 March 2007, 16:38	#8
webfuzz Posts: n/a	i never found a gvpscsi.device driver. the only thing i could find is something that I need to burn to rom (which i can't do). so I'm using all scsi devices with orginal gvpscsi.device found in memory (not a device file). so using this method, i have no need for a mountlist. i did try the mountlist way with a gvp mountlist entry for cdrom's that i found on the net. Worked! but made no difference. Mountlist entry or no Mountlist entry made no difference at all. Both ways worked the same. does anyone have the 4.15 gvpscsi.device driver?

02 March 2007, 16:54	#9
coze hastala vista winny vista Join Date: Feb 2006 Location: mt fuji Age: 46 Posts: 1,335	here. I think you'll want the binddrivers driver.

02 March 2007, 17:07	#10
webfuzz Posts: n/a	tried that already. it's a .hex file. have no clue what to do the the gvpscsi4.hex file!

03 March 2007, 05:37	#11
coze hastala vista winny vista Join Date: Feb 2006 Location: mt fuji Age: 46 Posts: 1,335	No' not the hexfile. You need the BindDrivers driver and put it into expansion drawer and boot workbench (or something like this)

03 March 2007, 09:09	#13
coze hastala vista winny vista Join Date: Feb 2006 Location: mt fuji Age: 46 Posts: 1,335	Yes, you can't find it on the HD. Just type "version gvpscsi.device" on the shell and tell us the result.

08 March 2007, 05:00	#14
webfuzz Posts: n/a	Hmmm.. I learned something new.. didn't know you could do that. anyways..... it says version 3.7 Also, I installed 3.1 roms today and still the same.

08 March 2007, 07:51	#15
coze hastala vista winny vista Join Date: Feb 2006 Location: mt fuji Age: 46 Posts: 1,335	that's a pretty old version. (3.7) you should get yourself at least something over 4.5 I guess. Or, alternately you can boot from a workbench floppy with gvp binddrivers driver in the expansion drawer. Then it should load it from the disk, and not use the 3.7 rom you have on board. You can check if it works with the version command. Or you can find ppl on ebay offering these roms. The 3.1 rom you mentioned is probably your amiga kickstart, which is irrelevant with the gvpscsi.device.

11 March 2007, 01:56	#17
webfuzz Posts: n/a	No..No.. I didn't install/upgrade to rom 3.1 to fix the gvp problem. Ha ha I just happend to get a switchable 2.04 and 3.1 rom. (ebay) Ok. this is what I did: 1. downloaded this file: http://babel.org/download/2/gvpscsi4.tar.bz2 2. unpacked it. got 2 files: gvpscsi and gvpscsi.info 3. copied both files to dh0:expansion 4. rebooted amiga and checked version by: version gvpscsi.device and it still says verion 3.7 5. even tried clicking on the gvpscsi icon in expansion and still says version 3.7 To be honest.. i'm beginning to think that there's something wrong with my gvp A500+. Even with version 3.7 I should be able to access cdroms over 80 megs!?

11 March 2007, 03:04	#18
webfuzz Posts: n/a	this is my cd0 file in wbstartup directory: /* $VER: CD0 2.40 (14.12.97) * * CD-ROM filesystem mount entry * amicdfs or cdfilesystem or fastfilesystem / Device = gvpscsi.device Unit = 0000000001 (this is for my Pioneer 604x drive) FileSystem = L:AmiCDFS (i d/l this from aminet. should i use it?) Flags = 0 BlocksPerTrack = 32 BlockSize = 2048 Reserved = 0 LowCyl = 0 HighCyl = 11000 Surfaces = 1 Buffers = 64 BufMemType = 1 Mask = 0x7fffffff GlobVec = -1 Priority = 10 DosType = 0x43444653 StackSize = 600 Mount = 1 Control = "LC BL=8 FB=32" / Control field template: * * LC=LOWERCASE/S,CS=CASESENSE/S, * HF=HFSFIRST/S,LN=LONGNAMES/S,TD=TRACKDISK/S, * BL=BUFFERLINES/K/N,FB=FILEBUFFERS/K/N, * DC=DISKCHANGE/K/N,MT=MOTORTIME/K/N, * SD=STARTDELAY/K/N,TDC=TDCHANGE/S, * TOSHIBA/S,OLDMODE/S */

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)