newcomb@altair.la.locus.com (Chris Newcomb) (11/20/90)
Hi everybody. I'm trying to create an installation set (of diskettes) for a Windows 3.0 network driver, and have run into a small but irritating problem. (Note that in all examples that follow, all information specific to our driver software has been replaced with generic names.) The installation diskette contains three files: OEMSETUP.INF /* Setup information file */ DRIVER.DRV /* Driver */ DRIVER.HLP /* Driver online help file */ The OEMSETUP.INF file looks like this: ------------------------------------------------------------------------------ [disks] 1 = . ,"Network Driver disk #1" [network] driver = 1:driver.drv, "Network Driver", 1:driver.hlp, , , , ------------------------------------------------------------------------------ When I run SETUP (from the Windows directory \WIN on my hard disk) and ask to install a network driver, I select "Other (Requires disk provided by a network manufacturer)", and it asks me to insert the network driver disk, with the default drive/path given as "A:\". I press return; it reads from drive A and pops up a box containing "Network Driver" (the name of my driver) in it. So far so good. So, I press return to select my driver, and the following message pops up: ------------------------------------------------------------------------------ Please insert the: Network Driver disk #1 If the files on this disk can be found at a different location, enter a new path to the files in the prompt below. C:\WIN ------------------------------------------------------------------------------ SETUP appears to be looking for the files in the same directory as it is run; it cannot find the files until I erase "C:\WIN" and replace it with "A:\". WHY? It already knows there's a network driver diskette in drive A; it had to read the name of my driver from it. If I run SETUP from drive A, it thinks that Windows has not been installed yet, and wants to install all of Windows. Is this a bug in SETUP, or is something wrong with my OEMSETUP.INF file? Has anybody run into this problem before? Thanks! Chris newcomb@prodnet.la.locus.com