CompuServe Thread

#GVP Software bugs

5 messages in this thread
#75175From: Wayne ColeFeb 22, 1994 3:31 AM
I've come across a couple of bugs in GVP software. 1) attempts to: copy <ascii_file> TO GVPPAR0: generate an error message, "object not found" 2) attempts to: copy <ascii_file> TO GVPSER0: generate an error message, "object not found" 3) the gvpscsi.device that is with the 4.12 and 4.13 ROMS seems prone to lock-up if you have multiple processes trying to access the same disk (not necessarily the same partition). This appears anly whent the system is running 3 or 4 process that each transfer large blocks of data to/from the disk. Usually it happens when an attempt is made to open another application from workbench off a ToolManager dock where the application resides on the disk being written to by the other process(es). The lock-up manifests as a Hard drive light that stays on, and the keyboard, mouse and remote access via ParNET are all locked out. The screen also does not update. This happens on one system with GVP Combo '030 33 Mhz, 16 MB ram, quantum 525LPS and Video Toaster 4000 board, parNET running and connected to the Amiga parallel port. It also happens on a system with a G-Force 040 with 16 MB ram, Quantum 105 LPS, Maxtor 1017 (1 gig), Fujitsu 2511 MO, all internal, a Toshiba 3401B CD-ROM and MaynStream 2.0 GIG dat externally connected to the '040 board. The ParNET is connected to the first of 2 parallel ports from a MFC II board. The serial port of the '040 is used for the modem. It's parallal port is set to replace the base AMiga parallel port and serves the printer. The base Amiga parallel port is taken up by an AmiLink dongle. Also in the box is AMiLink card, studio16, Y/C Plus, Toaster 3.1, FFV (version 2) and DKB megachip. Note the lock-up is relatively rare, except that I got it 3 times today on one machine and twice on the other where I hadn't seen it before today since I upgraded from ADos 1.3 and GVP 4.4 ROM.
#75214From: GVP TechFeb 22, 1994 1:51 PM
Wayne, You never mentioned what version of the GVPIO device driver is in your SYS:Expansion drawer! This can tell us exactly why you get the "not found" errors. Sounds like you have the latest version of that driver (1.8) but you are still trying to access the OLD names, which were gvpser0: and gvppar0:. Under v1.8, the names are GP0: and GS0: In regard to the SCSI error, nothing like that has ever been reported before, and we in Tech have never encountered it ourselves, and we have run systems that have multiple programs accessing the drive simultaneously. This could be due to a problem in cabling or termination. Specifically regarding the older Combo 33MHz 030 card, I suggest that you install the previous ROM version (3.12 to 4.0) instead of the ROM that is currently installed.
#75419From: Wayne ColeFeb 25, 1994 4:20 AM
Hmmm, I think I have a 4.4 and I used to have an Omni 3.5, but I don't recall seeing it when I straightened out my "parts bin" last week. With the older revs wasn't there something about the HD's not being able to DMA to 32 bit mem especially above autoconfig space? Seems like I remember that was the reason I was advised to upgrade when I did the first time. On the gvpio, version command shows 1.7. Also when I type "assign" down at th end of the list where it shows the devices it shows GVPSER0 and GVPPAR0. Should I be using 1.8 and is that available on your BBS? As for the SCSI problems, I've seen it only rarely (except that one day when I got a raft of them) and the disk activity is usually multiple applications moving big (like megabyte) files around. wmc – via Autopilot!
#76079From: GVP TechMar 3, 1994 7:49 AM
Wayne, Version 1.8 of the I/O Extender software is available over our BBS (610-337-5815) and I would recommend that you download and try it. Make sure that you remove ALL of the previous software before installing 1.8. GVP TECH
#76386From: Steve Peoples @ GVPMar 7, 1994 2:06 PM
This software is also posted in the GVP section of the File Libraries here on CompuServe. Steve