Thread View: EMail
2 messages
2 total messages
Started by Sascha Picchiantano
Sun, 13 Aug 1995 16:29
Re: A2090a <> GVP (transfering drives)
Author: Sascha Picchiantano
Date: Sun, 13 Aug 1995 16:29
Date: Sun, 13 Aug 1995 16:29
38 lines
2020 bytes
2020 bytes
Hello! On 11-Aug-95 13:47:58 you wrote about Re: A2090a <> GVP (transfering drives). This is what I have to say about it: >> Good, did it. Works fine. Exept for one thing... I use the 2090a to boot >> my system (I have WB on a 20 meg MFM drive). Now since I have both >> controllers in there, the machine takes AGES to start booting. I guess >> this is because both controllers are autoboot. >> Is there a way I can speed this up? It's annoying... > If you set your GVP card to NOT autoboot, you can then put the gvpscsi and > gvpscsi.info file in your SYS:Expansion drawer, and it will not try to > autoboot from the GVP card. Edit your SYS:S/Startup-Sequence and change the > line that says: > Binddrivers > to: > Run > nil: < nil: Binddrivers Ok, I did that and it works. Booting is now just as fast as it was before. However, I run into new problems now. If the GVP's autoboot jumper is removed, and binddrivers is used, my machine seems to recognize the drive only AFTER the WB has been loaded (after the loadwb command that is). Because I do a lot of assigns and path commands in the user-startup that point to the drive on the GVP, this doesn't work anymore. Is there a way around this? How can I make the machine recognize the drive before loadwb? Thanks for your help! Not only the booting has sped up, some other problems disappeared as well (I had loads of cheksum errors on the GVP drive. They are gone now :) bye, _Sascha Picchiantano (cscheper@ix.urz.uni-heidelberg.de)
Re: A2090a <> GVP (transfering drives)
Author: Chris"Big-Kahuna"Rampson
Date: Thu, 17 Aug 1995 13:06
Date: Thu, 17 Aug 1995 13:06
27 lines
1910 bytes
1910 bytes
Sascha Picchiantano (cscheper@ix.urz.uni-heidelberg.de) wrote:
: >> Good, did it. Works fine. Exept for one thing... I use the 2090a to boot
: >> my system (I have WB on a 20 meg MFM drive). Now since I have both
: >> controllers in there, the machine takes AGES to start booting. I guess
: >> this is because both controllers are autoboot.
: However, I run into new problems now. If the GVP's autoboot jumper is
: removed, and binddrivers is used, my machine seems to recognize the drive
: only AFTER the WB has been loaded (after the loadwb command that is).
: Because I do a lot of assigns and path commands in the user-startup that
: point to the drive on the GVP, this doesn't work anymore.
: Is there a way around this? How can I make the machine recognize the drive
: before loadwb?
Boot from the GVP! Use the RDB stuff for that drive! Make sure the GVP drive
is at id=0. Set reselect "off", sync "on", LastDisk "on", LastLUN "on" and
LastTarget "on". It should boot like greased lightning!
--
_/_/_/ _/ _/ Chris "Big Kahuna" Rampson
_/ _/_/_/ _/ _/_/ _/_/_/ crampson@ford.com
_/ _/ _/ _/_/ _/ _/_/ NO cutdowns,flames or insults
_/ _/ _/ _/ _/ _/_/ NO such thing as a stupid question!
_/_/_/ _/ _/ _/ _/ _/_/_/ "NOT an OFFICIAL FORD spokesperson"
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads