Article View: comp.os.os2.misc
Article #16977Re: "Cannot find VLIDE.ADD" - where should it be?
From: steve ames
Date: Fri, 14 Jun 1996 00:00
Date: Fri, 14 Jun 1996 00:00
30 lines
1757 bytes
1757 bytes
In message <4polu5$a41@styx.uwa.edu.au> - aledain@receptor.pharm.uwa.edu.au (Dr Alex) writes: :> :>G'Day Warpers, :> :>I have a VL-IDE controller card that can use a device driver called :>VLIDE.ADD to allow 32-bit access to the drive. When I include the line :>BASEDEV=VLIDE.ADD in CONFIG.SYS (after remming BASEDEV=IBM1SOD.ADD, as :>per the readme file's instructions), warp reports it cannot find :>VLIDE.ADD ... this particular file. I realise that BASEDEV's cannot have :>paths, so I have tried placing this device in all the directories (\, :>\OS2, \OS2\BOOT, \OS2\DRIVERS, \OS2\SYSTEM), but it still reports this :>message. :> :>Any ideas? Furthermore, does anyone have a newer version of the driver :>... i.e. one where the docs mention OS/2 version 3! :> :>cheers, Alex. :> I have a VLB contoller that can with its own driver as well. The QDI1S506.ADD driver is in \OS2 and in \OS2\BOOT However, I Rem'ed it out when I installed the ATAPI.ZIP files and an ATAPI CD ROM. In your case, it may be that the card manufacturer didn't bother to write a driver for Warp. I haven't seen an updated QDI driver either. Steve Ames sames@magi.com
Technical Details
Message-ID:
<4pqgcp$ne0@news.istar.ca>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1044c2,2e179a9db740619b X-Google-Attributes: gid1044c2,public X-Google-Thread: 10a752,2e179a9db740619b X-Google-Attributes: gid10a752,public X-Google-Thread: f4337,2e179a9db740619b X-Google-Attributes: gidf4337,public From: sames@magi.com (steve ames) Subject: Re: "Cannot find VLIDE.ADD" - where should it be? Date: 1996/06/14 Message-ID: <4pqgcp$ne0@news.istar.ca> X-Deja-AN: 160083731 organization: iSTAR internet inc. newsgroups: comp.os.os2.misc,comp.os.os2.setup.misc,aus.computers.os2